ZATCA Phase 2, wave 25: integrate by 1 February 2027

Connect your invoicing to ZATCA before 1 February 2027

For businesses in Saudi Arabia whose revenue subject to VAT exceeded SAR 187,500 in any year from 2022 to 2025. We connect the system you already invoice from, whether an ERP, a POS, an accounting package or custom software, to ZATCA's Fatoora platform, and quote a fixed price for the scope we agree with you.Get a fixed quote WhatsApp us (opens in a new tab)

Are you in wave 25?

Check your revenue against SAR 187,500

ZATCA announced wave 25 of Phase 2 (integration) on 24 July 2026. It covers taxpayers whose revenue subject to VAT exceeded SAR 187,500 in any one of 2022, 2023, 2024 or 2025. They must integrate their e-invoicing solution with Fatoora by 1 February 2027.

One year above the threshold is enough. Wave 24, the wave before, covered revenue above SAR 375,000 and closed on 30 June 2026. ZATCA notifies the taxpayers it selects for a wave at least six months before their deadline.

A quick self-check

  • You are registered for VAT in Saudi Arabia.
  • Your revenue subject to VAT was above SAR 187,500 in at least one of 2022, 2023, 2024 or 2025.
  • You have not yet integrated your invoicing with Fatoora.

If all three apply, plan for 1 February 2027 and look for ZATCA's notification in your taxpayer account.

You have been notified

Note the deadline in the notification, list every system and device that issues your invoices, and start planning onboarding now. Each POS terminal or billing server is onboarded separately.

You qualify but have no notice

Check your account and messages on the ZATCA portal, and confirm with your tax adviser. Starting the technical work early does no harm: it is the same work whichever wave you are in.

You are below the threshold

You are not in wave 25, but the Phase 1 (generation) rules still apply to your invoices, and each wave so far has lowered the threshold. Building on a structured invoice now makes a later wave easier.

This summarises ZATCA's public announcement and is not tax advice. Your ZATCA notification and your tax adviser decide whether and when you must integrate.

What integration involves

From onboarding to cleared invoices

Every e-invoice generation solution (EGS) unit, such as a POS terminal or a billing server, goes through the same ZATCA steps before it can issue live invoices.

01
Onboarding
Request an OTP

Generate a one-time password in the Fatoora portal for each EGS unit you will onboard.

02
Onboarding
Get a Compliance CSID

Generate a key pair and a certificate signing request, and exchange it with the OTP for a Compliance CSID (cryptographic stamp identifier).

03
Testing
Pass the compliance checks

Submit sample invoices of every type the unit will issue, including credit and debit notes, and have ZATCA validate them.

04
Go-live
Receive the Production CSID

ZATCA issues the production certificate that lets the unit use the live e-invoicing APIs.

05
Every day
Clear and report invoices

Standard (B2B) invoices are cleared by ZATCA before the buyer receives them. Simplified (B2C) invoices are issued at once and reported within 24 hours.

What ApexlyTech does

The technical work, end to end

You keep your tax adviser for the tax questions. We build and run the integration: certificates, invoice data, the signed XML, and the connection to Fatoora.

Onboarding and CSIDs

We generate keys and certificate signing requests for each EGS unit, obtain the Compliance and Production CSIDs, keep private keys out of source code and logs, and track certificate expiry.

Invoice mapping

We map invoices, credit notes and debit notes from your ERP, POS or accounting system to ZATCA's fields and code lists, including VAT categories, discounts and rounding.

XML, stamp and QR code

Each invoice is generated as UBL-based XML, signed with an ECDSA cryptographic stamp, chained to the previous invoice hash, and given its QR code in TLV format, Base64 encoded.

Clearance and reporting

Standard invoices are sent for clearance before they reach the buyer. Simplified invoices are queued and reported within 24 hours, with retries when Fatoora is slow or unavailable.

Sandbox testing

We run every invoice type and rejection case through ZATCA's SDK and sandbox before any unit is onboarded to production.

Go-live and monitoring

We onboard the production units with you, then watch rejections, the submission queue and certificate renewals, so problems surface before month end.

Works with your existing system

Keep the software your team already uses

Phase 2 adds a signed XML invoice, a QR code and a connection to Fatoora to the system that issues your invoices. That rarely means replacing it.

