UAE E-Invoicing vs Saudi FATOORAH: Key Differences 2026

Many multinationals operating across the GCC already have Saudi FATOORAH implemented. It went live for large businesses in December 2021, and Phase 2 clearance integration started in January 2023. So when finance teams hear that UAE e-invoicing is coming in 2027, a reasonable assumption surfaces: can we extend what we built for Saudi Arabia?

The answer is no. The two systems share only one thing in common: both are built on UBL 2.1 data structures. Everything else, the architecture, the clearance model, the regulatory body, the certification path, and the compliance timeline, is different. Saudi FATOORAH is a closed, centralised clearance system. UAE PINT AE is an open, decentralised Peppol network. A solution designed for one will not satisfy the other without meaningful rework.

This post breaks down exactly where the two systems diverge and what your finance and IT teams need to plan for.

For a deeper look at how the UAE's Peppol infrastructure works, see our UAE e-invoicing guide.

Key Takeaways- Saudi FATOORAH requires B2B invoices above SAR 1,000 to clear through ZATCA in real time before reaching the buyer. UAE PINT AE uses post-event reporting: the invoice goes to the buyer first, and tax data flows to the FTA through the Peppol network afterward.- The UAE runs on an open, five-corner Peppol model with 41 pre-approved ASPs as of June 2026 (UAE Ministry of Finance, 2026). Saudi Arabia uses a proprietary ZATCA Fatoora portal with a separate approval process.- Both standards are UBL 2.1-based, but field mappings differ enough that a single ERP output template will not cover both countries.- UAE Phase 1 go-live is 1 January 2027. Saudi Phase 2 has been rolling out since January 2023 - your Saudi implementation is already years ahead on the timeline.

What Is the Fundamental Architecture Difference?

The core distinction between the two systems is how the tax authority sits in the invoice flow. Saudi Arabia's FATOORAH, administered by ZATCA, requires that the tax authority clears a B2B invoice before it reaches the buyer (ZATCA, "E-Invoicing Overview", 2024). The UAE chose the opposite model: the invoice travels from seller to buyer through the Peppol network, and the FTA receives tax-relevant data automatically as part of that flow.

That's not a minor technical footnote. It changes everything about how you build the integration.

In Saudi Arabia, your ERP must call ZATCA's Fatoora API, receive a clearance response, attach the cryptographic stamp and QR code to the invoice, and only then send it to your buyer. If ZATCA's API is down or slow, your invoices are delayed. If the clearance step fails, the transaction stalls. Your uptime SLA with ZATCA effectively becomes part of your order-to-cash cycle.

In the UAE, your ASP handles the FTA reporting asynchronously. The buyer gets the invoice promptly. The FTA gets the data through the Peppol network. Your business keeps moving even if there's a short reporting delay, because the reporting obligation and the buyer delivery are separate operations.

This architectural difference reflects a deliberate policy choice. Saudi Arabia prioritised tax authority control at the point of transaction. The UAE prioritised trade efficiency and interoperability, accepting a slight reduction in real-time control in exchange for a model that works smoothly with international buyers. Neither approach is wrong — they reflect different priorities for where each economy wants friction to sit.

How Does Saudi FATOORAH's Clearance Model Work?

Saudi Arabia launched Phase 1 of FATOORAH on 4 December 2021, requiring all VAT-registered businesses to generate and store invoices digitally (ZATCA, "E-Invoicing Overview", 2021). Phase 2 began in January 2023 with Wave 1 targeting businesses with annual revenue above SAR 3 billion, then progressively expanded to lower revenue bands through subsequent waves.

The clearance model operates in three corners. You are Corner 1. ZATCA is Corner 2 and the central hub. Your buyer is Corner 3.

Here's what that flow looks like in practice. You generate an invoice in your system in FATOORAH XML format. That format is based on UBL 2.1 but includes Saudi-specific extensions: mandatory UUID, cryptographic hash, anti-tampering stamp, and a QR code containing encoded invoice data. You submit it to ZATCA's Fatoora portal via API. ZATCA validates and clears the invoice, attaching its own cryptographic stamp. You then send the stamped invoice to your buyer. The whole process happens in near-real time — typically seconds, but with variance depending on API load.

For simplified invoices (B2C transactions, or B2B invoices below SAR 1,000), the model is slightly different. You generate and send immediately, then report to ZATCA within 24 hours. The clearance step doesn't block delivery.

