ZATCA E-Invoicing Phase 2 (Integration with Fatoora): The Complete Guide

9 min read · Updated

Phase 2 of Saudi e-invoicing, the Integration Phase, requires a business's system to send every e-invoice to ZATCA's Fatoora platform: a standard tax invoice between businesses is cleared by ZATCA before it reaches the buyer, and a simplified tax invoice to a consumer is reported within 24 hours of issue. It has applied since 1 January 2023 in waves, each notified at least six months ahead; Wave 25 covers businesses whose VAT-able revenue exceeded SAR 187,500.

How does Phase 2 differ from Phase 1?

Saudi e-invoicing came in two phases. Phase 1, Generation, became mandatory on 4 December 2021 for resident VAT taxpayers: invoices, credit notes and debit notes had to be issued and kept by a compliant electronic solution, not by hand or in word processors and spreadsheets, with a QR code on simplified invoices.

Phase 2, Integration, began on 1 January 2023 and adds one thing on top: the solution itself is connected to ZATCA's Fatoora platform, so every invoice reaches it in a set format, carrying a cryptographic stamp that proves where it came from. The invoice is no longer only a document you keep; ZATCA sees it as it is issued, or within hours.

So moving to Phase 2 is not a change to the printed invoice but to how invoicing works: registering the solution with ZATCA, signing every invoice, sending it, reading the platform's answer and fixing what is rejected. A business that treats this as a daily routine goes through it without its sales being held up.

Standard or simplified tax invoice: which one do you issue?

The regulations distinguish two kinds. A standard tax invoice is issued between businesses, when the buyer is a business, and carries the buyer's full details, including its VAT number if registered and its address. A simplified tax invoice is issued when selling to an individual consumer, as at the tills of shops and restaurants.

The difference matters: the kind decides how the invoice reaches ZATCA in Phase 2, which details it must hold, and whether a registered buyer can deduct its input VAT, which needs a tax invoice in its own name. A common slip is leaving the choice to the cashier at each sale, so a business that needs a standard invoice gets a simplified one.

  • Standard invoice: the buyer is a business, with its VAT number and national address; cleared by ZATCA before it is handed over.
  • Simplified invoice: the buyer is a consumer, with fewer buyer details; handed over at once and reported within 24 hours.
  • In practice: classify customers in the system (individual or business) so the invoice kind follows the customer.

Clearance and reporting: how does an invoice reach Fatoora?

Under clearance, the system sends the standard tax invoice to Fatoora before sharing it with the buyer; the platform checks its data and format and returns it stamped by ZATCA. A standard invoice is not valid until cleared and is not handed to the buyer before then.

Under reporting, the system issues the simplified invoice, hands it to the customer at once, and sends it to the platform within 24 hours of issue, before or after handing it over. This is what lets a till keep its pace without waiting on the platform at each sale.

The platform answers each invoice: accepted, accepted with warnings (details to fix in the invoices that follow), or rejected. A rejected invoice is not complete; its cause must be fixed and it must be sent again. ZATCA's guidelines describe what to do when the platform cannot be reached; read their latest edition before building your own procedure on them.

What are the technical requirements: the XML, the stamp and the QR code?

A Phase 2 e-invoice is an XML file following UBL 2.1 and ZATCA's published specifications, not an image or a plain PDF. It holds the seller and buyer, the lines, the tax per category and the totals, together with elements that stop tampering: a unique identifier (UUID) per invoice, an invoice counter, and the hash of the previous invoice, which chains invoices so that none can be removed unseen. It may be shared with the buyer as XML, or as a PDF/A-3 with the XML embedded.

The cryptographic stamp is a digital signature the solution makes for each invoice with a private key that never leaves your system, paired with a certificate ZATCA issues. It proves that the invoice came from this solution and has not changed since.

In Phase 1 the QR code held five elements: the seller's name, its VAT number, the invoice's date and time, the total with VAT and the VAT amount. Phase 2 adds the invoice hash, the digital signature and the public key, and on a simplified invoice ZATCA's signature over the certificate too, so the invoice can be checked by scanning it. The system makes and prints the QR on a simplified invoice; a standard invoice comes back from clearance carrying it.

What is a CSID and how is a solution onboarded?

Before the system sends any invoice, each unit that issues invoices, which ZATCA calls an e-invoice generation solution unit (EGS), is registered on Fatoora and given a cryptographic stamp identifier (CSID). It starts on the Fatoora portal, where the taxpayer generates a short-lived one-time password (OTP); the system then goes through these steps:

