How to export transactions from your bank as CSV
By Andrii Furmanets, founder of FolioFlux. Questions: hello@folioflux.com.
Banks put the download in different places, so this guide does not name menus. Look for “export”, “download” or “statements” on the account’s transaction list, and choose CSV when you are offered a format.
What to download
- One file per account. Do not merge accounts into one file.
- A full month: first day to last day.
- Settled transactions. Leave pending ones for next time if the bank lets you choose.
- Keep the original file unchanged. Opening and re-saving it in a spreadsheet can change dates and drop leading zeros.
Columns you can expect
| Column | What varies between banks |
|---|---|
| Date | Day-first or month-first; sometimes a time; sometimes two dates |
| Description | Merchant text, often with a reference or a card number fragment |
| Amount | One signed column, or separate debit and credit columns |
| Balance | A running balance on some exports, none on others |
| Currency | Present when the account can hold more than one |
Quirks to check
- Encoding: accented or Cyrillic text that looks scrambled means the file is not UTF-8.
- Separators: semicolons and comma decimals are common in European exports.
- Extra lines: account details above the header, or a totals line at the end.
- Card exports that write charges as positive numbers.
Formats FolioFlux is tested with
FolioFlux is tested with sample exports from: monobank (English, and the Ukrainian card statement in Windows-1251), Chase checking, Chase card, Bank of America, Wells Fargo, Capital One, American Express, Citi, Revolut, Wise, N26, Mercury, Brex, ING (Germany), Sparkasse, mBank, Monzo, Barclays, QuickBooks “Transaction List by Date”, Excel “Unicode Text” (.txt), Excel CSV with a sep= line and page-break headers. The samples are synthetic. If your export looks different, you can correct the column mapping in the preview.
You can sign up at folioflux.com/sign-up
Not financial, tax or legal advice.