How it works: drop a CSV, MT940, OFX, or PDF statement. CSV expects headers on row 1. PDFs are parsed by AI (Ollama by default, switchable to Claude at /Admin/AISettings) — adjust mapping if needed in Step 2 (CSV only), preview in Step 3, Commit in Step 4. Amounts can be a single signed column OR separate Debit + Credit. Common date formats recognised (DD/MM/YYYY, YYYY-MM-DD, etc.).
📥
Drop a CSV / MT940 / OFX / PDF file here, or click to choose
CSV (headers on row 1) · SWIFT MT940 (.sta, .mt940, .txt) · Quicken OFX 1.x / 2.x (.ofx, .qfx) · PDF (selectable-text bank statements, parsed by AI)
AI is reading the PDF…Ollama on local hardware can take 1-3 min per page. Flip to Claude at /Admin/AISettings for ~10s per statement.
2 · Column Mapping —
e.g. "Transaction Date" / "Value Date"
Free-text narration / particulars
Cheque no · UTR · Ref no. (used as DocumentNo if present)
Either map this OR the Debit+Credit pair below — not both.
Money OUT of account → stored as negative
Money IN to account → stored as positive
Bank semantics: a debit on your account statement is money leaving (we store it as -amount).
A credit is money arriving (+amount).
This matches BC's BankLedgerEntry.Amount convention.
Mapping ready when Date + (Amount OR Debit/Credit) are set