Anyone billing 50 million dirhams or more a year in the United Arab Emirates has until 30 October 2026 to appoint an accredited e-invoicing service provider. A ticket bought by an individual falls outside the system, but the rest of what an event invoices does not.
What has happened
The UAE Ministry of Finance mandated e-invoicing through two ministerial decisions in 2025. Decision No. 243, signed by Mohamed bin Hadi Al Hussaini, Minister of State for Financial Affairs, builds the system. Decision No. 244 sets out who is covered and when.
The scope is broad. Article 3 of Decision 243 applies it to every person carrying out an economic activity in the State and to every business transaction, except what Article 4 excludes. The text refers to the State, not to a single emirate.
The exclusions in Article 4.1 are a closed list and almost all relate to aviation: the electronic ticket for international passengers, the Electronic Miscellaneous Document for ancillary services to those passengers, and the Airway Bill for goods, the last of these limited to 24 months from when the system takes effect. Also excluded are public entities exercising sovereign powers that do not compete with the private sector, and VAT-exempt or zero-rated financial services under Article 42 of the VAT Executive Regulation. The final clause leaves room for whatever the minister decides.
The mechanism is shared across both sides. Issuer and recipient each appoint an Accredited Service Provider (Art. 5.1), and the Ministry publishes the list of accredited providers (Art. 5.2). The invoice and the credit note are issued and transmitted through the system within 14 days of the "Date of Business Transaction" (Art. 6.5), defined as the earlier of the date the transaction occurred and the date of payment. An electronic credit note is mandatory in four cases: cancellation, reduction of the agreed consideration, full or partial refund, and administrative or numerical error (Art. 6.2). Invoices, credit notes and their data are stored within the State (Art. 11), and any system outage must be reported to the Authority within two working days (Art. 12).
The timetable sits in Decision 244 and has already shifted once. The pilot starts on 1 July 2026 (Art. 3.4), and voluntary implementation is possible from that date (Art. 4). For the large-revenue bracket, the original wording gave until 31 July 2026 to appoint a provider; Ministerial Decision No. (66) of 2026 pushed that to 30 October without touching the implementation date, and the Ministry's statement of 10 May 2026 confirms it.
| Subject | Appoint accredited provider | Implement the system |
|---|---|---|
| Revenue ≥ AED 50,000,000 | before 30 October 2026 | before 1 January 2027 |
| Revenue < AED 50,000,000 | before 31 March 2027 | before 1 July 2027 |
| Public entities | before 31 March 2027 | before 1 October 2027 |
And then there's Article 5.2 of Decision 244: Business-to-Consumer transactions are not subject to the system, and neither is anyone who deals exclusively in them, until the minister decides otherwise. Under the text's own definition, a B2C transaction is one running from a party carrying out an economic activity to a recipient who is a natural person not carrying out such an activity.
Why it matters
A ticket bought by an individual fits that definition. It's outside the system. That's as much as can be said, and it comes with the condition the text itself attaches: until the minister decides otherwise.
It doesn't follow that a promoter or a venue in the UAE is off the hook. Box office is the visible part of an event's money; almost everything beneath it is B2B and falls within the system: sponsorship, venue hire, production, the agency, ticket blocks sold to companies, and the ticketing platform's own commission invoiced to the promoter. An event can have almost every ticket outside the system and the whole of its invoicing inside it.
The date under most pressure isn't the January one either. Appointing a provider isn't an IT task: it's a purchase from a third party, drawn from the list the Ministry publishes, and it has to be closed within four weeks. Implementation comes after that.
Two details sit awkwardly with how an event actually works. The 14-day period in Article 6.5 runs from whichever comes first, the transaction or the payment, and at events payment is taken long before anything is delivered: the clock usually starts with the payment. And the credit note in Article 6.2 covers exactly what happens most here, cancellations and refunds. It's ground that Brazil's ticketing decree has also touched this year, there through consumer law and here through the invoice. None of this changes VAT or its rates: it changes the paperwork.
What to do about it
- Work out your bracket. Gross revenue for the last accounting period, according to the financial statements, determines whether the deadline is 30 October 2026 or 31 March 2027.
- Split B2C from B2B in the sales ledger, the same split that already forces a distinction between box office and everything else in ticket sales taxation. The former falls outside the system under Art. 5.2; the rest falls inside it.
- Contract from the official list. Only the accredited providers published by the Ministry count (Art. 5.2 of Decision 243).
- Measure how long it currently takes between taking payment and issuing each B2B invoice. If it exceeds 14 days, Article 6.5 requires a change of process.
- Close the loop on incidents: all four scenarios in Article 6.2 end in an electronic credit note. Also check where invoices are stored (Art. 11, within the State) and who notifies the Authority within the two working days required by Article 12.
- If you opt in voluntarily through the pilot, bear in mind that Article 4.3 of Decision 243 subjects voluntary participants to the whole system, except for administrative infringements and penalties.
- Ask your platform how it invoices its commission in the UAE: that invoice is B2B. It's one of the checks worth making when choosing a ticketing platform.