ZATCA e-invoicing Phase 2: integration, waves, and what your invoices must carry

The two phases, briefly

Phase 1 (generation, live since December 2021) required all VAT-registered businesses in KSA to issue e-invoices from a compliant system — no handwritten or plain-PDF invoices. Phase 2 (integration) is the real shift: your invoicing system connects to ZATCA's Fatoora platform, and invoices flow to the authority in near-real time.

What integration means day to day

• Standard (B2B) tax invoices are cleared: sent to ZATCA first, cryptographically stamped, and only then delivered to your customer — an uncleared invoice is not a valid tax invoice
• Simplified (B2C) invoices are reported: issued to the customer immediately, transmitted to ZATCA within 24 hours
• Every invoice carries the Phase 2 technical envelope: XML (or PDF/A-3 with embedded XML), UUID, cryptographic stamp, hash chain, and QR code
• Your system must be onboarded onto Fatoora with a production certificate per device/unit

The wave system

ZATCA phases businesses in by taxable revenue, in numbered waves with individually announced deadlines. Integration began in January 2023 with the largest taxpayers (above SAR 3 billion) and the threshold has stepped down wave by wave since — reaching businesses with revenue in the low millions of riyals through 2025 and continuing downward in 2026. Each wave gets formal notice from ZATCA at least six months before its deadline.

The operational takeaway: if you are VAT-registered in KSA and not yet integrated, your wave is a matter of when, not if. The revenue test uses your VAT-taxable revenue, and ZATCA's notification arrives against the year they measured — a business that grew recently should assume it is closer to the front of the queue than it feels.

Where implementations go wrong

• Treating it as a tax project instead of a systems project — the hard part is the ERP/POS integration and certificate management, not the VAT logic
• Invoice fields that pass Phase 1 but fail Phase 2 validation: missing buyer details on standard invoices, wrong invoice type codes, broken hash chains after system restores
• Credit notes issued outside the platform flow — corrections must travel the same cleared/reported path as the invoices they amend
• Waiting for the notification letter to start — six months is short for an ERP integration with certification testing

How Orbit applies this

Orbit validates KSA invoices against the Phase 2 field requirements as they arrive, flags documents that would fail clearance, and reconciles what your system issued against what the ledger holds — so integration day is a switch-flip, not an archaeology project.