UAE FTA vs Saudi ZATCA — e-invoicing comparison
UAE e-invoicing vs ZATCA compared: 5-corner Peppol model, PINT AE format, deadlines, penalties, and what Saudi-ready teams must rebuild. See the breakdown.
What is UAE e-invoicing vs ZATCA?
UAE e-invoicing vs ZATCA is the comparison between two GCC tax mandates: the UAE's 5-corner Peppol DCTCE model under the Federal Tax Authority (FTA) and Ministry of Finance (MoF), and Saudi Arabia's 2-stage ZATCA Fatoora system. Both digitise B2B invoicing, but they use different formats, clearance flows, and deadlines.
If your group operates in both Riyadh and Dubai, you cannot reuse a ZATCA integration for the UAE. The transport layer, the data format, and even the trigger event are different. This page breaks down every meaningful difference so finance, tax, and IT teams can plan one program instead of two disconnected projects.
The headline differences in one table
Most teams expect the UAE to copy ZATCA. It does not. Saudi Arabia built a centralised clearance platform. The UAE picked the decentralised Peppol network used across Europe and Australia. That single architectural choice cascades into every other decision.
| Dimension | UAE (FTA / MoF) | Saudi Arabia (ZATCA) |
|---|---|---|
| Model | 5-corner DCTCE (Decentralized Continuous Transaction Control and Exchange) | 2-stage centralised clearance (Fatoora platform) |
| Network | Peppol, via Accredited Service Providers (ASPs) | Direct integration with ZATCA Fatoora |
| Format | PINT AE (Peppol International Invoice, UAE specialisation), UBL 2.1 XML | ZATCA-specific XML, UBL 2.1 with KSA extensions |
| Clearance trigger | Invoice exchanged via Peppol, reported to FTA tax data domain (TDD) in near real time | Invoice cleared by ZATCA before delivery to buyer (B2B Phase 2) |
| QR code on invoice | Not the core mechanism, transport is XML over Peppol | Mandatory cryptographic QR code on every invoice |
| E-signature | Not required at invoice level, signed at transport layer by ASP | Cryptographic stamp required (Phase 2) |
| Identifier | Tax Registration Number (TRN) plus Peppol participant ID | VAT number plus device cryptographic ID |
| Phase 1 mandatory go-live | January 1, 2027 (AED 50M+ turnover) | December 4, 2021 (generation), January 1, 2023 (integration) |
| SME mandate | July 1, 2027 (under AED 50M) | Rolled out in waves by revenue band, mostly complete |
| Penalty range | AED 2,500 to AED 50,000 per invoice (Cabinet Decision 106 of 2025) | SAR 1,000 to SAR 40,000 per violation, escalating |
Architecture: decentralised vs centralised
This is the difference that drives everything else.
ZATCA: centralised clearance
In Saudi Arabia, your ERP or billing system talks to ZATCA's Fatoora platform directly. The invoice is generated, cryptographically stamped, and sent to ZATCA for clearance. ZATCA returns a cleared XML with a QR code. Only then can you share the invoice with the buyer. ZATCA sees every B2B invoice the moment it is issued.
The buyer receives the invoice however you choose to send it: email, portal, PDF print, the network does not care. ZATCA is the single hub.
UAE: 5-corner Peppol exchange
The UAE uses the Peppol network. Your ERP sends a PINT AE invoice to your appointed ASP (corner 2). Your ASP transmits it over Peppol to the buyer's ASP (corner 3), which delivers it to the buyer's ERP (corner 4). Both ASPs report the tax-relevant data to the FTA's tax data domain (corner 5) in near real time.
There are 32 pre-approved accredited service providers in the UAE. You pick one for sending and receiving. Your supplier picks theirs. They do not need to be the same provider. For a deeper walkthrough, see the Peppol 5 corner model UAE explainer.
Format: ZATCA XML vs PINT AE
Both use UBL 2.1 as the underlying syntax. That is where the similarity stops.
ZATCA defined its own XML extensions, mandatory fields, and cryptographic stamp envelope. The schema is published by ZATCA and updated through their technical bulletins. Validation rules are bespoke to KSA.
The UAE chose Peppol PINT AE format, a UAE specialisation of the global PINT (Peppol International) billing profile. That means UAE invoices are syntactically compatible with the rest of the Peppol network, with a country-specific business rule layer for VAT codes, TRN handling, and free-zone scenarios.
Practical impact: a Saudi ZATCA mapper cannot be reused for the UAE. The field structure, mandatory codes, and validation rules are different. You will rebuild the mapping. Your ERP integration partner needs to understand both.
What both formats share
- UBL 2.1 syntax as the base
- Buyer and seller tax identifiers as mandatory
- Line-level VAT category codes
- Structured currency, payment terms, and reference fields
- Support for credit notes and debit notes
Where they diverge
- ZATCA requires a cryptographic stamp on the document itself, the UAE does not
- ZATCA mandates a TLV-encoded QR code, the UAE invoice flow does not
- PINT AE uses Peppol participant identifiers for routing, ZATCA uses VAT numbers
- Free-zone and designated-zone handling exists only in the UAE rules
- Reverse charge codes differ in granularity
Timeline: where each country sits in 2026
Saudi Arabia is years ahead operationally. ZATCA Phase 1 (generation) went live December 4, 2021. Phase 2 (integration with Fatoora) started rolling out January 1, 2023, by revenue waves. By 2026, most KSA taxpayers are already integrated.
The UAE is still pre-mandate. Key dates from Ministerial Decisions 243, 244, and 64 of 2025:
- Q2 2026: Pilot opens with selected ASPs and large taxpayers
- October 30, 2026: Deadline for AED 50M+ turnover entities to appoint an ASP (extended by MD 244 amendment)
- January 1, 2027: Mandatory go-live for Phase 1 (AED 50M+ turnover)
- July 1, 2027: Mandatory go-live for SMEs under AED 50M
- October 1, 2027: Government entities go live
For the full sequence and what to do in each quarter, read the UAE e-invoicing timeline guide.
Penalties: how each regime punishes non-compliance
Both regimes treat e-invoicing as a tax compliance obligation. Both fine per invoice. The structure differs.
ZATCA penalties
ZATCA penalties follow a tiered escalation: warning, then SAR 1,000, SAR 5,000, SAR 10,000, up to SAR 40,000 per violation. Categories include failure to issue an electronic invoice, missing QR code, missing cryptographic stamp, and failure to archive. Repeat violations escalate fast.
UAE penalties
Cabinet Decision 106 of 2025 sets the penalty range at AED 2,500 to AED 50,000 per invoice. The triggers include failure to issue a compliant e-invoice, failure to transmit through an ASP, missing or incorrect data, and failure to report to the FTA tax data domain. The schedule is detailed on the UAE e-invoicing penalties page.
For a high-revenue exporter issuing 5,000 invoices a month, the worst-case exposure runs into millions of AED per quarter. This is not a fine you absorb, it is one you prevent at the system level.
What changes for finance teams running both regimes
If your group already complies with ZATCA, you have institutional knowledge: tax mapping, master data discipline, e-invoicing project governance. None of the technical artefacts transfer cleanly. Here is what does and does not carry over.
Transferable
- Master data hygiene: customer TRN/VAT capture, item tax codes, address completeness
- Process discipline: invoice approval workflows, credit note controls, period close timing
- Change management muscle: training sales ops, AR teams, and IT on a new invoice lifecycle
- Vendor evaluation experience: you know what questions to ask an ASP
Not transferable
- The ZATCA XML mapper and cryptographic stamping module
- The QR code generator
- The direct API integration to Fatoora
- KSA-specific VAT category logic, especially around designated zones
You will need a new ERP integration project for the UAE. Whether that is a thin connector to a Peppol ASP or a deeper rebuild depends on your stack. See the e invoicing ERP integration UAE guide for the patterns by platform.
Buyer-side handling: a major UAE difference
Under ZATCA, the buyer's obligation is light. They receive whatever the seller sends, by email or portal. Phase 2 introduces buyer-side validation in scope over time, but the seller carries the clearance burden.
Under the UAE 5-corner model, both parties are inside the network. Buyers must be reachable through a registered Peppol participant ID, served by their own ASP. That means buyers also need to appoint an ASP, configure inbound processing, and handle structured invoices in their AP system. Free-zone entities, government bodies, and SMEs are all caught by this.
The practical implication: in the UAE you cannot just send a PDF and call it done. PDFs are not valid e-invoices under the mandate, as explained in the is PDF invoice valid UAE breakdown.
Cross-border invoicing between KSA and UAE
This is where it gets interesting. A UAE supplier invoicing a Saudi buyer is issuing a cross-border B2B invoice. Today that is a paper or PDF flow with VAT treatment based on the GCC framework agreement and bilateral arrangements.
Once UAE mandatory go-live hits in January 2027, UAE suppliers must still issue a PINT AE invoice and report it to the FTA, even though the Saudi buyer is on Fatoora. The Saudi buyer's AP team receives the document by whatever channel works. There is no GCC-wide e-invoicing interconnect yet.
The reverse flow, a Saudi supplier to a UAE buyer, will require the UAE buyer's ASP to receive and process the inbound. Reconciliation logic on both sides will need to handle two different formats. See cross border e-invoicing UAE for the operating model.
Which model is better? The wrong question
Tax administrations pick the model that fits their existing infrastructure and policy goals. ZATCA prioritised real-time visibility and chose centralisation. The UAE prioritised interoperability with global trade partners and chose Peppol. Neither is objectively superior.
What matters for finance leaders is preparation. ZATCA gave KSA businesses about 18 months between announcement and Phase 2 enforcement. The UAE has been telegraphing the 2026 to 2027 sequence for longer, which gives you time to plan properly if you start now.
Sources to verify the regulatory detail
Always validate against primary sources, not interpretation. For the UAE, start with the UAE MoF e-invoicing portal and the UAE Federal Tax Authority for tax procedures and penalty schedules. For the technical specification, read the Peppol UAE specification.
How to plan one program across both regimes
If you operate in KSA and UAE, treat them as one e-invoicing program with two delivery tracks. Use the same master data governance, the same invoice lifecycle taxonomy, and the same control framework. Split the technical execution: one mapper and connector per regime, one ASP for the UAE side, one direct Fatoora integration on the KSA side.
Build a single dashboard that shows invoice status across both regimes. Your tax team should not be switching between two consoles.
For a deeper view of the UAE side, including ASP selection, ERP integration patterns, and the move to production, see our UAE e-invoicing guide. When you are ready to operationalise, Massive's UAE e-invoicing software integrates with your ERP, connects to a Peppol ASP of your choice, and gives finance teams the same audit trail and dashboard regardless of which regime issued the document.