Bank statement converter

Yes. Each connection can convert up to 30 pages a day without an account or email, with up to 30 pages and 20 MB per file. For more, paid plans add a monthly pool of pages: Starter is $9 a month for 150 pages, Pro $19 for 500 and Business $49 for 2,000, with 20% off yearly. See pricing.

Drop the PDF into the converter at the top of this page, review the table that appears, and choose Download Excel. Choose Download CSV instead for a plain text file. The workbook itself is described on the pdf bank statement to Excel page.

PDF statements, text, scanned or password-protected, and photos saved as JPG, PNG or HEIC, from any bank or card issuer. Separate debit and credit columns, DR and CR markers, decimal commas, Indian digit grouping and newest-first statements are all handled. Scans and photos are read with English OCR.

Yes. Choose or drop up to 24 files together. Each is converted and checked, then joined into one workbook per account, in date order. DocFig checks that each statement's closing balance matches the next one's opening balance, names any missing month, and keeps a transaction once when two statements overlap, listing the removed copies on their own sheet. Before converting, it says how many pages fit in today's free allowance.

Every row is checked against the statement's own arithmetic: the running balance on each line, the opening and closing balance, and any printed totals. Each amount must also appear in the page text. When something does not add up, the row is highlighted with the reason, so you know exactly where to look.

Yes. The file is sent over HTTPS to the DocFig server, held in memory while it is converted, and never written to disk. Account and card numbers are masked before the text is passed to the AI model that reads the rows. Nothing is kept after the result reaches your browser. DocFig does not train on statements, and OpenAI states that API data is not used to train its models.

Yes. After the table appears, choose Download CSV. The file is UTF-8 with ISO dates, a dot as the decimal point, and both a signed amount and separate money in and money out columns.

Yes. Scanned PDFs and photos saved as JPG, PNG or HEIC are read with OCR and then checked like any other statement. A flat, sharp, well-lit image converts best.

Yes. Purchases, fees and interest become money out; payments and refunds become money in. When the statement prints a previous and new balance, the rows are checked against them.

Most statements finish in well under a minute. Each page takes a few seconds, and pages of a long statement are read several at a time.

Yes. Upload the statement as it is; DocFig asks for the password your bank gave you, opens the file in memory and converts it. The password is used once and is never stored or sent to the AI model. Common password formats.

Date, Description, Money out, Money in, Amount and Balance, plus a Check column that explains any row that failed a check. Amount is signed: positive for money in, negative for money out.

Where a balance is printed on each line, every balance must equal the previous one plus the transactions in between. The opening balance plus every row must reach the closing balance, printed totals must match, and every amount must appear in the page text. If money in and out were swapped on a row, the printed balance proves it and the row is corrected and labelled; anything uncertain is highlighted, never quietly changed.