How the UAE's Decentralized CTCE (5-Corner) model works, what Accredited Service Providers must do, and what PINT-AE certification and data residency requirements apply.
Published 28 February 2026 · AutoFact AI
Quick Answer
The UAE uses a 5-Corner DCTCE model: Supplier → Sending ASP → (FTA) → Receiving ASP → Buyer. ASPs are mandatory. They validate PINT-AE XML invoices and transmit the Tax Data Document (TDD) to the FTA. ASPs must hold ISO 27001, ISO 22301, and meet UAE data residency requirements.
The UAE Federal Tax Authority (FTA) has adopted a Decentralized Continuous Transaction Control and Exchange (DCTCE) model for its e-invoicing framework. This is commonly referred to as the 5-Corner model — a reference to the five parties through which every compliant e-invoice must flow.
Unlike a centralized clearance model (where all invoices are submitted to and cleared by the tax authority before reaching the buyer), the UAE's decentralized approach routes invoices through FTA-accredited private sector intermediaries — Accredited Service Providers (ASPs) — while simultaneously transmitting tax data to the FTA in near real-time.
Supplier
The business issuing the invoice. Responsible for creating a PINT-AE XML-compliant e-invoice.
Sending ASP
FTA-accredited service provider used by the supplier. Validates PINT-AE XML, extracts the TDD, and transmits to FTA and Corner 3.
Receiving ASP
FTA-accredited service provider used by the buyer. Receives the validated invoice from Corner 2 and delivers it to the buyer.
Buyer
The recipient of the invoice. Receives the PINT-AE e-invoice delivered by the Receiving ASP.
Federal Tax Authority (FTA)
The UAE regulator. Receives the Tax Data Document (TDD) from the Sending ASP in near real-time for compliance monitoring.
An Accredited Service Provider (ASP) is a private entity authorized by the FTA to act as a trusted intermediary in the UAE e-invoicing network. Both suppliers (Corner 1) and buyers (Corner 4) must use an FTA-accredited ASP. Self-transmission to the FTA is not permitted — ASP intermediation is mandatory.
The Sending ASP (Corner 2) performs two critical functions: it validates the PINT-AE XML invoice against the required schema and extracts the Tax Data Document (TDD) for transmission to the FTA. The Receiving ASP (Corner 3) delivers the validated invoice to the buyer.
All UAE e-invoices must conform to PINT-AE — the UAE-specific profile of the PEPPOL International (PINT) standard. PINT-AE is an XML-based format that extends the PEPPOL BIS Billing 3.0 structure with UAE-specific fields required by the FTA.
Base Standard
PEPPOL International (PINT)
UAE Profile
PINT-AE (UAE-specific extension)
Syntax
XML
Validation
Performed by Sending ASP (Corner 2)
TDD Extraction
ASP extracts Tax Data Document from PINT-AE XML
FTA Transmission
TDD transmitted to FTA by Sending ASP in near real-time
The FTA imposes strict technical and compliance requirements on ASPs. These requirements ensure the security, resilience, and sovereignty of UAE invoice data.
Information Security Management
ASPs must hold ISO 27001 certification, demonstrating that they have implemented a formal information security management system (ISMS) protecting invoice data from unauthorized access, disclosure, and breach.
Business Continuity Management
ASPs must hold ISO 22301 certification, ensuring they have documented and tested business continuity plans to maintain e-invoicing transmission services without interruption — even during incidents or disasters.
Local Data Storage Requirement
All invoice data processed and stored by ASPs must reside on infrastructure located within the UAE. Cross-border data transfer for invoice storage is not permitted. This protects UAE tax data sovereignty.
You cannot transmit invoices directly to the FTA
All UAE e-invoices must pass through a Sending ASP. Direct submission to the FTA portal is not the model — ASP intermediation is mandated by design.
Your invoice software must output valid PINT-AE XML
Your ERP or accounting platform must produce PINT-AE XML that passes schema validation. If your system only exports PDF or non-compliant XML, it will fail at the ASP validation stage.
ASP selection affects your compliance posture
Your Sending ASP is responsible for validating your PINT-AE XML and transmitting the TDD to the FTA. Choosing an ASP that lacks ISO 27001/22301 or UAE data residency exposes your business to compliance risk.
Both buyer and seller need an ASP
The 5-Corner model requires ASPs on both sides of the transaction (Corners 2 and 3). Ensure your buyers are also connected to a Receiving ASP to complete the chain.
No. Businesses cannot self-accredit as an ASP for their own invoices. ASPs must be independent entities that have obtained FTA accreditation and meet all ISO and data residency requirements.
The UAE model is inspired by but distinct from the 4-Corner PEPPOL model. The UAE adds a fifth corner — the FTA — which receives the Tax Data Document from the Sending ASP. This creates a continuous transaction control layer that PEPPOL's standard 4-corner model does not include.
If the Sending ASP rejects the PINT-AE XML due to validation errors, the invoice is not transmitted and the transaction is not compliant. The supplier must correct the errors and resubmit.
Yes. AutoFact AI generates PINT-AE XML-compliant e-invoices and supports integration with UAE-accredited ASPs for transmission and TDD filing.
AutoFact AI generates valid PINT-AE XML invoices and connects with UAE-accredited ASPs — removing the need to build your own PINT-AE pipeline or manage ASP integration in-house.
Regulatory Disclaimer: This article is for informational purposes only and does not constitute legal or tax advice. Regulatory details are based on published FTA guidance and may be subject to revision. Consult qualified UAE tax counsel for compliance advice specific to your business.
© 2026 AutoFact AI. All rights reserved.