Bank Statement Import

ERPNext's built-in CSV / Excel / camt.053 import for Bank Transactions. When you don't have a live bank feed (GoCardless, Plaid), or when you need to backfill historical transactions, this is the fallback.

When to use it

• Backfilling history — your first GoCardless sync pulls 90 days max; older transactions need a CSV / camt.053 from the bank.
• Banks outside coverage — Mollie / GoCardless / Plaid don't cover every bank globally. CSV import is the universal fallback.
• One-off corrections — re-importing a corrected statement after a bank error.

Where it lives

Search Bank Statement Import in the awesomebar → New.

1. Bank Account — pick the ERPNext Bank Account to import into.
2. Import File — upload the bank's export. Supported formats: CSV, Excel, MT940 (text), camt.053 (XML).
3. Map columns — ERPNext shows the file's columns; map them to Bank Transaction fields (date, debit, credit, description, reference number). Save the mapping as a template if you'll re-use it.
4. Start Import — runs in the background. Watch the progress in the form.

Tips

• Use the bank's camt.053 export when available. It's an ISO 20022 XML standard with consistent field names. Less mapping fiddliness than CSV.
• Save column mappings. Most banks emit the same column order every month. A saved template means one click per import.
• Deduplicates by reference number. Re-importing the same statement won't create duplicate Bank Transactions, provided the bank's reference numbers are stable.

Prilk support

Built into ERPNext, supported as part of standard ERPNext upkeep. For the upstream documentation see the ERPNext Bank Statement Import docs.