Import a statement from any bank, by mapping its CSV columns
If your bank isn't one of the handful Home Budget Analytics recognizes automatically, you can still import its statement: export a CSV file from your bank, tell the app once which column is the date, which is the amount, and which is the description, and every future upload from that same bank is recognized automatically from then on.
Why this exists
There are thousands of banks in the world and no two export a CSV file in quite the same layout - different column orders, different date formats, some banks split spending and income into separate debit/credit columns, others use a single signed amount column. Building a dedicated parser for every bank on earth isn't realistic, so instead of guessing, Home Budget Analytics asks you once: which column is which.
This isn't a workaround or a lesser path - it's a first-class part of the app, and once a bank's layout is mapped, it behaves exactly like an automatically-recognized bank for every statement you upload after that.
How the column mapping works
When you upload a CSV or TXT file that doesn't match a known bank's layout, a mapping screen opens automatically, showing your file's actual column headers and a preview of the first few rows.
-
1
Upload your statement
Export a transaction history as CSV from your bank's website or app, and upload it on the Upload Statement page. If Home Budget Analytics doesn't already recognize the layout, the mapping screen opens right away - no extra step to find it.
-
2
Point out the date column
Pick which column holds the transaction date, and its format if it isn't obvious (day/month/year, month/day/year, and a few others are supported) - or leave it on Auto and let the app work it out from a sample of your actual rows.
-
3
Point out the description column
Pick the column with the merchant name or transaction description - this is what automatic categorization reads to sort each transaction later. A second description column can be added too, for banks that split this across two fields.
-
4
Point out the amount
Most banks use a single signed amount column (negative for spending, positive for income) - pick it, and flip the sign if your bank does it the other way around. Some banks split this into separate debit and credit columns instead; the mapping screen has a toggle for that, so you pick both columns rather than one.
-
5
Set the currency
If every transaction in the file is in one currency, just type the currency code once (like EUR or USD). If the file itself has a currency column (common on multi-currency cards), point at that column instead.
-
6
Save the mapping and import
Give the mapping a name and save it - this is the part that makes every future upload from this bank automatic. From here on, uploading a new statement from the same bank is picked up without going through this screen again.
If the mapping still feels wrong
Not every bank's export is straightforward, and it's fine not to get it right on the first try - go back and adjust any of the fields above and re-import. If a file genuinely doesn't fit the mapping tool at all (a strange multi-row header, merged cells, that kind of thing), there's a "can't figure this one out" option right on the mapping screen that sends the bank's name and country to support - a native parser can be added for that layout without you having to do any of this by hand.