The UAE model is Decentralized Continuous Transaction Control and Exchange — DCTCE — commonly described as the "five-corner model" because it adds the tax authority as a fifth corner on top of the familiar four-corner Peppol network.
The five corners, in order
- Corner one — the supplierYou. You raise the invoice in your accounting system as usual.
- Corner two — your accredited providerConverts your data into PINT AE, validates it, signs it digitally and sends it over Peppol. At the same time it extracts the tax data and reports it to the authority.
- Corner three — the buyer's providerReceives the invoice, validates it in turn, issues the status message, and also reports to the authority from the buyer's side.
- Corner four — the buyerThe invoice arrives in their system structured and ready to post.
- Corner five — the Federal Tax AuthorityReceives transaction data from both sides, giving it a consolidated, real-time view of economic activity.
Why report the same invoice twice?
This is the heart of dual validation. When both parties report the same transaction independently, the authority can reconcile the two accounts. Agreement builds confidence; divergence raises a flag. The effect is that one-sided manipulation becomes structurally visible, rather than something found in a later audit.
What this means for your business
| Design decision | Consequence |
|---|---|
| You cannot send it yourself | Network access is restricted to accredited access points — which is why appointing a provider is not optional |
| You need both directions | Sending and receiving are both part of the system, and only 24 of 48 providers advertise receiving |
| Data reaches the authority live | There is no quiet later correction; an error is visible as it happens |
| The status message matters | It is your evidence the invoice was actually accepted — ask your provider to surface it in the dashboard |
What is PINT AE, and why won't any XML do?
PINT AE is the UAE invoice specification, built on the Peppol International Invoice standard, itself built on UBL 2.1. Every field has a defined meaning in a defined place, so the buyer's system and the authority's system read it identically. A well-formed XML file that does not follow the specification will be rejected — which is why "our system can export XML" is not the same as being ready.
Check your invoice before the mandate
Our XML checker reads your file and tells you where it diverges from the PINT AE specification — free, and without uploading your data to any server.
Open the ASP directoryRead next
Frequently asked
What is the five-corner model in UAE e-invoicing?
It is the Decentralized Continuous Transaction Control and Exchange (DCTCE) model. The corners are the supplier, the supplier's accredited provider, the buyer's provider, the buyer, and the Federal Tax Authority as the fifth corner, receiving transaction data from both providers in real time.
How does the UAE model differ from Saudi Arabia's clearance model?
In Saudi Arabia the invoice passes through the authority's platform for clearance before it reaches the buyer. In the UAE the invoice travels directly between the two providers over Peppol while data is reported to the authority in parallel — continuous control without the government portal being a bottleneck.
Why is a single invoice reported twice?
Because the sender's provider and the receiver's provider each extract and report the data independently. That dual validation lets the authority reconcile both parties' accounts of the same transaction.
What is the PINT AE specification?
It is the UAE e-invoice specification, based on the Peppol International Invoice standard, which is itself based on UBL 2.1. A file being well-formed XML is not enough; it must follow this specification or it will be rejected.