Importing transactions from CSV

If your bank cannot connect through Mercury or Plaid, import its CSV statement instead. Everything downstream works the same: the transaction list, category breakdowns, and the cash, spend basis, and runway metrics.

Import a statement. On the Finance page, choose Import CSV, then upload the file or paste rows from a spreadsheet. The import agent reads your columns and proposes a mapping. You can adjust any column before importing, and a preview shows how the first rows will land.

What the file needs. A header row, a date column, and amounts in one of two shapes. Either a single signed amount column where negative numbers are money out, or a debit and credit pair where each column holds positive numbers. Merchant, description, running balance, and a bank category column are optional but improve the result.

Your cash figure. Enter your current account balance in the import dialog to set the Cash metric. If you skip it, the import uses the latest value from a mapped balance column, or keeps the existing figure.

Re-imports are safe. Importing the same file again updates the same rows instead of duplicating them, so overlapping monthly exports are fine.

Categories carry over. New transactions from merchants you have categorized before inherit that category automatically, the same as bank sync.

Limits. Imports are capped at 2000 rows per file. Split a larger export into smaller files and import them one after another.