Compliance guide

ZATCA Phase 2 e-invoicing requirements

Who must integrate and when, and exactly what your system has to do before the date.

What is ZATCA Phase 2?

Phase 2 of e-invoicing in Saudi Arabia, known as the Integration Phase, requires a business's invoicing system to connect directly to ZATCA's Fatoora platform, and to issue invoices in a specific format carrying elements the customer doesn't see: a unique identifier, a cryptographic stamp and a hash linked to the previous invoice. Phase 1 began on 4 December 2021. Phase 2 began on 1 January 2023 and applies to successive waves of taxpayers, which ZATCA notifies in advance.

Phase 1 versus Phase 2

Phase 1 required businesses to stop using paper and manual invoices, and to generate and store them in an electronic system. Phase 2 adds the other party: ZATCA itself. The system must now talk to Fatoora and prove an invoice hasn't changed since it was issued.

Phase 1: generation and storagePhase 2: integration
Start date4 December 20211 January 2023, in waves
What it requiresGenerate and store invoices electronicallyAll of that, plus a direct connection to Fatoora
Invoice formatNo single technical formatA specific XML format, or PDF/A-3 with embedded XML
Technical elementsQR code on simplified invoicesUnique ID, counter, chained hash, cryptographic stamp and QR code
Who checks the invoiceThe businessZATCA, by clearance before issue or reporting after it

Both start dates and the integration requirement are published on ZATCA's website.

Who must comply, and what's out of scope

ZATCA says e-invoicing applies to all persons subject to VAT and to anyone issuing tax invoices on their behalf. It excludes non-resident taxable persons.

CaseIs an e-invoice required?
Exempt suppliesNo
Import of goodsNo
Supplies under the reverse chargeNo
A transaction entirely not subject to VATNo tax invoice is needed
One invoice covering taxable and exempt suppliesYes, and tax invoice requirements apply
Non-resident taxable personExcluded
The exclusion applies to the transaction, not the whole business. A taxable business selling an exempt supply still has to e-invoice its other sales. If not-subject invoices come from the same system, ZATCA warns against gaps in the counter and hash sequence.

Source: ZATCA's e-invoicing FAQ and Detailed Guidelines.

Do you have to integrate now? Waves and dates

Not every business is required to integrate at once. ZATCA sets successive waves by revenue subject to VAT, and notifies each wave of its date. Wave 25 is the next one, and its threshold is half that of the wave before it.

Latest waves
Wave 25
1 February 2027
Revenue above SAR 187,500 in any year from 2022 to 2025
Wave 24
30 June 2026
Revenue above SAR 375,000. This date has passed
Wave 23
31 March 2026
Revenue above SAR 750,000. This date has passed
Read the test carefully. It's exceeding the threshold in any one reference year, not the latest. One high year in 2023 is enough to bring a business into a wave, even if revenue fell afterwards.

ZATCA notifies each wave's businesses directly at least six months before their date. Not having a notice doesn't necessarily put you out of scope, so check your account with ZATCA.

Wave 25 is from ZATCA's notice. Waves 23 and 24 are from matching published consolidations. For the full list and a checker, see ZATCA integration waves. Confirm your wave with ZATCA or on 19993 before planning around it.

Tax invoices and simplified invoices: clearance versus reporting

The two invoice types aren't treated the same way. A tax invoice goes to ZATCA before it reaches the customer. A simplified invoice goes to the customer immediately and is reported afterwards.

Tax invoiceSimplified tax invoice
Typical useTo a business or government bodyTo an individual consumer
ProcessClearance: sent to ZATCA and cleared before deliveryReporting: given to the customer, then sent to ZATCA
TimingBefore the invoice is issued to the customerWithin 24 hours of issue
If the connection dropsThe invoice can't complete until it returnsThe invoice is issued and reported once it returns
This has a real operational effect: a point of sale serving individuals can keep going during an outage, while a department invoicing businesses stops. Factor that into your choice of system and your contingency plan.

The invoice types are defined on ZATCA's website. Clearance, reporting and the 24-hour window come from the published Phase 2 specifications.

What the invoice file must contain

A Phase 2 invoice is a structured file, not an image or a text document. These are the elements an accountant or technical reviewer usually asks about:

  • Format: XML under UBL 2.1, or PDF/A-3 with embedded XML.
  • UUID: a unique identifier for each invoice, separate from your sequential invoice number.
  • Counter: a sequential counter that can't be reset, showing no invoices were deleted.
  • Hash: a digital fingerprint of the invoice that includes the previous invoice's fingerprint, forming a chain that breaks if an old invoice is changed or deleted.
  • Cryptographic stamp: a digital signature made with a certificate ZATCA issues to the issuing unit at onboarding.
  • QR code: on simplified invoices, with Phase 2 content.
A common mistake: re-sending a signed XML file is fine, but regenerating the invoice creates a new identifier, counter and hash, so ZATCA sees two invoices instead of one. Treat the signed file as the document, not as output you can produce again.

These elements are based on ZATCA's published e-invoice specifications and security requirements. Review them with your technical team before implementing.