Penalties for non-compliance range from SAR 1,000 to SAR 50,000 per violation, depending on severity and repeat offence history (ZATCA, 2021).

How Does the UAE PINT AE Peppol Model Work?

The UAE's e-invoicing system, established under Federal Decree-Laws 16 and 17 of 2024, uses a five-corner Peppol model where the seller and buyer are each connected to the network through their own accredited service provider (UAE Ministry of Finance, "UAE Electronic Invoicing Guidelines V1.1", June 2026). The FTA sits at Corner 5, receiving tax-relevant data from both ASPs automatically.

The invoice journey works like this. You generate an invoice in your ERP. It goes to your ASP (Corner 2), which validates it against the PINT AE standard, converts it to the required XML format, and transmits it through the Peppol network (Corner 3) to your buyer's ASP (Corner 4). That ASP delivers the invoice into the buyer's system. The FTA receives the transaction data from both sides of the network as part of this flow.

What does PINT AE require in terms of data? The standard has 130+ total fields, of which 51 are mandatory, across 16 invoice scenarios (KPMG, "UAE: Technical Guidance on Mandatory E-Invoicing Fields", February 2026). The scenarios cover standard invoices, credit notes, debit notes, and self-billed invoices. Each has its own validation rules. Your ASP applies all checks before the invoice enters the Peppol network.

One point worth emphasising: the post-event reporting model means the FTA is not a gatekeeper of each transaction. The invoice flows to your buyer even if there's a momentary reporting lag. That's structurally different from Saudi Arabia, where ZATCA clearance is a prerequisite for delivery.

For a detailed walkthrough of the five-corner model and how the Peppol network operates, see our Peppol network guide.

FATOORAH vs PINT AE: Side-by-Side Technical Comparison

The table below captures the key technical differences your ERP and tax teams need to account for. These aren't cosmetic differences — each row represents a separate integration requirement or compliance obligation.

Finance teams that have worked through both rollouts describe the Saudi implementation as more technically demanding at go-live, because the real-time clearance loop adds an API dependency that's absent in the UAE model. But the UAE's 51 mandatory PINT AE fields require cleaner master data than many ERP setups currently carry. Both implementations surface data quality problems; they just surface them at different points in the process.

What Are the Timeline Differences Between the Two Systems?

Saudi Arabia is years ahead on implementation. FATOORAH Phase 1 launched on 4 December 2021 for all VAT-registered businesses (ZATCA, 2021). Phase 2 clearance integration started in January 2023 with Wave 1 businesses above SAR 3 billion in revenue, then rolled progressively through lower revenue bands. If your Saudi entity has revenue above SAR 500 million, you're almost certainly already live on Phase 2.

As of mid-2026, ZATCA's wave rollout has extended well below the SAR 3 billion threshold — all VAT-registered businesses in Saudi Arabia are expected to be covered by integration requirements. Businesses operating in both the UAE and Saudi Arabia should verify their current ZATCA wave status directly with ZATCA.

The UAE is on a different clock entirely. Phase 1 applies to businesses with annual turnover above AED 50 million. Those businesses must appoint an ASP by 30 October 2026 and go live by 1 January 2027 (UAE Ministry of Finance, Ministerial Decision No. 66 of 2026). Phase 2 applies to all other in-scope businesses: ASP appointment by 31 March 2027, go-live by 1 July 2027.

A voluntary pilot is open from 1 July 2026. The non-compliance penalty of AED 5,000 per month kicks in only after the mandatory go-live date for your phase.

What does the timeline gap mean practically? If your Saudi entity has already gone through Phase 2 integration, your IT team has hands-on experience with e-invoicing architecture. That's an asset. But don't let that experience generate false confidence about the UAE project. The clearance model, the network, and the certification path are all different. The UAE implementation is a separate project, not an extension.

Can One Solution Cover Both UAE and Saudi E-Invoicing?

This is the question every multinational finance director asks. The honest answer: technically possible, but only with purpose-built configuration for each country. No off-the-shelf product handles both markets with a single setup.

Here's where the overlap is genuine. Both systems use UBL 2.1 as the underlying data standard. That means the conceptual data model — buyer, seller, line items, tax, totals — maps similarly. An ERP that can produce valid UBL 2.1 output is a reasonable starting point for both implementations.

