Why this is a deadline, not a discretionary project
Most transformation programs let you choose your pace. ZATCA’s e-invoicing mandate does not. The waves have pushed the turnover threshold down toward near-universal coverage of VAT-registered businesses in the Kingdom, each targeted taxpayer is notified at least six months before their Integration Date, and correctness — valid XML, cryptographic stamping, clearance through the Fatoora platform — is non-negotiable. If your wave lands mid-way through an S/4HANA migration, the two programs collide whether you planned for it or not.
The two phases, precisely
ZATCA structures e-invoicing in two phases. Phase 1, the “Generation Phase,” has applied since 4 December 2021: invoices must be generated electronically in a compliant format. Phase 2, the “Integration Phase,” began 1 January 2023 and rolls out in waves: on top of generation, targeted taxpayers must meet additional technical and business standards and integrate their e-invoicing solutions directly with ZATCA’s systems — the Fatoora platform.
The wave mechanism keeps lowering the bar
Each wave targets taxpayers above a VAT-relevant revenue threshold, and the threshold keeps dropping:
- Wave 20: taxpayers with VAT-subject revenues exceeding SAR 1.5 million during 2022 or 2023, integrating with Fatoora by 31 October 2025.
- Wave 23: resident taxpayers with taxable turnover exceeding SAR 750,000 during 2022, 2023, or 2024, with an integration window of 1 January to 31 March 2026 (as reported by EY).
- Wave 24: taxpayers whose VAT-subject revenues exceeded SAR 375,000 during 2022, 2023, or 2024, integrating by 30 June 2026, per ZATCA’s announcement.
The direction of travel is unambiguous: from SAR 1.5 million down to SAR 375,000 in four waves. ZATCA has not said any wave is the last one. The practical move is not to debate whether you will be in scope, but to check the ZATCA media center for your notification and treat six months as your real runway.
What compliance actually requires
At Phase 2, invoices are issued in a prescribed XML format and carry a cryptographic stamp, a UUID, and a QR code. Two processing models apply: standard tax invoices (B2B/B2G) follow the clearance model — validated and cleared by Fatoora before they can be shared with the buyer — while simplified invoices (B2C) follow the reporting model, reported to Fatoora within 24 hours. (These mechanics are consistent across ZATCA’s guidance; confirm format-version specifics against ZATCA’s Detailed Guidelines before implementation decisions.)
Read that again from a systems angle: for standard invoices, the tax authority sits inside your billing flow, in real time. An invoice that fails validation is not a report you fix next month — it is a document your customer does not receive.
Delivering it on SAP: DRC as the compliance layer
For SAP-run businesses, the standard-fit answer is SAP Document and Reporting Compliance (DRC), which supports KSA e-invoicing for ECC and S/4HANA across FI/SD/MM scenarios — generating the required XML with QR code and digital signature and integrating to ZATCA through SAP Integration Suite / CPI middleware. (Stated at a general level; verify editions, licensing, and supported process types against SAP’s product documentation for your landscape.)
The clean-core dividend: the next wave becomes a configuration event
Here is the strategic point most compliance projects miss. If you deliver ZATCA compliance by modifying the SAP digital core, every subsequent change — a new wave, a format version, a ZATCA rule update, an S/4HANA upgrade — reopens custom code. If you deliver it as a standardized layer (DRC configuration plus released extensibility: BTP side-by-side, released APIs and BAdIs), those same events become configuration and upgrade activities.
That is the difference between a compliance capability and a recurring compliance project. In a regime where the regulator sets the timetable, it is also the difference between six months being enough and six months being a crisis.
Where agentic assist genuinely helps
Agentic AI does not replace the deterministic compliance pipeline — the XML, the stamping, the clearance calls all run in validated code. Where an assistive, human-in-the-loop agent layer earns its keep is around that pipeline: monitoring wave announcements against your entity structure, triaging clearance and reporting exceptions, classifying rejection reasons, and reconciling cleared versus reported documents so nothing silently falls between systems. Useful, measurable — and deliberately not autonomous.
A pragmatic readiness checklist
Confirm your wave and Integration Date against ZATCA’s own announcements. Assess invoice master-data quality now — bad master data is the top source of rejections. Confirm DRC and Integration Suite licensing for your landscape. Test end-to-end in ZATCA’s sandbox before your window. And plan the cutover with your S/4HANA roadmap in view, not against it.
ZATCA sets the timetable; you choose the architecture. Businesses that treat Phase 2 as a clean-core capability will absorb every future wave as configuration. Businesses that hard-code it into the core will run the same project again every time the regulator moves.
Sources
- zatca.gov.sa — E-invoicing roll-out phases (ZATCA, official)
- zatca.gov.sa — Wave 20 announcement (ZATCA, official)
- ey.com — Saudi Arabia announces 23rd wave of Phase 2 e-invoicing integration (EY Global)
- zatca.gov.sa — Wave 24 announcement (ZATCA, official)
- ZATCA E-Invoicing Detailed Guidelines (ZATCA, official PDF)