UAE e-invoicing readiness means your ERP can produce every B2B and B2G invoice and credit note as structured data with the Ministry of Finance's mandatory fields, send it through your Accredited Service Provider (ASP) on the Peppol network, receive supplier e-invoices the same way, and handle rejections and corrections. The work is mostly data quality and integration, not new accounting.
The dates and rules below were checked on the UAE Ministry of Finance website (mof.gov.ae) in October 2026. The programme is still being rolled out, so treat every date as subject to official announcements and check the Ministry's news page before you lock a plan. This is a planning guide for finance and IT teams, not tax advice.
What is the UAE e-invoicing system?
It is a mandatory system in which invoices between businesses, and between businesses and government, are exchanged as structured electronic data through accredited providers rather than as PDFs or paper. On 29 September 2025 the Ministry of Finance announced Ministerial Decisions No. 243 and No. 244 of 2025, which set the scope and timeline. The Ministry states the system is based on the international OpenPeppol standard and applies to B2B and B2G transactions, with specified exclusions.
The key features the Ministry has published:
- Both sides use an ASP. The supplier and the buyer each appoint an Accredited Service Provider, and obligations are met through that provider. The Ministry publishes the list of accredited providers; its 10 May 2026 announcement said 32 providers had been approved.
- Every in-scope transaction needs an e-invoice containing the data fields the Ministry prescribes, and electronic credit notes are required for cancellations, reductions in price, refunds and corrections.
- Data flows to the tax authority as part of the exchange. This is often described as a decentralised five-corner model: supplier (1), supplier's ASP (2), buyer's ASP (3), buyer (4), with invoice data reported to the Federal Tax Authority (5).
The Ministry has also published technical documents on its website, including the UAE Electronic Invoice Mandatory Fields (version 1.0, 23 February 2026) and the UAE Electronic Invoicing Guidelines (version 1.1, 1 June 2026). Use the latest versions on mof.gov.ae as your specification, not a summary from a blog, including this one.
What is the UAE e-invoicing timeline?
As of October 2026, the Ministry of Finance timeline is as follows. The large-business ASP deadline was moved from 31 July 2026 to 30 October 2026 by the amendment announced on 10 May 2026; the go-live date did not change.
| Group | Appoint an ASP by | Go live |
|---|---|---|
| Pilot (selected taxpayers) | Not applicable | 1 July 2026 |
| Voluntary adopters (any business) | Before starting | From 1 July 2026 |
| Businesses with annual revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Businesses with annual revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| In-scope government entities | 31 March 2027 | 1 October 2027 |
Check with your adviser how revenue is measured for the threshold under the Ministerial Decision, especially for groups with several entities. If you are close to AED 50 million, plan for the earlier date.
If the integration between your ERP and an ASP is the part you need help with, our ERP integration services page explains how we connect finance systems to external platforms, including testing and error handling.
What changes inside your ERP?
Your accounting logic mostly stays the same. What changes is how invoices leave and enter the system, and how strict the data has to be.
| Area | Today (typical) | After e-invoicing |
|---|---|---|
| Invoice output | PDF emailed or printed | Structured data sent to your ASP, with a human-readable copy if you still want one |
| Data quality | Missing fields fixed by hand on the PDF | Missing or invalid fields cause rejection, so they must be fixed at source |
| Customer master | Name and address, TRN sometimes missing | Complete, validated identifiers for every in-scope customer |
| Credit notes | Sometimes a negative invoice | A proper electronic credit note referencing the original invoice |
| Supplier invoices | Received by email, keyed in or scanned | Received as structured data from your ASP, ready to match to purchase orders |
| Status | Sent means done | Each document has a status (sent, delivered, rejected) that someone must monitor |
| Archive | Files in a folder | Retained data plus the exchange record from the ASP |
How do you connect your ERP to an Accredited Service Provider?
There are three common routes. Pick based on how many invoices you issue, how old your ERP is, and how much control you want over error handling.
| Route | How it works | Suits | Watch out for |
|---|---|---|---|
| Vendor connector | Your ERP vendor or partner provides a ready connection to one or more ASPs | Packaged ERPs with an active UAE partner | Confirm it covers inbound invoices and rejections, not just outbound |
| ASP portal or file upload | You export invoice files and the ASP converts and sends them | Low volumes, short-term bridge | Manual steps, and weak links between ERP records and the exchange status |
| Direct API integration | Your ERP calls the ASP's API, and status updates flow back automatically | Custom or heavily customised ERPs, higher volumes | Needs proper logging, retries and monitoring |
Whichever route you choose, insist that rejection messages flow back into the ERP against the original document. A rejected invoice that only appears in an ASP portal is easy to miss, and an unsent invoice is an unpaid one. For the general design choices behind connections like this, see our guide to system integration approaches.
If your current ERP is old, undocumented or cannot expose invoice data cleanly, it may be easier to put a small integration service in front of it than to modify the core. Our legacy software modernization page explains that pattern.
UAE e-invoicing ERP readiness checklist
Work through this in order. Assign an owner and a date to each line.
Governance
- Confirm which entities are in scope and which phase each falls into
- Name a business owner for e-invoicing (usually finance) and a technical owner
- Shortlist and appoint an ASP before your deadline, and confirm the ASP is on the Ministry's accredited list
Data
- Compare your invoice data against the Ministry's published mandatory fields and list every gap
- Complete and validate customer identifiers (including TRNs) for every in-scope customer
- Clean up item descriptions, units of measure and tax codes so each line carries valid values
- Decide how you will collect identifiers for new customers at onboarding, so gaps do not return
Process
- Replace negative invoices with credit notes that reference the original invoice
- Define who monitors rejected documents each day, and how fast they must be fixed
- Agree how inbound supplier e-invoices are matched to purchase orders and approved
- Update the customer communication for invoice delivery
System
- Choose the connection route (vendor connector, portal, or API)
- Build or configure outbound, inbound and status flows
- Add logging so every document can be traced from ERP record to ASP status
- Test with your ASP: standard invoices, credit notes, foreign currency, zero-rated lines and deliberate errors
- Rehearse the switch-over, including invoices raised on the last day before go-live
Worked example (illustrative)
A distribution business with two UAE entities, one above and one below AED 50 million, issues several thousand invoices a month from a packaged ERP that has been customised over the years. A gap review against the mandatory fields finds that many customer records lack complete identifiers and that credit notes are raised as negative invoices in one entity.
The plan: appoint one ASP for both entities so the integration is built once. Fix the customer master first, with sales teams responsible for missing data. Change the credit note process. Build a direct API connection with a status table inside the ERP, and a daily rejection report for the credit control team. Go live with the larger entity on the earlier date, then switch the smaller entity on using the same integration well before its own deadline.
The numbers and structure here are invented to show the sequence. Your scope depends on your data and systems.
When is building your own integration not the right approach?
If your ERP vendor already offers a supported connector for UAE e-invoicing that covers outbound, inbound and status handling, use it. Building a parallel custom integration adds code you must maintain whenever the Ministry updates its specifications. Custom integration makes sense when your ERP is custom, heavily modified, or has no vendor route, or when you need features the connector lacks, such as linking statuses to your own workflow.
Likewise, if you issue very few B2B invoices, an ASP's portal may be enough for now. Plan to revisit it if volumes grow.
How to start
Start with a gap review this month, whatever your phase:
- Download the latest mandatory fields document and guidelines from mof.gov.ae
- Export a sample of recent invoices and credit notes from each entity
- Mark every field you cannot fill from the ERP today
- List your systems that create invoices, including e-commerce and billing tools outside the ERP
- Note your ASP shortlist and their integration options
Capture the results in a short brief; our software requirements brief template gives you a structure. For the wider picture of what a UAE ERP must handle, read ERP software in the UAE, and if Arabic output is part of your scope, see Arabic and English ERP.
Then discuss the project with us. Timeline Digital builds 2 to 3 key modules as a free pilot before the full project starts; for e-invoicing, that can be the outbound and inbound flows themselves, tested against your own data.