SARS e-Invoicing: what the Digital VAT Model means for your business, and the date that actually matters

SARS published a VAT Modernisation Consultation Paper on 17 August 2026, proposing a Digital VAT Model built on e-Invoicing, an Interoperability Framework and e-Reporting. Nothing is mandatory yet. Public comment closes 16 October 2026, and phased implementation is only expected to begin in the 2030 calendar year, with large business first.

That is the whole answer, and it is worth reading twice, because almost every headline about SARS e-invoicing this month has compressed it into something that sounds like a deadline you have to meet. It is not. It is a deadline to say something, which is a different kind of date entirely, and a much rarer one.

Here is what SARS actually proposed, what an e-Invoice legally is, when it reaches a business your size, and the one thing worth doing about it this year.

What did SARS actually publish?

On 17 August 2026 SARS released the VAT Modernisation Consultation Paper, a 27 page document setting out a proposed Digital VAT Model for South Africa. The Commissioner describes it as the beginning of a long term reform of the VAT ecosystem, not a change to this year's returns.

The model rests on three components:

• e-Invoicing. Invoices issued as structured, machine readable data rather than documents.
• An Interoperability Framework. A network of accredited service providers that carry those invoices between buyer, seller and SARS.
• e-Reporting. VAT transaction data reaching SARS near the moment of the transaction, instead of after a return is filed.

Together these form what the paper calls a Decentralised Continuous Transaction Control and Exchange model. The plain version: SARS wants to see VAT data as it happens, not months later, and it wants to eventually pre-fill your VAT return from that data.

Crucially, the paper preserves self-assessment. A pre-filled return "must be confirmed or edited by the taxpayer to preserve the self-assessment principle". SARS proposes to do the typing. You still sign off.

What counts as an e-Invoice, and why your current invoices are not one

This is the single most misread part of the paper, and it is the part that matters most to a small business.

SARS defines an e-Invoice as "a structured, machine-readable tax invoice, using a prescribed data model, that is issued, transmitted, and received in a structured electronic format". Then it says the quiet part directly: "It is not merely a PDF, scanned image or emailed document."

So if you invoice by exporting a PDF and attaching it to an email, you do not currently issue e-Invoices, and neither does most of the country. A PDF is a picture of an invoice. An e-Invoice is the invoice as data, in a prescribed format, that the receiving system can read and post without a human retyping it.

The paper names the likely standards: EN16931 CIUS, UN/CEFACT Cross-Industry Invoice, or Peppol PINT BIS. The specifics will land in Regulations still to be proposed, so nobody should be buying a format today.

The existing rules on what a valid tax invoice must contain do not go away. If you are unsure yours are compliant now, that is the more urgent question, and we cover it in tax invoice requirements in South Africa.

How the proposed model moves an invoice

The paper describes a five corner model. Stripped of the jargon, an invoice would travel like this:

1. The supplier issues the e-Invoice from their accounting system and sends it digitally, in near real time, to their own accredited service provider.
2. The supplier's service provider validates it against the prescribed standard.
3. The buyer's service provider receives it, passes it on, and reports it.
4. The buyer receives the cleared e-Invoice into their accounting system, and responds confirming receipt and how the VAT was treated, whether fully claimed, partly claimed or not claimed.
5. SARS, through its own appointed access point, receives the transaction data from both sides. Both the seller and the buyer report the same invoice, which is what the paper calls duplex clearance.

Two consequences follow from that fifth point, and they are the real story. Because both sides report the same invoice, a mismatch is visible immediately rather than at audit. And because SARS holds the data, it can pre-fill the return.

The paper is also explicit that suppliers and buyers "may freely choose their service providers", and that a decentralised framework "eliminates the risk of a single point of failure". This is not a proposal for one government invoicing portal that everyone must log into.

When does this actually reach a small business?

Later than the coverage suggests. SARS sets out five phases, with indicative timing:

Phase	What happens	Indicative timing
1. Preparation	Research, analysis and stakeholder consultation	Commences 2026/2027, about 12 months
2. Solution development	Design and build of the solution and technical framework	About 12 months, 2027/2028
3. Validation	Quality assurance testing in a controlled environment	About 6 months, 2028/2029
4. Pilot	Pilot with voluntary participants from priority segments	About 6 months, 2029/2030
5. Phased implementation	Staged rollout guided by mandates and turnover thresholds	Commences during 2030, extends about 36 months

Phase 5 itself is split, and the order is the part to notice:

• 5a, large taxpayers and businesses, first, because they have the systems and capacity.
• 5b, business to government, so state entities must receive e-Invoices for procurement. May run alongside 5a.
• 5c, micro, small and medium enterprises, after those, and the paper says adoption "will be progressive over several years".
• 5d, business to consumer, last.

