ERPNext Accounting in South Africa

A chart of accounts that serves SARS and the annual financial statements

South African companies need a ledger that feeds two quite different outputs: the periodic VAT return and the annual financial statements your accountant prepares, often under IFRS for SMEs or full IFRS. Income tax computations then start from those statements. A chart copied from an old Pastel setup usually serves the first output and makes the second harder.

In ERPNext I keep the account tree lean and push analysis into structure:

• Accounts grouped the way your accountant presents the statements, so the trial balance maps without a long mapping workbook.
• Cost centers for branches or divisions, and accounting dimensions for contracts, projects or product lines, rather than dozens of near-identical expense accounts.
• Separate accounts for items your tax practitioner usually adjusts, such as entertainment or certain fines, so they are visible at year end.
• Fixed assets in the asset module, with depreciation schedules agreed with your accountant and kept apart from any tax allowance calculation they perform.

VAT itself runs through tax templates: standard-rated and zero-rated sales, exempt supplies, imports, and purchases on which your practitioner says input VAT cannot be deducted. Customer and supplier VAT numbers sit on the master records. Each template is checked with your practitioner before go-live. The global module view is on ERPNext Accounting.

Bank statements, debit orders and EFT payment runs

Bank reconciliation in ERPNext works from imported statement lines, which the finance team pairs with payments and journals. South African banks each provide statement exports in their own layouts, so I collect samples from every bank account you hold and build an import template for each one. Recurring items such as debit orders, bank charges and card settlements get matching rules, which leaves the finance team handling exceptions rather than every line.

Paying suppliers is where control matters most. ERPNext can prepare payment entries and group them for approval, but producing a file in the exact layout your bank's business platform accepts is usually a custom report or app. I design the run as follows:

• A clerk prepares the proposal from due invoices.
• A second person reviews and approves it inside ERPNext.
• The export file is generated, uploaded and released on the bank platform by authorized signatories.
• Payment entries post once the bank confirms.

Fraud through changed supplier bank details is a risk every finance team should design for. Any change to a supplier's bank account should require verification through a known contact and a second approver, with the change logged. ERPNext's version history records who changed what; I add the workflow around it. Related controls are on finance automation.

Rand books, foreign currency and companies across the border

Exporters, importers and groups with neighboring subsidiaries all need more than a single-currency ledger. ERPNext keeps each company's books in its own currency, while customers, suppliers and bank accounts can be held in dollars, euros or pounds. Invoices record the exchange rate used, and a period-end revaluation adjusts open foreign balances to the closing rate, posting unrealized gains and losses separately from realized ones.

Points I settle with your accountant:

• Which rate source is used for transactions and for revaluation.
• How forward exchange contracts are recorded, since ERPNext has no dedicated treasury module and your accountant may prefer journals.
• Whether customs and freight on imports are capitalized into stock through landed cost vouchers.

A group with entities in Namibia, Botswana or other neighboring countries can run each as a separate company on the same ERPNext site, sharing items and suppliers where useful. Each company carries its own tax templates, and the local rules in each country need their own answer from a local accountant. Intercompany sales are handled through internal customers and suppliers, so both sides post and can be tied out monthly. Consolidation for statutory purposes usually stays with your accountant. For patterns, see multi-company ERP and multi-currency ERP.

Closing the month when the power is off

Load-shedding and unplanned outages change how a finance team should think about its accounting system. Whether ERPNext runs on Frappe Cloud, with a hosting provider or on a server in your building, the questions for the close are the same: can the people who post the month-end journals reach the system, and if something fails halfway, can you prove the books are intact?

I write a close routine that answers those questions in advance:

• Access. Which finance staff have laptops on battery and mobile data as a fallback, and whether a cloud-hosted site is reachable from home when the office is dark.
• Self-hosted servers. If ERPNext runs on-premise, the server, network switch and router need backup power long enough for an orderly shutdown, and someone must own that check.
• Backups and restore. Automated backups held off-site, plus a restore of a closed month into a test site so you know the backup is usable.
• Period locking. Accounting periods closed and a frozen-entries date set once the accountant signs off, so late postings cannot slip in after an interruption.
• Scheduled reports. Aged debtors, creditors and cash reports emailed automatically, so management still has figures during a long outage.

The ERPNext South Africa page discusses the wider hosting decision.

Leaving Sage or Pastel, licensing and who maintains the code

Most of the effort in moving from Sage or Pastel is in balances, not configuration. Each open debtor and creditor invoice comes across as its own opening document so the age analysis survives, bring in bank balances reconciled to statements, and agree the cutover date with your accountant so the last VAT period is filed from one system only. Historical detail usually stays in the old package as a read-only archive.

Because the ERPNext code is open source, nobody charges a seat fee. You still pay for hosting, implementation and support, and you choose who provides them: Frappe Cloud, a local implementation firm, a foreign one or a developer on your payroll. Whichever you pick, put these in writing:

• Custom reports and bank file formats live in a separate app under version control.
• Upgrades are tested on a staging copy against your VAT and bank reports before production changes.
• One named party owns each custom app.

SARS has signaled interest in electronic invoicing and digital reporting. ERPNext's API makes a future connection possible, but confirm with Frappe or your implementer what exists for your version, and with your practitioner what applies. I am independent of all providers. Platform comparisons for this market are covered under ERP consulting for South Africa, and the country hub explains how engagements run. The engagement runs in English and is delivered remotely.