UAE E-Invoicing Integration

The UAE Ministry of Finance has set out an e-invoicing system that covers business-to-business (B2B) and business-to-government (B2G) transactions. The rollout is phased: larger businesses (measured by revenue) are brought in first, with other businesses and government entities following in later phases announced by the Ministry.

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

• You are a business operating in the UAE that issues invoices to other businesses or to government entities.
• You receive invoices from UAE suppliers. Receiving through Peppol is part of the model too, so your accounts payable process 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.

B2C transactions are not part of the initial scope. Specific transaction types may be excluded or have special rules. Confirm your exact obligations against the current ministerial decisions linked in the sources below, or with your tax adviser.

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. That is why the quality of the ERP-to-ASP connector determines 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. Key requirements include:

• Mandatory data fields covering supplier and buyer details, Tax Registration Numbers (TRN/TIN), invoice type, dates, line items, tax categories, rates and totals in AED.
• 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.
• Credit notes issued electronically and 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.
• Record keeping of e-invoices and responses for the statutory retention period.

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 TINs, 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.