The UAE's Ministry of Finance (MoF) announced in 2023 that the country would adopt Peppol as the foundation for its national e-invoicing framework. What makes the UAE's approach unique is the 5-corner model— extending Peppol's standard 4-corner network with a fifth corner: the tax authority itself, which receives a real-time copy of every B2B and B2G transaction.
This hybrid Peppol + CTC approach gives the UAE the interoperability benefits of Peppol (cross-border compatibility with 40+ Peppol countries) while providing the tax authority with continuous transaction visibility — similar to what Poland's KSeF or Italy's SDI deliver, but built on an open international standard.
Jul 2026
Pilot programme
Jan 2027
Large biz ≥AED 50M
5-Corner
Peppol CTC model
7 Years
Archival requirement
UAE Mandate Overview
The UAE's e-invoicing mandate is governed by the Ministry of Finance (MoF) and applies to all businesses operating in the UAE — including free zone companies and branches of foreign entities. Key characteristics:
Peppol Foundation
The UAE joined the Peppol network as a full authority member. All e-invoices must be exchanged through the Peppol network using Peppol BIS 3.0 (based on UBL 2.1). This is a deliberate choice for global interoperability — UAE businesses trading with European Peppol countries can use the same infrastructure.
CTC Overlay (5th Corner)
On top of the standard Peppol 4-corner model, the UAE adds a 5th corner: the MoF's tax authority platform. Every invoice transmitted through the network is automatically copied to the tax authority in real-time. This CTC layer provides revenue visibility without requiring sellers to submit invoices separately.
No E-Signatures or QR Codes
Unlike Saudi Arabia's ZATCA (which requires digital signatures and QR codes on invoices), the UAE mandate does NOT require electronic signatures or QR codes. The authenticity and integrity of invoices is guaranteed by the Peppol network's own trust framework and the ASP accreditation process.
7-Year Archival
All e-invoices must be archived for a minimum of 7 years from the date of issuance. The Peppol network does not provide long-term storage, so businesses must ensure their ASP or ERP system handles archival. This 7-year period aligns with the UAE's Commercial Transactions Law requirements.
Peppol 5-Corner Model
The standard Peppol 4-corner model connects sellers and buyers through their respective Access Service Providers (ASPs). The UAE extends this with a 5th corner — the tax authority — creating a CTC overlay on top of the Peppol network:
How the 5 Corners Work
Creates the invoice in their ERP, exports it to their ASP.
Validates the invoice against Peppol BIS 3.0 rules, converts to UBL 2.1 if needed, and transmits through the Peppol network. Simultaneously, a copy is sent to Corner 5 (tax authority).
Receives the invoice from the Peppol network, validates, and delivers to the buyer in their preferred format.
Receives the validated invoice, posts to accounts payable, and processes payment.
Receives a real-time copy of every transaction. This enables automated VAT cross-matching, fraud detection, and revenue forecasting without requiring separate tax reporting.
Phased Rollout
The UAE mandate follows a phased approach, starting with a voluntary pilot and expanding to full coverage by October 2027:
UAE E-Invoicing Timeline
Voluntary participation for early adopters and accredited ASPs
Selected businesses and ASPs test the full 5-corner flow in a production-like environment. The MoF uses this phase to validate the CTC infrastructure, ASP connectivity, and edge cases. Approximately 50–100 organizations expected to participate.
Mandatory for large businesses with annual revenue ≥AED 50 million
Large B2B enterprises must issue and receive invoices exclusively through the Peppol network. This includes multinational corporations operating in the UAE, large DMCC and DIFC entities, and government suppliers. Estimated 3,000–5,000 businesses affected.
Mandatory for all remaining B2B businesses
All VAT-registered businesses in the UAE must use the Peppol network for B2B invoicing. This is the broadest phase, bringing in SMEs, free zone companies, and smaller enterprises. Estimated 300,000+ businesses.
Mandatory for B2G (Business-to-Government) invoicing
All invoices to UAE government entities (federal and emirate-level) must flow through the Peppol network. This completes the mandate coverage across B2B and B2G. B2C invoicing is currently excluded from the mandate scope.
ASP Accreditation
In the UAE's Peppol model, businesses do NOT connect directly to the Peppol network. Instead, they must use an Accredited Service Provider (ASP) — the UAE's term for what Peppol internationally calls an Access Point. Understanding ASP accreditation is critical:
Accreditation Requirements
ASPs must be accredited by the UAE's MoF and OpenPeppol. Requirements include: legal establishment in the UAE (or a UAE-based partner), technical compliance with Peppol AS4 transport protocol, successful completion of the MoF's interoperability testing suite, data residency compliance (invoice data must be stored in the UAE or approved jurisdictions), and a minimum SLA of 99.5% uptime.
Trust & Security
ASPs must implement Peppol's PKI (Public Key Infrastructure) for secure message exchange. Each ASP holds a Peppol AP certificate issued by OpenPeppol. The AS4 protocol ensures end-to-end encryption of invoice data. Additionally, ASPs must comply with the UAE's data protection regulations (Federal Decree-Law No. 45/2021).
Choosing Your ASP
When selecting an ASP, evaluate: supported ERP integrations (pre-built connectors save months), format conversion capabilities (can they transform your ERP's native format to Peppol BIS 3.0?), archival services (7-year requirement), cross-border capability (if you trade with EU Peppol countries), and pricing model (per-invoice vs. subscription).
InvoStaq as Your ASP
InvoStaq is pursuing ASP accreditation in the UAE. Our platform provides: ERP-agnostic integration (SAP, Oracle, Dynamics 365, and others), automatic format conversion to Peppol BIS 3.0, 7-year compliant archival, multi-country support (single platform for UAE + EU Peppol countries), and real-time dashboard with Traffic Light Protocol monitoring.
Preparing Your Business
Regardless of which phase applies to you, start preparation now. The UAE mandate is technically simpler than Poland's KSeF (no proprietary schema — just Peppol BIS 3.0) but operationally significant:
Map your B2B and B2G invoicing landscape. How many invoices per month? How many unique trading partners? Which are UAE-based vs. international? This determines your ASP requirements and pricing tier. If you already trade with EU Peppol countries (Belgium, Ireland, etc.), you may already have Peppol capability.
Choose your ASP early — accreditation takes time and the best providers will prioritize early adopters. Evaluate: ERP connector availability, format support, archival, multi-country capability, and pricing. Ask for proof of MoF and OpenPeppol accreditation.
Every business on the Peppol network needs a Peppol Participant Identifier. Your ASP will help you register — you'll need your UAE trade license number or TRN (Tax Registration Number). Once registered, trading partners can discover and send invoices to you via the Peppol SMP (Service Metadata Publisher).
Connect your ERP to your ASP. This typically involves: configuring an export of invoice data from your ERP (API, SFTP, or file-based), mapping your ERP's invoice fields to Peppol BIS 3.0 structure, setting up inbound invoice processing (receiving invoices from Peppol into your ERP's AP module), and testing the end-to-end flow.
Confirm that either your ASP or your internal systems handle the 7-year archival requirement. The archive must store the original Peppol BIS 3.0 XML, preserve data integrity (timestamped, tamper-evident), be retrievable on demand for audit purposes, and comply with UAE data residency requirements.
During the pilot phase (July 2026), test with actual trading partners — not just internal test scenarios. Verify that invoices flow correctly through the 5-corner model, that your buyer's AP module correctly processes received invoices, and that the CTC copy reaches the MoF without errors.
UAE vs. KSA: Key Differences
If you already comply with Saudi Arabia's ZATCA FATOORA, note that the UAE approach is significantly different: the UAE uses Peppol (not a proprietary platform), does NOT require e-signatures or QR codes, and uses a 5-corner CTC model instead of ZATCA's clearance model. Your ZATCA integration cannot be reused directly — but InvoStaq's unified platform handles both alongside EU mandates.
Ready for the UAE's Peppol Mandate?
InvoStaq connects your ERP to the UAE's Peppol CTC network — one platform for the UAE, EU, and beyond.