Does ZATCA e-invoicing apply to UAE companies?

ZATCA rules apply to businesses resident or VAT-registered in Saudi Arabia. A UAE company with no Saudi presence is not subject to ZATCA, but a UAE-headquartered group with Saudi entities must comply with ZATCA for those entities, and separately with the UAE FTA mandate for its UAE entities.

What is the difference between ZATCA and the UAE FTA e-invoicing mandate?

ZATCA (Saudi Arabia) uses a centralised clearance model through the Fatoora platform with UBL-based XML and mandatory Arabic. The UAE FTA mandate uses a decentralised five-corner model based on PINT AE (Peppol), exchanged through an accredited service provider. They are separate regimes with different formats, channels, and timelines.

What does ZATCA Phase 2 (Integration) require?

Phase 2 requires integrating your e-invoicing system with ZATCA’s Fatoora platform via API. Invoices must be Arabic, machine-readable XML with an embedded PDF/A-3, a UUID, a cryptographic stamp, a QR code, and sequential numbering. Standard invoices are cleared before issue, simplified (B2C) invoices are reported within 24 hours.

Which businesses are in the current ZATCA waves?

ZATCA has rolled Phase 2 out in waves by VAT-able turnover, and the thresholds have fallen steadily. Later waves in 2026 bring in businesses above roughly SAR 375,000 in turnover, making integrated e-invoicing effectively universal for small and mid-size Saudi businesses. Each wave has its own integration deadline.

When does UAE e-invoicing become mandatory?

The UAE mandate phases in from a voluntary pilot open since 1 July 2026. Businesses with revenue of AED 50 million or more must appoint an accredited service provider by 30 October 2026, extended from 31 July 2026, and go live on 1 January 2027. Remaining VAT-registered businesses appoint by 31 March 2027 and go live on 1 July 2027, and government entities go live on 1 October 2027. Dates have shifted before, so confirm the current schedule with the FTA.

How should a finance team prepare for both?

Map each entity to its regime, structure and clean invoice master data now, select your Fatoora integration and UAE ASP early, and build e-invoicing status checks into month-end close. A continuous-close platform like Rivane keeps invoice data structured and reconciled year-round.

GCC E-INVOICING

ZATCA e-invoicing: what UAE finance teams need to know

ZATCA is Saudi Arabia’s e-invoicing regime, but it matters to plenty of UAE finance teams: groups headquartered in the UAE often run Saudi entities that fall squarely in scope. And the UAE has its own mandate arriving on a different model. Here is what applies, when, and how the two differ.

Keep invoicing compliant Compare the two regimes

2 regimesZATCA and the UAE FTA

PINT AEPeppol 5-corner model

Fatooraclearance in Saudi Arabia

WHO IS IN SCOPE

Does ZATCA apply to you?

ZATCA (the Zakat, Tax and Customs Authority) governs e-invoicing for businesses resident or VAT-registered in Saudi Arabia, through the Fatoora platform. If your organisation operates only in the UAE, ZATCA does not apply to you directly, the UAE Federal Tax Authority mandate does.

But the line is not the border. A UAE-headquartered group with Saudi subsidiaries, branches, or VAT registration must comply with ZATCA for those Saudi entities, and with the FTA mandate for its UAE entities. Multi-entity teams end up managing both at once, which is exactly where they diverge.

Arabic XMLEmbedded PDF/A-3UUIDCryptographic stampQR codeSequential numberingFatoora APIClearance modelPINT AEPeppol networkAccredited service provider5-corner exchangeArabic XMLEmbedded PDF/A-3UUIDCryptographic stampQR codeSequential numberingFatoora APIClearance modelPINT AEPeppol networkAccredited service provider5-corner exchange

ZATCA vs the UAE FTA mandate

Dimension

ZATCA, Saudi Arabia

UAE, Federal Tax Authority

Authority

ZATCA (Saudi Arabia)

Federal Tax Authority (UAE)

Model

Centralised clearance / CTC via Fatoora

Decentralised (DCTCE), 5-corner exchange

Format

UBL-based XML with embedded PDF/A-3

PINT AE (Peppol) structured XML

Channel

Direct API integration to Fatoora

Accredited Service Provider on the Peppol network

Language

Arabic mandatory (bilingual allowed)

Structured data exchanged via ASP

Invoice types

Standard (clearance) and Simplified (report within 24h)

B2B / B2G in scope, phased by segment

Status

Phase 2 waves live and ongoing through 2026 to 2027

Pilot from Jul 2026, large-business go-live Jan 2027

ACTION PLAN

What finance teams should do now

01
Confirm where you are in scope
Map every entity to its regime: KSA-resident entities fall under ZATCA, UAE entities fall under the FTA mandate. A UAE-headquartered group with Saudi subsidiaries is subject to both.
02
Structure your invoice data
Both regimes require machine-readable structured invoices, not PDFs. Clean master data, tax registration numbers, item and tax codes, and sequential numbering, so it maps to XML without rework.
03
Select service providers early
For the UAE you must appoint an accredited service provider (ASP), for KSA you integrate with Fatoora. Both have lead times, and the UAE sets ASP-appointment deadlines ahead of each go-live.
04
Wire e-invoicing into the close
Reconcile invoice sequences and clearance or exchange status as part of month-end so nothing is missing or rejected when you file VAT.

This guide is general information for finance teams, not tax or legal advice, and e-invoicing rules change frequently. Confirm current requirements, thresholds, and deadlines with ZATCA, the UAE FTA, or your advisor. Details current as of August 2026.

Frequently asked questions

Keep going

UAE Month-End Close Checklist

Where e-invoicing readiness fits in a full UAE close, step by step.

Tax management

VAT and corporate tax handled inside the ledger, not bolted on after.

Continuous reconciliation

Keep invoice data matched and sequenced all month, ready to file.

Stay compliant across every GCC entity

Rivane keeps invoice data structured, sequenced, and reconciled year-round, so ZATCA clearance and UAE e-invoicing are a by-product of the close, not a fire drill.

Request a demo