Convert a PDF bank statement to CSV

Upload the PDF your bank gave you and download one clean CSV: one row per transaction, dates in a single format, amounts signed the way accounting software expects. It opens in Excel, Google Sheets or anything that reads CSV.

No AI. No Hallucinations. Just Deterministic Math.

How it works

  1. Upload the PDF

    Text-based PDFs are read from the page's own text layer. Scanned statements go through OCR. Several files at once are fine.

  2. Check it against the statement

    We add up the rows we found and compare them with the opening and closing balance, the column totals, or the running balance your statement prints. You see whether they match before you export, and which figure disagrees if they don't.

  3. Download the CSV

    Columns are Date, Description, Amount, Type, Category, Account and Source. Hide any you don't need before exporting. CSV export is included on every plan, including Free.

A staged file row for sample-statement.pdf reading “17 rows standardized” and “17 transactions reconcile against the statement’s printed opening (12,480.55) and closing (18,566.15) balances.”
Every file is checked against the totals the statement prints about itself, before you export.

What to know

No AI in the pipeline

Extraction is rule-based: the statement's text, the table's geometry and pattern-matching parsers. Nothing is guessed by a language model.

Nothing is kept

PDFs are processed in memory and discarded as soon as extraction finishes. CSV and Excel files never leave your browser.

What it costs

A PDF uses 1 credit per page. New accounts get 50 free PDF credits, no card required. CSV, Excel and OFX files are always free.

Common questions

How accurate is the extracted data?
PDF extraction uses each page's real text layer where available, with OCR as a fallback for scanned statements. CSV columns are auto-mapped to Date/Description/Amount from common header names — or, when a file's headers say nothing useful (some bank exports really do label their columns "Column 1" to "Column 7"), from the data itself. Both are best-effort: bank statement formats vary too much to guarantee perfect extraction, which is why every upload lands in an editable table where you can adjust the column mapping, edit, deselect or delete any row, and add one we missed, before exporting. We also check our own work: after extraction, we compare the rows we found against the totals your statement prints about itself, and show you the result as a badge next to the file rather than asking you to just trust the table.
What does the badge on each file mean — "Matches statement totals", "Running balance agrees", "Doesn't match statement", or "Verify against the statement"?
After extraction, we check whether the rows we found add up to what your statement says about itself — its opening and closing balance, its own column totals, or the running balance printed beside each row. "Matches statement totals" means they add up to the balances or totals it prints, to the cent. "Running balance agrees" is for transaction histories — the exports internet banking gives you, rather than monthly statements — which print no totals at all, only a balance on every row. Every row agrees with that balance, so nothing between the first and last row is missing or misread. It's a separate badge because it checks less: the first row's amount, and anything outside the dates the export covers, can't be checked this way. The running balance is also checked on statements that print totals, because it is checked at every row rather than once at the end, so it can tell you which row something goes wrong at — and it catches a case the totals cannot: a file that is missing transactions whose amounts happen to cancel out. "Doesn't match statement" means they don't, and we show you exactly which figures disagree. It also appears when the PDF itself is incomplete: if its page numbers say "Page 3 of 8" and the file has seven pages, or one page appears twice, the rows can't be the whole statement even if they add up to what the remaining pages print. "Verify against the statement" means your statement didn't print anything we could check against — no balances, no totals, no running balance — so we're telling you to eyeball it yourself rather than pretending it's fine. "Enter balances" beside it lets you type the opening and closing balance you can see, and the badge then reads "Matches balances you entered" or "Doesn't match your balances": the same check, against your figures instead of the statement's. It's a common enough outcome that we publish the actual rate across our own test corpus on the benchmark page rather than asking you to take a number on trust. None of this is the same as an accountant reconciling your account against an independent record; it only checks that what we extracted is internally consistent with what your own statement says. Edit an amount or delete a row afterward and we re-run the same check automatically, so the badge always reflects what you're about to export — and because that recheck runs entirely in your browser, fixing a flagged row never sends anything back to our servers or creates a new copy of your data there. Where a file printed nothing the check can be re-run from, the badge says "Edited since checked" instead. Hover over or tap any badge in your workspace to see all of them, with a line on what each means.
How do credits work?
CSV and Excel parsing is free on every plan, since it happens locally in your browser — you only need credits for PDFs, which use 1 credit per page. A statement that doesn't add up to the figures it prints isn't charged at all. New accounts start with 50 free PDF credits, and you can top up with a one-time Credit Pack or a Pro subscription.
What file types can I upload?
CSV, Excel (.xlsx/.xls), OFX/QFX, and PDF bank/credit card statements, including password-protected PDFs, and photos of a paper statement (.jpg, .png, .webp, and .heic where your browser can open it). CSV, Excel, and OFX/QFX are all parsed locally in your browser; PDFs are processed on our backend and use credits. A photo is turned into a PDF in your browser before it is sent, so it is processed and charged like a scanned PDF page: 1 credit per photo. Photos dropped together become one PDF, one page per photo in file-name order, because the pages of one statement belong together. For the best result, photograph the page flat, in good light, with the whole page in the frame.

All questions and answers

Try it on your own statement: 50 free PDF credits

No card required. CSV, Excel and OFX files are free on every plan.