Dubai · Riyadh · Bahrain · Cairo · AmmanEN · AR

Guide · Saudi Arabia · ZATCA e-invoicingZATCA e-invoicing Phase 2: what your ERP has to do

The integration phase is arriving in waves, and by now most Saudi companies with meaningful revenue have a date. This is the practical version: what the regulation asks of the software, how to tell whether your ERP does it, and the order to do things in.

Updated 26 Sep 202610 min readSaudi Arabia
About this guide
Topic
e-Invoicing, ZATCA Phase 2
Country
Saudi Arabia
Updated
26 Sep 2026
Reading time
10 minutes

Facts checked against zatca.gov.sa; the schedule changes, so confirm your own wave.

Phase 1 and Phase 2, in one paragraph each

Phase 1, generation, applied to every VAT-registered business from 4 December 2021. It replaced handwritten and scanned invoices with electronic ones issued from a compliant system, with a QR code on simplified invoices and a set of mandatory fields. It did not connect anything to ZATCA.

Phase 2, integration, began on 1 January 2023 and is rolled out in waves. Each invoice is now generated in a standard XML format, chained to the previous one, stamped, and exchanged with ZATCA's FATOORA platform: standard invoices before they reach the customer, simplified invoices within a day. The taxpayer's solution has to be onboarded with a device certificate first.

Waves and deadlines

ZATCA groups taxpayers by the VAT-taxable revenue of a reference year and announces each wave at least six months before its integration date. The thresholds started at SAR 3 billion and have come down steadily; the most recently announced waves, as of September 2026, reach businesses with taxable revenue above SAR 375,000 in 2022, 2023 or 2024.

WaveRevenue threshold (VAT-taxable)Integration date
1Above SAR 3 billion (2021)1 January 2023
2Above SAR 500 million (2021)1 July 2023
3 to 8SAR 250 million down to SAR 40 millionOctober 2023 to March 2024
9 to 15SAR 30 million down to SAR 4 millionJune 2024 to March 2025
16 to 22SAR 3 million down to SAR 1 millionApril 2025 to December 2025
23Above SAR 750,000 (2022, 2023 or 2024)31 March 2026
24Above SAR 375,000 (2022, 2023 or 2024)30 June 2026
The trend is the message. Each wave roughly halves the threshold. A business that has not been named yet should assume it will be, and that six months is the time to onboard and test, with the system already chosen.

Clearance versus reporting

Phase 2 treats the two kinds of tax invoice differently, and the difference decides how your ERP must behave at the moment of issue.

Standard tax invoice (B2B, B2G)Simplified tax invoice (B2C)
ModelClearance: sent to FATOORA in real time, validated, stamped by ZATCA, then sharedReporting: stamped by your solution, shared with the customer, reported to FATOORA within 24 hours
Who stampsZATCAThe taxpayer's solution, with its production CSID
Customer copyThe cleared XML, or a PDF/A-3 with the XML embeddedPrinted or electronic, with the QR code
If FATOORA is downThe invoice cannot be cleared; the solution queues it and retriesThe invoice is issued; reporting is retried within the window

The XML and its fields

Every Phase 2 invoice is an XML document in the UBL 2.1 standard with ZATCA's Saudi extensions. The printed or PDF invoice is only a rendering of that XML. The fields that trip up systems built for paper are:

  • UUID: a universally unique identifier per invoice, in addition to the sequential invoice number.
  • Invoice counter: a per-solution counter that increments by one for every invoice, credit note and debit note, with no gaps.
  • Previous invoice hash: the hash of the last document issued by the same solution unit, which chains the sequence.
  • Invoice type code and subtype: standard or simplified, and flags for third-party, nominal, export, summary and self-billed invoices.
  • Seller and buyer details: VAT numbers, the national address with the short address, and the buyer's identification for standard invoices.
  • Line items: each with quantity, unit price, VAT category and rate, and the totals in SAR even when the invoice is in another currency.
  • Reference to the original on credit and debit notes, with the reason for the adjustment.

Hash chain, cryptographic stamp and QR code

Three mechanisms make an invoice tamper-evident. The hash is computed over the canonical XML and carried into the next invoice, so a missing or altered document breaks the chain. The cryptographic stamp is a digital signature over the hash, made with the private key that belongs to the solution's CSID; for simplified invoices your solution applies it, for standard invoices ZATCA does. The QR code encodes, in TLV base64, the seller name, VAT number, timestamp, total with VAT, VAT amount, the invoice hash, the stamp, the public key and, for simplified invoices, ZATCA's signature over the key. A phone app from ZATCA can scan it and confirm the invoice is genuine.

