If you've searched for "SARS eInvoicing" recently you'll have found a wall of urgency: mandates starting in 2026, invoices that won't be valid unless a SARS platform clears them first, deadlines you're apparently already behind on. Some of that is a reasonable reading of where things are heading. A lot of it is software vendors describing a system that hasn't been built yet as though it were already law.
So it's worth separating the two. There is now a real legal framework for eInvoicing in South Africa, and it did change in 2026. There is also, as things stand, nothing you are obliged to do about it.
The short version: eInvoicing in South Africa is still voluntary. The Tax Administration Laws Amendment Act, 2026 put the legal scaffolding in place on 1 April 2026, but the rules that would make anything compulsory are left to regulations that haven't been issued. No business has a confirmed eInvoicing deadline yet.
What actually became law in April 2026
The Tax Administration Laws Amendment Act, 2026 was published on 1 April 2026. What it does is narrower than the coverage suggests: it inserts definitions and an enabling framework, not obligations.
- It defines an electronic invoice — a tax invoice issued, transmitted and received in a structured electronic format that allows automatic processing.
- It defines electronic reporting — submitting tax data extracted from e-invoices, e-debit notes and e-credit notes to SARS.
- It provides for an interoperability framework: a network of service providers through which those documents are exchanged between supplier and recipient.
- It makes participation in the e-reporting system voluntary.
- It requires the buyer's consent before you send them an e-invoice, so you can't unilaterally switch a customer over.
Notice what's missing. There's no start date, no list of who's in scope, and no technical specification. Those are left to regulations the Minister still has to issue. Until they exist, the Act is a foundation waiting for a building — deliberately so, because SARS has said repeatedly that the detail depends on further consultation and on its own systems being ready.
A PDF emailed to a customer is not an eInvoice
This is the distinction that catches people out, and it's worth getting straight now because it survives every version of the eventual rules.
Emailing a PDF is electronic delivery of a paper-style document. A human opens it and types the numbers into something. An eInvoice in the regulatory sense is structured data — fields a system can read and post without anyone retyping them. The test in the Act is "automatic electronic processing", and a PDF fails it no matter how neat the PDF is.
That matters practically: if your invoicing currently ends with a PDF attachment, the eventual transition isn't a formatting change. It's a change in how the invoice is produced and transmitted.
What's already true today
Electronic invoicing isn't new in South Africa and you don't need permission to do it. Electronic tax invoices have been acceptable for years, provided the ordinary rules are met:
- The invoice carries all the particulars a valid tax invoice requires. Our guide to what makes a tax invoice valid walks through the full list.
- It's legible, and you can retrieve it and produce it if SARS asks.
- You keep the records for five years under the VAT Act — and seven under the Companies Act, which is the number that usually governs in practice.
- No electronic signature is required.
Historically, businesses exchanging invoices by EDI have needed prior authorisation for those arrangements. The new interoperability framework is intended to replace that kind of case-by-case approval with a standard network — which is the part of this reform most likely to make life easier rather than harder.
Who goes first, and roughly when
SARS has been consistent about the sequencing since its VAT Modernisation Discussion Paper, published on 8 September 2023. The plan starts at the top of the vendor base, not the bottom.
That paper proposed beginning with the segment of vendors contributing around eighty percent of total VAT revenue — roughly twenty percent of registered vendors, the medium-to-large end. Subsequent commentary points the same way: the largest VAT contributors first (Category C filers, who submit monthly), then major suppliers to government, then sectors SARS treats as higher risk. Medium-sized businesses come later, and small vendors later still.
On timing, the target most often cited is full operational capability by 2028, with pilots and voluntary onboarding through 2026 and phased onboarding of large vendors and priority sectors across roughly 2026 to 2029. Treat those as direction of travel rather than dates in a diary. SARS's own position is that exact implementation dates remain pending further consultation and capacity development, and nothing has been gazetted.
If you're a small or medium business filing VAT every two months, you are not in the first wave, and on the published sequencing you're some years from being in any wave. That's breathing room — not a reason to stop reading.
About the "Central Tax Hub" and Peppol claims
Here's where you should be careful, because it's the most repeated claim and the least supported.
A great deal of commentary states that South Africa is adopting a Peppol-based five-corner model built around a SARS "Central Tax Hub", and that every invoice will have to be routed through that hub for real-time clearance before it counts as a valid tax invoice for input VAT purposes. If true, that would be a significant operational change — it would mean you couldn't issue a valid invoice while SARS's platform was unavailable.
But that isn't what the published material says. SARS's own discussion paper describes transmitting VAT data through channels like a RESTful API, eFiling or e@syFile. Independent summaries of SARS's 2026 announcements describe secure batch channels and API options with daily transmission moving to shorter intervals, and specifically do not mention Peppol or a central clearance platform. The enacted framework describes a decentralised network of service providers exchanging documents between supplier and recipient — which is close to the opposite of mandatory central clearance.
It's entirely possible the architecture lands somewhere near what those commentators describe; a tax authority receiving structured data as a fifth party to the exchange is a common design internationally. The honest position today is that the exchange model is not settled in anything published, and you should not re-plan your finance systems around a specific architecture until the regulations name one.
What's worth doing now
Not much, and that's the point. The useful preparation is all stuff that pays for itself regardless of what the regulations eventually say.
- Make sure your invoices already carry every required particular, correctly, every time. Whatever the transmission mechanism turns out to be, it will validate the same fields SARS validates now — and structured data is far less forgiving of a missing VAT number than a human reviewer is.
- Get your customer and supplier master data clean. Registered names, VAT numbers, addresses. This is the single biggest source of pain in every country that has gone through this, because errors that a person would have quietly corrected become hard rejections.
- Stop treating the PDF as the invoice. If your invoices originate in a system that holds them as data, you already have the raw material. If they originate in a spreadsheet or a template, that's the thing to change.
- Keep your VAT records in a form you can actually query. Five years under the VAT Act, seven under the Companies Act.
- Watch for the regulations rather than the headlines. The commentary will keep churning; the moment that matters is when the Minister issues regulations naming scope, dates and format.
If you're on Bluubin, invoices are already structured records rather than documents, and the VAT treatment is calculated on each transaction as it's captured — which is the part that has to be right before any of this becomes interesting. Our VAT compliance features cover how that works, and the VAT201 figures follow from the same data.
Why this is mostly good news
It's easy to read continuous reporting as continuous surveillance, and there is a real shift here: from SARS checking your numbers after the fact to SARS seeing them as they happen. But the trade is a decent one for businesses that keep clean books.
The countries that have done this well have seen fewer verification requests, faster refunds, and far less of the archaeology that a VAT audit currently involves. If SARS already holds your transaction data in a structured form, there is much less to argue about — and the vendors who suffer under these regimes are consistently the ones whose records were disorganised to begin with.
So the sensible posture is neither panic nor indifference. There is no deadline to miss right now. There is, however, a very predictable direction of travel, and the work that gets you ready for it is the same work that makes your VAT returns boring. That's worth doing anyway.
This guide is general information to help you get oriented — it isn't formal tax or legal advice. Thresholds, rates and deadlines change, so confirm the current figures on the SARS website or with your accountant before you act.