You do not have to rename your bank’s columns. The importer lets you map any
column to the right field, and auto-detects the common ones. This page tells
you what each field expects.
Required fields
A CSV must provide:- A Date column, and
- Either an Amount column, or an Inflow and Outflow pair.
Fields you can map
| Field | Required | Notes |
|---|---|---|
| Date | Yes | One date per transaction. |
| Amount | One of Amount or Inflow/Outflow | Single signed column. Negative is spending. |
| Inflow (credit) | — | Money in. Use with Outflow when your bank splits the two. |
| Outflow (debit) | — | Money out. |
| Payee / Description | No | Merchant or description. |
| Memo / Notes | No | Extra text. |
| Category | No | A category name if your file has one. |
| Reference ID | No | A bank-supplied unique ID; improves duplicate matching. |
| Skip | — | Mark columns you do not want imported. |
Date formats
Leave the date format on Auto-detect unless the sample looks wrong. The supported explicit formats are:MM/DD/YYYYDD/MM/YYYYYYYY-MM-DDM/D/YYM/D/YYYYDD-MM-YYYY
03/04/2026), pick the exact format so
day and month are not swapped.
Amounts
- A single Amount column should be negative for spending and positive for money in.
- If your bank reports spending as positive numbers, tick Invert amounts to flip every sign.
- If you map Inflow only, every row imports positive. Outflow only, every row imports negative.
- Currency symbols and thousands separators (like
$1,250.00) are handled.
Duplicate matching
A Reference ID column, where your bank provides one, gives the most reliable duplicate detection — exact ID matches are caught precisely. Without it, Budget Bandit falls back to matching on date, amount, and payee within a few days. See duplicate handling in Import a CSV.A minimal example
Date to Date, Description to Payee /
Description, and Amount to Amount.
Related
Import a CSV
The full import flow.
Why rows did not import
Diagnose skipped or dropped rows.