ZATCA Phase 2 integration: the steps from wave notice to live invoices
A practical walk-through of ZATCA's integration phase: how waves are set, what to prepare, how onboarding with an OTP and CSID works, and the difference between clearing standard invoices and reporting simplified ones.
Phase 2 of e-invoicing in Saudi Arabia, the integration phase, means your invoicing solution no longer just generates electronic invoices: it connects to ZATCA's Fatoora platform and sends each invoice to ZATCA. For a standard (B2B) invoice, ZATCA must clear it before the buyer receives it; for a simplified (B2C) invoice, you report it within 24 hours. This guide orders the work as it really happens, from receiving your wave notice to issuing live invoices. If you are choosing a system, our page on ZATCA Phase 2 e-invoicing software shows how Aspirations handles each step.
Step 1: know your wave
According to ZATCA, Phase 1 (generation) has been enforceable since 4 December 2021, and Phase 2 started on 1 January 2023 and is rolled out in waves of taxpayers. ZATCA notifies each taxpayer of its wave at least six months in advance. The thresholds are based on revenue subject to VAT, and they have been coming down with each wave:
| Wave | VAT-subject revenue exceeded | In any of the years | Integrate by |
|---|---|---|---|
| 24 | SAR 375,000 | 2022, 2023 or 2024 | 30 June 2026 |
| 25 | SAR 187,500 | 2022, 2023, 2024 or 2025 | 1 February 2027 |
Wave 24 was announced on 26 September 2025 and wave 25 on 24 July 2026. The date that binds you is the one in ZATCA's notification to your company, so check your notices before planning.
Who does what
Phase 2 is shared work. Finance owns the tax data and decides which invoice types the company issues; IT or the software provider owns the solution and the certificates; the person with access to the taxpayer's Fatoora account generates OTPs. Name one owner for each before you start, because onboarding stalls most often while someone waits for an OTP or a missing address.
Step 2: get your master data right
Most rejections come from data, not software. Before onboarding, prepare:
- your VAT number, commercial registration and full national address, including the district, for the company and any branch that invoices under its own tax registration;
- buyer data for B2B customers: VAT number and address, because standard invoices need them;
- a VAT category on every item: standard 15%, zero-rated or exempt;
- a clear list of where invoices are issued: head office, branches, POS terminals. Each issuing solution is onboarded as an e-invoice generation solution unit (EGS unit).
Step 3: make sure the solution meets the technical requirements
ZATCA's technical guidelines and security features standard define what each Phase 2 invoice carries:
- UBL 2.1 XML: the invoice is a structured XML document, not a PDF.
- UUID: a unique identifier for every invoice.
- Invoice counter (ICV): a sequential counter per EGS unit that cannot be reset or skipped.
- Previous invoice hash (PIH): each invoice carries the hash of the one before it, forming a chain that shows if an invoice is removed or reordered.
- Cryptographic stamp: an electronic signature created with the unit's certificate, using ECDSA keys and the XAdES format described in the standard.
- QR code: encoded in TLV format; in Phase 2 it carries more than the Phase 1 fields, including hash and signature data.
Step 4: onboard each EGS unit with an OTP
Onboarding links each unit to your VAT account. ZATCA's documents describe the sequence:
- Generate an OTP on the Fatoora portal with your taxpayer account. ZATCA's portal manual notes that OTPs are short-lived, so generate it when you are ready.
- Create a key pair and a certificate signing request (CSR) in the solution, with your VAT number, unit serial number and branch details.
- Submit the CSR with the OTP to obtain a compliance CSID, a certificate that only lets the unit continue onboarding.
- Pass the compliance checks: the unit sends sample invoices and notes of the types it will issue, and ZATCA validates them.
- Request the production CSID. This is the certificate used to stamp invoices and call the clearance and reporting APIs.
Certificates expire. Renewal uses a new OTP and replaces the existing CSID, and the Fatoora portal lists each unit with its CSID status (active, expired or revoked).
Step 5: clearance or reporting, per invoice
| Standard tax invoice | Simplified tax invoice | |
|---|---|---|
| Typical buyer | Business or government (B2B, B2G) | Consumer (B2C), including POS |
| Model | Clearance | Reporting |
| Timing | Sent to ZATCA and cleared before sharing with the buyer | Reported within 24 hours of issue, before or after giving it to the buyer |
| What the buyer receives | The invoice as cleared by ZATCA | The invoice stamped by your unit, with its QR code |
Credit and debit notes follow the path of the invoice type they relate to. If an invoice is rejected, the response lists the errors; fix the data and issue it correctly rather than editing a stamped invoice.
Step 6: run it every day
- Watch for invoices that could not be sent during an outage and make sure they go out in order, so the chain stays intact.
- Review rejections and warnings, which usually point to master data such as a missing buyer address.
- Renew CSIDs before they expire, and onboard new branches or POS terminals as separate units when they start issuing.
- Keep your VAT return tied to the same invoices, so the ledger and ZATCA agree.
Common mistakes
- Treating Phase 2 as a printing change. It is an integration project; plan time for data clean-up and testing.
- One unit for everything. Branches with their own tax registration and separate POS terminals need their own units and chains.
- Breaking the chain. Deleting, renumbering or resending invoices out of order breaks the hash chain.
- Sending standard invoices before clearance. The buyer should receive the cleared version.
- Letting the certificate expire. Put the renewal date in your calendar.
How Aspirations handles Phase 2
In Aspirations, standard invoices go through clearance and simplified invoices, including POS receipts, are reported, with the signed XML stored with each invoice. Invoices carry the hash chain, counter, cryptographic stamp and TLV QR. Onboarding runs from inside the system: it generates the key and CSR, you enter the OTP from the Fatoora portal, and it obtains the compliance CSID, runs the compliance checks and then the production CSID, saving each step. When ZATCA answers that clearance is temporarily unavailable, the invoice is reported instead, as the platform allows. Pending Saudi invoices are resubmitted automatically in counter order, and data ZATCA requires is checked before an invoice number is used. The integration is tested on ZATCA's developer environment; ZATCA does not publish an approval we can claim, and each company completes its own onboarding (CSID). Groups that also sell in Jordan can run JoFotara for the Jordanian company on the same platform; see our JoFotara e-invoicing guide and the accounting software that consolidates both. Plans are being finalised, and a free trial is available.
This guide is general information. Technical requirements and wave dates are set by ZATCA; confirm them on zatca.gov.sa and in your own notification.