With several branches or tills, decide early whether each branch is its own unit or one central system issues every invoice: the counter and the hash chain belong to the unit, and mixing two units gets invoices rejected. Put certificate renewal in the system owner's calendar; an expired certificate stops sending.

  • The system makes a key pair and a certificate signing request (CSR) with the business's and the unit's details, and sends it with the OTP.
  • ZATCA issues a compliance CSID, with which the system runs the compliance checks: sample invoices and notes of every kind the unit will issue.
  • Once they pass, the system asks for the production CSID, which stamps and sends the real invoices.
  • Each certificate expires and is renewed in time; the private key is the solution's identity before ZATCA and is kept safe.

How are credit and debit notes handled in Phase 2?

A credit note lowers an earlier invoice's value, as for returns and later discounts; a debit note raises it. In Phase 2 both are e-documents exactly like the invoice: a stamped XML, cleared when it follows a standard invoice and reported when it follows a simplified one.

Each note must refer to the original invoice and its number and state why it was issued. An issued invoice is never edited or deleted; any correction after issue is a note that keeps the trail. A system that lets a posted invoice be changed or cancelled without a matching document does not fit Phase 2, however convenient it feels.

Credit notes flow into the VAT return's adjustments column, so their accuracy shows directly in the return; any return of goods recorded outside the system later appears as a gap between the return and the books.

What are the waves and when must your business integrate?

Phase 2 did not apply to everyone at once but in waves, starting on 1 January 2023 with the largest businesses, the revenue threshold falling with each wave. For each wave ZATCA sets a threshold of VAT-able revenue in given years and notifies the targeted taxpayers at least six months before the integration date.

Among the latest: Wave 24 covered taxpayers whose VAT-able revenue exceeded SAR 375,000 in 2022, 2023 or 2024, with an integration deadline of 30 June 2026. Wave 25, announced by ZATCA on 24 July 2026, covers those above SAR 187,500 in any year from 2022 to 2025, with a deadline of 1 February 2027.

Do not rely on these figures alone: ZATCA's notice to you, what the Fatoora portal shows for your business, and ZATCA's official announcements of later waves are the reference. If you are not in an announced wave yet, preparing early costs less than integrating in a rush weeks before the date.

A readiness checklist for Fatoora integration

Most of the work is clean data and set procedures, not only technology. Start this list at least three months before your date and share it between the accountant, the system owner and the sales manager:

After integration, make checking the sending status part of the daily close, just like the cash count: an invoice not yet accepted is not finished.

  • Confirm your wave's date on the Fatoora portal and in ZATCA's notice.
  • Make sure your system really supports Phase 2: clearance, reporting, stamping and notes, not just printing a QR code.
  • Complete the business's details: VAT number, commercial registration, and the national address with building number, street, district, city and postal code.
  • Classify customers as individuals or businesses, and complete the businesses' VAT numbers and national addresses.
  • Review items and their tax categories: standard, zero-rated or exempt, with the reason for exemption or zero rating.
  • List the issuing units, branches and tills, and onboard each one with its certificates.
  • Run the compliance checks and try every document kind: standard, simplified, credit note and debit note.
  • Name someone to follow rejected invoices and those accepted with warnings every day, and fix them.

How does Arkan handle Phase 2?

Arkan is an Arabic cloud ERP built on ERPNext, and e-invoicing is part of its sales cycle, so invoices never move to another program. An activation wizard takes you through it: checking the company's and branches' data, entering the Fatoora OTP to get the certificate, running the compliance checks with temporary invoices that leave nothing in the accounts or the return, then linking to production.

Invoices are sent as they are approved, or in batches; each one shows its status and ZATCA's answer, with an errors and warnings report that suggests the fix, and a rejected invoice is resent once corrected. Each branch may have its own unit and address, and invoices print on A4 or thermal paper with the QR code. The VAT number and national address are asked when a business customer is made, so the right invoice kind follows from the customer, and each unit's private key is kept encrypted in the database.

What is sent to ZATCA feeds the VAT return in the same system, so invoicing and the return read the same data.

Common questions

Is printing a QR code enough for Phase 2?

No. The QR code was a Phase 1 requirement. Phase 2 needs the system connected to Fatoora, stamping every invoice and sending it for clearance or reporting.

Must I wait for ZATCA before handing over the invoice?

For a standard invoice, yes: it is not valid until cleared. For a simplified invoice, no: it is handed over at once and reported within 24 hours of issue.

How do I find my wave's date?

ZATCA notifies targeted taxpayers at least six months ahead, and it shows on the Fatoora portal. The official wave announcements are on zatca.gov.sa.

What do I do when an invoice is rejected?

Read the reason in the platform's answer, fix the data (most often the buyer's address or VAT number, or the tax amounts), then send it again. Never hand a rejected standard invoice to the buyer.

Can an invoice be cancelled after it is sent?

It is never deleted. A credit note referring to it and stating the reason is issued and sent to ZATCA as the invoice was.