So a small business sits in 5c, inside a phase that starts in 2030 and runs for roughly three years, behind large business and government. Voluntary participation is open to any size of business earlier than that.

SARS states plainly that it expects MSMEs to face greater challenges "due to limited IT and finance resources and capability", and commits to onboarding support. It also says what the direction of travel is: MSMEs "will need to gradually move away from paper-based, spreadsheets or emailed PDF invoices, to data driven digital invoicing and exchange, by adopting accounting software or service provider solutions".

That sentence is the actual instruction to small business owners, and it has no date attached to it.

The date that does matter this year

16 October 2026. That is when public comment closes. SARS invites feedback on, among other things, implementation timeframes, readiness, costs and challenges, and submissions go through a Qualtrics survey linked in the paper.

This is the unusual bit. Most SARS dates take a filing or a payment from you. This one takes an opinion, and it is the only point in the process where the cost of compliance for a business your size is still an open question rather than a rule. The businesses that will find Phase 5c hardest are exactly the ones least likely to comment before 16 October.

If the cost of new accounting software or a service provider would be a real problem for you, that is precisely the input the consultation is asking for.

What to do now, and what not to do

Do not buy anything for this yet. The technical specifications will be set in Regulations that do not exist. Any vendor selling you SARS e-invoicing compliance today is selling you a guess.

What is worth doing is the work that pays off regardless of what SARS finally prescribes, because all of it is the same work: getting your invoice data out of documents and into a system.

Capture once, reuse everywhere

The reason a PDF invoice is a problem is not the format. It is that the data inside it gets typed more than once. In most small businesses the same invoice line is entered when the quote is written, again when the invoice is raised, again when it is captured for the books, and again when someone reconciles the payment. Four keystrokes of the same fact, three chances to disagree.

The fix is structural, not clerical:

• One place where a customer exists. Name, VAT number, address and terms live in one record, and the invoice pulls from it. Nobody retypes a VAT number, so nobody mistypes one.
• The quote becomes the invoice. Accepted line items convert directly. No re-entry, so no drift between what was agreed and what was billed.
• The invoice carries its own status. Sent, viewed, due, paid, all on the record itself, so chasing is driven off a field rather than off memory. Our guide on the invoice follow-up process covers the mechanism.
• Reconciliation matches on the reference, not the eye. The payment finds the invoice because they share a reference that was generated once.
• The record is retrievable, not merely kept. Structured records survive a five year retention period in a way that a folder of PDFs named "invoice final v2" does not. See SARS record keeping for the periods and the Acts behind them.

A business that already works this way has a straightforward path when the Regulations land, because its invoice data is already data. A business running on spreadsheets and emailed PDFs will be doing a migration under a deadline, alongside everyone else, in the same year.

None of that is a reason to panic in 2026. It is a reason to stop adding manual invoicing habits you will have to unwind later. Our walkthrough on how to automate the invoicing process covers the practical sequence, and document management covers where the resulting records should live.

Frequently Asked Questions

Is e-invoicing mandatory in South Africa?

No. As at September 2026 e-invoicing is not mandatory in South Africa. SARS has published a consultation paper proposing a Digital VAT Model, with voluntary adoption first and mandatory adoption introduced later in a phased rollout expected to commence in 2030.

When is the SARS e-invoicing deadline?

The only live deadline is 16 October 2026, for public comment on the consultation paper. There is no compliance deadline yet. Phased implementation is expected to start during the 2030 calendar year and run for about 36 months, with large business first.

Does a PDF invoice count as an e-Invoice?

No. SARS states that an e-Invoice "is not merely a PDF, scanned image or emailed document". It must be structured, machine readable, in a prescribed data model, so a receiving accounting system can process it automatically without anyone retyping it.

Will small businesses have to change first?

No. Micro, small and medium enterprises fall into Phase 5c, after large business and government entities. SARS says MSME adoption will be progressive over several years and commits to onboarding and assistance for the segment.

Do I have to use a specific SARS platform?

The paper proposes a decentralised network of accredited service providers, and states that suppliers and buyers may freely choose their service providers. It is not a single government portal, and accreditation lists would be published by a Network Authority.

The short version

SARS e-invoicing is real, it is coming, and it is not coming this year or next. The work that prepares you for it is the same work that makes invoicing less painful today: capture the data once, let every downstream step read from that record, and stop treating a PDF as a system.

If you want to know which parts of your own admin are still running on retyping, that is what a Business Autopsy is for. We map where the same fact gets entered more than once, and what it would take to stop.

Sources: SARS, VAT Modernisation Consultation Paper, August 2026. SARS media release, 17 August 2026, "SARS invites public input on a new digital VAT model to modernise VAT administration". Both read directly on sars.gov.za on 8 September 2026.