Is Your ERP Ready for UAE E-Invoicing? A Practical Readiness Checklist

ERP e-invoicing readiness in the UAE is no longer a future project. Under Ministerial Decision No. 244 of 2025, as amended by Ministerial Resolution No. 66 of 2026, businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider (ASP) by 30 October 2026 and issue structured e-invoices from 1 January 2027. Everyone else follows six months later. Whichever group you are in, your ERP is where every e-invoice will start, so it is where most of the readiness work sits.

This guide is vendor-neutral. Whether you run SAP Business One, Oracle NetSuite, Microsoft Dynamics 365, Odoo or another system, the same questions apply: is your data complete, can the system produce the right document types, and can it talk reliably to one ASP?

As of 18 October 2026. Always check the Ministry of Finance e-invoicing hub for the latest updates.

The UAE e-invoicing timeline your ERP must meet

Voluntary adoption and the pilot phase opened on 1 July 2026. Note that the Ministry's Guidelines (version 1.1, June 2026) still show the earlier 31 July 2026 ASP date; the later Ministerial Resolution No. 66 of 2026 moved it to 30 October 2026, and the legal text takes precedence.

What changes for your ERP

The UAE uses a Peppol-based "5-corner" model. Your ERP (corner 1) sends invoice data to your ASP (corner 2), which validates it and exchanges it with the buyer's ASP (corner 3) and the buyer (corner 4). Tax data is reported to the Federal Tax Authority platform (corner 5).

Three practical consequences follow:

• A PDF is no longer an e-invoice. The required format is structured XML following the PINT AE specification. Scans, PDFs and emailed invoices do not count, and there is no QR-code requirement.
• Scope covers B2B and B2G. Business-to-business, business-to-government, government-to-business and government-to-government transactions are in scope. Business-to-consumer sales are currently out of scope.
• Intra-VAT-group transactions are in scope, but the Guidelines give them a 24-month grace period from 1 January 2027.

Some sectors are excluded under Ministerial Decision No. 243 of 2025, including certain international passenger air transport with e-tickets, VAT-exempt or zero-rated financial services, and (for 24 months) international air cargo with an airway bill. Check whether any of your revenue streams fall in these categories before you design your ERP mapping.

ERP e-invoicing readiness UAE checklist

Use the checklist below as a structured gap review. Each item should have an owner, a status and a target date.

1. Master data and identifiers

E-invoicing fails most often on data, not technology.

• Your own identifiers. Your Tax Identification Number (TIN) is the first 10 digits of your TRN. Your Peppol participant ID is "0235" followed by the TIN. Both need to be stored correctly in the ERP company settings.
• Customer master. Every B2B and B2G customer needs a valid TRN (where VAT-registered), legal name and address in the structured fields your ERP uses. Free-text addresses and missing TRNs will cause rejections.
• Supplier master. You will receive e-invoices as well as send them, so supplier records need the same clean-up.
• Item and tax codes. Map each product and service to the correct VAT treatment (standard, zero-rated, exempt, out of scope, reverse charge).

2. PINT AE data fields

PINT AE defines the fields an e-invoice must carry. Compare it against your current invoice template and identify:

• fields you already capture but print only on the PDF;
• fields captured inconsistently (for example, units of measure or currency codes);
• fields not captured at all, which may need new ERP fields or custom extensions.

This mapping exercise is usually the longest workstream. Start it before you sign with an ASP, because it will shape your integration scope.

3. Document types and credit notes

The Guidelines set out clear rules that your ERP workflows must respect:

• An e-credit note is required whenever output tax is reduced. Credit notes can be partial and can reference more than one original invoice.
• A negative invoice is not allowed; a negative summary invoice must be issued as a credit note.
• There is no provisional invoice type. Pro-forma documents stay outside the e-invoicing flow.

Review how your ERP handles returns, discounts after invoicing, rebates and cancellations. Many systems allow users to post negative lines on an invoice; that practice will need to change.

4. Integration with one ASP

A business may appoint only one ASP. Your ERP integration therefore needs to be robust:

• Decide between a native connector (if your ERP or ASP offers one), middleware, or an API build.
• Define how validation errors from the ASP flow back to users in the ERP, and who fixes them.
• Plan for failure. If your system or your ASP's system fails, Ministerial Decision No. 243 of 2025 requires the failure to be notified within two business days.

The Ministry publishes the official list of accredited providers; as of 16 October 2026 it showed 67 accredited ASPs. Choose from that list only.

5. Timing of issue and transmission

For VAT-registered businesses, e-invoices and e-credit notes must be issued and transmitted within the timelines in the VAT Law. For persons who are not VAT-registered, the timeframe is 14 days from the transaction date. Your ERP posting rules, approval workflows and batch schedules should be checked against these limits. A month-end batch that holds invoices for weeks will not work.

6. Archiving and record retention

E-invoicing records must be stored for the period required by the Tax Procedures Law and be retrievable for the FTA, wherever your servers are. The Guidelines refer to five years in general and seven years for real estate, with longer retention where an audit or dispute is open. Check that your ERP, your ASP and any document store between them together meet this, including after a system migration.

7. Onboarding on EmaraTax

Onboarding is started by the business, not the ASP. In EmaraTax, the business selects the e-invoicing tile, chooses its ASP and proceeds. Each member of a tax group onboards separately, so groups need a plan for every entity.

Penalties for getting it wrong

Cabinet Decision No. 106 of 2025 sets the e-invoicing penalties. Key amounts include:

• AED 5,000 per month (or part month) for failing to implement the system, including not appointing an ASP on time;
• AED 100 per e-invoice or e-credit note not issued or transmitted on time, capped at AED 5,000 per calendar month;
• AED 1,000 per day for failing to notify a system failure or changes to registered data on time.

A Ministry presentation from October 2026 refers to a replacement decision, but we could not find its published text, so the figures above are those in the decision currently shown as active.

A realistic project plan

For a mid-sized business, a sensible sequence is:

1. Weeks 1–3: scoping and gap analysis against PINT AE; master data audit.
2. Weeks 3–6: ASP selection and contract; integration design.
3. Weeks 6–12: ERP configuration, field extensions and connector build.
4. Weeks 10–14: testing with the ASP, including credit notes, rejections and failure scenarios.
5. Before go-live: EmaraTax onboarding, user training and a cut-over plan.

Businesses in the AED 50 million band are already against a tight deadline. Those below it have until 31 March 2027 to appoint an ASP, but should not wait: the data clean-up alone can take months.

Talk to GULF CONSULT

GULF CONSULT implements and configures SAP Business One, NetSuite, Dynamics 365 and Odoo, and runs vendor-neutral e-invoicing readiness reviews for UAE businesses. Book a free 30-minute consultation to review your ERP against the 2027 requirements: email [email protected], call +971 58 600 4833 or message us on WhatsApp.