UAE E-Invoicing 2027: What Your Software and ERP Must Do

From 1 January 2027, large UAE businesses will no longer be able to send a PDF invoice and call it done. Invoices will have to be issued as structured electronic data, exchanged through an accredited provider, and reported to the Federal Tax Authority. Accounting teams are hearing about it — but most of the work lands on your software: the ERP, billing platform or custom system that actually produces your invoices.

The timeline

Who	Appoint an ASP by	Go live
Revenue of AED 50 million or more	30 October 2026	1 January 2027
Revenue below AED 50 million	31 March 2027	1 July 2027
Government entities	—	1 October 2027

The Ministry of Finance moved the large-business ASP deadline from 31 July to 30 October 2026, but the go-live date did not move. A voluntary pilot has been open since 1 July 2026. Dates can change, so check the latest Ministry of Finance guidance.

How the UAE model works

• Peppol "5-corner" model — you send an invoice to your Accredited Service Provider (ASP), which delivers it to your customer's ASP and reports the data to the Federal Tax Authority.
• PINT AE format — invoices are structured XML following the UAE's Peppol specification, not PDFs.
• Scope — business-to-business and business-to-government invoices first; business-to-consumer sales are currently excluded.
• Accredited providers only — you connect through an ASP accredited by the Ministry of Finance, not directly to the government.

What your software needs to do

1. Capture the right data. Buyer and supplier identifiers, tax registration numbers, item classification, VAT breakdown and payment terms — every mandatory field, on every invoice. Missing master data is the most common gap.
2. Generate structured invoices. Produce PINT AE-compliant data, or hand clean data to the ASP to convert.
3. Integrate with your ASP. Usually through the ASP's API, so invoices go out automatically when they are posted — no manual uploads.
4. Handle responses. Track delivery, rejections and errors back into the system, so finance sees the status of every invoice.
5. Credit notes and corrections. These follow the same rules and are often forgotten in testing.
6. Receive e-invoices. Supplier invoices will arrive as structured data too — a chance to automate accounts payable.
7. Keep an audit trail. Store what was sent, when, and the response received.

Where businesses get stuck

• Custom and legacy systems with no API and incomplete customer master data.
• Several systems issuing invoices — for example ERP, a POS back office and a project billing tool — each needing its own integration.
• Leaving testing too late. ASP onboarding, integration and testing all take time.

A practical readiness plan

1. List every system that issues or receives invoices.
2. Check each against the mandatory data fields and fix master data.
3. Choose and appoint an ASP before your deadline.
4. Build and test the integration, including rejections and credit notes.
5. Join the pilot or run a parallel test before go-live.

How Skyline helps

Skyline is a software development company, not an ASP or a tax adviser — our part is the software. We extend ERP, billing and custom systems to capture the required data, build and test the integration with your chosen ASP, and add status tracking so finance can see every invoice. See our ERP development guide and software development services, or talk to us about your systems.