Choose a statement
Select a PDF or a clear JPG, PNG or WebP statement image.
Extract and review a statement transaction table, then save UTF-8 CSV with original date, amount and reference strings.
English statement layouts are the tested starting point. Selectable PDFs use native text; scanned pages and images use local OCR.
Leave this off for statements containing multiple accounts. Unrelated tables stay separate.
Your statement stays on your device. File names, account details and transaction values are never sent to analytics.
Select a PDF or a clear JPG, PNG or WebP statement image.
Check column mapping, wrapped descriptions, amounts and balances. Edit uncertain values against your source.
Save the reviewed transaction table. Excel cells preserve your values as text.
Move transaction rows from old PDF statements into an editable spreadsheet.
Review extracted transactions before using them in your own bookkeeping workflow.
Recover tables from readable statement scans with local OCR, then correct recognition errors.
The details that matter before you use Bank Statement to Excel.
No. PDF parsing, OCR, review and export run in your browser. Statement content, filenames, account identifiers and transaction values are not sent to analytics or stored in the control database.
Yes. Scanned pages use the existing local OCR engines. Selectable tables use native PDF text first and do not need OCR. Clear, upright English statements are the tested starting point.
No. Bank statement layouts vary. Aligned tables with explicit date, description and amount or debit/credit headers work best. Complex layouts may need manual correction or remain a raw extracted table.
Yes. Both downloads contain the selected, reviewed table and your edits. Excel uses text cells. CSV is UTF-8 with a BOM; import columns as text because spreadsheet software may otherwise change dates, leading zeros or formula-like strings.
Yes. OCR can confuse digits, punctuation and words. Check every amount, balance, date and reference against the source before using the result.
It preserves extracted strings and your edits. It does not infer debit/credit direction, currency, categories or signs, and never repairs values using arithmetic. Clearly supported wrapped descriptions and repeated headers may be consolidated; original extracted tables remain available.
PDFs up to 25 MB and 300 pages are processed sequentially. You can opt to combine matching transaction schemas on consecutive pages from the same ledger; keep this off for multiple accounts. Other tables remain selectable. Images are limited to 15 MB and 20 megapixels.
Extraction is not verification. Column placement, wrapped lines and OCR may be uncertain. Correct the mapping and cells before export. This tool extracts data and does not provide financial advice.