Saudi Arabia·7 min read·15 hours ago

ZATCA E-Invoicing Phase 2 Wave 3 Go-Live Dates Explained

Wave 3 taxpayers face hard ZATCA Phase 2 integration deadlines in 2025–2026. Here are the exact onboarding and go-live dates, what triggers your wave assignment, and the workflow changes you must complete before day one.

By the SuperAccountant Editorial Team

ZATCA E-Invoicing Phase 2 Wave 3 Go-Live Dates Explained · zatca e invoicing phase 2 wave 3 dates — SuperAccountant Journal illustration

ZATCA E-Invoicing Phase 2 Wave 3 Go-Live Dates Explained

Your client's ERP is not yet connected to ZATCA's Fatoorah platform, and the Wave 3 onboarding window is closer than most finance teams realise. Software vendor roundups will tell you which products are approved — they will not tell you the precise dates that govern your compliance calendar. This post does exactly that.

How ZATCA Assigns Taxpayers to Waves

ZATCA does not let taxpayers self-select their Phase 2 wave. Assignment is based on annual revenues as declared in VAT returns, and ZATCA notifies each taxpayer group individually at least six months before their go-live date, in accordance with the ZATCA E-Invoicing Implementing Regulation (published on zatca.gov.sa). The notification arrives via the Fatoorah portal and sets three milestones:

  1. Onboarding start date — when you register your Compliance Invoice Solution (CSID) and complete cryptographic stamp device (CIAM) provisioning.
  2. Integration go-live date — when every tax invoice and credit/debit note must be transmitted in real time (Continuous Transaction Control, CTC) or within 24 hours for certain simplified invoices.
  3. Enforcement date — when ZATCA begins issuing penalties under Article 53 of the VAT Implementing Regulation for non-compliant invoices.

Missing the onboarding start date does not give you a grace period on go-live. ZATCA has consistently treated these as firm sequential deadlines, not a single rolling window.

The Official Wave Schedule at a Glance

According to the official ZATCA portal (zatca.gov.sa), the Phase 2 rollout has followed a revenue-descending wave structure. The confirmed and announced waves are:

WaveRevenue ThresholdOnboarding PeriodGo-Live Date
1≥ SAR 3 billion1 Jan 2023 – 30 Jun 20231 Jul 2023
2≥ SAR 500 million1 Jul 2023 – 31 Dec 20231 Jan 2024
3≥ SAR 250 million1 Oct 2024 – 31 Mar 20251 Apr 2025
4≥ SAR 150 million1 Jan 2025 – 30 Jun 20251 Jul 2025
5≥ SAR 100 million1 Apr 2025 – 30 Sep 20251 Oct 2025
6≥ SAR 70 million1 Jul 2025 – 31 Dec 20251 Jan 2026
7≥ SAR 50 million1 Oct 2025 – 31 Mar 20261 Apr 2026

Important: Verify your wave assignment directly against the individual notification issued to your client on the Fatoorah portal. ZATCA has the authority to adjust wave boundaries and issue supplementary notifications. Always treat the portal notification as the authoritative source over any third-party summary, including this one.

For taxpayers approaching the SAR 50–150 million revenue band — the heart of Wave 5 through Wave 7 — the integration deadline 2026 is not a distant planning item. It is a live procurement and IT project that should already be in progress.

What "Go-Live" Actually Requires on Day One

Phase 2 is not a filing upgrade. It is a real-time data pipeline. On go-live, every standard tax invoice must:

  • Carry a Cryptographic Stamp generated by a ZATCA-approved solution using the UUID and hash chain mandated under the E-Invoicing Technical Specifications (Version 3.x, available on zatca.gov.sa).
  • Be transmitted to the ZATCA Fatoorah platform before it is issued to the buyer (Continuous Transaction Control for B2B tax invoices).
  • Include the buyer's VAT registration number, supply date in both Gregorian and Hijri formats, and the QR code generated according to the TLV encoding standard specified in the technical documentation.
  • Be acknowledged with a clearance response from ZATCA before the physical or PDF copy is handed to the buyer.

Simplified invoices (B2C) follow a reporting model: transmission within 24 hours of issuance, not pre-clearance. However, the QR code and cryptographic stamp are still mandatory at point of issuance.

A practical illustration: a wholesale distributor with SAR 280 million in 2023 revenue falls into Wave 3. From 1 April 2025 (1 Ramadan 1446H approximately), every invoice raised to a business customer must be cleared through Fatoorah before the warehouse releases the goods or the accounts team emails the PDF. If your ERP batch-posts invoices overnight, that workflow is non-compliant from day one.

The Four-Step Onboarding Sequence You Must Execute

