The UAE has adopted the Peppol e-invoicing. This runs on a Peppol CTC model which is a Decentralised Continuous Transaction Control and Exchange (DCTCE) or a 5-corner model.
The Peppol CTC model enables FTA to collect transactional data in real-time or near real-time. Accredited Service Providers are required to be appointed for invoice exchange.
Latest update: The Ministry of Finance has extended the deadline for appointing an ASP from 31 July 2026 to 30 October 2026 for businesses with annual revenues above AED 50 million.
Key Takeaways
- The decentralised Continuous Transaction Control and Exchange (DCTCE) in the UAE is built on the Peppol Interoperability Framework.
- No government pre-approval is needed before you send an invoice. The tax data is reported separately to the FTA's Access Point and Central Data Platform.
- You cannot comply alone. Both issuer and recipient must appoint an Accredited Service Provider as a legal obligation.
- Deadlines are staged by revenue. AED 50m+ (get a ASP by 30 October 2026, go-live by 1 January 2027); under AED 50m (get an ASP by 31 March 2027, go-live by 1 July 2027); government entities (ASP by 31 March 2027, live 1 October 2027).
- B2C is out of scope for now, and invoices must be issued and transmitted within 14 days of the business transaction date.
Peppol e-invoicing is the exchange of structured and electronic invoices across a governed international network, where each party connects through a certified service provider rather than building point-to-point links with every counterparty.
In the UAE, the invoice format is PINT AE which is the UAE-specific Peppol International Invoice specification. Under Ministerial Decision No. 243 of 2025, an Electronic Invoice is defined as "an invoice issued, transmitted, and received in a structured electronic format that enables automatic and electronic processing." A PDF emailed to a customer is not an e-invoice.
The Peppol CTC (Continuous Transaction Control) model is a tax-reporting architecture where the trading parties directly exchange the invoices. Such exchange of invoices is done over the Peppol network and transaction data is reported to the tax authority.
The UAE's version of Peppol CTC model is the decentralised Continuous Transaction Control and Exchange (DCTCE). The FTA gets full transaction visibility without sitting in the middle of your order-to-cash cycle.
The Peppol e-invoicing in UAE framework is an infrastructure designed to facilitate the real-time exchange of electronic invoices, between businesses and government tax authorities. The UAE reuses the standard Peppol 4-corner model and adds a fifth corner for the tax authority.
This model includes five key components:
Corner | Who it is | Role |
C1 | Supplier (sender) | Issues the invoice from its ERP or billing system |
C2 | Supplier's ASP | Validates, converts to PINT AE, transmits, and generates the Tax Data Document |
C3 | Buyer's ASP | Receives, validates, delivers to buyer, reports its own Tax Data Document |
C4 | Buyer (recipient) | Receives the structured invoice into its system |
C5 | FTA Access Point | Receives Tax Data Documents and passes them to the FTA Central Data Platform |
The clearest contrast is with Saudi Arabia, which uses a centralised clearance model through ZATCA's Fatoora platform.
Dimension | Peppol CTC (5-corner DCTCE) | Centralized Clearance |
Invoice route to buyer | Supplier → ASP (C2) → ASP (C3) → Buyer, over the Peppol network | Supplier → tax authority platform → back to supplier → Buyer |
Authority approval before sending? | No. The invoice is exchanged directly; tax data is reported separately | Yes. The standard tax invoices must be "Cleared" by the government before sharing with the buyer. (e.g.: ZATCA in KSA) |
Authority's position | Alongside the flow. FTA in the UAE Access Point (C5) receives Tax Data Documents into the Central Data Platform. | Inside the flow. Fatoora validates, applies a cryptographic stamp and QR code, returns the cleared XML. |
Who reports | Both supplier's ASP (C2) and buyer's ASP (C3) | Primarily the seller (buyer under approved self-billing) |
B2C treatment | Out of scope until the Minister decides otherwise (MD 244, Art. 5(2)) | Simplified invoices "Reported" to Fatoora within 24 hours of generation |
Invoice Format | PINT AE (Peppol International Invoice, UAE) | ZATCA XML Implementation Standard |
Party identification | UAE TIN under Peppol scheme 0235 | Solution-level cryptographic stamp identifiers (CSIDs) |
Intermediary | Accredited Service Provider is mandatory for issuer and recipient | Direct integration between the taxpayer's solution and the authority |
Cross-border reach | Inherits Peppol interoperability with other Peppol jurisdictions | Designed around the domestic platform |
In a clearance model, a rejected invoice blocks the customer from receiving a valid document. It’s a dependency on the tax authority in a revenue cycle. In the UAE's Peppol CTC model, invoice delivery and tax reporting are decoupled and the billing cycle is not gated on the FTA.
What’s the trade-off: The reporting obligations are on both sides of every transaction, so your master data and AP process quality now directly drive your compliance record.
The preparation for Peppol e-invoicing in UAE must begin before the ASP appointment. The vendor appointment deadline is a procurement milestone; the go-live date is a systems milestone.
The process assessment is the first step which includes how invoices are generated, exchanged, approved, and stored.
Step 1 - Confirm your wave: Revenue is defined in MD 244 as "the gross income earned by a Person during the most recent Accounting Period, based on the financial statements." It’s not taxable turnover, it’s the gross income. Determine this precisely; it sets your entire timeline.
Category | Appoint ASP by | Go live by |
Revenue ≥ AED 50 million | 30 October 2026 | 1 January 2027 |
Revenue < AED 50 million | 31 March 2027 | 1 July 2027 |
Government entities | 31 March 2027 | 1 October 2027 |
The AED 50m+ deadline was extended from 31 July 2026 to 30 October 2026 by Ministerial Decision No. 66 of 2026.
Step 2 - Invoice process mapping: List your every invoice source, such as ERP, accounting software, POS, ecommerce, subscription billing tool, manual entries, or spreadsheet.
Step 3 - Audit your master data: Next is your master data cleanup. Customers, TRNs, item descriptions, VAT codes, tax categories, currency fields, etc. must not be incorrect or unverified. Missing, malformed or unverified counterparty TINs will fail validation at C2 before an invoice ever leaves your ASP.
Cleanse customer and vendor master data now. This is not exciting work. This is consistently the longest task and the one CFOs underestimate.
Step 4 - Map your transaction population against the exclusions: Airlines, financial services and sovereign government transactions need specific analysis. Run all revenue streams and every AP category against MD 243 Art. 4. Identify self-billing arrangements early as permitted under Art. 9 where both parties are registrants.
Step 5 - Fix the accounts payable side: Recipients must process electronic invoices and credit notes through the system (Art. 6(3)), and the buyer's ASP reports a TDD. Most readiness programmes over-invest in AR and under-invest in AP.
Step 6 - Assess your ERP's field-level readiness: PINT AE mandates fields that many UAE ERP configurations do not currently populate. Run a gap analysis against the mandatory field set before selecting an integration approach.
Step 7 - Select your ASP on substance: Test for; Article 16 accreditation status, native connectors for your ERP, UAE data residency, ISO/IEC 27001 for the actual product, exception-handling workflow when an MLS fails, and reconciliation reporting between your ledger and what was reported to the FTA.
Check for your Peppol readiness. You should confirm whether your selected solution can support structured invoice exchange, buyer and supplier connectivity, validation rules, and reporting workflows.
Step 8 - Build the exception process before go-live: Decide now who owns a failed MLS, who notifies the FTA within 2 business days of a system failure, and who reconciles TDDs against the GL each period.
Step 9 - Use the voluntary window: Voluntary implementation has been available from 1 July 2026, alongside the Pilot Programme commenced on the same date. If you adopt early, it will help you with a controlled testing period.
Only an OpenPeppol-certified service provider can be a Peppol access point in the UAE.
apply for UAE accreditation. An Access Point in the UAE is an Accredited Service Provider (ASP).
Under Ministerial Decision No. 64 of 2025, an ASP must:
Important things to note:
Businesses should proactively prepare for the transition to the Peppol CTC model and ensure their business systems are compliant with Peppol standards. This involves integrating Peppol-compatible software and solutions into their existing infrastructure to facilitate seamless electronic document exchange.
ClearTax, as a global e-invoicing solution provider and pre-approved ASP for UAE e-invoicing, helps businesses transition to the Peppol CTC framework.