Lesson 2 — The five-corner model
The UAE has not built a portal you upload invoices to. It has adopted a network, and the shape of that network answers most of the practical questions people ask.
The model is a Decentralised Continuous Transaction Control and Exchange, abbreviated DCTCE, and it has five corners. Decentralised: no single government gateway sits in the middle of the exchange. Continuous: tax data reaches the Federal Tax Authority with the transaction rather than weeks later in a return. Transaction control: the document is checked as it moves, not audited long afterwards.
The five corners are these.
| Corner | Who | What happens there |
|---|---|---|
| C1 | The supplier | Issues the invoice in its own system |
| C2 | The supplier's ASP | Validates the document, transmits it over Peppol, reports the tax data |
| C3 | The recipient's ASP | Receives the document and delivers it onward |
| C4 | The recipient | Takes the e-invoice into its own system |
| C5 | The Federal Tax Authority | Receives the tax data |
Read C2 twice. The supplier's ASP does two jobs, not one: it delivers the document to the other side, and it reports the tax data to the FTA. That second job is why the mandate is written around appointing a provider rather than around buying a file format.
One invoice, in order. Your system issues an invoice to a UAE customer (C1). Your ASP validates it against the UAE rules and transmits it over the Peppol network to your customer's ASP (C2). Their ASP delivers it to your customer, whose system takes it in as a purchase document (C3 to C4). In parallel, your ASP reports the tax data to the FTA (C5). You did not log in anywhere. Neither did your customer.
The FTA outcome arrives last, and it arrives through your ASP. Clearance is not instantaneous and it is not visible to you directly — you learn it when the provider tells you. Honest software therefore shows three states rather than two: sent, cleared, and handed over but not yet answered for.
Two expectations cause most of the confusion. The first is the EmaraTax expectation — people look for a government screen to upload invoices to, and for invoices there is not one. The second is the instant-status expectation: a document that has left your system with no FTA result yet is neither a failure nor a success. Odoone counts those separately for exactly that reason, keeping documents in flight in their own column, because a compliance percentage that quietly absorbed them would climb during a provider outage, which is precisely when it should fall.
The idea to carry forward: you cannot comply alone. Corner 2 is a licensed role, and the next lesson is about which corners software can and cannot occupy.