Saudi Arabia
ZATCA Phase 2 e-invoicing: what Saudi businesses must do
Integration phase waves now reach businesses with modest revenues. Here is exactly what your invoicing system has to produce, and the order to do the work in.
18 June 2026 · 8 min read · By the Meridian team
Phase 2 is an integration exercise, not a formatting one
Phase 1 asked you to issue structured electronic invoices. Phase 2 asks your system to talk directly to ZATCA's Fatoora platform in real time. Standard tax invoices must be cleared before they reach the buyer; simplified invoices are reported within twenty-four hours. That difference decides your architecture, so establish which invoice types you actually issue before you evaluate a single vendor.
The technical requirements in plain terms
Your solution must generate XML or PDF/A-3 with embedded XML, apply a cryptographic stamp, carry a UUID and a hash of the previous invoice, print a compliant QR code, and store an anti-tampering counter. It must also block deletion of issued invoices. Most reputable cloud platforms handle this natively; bespoke ERP builds are where projects overrun.
A sensible sequence of work
First, confirm your wave date from the ZATCA notification. Second, audit your master data — buyer VAT numbers, addresses and item tax codes are the most common cause of rejected invoices. Third, obtain your compliance cryptographic stamp identity through the onboarding portal in a sandbox. Fourth, run parallel issuance for at least two weeks before your live date so failures surface while you still have a fallback.
What goes wrong most often
Missing or malformed buyer VAT registration numbers, credit notes that do not reference the original invoice, and rounding differences of a halala between the XML and the PDF. None of these are difficult, but all of them are found on the day you go live unless you test deliberately.