UAE E-Invoicing Integration

Ministerial Decision No. 243 of 2025 applies the e-invoicing system to any person conducting business in the UAE, for every business transaction, except the exclusions in its Article 4 (sovereign government transactions, international passenger air tickets and related documents, air cargo for 24 months, and certain exempt or zero-rated financial services). Implementation is phased by revenue under Ministerial Decision No. 244 of 2025, as shown in the key dates table.

In practical terms, you should plan for UAE e-invoicing if:

• You issue invoices to other businesses or to government entities in the UAE.
• You receive invoices from UAE suppliers: receiving and processing e-invoices is an obligation too, so accounts payable is affected, not just billing.
• You are a group with several UAE entities, free zone companies or branches invoicing from different systems.
• You are a foreign business with UAE operations or a UAE VAT registration.

Business-to-consumer (B2C) transactions are outside the system until the Minister decides otherwise (MD 244/2025, Art. 5(2)).

The UAE uses a decentralised continuous transaction control and exchange approach built on Peppol, often called the 5-corner model:

1. Corner 1, supplier: your ERP creates the invoice.
2. Corner 2, supplier's ASP: receives the invoice data, validates it against PINT AE and sends it over Peppol.
3. Corner 3, buyer's ASP: receives the invoice on the Peppol network.
4. Corner 4, buyer: gets a structured invoice in their own system.
5. Corner 5, Federal Tax Authority: receives the tax data reported by the ASPs.

Your business does not connect to the FTA directly. Your integration point is your ASP, which is why the quality of the ERP-to-ASP connector decides how smooth compliance feels day to day.

UAE e-invoices follow PINT AE, the UAE specification of the Peppol International (PINT) data model, expressed as UBL-based XML. The Ministry's mandatory fields document lists every required field. Key requirements include:

• Mandatory data fields for supplier and buyer, Tax Registration Numbers (TRN), invoice type, dates, line items, tax categories, rates and totals.
• Peppol participant identifiers for sender and receiver, so invoices route to the right ASP.
• Business rules and code lists for tax categories, units of measure, payment means and invoice type codes.
• Electronic credit notes linked to the original invoice.
• Specific invoice scenarios such as zero-rated exports, reverse charge, self-billing and disclosed agent billing, each with its own data requirements.

We build a connector that sits beside your ERP. Your team keeps posting invoices exactly as they do today.

1. Extract: read posted invoices and credit notes through your ERP's API, service layer, database views or export events.
2. Map: convert each document into PINT AE using a mapping table agreed with your finance team.
3. Pre-validate: check TRNs, Peppol IDs, tax categories, totals and rounding before anything leaves your network.
4. Submit: send to your ASP's API with retries, idempotency keys and secure credential storage.
5. Write back: store ASP status, message IDs and any rejection reason against the invoice in your ERP.
6. Receive: optionally pull inbound supplier e-invoices from your ASP into accounts payable.

ASP-agnostic by design. The ASP adapter is a separate module. If you switch providers, we replace the adapter, not your integration. For how this compares with buying a module from your ERP vendor, see ASP vs integrator vs ERP vendor.