ZATCA E-Invoicing, Defined
ZATCA (the Zakat, Tax and Customs Authority) is Saudi Arabia's tax authority, and e-invoicing — locally known as Fatoora — is its mandate requiring businesses to generate, store, and (depending on phase) transmit invoices electronically in a structured, standardized format, rather than as unstructured PDFs or paper.
The goal is straightforward: make tax reporting more accurate and harder to manipulate, by having invoices generated in a consistent digital format from the point of sale rather than reconstructed later for tax filings.
Phase 1 vs. Phase 2: What's the Difference
Phase 1 (the 'Generation Phase', in effect since December 2021) requires businesses to generate invoices electronically, in a compliant structured format, and store them digitally — no more handwritten or purely PDF invoices for compliance purposes.
Phase 2 (the 'Integration Phase', rolling out in waves since 2023 by taxpayer group) goes further: invoicing systems must integrate directly with ZATCA's platform, invoices need a cryptographic stamp and UUID, and — for B2B ("standard") invoices — need to be cleared through ZATCA in near real time, while B2C ("simplified") invoices need a QR code and are reported shortly after issuance.
Who Needs to Comply
Phase 2 has rolled out in waves based on annual taxable revenue, with ZATCA notifying businesses in each wave ahead of their integration deadline — meaning compliance isn't a single fixed date for every business, but a schedule based on company size that continues to expand to smaller businesses over time.
Any VAT-registered business issuing invoices in Saudi Arabia is in scope eventually; the practical question for most businesses is which wave they fall into and when their integration deadline lands.
What Compliant Software Actually Needs to Do
Generate invoices in the required structured XML format (not just a PDF that looks like an invoice).
Include the mandatory fields — VAT numbers, UUID, cryptographic stamp, and (for simplified invoices) a scannable QR code.
Integrate with ZATCA's API for real-time clearance (standard invoices) or reporting (simplified invoices), depending on invoice type and phase.
Store invoices in a tamper-evident way, since the entire point of the mandate is auditability.
Common Compliance Mistakes
Treating e-invoicing as a bolt-on PDF generator rather than a core part of the ERP/POS system — which tends to break down under real transaction volume and audits.
Missing the distinction between standard (B2B) and simplified (B2C) invoice requirements, which have different technical and timing requirements.
Waiting until close to an integration deadline to start implementation — API integration, testing, and ZATCA onboarding all take real time to get right.
Common Questions
Ready to Put This Into Practice?
Tell us about your project — we'll respond within 24 hours with a tailored proposal.