TRW & Co · Tax
UAE E-Invoicing Timeline: Phases, Deadlines and How to Prepare
The UAE e-invoicing timeline starts with large businesses: those with revenue of AED 50 million or more must appoint an accredited service provider by 30 October 2026 and go live on 1 January 2027. Smaller businesses follow on 1 July 2027 and government entities on 1 October 2027. Here is what changed, who is caught and how to prepare.
Key pointThe Ministry of Finance moved only the Phase 1 provider-appointment deadline, not the go-live date, so a large business signing with an ASP at the end of October 2026 has roughly two months to build, test and switch on.
At a glance
Phase 1 dates
Revenue of AED 50 million or more: appoint an accredited service provider by 30 October 2026 and go live on 1 January 2027.
Phase 2 dates
Revenue below AED 50 million: appoint a provider by 31 March 2027 and go live on 1 July 2027 under Ministerial Decision No. 244 of 2025.
Government entities
Mandatory from 1 October 2027 for transactions outside their sovereign capacity, completing the phased rollout.
Five-corner Peppol model
Structured invoices pass between accredited providers using the PINT AE specification, with tax data reported to the Federal Tax Authority.
Penalties apply
Cabinet Decision No. 106 of 2025 sets monthly penalties for late implementation and per-invoice penalties for invoices not issued electronically.
Swipe or scroll →
The short answer: the UAE e-invoicing timeline as of October 2026
As of October 2026, the UAE e-invoicing timeline has three mandatory phases. Businesses with annual revenue of AED 50 million or more must appoint an Accredited Service Provider (ASP) by 30 October 2026 and go live on 1 January 2027. Businesses below that figure must appoint an ASP by 31 March 2027 and go live on 1 July 2027. Government entities follow, with mandatory implementation from 1 October 2027.
A pilot started on 1 July 2026 for invited taxpayers, and any business can adopt the system voluntarily from that date. The Ministry of Finance has described the extension of the large-business ASP deadline as a final adjustment, and the 1 January 2027 go-live has not moved. Amendments in force from 1 October 2026 eased several operational rules, but did not change any appointment or go-live date.
This article explains what changed, who is caught, how the system works and what to do in the weeks that remain. It complements our practice page on VAT in the UAE.
What changed and when
The legal basis is two Ministerial Decisions published at the end of September 2025: Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System and Ministerial Decision No. 244 of 2025 on its implementation. Decision 243 sets the rules of the system; Decision 244 sets who is in scope and when.
Several developments followed. First, Cabinet Decision No. 106 of 2025 introduced administrative penalties for non-compliance. Second, in May 2026 the Ministry of Finance announced targeted amendments that moved the ASP appointment deadline for the largest businesses from 31 July 2026 to 30 October 2026, while keeping their go-live date, and widened the accreditation framework so that UAE providers can deliver solutions with third-party technology partners, including white-label arrangements.
Third, Ministerial Decision No. 197 of 2026, in force from 1 October 2026, amended Decision 243.
Decision 197 replaces Article 11 with a duty to keep e-invoices, e-credit notes and associated data for the period set by the Tax Procedures Law and produce them to the FTA on request; it repeals Article 12, which required businesses to notify the FTA of a system failure; it requires e-invoices and e-credit notes to be issued and transmitted within 14 business days of the transaction date; and it excludes transactions between members of the same VAT tax group for 24 months from 1 January 2027.
A separate decision, Ministerial Decision No. 168 of 2026, now allows only fully accredited providers to offer e-invoicing services. Our article on the October 2026 e-invoicing changes covers both decisions in detail.
The Ministry of Finance e-invoicing page hosts the guidelines, the mandatory field requirements and the list of accredited providers. Because the UAE e-invoicing timeline has already been adjusted once, check that page before relying on any date.
| Phase | Who | Appoint an ASP by | Mandatory from |
|---|---|---|---|
| Pilot and voluntary | Invited pilot taxpayers; any business opting in | Before joining | 1 July 2026 (voluntary) |
| Phase 1 | Businesses with revenue of AED 50 million or more | 30 October 2026 (extended from 31 July 2026) | 1 January 2027 |
| Phase 2 | Businesses with revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government | Government entities (outside sovereign activities) | Ahead of go-live | 1 October 2027 |
Who is affected and what is excluded
The system applies to persons conducting business in the UAE, whether or not they are VAT registered, and including non-resident businesses that transact here, unless an exclusion applies. Its focus is business-to-business and business-to-government transactions. Business-to-consumer transactions are outside the system until the Minister of Finance issues a further decision.
The decisions exclude certain transactions, including:
- activities of government entities acting in a sovereign capacity;
- international passenger air transport documented by electronic tickets, and related ancillary services;
- international transport of goods documented by airway bills, for a transitional period;
- financial services that are exempt or zero-rated for VAT;
- transactions between members of the same VAT tax group, for 24 months from 1 January 2027; and
- other transactions the Minister designates.
In practice, scope questions arise at the edges. A business that sells mainly to consumers but also invoices corporate customers will be in scope for the corporate sales. A company whose income is mostly exempt financial services may still issue in-scope invoices for other services. Treat the exclusions narrowly and record your reasoning, because the FTA will see the reported data and can query gaps.
The revenue test decides the phase. Groups should confirm how revenue is measured under Decision 244 for each legal entity and keep a record of the calculation, because the phase drives both the appointment deadline and the go-live date. Free zone, DIFC and ADGM entities are not carved out simply because of where they are licensed.
How the system works: five corners, Peppol and PINT AE
The UAE has chosen a decentralised continuous transaction control and exchange model, often called the "five-corner" model. The supplier (corner 1) sends invoice data to its ASP (corner 2), which validates it and transmits it to the buyer's ASP (corner 3), which delivers it to the buyer (corner 4). In parallel, tax data is reported to the Federal Tax Authority (corner 5).
Exchange runs over the OpenPeppol network, using a UAE data specification known as PINT AE that sets the mandatory fields. The Ministry has been clear that a PDF, a scanned copy, a Word file or an email attachment is not an e-invoice. Invoices must be issued in a structured, machine-readable format through an accredited provider, and each e-invoice or e-credit note must be issued and transmitted within 14 business days of the date of the transaction.
Businesses onboard with their chosen ASP and link the arrangement through EmaraTax. The Federal Tax Authority receives the tax data; the Ministry of Finance accredits providers and owns the policy.
Credit notes, corrections and outages
The system covers electronic credit notes as well as invoices, and the penalty regime treats a missing credit note the same way as a missing invoice. Businesses that issue frequent price adjustments, rebates or returns should map those flows as carefully as their sales invoices.
The original rules required a business to notify the Federal Tax Authority when its own or a recipient's system failed. Decision 197 of 2026 repealed that duty with effect from 1 October 2026, but it did not relax the 14-business-day issuing deadline, so an outage does not stop the clock on late-issue penalties. Changes to registered data, such as a new address or TRN detail, must still be passed to the ASP promptly. Build a catch-up procedure for outages and the data-change notice into one incident process with a named owner rather than leaving them to IT support.
Records and data location
As amended by Decision 197 of 2026, Article 11 of Ministerial Decision No. 243 of 2025 requires businesses to keep e-invoices, e-credit notes and associated data for the period set by the Tax Procedures Law and to produce them to the FTA on request. The new article does not say where the records must be held, and published commentary reads this as removing the earlier requirement to store them in the UAE. The retention and production duty remains, and so do other rules on where data can go.
Groups that run finance systems from a regional or global data centre should confirm where invoice data and archives sit, how quickly they can be retrieved, and how they will be returned if the ASP changes. This overlaps with data protection obligations covered on our page on cross-border data transfers, and should be addressed in the ASP contract.
E-invoicing is not just a tax project. It changes how invoices leave your ERP, how customers receive them and how credit notes, disputes and corrections are handled. The businesses that cope best appoint an owner from finance and IT jointly and test real invoices end to end with their main customers during the pilot window.
Steps to meet the UAE e-invoicing timeline
- Confirm your phase. Calculate revenue for each UAE entity on the basis set by Ministerial Decision No. 244 of 2025 and record which phase applies. Note non-resident group entities that transact in the UAE.
- Map invoice flows. List every system that issues invoices or credit notes, including billing platforms, ERPs and manual processes, and identify excluded transactions.
- Select and appoint an ASP. Choose from the Ministry's accredited list. Confirm the provider is on the accredited list on the day you sign, and compare connectivity with your ERP, where data is hosted, service levels, support for credit notes and pricing. Sign before your appointment deadline.
- Fix master data. Clean customer records, TRNs, addresses and product codes. Invalid or incomplete data is the most common cause of rejected e-invoices.
- Build and test. Configure the PINT AE fields, connect to the ASP and run test transactions with key customers and suppliers. Use the pilot or voluntary period if available.
- Update contracts and processes. Amend customer and supplier terms so that e-invoices are the valid invoice, set catch-up procedures for outages and data changes, and train staff.
- Go live and monitor. Switch on by your mandatory date, monitor rejections daily for the first weeks and keep evidence of compliance for audits.
Penalties for missing the UAE e-invoicing timeline
Cabinet Decision No. 106 of 2025 sets the administrative penalties. As summarised in published commentary on the decision, they include:
| Breach | Penalty |
|---|---|
| Failing to implement the system 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 |
| Failing to update the ASP about changes to registered data | AED 1,000 for each day of delay |
The same table lists AED 1,000 a day for failing to notify the FTA of a system failure. Decision 197 of 2026 repealed the underlying notification duty from 1 October 2026, so that penalty should no longer have an obligation to attach to, although FTA confirmation of the point would be welcome.
These amounts look modest beside the cost of a project, but the commercial risk is larger. A customer that cannot receive a compliant e-invoice may delay payment, and input VAT recovery depends on valid invoices. Penalties and their review sit within the wider FTA regime covered in our article on FTA audits, penalties and disputes.
An illustrative scenario
This scenario is illustrative only; it does not describe a real client.
A regional distribution group has three UAE entities: a mainland trading company with revenue well above AED 50 million, a free zone logistics company below it and a DIFC holding company that charges management fees. The finance team assumed all three would follow the January 2027 date.
On review, only the trading company falls in Phase 1. It must sign with an ASP by 30 October 2026 and go live on 1 January 2027. The logistics company follows Phase 2, with until 31 March 2027 to appoint a provider. The holding company's management fees are business-to-business supplies, so it is also in scope for Phase 2 despite being in the DIFC. Because the three companies are registered for VAT separately rather than as a VAT group, the tax group exclusion does not cover their intercompany charges.
The group chose a single ASP for all three entities, went live voluntarily with the smaller entities shortly after the trading company, and used the gap to fix customer master data. The lesson: test each entity separately against the UAE e-invoicing timeline and use the staggered dates to your advantage.
Risks and common mistakes
Treating the October deadline as soft
The Ministry extended the Phase 1 ASP deadline once and has said no further extensions will be granted. Penalties for late appointment run monthly. A business in Phase 1 that has not signed with an accredited provider by 30 October 2026 should treat it as an urgent board-level item, sign a contract with an accredited provider and document the plan to go live on 1 January 2027.
Assuming PDFs will do
Many businesses already send invoices by email and assume they are "electronic". Under the UAE system they are not. A valid e-invoice is a structured data file exchanged through accredited providers on the Peppol network with the PINT AE fields. Customers will increasingly reject PDFs from in-scope suppliers once their own systems switch over, so the commercial pressure may arrive before the legal one.
Weak contracts with the ASP
The ASP relationship is an outsourced, regulated data-processing arrangement. Contracts should cover the provider's accreditation status, service levels, data hosting location and sub-processors, availability during outages, liability for rejected invoices, exit and data return, and audit rights. Our pages on SaaS and technology contracts and data processing agreements explain the key clauses.
Leaving customers and suppliers out of testing
An e-invoice is only useful if the other side can receive it. Large customers may have their own onboarding requirements, purchase order references or mandatory fields, and suppliers sending you e-invoices need your correct Peppol identifier. Businesses that test only internally discover these problems after go-live, when payments start to slip. Agree a testing calendar with your top customers and suppliers, share identifiers early and confirm who will chase rejected invoices on both sides.
Ignoring non-resident and free zone entities
Groups often focus on their main operating company. Non-resident entities that transact in the UAE and free zone or financial free zone entities can also be in scope. Build an entity-by-entity register, record the phase for each and assign ownership.
Cross-border angle
Peppol is an international network, so UAE e-invoices can in principle be exchanged with businesses abroad that use it. Groups headquartered in Singapore, which also uses Peppol, may be able to reuse parts of their existing architecture. Suppliers in Bangladesh, India, the UK or China that invoice UAE customers should watch whether their customers begin asking for Peppol-compatible invoices, even where the supplier itself is outside the UAE system.
For Saudi-linked groups, the Saudi e-invoicing regime runs on a different, centralised model. Group systems built for Saudi Arabia will need separate configuration for the UAE rather than a simple extension.
What to do now
- Confirm each UAE entity's phase against the UAE e-invoicing timeline and record the basis.
- If you are in Phase 1, sign with an accredited provider before 30 October 2026.
- Run end-to-end tests with your largest customers before 1 January 2027.
- Clean master data and align it with your VAT registration records.
- Update customer and supplier contracts to recognise e-invoices and allocate failure risk.
- Document a catch-up procedure for outages so invoices still go out within 14 business days, and notify data changes to your ASP on time.
- Check how e-invoicing interacts with VAT returns and input VAT recovery.
The UAE Government portal and the Ministry of Finance page will announce any further changes to the UAE e-invoicing timeline. For a contract review of your ASP terms or a readiness check, contact TRW & Co. We coordinate with registered tax agents and technology advisers where needed.
Frequently asked questions
01When does e-invoicing become mandatory in the UAE?
It is phased. Businesses with revenue of AED 50 million or more must go live on 1 January 2027, after appointing an accredited service provider by 30 October 2026. Businesses below that figure go live on 1 July 2027, with a provider appointed by 31 March 2027. Government entities follow from 1 October 2027. A pilot and voluntary adoption began on 1 July 2026. Check the Ministry of Finance page for any later amendments.
02Is a PDF invoice an e-invoice in the UAE?
No. The Ministry of Finance has stated that unstructured formats such as PDFs, Word documents, images, scans and emails are not e-invoices. A UAE e-invoice is a structured, machine-readable file containing the PINT AE mandatory fields, issued and exchanged through accredited service providers over the Peppol network, with tax data reported to the Federal Tax Authority. Businesses can still send a PDF copy for convenience, but it will not be the legal invoice.
03Does e-invoicing apply to free zone and DIFC companies?
Yes, if they conduct business transactions in scope. The system is federal and applies to persons conducting business in the UAE, including those in free zones and the financial free zones. Exclusions are based on the type of transaction, such as certain financial services and international transport, not on where the business is licensed. Each entity should be assessed separately to confirm its phase.
04Do B2C transactions need e-invoices?
Not at present. Business-to-consumer transactions, and persons engaged exclusively in them, are outside the system until the Minister of Finance issues a further decision. Businesses with mixed customer bases still need e-invoicing for their business-to-business and business-to-government sales. Retailers should keep watching for announcements, because B2C reporting could be added later.
05What is an Accredited Service Provider?
An ASP is a provider accredited by the Ministry of Finance to validate, exchange and report e-invoices on behalf of businesses. Every in-scope business must appoint one by its phase deadline. The Ministry publishes the list of accredited providers, and amendments in 2026 allow UAE providers to work with third-party technology partners, including through white-label arrangements. From 1 October 2026 only fully accredited providers may offer services, so check the list on the day you sign and choose based on ERP integration, data hosting, service levels and contract terms.
06What are the penalties for not complying with e-invoicing?
Cabinet Decision No. 106 of 2025 sets the penalties. They include AED 5,000 for each month of delay in implementing the system or appointing a provider, AED 100 per invoice or credit note not issued electronically capped at AED 5,000 a month, and AED 1,000 a day for failing to update the provider on data changes. The table also lists a daily penalty for not notifying the FTA of a system failure, but that duty was repealed from 1 October 2026. Commercial consequences, such as delayed customer payments, can be larger.
Sources and official materials
- Ministry of Finance: eInvoicing — Guidelines, mandatory fields and accredited service providers
- Ministerial Decision No. 197 of 2026 amending Ministerial Decision No. 243 of 2025 — Data retention, repeal of system failure notice, 14-business-day rule and tax group exclusion
- Federal Tax Authority — VAT and e-invoicing reporting
- EmaraTax portal — Onboarding and ASP linkage
- UAE Government portal: Taxation — Government updates on tax programmes
General information only, current as at 27 October 2026. It is not legal advice and does not create a lawyer–client relationship. UAE law differs between the onshore jurisdiction, the DIFC, ADGM and the free zones, and changes frequently; check current official sources and take advice on the facts of your matter.
