SARS e-invoicing and VAT Modernisation: what South African businesses need to know

What is SARS VAT Modernisation?

VAT Modernisation is SARS’s programme to move VAT away from retrospective, declaration-based returns towards transaction-level data that SARS receives as business happens. It builds on a 2023 discussion paper and, in August 2026, became a formal VAT Modernisation Consultation Paper open for public comment.

The long-term goal is ambitious: with structured invoice data flowing in near real time, SARS wants to pre-fill VAT returns and, over time, move towards auto-assessment — so a vendor’s job shifts from compiling a return to reviewing one. SARS describes the direction as connecting it “across the VAT value chain to every point of sale”.

The Digital VAT Model, explained

The proposal rests on three connected pillars:

1. Structured e-invoicing. Invoices become machine-readable data that accounting systems can process automatically — not documents that people read.
2. An interoperability framework. Suppliers and buyers exchange invoices through accredited service providers (access points) that validate and transmit them, rather than sending files directly. SARS would publish the list of accredited providers.
3. E-reporting. VAT transaction data reaches SARS electronically in near real time, supporting risk detection, pre-filled returns and later auto-assessment.

Commentators describe this as a decentralised, five-corner model: the supplier (1) sends an invoice through its provider (2) to the buyer’s provider (3) and on to the buyer (4), while SARS (5) receives the tax data. SARS itself calls the design a Decentralised Continuous Transaction Control and Exchange (DCTCE) model. Unlike fully centralised systems, SARS would not sit in the middle of every exchange.

What counts as an e-invoice?

Under the proposal, an e-invoice is structured and machine-readable, following a prescribed data model. A PDF, a scanned copy or an emailed file would not qualify on its own. The paper names several standards as reference points:

• EN 16931 (the European e-invoicing semantic standard, via a CIUS)
• UN/CEFACT Cross-Industry Invoice (CII)
• Peppol PINT — the international Peppol specification

The final standard, signature requirements and validation rules will be set in regulations still to come. Scope is expected to cover B2B, B2G and eventually B2C transactions, including credit and debit notes.

Proposed timeline

SARS has not set a binding start date. The consultation paper outlines a staged path — as summarised by KPMG — that looks like this:

Why act before it’s mandatory? The businesses that struggle most with e-invoicing mandates are those that leave integration until the final year — when every service provider and consultant is booked, and data-quality problems surface under deadline pressure. The preparation window is the cheapest time to fix your invoice data and choose an integration approach.

What this means for your ERP and billing systems

E-invoicing is less a tax change than a data and systems change. Most South African organisations will face some version of the same questions:

• Data completeness. Every invoice must carry clean, structured data — VAT numbers, tax categories, line items, references to original invoices for credit notes. Gaps that a human reader ignores will fail automated validation.
• Many invoicing systems. Groups often invoice from several systems — an ERP, a POS estate, a billing platform, sometimes a custom database. Each one needs a compliant path to an accredited provider.
• Legacy and customised ERPs. Older or heavily customised installations (common across Sage, Syspro and in-house systems) may not get native e-invoicing support, or only through costly upgrades.
• Resilience. When invoice exchange depends on external networks and SARS systems, outages and slowdowns must never stop you from trading or billing. Plan for queuing, retries and reconciliation.
• Receiving, not just sending. Your suppliers will send you e-invoices too. Accounts payable needs a way to import structured purchase invoices, match them to suppliers and respond to them.
• Audit trail. You will need to prove what was sent, when, and what came back — for years.

Lessons from the UAE: what goes wrong in practice

The UAE is rolling out a similar model — invoices exchanged through accredited service providers on a Peppol-based network — about two to three years ahead of South Africa. Practitioners there keep reporting the same problems, and most of them aren’t technical.

1. Master data is the critical path

Customer records that look complete often turn out to lack VAT numbers, and product lines lack the classification data a structured invoice requires. Closing those gaps needs people who know the customers and products — it isn’t an IT task. One UAE practitioner reports projects planned at six to eight weeks taking sixteen to twenty for exactly this reason.

2. Issued e-invoices can’t be quietly edited

Informal habits stop working: amending an invoice after it’s sent, fixing a price on next month’s invoice, or recording intercompany stock transfers on internal forms. In the UAE an issued e-invoice can’t be changed — the only correction is a credit note and a reissued invoice, which affects both your VAT and your customer’s. South Africa’s rules aren’t final, but expect the same principle.

3. Collecting customer VAT numbers takes longer than you think

Start early. Larger customers respond faster when you explain that a correct VAT number protects their input tax claims. Email requests to small retailers are often ignored — routing them through your sales team works better. Verify every number you receive, and remember that a small business customer isn’t automatically a consumer.

4. Test your real invoices, not just the connection