Practical consequence. Once an invoice is issued it cannot be edited or deleted, by anyone, in any screen. Corrections are credit and debit notes referencing the original. An ERP that lets an administrator "fix" a posted invoice is not compliant, however convenient.

Onboarding and CSIDs

Before the first live invoice, each solution unit (each server, branch device or instance that issues invoices) is registered on the FATOORA portal. The steps are the same for everyone:

  1. Log in to the FATOORA portal with the taxpayer's ZATCA credentials and generate a one-time password (OTP) for the unit.
  2. The solution generates a key pair and a certificate signing request with the unit's details, and submits it with the OTP. ZATCA returns a compliance CSID.
  3. The solution submits sample invoices, credit notes and debit notes (standard and simplified) for compliance checks.
  4. On success, the solution requests the production CSID, which is the certificate used to stamp and to authenticate against the live APIs.
  5. The production CSID is renewed before it expires, and revoked if the unit is retired or compromised.

What this means for the ERP

The regulation is written about invoices, but its weight falls on the software. In practice your ERP or e-invoicing layer needs to:

  • Generate the UBL 2.1 XML with every mandatory field, from data that already sits on the sales invoice: the customer's VAT number and national address, the VAT category per line, the SAR equivalents.
  • Keep the counter and the hash chain per solution unit, and never reuse or skip a number.
  • Hold the CSID keys securely, stamp simplified invoices, and call the clearance and reporting APIs with retries and a queue for outages.
  • Refuse edits and deletions after issue, and route corrections through credit and debit notes that reference the original.
  • Render the QR code on every simplified invoice and the cleared XML on every standard one, and archive both for the retention period.
  • Show the status of every invoice (cleared, reported, rejected, queued) to the finance team, with the reason when ZATCA rejects one.
How CorporateStack does it

e-Invoicing inside the Finance module, not beside it

Sales invoices in CorporateStack carry the ZATCA fields on the customer and on the line, generate the XML and the QR at posting, and clear or report through FATOORA with the invoice's status shown on the record. Corrections are credit and debit notes; nothing posted can be edited. The same module handles Egypt's ETA, so a group with companies in both countries runs one process.

INV-26-1194 · Riyadh branch · standard invoiceZATCA
✓XML generated · UBL 2.1 · counter 8,41214:02:11
✓Cleared by FATOORA · stamped14:02:13
✓PDF/A-3 with XML sent to the customer14:02:14
See the ERP Core page

Penalties

ZATCA's penalty schedule covers not issuing or archiving e-invoices, missing QR codes or mandatory fields, deleting or amending issued invoices, and failing to integrate by the wave date. Published amounts run from SAR 5,000 to SAR 50,000 per violation, escalating with repetition; ZATCA has generally issued a warning for a first offence and has run grace periods for late integrators. The schedule is the smaller cost; the real one is a customer who cannot deduct input VAT on your invoice.

An integration checklist

  1. Find your wave on the ZATCA portal and diarise the date; if unnamed, plan for the next threshold.
  2. Clean the master data: customer VAT numbers, national addresses, VAT categories on products, the SAR rate source.
  3. Confirm the ERP (or its e-invoicing layer) generates UBL 2.1, chains hashes, stamps and produces the QR; ask for the compliance test report.
  4. Decide the solution units: head office, branches, point-of-sale devices, each with its own CSID (the till side is in our POS guide).
  5. Onboard in the ZATCA sandbox, pass the compliance invoices, then obtain production CSIDs.
  6. Train the finance team on credit and debit notes as the only correction path.
  7. Go live on a quiet day, watch the clearance queue for a week, and archive the XML from day one.

Questions we are asked

How do I know which wave my company is in?

ZATCA notifies each taxpayer at least six months before its date, by the VAT-taxable revenue of a reference year. As of September 2026 the announced waves reach revenue above SAR 375,000. If you have not been notified, check the portal and your registered email, and prepare anyway.

Do I need a separate e-invoicing tool if my ERP is compliant?

No. A compliant ERP is an e-invoicing solution in ZATCA's terms. A separate tool makes sense only when the ERP cannot be changed; then the ERP posts the invoice and the tool generates, stamps and exchanges it, and the status has to flow back.

What happens when FATOORA is unreachable?

Standard invoices wait in a queue until they can be cleared; the customer receives them after clearance. Simplified invoices are issued immediately and reported when the connection returns, within the 24-hour window.

Can invoices be issued in USD or EUR?

Yes. The XML carries the invoice currency and the totals, and the VAT amounts are also expressed in SAR at the rate used on the invoice; the ERP has to store that rate on the document.

See ZATCA clearance on your own invoice

A consultant sets up a Saudi tenant, posts a sales invoice with your data, clears it in the ZATCA sandbox and shows the XML, the QR and the journal.

Book a demo