Privacy-first local tool. This page reads files in your browser and does not intentionally upload statement data. Do not send bank statements to Budget Toolkit. Review the preview carefully before exporting because PDF layouts, multi-line descriptions, balances, and scanned image statements can affect accuracy.

How to use it

Start with your bank's CSV export when available. If you only have a PDF, choose it locally or paste copied transaction table text. The browser extracts readable PDF text, estimates transaction rows, and lets you preview before export.

After previewing, use the mapping controls to decide which detected column should become date, description, debit, credit, amount, or balance. For the cleanest budget workflow, use the CSV Transaction Cleaner after export.

Why mapping matters

Bank statement PDFs are not standardized. Some show debit and credit columns, some show one signed amount column, and some place the balance at the end of a transaction row. Mapping keeps the tool flexible without asking you to send statements or trust a bank connection.

FAQ

Are statement files uploaded?

No. File reading and parsing are designed to run locally in your browser.

Will every PDF statement convert perfectly?

No. Text extraction varies by bank and PDF format. Scanned image PDFs usually require OCR and may not parse accurately in this local tool.

Related: CSV Transaction Cleaner, Budget Snapshot Calculator, and privacy policy.