e-Invoicing
UAE e-Invoicing Requirements: What a Business Must Have in Place
The UAE e-invoicing requirements a finance team can act on: who is in scope, the 51 mandatory data fields, storage duties, deadlines and penalties.
e invoicing uae requirements
Every person conducting business in the UAE must issue invoices as structured XML exchanged through an Accredited Service Provider, whether or not they are registered for VAT. The Ministry of Finance prescribes 51 mandatory fields for an electronic tax invoice and 49 for a commercial one. Businesses with revenue of AED 50 million or more appoint a provider by 30 October 2026 and go live on 1 January 2027.
Basis: UAE Ministry of Finance
- Mandatory fields, electronic tax invoice
- 51
- Mandatory fields, commercial electronic invoice
- 49
- Revenue threshold splitting phase 1 from phase 2
- AED 50,000,000
- Deadline to appoint a provider, revenue AED 50m or more
- 30 October 2026
- Window to transmit an invoice through the system
- 14 days from the date of the business transaction
UAE Electronic Invoice mandatory fields, version 1.0, 23 February 2026
UAE Electronic Invoice mandatory fields, version 1.0, 23 February 2026
Article 5(1), Ministerial Decision No. 244 of 2025
Ministerial Decision No. 66 of 2026, replacing Article 5(1)(a) of MD No. 244 of 2025
Article 6(5), Ministerial Decision No. 243 of 2025
#Who has to comply, and from which date
The obligation is drawn by activity, not by tax registration. Article 3 of Ministerial Decision No. 243 of 2025 applies the Electronic Invoicing System to "any Person conducting Business in the State in respect of every Business Transaction", subject only to the exclusions in Article 4. There is no revenue floor and no VAT condition: a person under the VAT registration threshold, or registered for corporate tax only, is still in scope.
Revenue does not decide whether you are in scope. It decides when. Article 5(1) of Ministerial Decision No. 244 of 2025 splits the population at AED 50,000,000 of revenue, which Article 1 of that decision defines as gross income for the most recent accounting period per your financial statements — not a fixed calendar year. A person in scope who is not required to register for any tax must still register with the Federal Tax Authority to obtain a Tax Identification Number, because the TIN is what identifies you on the network.
| Who | Appoint an Accredited Service Provider by | Go live by |
|---|---|---|
| Person with revenue of AED 50,000,000 or more | 30 October 2026 | 1 January 2027 |
| Person with revenue under AED 50,000,000 | 31 March 2027 | 1 July 2027 |
| Government entity | 31 March 2027 | 1 October 2027 |
| Anyone, voluntarily, or by invitation to the pilot | From 1 July 2026 | From 1 July 2026 |
#The data requirement: 51 mandatory fields, and where they come from
This is the part that turns a policy into a systems project. An electronic invoice is not a PDF with a logo on it — it is an XML document that must validate against the UAE's Peppol specification, PINT AE, whose UAE-specific requirements sit in the Data Dictionary referred to in Article 7(4) of Ministerial Decision No. 64 of 2025. Article 7 of Ministerial Decision No. 243 of 2025 delegates the field list to the Ministry, which published it on 23 February 2026 as UAE Electronic Invoice mandatory fields, version 1.0.
There are two field sets. An electronic tax invoice — what a VAT registrant issues for a taxable supply — carries 51 mandatory fields. A commercial electronic invoice — used where the VAT Decree-Law does not require a tax invoice, for example exempt or out-of-scope supplies, or supplies by a person not registered for VAT — carries 49. The lists differ in three places only: the tax invoice takes the buyer's tax identifier and tax scheme code where the commercial invoice takes the buyer's legal registration identifier and its type, and the tax invoice adds two line-level fields, the VAT line amount in AED and the invoice line amount in AED.
| Field group | Electronic tax invoice | Commercial electronic invoice |
|---|---|---|
| Invoice details (number, date, type code, currency, transaction type flags, payment due date, business process type, specification identifier, payment means) | 9 | 9 |
| Seller details (name, electronic address, electronic identifier, legal registration identifier and type, tax identifier, tax scheme, address, city, country subdivision, country) | 11 | 11 |
| Buyer details | 9 | 9 |
| Document totals (line net total, total without tax, total tax, total with tax, amount due) | 5 | 5 |
| Tax breakdown (category taxable amount, category tax amount, category code, category rate) | 4 | 4 |
| Invoice line (identifier, quantity, unit of measure, net amount, net and gross price, base quantity, item tax category and rate, item name and description, plus AED line amounts on a tax invoice) | 13 | 11 |
| Total mandatory fields | 51 | 49 |
Your identity on the network: TIN and the 0235 identifier
Your participant identifier is your Tax Identification Number, and the Ministry states the TIN is the first 10 digits of your 15-digit TRN. The seller electronic identifier is the fixed value 0235 for businesses registered in the UAE; the identifier and the electronic address together form the endpoint your provider registers on the network. If you are in a tax group, the Ministry is explicit that your TIN is the first 10 digits of your own TRN, not the group representative's.
One caveat worth carrying into a systems design. The mandatory-fields document of February 2026 ties the TIN to a corporate tax registration; the later Guidelines, version 1.1 of 1 June 2026, generalise it to registration with the FTA "for any Tax type". Where the two published documents differ, take the later one and confirm the number your provider actually registers.
The transaction type flags
One field does a great deal of work: the invoice transaction type code, a sequence of eight binary flags for free trade zone, deemed supply, margin scheme, summary invoice, continuous supply, disclosed agent billing, supply through e-commerce and exports. Whether your ERP can derive those eight flags per transaction, rather than have a person tick them, is a fair test of whether the project is finished.
#What is excluded, and what people wrongly assume is excluded
Article 4 of Ministerial Decision No. 243 of 2025 lists the excluded transactions, and Article 5(2) of Ministerial Decision No. 244 of 2025 adds the business-to-consumer carve-out. The exclusions are narrow and specific:
- Sovereign activity. Business transactions conducted by a government entity in a sovereign capacity and not in competition with the private sector.
- Airline passenger services. International passenger transport supplied by an airline where an electronic ticket is issued, plus ancillary services where an electronic miscellaneous document is issued.
- Airline goods transport, temporarily. International transport of goods by an airline against an airway bill — but only for 24 months from the date the system becomes effective.
- Exempt financial services. Financial services exempt from VAT or zero-rated under Article 42 of the VAT Executive Regulation. The Guidelines add that standard-rated financial services are not excluded even where they qualify as zero-rated exports under Article 31.
- Business-to-consumer transactions, and a person engaged exclusively in them, until a further decision by the Minister.
What is not excluded catches people out. Free zone companies are in scope — the free trade zone flag exists precisely because those invoices travel the network. Intra-group transactions between members of the same VAT group are in scope, although the Guidelines grant a temporary 24-month grace period for them starting 1 January 2027. An investment holding company earning only passive income has no business transactions and is out of scope, but the moment it recharges management costs to a related party, it has one. A person with no place of residence in the UAE who is obliged to issue UAE tax invoices must issue them electronically.
#Appointing a provider is itself a legal requirement
You cannot connect to the Federal Tax Authority yourself. Article 6(7) of Ministerial Decision No. 243 of 2025 requires the issuer and the recipient to discharge their exchange and reporting obligations through the appointment of an Accredited Service Provider, and Article 3(1) of Ministerial Decision No. 64 of 2025 forbids anyone else from providing electronic invoicing services in the country.
Three operational points follow, and each of them changes a procurement conversation:
- One provider, both directions. The Guidelines state that a person in scope must appoint only one provider for both sending, that is accounts receivable, and receiving, that is accounts payable. Splitting the mandate across two vendors is not an option.
- You start the onboarding, not the vendor. The Guidelines are explicit that onboarding is initiated by the person or government entity via EmaraTax, then completed with the chosen provider, who obtains your Peppol participant identifier.
- You must keep the provider updated. Article 5(3) of MD No. 243 of 2025 gives you five business days from the FTA confirming any change to your registered data to notify your provider in writing.
#Storage, system failures and the obligations that continue after go-live
Compliance does not end when the first XML document validates. Three continuing duties sit in Ministerial Decision No. 243 of 2025.
Storage. Article 11 requires every person subject to the system to store all electronic invoices, electronic credit notes and associated data within the State, for the period prescribed by the Tax Procedures Law and its Executive Regulation, Cabinet Decision No. 74 of 2023. Appendix 4 of the Guidelines adds two points to read before signing an archiving clause: your provider may store the data for you where the contract says so, but delegation does not transfer the legal obligation; and there is no rule that storage must sit at a particular layer of the network, provided retention, integrity and availability to the FTA are met.
System failure. Article 12 requires the issuer and the recipient to notify the Authority of a system failure within two business days.
Credit notes. Article 6(2) requires an electronic credit note where a transaction is cancelled, the consideration is reduced, the consideration is returned in whole or part, or an administrative or numerical error has occurred.
#Penalties for missing a requirement
Cabinet Decision No. 106 of 2025 sets the penalties specific to the electronic invoicing system; ordinary VAT and tax-procedures penalties under Cabinet Decision No. 40 of 2017 continue to apply on top for invoicing failures generally. The first line of the table is the one worth planning around, because it accrues monthly and starts from your own appointment deadline.
| Violation | Penalty |
|---|---|
| Failure by the issuer to implement the system, including failure to appoint an Accredited Service Provider within the timeline set by the Minister | AED 5,000 for each month of delay or part thereof |
| Failure by the issuer to issue and transmit an electronic invoice through the system within the prescribed timeline | AED 100 per electronic invoice, capped at AED 5,000 per calendar month |
| Failure by the issuer to issue and transmit an electronic credit note through the system within the prescribed timeline | AED 100 per electronic credit note, capped at AED 5,000 per calendar month |
| Failure by the issuer or the recipient to notify the FTA of a system failure within the prescribed timeline | AED 1,000 for each day of delay or part thereof |
| Failure by the issuer or recipient to notify the appointed provider of changes to data registered with the FTA within the prescribed timeline | AED 1,000 for each day of delay or part thereof |
#A readiness sequence you can put in a project plan
The Ministry sets out four steps in chapter 9 of the Guidelines and expands them in Appendix 1. They are written as a project, and they are the honest order of work: nothing in step 3 can be tested until the contract in step 2 exists.
Understand what applies to you
Read the changes to the VAT Decree-Law, the VAT Executive Regulation, Cabinet Decision No. 106 of 2025 and the ministerial decisions. Fix your phase from your revenue for the most recent accounting period and identify the changes needed in your accounting, ERP or invoicing systems.
Select and onboard a provider
Select an Accredited Service Provider from the Ministry's published register and finalise the contract. Onboard onto that provider's system via EmaraTax, and obtain your Peppol participant identifier through them.
Test exchange and reporting end to end
Agree how invoice data will be transmitted, confirm your systems can produce it, and test the full exchange and reporting cycle — including the failure paths, not only the clean ones.
Go live and keep governing it
Agree with your provider who oversees transmission and who resolves errors, then begin exchanging and reporting. Afterwards, use the reverification and offboarding process in EmaraTax whenever your circumstances change.
#What we cannot tell you, and what to ask instead
We do not publish a cost. Neither the Ministry of Finance nor the FTA publishes a price for electronic invoicing, and provider pricing is commercial and unpublished. Any figure quoted as "the cost of UAE e-invoicing" is somebody's estimate. What is documented is a floor on what you should receive: under Article 10(4) of Ministerial Decision No. 64 of 2025 every accredited provider has declared a commitment to supply 100 free electronic invoice exchange and reporting services per year from the date the end-user agreement is signed, and the Ministry's selection guidance recommends confirming that this is written into your contract.
We do not name or recommend providers. The register is the Ministry's to publish and it changes; we link to it rather than reproduce it.
There is no taxpayer-facing API to build against. As at 21 August 2026 the Ministry publishes the Guidelines, the mandatory-fields list and a selection guide; the integration specification your developers need is PINT AE, published by OpenPeppol, and the connection documentation belongs to your provider.
Sources and legal basis
This page relies on
- Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System
- Ministerial Decision No. 244 of 2025 on the Implementation of the Electronic Invoicing System
- Ministerial Decision No. 66 of 2026 (replacing Article 5(1)(a) of MD No. 244 of 2025)
- Ministerial Decision No. 64 of 2025 on the eligibility criteria and Accreditation procedure for Service Providers
- Cabinet Decision No. 106 of 2025 on the Violations and Administrative Penalties for the Electronic Invoicing System
- Cabinet Decision No. 74 of 2023 on the Executive Regulation of the Tax Procedures Law
- Federal Decree-Law No. 8 of 2017 on Value Added Tax
- Cabinet Decision No. 52 of 2017 on the VAT Executive Regulation
- UAE Electronic Invoice mandatory fields, version 1.0, 23 February 2026
- UAE Electronic Invoicing Guidelines, version 1.1, 1 June 2026
- PINT AE and the OpenPeppol Data Dictionary
- Peppol Electronic Address Scheme identifier 0235
- Tax Identification Number (TIN) and Tax Registration Number (TRN)
- Accredited Service Provider (ASP)
- Federal Tax Authority (FTA)
- UAE Ministry of Finance
- EmaraTax
- Ministerial Decision No. 243 of 2025 on the Electronic Invoicing SystemUAE Ministry of Finance
- Ministerial Decision No. 244 of 2025 on the Implementation of the Electronic Invoicing SystemUAE Ministry of Finance
- Ministerial Decision No. 66 of 2026 amending the implementation timelineUAE Ministry of Finance
- UAE Electronic Invoice mandatory fields, version 1.0, 23 February 2026UAE Ministry of Finance
- UAE Electronic Invoicing Guidelines, version 1.1, 1 June 2026UAE Ministry of Finance
- Ministerial Decision No. 64 of 2025 on service provider eligibility and accreditationUAE Ministry of Finance
- Cabinet Decision No. 106 of 2025 on violations and administrative penaltiesFederal Tax Authority
- eInvoicing programme overview and the five-corner modelUAE Ministry of Finance
- UAE e-Invoicing overview and legislation indexFederal Tax Authority
Rates, thresholds and deadlines change. Every figure above is linked to the authority that publishes it — if the two ever disagree, the authority is right and this page is out of date. Tell us and we will fix it.
Frequently asked questions
What are the e-invoicing requirements for UAE businesses?
Any person conducting business in the UAE must issue and receive invoices as structured XML through one Accredited Service Provider, using the mandatory field set published by the Ministry of Finance, store the data inside the UAE for the period set by the Tax Procedures Law, and report each document to the Federal Tax Authority within 14 days of the transaction. The obligation applies regardless of VAT registration status.
What are the UAE invoice requirements under the electronic invoicing system?
The Ministry of Finance prescribes 51 mandatory fields for an electronic tax invoice and 49 for a commercial electronic invoice, grouped into invoice details, seller details, buyer details, document totals, tax breakdown and invoice lines. They sit on top of the tax invoice particulars in Article 59 of the VAT Executive Regulation, and the document must validate against the UAE Peppol specification, PINT AE.
Does UAE e-invoicing apply if a business is not registered for VAT?
Yes. Article 3 of Ministerial Decision No. 243 of 2025 applies the system to any person conducting business in the UAE in respect of every business transaction, with no revenue floor and no VAT condition. A business that is not registered for any tax must still register with the Federal Tax Authority to obtain a Tax Identification Number, because that number identifies it on the network.
When must a UAE business have e-invoicing in place?
A business with revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026 and implement the system by 1 January 2027. Below that threshold, appointment is due by 31 March 2027 and implementation by 1 July 2027. Government entities appoint by 31 March 2027 and implement by 1 October 2027. Voluntary implementation opened on 1 July 2026.
What happens if a business misses the e-invoicing requirements?
Cabinet Decision No. 106 of 2025 imposes AED 5,000 for each month of delay, or part of a month, in implementing the system or appointing a provider. Failing to transmit an invoice or credit note on time costs AED 100 per document, capped at AED 5,000 a calendar month. Failing to report a system failure or a change of registered data costs AED 1,000 a day.