CSV vs PDF vs XLSX: how your bank statement's format affects import
When you export a statement from your bank, the file format you're handed isn't just a technical detail - it decides how much work is left before that data becomes a usable budget. Some formats hand over clean, structured data. Others hand over something that was only ever meant to be printed.
What each format actually contains
Same transaction history, four very different starting points:
| Format | What it really is | How well it imports |
|---|---|---|
| CSV / TXT | Plain rows of structured data - one line per transaction, columns for date/amount/description | Automatic once its column layout is recognized, or mapped once for a new bank |
| XLS / XLSX | The same structured idea as CSV, inside a spreadsheet file with a real header row | Automatic for a recognized bank's layout - same principle as CSV, just a different container |
| A rendered, print-oriented document - visually laid out for a human eye, not built for machines to parse | Needs a bank-specific parser that reads the actual layout of that bank's statement, since PDF has no built-in structure | |
| OFX / QFX, CAMT.053, QIF | Standardized banking-data formats, purpose-built for import into financial software | Automatic for every bank that offers them, with no bank-specific work needed at all |
Why PDF is the odd one out
A CSV file is data first and readable-by-a-person second. A PDF statement is the opposite: it's built to look right when printed or viewed, with dates, amounts, and descriptions positioned wherever the bank's own template happens to put them - sometimes lined up in neat columns, sometimes wrapped across several lines, sometimes with running balances and page totals mixed in among the real transactions.
That's exactly why PDF statements need a bank-specific parser rather than a generic one: reading a PDF statement means understanding the specific visual layout that particular bank uses, down to which lines are transactions and which are headers, footers, or the closing balance. See which formats Home Budget Analytics recognizes automatically - PDF is supported for several banks by name, precisely because each one's layout has been read and mapped by hand.
If your bank isn't recognized automatically yet
If your bank's CSV or TXT export doesn't match a known layout, that's not a dead end - it's a one-time setup step. You point out which column is the date, which is the amount, and which is the description, and the app remembers that mapping for every future statement from that same bank. It only needs to be done once, and then that bank behaves exactly like an automatically-recognized one.
If you're not sure which format to export from your bank's website or app, CSV is usually the safest first choice - it's the most common export option and, once mapped, the most reliable to import going forward.
See what your bank exports
Check the full list of automatically recognized formats and banks, or start a free trial and find out in under a minute.
Check supported formats