SARS's Digital VAT Model Is Coming — Why Load-Shedding-Proof Software Matters More Than Ever
SARS and National Treasury confirmed in February 2026 that South Africa is moving to mandatory e-invoicing and near-real-time VAT reporting, built on a Peppol-based five-corner model routed through a Central Tax Hub. A public consultation on the proposal ran through October 2026. The rollout is phased — largest VAT-liable businesses and priority sectors first, full operation targeted around 2028 — but the model itself is worth understanding well before it reaches you.
What "real-time" actually means here
Under the five-corner model, invoices route through SARS's Central Tax Hub for validation — "clearing" — before they count as valid tax invoices for VAT deduction. That's a meaningful shift from today's world, where you generate an invoice and only reconcile with SARS later. It also means your accounting and ERP systems need to produce properly structured invoices and hold a live, secure connection to an accredited service provider — not just export a report at month-end.
The part that doesn't get discussed enough
A real-time compliance model quietly assumes something South African businesses can't take for granted: a real-time connection. Load-shedding schedules, patchy mobile data on the road, and site-level connectivity gaps are just Tuesday for a lot of businesses here — especially anyone with people or vehicles out in the field. A system that simply fails, or worse, silently drops a transaction, when the connection cuts out isn't just an operational headache under this model. It's a compliance gap.
The fix isn't complicated in principle: software that keeps working offline, queues what it needs to send, and syncs cleanly the moment connectivity comes back — rather than treating "online" as a given. It's exactly the approach behind Delivery, our proof-of-delivery and route-planning app, which is built to keep capturing proof of delivery, damage, and refusals whether or not the driver has signal at that exact moment. The same offline-first thinking needs to extend across the rest of a business's stack as real-time reporting becomes the norm, not just the customer-facing side.
What to do now, not later
You don't need to solve for the full five-corner model today — the phased timeline gives you room. What's worth doing now is an honest audit: does your current software actually handle a dropped connection gracefully, or does it just fail and hope someone notices? That answer matters a lot more once "real-time" becomes a legal requirement, not just good practice.
We build software to how South African businesses actually operate — load-shedding included, not treated as an edge case. If you want a straight answer on where your setup stands, let's talk.