Bank Statement to CSV

Extract transaction rows from PDF or image bank statements to CSV without inventing ambiguous rows.

How the transaction extractor works

Choose a PDF, JPG, PNG or WebP statement. The local parser identifies lines beginning with a date and requires a recognizable description and a decimal amount. If any dated line cannot be parsed unambiguously, it stops rather than exporting an incomplete statement.

Balances and CSV safety

Where two consecutive running balances are available, the tool checks whether the amount explains the balance change. An inconsistency is reported for manual review; it is not silently corrected. Text beginning with spreadsheet formula operators is neutralized before CSV export, while amounts remain numeric.

Important limitations

If extracted text preserves column separators (pipe, tab or semicolon), the parser recognizes Date, Description, Debit, Credit and Balance headers. Debits become negative amounts and credits positive amounts; repeated headers and reverse-chronological balances are supported. Conflicting debit/credit values, changed column layouts and unreadable dated entries stop export. Scanned statements that lose separators during OCR still require manual checking. Before download you must acknowledge comparing the output with the source; this is not bank-certified reconciliation.

Choose the date convention before extraction

For ambiguous dates such as 04/05/2026, choose day/month/year or month/day/year explicitly; otherwise automatic mode rejects the entry rather than guessing. When a convention is selected, the CSV writes ISO dates (YYYY-MM-DD) to avoid spreadsheet locale ambiguity.

Review before download

The tool displays up to 12 reconstructed transactions, including amounts and balances, before you acknowledge source comparison. Double-space-separated OCR tables are supported only when they have an explicit Amount column; debit/credit columns with missing separators are rejected. A contradictory running balance blocks export instead of being labeled verified.

Multi-line transactions and complete review

Some bank exports wrap a transaction description onto the next physical line. A continuation is joined only when explicit column delimiters are preserved and the date and every monetary column are empty. Rows with damaged dates but recognizable amounts are reported as rejected, not silently skipped. The preview has next/previous controls for checking all transactions, not only the first twelve; the CSV contains every accepted row. Missing balances cannot establish complete reconciliation.