FAQ
Frequently asked questions about how Bank Statement Parser works, privacy, and how to use it effectively.
What does this tool do? 📄
Bank Statement Parser reads your statement PDF, extracts transaction lines, and converts them into structured rows.
You can then copy the output as TSV and paste it into your spreadsheet without manually typing each transaction.
Which bank is currently supported? 🏦
Right now, parsing is tuned for ABN AMRO statement layouts.
Other banks are listed in the interface but are not fully supported yet.
How do I use it? 🧭
- Upload your PDF statement from the homepage parser.
- Review the parsed transactions in the table.
- Copy the generated TSV output into your spreadsheet.
- Do a quick final check before analysis, especially dates and amounts.
Are my files uploaded to a server? 🔒
No. Parsing happens locally in your browser during normal use.
Your statement file stays on your device, and the app is designed with a local-first workflow.
Do I still need to review the output? ✅
Parser rules can be affected by bank layout changes or uncommon transaction formats.
A quick final check helps catch edge cases before you use the data for budgeting or analysis.
This is recommended for any parser tool.
Why export as TSV instead of CSV? 🔁
TSV uses tabs to separate columns, while CSV uses commas.
Because transaction descriptions often contain commas, TSV reduces broken column splits when pasting into spreadsheet tools.