For the technical detail, read our developer guide to ZATCA Phase 2.

  • ERP systems

    We connect the ERP you run today, or build the integration into Apex ERP if you are moving to it.

  • POS and retail

    Each terminal is its own EGS unit with its own CSID, counter and hash chain. We plan for offline periods so simplified invoices still reach ZATCA within 24 hours.

  • Accounting and billing software

    Where your package offers an API or an export, we connect it to Fatoora through a small integration service.

  • Custom and Laravel applications

    For Laravel stacks, our open-source laravel-zatca package handles XML generation and cryptographic stamping. We can build on it, or on whichever library suits your stack.

Timeline

From now to 1 February 2027

The deadline is fixed; how long each phase takes depends on how many systems and devices issue your invoices and how clean your invoice data is. We agree dates with you after the assessment rather than promise them here. Starting early leaves time to fix rejections before the deadline.

  1. 1
    Now

    Assess

    Confirm your wave, list every system and device that issues invoices, and agree the scope and a fixed quote.

  2. 2
    Next

    Build

    Map your invoice data and add the XML, stamp, QR code and the clearance and reporting queue to your system.

  3. 3
    Before go-live

    Test

    Run every invoice type through ZATCA's SDK and sandbox, then pass the compliance checks for each unit.

  4. 4
    Ahead of the deadline

    Go live

    Obtain the Production CSIDs, switch each unit to the live APIs and brief the staff who issue invoices.

  5. 5
    From 1 February 2027

    Operate

    Every invoice is cleared or reported. We monitor rejections, the queue and certificate renewals.

Get a fixed quote

Tell us how you invoice today

Send the form and we will reply by email with our questions or a fixed quote for the scope we agree.

What to include

Which systems issue your invoices (ERP, POS, accounting or custom), how many branches, terminals or servers issue them, roughly how many invoices you issue a month, and whether ZATCA has notified you. Any project type in the form is fine: requests sent from this page reach us marked as ZATCA e-invoicing integration.

Drag and drop your file here
or click to browse. PDF, Word, image or ZIP, up to 10 MB.
By submitting, you agree to our Privacy Policy.
FAQ

ZATCA e-invoicing questions

Something else? Ask us, or read our developer guide to ZATCA Phase 2.

It applies to taxpayers whose revenue subject to VAT exceeded SAR 187,500 in any of 2022, 2023, 2024 or 2025. ZATCA notifies the taxpayers it selects at least six months before their deadline, so check your ZATCA account and confirm with your tax adviser.
1 February 2027. ZATCA announced the wave on 24 July 2026. The wave before it, wave 24, covered revenue above SAR 375,000 and had a deadline of 30 June 2026.
Standard tax invoices (business to business) are cleared: your system sends each one to Fatoora, which validates and stamps it, and only then is it shared with the buyer. Simplified tax invoices (mostly business to consumer) are given to the customer at once and reported to ZATCA within 24 hours.
A CSID (cryptographic stamp identifier) is the certificate an e-invoice generation solution (EGS) unit uses to stamp its invoices. Each unit, such as a POS terminal or a billing server, first gets a Compliance CSID for testing and then a Production CSID for live invoicing, so a business with several tills or servers needs one for each.
Not necessarily. Integration adds XML generation, the cryptographic stamp, the QR code and the connection to Fatoora to the system you already use. If a system cannot be extended, we discuss the options with you, including Apex ERP, before we quote.
Yes. laravel-zatca is our open-source, MIT-licensed package for Laravel applications, covering XML generation and cryptographic stamping. Your team still owns onboarding each unit, mapping your data, the submission queue and testing against ZATCA's SDK and sandbox. We can help with those parts or do the whole integration.
The scope we agree with you in writing after reviewing your setup: which systems and units are integrated, which invoice types are covered, and the testing and go-live support included. Send the form on this page and we will reply with our questions or a quote.
No. We handle the technical integration. Confirm your obligations, your wave and the tax treatment of your invoices with your tax adviser and with ZATCA.

Get ready for 1 February 2027

Tell us which systems issue your invoices and we will reply with a fixed quote for connecting them to ZATCA Fatoora.

Get a fixed quote