Bank statements into ERPNext, the South African way

A South African franchise retailerIn production

OFX bank statement import for ERPNext, tested against real exports from five South African banks.

The challenge

ERPNext has no OFX import, and each South African bank's OFX export has its own quirks, so reconciliation meant reworking CSV files by hand.

What we built

  • Imports both OFX formats in use (1.0.x SGML and 2.0 XML)
  • A preview fills in the bank account, bank and statement period from the file
  • Creates ERPNext Bank Transactions and skips anything already imported, so re-uploading a file is safe
  • Records the closing balance and works out the opening balance
  • Fixes for each bank's quirks: account-number formats, character sets, date precision
  • Hands straight over to ERPNext's own Bank Reconciliation Tool

How it works

Upload the file from Bank Statement Import. The app normalises it, shows a preview, then writes standard Bank Transactions per company and account. Matching against payments and invoices happens in ERPNext's built-in reconciliation tool, so nothing about the normal workflow changes.

  1. Bank OFX file
  2. OFX Import
  3. Bank Transactions
  4. Bank Reconciliation

By the numbers

  • Tested with real exports from Nedbank, FNB, Standard Bank, Investec and ABSA
  • Three of the four big SA banks export the older SGML format, which is supported

Request a licence for Bank statements into ERPNext, the South African way

Have a system that doesn't quite fit?

Tell us what you need it to do. We'll scope it with you.

Start a project