UAE E-Invoicing: Deadlines and What Your Software Must Do

The UAE Ministry of Finance is introducing a national electronic invoicing system for business-to-business and business-to-government transactions. Instead of emailing a PDF, your system sends structured invoice data through an Accredited Service Provider, which passes it on to the buyer and to the tax authority's systems.

The format is based on Peppol, the same standard used in parts of Europe and Asia. In the UAE it is called PINT AE. If your invoices today are PDFs generated from Word, Excel, or a basic template, they will need to come from a system that can output structured data.

Published guidance sets the first milestone at 30 October 2026: businesses with annual revenue of AED 50 million or more must have appointed an ASP. Mandatory use for that group starts on 1 January 2027.

Smaller VAT-registered businesses are expected to follow in later phases. Public sources disagree on those dates, with some pointing to 2027 and others to a wider rollout after that. Treat any date for smaller businesses as provisional until the Ministry of Finance or the Federal Tax Authority confirms it for your revenue band.

Reported penalties are AED 5,000 for each month of delay in appointing an ASP or implementing the system. Even if you are in a later phase, the work is the same, and starting early is cheaper than rushing.

Produce invoices and credit notes as structured data in the PINT AE format, not only as a printable document.

Hold clean master data: customer legal names, tax registration numbers, addresses, product codes, and tax categories. Most failed submissions come from missing or inconsistent master data, not from the connection itself.

Connect to an Accredited Service Provider through its API or a supported integration, and handle accepted, rejected, and pending statuses.

Keep an audit trail and archive invoices. Public guidance mentions a five-year retention period.

1. Confirm which phase applies to your revenue band, using official sources.

2. List every system that issues invoices: accounting package, ERP, POS, billing portal, spreadsheets.

3. Clean your customer and product master data, especially tax registration numbers and units of measure.

4. Ask your software vendor in writing whether and when they will support an ASP connection.

5. Shortlist ASPs and compare integration options, pricing, and support.

6. Map your invoice fields to PINT AE and note gaps, such as missing reference numbers or tax codes.

7. Test with real invoice samples, including credit notes and corrections, before go-live.

8. Train the finance team on rejected-invoice handling and corrections.

If your accounting package already announced ASP support, upgrading is usually the fastest route. If you run a custom or heavily modified system, an integration layer that sits between your software and the ASP is often cheaper than a rebuild.

Replace the system only when it cannot hold structured data at all, or when the vendor has no plan to support the mandate. We cover the wider trade-offs in our custom versus off-the-shelf guide.

We build invoicing modules, ERP integrations, and data clean-up tools for UAE businesses. A typical first step is a short review of how invoices are created today and which system owns the data. From there we recommend the smallest change that meets your deadline.

If you are close to the 30 October date, say so when you contact us. We will tell you honestly what can be done in the time left.