South Africa's VAT return is starting to disappear into the transaction

On 17 August 2026 SARS published a consultation paper on VAT modernisation, and it deserves more attention than it has had outside tax circles. No regulation has been gazetted and nothing is mandated. What SARS has published is a description of where VAT administration in South Africa is heading, put out for comment, with the window closing on 16 October 2026.

For anyone responsible for finance systems, that window is the point. This is the phase where the design can still be influenced.

Structured invoices, five corners, near-real-time data

Three pillars.

Structured e-invoicing. Invoices as machine-readable data in a defined format, with the PDF demoted to a rendering of it. The paper points at the European semantic standard and the Peppol business specification as candidate formats.

An interoperability framework. A five-corner model, meaning supplier, supplier's access point, buyer's access point, buyer, and the revenue authority as the fifth corner receiving the data. Accredited service providers act as the access points.

Near-real-time reporting. Transaction data reaching SARS close to the point of transaction, with no periodic return assembled afterwards.

The Commissioner's framing is worth quoting because it says the quiet part plainly. The intention, in his words, is to move "from a system that is still too dependent on manual processes and retrospective verification, to one where VAT compliance becomes part of the systems businesses already use every day."

Read that as an operations statement rather than a tax statement and its implications land differently. Compliance stops being something the finance team assembles afterwards and becomes a property of the transaction systems themselves.

No legislation, no gazetted regulation, no date

This part matters, because the vendor commentary has already run ahead of it.

There is no legislation. No regulation has been gazetted. No mandatory start date exists. SARS's own indicative sequencing puts consultation and draft regulations across 2026 and 2027, design and technical standards in 2027 and 2028, validation with volunteers around 2028 and 2029, a voluntary pilot with large taxpayers near the end of that period, and a phased mandatory rollout beginning around 2030, large businesses and government first.

Indicative is the operative word. Vendor blogs have already published firm mandate dates, and the ones we have seen disagree with each other by two years. If you are being sold a compliance product on the strength of a 2028 deadline, ask where that date comes from, because it does not come from SARS.

Equally, nobody should describe SARS as piloting e-invoicing today. On its own timeline the pilot is years away.

The region is ahead, and that is the useful signal

South Africa is late to this, which makes the direction easier to read.

Egypt began with its largest firms in late 2021 and had extended B2B e-invoicing to effectively all taxpayers by the end of 2024. Since July 2023 a paper invoice there does not support a VAT deduction. Rwanda has required electronic billing machines since 2021. Zambia's Smart Invoice became mandatory for VAT-registered vendors in July 2024, and from January 2025 input VAT deduction depends on the invoice having been validated through it. Uganda's EFRIS obligation has been in place for years and was extended to further sectors during 2026. Nigeria made its system mandatory for large taxpayers from August 2025.

Closer to home for us, the Mauritius Revenue Authority has phased fiscalisation by turnover since 2024. The published timetable moved from the MUR 80 million tier on 30 June 2026 to the MUR 40 million tier on 1 September 2026.

The European Union adopted its VAT in the Digital Age package in March 2025, with digital reporting and structured e-invoicing for intra-EU business-to-business transactions becoming mandatory in July 2030, and existing national schemes required to harmonise onto the same standard by 2035.

The pattern across all of them is the same. Phased by taxpayer size. Documents give way to data structures. Validation moves upstream into the moment of the transaction. And input deduction eventually depends on the invoice having gone through the system, which is the point at which this turns into a cash-flow matter.

Why the revenue authorities are doing it

The European Commission put the EU's VAT compliance gap at 128 billion euro, or 9.5 percent of total VAT liability, for 2023, in its report published in December 2025. Italy, the earliest large adopter of mandatory e-invoicing, recorded the largest single-year fall in its gap of any member state in the year following implementation. The Commission publishes the gap figures. The causal attribution to e-invoicing belongs to commentators, not to the Commission, and the distinction is worth keeping.

No equivalent published figure exists for South Africa's own VAT gap, so anyone quoting one to you should be asked for the source.

What to do in the next twelve months

Nothing about this requires a compliance product today. Four things are worth doing anyway, because they have value regardless of what SARS finally legislates.

Read the paper and comment. The window closes on 16 October 2026. Access-point accreditation and the treatment of non-resident vendors are both live questions, and the organisations that engage now are the ones whose operational reality gets reflected.

Find out whether your systems can emit a structured invoice at all. Not a PDF, not a report. A defined, validated data structure, produced at the time of the transaction. In most estates we have looked at, invoices are assembled from several systems at month end, and that is the thing that will have to change.

Look at your master data. Continuous transaction controls fail loudly on inconsistent customer, tax and product data, because errors that used to be absorbed in a reconciliation become rejections at the point of issue.

Treat it as an integration question. Every implementation of this elsewhere has been won or lost on whether the finance system, the billing system and the tax engine can exchange data cleanly without a person in the middle. That is the same seam we wrote about earlier in this series, and it does not get easier by being left.

Where we come in

Our e-invoicing and tax compliance accelerator is built around that seam: producing a validated, structured invoice at the point of the transaction from the finance and billing systems a business already runs, and exchanging it with an access point. The integration patterns underneath it are the ones described under events, messaging and data. A readiness review against the SARS consultation model is a sensible first step while the design can still be influenced, and it does not require committing to a product.

The last three pieces go back inside our own business, to what happened when we finally measured whether four months of this work had made us faster.