Saudi Arabia's e-invoicing, run by the Zakat, Tax and Customs Authority (ZATCA) under the name Fatoora, has two phases. The first requires invoices to be generated and stored electronically. The second requires the invoicing system to be integrated with ZATCA's platform. Taxpayers are brought into the second phase in waves, each told in advance.
Last reviewed: 17 October 2026. Facts checked. We opened ZATCA's e-invoicing roll-out page, and the page text gave the following. Phase 1 (Generation) was enforceable from 4 December 2021 for all taxpayers except non-resident taxpayers, plus parties issuing tax invoices on behalf of VAT-registered suppliers. Phase 2 (Integration) was enforceable from 1 January 2023, rolled out in waves, and ZATCA notifies a taxpayer of its wave at least six months in advance. The wave table was not included in the text we received, so we do not state wave criteria or deadlines. Web search summaries mentioned wave criteria in terms of revenue bands and several dated deadlines, but these came from secondary sources and are not repeated. Check ZATCA's site for the wave your client is in. We did not open the technical specifications or the e-invoicing regulation.
Phase 1: generation
From the date above, taxpayers must generate and store tax invoices and notes through electronic solutions that meet Phase 1 requirements. In plain terms, handwritten invoices and informal spreadsheets are not the way to issue tax invoices. The exact technical and content requirements are in ZATCA's regulation and its supporting documents.
Phase 2: integration
Phase 2 goes further. Electronic invoices and the solutions that issue them must meet the Phase 2 technical and business requirements, and the solutions must be integrated with ZATCA's systems. Practically, this means the accounting or ERP system, or a connected invoicing tool, communicates with ZATCA's platform in a prescribed format.
Phase 2 is not applied to everyone at once. ZATCA groups taxpayers into waves and informs each group at least six months before its date. That notice period is the useful planning fact: a finance team can build the project once the notice arrives.
What a finance team should do
- Find out the wave status. Check ZATCA's communications for the entity's tax registration. Do not rely on a consultant's list without confirming.
- Map the invoice flow. List every system that issues invoices, credit notes and debit notes: ERP, point-of-sale, billing tool, spreadsheets.
- Check master data. Customer and supplier names, tax registration numbers and addresses must be complete and consistent. Weak master data is the most common cause of rejections in e-invoicing programmes generally.
- Choose the solution. Decide whether the ERP vendor, an add-on or a separate provider will handle integration. Ask what happens when the connection is down.
- Test before go-live. Run invoices in a test environment, with credit notes and corrections, not only clean sales.
- Reconcile. After go-live, compare the invoices accepted by the platform with the ledger and the VAT return each period.
- Set ownership. One person should own rejections and exceptions.
The audit and assurance angle
For an auditor, e-invoicing creates new evidence and new risks.
- Completeness of revenue. If every invoice passes through a central platform, the authority has an independent record of sales. Differences between the platform and the ledger become visible externally. An auditor should compare the two.
- Controls over the integration. Who can change invoice templates, mapping or tax codes? Are failed invoices followed up and resolved? Our guide to cloud security audits and shared responsibility is relevant where a third-party provider handles integration.
- VAT return reconciliation. The usual books-to-return check applies; see the structure in our UAE VAT reconciliation checklist, which transfers conceptually, though the rates, forms and rules are Saudi-specific and must come from ZATCA.
- Cut-off and corrections. Credit notes and cancellations need to follow the permitted process, not be handled informally in the ledger.
Comparing with the UAE
The UAE is also moving to e-invoicing, and the two programmes share a broad pattern: a central platform, structured data, and phased adoption. The details, authorities and timelines differ. Our article on UAE e-invoicing readiness covers the UAE side. A group with entities in both countries needs a separate plan for each, though a shared master-data clean-up helps both.
What this guide does not cover
- Wave criteria and deadlines, which need to be read from ZATCA's current wave announcements.
- Technical specifications, formats and security requirements.
- Penalties. These are set by the relevant Saudi regulations and we did not review them.
- VAT rates and rules beyond e-invoicing.
- Audit requirements for Saudi companies, which are separate and depend on the company type and applicable law. We did not source these, so a Saudi licensed auditor should be consulted.
For Indian firms with Saudi-linked clients
The common scenario is an Indian group with a Saudi subsidiary. Support from an Indian firm is typically in group reporting and process review, while the local VAT filing and any statutory audit sit with locally authorised advisers. Agree the split in writing, as for any cross-border work.
Related Articles
Statutory facts on this page are checked against their sources, and the page says where it relied on secondary reporting. How we verify · Report an error