Importing transactions
Prepare your file
Export your transaction history
In your bank or budgeting app, look for an export or download option and choose CSV. Keep the original file as a backup. An Excel workbook must be saved as CSV or tab-separated text first; renaming the extension is not enough.
Keep the original columns
Keep the header row, transaction dates, descriptions and amounts. Do not replace transaction amounts with account balances. If text looks garbled, open the file using its original encoding and save a UTF-8 copy.
Check dates and currency
Confirm whether dates use day/month/year or month/day/year. Check the currency and select the destination account. Preview every transaction before saving. Imports add history without changing current balances; transfers, balance adjustments, future dates, unreadable rows and matching prior imports are skipped. No currency conversion is performed.
Supported file layouts
These are recognized CSV layouts, not live bank connections. Compatibility depends on the actual columns in your file. Use UTF-8 or UTF-16 text, up to 2 MB and 5,000 rows. Tests use fictional transactions; they do not certify every export version from each provider.
| Source | Recognized layout and limits |
|---|---|
| Mint (Intuit) | Legacy Mint transaction CSV. US month-first dates; debit and credit identify money out and in. |
| QuickBooks (Intuit) | Intuit’s three- or four-column bank-upload template only. Requires explicit format selection: accounting Credit means money out and Debit means money in. Arbitrary QuickBooks reports are not covered. |
| Westpac | Corporate Online previous-day CSV only, with YYYYMMDD dates and a currency column. Other Westpac retail and card exports are not covered. |
| Money Forward ME | ME transaction CSV, JPY only. Preserves transfers and skips excluded non-transfer entries. |
| PayPay | Consumer transaction-history CSV, JPY only. Reads domestic yen amounts; refunds and transfers are distinguished from spending. |
| Realbyte · 편한가계부 | Korean 편한가계부 template saved as CSV or tab-separated text, KRW only. Supports income, spending and outgoing transfers. Excel workbooks cannot be read directly. |
| Money Lover | CSV layout with date, amount, note and wallet columns. Keep the wallet column so the format can be identified. |
| Bluecoins | CSV layout with date, type, item or title, and amount columns. |
| Mobills | CSV layout with Portuguese or Spanish date and amount headers, plus a description column. |
| Spendee | CSV layout with date, category name, wallet and amount columns. |
| Wallet (BudgetBakers) | CSV layout with date, account, category, amount and type columns. |
| GCash | Statement-shaped CSV with date, reference number and amount columns. This does not mean GCash offers a native CSV download; PDF statements are not supported. |
| Nubank | Card invoice CSV or NuConta statement CSV. Card refunds retain their positive effect; account statements require the transaction identifier column. |
| Other bank CSV files | Headered CSV with dates, descriptions and signed amounts, or separate debit/credit columns. Includes common Korean and Japanese headers. US month-first dates need an explicit date setting; arbitrary bank or wallet layouts are not guaranteed. |
Not supported yet
PDFs, screenshots, XLS/XLSX workbooks, headerless files, OFX/QFX/QBO and IIF are not supported. There are no dedicated KakaoPay, Toss, Naver Pay or Zaim formats. Japanese era dates are not inferred; use Gregorian dates. JPY and KRW amounts must be whole units.
Need help with a format?
Send the provider name and column headings only. Do not email statements, account numbers or transaction history.
Email: hello [at] zalt.fyi