UAE · MoF · FTA · DCTCE · PINT AE · Peppol C5

UAE eInvoicing.
Peppol 5-corner,
built before the deadline.

The UAE's DCTCE framework is a Peppol-based 5-corner model: PINT AE documents exchanged through Accredited Service Providers, with Tax Data Documents reported to the FTA. Pilot from July 2026 — Phase 1 mandatory January 2027. The architecture is the same one I have already built for Singapore's C5.

Jan 2027
Phase 1 Mandatory
AED 50M
Phase 1 Revenue Threshold
PINT AE
UAE Peppol Profile
Book a Readiness Assessment View Mandate Timeline →
DCTCE

The UAE's 5-corner model

DCTCE — Decentralised Continuous Transaction Control and Exchange — is the UAE's e-invoicing framework, run jointly by the Ministry of Finance and the Federal Tax Authority. It is a Peppol 5-corner architecture: invoices exchange between businesses through service providers, while tax data flows continuously to the FTA.

In a classic Peppol 4-corner model, an invoice travels from C1 (supplier) through C2 (supplier's service provider) and C3 (buyer's service provider) to C4 (buyer). No tax authority sits in the flow.

The UAE adds a fifth corner: the FTA. When an invoice passes between Accredited Service Providers, the supplier's ASP simultaneously reports a Tax Data Document (TDD) — the tax-relevant subset of the invoice — to the Federal Tax Authority, which returns electronic confirmations.

This is the same architectural pattern as Singapore's C5, where Access Points forward GST data to IRAS in parallel with delivery. The UAE differs in governance — ASPs must be accredited by the Ministry of Finance, and accreditation itself requires Peppol certification — but the engineering problems are the same: jurisdiction-specific document mapping, parallel authority reporting, and confirmation handling.

The exchange is decentralised: there is no single government portal that invoices clear through. Validation and transmission responsibility sits with the ASPs — which is exactly why choosing and integrating the right ASP correctly is the critical path of every UAE project.

Corner 1
Supplier

Issues invoice from ERP / billing system

→
Corner 2
Supplier's ASP

Validates PINT AE, transmits via Peppol

→
Corner 3
Buyer's ASP

Receives, validates, delivers

→
Corner 4
Buyer

Receives invoice into AP system

↓↓
Tax Data Document (TDD) + confirmations
Corner 5
Federal Tax Authority

Receives tax data continuously from ASPs — Decentralised CTC

PINT AE

The UAE document standard

PINT AE is the UAE specialisation of the Peppol International Invoice (PINT) — the same family as Singapore's PINT SG. It defines the mandatory and optional fields for UAE e-invoices, tax credit notes, and related documents.

pint_ae_invoice.xml
Document Type
PINT AE Invoice & Credit Note

UBL-based structured XML on the global PINT baseline, extended with UAE data rules — VAT treatment, TRN identifiers, and UAE-specific validation. Free-form PDFs stop counting as invoices once your phase goes live.

tax_data_document.xml
Corner 5 Reporting
Tax Data Document (TDD)

The tax-relevant extract of each invoice that the ASP reports to the FTA. Getting the TDD mapping right — and handling FTA confirmations and rejections — is the heart of DCTCE compliance.

asp_accreditation.cer
Service Providers
MoF-Accredited ASPs

Invoices may only flow through Accredited Service Providers — Peppol-certified providers additionally accredited by the Ministry of Finance. Every business in scope must appoint one before its phase deadline.

Why this is familiar territory: PINT AE sits in the same specification family as PINT SG, which I have implemented end-to-end — document mapping, jurisdiction Schematron validation, and 5-corner authority reporting. For UAE clients this means the unknowns are the UAE-specific rules, not the architecture. Verify current specifications against the Ministry of Finance's official eInvoicing publications — the programme is still issuing technical updates.
Mandate Timeline

Phased rollout, tight deadlines

The UAE rollout moves quickly: pilot in mid-2026, then mandatory phases through 2027. Businesses in Phase 1 must have an Accredited Service Provider appointed months before go-live.

phase_pilot.log
Starts Next Month
1 Jul 2026
Pilot Programme

DCTCE goes live with pilot participants. ASPs and early adopters exchange production-grade PINT AE documents and TDD reporting with the FTA.

phase_1.log
Mandatory
1 Jan 2027
Phase 1 — Large Businesses

Businesses with revenue ≥ AED 50M must issue and receive e-invoices through an ASP — with the ASP appointed well in advance (per MoF schedule, during 2026).

phase_2.log
Mandatory
1 Jul 2027
Phase 2 — Remaining Businesses

The mandate extends to businesses below the AED 50M threshold, with ASP appointment deadlines in early 2027.

phase_gov.log
Mandatory
1 Oct 2027
Government Entities

Government entities follow a separate track, completing the B2B and B2G coverage of the DCTCE framework.

The practical deadline is earlier than the legal one. Phase 1 businesses need an appointed ASP, a working PINT AE mapping from their ERP, and tested TDD flows before January 2027 — which makes the second half of 2026 the integration window. Dates above reflect the Ministry of Finance's published schedule; confirm your entity's exact obligations against current MoF guidance.
UAE Services

From ERP to FTA, end to end

Built on production Peppol 5-corner experience from Singapore — applied to the UAE's DCTCE framework.

🧭
DCTCE Readiness Assessment

Scope your obligations by phase, map your invoice flows (B2B, B2G, self-billing), and produce a gap analysis between your current billing data and PINT AE requirements.

🔗
ASP Selection & Integration

Evaluate MoF-accredited ASPs against your volumes, ERP landscape, and cross-border needs — then build and test the integration between your systems and the chosen ASP.

📄
PINT AE Document Mapping

Field-by-field mapping from your ERP (SAP, Oracle, Dynamics, custom) to PINT AE invoices and tax credit notes — including VAT treatment and TRN handling.

📡
TDD & FTA Confirmation Handling

Design the Tax Data Document flow: what gets reported to the FTA, how confirmations and rejections come back, and how your AR/AP processes react to them.

🌐
Cross-Border Peppol Routing

UAE corridors to Singapore, Malaysia, and the EU — one Peppol-based stack covering your regional invoicing instead of one-off country builds.

🛠️
For Software Vendors & ASP Candidates

Building ASP capability or adding UAE support to your product? I bring the Peppol AP engineering — AS4, SMP/SML, PINT validation pipelines — that accreditation requires.

Let's Talk

January 2027 is closer
than it looks.

Whether you are a Phase 1 business scoping the mandate, a vendor adding UAE support, or a regional group planning SG + UAE + MY together — reach out. First consultation is complimentary.

hello@peppwise.com
Send an Enquiry Book a Discovery Call