What SARS's e-invoicing plan means for South African distributors, and why to fix the invoice chain now

On 17 August 2026 SARS published its consultation paper on VAT modernisation. It proposes a Digital VAT Model built on e-invoicing, an interoperability framework between service providers, and e-reporting to SARS in near real time. Comments close on 16 October 2026, through the survey link in the paper.

An e-invoice, in the paper's words, is not merely a PDF, a scan or an emailed document. It is a structured tax invoice in a prescribed data model, such as EN 16931, UN/CEFACT Cross-Industry Invoice or Peppol PINT BIS. The same applies to debit and credit notes.

The supplier would appoint a service provider from a list published by a Network Authority. That provider validates each invoice and clears it, or returns it to the supplier for correction. The buyer's provider validates it again and delivers it. Both providers report to SARS's own access point, and SARS would use that data to pre-fill VAT returns, which the taxpayer confirms or edits.

The paper sets out five phases. Preparation runs for about 12 months from 2026/27 and includes draft VAT regulations. Solution development follows in 2027/28, when the regulations would be promulgated. Testing with volunteers takes about six months in 2028/29, and a pilot about six months in 2029/30.

Rollout is expected to start during 2030 and run for about 36 months. Large businesses go first, voluntarily at first and then under a mandate. Government buyers may be brought in alongside them. Small and medium businesses follow over several years, and sales to consumers come last. SARS says the order may change.

A distributor sits in the middle of that order. Your largest suppliers are likely to be in the first wave, and most of your customers in a later one. Your purchase side may change before your sales side does, and your systems will need to handle both for years.

Validation moves to the moment of issue. Today a wrong VAT number on an invoice surfaces when the customer's input claim is queried, sometimes months later. Under the proposed model the provider rejects the invoice, and it goes back to your billing team before the customer ever sees it.

Credit notes become as visible as invoices. Distribution runs on them, for returns, breakage, scheme payouts and rate differences. Each one would be a structured document that has to point to the invoice it adjusts.

The buyer side answers back. In the model as proposed, the buyer's system confirms receipt of each invoice and states whether the VAT was claimed fully, partly or not at all. With both sides reporting, a gap between your input claims and your suppliers' invoices becomes something SARS sees in the data, not something an auditor has to find.

Finance work shifts from month-end preparation to handling the exceptions a system flags as they happen. The paper says as much.

None of this needs the regulations to exist. Each item also cuts VAT risk under today's rules.

1. One customer master. Every VAT-registered customer with a checked VAT number, name and address. A full tax invoice, required above R5,000, must already carry the recipient's name, address and VAT number.
2. Invoices generated from the dispatch. Quantity, unit and VAT on every line, taken from the order and the delivery, not typed again. A full tax invoice must already show quantity or volume.
3. Credit notes tied to their invoice. Every return, scheme payout or price difference raised against the invoice it reduces, with the reason recorded.
4. Supplier bills checked before input tax is claimed. The bill matched to the purchase order and the goods received, and the tax invoice kept on file. SARS allows the deduction only in a period in which you hold the document, and within five years.
5. A question for your software vendor. Which standard will it support, and will it connect to an accredited provider or expect you to find one?
6. A comment to SARS by 16 October. If scheme settlements, returns or small retail customers make the model hard for your trade, the consultation is the place to say so.

Neauron Intelligent Core, our ERP, builds the invoice from the dispatch, raises purchase orders against the budget and receives goods against the order, so a supplier's bill is checked against what arrived before anyone pays it. NeauraBeat AI, our field CRM, takes counter orders at the rate the price master sets and calculates schemes instead of promising them. It is live with distribution businesses today.

For South Africa, Neauron's VAT engine is scoped with your advisers against the SARS roadmap, and field data stays in a South African region. We would start with one number, such as credit notes raised without a link to an invoice, and measure it every week.