UAE E-Invoicing and PINT AE: Getting Your ERP Ready

What changes, and when

The UAE is moving business invoicing onto a national e-invoicing system. Invoices between businesses, and between businesses and government, stop being documents one side emails to the other. They become structured data, validated and exchanged through Accredited Service Providers approved by the Ministry of Finance, with the tax data reported to the Federal Tax Authority.

The rollout is phased by size. These are the dates as published at the time of writing. Check the Ministry of Finance's current guidance before planning a project around them, because the first deadline has already moved once.

• Voluntary pilot: from 1 July 2026
• Businesses with annual revenue of AED 50 million or more: appoint an Accredited Service Provider by 30 October 2026 (extended from 31 July 2026), live from 1 January 2027
• Businesses below AED 50 million: appoint a provider by 31 March 2027, live from 1 July 2027
• Government entities: appoint a provider by 31 March 2027, live from 1 October 2027

What PINT AE actually is

PINT AE is the UAE's specification of the Peppol International invoice model: an XML invoice format with a defined set of fields and the rules those fields must satisfy. The Ministry's guidance lists 51 mandatory fields for a tax invoice and 49 for a commercial invoice. Businesses are identified by a Tax Identification Number taken from the first ten digits of their VAT registration number.

The practical consequence is that the PDF stops being the invoice. The invoice is the data, and it either passes validation or it does not. A document that looks right to a person but is missing the buyer's identifier or carries the wrong tax category is rejected before it reaches the customer.

The five-corner model, in plain terms

The system follows what is usually described as a five-corner model. Your system issues the invoice data. Your provider validates it and passes it to the buyer's provider, which delivers it into the buyer's system. The fifth corner is the tax authority, which receives the tax data from the exchange.

Your provider handles the network, the format and the reporting. What it cannot do is supply data your systems do not hold. The work that stays with you is producing complete and correct invoice data, sending it reliably, handling rejections, and receiving supplier invoices the same way.

Where ERP readiness actually stalls

The work that decides the timeline sits in the data and in the systems that issue invoices. It is routinely underestimated, because today's process appears to work - a person quietly fills every gap before the PDF goes out.

• Invoices issued from more than one place - the ERP, a separate billing tool, a spreadsheet template for one-off charges - each of which needs its own path to the provider
• Customer records without reliable tax registration numbers, structured addresses or consistent legal names
• Line items without the tax category, unit of measure or item classification the format requires
• Credit notes that cannot be traced back to the invoice they correct
• Several legal entities or a VAT group on one system, each of which issues under its own identifier
• Legacy or custom billing systems with no API, where there is nothing for a connector to connect to

Connecting your systems to a provider

Mainstream ERPs will often have a connector from the provider or the ERP vendor, and for a single, clean system that may be most of the answer. Custom platforms, older ERPs and businesses that invoice from several systems usually need an integration built for them: a mapping layer that turns each source into valid PINT AE data and submits it through the provider's API.

Build that layer the way any integration that touches money should be built. Queue outbound invoices so a provider outage delays them rather than losing them. Make submission idempotent, so a retry cannot issue the same invoice twice. Write the provider's response - accepted, or rejected and why - back into the system the finance team already works in. The same patterns come up in streamlining order management systems.

A realistic plan for the time left

For a business in the first cohort, the months before go-live are enough for a controlled project, but not for one that begins by discovering where its invoices come from. Cabinet Decision No. 106 of 2025 also sets administrative penalties for not meeting the requirements, so a late start has a direct cost as well as an operational one. The sequence below puts the discovery that decides everything else first.

• List every place an invoice or credit note is issued today, including the manual ones
• Map each source against the mandatory fields and record every gap
• Fix the master data - customer tax numbers, addresses, item tax categories - before building anything
• Select a provider, confirm how it connects to each source, and get sandbox access early
• Build and test the integration against real invoice history, including credit notes and exceptions
• Run in parallel for a period and train the finance team on handling rejections before the go-live date

Where custom software fits

We are not an Accredited Service Provider, and you do not need a software company to appoint one. Where we help is on your side of the exchange: mapping invoice data, building the integration between your ERP, billing tool or custom platform and your chosen provider, and modernising systems that cannot produce the data at all. The cloud ERP and invoicing platform we built for a D2C retailer generates every invoice from structured system data, which is the starting point this mandate assumes.

If your invoicing runs on something that will struggle to meet the format, our custom software development team can assess it and give you a written scope before you commit. This article is general guidance, not tax advice: confirm your obligations and dates with your tax adviser and the Ministry of Finance.