South African VAT is, on paper, one of the simpler regimes to configure: a single standard rate (15%), a set of zero-rated and exempt supplies, and a periodic return — the VAT201 — filed to SARS through eFiling. The work in Acumatica is not exotic device integration; it is getting the tax zones, tax categories, and tax IDs set up so that every transaction lands in the right box of the VAT201, and so that the VAT report reconciles to the general ledger at the end of the period.
The shape of South African VAT
Three treatments cover almost everything. Standard-rated supplies carry 15% output VAT on sales and allow input VAT deduction on purchases. Zero-rated supplies (exports, certain basic foodstuffs, fuel) are taxable at 0% — they still appear on the return, and the vendor can claim input VAT. Exempt supplies (financial services, residential rent) carry no VAT and do not allow input deduction. The distinction between zero-rated and exempt is the one people get wrong, and it changes what you can claim, so model them as separate tax categories rather than lumping both under "no VAT".
Configuring taxes in Acumatica
Acumatica's tax model has three layers that combine to produce the rate on a document: the Tax (the rate and its GL accounts), the Tax Category (attached to items and accounts, saying "this thing is standard-rated"), and the Tax Zone (attached to customers and vendors, saying "this party is in South Africa"). A line picks up tax when its category and the party's zone intersect. Set up one tax each for the output and input side at 15%, plus zero-rated and exempt taxes, and wire each to the correct VAT control accounts.
Tax ZA-VAT15-OUT 15% Output VAT (sales) -> VAT payable (liability)
Tax ZA-VAT15-IN 15% Input VAT (purchases) -> VAT receivable (asset)
Tax ZA-ZERO 0% Zero-rated supplies -> reported, no VAT
Tax ZA-EXEMPT n/a Exempt supplies -> no VAT, no input claim
Tax Category STD -> ZA-VAT15-OUT / ZA-VAT15-IN
Tax Category ZERO -> ZA-ZERO
Tax Category EXMPT -> ZA-EXEMPT
Tax Zone ZA -> customers & vendors registered for SA VATKeep VAT payable (output) and VAT receivable (input) in distinct GL accounts. The VAT201 nets them, but during a period you want to see each side independently — it makes the return reconcile cleanly and makes an over- or under-claim obvious before you file, not after SARS queries it.
Tax invoice requirements
SARS has specific requirements for a valid tax invoice: the words "Tax Invoice", the supplier's and (above a threshold) the recipient's VAT registration number, a serial number, the date, and the VAT shown separately or the statement that the price includes VAT. Acumatica handles most of this through the invoice form, but the VAT registration numbers and the "Tax Invoice" wording usually need to be added to the printed form template. Get this right early — an invoice that is not a valid tax invoice cannot be used by your customer to claim input VAT, and that generates support calls fast.
For invoices above the SARS full-tax-invoice threshold, the recipient's VAT number is a legal requirement. If your customer master doesn't capture it, the printed invoice is defective. Add VAT registration as a required field on the customer for the ZA tax zone rather than trusting people to fill it in per invoice.
Mapping to the VAT201
The VAT201 return has numbered fields: output tax on standard-rated supplies, zero-rated supplies, input tax, capital-goods input, and so on. The practical goal of your setup is that Acumatica's VAT report (or a tax report configured to the VAT201 boxes) can be produced by reading the tax control accounts and the tax detail. Configure the tax report codes so each tax maps to its VAT201 field; then filing is a matter of transcribing report totals into eFiling, and the numbers already tie back to the ledger.
| VAT201 area | Source in Acumatica |
|---|---|
| Standard-rated output (Block 1) | Sales tagged STD category, output tax total |
| Zero-rated supplies | Sales tagged ZERO category |
| Input tax (Block 14/15) | Purchases with input VAT, capital vs other |
| Net VAT payable/refundable | Output control less input control |
Periods and reconciliation
Most vendors file the VAT201 every two months on a category cycle SARS assigns; larger turnovers file monthly. Align your tax period configuration to that cycle so a period's report is exactly one return. At close, reconcile the VAT report to the control-account balances: if the report says you owe an amount and the GL control accounts say something else, you have a transaction with the wrong tax category or a manual journal that bypassed the tax logic. Find it before filing — SARS reconciles the same numbers.
Common mistakes
The recurring ones: treating exempt supplies as zero-rated (and wrongly claiming input VAT), posting manual GL journals straight to the VAT control account so they never appear on the tax report, and forgetting that imports carry VAT at customs that must be claimed as input tax on a different document trail. Each shows up as a mismatch between the tax report and the ledger — which is exactly why the period-end reconciliation is non-negotiable.
Wrapping up
SARS VAT in Acumatica is a configuration exercise, not an integration one: define the standard, zero-rated, and exempt taxes with clean control accounts, attach categories and zones so transactions self-classify, make the printed invoice a valid tax invoice, and map the taxes to the VAT201 boxes. Do that and each period's return falls out of a report that already agrees with the general ledger. If you are setting this up for a specific entity, reach out or keep reading through the rest of the Acumatica blog.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.