Bank statement extraction
Extraction is turning the printed rows of a statement back into data. Upload a PDF or scan and download a file with one transaction per row, using the same engine as the converters.
Upload a file
What you get out
- One row per transaction, in statement order
- Date, description, and amount in their own columns
- Rows read from the content of the statement, not from page coordinates
- CSV, Excel, or any of the other supported output formats
How to convert
Upload the statement
A PDF from the bank as downloaded, or a scan.
Pick an output format
CSV or Excel for a spreadsheet, JSON if the next step is code.
Download the data
One row per transaction, ready to import or inspect.
Statements it handles
Layouts differ from bank to bank, so nothing is matched against a fixed template. An unusual statement still produces a table you can check before exporting — which is what makes it usable for bookkeepers and accountants who receive statements from every client.
PDF statements and CSV exports
A statement downloaded from your bank, or the CSV your bank lets you export. Both arrive as the same clean table.
Multi-page statements, read as one table
A statement that runs over several pages — or several statements uploaded together — is read as one continuous table, not one file per page.
Amounts and dates kept as your bank prints them
Debit and credit signs, decimal places and date formats are left as printed, so the numbers still reconcile against the statement.
Scanned, image-only PDFs, read with OCR
A statement with no text layer is read with OCR and may need a quick review — the one case where a row can come out wrong.
- CSV
- Scan
Why this is more accurate than OCR
OCR reads a statement by position on the page, so a wrapped description or a pair of narrow amount columns sends the text to the wrong row. Reading the content instead of the coordinates is what keeps each transaction whole.
01
A wrapped description becomes two rows
The second line of a description sits below the first, so it is read as a new row — and the amount follows it down, onto the wrong transaction.
02
Debit and credit collapse into one column
Two narrow amount columns are read as one, so a payment and a deposit come out identical — the sign that told them apart is gone.
03
The totals block becomes transactions
Opening balance and closing balance are printed like rows, so they are read like rows — and land in your books as money that never moved.
Why OCR mangles bank statements — the four failures in detail.
Frequently asked questions
What is bank statement extraction?
Pulling the individual transactions out of a statement so they can be used as data — a row per transaction with the date, description, and amount separated into columns.
Is extraction the same as OCR?
No. OCR turns an image into text and reads the page by position, which breaks on tables. Extraction here reads what each piece of text is — a date, a description, an amount — so a wrapped line stays with its transaction.
What can it extract from?
PDF statements and CSV exports from your bank. Text-based PDFs give the cleanest result; scanned, image-only PDFs depend on OCR and should be reviewed.
Is my statement kept after extraction?
Only until it is converted, or 24 hours if it is never paid for. The result stays at your private link.
Do I need an account?
No. It works without signing up.