Here's where the divergence is real. Saudi FATOORAH requires a live API connection to ZATCA's Fatoora portal, real-time clearance handling, cryptographic stamping on each invoice, and a QR code containing hashed invoice data. UAE PINT AE requires connection to a Peppol-accredited ASP, post-event transmission, 51 specific mandatory fields with UAE-specific validation rules, and a Peppol Participant Identifier built from your 10-digit TIN with the prefix 0235.

The certification bodies are also separate. UAE ASPs are accredited by the Ministry of Finance (41 approved providers as of June 2026). Saudi solutions are approved by ZATCA. Some providers hold both accreditations — Deloitte, for example, is a UAE pre-approved ASP and operates in the Saudi market. But "the same provider" is not the same as "the same technical solution."

What's the realistic path for multinationals? Choose an ASP for UAE that also operates in Saudi Arabia and has existing FATOORAH capability. Ask them directly: can your platform output both PINT AE and FATOORAH formats from the same ERP integration? The answer will vary by provider. For guidance on evaluating UAE providers specifically, see our UAE ASP selection guide.

What Should Multinationals Do Now to Prepare for Both?

The UAE Phase 1 deadline is 1 January 2027 for businesses above AED 50 million. As of mid-2026, businesses in the Phase 1 cohort have under seven months until the January 2027 go-live deadline. Businesses that wait until Q4 2026 to start will find the 41 approved ASPs stretched and onboarding timelines extended.

Three actions should happen now. First, confirm your UAE entity's revenue against the AED 50 million threshold. If you're Phase 1, your ASP appointment deadline is 30 October 2026. Missing that date is a compliance failure before you've even issued your first e-invoice.

Second, run an ERP readiness audit. The 51 mandatory PINT AE fields include data points that many UAE ERPs don't currently capture cleanly: buyer TIN, Peppol Participant Identifier, specific address structures, and correct VAT accounting key. The data mapping exercise typically takes four to eight weeks for a business with complex ERP setups. Start now.

Third, talk to your Saudi FATOORAH provider. If they're also a UAE pre-approved ASP, ask about a unified integration approach. Even if a single template won't work, sharing the ERP integration layer reduces your total implementation effort. Don't assume the answer is yes, but don't assume it's no either.

One pattern we see in GCC multinational implementations: the Saudi FATOORAH experience often underestimates UAE project effort because the clearance model is simpler in the UAE. But the Peppol network adds a new layer of directory registration — the Peppol Participant Identifier — that has no Saudi equivalent. Getting your entity registered in the Peppol SMP (Service Metadata Publisher) is a step Saudi implementations never required, and it catches teams by surprise.

The voluntary pilot opens on 1 July 2026. Running a controlled pilot transaction before the mandatory go-live date is the most reliable way to confirm your ASP integration actually works end-to-end. Saudi Phase 2 onboarding teams learned that lesson from Wave 1 businesses that went live without adequate testing.

---

---

Sources

• UAE Ministry of Finance, "UAE Electronic Invoicing Guidelines V1.1," retrieved 2026-06-22, https://mof.gov.ae/en/ourpoliciesandinitiatives/Pages/eInvoicing.aspx
• UAE Ministry of Finance, "Ministerial Decision No. 66 of 2026 (amending MD No. 244 of 2025)," retrieved 2026-06-22, https://mof.gov.ae/en/news/issuance-of-amendments-to-federal-decree-law-on-tax-procedures-and-federal-decree-law-on-value-added-tax-to-support-the-einvoicing-system/
• ZATCA, "E-Invoicing Overview," retrieved 2026-06-22, https://zatca.gov.sa/en/E-Invoicing/
• OpenPeppol, "About Peppol," retrieved 2026-06-22, https://peppol.eu/
• KPMG UAE, "UAE: Technical Guidance on Mandatory E-Invoicing Fields," retrieved 2026-06-22, https://kpmg.com/us/en/taxnewsflash/news/2026/02/uae-technical-guidance-mandatory-e-invoicing-fields.html
• Deloitte, "Tax services - GCC e-invoicing," retrieved 2026-06-22, https://www.deloitte.com/xe/en/services/tax.html
• PwC, "GCC e-invoicing," retrieved 2026-06-22, https://www.pwc.com/m1/en/tax/e-invoicing.html