Every return a South African business files — VAT201, EMP201, provisional tax, the CIPC annual return — is a number that has to reconcile back to the ledger it came from. This leaf is about assembling those figures from ERP data so they tie out, with the agent doing the reconciliation and a human submitting via SARS eFiling. The submit button stays human.
Tax and statutory compliance is the set of returns a business is legally required to file — to SARS for tax, to CIPC for company records. Each one is, at heart, a specific cut of the same ledger the financial statements come from: VAT owed, PAYE deducted, profit taxed. The work is assembling the right figures, on the right form, by the right date, and being able to prove each number ties back to the books.
That tie-back is the whole game. A VAT return that doesn't reconcile to the VAT control account in the GL is a query waiting to happen. The reporting and warehouse layers that produce management accounts are the same machinery that makes a return defensible — which is why compliance belongs in the finance domain, not bolted on beside it.
This is the hardest guardrail in the finance domain. The tooling and the agent prepare the figures and reconcile them to the ledger. A human reviews and submits through SARS eFiling. An AI does not file a return, sign a declaration, or transact with the revenue authority — the legal liability sits with a person, and the workflow must too.
A working South African business runs a rhythm of recurring filings. Every one pulls from a part of the ledger the ERP already holds.
| Return | What it is | Source in the ledger |
|---|---|---|
| VAT201 | VAT return (usually bi-monthly) | Output vs input VAT control accounts |
| EMP201 | Monthly PAYE, UIF, SDL | Payroll journals |
| EMP501 | Bi-annual employer reconciliation | Payroll, tied to EMP201s filed |
| IRP6 | Provisional tax (twice yearly) | Estimated taxable profit from the P&L |
| ITR14 | Annual company income tax return | Audited annual financial statements |
| CIPC annual return | Company-status filing | Turnover + company particulars |
The pattern repeats: each return is a query against the ledger, formatted to a SARS or CIPC schema, filed on a deadline. The value of getting the data layer right is that the figures assemble themselves and reconcile automatically — instead of a scramble through exports every two months.
The single most important control in compliance is reconciliation: the VAT on the VAT201 must equal the movement on the VAT control account; the PAYE on the EMP201s must sum to the EMP501; the profit on the IRP6 must reconcile to the management accounts. When SARS asks — and on VAT, they do — you have to show the working.
This is where ERP data plus a warehouse pays for itself. The control-account reconciliation becomes a saved query, not a quarterly archaeology project. Every filed figure has a derivation a human and an auditor can re-run. ERPNext's open data makes this cheap: the VAT and payroll figures come straight out over REST, no per-seat reporting licence between you and your own tax numbers.
Compliance is repetitive, deadline-driven and high-stakes — strong for assistance, off-limits for autonomy at the point of submission.
Pull the period's figures into the VAT201 / EMP201 shape, ready for a human to review on eFiling. No more re-keying from a spreadsheet export.
Confirm the return ties to the GL control account and flag any difference with its likely cause before anything is submitted.
Surface what's due when, and whether the data for it is ready. A missed VAT deadline is a penalty; a tireless calendar is genuine value.
The agent does not log into eFiling, submit a return, or sign a declaration. It hands a reconciled, review-ready pack to a person who does. Liability stays human, by design.
| Build the reconciled pipeline when | ERP reports + an accountant suffice when |
|---|---|
| VAT volume makes manual reconciliation painful | Low volume, an accountant handles it in an afternoon |
| You file across multiple entities | One company, simple returns |
| You want every figure auditable on demand | The ERP's own tax reports already reconcile cleanly |
| You already run the reporting warehouse | No warehouse, and the volume doesn't justify one |
The honest line: most small companies are well served by their ERP's tax reports plus a good accountant, and shouldn't build anything. The pipeline earns its place when volume, multiple entities, or audit scrutiny make manual reconciliation the thing that breaks at month-end.
Tax compliance is the most jurisdiction-specific work in finance, and this leaf is built around the SA reality: SARS as the revenue authority, eFiling as the submission channel, and CIPC for company filings. The returns named above — VAT201, EMP201, EMP501, IRP6, ITR14 — are the actual forms, on the actual cadence, that a local business runs.
Two further notes. POPIA applies: taxpayer and payroll data is personal information, so the warehouse and any agent touching it inherit the same residency and minimisation obligations the rest of the stack carries. And the line is absolute — assembling a return is assistance; submitting it and signing the declaration is a human, registered act.
It sits at the end of the chain — every return reconciles to the same books reporting and consolidation work on.
The authorities and channels the returns are filed to.