Contents
South African businesses have until 16 October 2026 to comment on a document that will decide what their accounting software has to be able to do. On 17 August 2026 SARS published its Consultation Paper on VAT Modernisation, setting out what it calls the Digital VAT Model: structured electronic invoices, exchanged through a network of accredited service providers and reported as transactions happen. The end state, in SARS’s words, is VAT compliance that “becomes part of the systems businesses already use every day”: pre-filled returns and, over time, auto-assessment.
Nothing in it is mandatory before 2030. That is why it is worth reading now: the accounting and ERP contracts signed between now and then will decide what the transition costs, and the standard those systems must meet has not yet been chosen.
What is happening?
SARS has moved from a discussion paper to a consultation paper: the 2023 paper tested the idea, the 2026 one proposes an architecture and a roadmap. SARS published accompanying FAQs on 8 September 2026 and the paper in all eleven official languages on 15 September 2026, according to its VAT Modernisation page.
Today VAT is self-assessed and checked afterwards. SARS, the paper says, “uses the post-audit model to verify the VAT submissions with limited visibility of transactional activity only after returns have been submitted.”
The proposal replaces that with three connected components — e-invoicing, an Interoperability Framework and e-reporting — forming what the paper calls a Decentralised Continuous Transaction Control and Exchange model. An e-invoice here is a structured, machine-readable tax invoice following a prescribed data model, drawn from a standard such as EN 16931 CIUS or Peppol PINT BIS. The paper is explicit that it “is not merely a PDF, scanned image or emailed document.”
The exchange runs across five roles. The supplier issues the invoice from its accounting software to an accredited access point, which validates and clears it or rejects it for correction. The buyer’s own access point validates it again, and the buyer must then process it and respond with its VAT treatment — fully, partly or not claimed. A fifth access point, appointed for SARS, receives the cleared data from both sides and uses it to pre-fill returns. A Network Authority would accredit the providers and publish the approved list; buyers and suppliers each choose their own.
The roadmap runs from preparation and draft regulations in 2026/2027 through development, testing and a voluntary pilot, to phased implementation commencing in the 2030 calendar year over roughly 36 months. Large businesses go first, then government as a recipient, then smaller enterprises, then business-to-consumer.
What remains uncertain matters as much as what is proposed. The e-invoice standard has not been selected. The Network Authority has not been appointed — the paper says that selection and procurement is “currently being finalised”. The regulations do not exist and penalties are not specified. TechCentral, reporting on 17 August 2026, noted that SARS has defined neither what “near real-time” means nor how costs will be shared. The implementation order may change too.
Why it matters economically
Three costs move, and they do not move together.
The first is the compliance cost of VAT itself, which should fall. An invoice validated at issue cannot be rejected later for a formal defect, which shortens the argument about input-tax deductions and, SARS argues, speeds up refunds — a working-capital event for many businesses.
The second is the cost of getting there: SARS acknowledges investment in technology, systems integration, process change and organisational readiness, varying by size and digital maturity, and expects legacy and new systems to run in parallel during the transition — which means paying for both.
The third is less visible and, in our view, the most consequential. SARS would receive cleared data from both sides of every invoice, and the paper is candid that it will apply AI and analytics to build a whole-of-value-chain picture. A business that cannot see its own transaction data as clearly as the revenue authority can is weaker in every verification and dispute. That asymmetry is the economic story, and it can be closed on a business’s own terms before 2030. For scale, SARS and the National Treasury reported on 5 December 2025 that 496,858 of South Africa’s 900,285 registered VAT vendors were active in 2024/25, accounting for 93.8% of domestic VAT payments.
What it means for African businesses
This proposal applies only to South African VAT, but South Africa is joining a pattern visible in other African markets, and businesses trading across them should pay closest attention.
Kenya is furthest along, and shows where these regimes lead. KPMG’s Kenya tax alert of January 2026 records that the Finance Act 2023 disallowed expense deductions unsupported by TIMS or eTIMS invoices; that the Electronic Tax Invoice Regulations 2024 extended electronic invoicing to everyone carrying on business, VAT-registered or not; and that from 1 January 2026 iTax validates income tax returns against KRA’s datasets at submission, potentially preventing filing where the numbers do not tie. An invoicing rule became a deduction rule, then a filing gate, inside three years — the direction we described in Kenya’s payment law is being rewritten.
Nigeria took a different architectural route. EY reported on 20 May 2025 that the Merchant Buyer Solution pre-clears business and government invoices through the revenue service’s own central platform, returning a unique invoice reference number and a cryptographic stamp.
For a group trading in several of these markets there is no single continental standard, and will not be one soon: South Africa’s decentralised network, Nigeria’s central clearance and Kenya’s software-based fiscalisation are three technical shapes for one policy idea. Hold one canonical record of every sale in your own systems, and treat each market’s format as an output mapping from it. A market-specific compliance tool should never become your system of record.
Technology and AI implications
Start with where technology does not help. Nothing can be built against a standard that has not been chosen: until SARS publishes the prescribed data model and appoints the Network Authority, a product sold as “SARS e-invoicing ready” is selling a guess.
AI does not fix bad master data, and under continuous transaction controls that matters more than it does today. If a customer’s VAT number, a product’s tax treatment or a line-item description is wrong in your records, an invoice built from it is rejected at source or creates an exposure. The control has to be deterministic — validation rules applied before issue — not a model’s best guess at a tax code. KPMG’s Kenya alert lists this failure mode precisely: missing buyer PINs, wrong HS codes and inaccurate descriptions invalidating otherwise genuine invoices.
Where technology earns its place, in our assessment, is in three narrower jobs: reconciling your own records to find where sales, invoices and payments already disagree, before a regulator finds it for you; routing rejected invoices to a person once validation is continuous; and extracting structure from the PDFs small suppliers will keep sending through the years of parallel running. The last is genuine AI work, useful now, independently of SARS.
The heavier rebuild is on the buying side, and it is under-discussed. The recipient must receive a structured invoice, process it automatically and respond with its VAT treatment. That moves the input-VAT decision from a month-end schedule to a transaction-level event — a change to how accounts payable works, not a software purchase. It also arrives earlier than your own mandate suggests, since government entities are to be mandated to accept e-invoices and voluntary early adopters will push structured invoices at their customers.
Practical business implications
Four questions worth answering this quarter, none of which depend on SARS deciding anything:
- Can your accounting or ERP system emit a structured invoice — not a PDF — and can it receive one and respond?
- Are counterparty identifiers, product tax treatments and line-item descriptions correct at the moment of issue, or repaired at month-end?
- Is there one record of a sale, or several? If the honest answer involves spreadsheets, that is a present-day problem before it is a 2030 one — see why growing businesses outgrow spreadsheets.
- When does your software contract end, and will the vendor commit in writing to supporting a prescribed South African e-invoice standard once published, at no higher licence tier?
One thing has a date on it: respond to the consultation by 16 October 2026, through the survey link in the paper. The questions worth answering are cost-sharing, the buyer-side response obligation, and onboarding for smaller businesses. One thing not to do: buy an e-invoicing compliance product now.
RevenueStack perspective
Our reading is that the compliance deadline is 2030 but the commercial deadline is your next software decision. Systems bought in 2027 will still be running in 2030, and roadmaps of this length move. Plan for a capability, not a date. That points to a simple split: separate the work that pays for itself now, whatever SARS decides, from the work that only serves the mandate.
In the first pile — one clean record of a customer, a product and a sale; correct counterparty and tax data captured at the point of transaction rather than repaired later; invoices generated by a system rather than assembled by hand; automated matching of order to invoice to payment. Each cuts manual effort and error this year. It is the argument we made about mobile money reconciliation: the payment is the easy part, the record is the system.
In the second pile — access-point contracts, the prescribed syntax, network onboarding, certification. None of it can be specified yet. Defer it, and keep the option to do it cheaply later by insisting now on structured, exportable data and contracts you can exit.
Businesses that treat this as a 2029 IT project will buy compliance twice: once in panic, once properly. Businesses that treat it as a reason to fix their business systems and integrations get the operational return now and the compliance outcome as a by-product — and that route is open today, without knowing a single detail SARS has yet to publish.
Conclusion
SARS is proposing to move VAT compliance out of the return and into the invoice, with a network of accredited service providers between businesses and the revenue authority. The standard is undecided; nothing is compulsory before 2030. The useful response is neither to buy a compliance product nor to wait for certainty, but to make the invoice a reliable piece of structured data inside your own systems — work that cuts manual effort and reconciliation error now, and the one part of the transition that cannot be bought in a hurry later. The consultation closes on 16 October 2026, and businesses, not only their software vendors, should be in it.
Sources
- SARS Consultation Paper on VAT Modernisation: e-Invoicing, Interoperability Framework and e-Reporting — South African Revenue Service, 2026-08
- SARS invites public input on a new digital VAT model to modernise VAT administration — South African Revenue Service, 2026-08-17
- VAT Modernisation — South African Revenue Service, 2026-09
- Sars maps out the tech stack that will replace VAT returns — TechCentral, 2026-08-17
- Joint media statement National Treasury and the South African Revenue Service on the release of the 18th annual edition of Tax Statistics — National Treasury and SARS, 2025-12-05
- Tax Alert: eTIMS and the Shift to Data-Driven Income and Expense Validation — KPMG Advisory Services Limited (Kenya), 2026-01
- Nigeria's Federal Inland Revenue Service rolls out e-Invoicing platform — EY, 2025-05-20