What Is Fatoorah?
Fatoorah is Saudi Arabia’s mandatory electronic invoicing system, introduced by ZATCA under the E-Invoicing Regulation issued in December 2020. It requires all VAT-registered resident taxpayers to generate, store, and — from Phase 2 onwards — transmit invoices electronically through a ZATCA-compliant system. The regulation covers Tax Invoices (B2B), Simplified Tax Invoices (B2C), and their associated credit and debit notes.
The name simply means “invoice” in Arabic. But behind it sits a compliance framework far more demanding than the word suggests. Fatoorah is not about producing a digital PDF instead of a paper document — it mandates specific XML formats, mandatory data fields, cryptographic stamps (tamper-evident digital seals), QR codes, and in Phase 2, real-time connectivity between your invoicing system and ZATCA’s FATOORA platform.
The E-Invoicing Regulation was issued by ZATCA’s Board of Governors on 4 December 2020. The implementation rules are set out in the Controls, Requirements, Technical Specifications and Procedural Rules Resolution (last updated May 2023). The regulation is read alongside the VAT Law and VAT Implementing Regulation — a non-compliant e-invoice is not a valid tax invoice and cannot support a buyer’s input VAT deduction.
Who Must Comply
The E-Invoicing Regulation applies to all resident taxable persons registered for VAT in Saudi Arabia, and to any third party issuing invoices on behalf of a resident taxable person. There are no industry or sector exemptions. Non-resident taxpayers without a Saudi establishment are outside scope.
| Taxpayer Category | Phase 1 | Phase 2 |
|---|---|---|
| Resident VAT-registered taxpayers | Yes — since Dec 2021 | Yes — wave-based rollout |
| Third parties billing on behalf of a resident taxpayer | Yes | Yes |
| Non-resident taxpayers | Exempt | Exempt |
| Businesses making only exempt supplies | Limited — in-scope for taxable transactions | Limited — in-scope for taxable transactions |
If your business is VAT-registered, Fatoorah applies — there is no opt-out and no size exemption for Phase 1. The only variable is timing: which wave determines your Phase 2 integration deadline.
Phase 1 vs Phase 2 — What Each Requires
Phase 1 (Generation Phase), effective 4 December 2021, required all VAT-registered taxpayers to switch from paper or unstructured digital invoices to electronically generated invoices produced by a compliant EGS. No specific format was mandated. No connection to ZATCA’s systems was required. But the tamper-proofing rules applied in full from day one — no invoice deletion, sequential counters, session logging, unique login credentials.
Phase 2 (Integration Phase), rolling out in waves from January 2023, requires real-time API connectivity between your invoicing system and ZATCA’s FATOORA platform. Tax Invoices (B2B) must be cleared by FATOORA before being shared with the buyer. Simplified Tax Invoices (B2C) are shared immediately and reported to FATOORA within 24 hours. Format is now mandatory XML (UBL 2.1) or PDF/A-3 with embedded XML.
| Requirement | Phase 1 | Phase 2 |
|---|---|---|
| Invoice format | Any electronic format | XML or PDF/A-3 with embedded XML |
| Cryptographic stamp | Not required | Mandatory — applied by EGS using CSID |
| UUID per invoice | Not required | Mandatory |
| FATOORA API connection | Not required | Mandatory |
| Tax Invoice clearance | Not required | Required before sharing with buyer |
| Simplified Invoice reporting | Not required | Within 24 hours of issuance |
| QR code | Required on simplified invoices (4 fields) | Required on both types (9 fields) |
Many businesses believe they are “Phase 2 compliant” because their accounting software generates well-formatted invoices. Compliance is not determined by how the invoice looks — it is determined by whether the system is onboarded to FATOORA with a valid Cryptographic Stamp Identifier and whether Tax Invoices are being cleared in real time. A formatted XML invoice that never reaches FATOORA is not compliant.
Phase 2 Wave Timeline — All 24 Waves
ZATCA rolls out Phase 2 in waves, each targeting taxpayers in a specific revenue band. The rollout began in January 2023 at the SAR 3 billion threshold and has progressively expanded. Wave 24, announced September 2025, brings the threshold down to SAR 375,000 — bringing thousands of SMEs into mandatory scope for the first time. ZATCA must notify businesses at least six months before their integration deadline.
| Wave | Revenue Threshold (VAT-taxable) | Reference Period | Deadline |
|---|---|---|---|
| Wave 1 | Above SAR 3 billion | 2021 | 1 Jan 2023 |
| Wave 2 | SAR 500M – SAR 3B | 2021 | 1 Jul 2023 |
| Wave 3 | SAR 250M – SAR 500M | 2021 | 1 Oct 2023 |
| Wave 4 | SAR 150M – SAR 250M | 2021 | 1 Nov 2023 |
| Wave 5 | SAR 100M – SAR 150M | 2021 | 1 Dec 2023 |
| Wave 6 | SAR 70M – SAR 100M | 2021 or 2022 | 1 Jan 2024 |
| Wave 7 | SAR 50M – SAR 70M | 2021 or 2022 | 1 Feb 2024 |
| Wave 8 | SAR 40M – SAR 50M | 2021 or 2022 | 1 Mar 2024 |
| Wave 9 | SAR 30M – SAR 40M | 2022 or 2023 | 1 Jun 2024 |
| Wave 10 | SAR 25M – SAR 30M | 2022 or 2023 | 1 Oct 2024 |
| Wave 11 | SAR 15M – SAR 25M | 2022 or 2023 | 1 Nov 2024 – 31 Jan 2025 |
| Wave 12 | SAR 10M – SAR 15M | 2022 or 2023 | 1 Dec 2024 |
| Wave 13 | SAR 7M – SAR 10M | 2022 or 2023 | 1 Jan 2025 – 31 Mar 2025 |
| Wave 14 | SAR 5M – SAR 7M | 2022 or 2023 | 1 Feb 2025 |
| Waves 15–22 | SAR 1M – SAR 5M | 2022, 2023, or 2024 | Apr 2025 – Dec 2025 |
| Wave 23 | SAR 750K – SAR 1M | 2022, 2023, or 2024 | 31 Mar 2026 |
| Wave 24 | SAR 375K – SAR 750K | 2022, 2023, or 2024 | 30 Jun 2026 |
Your wave is based on your highest VAT-taxable revenue in any of the listed reference years — not your most recent year. If your revenue was SAR 900,000 in 2022 but fell to SAR 500,000 in 2024, you still fall within Wave 23 (SAR 750,000 threshold) based on the 2022 figure. Always check across all reference years before concluding you are outside a particular wave’s scope.
ZATCA’s “Initiative to Cancel Fines and Exempt Taxpayers from Penalties” has been extended until 30 June 2026. This window covers historical e-invoicing violations. It does not remove the underlying compliance obligation — but it is a time-limited opportunity to correct past gaps without financial penalty.
Tax Invoice vs. Simplified Tax Invoice
Every transaction requires either a Tax Invoice or a Simplified Tax Invoice. The classification flows from the nature of the transaction — not preference — and determines the Phase 2 compliance model for that invoice.
| Feature | Tax Invoice | Simplified Tax Invoice |
|---|---|---|
| Issued to | VAT-registered buyers, government entities (B2B/B2G) | Consumers, non-registered buyers (B2C) |
| Phase 2 model | Clearance — FATOORA must stamp before sharing with buyer | Reporting — share immediately, report within 24 hours |
| Buyer VAT number required | Yes | No |
| Supports buyer input tax deduction | Yes | No |
| B2B sales below SAR 1,000 | Optional — seller may issue simplified, but buyer can request Tax Invoice | Permitted — but buyer loses input tax recovery |
Credit notes and debit notes follow the type of the original invoice they are issued against. A credit note against a Tax Invoice must go through clearance. A credit note against a Simplified Tax Invoice follows the reporting model.
Clearance and Reporting — How the Mechanics Work
Clearance (Tax Invoices): Your EGS generates the invoice in XML, applies your cryptographic stamp using your CSID, assigns a UUID and Previous Invoice Hash, then transmits to FATOORA via API. FATOORA validates the invoice, applies ZATCA’s stamp, and returns the cleared XML. You then share the cleared document with the buyer. An uncleared Tax Invoice is legally invalid — the buyer cannot claim input tax on it.
Reporting (Simplified Tax Invoices): Your EGS generates and stamps the invoice, you share it with the customer immediately, then transmit the XML to FATOORA within 24 hours. The 24-hour window is absolute — it does not pause for weekends, public holidays, or connectivity issues. Automated reporting with retry logic is the only reliable solution at any meaningful transaction volume.
FATOORA validates XML schema conformance, presence of all mandatory fields, mathematical VAT accuracy, cryptographic stamp validity, UUID uniqueness, invoice counter sequence, and the Previous Invoice Hash linkage. Every layer must pass before clearance or acceptance.
EGS Requirements — What Your System Must Do
Your E-Invoice Generation Solution must generate XML invoices in UBL 2.1, assign a UUID to every invoice, apply a cryptographic stamp using ECDSA with your CSID private key, embed the Previous Invoice Hash, generate a 9-field TLV QR code, and connect to FATOORA via API. It must also exclude all prohibited functionalities.
Prohibited functionalities (active from Phase 1): anonymous or default-password access, invoice deletion or alteration after generation, log modification, inaccurate timestamps, invoice counter reset, multiple invoice sequences from one unit, and export of the cryptographic stamp private key.
Onboarding requires accessing the FATOORA portal, generating an OTP per EGS unit, entering it in your system to receive a CSID, and testing in ZATCA’s sandbox before going live. A CSID is required per unit — not per business. A business with 10 POS terminals needs 10 CSIDs.
Option for Very Small Businesses: The ZATCA Online Portal
ZATCA has announced an important accommodation for businesses issuing fewer than 1,000 invoices per year: these taxpayers can generate e-invoices directly through ZATCA’s own online Fatoora portal — without integrating their internal ERP or billing system with the platform.
Under this route, the taxpayer logs into the FATOORA portal using ERAD credentials and generates invoices manually through the portal interface. ZATCA’s system handles XML generation, cryptographic stamping, UUID assignment, clearance, and reporting within the portal environment. The taxpayer downloads the cleared invoice and shares it with the buyer.
The portal route is a compliance-grade solution, not an operational efficiency tool. At 900 invoices per year — roughly 17 per week — it is workable but requires reliable internet access at the time of invoice generation. Businesses approaching the 1,000-invoice threshold should plan an EGS integration before they cross it rather than retrofitting under pressure. Verify current eligibility criteria with ZATCA’s official guidance, as specifics may be refined as the portal option rolls out.
Common Compliance Mistakes
- Treating Phase 1 as finished business. ZATCA auditors examine historical records going back to December 2021. Non-compliant Phase 1 invoices — generated by a Word template, produced by a system with prohibited functionalities, missing QR codes on simplified invoices — are invalid VAT documents. The exposure has not expired.
- Confusing “compliant software” with compliant deployment. A software version that supports Phase 2 is not compliant unless it is correctly configured, every EGS unit is onboarded with its own CSID, and clearance/reporting are actually occurring. Software compliance and deployment compliance are different things.
- Not onboarding every EGS unit. One CSID per business is a common misconception. One CSID per unit is the requirement. Invoices stamped with the wrong or absent CSID are non-compliant — regardless of their content.
- Sharing Tax Invoices before clearance. A workflow that dispatches the invoice on generation — before the clearance response is received — is issuing legally invalid VAT documents on every B2B transaction. This is the single most commercially damaging error because it also puts your buyer’s input tax deduction at risk.
- Missing the 24-hour reporting window. Manual batch reporting that depends on staff availability will miss this window systematically over weekends, public holidays, and holidays. Automated reporting is not optional for any meaningful B2C volume.
Penalties and Enforcement
E-invoicing penalties are applied under the VAT Law framework, with violation classifications set by ZATCA Board resolutions. The key principle: penalties accumulate across assessment periods. A business that fails to integrate with FATOORA is not facing a single fine — it faces exposure for each period of continued non-compliance.
| Violation | Penalty Range |
|---|---|
| Failure to issue invoices through a compliant EGS | SAR 5,000 – SAR 50,000 |
| Using an EGS with prohibited functionalities | SAR 5,000 – SAR 50,000 |
| Failure to integrate with FATOORA by wave deadline | SAR 5,000 – SAR 50,000 |
| Sharing a Tax Invoice before clearance | SAR 1,000 – SAR 10,000 |
| Failure to report Simplified Tax Invoices within 24 hours | SAR 1,000 – SAR 10,000 |
| Failure to maintain e-invoice records as required | SAR 10,000 – SAR 50,000 |
ZATCA processed over 8.2 billion e-invoices in 2025 — a 64% increase from 2024. The data flowing through FATOORA gives ZATCA near-real-time visibility into which businesses are issuing invoices, at what volumes, and whether those invoices are passing clearance. The ability to detect non-compliance without a field audit has never been stronger.
Frequently Asked Questions
- Fatoorah is a tax compliance obligation managed through technology — not an IT project with tax implications. A non-compliant e-invoice is an invalid VAT document. The stakes go well beyond a technical checklist.
- Phase 1 compliance is not a closed chapter. ZATCA can examine records back to December 2021. Businesses with Phase 1 gaps carry live audit exposure, and the penalty waiver window (open until 30 June 2026) is the practical route to resolve it.
- Wave 24 (deadline 30 June 2026) covers businesses with VAT-taxable revenue above SAR 375,000 in any of 2022, 2023, or 2024. The threshold has expanded significantly. Check all reference years before concluding you are out of scope.
- ZATCA has introduced a portal-based option for businesses issuing fewer than 1,000 invoices per year — allowing invoice generation directly in the Fatoora platform without ERP integration. Verify eligibility criteria with ZATCA’s official guidance.
- Clearance is a prerequisite for Tax Invoices, not a background step. A Tax Invoice that reaches your buyer before FATOORA has cleared it is legally invalid. Configure your workflow so clearance completes before delivery — not after.
- Each EGS unit requires its own CSID. Map your units before onboarding. A shared or missing CSID makes every invoice that unit produces non-compliant from day one of Phase 2.
- With 8.2 billion invoices processed in 2025 alone, ZATCA’s ability to detect non-compliance through FATOORA data is near-real-time. The question is not whether gaps will be found — it is when enforcement action follows.
Deep-dive articles in this series
This article reflects ZATCA’s E-Invoicing Regulation (December 2020) and the Controls, Requirements, Technical Specifications and Procedural Rules Resolution (May 2023 edition), supplemented by publicly available ZATCA wave announcements through September 2025. It is for informational purposes only and does not constitute legal or tax advice. Wave deadlines and eligibility criteria may be updated by ZATCA — confirm the current position at zatca.gov.sa or with a qualified Saudi tax advisor. dariba.co is an independent platform with no consulting relationships.