The UAE 5-Corner E-Invoicing Model and PINT AE Standard Explained
Understand the UAE five-corner e-invoicing model: supplier, supplier ASP, buyer ASP, buyer and FTA tax-data reporting, plus practical implementation checks.
Editorial disclosure: Pyalm publishes and maintains the products and free tools discussed on this site. Regulatory statements are linked to primary sources where applicable. No independent professional review is claimed unless a reviewer is explicitly named.
Why the UAE Chose a 5-Corner Model
Traditional Peppol exchange connects seller, seller's access point, buyer's access point and buyer. The UAE model adds FTA tax-data reporting as a fifth corner. It is not a clearance model in which every invoice must pass through the FTA before reaching its buyer.
The exchange and reporting responsibilities are distinct. Follow the MoF architecture and technical documents for the applicable workflow.
Official details are published by the UAE Ministry of Finance at mof.gov.ae.
The 5 Corners
Corner 1 — The Seller (Supplier)
Your business. Your accounting or ERP system generates the invoice in structured format and sends it to your ASP.
Corner 2 — The Seller's ASP (Accredited Service Provider)
The supplier's ASP validates and exchanges invoice data with the buyer's ASP and handles its required tax-data reporting.
Corner 3 — The Buyer's ASP
The buyer's ASP receives the structured invoice and delivers it to the buyer, with the required validation and reporting workflow.
Corner 4 — The Buyer
The buyer receives the invoice through its connected accounting workflow.
Corner 5 — The Federal Tax Authority
The FTA receives the required tax-data reports. Do not confuse tax-data reporting with the supplier-to-buyer invoice exchange.
What Is PINT AE?
PINT AE is the UAE specification for structured electronic invoices. Implementation should follow the current published specification and validation rules, not a fixed field count copied from an older article.
PINT AE Key Facts
- Exchange: Structured XML between the ASPs; agree your own system-to-ASP input format with the provider.
- Data: Use the current mandatory and conditional rules for the transaction being issued.
- Evidence: Request sample validation results, delivery statuses and reporting statuses.
- Source: Use the official MoF technical resources and the provider's current implementation documentation.
For the field-by-field breakdown, see the dedicated PINT AE mandatory fields checklist. This article focuses on the architecture.
What PINT AE Requires That Standard Invoices Do Not
| Requirement | PINT AE | Standard PDF Invoice |
|---|---|---|
| Structured XML format | Required | Not required |
| Validated invoice data | Follow current specification | A PDF alone does not establish this |
| Exchange and reporting statuses | Verify with the ASP | A PDF alone does not establish this |
| Connected workflow | Demonstrate end-to-end processing | Emailing a PDF is not equivalent |
What Your Accounting System Needs
Your accounting software must be able to:
- Capture the mandatory PINT AE fields from your business and client records
- Export invoice data in UBL 2.1 XML format
- Agree an interface with a currently accredited ASP for exchange and reporting
- Receive acknowledgements and handle rejections
Pyalm Books supports accounting workflows and is free during beta. Structured e-invoicing integration is in development. Ask for a current demonstration and written implementation scope rather than assuming roadmap capabilities are already live.
Explore Pyalm Books | UAE MoF E-Invoicing Technical Guidelines