Steps to integrate with Fatoora

Integration is a technical process done once per issuing unit, after which invoicing runs automatically. The general sequence is:

  1. Confirm your system supports Phase 2Generating an electronic invoice isn't enough. It must produce a certificate request, sign invoices and connect to ZATCA's APIs.
  2. List your issuing unitsCount every device, branch or point of sale that issues invoices, because each needs its own certificate.
  3. Generate the certificate signing request (CSR)The system creates it, not you, carrying the business and issuing-unit details.
  4. Request a one-time password (OTP) in FatooraFrom the business's ZATCA account. The code links the request to the business.
  5. Enter the code to receive the certificate (CSID)The system can then apply a recognised stamp to invoices.
  6. Test in the simulation environment firstIssue tax invoices, simplified invoices, and credit and debit notes, and confirm they're accepted before going live.
Start well before your date. What delays businesses most is usually not integration itself but what testing reveals: incomplete customer data, wrong VAT numbers, and items without a correct tax rate.

Each step has more detail, including certificate fields and compliance checks, in our Fatoora onboarding guide. If an invoice is rejected, see ZATCA error codes.

Is there "ZATCA-approved" software?

You'll see "ZATCA-approved software" in many ads. The phrase isn't accurate, and ZATCA's own wording is clearer.

ZATCA says a taxpayer can get invoicing services from any company offering electronic systems, provided the system meets the requirements, and that it considers the taxpayer compliant even if the provider isn't on its list. It describes that list as indicative: it contains providers who voluntarily passed qualification, and isn't exclusive.

  • Compliance belongs to the business and its invoices, not to a stamp given to a product.
  • A provider being on the indicative list is a useful sign, not a legal condition.
  • Responsibility stays with the business: if its invoices don't meet the requirements, the provider's name doesn't protect it.
That's why we describe our system as compliant with Phase 2 requirements, and not as "approved". The first describes what the system does. The second claims an approval ZATCA doesn't give.

ZATCA's text on providers and the indicative list is on its e-invoicing page. We cover it in detail in our guide, in Arabic.

What happens if you don't comply?

E-invoicing violations vary by type: not issuing or storing, a missing QR code on a simplified invoice, deleting or changing an issued invoice, or not integrating. Fines escalate if a violation repeats within a set period.

According to ZATCA's simplified guideline on classifying general VAT violations (2nd edition, May 2024), every violation starts with a warning and 30 to 60 days to correct it, not a fine. If it repeats, the fine climbs with each repeat:

  • Not integrating with ZATCA's systems: from SAR 10,000 up to SAR 50,000 after the sixth time.
  • Not issuing or sharing on time, or deleting or changing an issued invoice: from SAR 5,000 up to SAR 40,000.
  • A missing QR code, missing fields, or not storing invoices: from SAR 1,000 up to SAR 40,000.
A violation counts as repeated if 12 months haven't passed since it was last found. The full table, with each violation and its cycle, and what the fines initiative does and doesn't cover, is in our penalties guide, in Arabic, sourced to ZATCA's guideline.

A quick readiness check

  • Does your system generate UBL 2.1 XML, or only an image or plain PDF?
  • Does it sign invoices with a ZATCA certificate, or just print a QR code?
  • Have you listed every issuing unit, including branches, points of sale and side systems?
  • Are your business customers' VAT numbers complete and correct?
  • Does every item have the right tax rate, and are exempt items really classified that way?
  • Have you tried issuing a credit note and a debit note, not just a sales invoice?
  • What's your plan when the connection drops during a tax invoice?

How emerge handles this

The emerge accounting system issues Phase 2 invoices from inside the system: signed XML, a QR code, clearance for tax invoices, reporting for simplified ones, and credit and debit notes. Issued invoices and recorded payments post balanced entries in the same books, so tax compliance doesn't sit apart from accounting.

See the accounting system

Common questions

Is e-invoicing mandatory for all businesses in Saudi Arabia?

It applies to all persons subject to VAT and anyone issuing invoices on their behalf, and excludes non-resident taxable persons. An e-invoice isn't required for exempt supplies, imports of goods, or supplies under the reverse charge.

What are the phases of ZATCA e-invoicing?

Two: Phase 1, generation and storage, began on 4 December 2021. Phase 2, integration, began on 1 January 2023 and requires connecting to Fatoora and issuing invoices in a specific format. Phase 2 applies to successive waves by revenue.

What is the difference between clearance and reporting?

Clearance is for tax invoices, which are sent to ZATCA and cleared before reaching the customer. Reporting is for simplified invoices, which go to the customer immediately and are sent to ZATCA within 24 hours.

Do I have to use ZATCA-approved software?

No. ZATCA says a taxpayer can use any company's system that meets the requirements, and considers the taxpayer compliant even if the provider isn't on its list. That list is indicative, not exclusive.

Want to put this into practice in your business? Try it yourself, or ask us on WhatsApp.

Note

This guide is general information, not tax or legal advice. Regulations and deadlines change, and the final reference is what the Zakat, Tax and Customs Authority publishes. Check with your tax adviser before acting on it.