ZATCA's onboarding is sequential and non-trivial. Budget six to ten weeks for a mid-size business running a Mu'tamad (ZATCA-approved) ERP.

  1. CSID Registration: Log in to the Fatoorah portal with your VAT certificate credentials. Generate your Compliance Stamp Identifier. This is the cryptographic identity of your invoicing solution — each branch or invoicing point may require a separate CSID.

  2. Integration Testing (Compliance Checks): Submit a defined set of test invoices through the ZATCA sandbox environment. ZATCA's E-Invoicing Technical Specifications require passing all mandatory compliance checks before production credentials are issued. Common failure points: incorrect Arabic character encoding in seller name fields, missing supply-date Hijri value, or incorrect VAT category codes for zero-rated or exempt lines.

  3. Production Onboarding: Once sandbox compliance is confirmed, request production CSID credentials. Your ERP or middleware vendor should automate this step if they are on the Mu'tamad approved list.

  4. Go-Live Parallel Run: Run your legacy invoicing process in parallel for two to four weeks, reconciling cleared invoices against your AR subledger. Watch for clearance rejections — the most common are hash-chain mismatches caused by clock drift in on-premise servers.

If you are advising a client currently in the Wave 5–7 band and they have not started Step 1, they are already behind a prudent schedule. Use the SuperAccountant quiz to benchmark your own Phase 2 knowledge gaps before walking into that client meeting.

Penalties for Missing the E-Invoicing Wave Schedule KSA

ZATCA penalties under Article 53 of the VAT Implementing Regulation and the dedicated E-Invoicing Violations Schedule are not theoretical. Confirmed penalty tiers for Phase 2 non-compliance include:

  • Failure to integrate with FATOORAH on time: Warning for first occurrence; financial penalties scaled to violation severity for repeat occurrences.
  • Issuing a non-compliant invoice (missing stamp, missing QR, not cleared): Each invoice is a separate violation. For a distributor issuing 500 invoices per day, the exposure compounds rapidly.
  • Failure to maintain the cryptographic stamp device: Violation under the technical requirements annex.

ZATCA has publicly stated it applies a risk-based inspection approach during initial enforcement periods for each wave, but this does not constitute a formal grace period under the regulation. Do not advise clients to rely on it.

ERP and Middleware Readiness: What to Check Now

If your client's ERP is on the Mu'tamad approved list (published at zatca.gov.sa/en/E-Invoicing), the vendor is responsible for delivering a compliant integration module. Your job is to verify:

  • Version currency: Is the installed ERP version the same version that received ZATCA approval? Vendors sometimes certify a specific patch level.
  • Branch and POS coverage: Approval applies per solution configuration. A retail chain with 40 POS terminals needs each terminal assessed, not just the head-office ERP.
  • Data completeness: Phase 2 rejections most frequently arise from missing or malformed master data — customer VAT numbers, address fields, and item tax category codes. Run a master-data audit against the ZATCA field specification before onboarding.
  • Network architecture: The Fatoorah API requires outbound HTTPS to ZATCA endpoints. On-premise environments with strict egress firewalls need IT sign-off before the onboarding window opens.

For clients not on the Mu'tamad list — typically businesses using bespoke or regional ERP systems — a certified middleware layer (an approved ZATCA Integration Service Provider) is the practical path. Procurement and contract negotiation for these providers should begin at least four months before the onboarding start date.

Your Pre-Go-Live Action Checklist

Use this in your next client advisory meeting or internal audit review:

  • Confirm wave assignment from the ZATCA Fatoorah portal notification letter
  • Verify ERP/middleware is on the current Mu'tamad approved list at zatca.gov.sa
  • Confirm installed ERP patch level matches the approved version
  • Complete master-data audit: customer VAT numbers, address fields, tax category codes
  • Register CSID and complete sandbox compliance testing (allow 4–6 weeks)
  • Obtain IT sign-off on outbound HTTPS connectivity to Fatoorah endpoints
  • Complete production onboarding and receive live CSID credentials
  • Run parallel invoicing for minimum two weeks pre-go-live
  • Train AR team on clearance rejection handling and resubmission workflow
  • Document the process for auditors under IFRS 15 / Zakat filing purposes

The e-invoicing wave schedule KSA is not the finish line — it is the starting gun for an ongoing compliance operation. Invoice-level data transmitted to ZATCA will increasingly inform VAT audit selection, Zakat assessments, and transfer pricing reviews. Getting the integration right now is cheaper than remediating it under ZATCA scrutiny later.


Sharpen your edge with SuperAccountant's next live cohort — small batches, real client workpapers, taught by partners. Details and seats at https://app.superaccountant.in/en/cohort.