The SARS e-invoicing roadmap in 2025
Where SARS sits in 2025 on structured electronic invoicing — MTC, the VAT modernisation track, the OECD CTC direction of travel, and the practical preparation that keeps your VAT201 cycle ready for whatever comes next.
MTC: the umbrella under which SARS is modernising
The Modernised Tax Collection (MTC) programme is the over-arching, multi-year transformation that SARS articulates through its Strategic Plan and Annual Performance Plan. MTC is broader than e-invoicing — it touches PAYE, customs, audit selection, taxpayer engagement and data analytics — but the VAT modernisation track is the closest cousin of the e-invoicing mandates rolling out across the EU, Latin America and parts of Asia. Successive SARS commissioners (Mark Kingon, Edward Kieswetter) have used the MTC framing to signal a direction of travel rather than a fixed date, and the strategic plans tabled in Parliament make explicit reference to OECD best practice on continuous transaction controls. The practical effect for an invoicing team is that SARS will increasingly expect structured electronic data — supplier and customer VAT numbers as separate fields, line-level VAT treatment, CIPC registration numbers — rather than the unstructured PDFs that still dominate the South African business landscape.
VAT modernisation: the sub-track that touches your invoices
Inside MTC, the VAT modernisation track is the one to watch. Its scope covers VAT vendor registration, the VAT201 bi-monthly return cycle, EMP201 PAYE coordination, and the eventual move toward structured B2B invoice exchange. SARS has run multiple consultation rounds with SAICA, IRBA and the larger accounting-software vendors (Sage, Xero, QuickBooks, 4invoices) on what a future e-invoicing architecture should look like. The most consistent signal — both from those consultations and from SARS public statements — is that the architecture is likely to be a Peppol-style four-corner network with a SARS-side reporting overlay, broadly aligned with EU's ViDA package, rather than a centralised clearance model on the Italian SdI or Mexican PAC patterns. That choice matters: it means South African vendors can prepare today by adopting Peppol-capable software and clean VAT-vendor data, rather than waiting for a national platform to be built.
The OECD CTC trend SARS is plugged into
Continuous transaction controls (CTC) is the OECD's umbrella label for the global pattern of tax authorities receiving invoice data at or near the moment of issue, rather than aggregated and reconciled months later in a VAT return. The OECD's Tax Administration Forum publishes regular reports cataloguing CTC adoption: Italy's SdI, Spain's SII, Hungary's RTIR, Poland's KSeF, Mexico's CFDI, Brazil's NF-e, Chile's DTE, and now the EU-wide ViDA implementation. SARS participates in these forums and has explicitly referenced OECD CTC work in its own strategic documents. For South African vendors, the takeaway is that the destination is not in doubt — only the timetable. Whether the SARS go-live is 2027, 2029 or 2030, your VAT201 cycle is on a trajectory toward real-time data sharing with SARS, and your invoicing software should already be capturing the structured fields that will support that.
Likely architecture: four-corner with SARS overlay
The architecture that emerges most often in South African industry discussions — and that matches the international convergence — is a Peppol-style four-corner model with a SARS reporting overlay. Vendor sends an invoice to vendor's access point; access point routes to recipient's access point via the Peppol network using the recipient's registered identifier (likely the SARS VAT vendor number or CIPC registration number); recipient receives the structured invoice. In parallel, both access points report the transaction to SARS in near-real-time. The model preserves vendor choice of software (any Peppol-capable platform works), avoids the bottleneck of a centralised clearance gateway, and gives SARS the visibility it needs for VAT analytics. It mirrors what the EU is building under ViDA and what South Africa would have to interoperate with anyway if it engaged with cross-border digital trade across SADC and OECD partners.
B2G first: the likely first step
International experience — Italy, France, Poland, Denmark, Belgium — suggests that South Africa is most likely to start by mandating e-invoicing into government before extending to B2B. That means National Treasury, SARS itself, provincial governments, state-owned enterprises like Eskom, Transnet, PRASA and Denel, and the larger municipalities. The pattern allows infrastructure to be tested at scale with a controlled set of receivers, software vendors to certify their products against the receiving rules, and accounting teams to build operational familiarity before the network expands to private B2B. If you supply government in any form, treat the eventual B2G mandate as the more imminent risk; if you are purely B2B, you have more runway, but your software stack still needs to be ready.
What clean VAT vendor data looks like today
Whether the mandate lands in 2027 or 2030, the preparation that pays off either way is clean VAT vendor data. That means: every active customer and supplier in your master data has a verified VAT vendor number (validated against SARS's online VAT vendor search), CIPC registration numbers are captured as structured fields rather than free text on the invoice, line items carry the VAT treatment (standard 15%, zero-rated, exempt) at the line level rather than only at the invoice total, and your invoice numbering is sequential, gap-free and reconcilable to your VAT201 working papers. Modern South African accounting platforms — Sage Pastel, Xero ZA, QuickBooks SA, 4invoices — capture this natively. If your business is still on a desktop installation of Pastel Partner from 2014, the migration to structured data is the work that needs to happen first, regardless of the SARS roadmap.
Practical next steps for South African vendors
Three concrete moves serve you well no matter when SARS pulls the trigger. First, move off PDF-by-email as your primary invoice exchange — adopt either a Peppol-capable platform (4invoices, Sage Cloud, Xero) or, at minimum, a structured XML export from your existing system. Second, run a data quality audit on your customer and supplier master: validate every VAT vendor number, capture CIPC numbers, and clean up trading partner duplicates. Third, train your AR and AP teams on the operational difference between a PDF flow and a structured flow — credit notes, partial settlements, dispute resolution all change shape when the exchange is machine-readable. Done in 2025, these three steps put your team ahead of the curve. Wait until the mandate lands and you will be doing the same work under deadline pressure, alongside every other South African business trying to certify against the new rules.
Source instruments at a glance
Frequently asked questions
Is there a confirmed go-live date for SARS e-invoicing?
Not at the time of writing. SARS has signalled direction but not committed to a fixed date in any public document. Industry estimates cluster around 2027–2030, broadly aligned with the EU ViDA timeline, but the actual rollout depends on SARS's IT capacity, Treasury budget allocations, and political prioritisation. Treat any specific date you see in trade media as informed speculation rather than official SARS commitment.
Will SARS use Peppol or build its own platform?
The most likely outcome — based on industry consultations and SARS public statements — is a Peppol-style four-corner network with a SARS reporting overlay. This matches the EU ViDA direction and avoids the cost of building a centralised national gateway. South Africa is not yet a formal Peppol Authority, but the country's largest software vendors are already implementing Peppol BIS Billing 3.0 in anticipation, and the technical foundations are in place.
Do I have to change anything in my VAT201 process now?
No — the VAT201 bi-monthly return through SARS eFiling remains the law, and the current rules on tax invoice content (VAT Act s20) are unchanged. What you should be doing is cleaning up your underlying data: validate VAT vendor numbers, capture CIPC numbers, push VAT treatment to the line level, and adopt invoicing software that can export structured XML if asked. The VAT201 you file is unchanged; the system underneath should be ready for the next step.
How does South Africa's roadmap compare with the EU's ViDA?
Architecturally, the most likely outcomes are very similar: a structured exchange network (Peppol BIS Billing 3.0) plus a tax-authority reporting overlay. ViDA mandates EU-wide adoption by 2030; South Africa's pace is determined by SARS's internal capacity and Treasury prioritisation. The technical model is broadly converged across both jurisdictions, which is good news for software vendors and for any South African business that trades into the EU — the same invoicing platform handles both regimes.
Where does B-BBEE compliance fit in?
B-BBEE is a separate regulatory layer from VAT and SARS e-invoicing, but it overlaps in interesting ways. Future B2G e-invoicing flows are very likely to surface B-BBEE level information on the structured invoice (or in a linked metadata field), so that the public-sector buyer can see immediately how the supplier counts toward its B-BBEE scorecard. The SARS roadmap and the B-BBEE Codes will increasingly intersect at the data-capture layer — another reason to capture supplier B-BBEE certificates as structured fields today.