ZATCA & Compliance

ZATCA Phase 2 e-invoicing: a practical setup guide for Zoho Books users

CSID generation, invoice clearance and reporting, step by step.

Axiora team · 20 November 2026 · 3 min read

ZATCA's e-invoicing programme (FATOORA) was introduced in two phases. Phase 1, the generation phase, required businesses to issue invoices electronically from a compliant system. Phase 2, the integration phase, goes further: your invoicing system must connect directly to ZATCA's FATOORA platform, so that invoices are cleared or reported electronically as they are issued.

Businesses are brought into Phase 2 in waves, and ZATCA notifies each taxpayer of its integration date in advance, usually around six months ahead. Zoho Books supports Phase 2 integration, but a smooth go-live depends on preparation done well before that date.

What changes in Phase 2

  • Every invoice and note carries a cryptographic stamp, a QR code and a unique identifier generated by your system.
  • Standard tax invoices (B2B) must be sent to ZATCA and cleared before you share them with the customer.
  • Simplified tax invoices (B2C) are shared immediately and reported to ZATCA within 24 hours.
  • Each invoicing unit, such as a branch or a separate device, must be onboarded with its own certificate.

Before you start: get your data right

Most Phase 2 problems are data problems, not technical ones. Before switching anything on, check the following.

  • Your integration date, from the notification ZATCA sent you.
  • Your VAT registration number, legal name in Arabic and English, and national address in Zoho Books match your ZATCA records exactly.
  • B2B customer records hold the customer's VAT number, legal name and full national address, including building number and postal code.
  • Item and tax settings are correct: standard, zero-rated and exempt supplies each use the right tax code.
  • Invoice templates show the mandatory fields in Arabic, and English where you use both.
  • You have agreed who owns the FATOORA portal login and who will handle rejected invoices.

The setup, step by step

  1. Log in to the FATOORA portal and generate a one-time password (OTP) for each invoicing unit you are onboarding.
  2. In Zoho Books, open the ZATCA settings and enter the OTP to request a compliance CSID (Cryptographic Stamp Identifier) for that unit.
  3. Run the compliance checks. Zoho Books sends sample documents for each type you will issue: standard and simplified invoices, credit notes and debit notes.
  4. When all checks pass, request the production CSID. From this point, invoices are integrated with ZATCA.
  5. Issue a few real invoices of each type, and confirm that they are cleared or reported successfully before you announce go-live to your team.

How invoices behave after go-live

For B2B sales, an invoice is sent to ZATCA for clearance as you issue it. Only a cleared invoice should be shared with the customer. If ZATCA rejects it, the reason is shown, and you correct the data and issue it again. For B2C sales, the simplified invoice is printed or shared at once and reported to ZATCA in the background within 24 hours.

Credit and debit notes follow the same route as the invoice they relate to and must reference it. Once an invoice is cleared, it cannot be edited; any correction is made through a note.

Common problems and how to avoid them

  • Rejections caused by missing or incorrect customer VAT numbers or addresses. Clean customer data before go-live and make the fields mandatory for B2B customers.
  • Invoices edited after clearance. Train the team to issue credit notes instead, and restrict edit rights.
  • Branches or devices that were never onboarded. List every place invoices are issued from and onboard each one.
  • Certificates that expire unnoticed. Put the renewal date in the calendar of a named person.
  • Rejected invoices that nobody follows up. Assign one person to check the e-invoicing status daily in the first weeks.

A practical timeline

  • Three to six months before your date: review customer data, tax settings and invoice templates.
  • Six to eight weeks before: onboard units in a test setup, run compliance checks and train the team.
  • Go-live week: switch to production, issue test invoices of each type, monitor every rejection.
  • First month: review the e-invoicing status daily, then weekly once it runs cleanly.

ZATCA updates its requirements and technical guidelines from time to time. Always check the latest guidance on ZATCA's website before your integration date.

Want this working in your business?

Book a free 30-minute call and we will show you how it applies to your setup.

Chat on WhatsApp