Status as of 22 October 2026. This guide summarises the UAE Ministry of Finance decisions and published guidance listed in the sources at the end. It is general information, not tax or legal advice. Rules and guidance are still being updated, so confirm details with the Ministry of Finance, the Federal Tax Authority (FTA) or your tax adviser.
The UAE is replacing PDF and paper invoices between businesses with structured electronic invoices that travel over the Peppol network and are reported to the tax authority. For the largest companies the deadline is close: businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider (ASP) by 30 October 2026 and issue compliant e-invoices from 1 January 2027. Everyone else follows in 2027.
This guide explains what is required, who is in scope, what the penalties are, how to choose an ASP and what has to change in your ERP or accounting system. It is written for finance, tax and IT teams in the UAE, and for European and other foreign groups with a UAE VAT registration.
| Who | Appoint an ASP by | E-invoicing mandatory from |
|---|---|---|
| Any business (voluntary) | — | Optional from 1 July 2026 |
| Revenue of AED 50 million or more | 30 October 2026 (extended from 31 July 2026) | 1 January 2027 |
| Revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
What UAE e-invoicing is (and what it is not)
An e-invoice under the UAE system is not a PDF sent by email. It is a structured XML document that follows the UAE’s own Peppol specification, called PINT AE, and is exchanged between the seller’s and the buyer’s service providers over the Peppol network. The legal framework sits mainly in two Ministry of Finance decisions issued on 29 September 2025: Ministerial Decision No. 243 of 2025 (scope and obligations) and Ministerial Decision No. 244 of 2025 (implementation timeline).
The UAE uses a decentralised five-corner model. Businesses do not connect directly to a government portal. Instead, each business appoints an Accredited Service Provider that validates, sends and receives e-invoices, and the issuer’s provider reports the tax data to the Federal Tax Authority.
- 1. Supplier
ERP or invoicing system creates the invoice data - 2. Supplier’s ASP
Validates it, converts it to PINT AE and sends it over Peppol - 3. Buyer’s ASP
Receives the e-invoice and confirms receipt - 4. Buyer
Imports the e-invoice into its own system - 5. Federal Tax Authority
Receives the tax data reported by the ASP
If you already know Saudi Arabia’s FATOORA system, note the difference: ZATCA’s model connects taxpayers’ systems to a central government platform, while the UAE routes invoices through accredited private providers on Peppol. A group trading in both countries usually needs two separate integrations. For background on Saudi requirements, see our guide to cloud ERP and complex compliance in the Gulf.
Timeline and the AED 50 million revenue test
Ministerial Decision No. 244 of 2025 sets out a phased rollout. Voluntary adoption opened on 1 July 2026 for businesses that meet the technical requirements. The original deadline for large businesses to appoint an ASP was 31 July 2026. In 2026 the Ministry of Finance extended that deadline to 30 October 2026, but it did not move the go-live date of 1 January 2027. The later phases for smaller businesses and government entities were not changed by that extension.
How “revenue” is measured
The decision defines Revenue as the gross income earned by a person during its most recent accounting period, based on financial statements prepared under applicable UAE legislation. If financial statements are not available, other documentation acceptable to the FTA can be used. In practice, check each legal entity’s latest audited figures early, because the result decides whether you are in the January 2027 or the July 2027 phase.
The decision also provides that once the initial phases are complete, any person that becomes subject to the system must appoint an ASP and implement it. It does not set a separate deadline for businesses that cross the threshold or start trading later, so new or fast-growing businesses should take advice rather than assume a grace period.
Who is in scope, and what is excluded
The system applies to business-to-business (B2B) and business-to-government (B2G) transactions carried out by persons conducting business in the UAE. Business-to-consumer (B2C) transactions are excluded until further notice.
- In scope: UAE businesses issuing invoices for B2B and B2G supplies, including non-resident businesses that are registered for UAE VAT and must issue tax invoices under UAE VAT law.
- Excluded transactions: government activities carried out in a sovereign capacity, certain airline passenger services, and exempt financial services. Published guidance adds a temporary 24-month exclusion from 1 January 2027 for airline goods transport evidenced by an air waybill.
- Grace period, not exclusion: transactions between members of the same VAT group remain in scope but benefit from a 24-month grace period starting 1 January 2027.
- B2C: excluded until further notice, so retail invoices to consumers are not affected for now. Mixed businesses still need e-invoicing for their B2B and B2G sales.
What changes on your invoices
Most of the effort in an e-invoicing project goes into data, not technology. The Ministry of Finance published its Electronic Invoicing Guidelines, a mandatory fields list and guidance on choosing an ASP on 23 February 2026, followed by an updated Version 1.1 of the guidelines in June 2026. Key points:
| Requirement | What it means in practice |
|---|---|
| 51 mandatory fields for electronic tax invoices | Invoice, seller, buyer, totals, tax breakdown and line-level data must all be present and correctly formatted. Many ERPs do not hold every field today. |
| PINT AE format | Invoices must follow the UAE Peppol specification, including its specification identifier and code lists. |
| Participant identifier | Businesses are identified on Peppol with the scheme code 0235 followed by their tax identification number (the first 10 digits of the TRN). |
| Transaction type flags | Special cases such as free zone supplies, deemed supplies, margin scheme, summary invoices, continuous supplies, disclosed agent billing, e-commerce and exports must be flagged. |
| VAT in AED | VAT and total payable amounts must be shown in AED, converted at the UAE Central Bank rate where the invoice is in another currency. |
| Credit notes | Credit notes must also be issued electronically and need data such as a reason code that many systems do not capture. |
| Timing | E-invoices must be issued within 14 days of the taxable event, in line with UAE VAT invoicing rules. |
| One ASP per entity | Each entity appoints a single Accredited Service Provider to send and receive its e-invoices. |
| Record keeping | Electronic records must be retained and available to the authorities, generally for five years (seven for real estate), with longer periods possible during audits. Check your ASP’s and ERP’s data storage arrangements against Ministerial Decision No. 243. |
Penalties for non-compliance
Administrative penalties are set by Cabinet Decision No. 106 of 2025, which the Ministry of Finance published in November 2025. They apply once a business is required to comply under its phase.
| Violation | Penalty |
|---|---|
| Failing to implement e-invoicing or appoint an ASP on time | AED 5,000 for each month or part of a month of delay |
| Failing to issue and send an e-invoice | AED 100 per invoice, capped at AED 5,000 per calendar month |
| Failing to issue and send an electronic credit note | AED 100 per credit note, capped at AED 5,000 per calendar month |
| Issuer not informing the FTA of a system failure | AED 1,000 for each day of delay or part of a day |
| Recipient not informing the FTA of a system failure | AED 1,000 for each day of delay or part of a day |
| Not updating the ASP about changes to registered data | AED 1,000 for each day of delay or part of a day |
The fines are modest compared with the operational risk. The bigger exposure is customers who cannot pay invoices that are not delivered in the required format, and VAT input-tax questions if invoices are not compliant.
How to choose an Accredited Service Provider
Only providers accredited by the Ministry of Finance can transmit validated e-invoices and report them to the FTA. To be accredited, a provider must, among other conditions, be an active Peppol-certified service provider that has passed OpenPeppol conformance testing, have at least two years’ experience operating an e-invoicing system, and hold ISO/IEC 27001 (information security) and ISO 22301 (business continuity) certifications. The Ministry publishes and periodically updates the list of accredited and pre-approved providers, so check that list before you sign.
The Ministry’s own selection guidance highlights e-invoicing and Peppol experience, platform control, ERP integration, data protection and security certifications, service levels, pricing transparency, scalability and support for future updates. Questions worth asking every shortlisted provider:
- Is there a ready-made connector for our ERP version (for example SAP, Oracle, Microsoft Dynamics 365, Odoo or Tally), or do we need custom integration?
- How do you handle rejected invoices, validation errors and system outages, and how quickly will we be alerted?
- Can you receive invoices from our suppliers and deliver them into our accounts payable workflow, not just send our sales invoices?
- Where is our data stored, how long do you retain it, and how do we export it if we change provider?
- What is the full price: set-up and integration fees, subscription, per-document charges and charges for received invoices?
- Do you also support other countries we operate in, such as Saudi Arabia or European Peppol mandates?
ERP readiness checklist
These steps follow the order in which most projects run. Large businesses that have not started should treat the first four as urgent.
- Confirm your phase for each legal entity using the revenue definition above, and list every system that issues invoices or credit notes, including billing tools outside the main ERP.
- Map your invoice flows: domestic B2B, B2G, free zone, exports, intercompany, self-billing, deemed supplies, credit notes and any excluded transactions.
- Run a data gap assessment against the 51 mandatory fields. Typical gaps are buyer TINs and Peppol IDs, unit codes, transaction type flags, credit note reason codes and line-level AED tax amounts.
- Select and appoint an ASP from the Ministry’s list, and agree a written onboarding and testing plan with dates.
- Clean master data: collect TINs and Peppol participant identifiers from customers and suppliers, and fix addresses, units of measure and tax codes.
- Build or configure the integration between your ERP and the ASP, including status messages, rejections and failure handling.
- Update processes and controls: who fixes rejected invoices, how outages are reported to the FTA, how inbound e-invoices are approved and posted, and how records are archived.
- Test end to end with the ASP using real scenarios, ideally in the voluntary phase, and run a short parallel period before the mandatory date.
If your ERP is old or heavily customised, e-invoicing may be the trigger for a wider upgrade. Our guides to cloud ERP implementation costs and integrating legacy systems with cloud ERP cover the trade-offs. Do not let a long ERP replacement delay the e-invoicing deadline, though: an ASP connector on your current system is usually the faster route to compliance.
For European and other foreign groups with UAE operations
Non-resident businesses that are registered for UAE VAT and must issue UAE tax invoices are in scope, so a European company with a UAE VAT registration cannot assume the rules only affect local subsidiaries. Points to plan for:
- Peppol helps, but is not enough on its own. If your group already exchanges invoices over Peppol in Europe, the network is the same, but UAE invoices must follow PINT AE, use UAE identifiers and go through a UAE-accredited ASP.
- Revenue is tested per person. Check which UAE entity or registration the revenue test applies to and which phase each one falls into.
- Central ERP templates may need a UAE localisation for fields such as transaction type flags and AED tax amounts.
- Your UAE customers will start asking for your Peppol identifier. Collecting your suppliers’ identifiers works the same way in reverse.
Common mistakes to avoid
- Treating e-invoicing as an IT task. Tax, finance, sales and procurement all own part of the data.
- Planning only for sales invoices. Your accounts payable team must also receive and process e-invoices from suppliers.
- Forgetting credit notes, self-billing and invoices raised outside the main ERP.
- Choosing an ASP on price alone without checking ERP integration, outage handling and data export.
- Assuming the October 2026 extension moved the January 2027 go-live date. It did not.
Frequently asked questions
When does e-invoicing become mandatory in the UAE?
From 1 January 2027 for businesses with revenue of AED 50 million or more, from 1 July 2027 for businesses below that threshold, and from 1 October 2027 for government entities. Voluntary adoption has been possible since 1 July 2026.
What is the deadline to appoint an Accredited Service Provider?
30 October 2026 for businesses with revenue of AED 50 million or more, after the Ministry of Finance extended the original 31 July 2026 date. It is 31 March 2027 for smaller businesses and government entities.
Does UAE e-invoicing apply to B2C sales?
No. B2C transactions are excluded until further notice. The mandate covers B2B and B2G transactions.
Can I keep sending PDF invoices after the deadline?
Not as your legal invoice for in-scope transactions. The legal invoice becomes the structured e-invoice exchanged through your ASP. Published guidance allows a human-readable invoice to be shared alongside it during a transitional period, but it does not replace the e-invoice.
What are the penalties if we are late?
Under Cabinet Decision No. 106 of 2025, failing to implement the system or appoint an ASP on time costs AED 5,000 for each month or part of a month of delay, and failing to issue an e-invoice costs AED 100 per invoice, capped at AED 5,000 per month. Other penalties are listed in the table above.
Do foreign companies need to comply?
Non-resident businesses registered for UAE VAT that must issue UAE tax invoices are in scope. Foreign companies without a UAE VAT registration that only buy from UAE suppliers are not issuers, but their UAE suppliers will need correct buyer details.
Is UAE e-invoicing the same as Saudi Arabia’s FATOORA?
No. Both aim to digitise invoicing, but Saudi Arabia connects taxpayers to ZATCA’s central platform, while the UAE uses a Peppol-based five-corner model with accredited private service providers. Data formats, identifiers and timelines are different.
The bottom line
For businesses with revenue of AED 50 million or more, the next step is immediate: appoint an accredited service provider by 30 October 2026 and use the remaining weeks for data clean-up and testing before 1 January 2027. Smaller businesses have until 31 March 2027 to appoint a provider, but the data and process work takes months, so starting now is the cheaper option.
Sources
- UAE Ministry of Finance, Ministerial Decision No. 244 of 2025 on the Implementation of the Electronic Invoicing System
- UAE Ministry of Finance, Cabinet Decision on violations and penalties for e-invoicing
- UAE Ministry of Finance, Accreditation of eInvoicing Service Providers
- KPMG, UAE: framework, scope and implementation of the e-invoicing system and technical guidance on mandatory e-invoicing fields
- Deloitte Middle East, UAE e-invoicing: ASP appointment deadline extended, but go-live remains 1 January 2027
- EY, UAE Ministry of Finance publishes Cabinet Decision on penalties for noncompliance with e-invoicing
- Alvarez & Marsal, UAE Electronic Invoicing Guidelines (February 2026): regulatory clarifications
- PwC Middle East, UAE e-invoicing updates (2026)