E-invoicing is not mandatory in South Africa today. SARS's Consultation Paper on VAT Modernisation, published in August 2026, expects mandatory, phased adoption to begin during the 2030 calendar year and to run over about 36 months. Large taxpayers come first, adopting voluntarily at first with mandatory adoption introduced later, and government buyers may be brought in alongside them. Micro, small and medium enterprises follow over several years, and sales to consumers come last.
If you have seen 2028 given as the start date, it comes from press and adviser coverage in 2025, not from a SARS document. SARS's own roadmap now sets 2028/2029 aside for testing with voluntary participants and 2029/2030 for a voluntary pilot. The model it proposes is decentralised: accredited service providers validate and clear each invoice, and SARS receives the data through its own access point rather than running a single platform that every invoice must pass through.
What exists in law today is the groundwork. The Tax Administration Laws Amendment Act 4 of 2026 added definitions of an e-invoice, e-reporting and an interoperability framework to the VAT Act, and gave the Minister the power to regulate a voluntary e-reporting system. No regulations have been made under it, and no format or mandatory date is set in law.
SARS's refund figures show why it wants invoice-level data. SARS prevented R50.1 billion in impermissible VAT refunds during the 2024/25 fiscal year, up from R49.0 billion the previous year. Those refunds were caught after returns had been filed. The consultation paper's stated aims are to reduce fraud, close the VAT gap, pay refunds faster, and pre-fill VAT returns from invoice data SARS already holds.
What South African Law Says About E-Invoicing Today
The Tax Administration Laws Amendment Act 4 of 2026 was published in Government Gazette No. 54447 on 1 April 2026. Section 11 of the Act inserts five definitions into section 1 of the VAT Act:
- E-invoice: a tax invoice that "is issued, transmitted and received in a structured electronic format which allows for its automatic and electronic processing" and complies with further requirements the Minister may prescribe by Regulation.
- E-debit note and e-credit note: debit and credit notes under section 21 that meet the same structured-format test.
- E-reporting: electronically submitting tax data extracted from an e-invoice, e-debit note or e-credit note to SARS, to the supplier or its service provider, and to the recipient or its service provider, "within the interoperability framework".
- Interoperability framework: "the use of a network of service providers, where decentralised exchange of e-invoices, e-debit notes and e-credit notes occur, and that can facilitate clearance and interoperability between supplier and recipient".
Section 14 of the Act adds subsection (1B) to section 74 of the VAT Act, allowing the Minister to make regulations "prescribing the requirements for participation by a vendor in a voluntary e-reporting system".
That is the whole of the current legal position. The definitions fix the direction (structured invoices exchanged through a decentralised network of service providers) and the regulation power covers a voluntary system. Nothing in the Act makes e-invoicing compulsory, names a technical standard, or sets a date.
Until regulations say otherwise, a South African tax invoice is still governed by section 20 of the VAT Act. It can be a PDF, a printed page or output from any accounting package, provided it carries the prescribed fields, and the R5,000 threshold still decides whether a full or abridged tax invoice is needed. The current South African VAT invoice field requirements set out those fields in detail.
From Discussion Paper to 2030: SARS's E-Invoicing Roadmap
2023: The Discussion Paper. SARS published its Discussion Paper on Value-Added Tax Modernisation, setting out the case for moving VAT administration onto transaction-level data and inviting comment.
August 2025: The draft bill. The draft Tax Administration Laws Amendment Bill of 2025 carried the e-invoicing definitions and the voluntary e-reporting power for public comment.
1 April 2026: The Act. The bill was enacted as the Tax Administration Laws Amendment Act 4 of 2026.
17 August 2026: The Consultation Paper. SARS released its Consultation Paper on VAT Modernisation: e-Invoicing, Interoperability Framework and e-Reporting, which builds on the 2023 Discussion Paper and sets out the proposed model and a five-phase roadmap. Comments closed on 16 October 2026. SARS says it will consolidate the submissions and hold structured working groups with associations, software vendors, government bodies and taxpayers before adopting a final policy. The paper says its proposals "may be refined following stakeholder input".
The roadmap itself, as SARS sets it out:
| Phase | What happens | SARS's timing |
|---|---|---|
| 1. Preparation | Research, readiness assessment, stakeholder consultation; publication of draft VAT regulations | 2026/2027, about 12 months |
| 2. Solution development | Standards, specifications and operating models defined and built; promulgation of the VAT regulations | 2027/2028, about 12 months |
| 3. Validation | Quality-assurance testing in a controlled environment with voluntary participants | 2028/2029, about 6 months |
| 4. Pilot | Live-like pilot with voluntary participants from priority segments | 2029/2030, about 6 months |
| 5. Phased implementation | Rollout by segment, guided by mandates and turnover thresholds | From the 2030 calendar year, over about 36 months |
Phase 5 is split into four segments:
- 5a: Large taxpayers and businesses (B2B). First, because their systems are more advanced. They are "expected to adopt voluntarily at first, with mandatory adoption introduced later".
- 5b: Business-to-government (B2G). Government entities would be mandated to accept e-invoices for procurement. SARS says this segment may run alongside 5a.
- 5c: Micro, small and medium enterprises (B2B). Adoption "will be progressive over several years", with onboarding support.
- 5d: Business-to-consumer (B2C). Transactions with non-VAT-registered buyers and consumers, where SARS says incentives may be considered.
Voluntary participation will be open to any business of any size. SARS also states that the order of segments may change, "subject to ease of adoption, risk of compliance, VAT gap indications and other factors". The roadmap is a proposal under consultation, so treat the years as SARS's current plan rather than legal deadlines.
How SARS's Digital VAT Model Would Work
SARS calls the proposal the Digital VAT Model: three pillars (e-invoicing, an interoperability framework and e-reporting) forming what the paper names a Decentralised Continuous Transaction Control and Exchange model.
Decentralised Clearance Explained
Today a South African business creates a tax invoice, sends it straight to the customer, and SARS sees only the totals when the VAT201 return is filed. If SARS wants to check an individual transaction, it does so in a verification or audit, often months later.
Under the proposed model, the invoice is checked before it reaches the buyer, but not by SARS itself:
- The supplier issues an e-invoice from its accounting software and submits it "in near real-time for validation and clearance" to its accredited service provider.
- The supplier's provider validates it against the prescribed technical standards and VAT rules. A valid invoice is cleared and sent on; an invalid one is rejected and returned to the supplier for correction and resubmission.
- The buyer's provider validates it again on the buyer's behalf, delivers it, and confirms back to the supplier's provider.
- The buyer responds from its own system with the VAT treatment of the purchase: input tax fully, partially or not claimed.
- Both providers report to SARS's access point. The cleared invoice reaches SARS from the supplier's side and, with the buyer's VAT status, from the buyer's side. The paper calls this "duplex clearance".
Clearance at the supplier's provider, in SARS's words, "ensures compliance at source and eliminates invalid tax invoices". The paper envisages the cleared e-invoice becoming the supporting document for the supplier's VAT liability and for the buyer's VAT deduction. That is SARS's proposal for when the system is in force; until then, a section 20 tax invoice still supports input tax.
Continuous Transaction Controls and Pre-Filled Returns
The approach belongs to the family known as Continuous Transaction Controls (CTC), in which the revenue authority receives transaction data as business happens rather than in periodic returns.
What SARS wants from the data is pre-filled VAT returns, leading in time to VAT auto-assessment, where in SARS's phrase tax compliance "just happens". The taxpayer would still confirm or edit the pre-filled return, which the paper says preserves the self-assessment principle. For a sense of what that would replace, see how finance teams prepare a VAT201 from supplier invoices today, working from each supplier invoice to the return's fields.
What Counts as an E-Invoice
The paper is direct about it: an e-invoice "is not merely a PDF, scanned image or emailed document". It is a structured, machine-readable invoice built on a prescribed data model, with standardised data elements that allow validation, matching, accounting integration and VAT reporting. It must follow an e-invoice standard or specification, for which the paper gives examples: EN16931 CIUS, UN/CEFACT Cross-Industry Invoice, or Peppol PINT BIS, plus the requirements in Regulations still to be proposed. The technical specifications are to cover zero rating, deemed supplies and apportionment.
For a business, that means its invoicing system must produce structured output in the chosen standard and exchange it with a service provider. Invoices typed in spreadsheets or word processors will not meet the definition.
Scope
E-debit notes and e-credit notes are in scope alongside invoices, as both the Act's definitions and the paper make clear. Transactions that do not ordinarily need an invoice, such as deemed supplies, are outside the proposed requirement and are to be considered during consultation and solution design.
Two things are not yet defined. "Near real-time" is described as "a short timeframe close to the point at which a transaction occurs", to be defined in legislation and opened for public comment; no submission window has been proposed. Cross-border compatibility is listed among the success factors, but no rules for cross-border transactions have been set, so businesses with international trade should follow the consultation for updates.
The Five Corners, the Network Authority and Accredited Service Providers
Who Sits in Each Corner
The proposal is a five-corner model, with SARS at the end of the chain rather than in the middle:
- Corner 1 (Supplier): issues the e-invoice from its accounting software and contracts an accredited service provider from a list published by the Network Authority.
- Corner 2 (Supplier's access point): a certified service provider that validates and clears the invoice, then sends it to the buyer's provider and to SARS.
- Corner 3 (Buyer's access point): a certified service provider that validates the invoice on the buyer's behalf, delivers it, and passes the buyer's VAT response to SARS.
- Corner 4 (Buyer): receives and processes the cleared e-invoice and responds with its VAT treatment.
- Corner 5 (Tax authority access point): "the service provider appointed on behalf of SARS". It must connect to every provider in the network and receives all VAT transaction data for risk management and pre-filled returns.
The paper's glossary defines decentralised clearance as "a system where e-Invoices are cleared by accredited service providers rather than a single central authority". SARS gives its main advantage over a central clearance platform as removing the risk of a single point of failure.
The Network Authority
A Network Authority would set, maintain and enforce the network's technical and legal rules, accredit the service providers, and publish the list businesses choose from. Each provider would contract with it under a service level agreement. Who the Network Authority will be, which interoperability framework and which standards are used, depends on "selection and procurement processes currently being finalised by SARS". Legislation is also to address the certification and authorisation of service providers.
Where Peppol Fits
Peppol is an international framework for exchanging e-invoices between certified access points, governed by the non-profit OpenPeppol. A standard Peppol exchange is a four-corner model: supplier, supplier's access point, buyer's access point, buyer, with no tax authority in the flow. Some countries add a fifth corner that receives a copy for tax purposes; Singapore's Peppol-based InvoiceNow system reports invoice data to IRAS that way.
SARS's model has the same shape, with clearance added at the providers. But SARS has not named Peppol as South Africa's network. Peppol PINT BIS appears in the paper as one example standard, alongside EN16931 and UN/CEFACT, and the final choice is part of the procurement SARS is running.
What Accredited Service Providers Mean for Your Business
Once the system applies to you, you will need an accredited service provider, and so will your customers: suppliers and buyers each contract one from the Network Authority's list. Your accounting software, whether Sage, Xero, SAP or a locally developed system, will need to produce compliant e-invoices and connect to a provider, either built in by the vendor or through an integration.
SARS's paper also addresses businesses without that capability. Vendors may "use accredited Access Point service providers to convert existing invoice data into the prescribed format", smaller taxpayers may use service-provider portals or simplified digital tools, and SARS says it will engage software providers on tiered subscription models, "to consider subsidised or low-cost options".
Interoperability
Suppliers, buyers and SARS "may freely choose their service providers". The interoperability framework is what lets a supplier on one accredited provider invoice a buyer on another, so large buyers would not need to dictate which provider each supplier uses.
What Non-Compliance Would Mean
The consultation paper proposes no penalties or enforcement rules for e-invoicing; those would come with the regulations and any later legislation. What it does set out is how the model changes the evidence for VAT.
Once a segment is mandatory, a cleared e-invoice is envisaged as the document that supports the buyer's VAT deduction. A supplier that cannot issue one would leave its customers without the evidence they need to claim input tax. In a clearance model, that is how pressure to comply reaches suppliers: through their customers.
The Tax Administration Act's existing penalties, including administrative non-compliance and understatement penalties, already apply to VAT today and are unaffected by the proposal.
The earliest pressure is likely to be commercial. Large businesses come first in Phase 5, and Phase 5b would require government entities to accept e-invoices for procurement. Suppliers to large firms and the state are therefore the ones likely to be asked for e-invoices first. Government suppliers already work under strict invoicing rules within the PFMA's 30-day payment framework, where non-compliant invoices are rejected and the payment clock resets.
How to Prepare: A Roadmap for Large Taxpayers and SMEs
With mandatory adoption expected from 2030, and large taxpayers voluntary at first, nobody faces a deadline in 2028. The years before then are when the rules get written: draft VAT regulations in 2026/2027, standards and promulgated regulations in 2027/2028, testing with voluntary participants in 2028/2029 and a voluntary pilot in 2029/2030. Preparation is about being ready to act on each of those as it lands.
Large Taxpayers: Plan Through the Regulation Years
Map your invoicing flows. Record how invoices, debit notes and credit notes are generated, sent, received and stored across the organisation, and which systems produce them. Debit and credit notes are in scope, and they are often issued from different systems or by hand.
Ask your software vendors about structured e-invoice output. The question for Sage, SAP, Oracle or a custom ERP is whether it can issue and receive invoices in a structured standard such as EN16931 or Peppol PINT, return the buyer's VAT treatment, and connect to an accredited service provider. A vendor with no answer is something to learn now.
Watch for the Network Authority and the accreditation list. Provider selection becomes possible only once SARS has appointed a Network Authority and accredited providers. Until then, track the procurement and the draft regulations.
Decide on early participation. Testing in 2028/2029 and the pilot in 2029/2030 run with voluntary participants, and voluntary adoption comes before mandatory adoption for large taxpayers. Taking part early gives more time to fix integration problems.
Assign a project team. The paper itself suggests project teams "bridging IT, finance, and compliance functions". Without one owner, e-invoicing work splits between departments.
Budget for parallel running. SARS expects legacy and new systems "to operate in parallel across segments until full transition is achieved". Costs will cover software changes, provider fees, training and that period of running both.
SMEs: Understand the Direction, Act Later
Know what is settled and what is not. The direction is in law: the VAT Act now defines e-invoices and an interoperability framework. The dates are SARS's proposal, and micro, small and medium enterprises are scheduled after large businesses, with adoption "progressive over several years". There is time, but the change is coming.
Follow SARS communications and industry bodies. You do not need to invest in new infrastructure until the standards and the list of accredited providers exist. Accounting bodies and industry associations will carry updates as the regulations are drafted.
Assess how digital your invoicing is. Businesses still issuing paper invoices, spreadsheet invoices or emailed PDFs have the furthest to go, since none of those will be an e-invoice. Standardising how invoice data is captured is a sensible interim step. For organisations working with paper or scanned documents, automated invoice data extraction tools can turn existing invoices into structured spreadsheet data, which is a foundation for later e-invoicing.
Weigh e-invoicing readiness in software decisions. If you are buying or upgrading accounting software in the next year or two, favour providers that already issue structured e-invoices in other mandatory markets. It avoids a forced migration later.
Engage a provider when your segment's rules are set. By then the standards will be fixed, accredited providers will be competing for business, and the service-provider portals and low-cost options SARS has discussed may be available.
South Africa's E-Invoicing Plans in Global Context
South Africa is joining a long list of countries moving to Continuous Transaction Controls, and SARS's paper names the ones it has learned from.
Italy has required clearance of B2B and B2C invoices through a central platform since 2019, which SARS credits with a significant reduction in its VAT gap. South Africa has chosen the other route: decentralised clearance by accredited providers. France is the closest parallel SARS itself names, with a planned "five-corner decentralised model" for B2B e-invoicing and reporting, built on approved private platforms that exchange invoices between businesses. India's phasing by turnover threshold is the closest match to how SARS's Phase 5 would be paced.
Among non-EU economies, the UAE's e-invoicing mandate also routes invoices through accredited service providers in a five-corner model built on Peppol.
Elsewhere in Africa, Nigeria has been building its own invoice controls. Nigeria's VAT invoice requirements set the field rules, and the guide to Nigeria's e-invoicing system covers how its tax authority is applying clearance to business invoices.