CATEGORIES
- (3)AI & Technology
- (52)Accounting & Financial Reporting
- (1)Accounting for Income Tax
- (1)Assessed losses
- (38)Blogs
- (4)Business Advisory
- (8)Capital Gains Tax
- (1)Capital Gains Tax - Individuals Tax
- (1)Capital Gains Tax Implications of Trusts
- (2)Case study: Home office expense
- (1)Case study: Travel allowances
- (1)Company Formations
- (10)Compliance
- (141)Corporate Tax
- (15)Customs and Excise
- (2)Deceased Estate
- (1)Deductions Pre-trade and prepaid expenses
- (1)Deregistration
- (2)Employer and Employee (PAYE and UIF Specific)
- (1)Estate Duty
- (1)Events / Webinars
- (11)Faculty News
- (2)Farming
- (177)Individuals Tax
- (1)Input - Customs Duty
- (3)Interest
- (23)International Tax
- (1)Nature of the rights of beneficiaries
- (1)Notional input tax
- (10)Payroll
- (1)People & Practice Management
- (2)Practical Payroll
- (1)Professional Ethics
- (2)Provisional tax (Link with other Taxes)
- (4)SARS Issues
- (178)Tax Administration
- (2)Tax Administration Part 2B: Resolving Problems with SARS using the Tax Ombud
- (1)Tax Administration Part 3B Dispute Resolution - Objection and appeal
- (8)Tax Dispute Resolution
- (1)Tax Opinions
- (3)Tax Update
- (1)Tax implications of loans to trusts
- (1)Tax residence
- (1)Tax returns and payments
- (3)Transfer-Pricing
- (1)Trust Income / Gain Allocations
- (1)Trust types and income allocations
- (12)Trusts
- (88)VAT
- (3)VAT periods
- (1)Wear and tear allowances
- (14)Wills, Estates & Succession
- (1)Zero Rated
- (2)eFiling
- Show All
VAT modernisation: prepare the transaction data before buying the technology
- 27 October 2026
- VAT
- Dr Stiaan Klue
Source: Monthly Tax Update, Professor Jackie Arendse, October 2026. Webinar-on-Demand: Monthly SARS Update with Prof Jackie Arendse - October 2026
At a glance
|
Topic |
Position in the proposal |
Sensible action now |
|
Digital model |
Structured e-invoicing, exchange and e-reporting through a decentralised network. |
Map how invoices become ledger and VAT data. |
|
SARS information |
VAT-relevant information, with detail subject to design and consultation. |
Identify data ownership and access controls. |
|
Rollout |
Indicative phased implementation from 2030, after development, validation and pilot stages. |
Prepare a proportionate readiness plan; monitor final requirements. |
|
Small businesses |
Simpler tools and later onboarding are contemplated. |
Improve basic records before committing to complex integration. |
|
Consultation |
The published comment deadline was 16 October 2026. |
Track subsequent decisions; the stated deadline has passed. |
VAT modernisation will place greater emphasis on the quality of transaction data at the point where invoices are created and received. That is the central preparation task for tax accountants. Automating a flawed tax code or incomplete customer record can transmit the error more quickly without correcting the underlying tax treatment.
The South African Revenue Service (SARS) consultation paper proposes a Digital VAT Model combining structured e-invoicing, secure exchange and e-reporting. It describes a direction and indicative implementation journey, rather than a presently operative universal mandate requiring every vendor to connect immediately. The existing statutory steps supporting voluntary e-reporting should likewise not be confused with a final compulsory rollout for all businesses.
Understand what the five-corner model does
The proposed five corners are the supplier, the supplier’s service provider, the buyer’s service provider, the buyer and SARS’s service provider. Businesses would interact through their systems and accredited providers, with invoice exchange and VAT-relevant reporting operating through the wider network.
This differs from emailing a PDF. A structured electronic invoice contains data capable of being processed through agreed formats and rules. The commercial invoice, the accounting entry and the information reported for VAT must remain connected, including subsequent adjustments.
The FAQs describe decentralised clearance as checks performed by an accredited provider before an invoice is accepted and transmitted. Those checks should not be understood as a professional opinion that the underlying supply is correctly classified for VAT. A technically accepted invoice may still contain an incorrect tax treatment. The responsibility for tax analysis therefore remains an important design consideration.
The published model also does not establish unrestricted access by SARS to every field in a business’s systems. The stated intention is to provide VAT-relevant information, with final data requirements subject to consultation, legislation and design. Accountants should record what is proposed and what remains unsettled rather than supply a definitive field list that SARS has not finalised.
Client conversation trigger: Ask VAT clients to map one sales invoice and one supplier invoice from creation through approval, ledger posting, VAT coding and later correction.
Use the published roadmap without turning it into a deadline
The consultation paper describes preparation in 2026/2027, solution development in 2027/2028, validation in 2028/2029 and a pilot in 2029/2030. Phased implementation is expected to commence during 2030 and extend over approximately 36 months. These are indicative planning assumptions, subject to consultation, approvals and readiness.
|
Proposed stage |
Indicative period in the paper |
Focus |
|
Preparation |
2026/2027 |
Research, consultation, readiness and draft regulations |
|
Solution development |
2027/2028 |
Standards, systems and enabling framework |
|
Validation |
2028/2029 |
Controlled testing with voluntary participants |
|
Pilot |
2029/2030 |
Operational testing and refinement |
|
Phased implementation |
From 2030, approximately 36 months |
Segment-based adoption, with sequencing subject to change |
Large businesses are expected to feature early, with government and smaller-business segments addressed through the phased approach. Voluntary participation precedes later mandatory adoption under the proposed model. A shorthand statement that all businesses have five years to comply would therefore conceal both the proposed stages and the uncertainty in final obligations.
The public consultation deadline stated on the SARS page was 16 October 2026. At the preparation date of this article it has passed. Firms should monitor the subsequent specifications and legal instruments, rather than tell clients that this particular consultation remains open.
Client conversation trigger: For clients planning an accounting-system replacement, include structured invoicing and adaptable tax-data interfaces in requirements, while marking all SARS-specific mandates as subject to final confirmation.
Move tax controls closer to the transaction
The most useful immediate work is largely independent of vendor selection. Review customer and supplier master data, the ownership of VAT registration details, tax-code approval, invoice numbering, credit-note links and reconciliation procedures. Identify manual spreadsheets that currently repair errors only when the VAT return is prepared.
For each material supply type, the tax team should be able to explain why the code is appropriate and what evidence supports it. This includes the handling of exceptions, changes in treatment and transactions that require further documentation. The recommendation is an editorial control response to the proposed model, not a new statutory list of mandatory system features.
A practical test is to select a credit note. Can the business trace it to the original invoice, show the commercial reason, identify the VAT effect and prevent both documents being reported inconsistently? Similar tests should cover duplicates, rejected invoices, cancellations and timing differences. They expose weaknesses that can already affect returns, even before e-reporting changes the submission process.
An implementation plan also needs a clear division of responsibility. Finance should own transaction completeness; the tax function should approve treatment; technology teams should manage interfaces and access; and management should approve service arrangements and continuity plans. A service provider can transmit information without taking responsibility for every business judgement embodied in it.
Client conversation trigger: Offer a targeted VAT-data review focused on master data, tax codes, credit notes and reconciliation exceptions, with an accountable owner for each defect.
Keep preparation proportionate to the client
A large vendor with several systems may need to map interfaces, business units and providers early. A small vendor may first need reliable invoice records and separation of business and personal transactions. The FAQs contemplate simpler accounting packages, portals and assisted channels; they do not require every small business to build a bespoke integration now.
The commercial case should therefore be based on current weaknesses and plausible adaptability. Avoid presenting speculative accreditation, guaranteed refunds or a specific supplier’s product as an established SARS requirement. Faster refunds and reduced manual work are intended outcomes of better information and risk assessment, not guarantees for every vendor.
Readiness should be measured through evidence: a documented invoice flow, clean master data, explainable VAT codes, traceable adjustments and a reconciliation that identifies exceptions. Those improvements have value under current compliance processes and provide a defensible base for responding when the final design is published.
Client conversation trigger: Agree a readiness scope suited to the client’s scale: basic records and controls for smaller vendors, and interface, governance and testing plans for complex groups.
Practitioner action checklist
|
# |
Area |
Finding or requirement |
Clients affected |
Action required |
Deadline |
|
1 |
Current process |
Digital reporting depends on transaction quality. |
All VAT vendors |
Map invoice-to-return flow and manual adjustments. |
Next control review |
|
2 |
Tax treatment |
Technical validation does not settle tax classification. |
Vendors with varied supplies |
Assign tax-code ownership and evidence requirements. |
Before system changes |
|
3 |
Adjustments |
Credits and exceptions must remain traceable. |
High-volume vendors |
Test original-document links and reconciliations. |
During readiness review |
|
4 |
Procurement |
Final specifications and mandates remain subject to development. |
Clients upgrading systems |
Require adaptability; verify claims against published SARS material. |
Before commitments |
|
5 |
Monitoring |
Indicative rollout begins from 2030. |
Firms and VAT clients |
Review final regulations, specifications and onboarding notices as issued. |
At each material publication |
Related reading: Reconstructing liability after backdated VAT registration; Completing the diesel refund registration transition; Reportable arrangements: put the disclosure decision into the transaction file.
Official source: SARS: VAT modernisation.
Frequently asked questions
When will SARS e-invoicing become mandatory?
The consultation paper describes indicative phased implementation from 2030, after development, validation and pilot stages. It is not a presently operative universal mandate.
What is the five-corner VAT model?
The five corners are the supplier, the supplier’s service provider, the buyer’s service provider, the buyer and SARS’s service provider. Invoice exchange and VAT reporting operate through that network.
Does a validated e-invoice mean the VAT treatment is correct?
No. Clearance checks are not a professional opinion that the supply is correctly classified, and a technically accepted invoice may still contain an incorrect tax treatment.
Build your expertise: to apply these principles in practice, explore The Tax Faculty’s Short Course in Value-Added Tax.
About the author
Dr Stiaan Klue is Executive Dean and CEO of The Tax Faculty. He was the founding CEO of the South African Institute of Taxation (SAIT) and is the founding author of Silke on Tax Administration (LexisNexis).