Bank Statement to Excel / CSV
Extract a text-based PDF statement into editable transactions with page references, original values and separate account/currency balance checks. Export a local Excel workbook or an explicitly configured CSV.
Preparing your tool…
How to use it
- Load a statement and review the grid on each PDF page. Correct column boundaries and explicitly select repeated-header removal or text-only continuation merging.
- Map booking/value dates, description, debit/credit, currency, optional balance, account and period. Choose date, number and sign conventions explicitly.
- Compare original cells and page positions with the editable and normalized preview. Correct ambiguous values while retaining genuine repeated transactions.
- Enter opening and closing balances for each account/period/currency block. Review matches, differences and checks that are not possible, then confirm and export.
The two-page sample contains a multiline booking, two real Coffee transactions, account 000012 in CHF and account 000099 in EUR. Its final balances are CHF 2213.66 and EUR 485.00. Changing a debit from 12.50 to 12.51 exposes an exact −0.01 difference.
Details & limits
Text PDFs up to 25 MiB / 20 pages, 200 rows per page, 2,000 rows / 30,000 cells total, 4,000 characters per cell. Explicit complete dates and 0–4 amount decimals; at most 15 fixed-point digits. At most 20 million embedded image pixels; unsupported filters are rejected. Scans need a separate reviewed OCR workflow. No claimed compatibility with every bank. Embedded images: unfiltered/Flate pixels or checked JPEG, up to 8,192 px per side. Inline images, JPEG 2000, JBIG2, CCITT and unusual JPEG variants are unsupported.
Does a matching closing balance prove that all transactions were extracted correctly?
No. The exact equation opening + credits − debits = closing only checks totals within the selected account, period and currency. Missing balances are reported as not checkable. Excel includes numeric amounts, ISO dates as text, original/reviewed cells and balance sheets. CSV contains normalized transactions; the accompanying JSON preserves the source/check trace. Its optional apostrophe protection changes formula-looking text and reports the changed-cell count; no CSV profile protects every spreadsheet application.