LEGISLATION
Ministerial Decision 243 of 2025 Explained: The Core UAE E-Invoicing Law Every Business Must Understand
Ministerial Decision No. 243 of 2025 is the legal foundation of the UAE’s Electronic Invoicing System. It defines what the system is, who must participate, what counts as a valid electronic invoice, what your obligations are as a supplier and buyer, and what is excluded. This article translates every key provision into plain language — with the original legal language alongside so you can verify each point directly.
reading time: 13 min
SOURCES: MOF OFFICIAL PUBLICATIONS
may 2026
aiverix research
Most finance leaders who are preparing for UAE e-invoicing have heard of Ministerial Decision No. 243 of 2025. It is cited in almost every piece of guidance on the subject. But very few have actually read it in detail — and even fewer understand exactly what each provision means in practice. This article changes that. It takes the key articles of MD 243 and explains each one in plain language, article by article, so that any finance professional — regardless of legal background and regardless of whether English is their first language — can understand precisely what the law requires of their business.
“
OFFICIAL SOURCES:
Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System
UAE Electronic Invoicing Guidelines V1.0 — Ministry of Finance, 23 February 2026
Federal Decree-Law No. 8 of 2017 on Value Added Tax (VAT Decree-Law) — Article 65(5) as amended
Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System
UAE Electronic Invoicing Guidelines V1.0 — Ministry of Finance, 23 February 2026
Federal Decree-Law No. 8 of 2017 on Value Added Tax (VAT Decree-Law) — Article 65(5) as amended
Where MD 243 Fits in the Legal Framework
Before looking at what MD 243 says, it helps to understand where it sits in the broader legal framework for UAE e-invoicing. There are four legal instruments that together create the complete framework, and each one does a different job.
MD 243 is the foundational document. The other three build on it — they set the timeline, the provider rules, and the penalties for what MD 243 requires. You cannot fully understand MD 244 or CD 106 without understanding what MD 243 establishes first.
2025
Year of issue — MD 243 is already law, not a proposal
4
Legal instruments that together form the complete UAE e-invoicing framework
3
Named exclusion categories under Article 4 of MD 243
1
ASP per business — MD 243 requires you appoint only one, for both sending and receiving
The Legal Definition of an Electronic Invoice
The first thing MD 243 establishes — and the most important for understanding everything else — is the legal definition of an Electronic Invoice. This definition is not flexible or open to interpretation. It is precise, and it has direct consequences for what counts as a legally valid invoice from your mandatory date.
An Electronic Invoice is an invoice that is issued, transmitted, and received through the Electronic Invoicing System, in a structured electronic format that enables automatic and electronic processing, in accordance with the Electronic Invoicing System.
WHAT THIS MEANS IN PLAIN LANGUAGE
Three words define what makes an invoice electronic: issued, transmitted, and received — all through the EIS. A document that is created digitally but emailed as a PDF is not an electronic invoice under this definition. A document that is transmitted through the EIS but generated manually is not an electronic invoice. All three elements must occur through the system. The "structured electronic format" requirement means XML — specifically PINT AE XML. A human-readable document, even a digital one, does not qualify.
Three words define what makes an invoice electronic: issued, transmitted, and received — all through the EIS. A document that is created digitally but emailed as a PDF is not an electronic invoice under this definition. A document that is transmitted through the EIS but generated manually is not an electronic invoice. All three elements must occur through the system. The "structured electronic format" requirement means XML — specifically PINT AE XML. A human-readable document, even a digital one, does not qualify.
This definition has an important practical consequence: from your mandatory date, any invoice that is not issued, transmitted, and received through the EIS in PINT AE XML format is not a valid invoice under UAE law — regardless of how accurate, complete, or professionally formatted it is.
The Scope of the Obligation: Who Must Participate
Electronic Invoicing is mandatory for any Person conducting Business in the UAE, in respect of every Business Transaction, regardless of whether they are established in the UAE, unless specifically excluded under Article 4.
WHAT THIS MEANS IN PLAIN LANGUAGE
"Any Person" means both natural persons (individuals running a business) and juridical persons (companies, partnerships). "Conducting Business in the UAE" means the activity takes place in or involves the UAE — it does not require the business to be incorporated in the UAE. "Regardless of whether they are established in the UAE" explicitly extends the obligation to foreign businesses with UAE tax obligations.
"Any Person" means both natural persons (individuals running a business) and juridical persons (companies, partnerships). "Conducting Business in the UAE" means the activity takes place in or involves the UAE — it does not require the business to be incorporated in the UAE. "Regardless of whether they are established in the UAE" explicitly extends the obligation to foreign businesses with UAE tax obligations.
The scope is intentionally broad. There is no revenue floor, no employee count threshold, and no sector exemption for the obligation itself. The only variables are the timing — set by MD 244 — and the narrow exclusions set by Article 4.
The UAE Electronic Invoicing Guidelines — which interpret and apply MD 243 — confirm explicitly: "All Persons who make a Business Transaction in the UAE, notwithstanding their VAT registration status, are within the scope of Electronic Invoicing."
WHAT THIS MEANS IN PLAIN LANGUAGE
E-invoicing is not an extension of UAE VAT law. It is a separate obligation under a different legal framework. Whether your business is VAT-registered, VAT-exempt, below the VAT threshold, or not registered for any tax type at all — if you make business transactions in the UAE involving other businesses or government entities, you are in scope.
E-invoicing is not an extension of UAE VAT law. It is a separate obligation under a different legal framework. Whether your business is VAT-registered, VAT-exempt, below the VAT threshold, or not registered for any tax type at all — if you make business transactions in the UAE involving other businesses or government entities, you are in scope.
This is the single most commonly misunderstood aspect of MD 243. Many businesses below the VAT registration threshold of AED 375,000 assume the mandate does not apply to them. It does — from their Wave 2 mandatory date of July 1, 2027.
Article 4: The Exclusions — Read Carefully
Article 4 of MD 243 is the only place where businesses are formally excluded from the obligation. It is short, specific, and narrow. Every business that is not named in Article 4 is in scope. There are no other exclusions.
Three categories of transaction are excluded from MD 243:
1. Sovereign government activities: Business Transactions conducted by a Government Entity in a sovereign capacity and not in competition with the private sector.
1. Sovereign government activities: Business Transactions conducted by a Government Entity in a sovereign capacity and not in competition with the private sector.
PLAIN LANGUAGE
A government ministry issuing a licence or permit is acting sovereignly — excluded. A government-owned commercial company selling goods or services in competition with private businesses is not acting sovereignly — included. The test is whether the transaction is part of governmental authority or commercial activity.
A government ministry issuing a licence or permit is acting sovereignly — excluded. A government-owned commercial company selling goods or services in competition with private businesses is not acting sovereignly — included. The test is whether the transaction is part of governmental authority or commercial activity.
2. Airline passenger services: International passenger transportation services where an Electronic Ticket is issued, and ancillary passenger services where an Electronic Miscellaneous Document is issued. A temporary additional exclusion exists for airway bills (cargo) — for 24 months only from the date in Article 5 of MD 244.
PLAIN LANGUAGE
Airlines do not need to issue e-invoices for passenger ticket sales to consumers. They do for B2B transactions. The cargo exclusion is temporary — airline freight invoicing will become mandatory approximately mid-2029.
Airlines do not need to issue e-invoices for passenger ticket sales to consumers. They do for B2B transactions. The cargo exclusion is temporary — airline freight invoicing will become mandatory approximately mid-2029.
3. Exempt financial services: Financial services exempt from VAT under Article 42 of the VAT Executive Regulation, and zero-rated exports of those same exempt services to non-resident customers.
PLAIN LANGUAGE
VAT-exempt financial services — such as certain lending, insurance (partly), and currency exchange — are excluded. But financial services that are standard-rated for UAE resident customers are not excluded even if they qualify as zero-rated exports to non-resident customers. The exemption follows the UAE VAT treatment, not the export destination.
VAT-exempt financial services — such as certain lending, insurance (partly), and currency exchange — are excluded. But financial services that are standard-rated for UAE resident customers are not excluded even if they qualify as zero-rated exports to non-resident customers. The exemption follows the UAE VAT treatment, not the export destination.
Article 4 also states that the Minister may add further exclusions through future ministerial decisions. Any new exclusions will be announced officially — they do not apply until formally gazetted.
THE DEFAULT IS ALWAYS IN-SCOPE
Article 4 operates on an explicit, named-exclusion basis. If your business type or transaction type is not specifically named in Article 4, you are in scope. There is no general exemption for small businesses, for free zone companies, for businesses below the VAT threshold, or for any sector not explicitly listed. Do not assume you are excluded unless you can point to a specific provision in Article 4 that covers your situation.
Article 4 operates on an explicit, named-exclusion basis. If your business type or transaction type is not specifically named in Article 4, you are in scope. There is no general exemption for small businesses, for free zone companies, for businesses below the VAT threshold, or for any sector not explicitly listed. Do not assume you are excluded unless you can point to a specific provision in Article 4 that covers your situation.
Article 5: What MD 243 Requires of Suppliers
Every person subject to MD 243 who issues invoices — the supplier — must:
1. Issue, transmit, share, and exchange Electronic Invoices and Electronic Credit Notes through the Electronic Invoicing System.
2. Appoint one Accredited Service Provider in respect of both sending (accounts receivable) and receiving (accounts payable) Electronic Invoices.
3. Contact buyers and gather their Peppol Participant Identifiers in order to issue Electronic Invoices to them correctly.
4. Calculate all Electronic Invoice values correctly — the mathematical accuracy of the invoice is the supplier’s responsibility, not the ASP’s.
5. Agree business-specific data security requirements with the appointed ASP.
1. Issue, transmit, share, and exchange Electronic Invoices and Electronic Credit Notes through the Electronic Invoicing System.
2. Appoint one Accredited Service Provider in respect of both sending (accounts receivable) and receiving (accounts payable) Electronic Invoices.
3. Contact buyers and gather their Peppol Participant Identifiers in order to issue Electronic Invoices to them correctly.
4. Calculate all Electronic Invoice values correctly — the mathematical accuracy of the invoice is the supplier’s responsibility, not the ASP’s.
5. Agree business-specific data security requirements with the appointed ASP.
WHAT THIS MEANS IN PLAIN LANGUAGE
Five obligations. The most operationally significant are the one-ASP rule, the buyer Peppol ID collection requirement, and the calculation accuracy obligation. The one-ASP rule means you cannot use one provider for outgoing invoices and a different one for incoming invoices — one ASP handles both. The buyer Peppol ID collection is an administrative task your finance team must complete before go-live. The calculation accuracy obligation means your ERP’s rounding and VAT calculation settings must be correct — a wrong total is your error, not your ASP’s.
Five obligations. The most operationally significant are the one-ASP rule, the buyer Peppol ID collection requirement, and the calculation accuracy obligation. The one-ASP rule means you cannot use one provider for outgoing invoices and a different one for incoming invoices — one ASP handles both. The buyer Peppol ID collection is an administrative task your finance team must complete before go-live. The calculation accuracy obligation means your ERP’s rounding and VAT calculation settings must be correct — a wrong total is your error, not your ASP’s.
Article 6: What MD 243 Requires of Buyers
Every person subject to MD 243 who receives invoices — the buyer — must:
1. Receive Electronic Invoices and Electronic Credit Notes through the Electronic Invoicing System.
2. Appoint one Accredited Service Provider for receiving Electronic Invoices (the same ASP that handles sending, as per Article 5).
3. Agree business-specific data security requirements with the appointed ASP.
1. Receive Electronic Invoices and Electronic Credit Notes through the Electronic Invoicing System.
2. Appoint one Accredited Service Provider for receiving Electronic Invoices (the same ASP that handles sending, as per Article 5).
3. Agree business-specific data security requirements with the appointed ASP.
WHAT THIS MEANS IN PLAIN LANGUAGE
Being a buyer in a B2B or B2G transaction is not a passive role under MD 243. Buyers have independent compliance obligations. A buyer who does not appoint an ASP is in violation of MD 243 from their mandatory date — even if all their suppliers are fully compliant and transmitting correctly. This is an important point for businesses that think of themselves primarily as customers rather than invoicers: if you receive B2B invoices, you must be registered and receiving them through the EIS.
Being a buyer in a B2B or B2G transaction is not a passive role under MD 243. Buyers have independent compliance obligations. A buyer who does not appoint an ASP is in violation of MD 243 from their mandatory date — even if all their suppliers are fully compliant and transmitting correctly. This is an important point for businesses that think of themselves primarily as customers rather than invoicers: if you receive B2B invoices, you must be registered and receiving them through the EIS.
Article 9: The Connection Between E-Invoicing and VAT Law
One of the most legally significant aspects of MD 243 is how it connects to existing UAE VAT law — specifically to Article 65 of the VAT Decree-Law. This connection has been amended as part of the e-invoicing framework and changes what counts as a valid Tax Invoice for VAT purposes.
Article 65(5) of the UAE VAT Decree-Law — as amended following the introduction of the e-invoicing framework — states that a Person subject to the Electronic Invoicing System will be required to issue a Tax Invoice or Tax Credit Note in the form of an Electronic Invoice or an Electronic Credit Note.
WHAT THIS MEANS IN PLAIN LANGUAGE
Before e-invoicing, the VAT Decree-Law required taxable persons to issue Tax Invoices — but did not specify the format. After the amendment, for businesses subject to MD 243, "issuing a Tax Invoice" means issuing an Electronic Invoice. There is no longer a choice between a paper invoice, a PDF, and an electronic invoice. The Electronic Invoice is the Tax Invoice. They are the same document.
Before e-invoicing, the VAT Decree-Law required taxable persons to issue Tax Invoices — but did not specify the format. After the amendment, for businesses subject to MD 243, "issuing a Tax Invoice" means issuing an Electronic Invoice. There is no longer a choice between a paper invoice, a PDF, and an electronic invoice. The Electronic Invoice is the Tax Invoice. They are the same document.
This has two important consequences. First: from your mandatory date, a PDF invoice is not a Tax Invoice for VAT purposes — it is not valid for input VAT recovery by your buyer. Second: the e-invoicing obligation and the VAT Tax Invoice obligation are now the same obligation — failing one means failing both, which means two penalty frameworks can apply simultaneously (as covered in Article 4 of this series).
Article 11: Data Retention Under MD 243
Any Person subject to the Electronic Invoicing System must store Electronic Invoices, Electronic Credit Notes, and any associated data within the State in accordance with the timeline prescribed under the Tax Procedures Law.
WHAT THIS MEANS IN PLAIN LANGUAGE
The retention obligation is established directly in MD 243 — it is not an optional best practice. The phrase "within the State" has been officially interpreted by the Ministry of Finance to mean "accessible to the FTA on request" rather than "physically stored on UAE soil." Cloud storage on international servers is acceptable, provided the three accessibility conditions are met. Full details are covered in Article 6 of this series on data retention.
The retention obligation is established directly in MD 243 — it is not an optional best practice. The phrase "within the State" has been officially interpreted by the Ministry of Finance to mean "accessible to the FTA on request" rather than "physically stored on UAE soil." Cloud storage on international servers is acceptable, provided the three accessibility conditions are met. Full details are covered in Article 6 of this series on data retention.
What MD 243 Changed in the Existing UAE Legal Framework
MD 243 did not create e-invoicing obligations in isolation. It amended several existing laws and regulations to integrate the new system into the existing UAE legal framework. Understanding these amendments helps explain why the consequences of non-compliance extend beyond the specific EIS penalties in CD 106.
Specific Scenarios Addressed by MD 243
MD 243 also addresses specific business situations that do not fit the standard supplier-to-buyer model. These are covered in Article 6.3 of the Guidelines which interpret MD 243, and they include situations that are common in the UAE business environment.
Intra-group transactions within a VAT group
MD 243 establishes that business transactions between members of the same VAT group are in scope. They are not excluded simply because they are intra-group. However, the Guidelines note that MD 244 — the implementation decision — provides a 24-month grace period for intra-group transactions starting January 1, 2027. This grace period is a timing concession under MD 244, not a scope exclusion under MD 243. After the grace period expires on January 1, 2029, intra-group transactions are fully subject to MD 243.
Non-UAE established persons
MD 243 explicitly extends to persons without a place of residence in the UAE who are obligated to issue Tax Invoices under the UAE VAT Decree-Law. Foreign businesses that have registered for UAE VAT in respect of taxable supplies made in the UAE — for example, a foreign company selling digital services to UAE businesses — are subject to MD 243 from their mandatory date, even with no physical presence in the country.
The buyer's status does not affect your obligations
A point that MD 243 makes clear through its scope definition is that your e-invoicing obligations do not depend on your buyer’s e-invoicing status. You cannot defer your obligation because your buyer has not yet registered on the Peppol network. You cannot issue a PDF instead of an electronic invoice because your buyer is a Wave 2 business whose mandatory date has not yet arrived. Your obligation runs independently. When your buyer is not yet registered, you use the predefined fallback endpoint — your compliance is met regardless of the buyer’s status.
SUMMARY: WHAT MD 243 ESTABLISHES IN 5 POINTS
- An Electronic Invoice has a precise legal definition — issued, transmitted, and received through the EIS in structured XML format. Nothing else qualifies.
- The obligation applies to any person conducting business transactions in the UAE — regardless of VAT status, entity size, or free zone location — unless specifically named in Article 4.
- Both suppliers and buyers have independent compliance obligations. Being only a buyer does not exempt you.
- You must appoint exactly one ASP for both sending and receiving. You collect buyer Peppol IDs. You are responsible for invoice calculation accuracy.
- From your mandatory date, an Electronic Invoice is the only valid form of Tax Invoice under UAE VAT law for in-scope businesses. PDF invoices are legally void for VAT purposes.
Why Reading the Law Matters
Most finance teams prepare for e-invoicing based on summaries, provider materials, and industry briefings. These are useful — but they often simplify or omit the specific provisions that turn out to matter most. Knowing that Article 4 of MD 243 is the only place where exclusions exist — and that if you are not named there you are in scope — is more useful than a general statement that "most businesses are covered." Knowing that Article 5 makes you responsible for collecting buyer Peppol IDs gives you a specific preparation task. Knowing that Article 65(5) of the VAT Decree-Law now makes your Electronic Invoice and your Tax Invoice the same document tells you why a non-EIS invoice creates both e-invoicing and VAT liability simultaneously.
The next article in this series covers Ministerial Decision No. 244 of 2025 — the implementation timeline law — in the same article-by-article format. And Article 10 covers Cabinet Decision No. 106 of 2025 — the penalty framework — in full legal detail.
Aiverix is an FTA-accredited Accredited Service Provider and certified Peppol Access Point, based in Dubai. Our compliance assessment includes a scope determination based on your specific business structure — so you know exactly which provisions of MD 243 apply to you, which exclusions if any are relevant, and what your implementation timeline looks like. Request yours at aiverix.ae.
The next article in this series covers Ministerial Decision No. 244 of 2025 — the implementation timeline law — in the same article-by-article format. And Article 10 covers Cabinet Decision No. 106 of 2025 — the penalty framework — in full legal detail.
Aiverix is an FTA-accredited Accredited Service Provider and certified Peppol Access Point, based in Dubai. Our compliance assessment includes a scope determination based on your specific business structure — so you know exactly which provisions of MD 243 apply to you, which exclusions if any are relevant, and what your implementation timeline looks like. Request yours at aiverix.ae.