GULF CONSULT E-Invoicing Team on

UAE vs Saudi E-Invoicing: How GCC Groups Can Comply in Both Countries in 2027

UAE vs Saudi e-invoicing for GCC groups: Peppol PINT AE vs ZATCA Fatoora, 2027 deadlines and one ERP plan for both. Book a free 30-minute call.

UAE vs Saudi e-invoicing featured image reading E-Invoicing: UAE vs Saudi Arabia on a dark skyline graphic
5 min read

For groups trading across the Gulf, the UAE vs Saudi e-invoicing question has become urgent. Large UAE businesses must go live on 1 January 2027. In Saudi Arabia, the Zakat, Tax and Customs Authority (ZATCA) has set 1 February 2027 as the start date for Wave 25 of its integration phase. Both systems produce structured electronic invoices, but they work very differently. A group that builds one solution for both, without understanding the differences, will end up rebuilding it.

The UAE model at a glance

The UAE uses a decentralised model built on the Peppol network:

  • Invoices are exchanged through Accredited Service Providers (ASPs), which validate them and pass tax data to the Federal Tax Authority (FTA).
  • The data standard is PINT AE, the UAE's Peppol specification.
  • The first phases cover business-to-business and business-to-government invoices.
  • Activation and onboarding run through EmaraTax.

The FTA confirmed the timeline on 25 October 2026:

UAE taxpayerAppoint an ASP byGo live by
Annual revenue of AED 50 million or more30 October 20261 January 2027
Annual revenue below AED 50 million31 March 20271 July 2027

The penalty for failing to implement, including failing to appoint an ASP on time, is AED 5,000 for each month or part of a month of delay.

The Saudi model at a glance

Saudi Arabia's system, known as Fatoora, is centralised:

  • Phase 1, from 4 December 2021, required businesses to generate electronic invoices in a compliant format.
  • Phase 2, the integration phase, started on 1 January 2023 and connects each taxpayer's system directly to ZATCA. It is rolled out in waves by revenue.
  • Standard tax invoices between businesses are cleared by ZATCA before they are issued to the buyer. Simplified invoices, typically business-to-consumer, are reported to ZATCA after issue.
  • Invoices carry ZATCA's technical requirements, such as a cryptographic stamp and a QR code.

On 24 July 2026 ZATCA announced Wave 25: Saudi resident taxpayers with taxable turnover above SAR 187,500 in any of 2022, 2023, 2024 or 2025 must comply with Phase 2 from 1 February 2027. This is the first wave to look at 2025 revenue, so companies established in 2025 can be caught.

Side by side: UAE vs Saudi e-invoicing

PointUAESaudi Arabia
ArchitectureDecentralised, Peppol network with ASPsCentralised, direct integration with ZATCA's Fatoora platform
Invoice standardPINT AEZATCA's XML specification
Real-time controlASP validates and reports tax data to the FTAB2B invoices cleared by ZATCA before issue; B2C reported after issue
Who connects youAn accredited service provider you contract withYour own system or solution provider, onboarded to ZATCA
Next big date1 January 2027 (revenue of AED 50m or more); 1 July 2027 (others)1 February 2027 (Wave 25)
Scope at launchB2B and B2GB2B and B2C, with different flows

What this means for a GCC group

You need two compliance engines, not one

A Saudi Fatoora integration will not satisfy the UAE, and a UAE ASP connection will not satisfy ZATCA. The good news is that both start from the same place: clean master data and invoice data in your ERP.

Master data is where projects fail

Both systems reject invoices with missing or inconsistent buyer data. Before go-live, clean customer records: legal names, tax registration numbers, addresses and, for the UAE, the identifiers your ASP needs for Peppol routing.

Cross-border invoices need rules

A UAE entity invoicing a Saudi affiliate, or the reverse, issues an invoice under its own country's system. Map these flows so intercompany billing does not stall.

Timelines collide in Q1 2027

UAE large-business go-live on 1 January 2027 and Saudi Wave 25 on 1 February 2027 fall within five weeks of each other. Shared finance teams and ERP partners will be stretched. Plan testing windows now.

A practical plan for groups operating in both countries

  1. Confirm scope in each country. UAE revenue band and Saudi wave for every entity.
  2. Choose the UAE ASP. Larger UAE entities should already have one; others have until 31 March 2027.
  3. Confirm the Saudi solution. Check whether your ERP's Saudi localisation supports Phase 2 or whether you need a middleware provider.
  4. Design one data layer. Keep a single, clean invoice data model in the ERP that feeds both country outputs.
  5. Test with real scenarios. Credit notes, advance payments, multi-currency invoices, discounts and intercompany charges.
  6. Train the finance team. Rejected invoices need a fast fix process, or cash collection suffers.

How GULF CONSULT helps

Our e-invoicing team runs UAE readiness reviews, ASP selection and EmaraTax onboarding, and coordinates with Saudi solution providers for group-wide projects. Our ERP implementation team configures SAP Business One, NetSuite, Dynamics 365 and Odoo for both data standards. If you are still choosing an ASP, see our ASP selection checklist.

Talk to GULF CONSULT

Running entities in both the UAE and Saudi Arabia? Book a free 30-minute consultation with GULF CONSULT to map one plan for both. Email [email protected], call +971 58 600 4833 or message us on WhatsApp.

Frequently Asked Questions

Is UAE e-invoicing the same as Saudi Fatoora?

No. The UAE uses a decentralised Peppol model with accredited service providers and the PINT AE standard. Saudi Arabia uses a centralised model where ZATCA clears B2B invoices before issue.

When does UAE e-invoicing start?

Businesses with revenue of AED 50 million or more go live by 1 January 2027. Others must appoint an ASP by 31 March 2027 and go live by 1 July 2027.

Which Saudi businesses are in Wave 25?

Saudi resident taxpayers with taxable turnover above SAR 187,500 in 2022, 2023, 2024 or 2025, with compliance from 1 February 2027.

Can one ERP handle both countries?

Yes, if it is configured with clean master data and connected to a UAE ASP and a ZATCA-compliant integration. Many ERPs need localisation add-ons or middleware.

What is the UAE penalty for missing the e-invoicing deadline?

AED 5,000 for each month or part of a month of delay, including failure to appoint an ASP on time.

Sources

  1. FTA e-invoicing deadlines announcement, 25 October 2026
  2. ZATCA e-invoicing laws and regulations
  3. EY on Saudi Wave 25

This article is general information, not advice for your situation. Rules change; check the current position or speak to an advisor before acting.

Need help with this? See our E-Invoicing Services.

E-Invoicing Services

Turn the Rule Into a Plan

A 30-minute session with the advisor who would run the work tells you what this means for your business, your deadlines and your filings.

More Business News