A sandbox test proves the integration works; it doesn’t tell you how many of your real invoices will pass validation. Run last month’s actual invoices through validation and count failures by invoice type. Standard invoices often pass while credit notes fail on a missing reference to the original invoice, or advance-payment invoices fail on the wrong type code — and that tells you exactly what to fix, and who owns the fix.

Choosing an e-invoicing provider: questions to ask

Under the proposed model you will exchange invoices through an accredited service provider. Accreditation and price are only the starting point. Drawing on the UAE Ministry of Finance’s guidance and practitioners’ experience, ask:

• Accreditation: is the provider fully accredited, or only pre-approved? Ask for the reference rather than a press release.
• Ownership: does it run its own platform, or resell someone else’s?
• Integration: can it connect to every system you invoice from, including legacy and custom ones?
• Data readiness: will it help you find and fix data gaps before go-live?
• Scenarios: how does it handle each of your invoice types — credit notes, advance payments, intercompany supplies, exports?
• Resilience: what happens when the network or SARS is unavailable, and what availability commitments (and penalties) does it offer?
• Data protection: where is your data stored, how is it secured and archived, and how does that meet POPIA?
• Life after go-live: what support continues as rules, formats and your business change?

Ask about integration first. Network access is becoming a commodity; getting clean invoice data out of your existing systems is where most projects succeed or fail.

A practical checklist: what to do now

1. Read the consultation paper and the SARS FAQs on the SARS VAT Modernisation page.
2. Comment before 16 October 2026 if your sector has specific invoicing needs — zero-rating, partial input tax, existing EDI, high-volume B2C.
3. Inventory every system that issues invoices, credit notes or debit notes, including POS and custom tools.
4. Assess invoice data quality — customer and supplier VAT numbers, tax codes, master data.
5. Map every invoice scenario you issue — credit and debit notes, advance payments, intercompany supplies, exports, government invoices.
6. Start collecting and verifying customer VAT numbers.
7. Decide your integration approach: native ERP upgrades, a provider-specific connector, or a connecting layer that leaves your systems unchanged.
8. Run last month’s invoices through validation before go-live, and review failures by invoice type.
9. Talk to your auditor or tax adviser about timelines, budget and responsibilities.

How Celium Surge helps

Celium Surge is being built for exactly this transition. Instead of upgrading or modifying your ERP, Surge connects to the systems you already run — receiving files or API calls they already produce, reading new invoices from your existing database, or syncing with cloud accounting — and turns them into compliant e-invoices. It works in both directions: your invoices go out, and your suppliers’ e-invoices come back into your ERP.

• Zero ERP changes: no upgrades, schema changes or new screens for your finance team.
• Never blocks billing: invoices are accepted instantly and buffered safely if external systems are slow, then delivered automatically.
• No Access Point to arrange: Surge works with certified Peppol Access Point partners, which handle the AS4 network exchange and reporting to SARS. Surge connects them to your ERP in both directions.
• Sends your invoices: mapped to Peppol PINT UBL and validated before they leave, with status and invoice IDs returned to your ERP.
• Receives your supplier invoices: mapped to your ERP’s format and posted into accounts payable, with supplier matching, duplicate checks and accept or reject responses — so your input VAT lines up with what suppliers reported to SARS.
• Finds problems before they’re live: run your real invoice history through validation and see failures by invoice type.
• One integration, two countries: the same connection serves SARS and the Mauritius MRA.
• Audit-ready: every submission and response archived to tamper-proof storage.

Surge is in its pilot phase and is being built to the standards SARS confirms after consultation. We’re onboarding a limited first cohort — tell us about your systems and we’ll map your zero-change route. Operating in Mauritius too? Read our MRA e-invoicing guide.

Frequently asked questions

Sources

Checked on 9 October 2026. Regulations change: always confirm details against the official SARS and MRA publications before acting. This guide is general information, not tax or legal advice.

1. SARS — VAT Modernisation (official page) — consultation paper, FAQs, closing date
2. SARS — Media release: SARS invites public input on a new digital VAT model
3. KPMG — South Africa: public consultation on e-invoicing and digital reporting — proposed scope, standards and phased timeline
4. VATupdate — SARS launches consultation on digital VAT modernisation
5. Nexia SAB&T — SARS moves closer to a digital future for VAT administration
6. UAE Ministry of Finance — Considerations for selecting an Accredited Service Provider (PDF) — provider selection criteria
7. Aamer Bhatti (EY) — Choosing an e-invoicing ASP: why businesses need to look beyond compliance — LinkedIn, 28 September 2026
8. Ameer Hamza (AH Chartered Accountants) — E-Invoicing in the UAE: The Deadline Is Fixed. The Quality of Your Implementation Is a Choice. — LinkedIn, 21 September 2026