How UAE e-invoicing works
The five-corner (DCTCE) model in plain language, what the FTA receives, and why the XML is your legal record.
The UAE has adopted a five-corner model, formally the Decentralised Continuous Transaction Control and Exchange (DCTCE) model, built on the Peppol network.
| Corner | Who | What happens |
|---|---|---|
| C1 | You (supplier) | Create the invoice in the InvoiceNET portal, by bulk upload, or from your ERP. |
| C2 | Your Accredited Service Provider (ASP) | Converts it to PINT AE XML, validates it against the UAE rules, sends it over Peppol and reports it to the FTA. |
| C3 | Your customer's ASP | Receives the invoice, validates it again and reports it to the FTA as well. |
| C4 | Your customer | Receives the invoice in their own finance system. |
| C5 | Federal Tax Authority | Receives a Tax Data Document (TDD) from both C2 and C3, in parallel with delivery. |
What this means for you
- You never submit anything to the FTA yourself. Reporting happens automatically as part of transmission. There is no separate upload or filing step for each invoice.
- Delivery is never blocked by tax reporting. The invoice and the tax report travel in parallel. If the tax report needs a retry, your invoice has usually already been delivered.
- The XML file is the legal record, not the PDF. A PDF is a courtesy copy for people to read. Keep the electronic invoice; the platform archives it unchanged for you.
- Both sides validate. Your ASP validates before sending, and your customer's ASP validates again on receipt. An invoice can be Delivered and then Rejected if the receiving side finds a rule failure.
The standard behind it
Invoices are produced in PINT AE (Peppol International Invoice, UAE jurisdiction) carried in UBL 2.1 XML. Every document declares urn:peppol:pint:billing-1@ae-1 (or urn:peppol:pint:selfbilling-1@ae-1 for self-billing) as its specification identifier. You do not need to write XML: the portal and the ERP integration produce it.
Not the same as Saudi Arabia. ZATCA uses clearance with QR codes, cryptographic stamps and invoice hashes. The UAE model has none of these. A system built for one does not automatically satisfy the other.
Related: Mandate timeline and penalties, Document status explained.