Back to all briefings
/ TAX 22 Apr 2026 · 6 min read

ZATCA Phase 2 wave 14: a 90-day go-live playbook.

What the five operationally-painful integration patterns are, and how to sequence around them.

What wave 14 actually means

If your group is in wave 14 (annual VAT-taxable revenue between SAR 30m and SAR 40m as of the relevant reference period), ZATCA expects you to be issuing compliant electronic invoices through an integrated solution from your go-live date. The 90-day window before that date is where every project either lands or slips.

The five painful integration patterns

Across the engagements we have run, the friction concentrates in five places:

  • Multiple billing systems. Groups that run more than one invoicing source — a primary ERP plus a billing tool, plus a manual workaround — face an aggregation problem the SDK does not solve.
  • Credit-note flows. The Phase 2 schema is strict about reference-invoice linkage. Legacy systems that issued credit notes without binding them to a specific invoice will fail validation.
  • Multi-currency edge cases. Conversion treatment must match ZATCA's stated approach; small rounding differences propagate.
  • Self-billing and intra-group flows. Where the customer creates the invoice, the responsibility for compliance does not transfer.
  • B2C scenarios at scale. Volume B2C invoicing has different cryptographic-stamp and reporting requirements; the system must clear them in real time.

How to sequence the 90 days

  • Days 1–15: in-scope mapping. Identify every system that issues a tax-relevant document. Most groups discover at least one they had forgotten.
  • Days 15–45: integration build. Working SDK integration for the primary system; UAT against ZATCA's sandbox.
  • Days 45–75: edge-case coverage. Credit notes, FX, self-billing. This is where projects slip.
  • Days 75–90: parallel run with the legacy system. Reconcile every invoice through both channels before cutover.

The thing most groups underestimate

The cryptographic-stamp lifecycle. Phase 2 requires that each invoice carry a stamp tied to a certificate that itself must be renewed on schedule. The renewal process is operational, not one-time. Build the calendar reminder into your finance ops the same week you go live, not the week before the first certificate expires.

/ FW GLOBAL CONSULTING

If this briefing raises a question on your file, we are glad to take it on a call.