UAE eInvoicing and Government Entities: how the Article 4(1)(a) sovereign exclusion and the Article 5(1)(c) timetable apply to public bodies and their suppliers
Published · Ministerial Decisions 243/2025 and 197/2026 read in the official English text on 23 October 2026 · Other official sources last reviewed 22 October 2026 · 10 min read
Government Entities appear in two different places in the UAE eInvoicing legislation, and the two provisions answer different questions. Article 4(1)(a) of Ministerial Decision No. 243 of 2025, as replaced by Ministerial Decision No. 197 of 2026, decides which transactions of a Government Entity are excluded from the system. Article 5(1)(c) of Ministerial Decision No. 244 of 2025 decides when a Government Entity has to appoint an accredited service provider (ASP) and implement the system: by 31 March 2027 and 1 October 2027 respectively.
Reading one provision without the other leads to two common mistakes. The first is to assume that a public body is outside eInvoicing altogether because some of its activity is sovereign. The second is to assume that a private company selling to a ministry can wait for the government timetable. This guide puts the two provisions side by side for two audiences: businesses that sell to or buy from Government Entities, and the finance and procurement teams inside Government Entities. It is general information, not legal or tax advice, and it does not decide whether any particular body, activity or invoice is in scope.
Two provisions, two different questions
Scope: Decision 243/2025
Article 3(a) of Decision 243/2025 brings into the system any Person conducting Business in the State in respect of every Business Transaction, unless the transaction or Person is excluded under Article 4. Decision 197/2026, in force from 1 October 2026 and announced by the Ministry of Finance on 19 October 2026, replaced Article 4. The replaced Article 4(1) lists seven Excluded Transactions, items (a) to (g). Item (a) is the one that concerns Government Entities. Our guide to Decision 243/2025 scope and exclusions walks through all seven items.
Timing: Decision 244/2025
Decision 244/2025 sets the implementation timetable. Article 5(1)(a) and (b) describe two revenue-based categories of persons subject to the system, and Article 5(1)(c) separately names “A Government Entity”. Ministerial Decision No. 66 of 2026 replaced only Article 5(1)(a); it did not change the government paragraph. Our Government Entity timeline guide explains Article 5(1)(c) in detail.
The practical rule is to answer the scope question first and the timing question second. A date in Decision 244/2025 tells an organisation when to be ready for the transactions that are in scope; it does not by itself tell the organisation which transactions those are.
Who counts as a Government Entity
Article 1 of Decision 243/2025 defines Government Entities as federal or local ministries, government departments, agencies, authorities and public institutions, together with entities treated as such by Cabinet decisions for VAT purposes. The definition is therefore tied to public status and to the VAT framework, not to size or revenue.
Two consequences follow. First, Article 5(1)(c) of Decision 244/2025 is not a third revenue band: an organisation cannot work out whether the government timetable applies by comparing its revenue with AED 50 million. Second, the definition does not automatically extend to every company owned by the government. Whether a particular state-owned company, free zone authority subsidiary or commercially run public enterprise falls within the definition is a question of fact and law that this guide does not answer. Where the answer is unclear, record it as an open question and obtain qualified UAE tax advice rather than assuming either result.
What Article 4(1)(a) excludes
The wording and its three conditions
Replaced Article 4(1)(a) excludes Business Transactions conducted by Government Entities in a sovereign capacity which are not in competition with the private sector, in accordance with the VAT Law. Read closely, the item has three conditions that must all be met:
- Conducted by a Government Entity. The transaction must be one that the Government Entity itself conducts.
- In a sovereign capacity. The activity must be sovereign in character, judged in accordance with the VAT Law.
- Not in competition with the private sector. An activity that competes with private businesses does not meet the condition, even if a public body carries it out.
The legislation we read does not list which particular activities are sovereign or non-competing. Classification of individual activities should be agreed with a qualified adviser by reference to the VAT Law, and the reasoning should be documented so that it can be explained later.
It excludes transactions, not the entity
Article 4(1) excludes transactions, not whole organisations. A ministry or authority whose core activity is sovereign may still conduct other transactions, for example commercial services offered on terms comparable to private providers, that do not meet all three conditions. Those transactions are not excluded by item (a). A Government Entity should therefore map its activities into at least two groups, sovereign and non-competing on one side and everything else on the other, before it relies on the exclusion. The sector exclusions guide discusses the same transaction-by-transaction approach for airlines and financial services.
It runs one way
Item (a) covers transactions conducted by the Government Entity. It does not cover sales made to a Government Entity by a business. On our reading, a supplier’s sale to a ministry is not excluded by Article 4(1)(a), and it is not a B2C sale either, so the separate B2C rule in Article 5(2) of Decision 244/2025 does not remove it. Our transaction scope guide and our B2C exclusion guide explain those readings and their limits.
If you sell to a Government Entity
Your own category decides your dates
A business that supplies goods or services to a Government Entity follows its own timetable, not the government one. If the supplier is a person subject to the system with Revenue equal to or exceeding AED 50 million, its ASP appointment date is 30 October 2026 and its implementation date is 1 January 2027. If its Revenue is below that amount, the dates are 31 March 2027 and 1 July 2027. Our roadmaps for businesses at or above AED 50 million and businesses below AED 50 million set out those phases.
Having a government customer does not move a supplier into the later government phase, and it does not exclude the supplier’s sales. A supplier should treat its sales to public bodies as part of its ordinary in-scope transaction population unless a specific exclusion, such as the temporary Tax Group item, applies on its own terms.
The timing gap with government customers
Because the supplier categories start earlier than the government phase, there may be a period in which a supplier is already live while its government customer has not yet implemented the system. For a large supplier that period could run from 1 January 2027 to 1 October 2027; for a smaller supplier, from 1 July 2027 to 1 October 2027. The texts we reviewed do not set out a special procedure for invoices sent to a recipient that has not yet implemented the system. We therefore do not describe one. A supplier should raise the question early with its ASP and with each government customer, agree how invoices will be delivered and acknowledged during that period, and confirm the position against current official guidance.
Practical points for suppliers
- Record which customers are Government Entities in your customer master data, but do not use that flag to switch eInvoicing off.
- Ask each government customer for its ASP arrangements and planned implementation milestones once they are available.
- Check whether the customer’s procurement or purchase order process needs to change, and agree reference data such as purchase order numbers in advance.
- Keep the same credit note discipline as with any other customer; our trading partner onboarding guide lists the points to agree with each partner.
If you work inside a Government Entity
Sales side: map activities before relying on item (a)
For outgoing transactions, the key task is the activity map described above. Activities that meet all three conditions of Article 4(1)(a) are excluded; other Business Transactions are not excluded by that item. The organisation should identify which systems raise invoices for non-excluded activities and plan their integration with an ASP. If the entity decides to bring excluded transactions into the system anyway, Article 4(3) of Decision 243/2025 allows voluntary participation; our voluntary participation guide explains what that involves.
Purchase side: suppliers will be live first
Article 4(1)(a) does not touch purchases. Many of the entity’s suppliers will be in the earlier revenue-based phases, so electronic invoices addressed to the entity may start arriving before its own implementation date. Accounts payable teams should plan how they will receive, validate and approve those invoices, and how purchase order matching will work. Our accounts payable recipient guide covers the recipient side of the process in general terms. How recipient obligations apply to a Government Entity before 1 October 2027 is not settled in the texts we reviewed, so this should be confirmed rather than assumed.
Two milestones, two workstreams
Article 5(1)(c) separates ASP appointment (31 March 2027) from implementation (1 October 2027). Appointment is a procurement and governance milestone; implementation requires data, systems and testing. Public procurement cycles can be long, so provider selection should start well before the appointment date. Under Ministerial Decision No. 168 of 2026, announced by the Ministry of Finance on 9 October 2026, the former pre-approval stage was removed and direct accreditation was introduced, so a provider’s current accreditation should be reconfirmed through official channels. Our ASP selection guide sets out a checking sequence.
How the government timetable compares
| Who | ASP appointment | Implementation | Basis |
|---|---|---|---|
| Persons subject to the system with Revenue equal to or exceeding AED 50 million | 30 October 2026 | 1 January 2027 | Decision 244/2025, Article 5(1)(a), as replaced by Decision 66/2026 |
| Persons subject to the system with Revenue below AED 50 million | 31 March 2027 | 1 July 2027 | Decision 244/2025, Article 5(1)(b) |
| A Government Entity | 31 March 2027 | 1 October 2027 | Decision 244/2025, Article 5(1)(c) |
The table shows dates only. It does not show which transactions are in scope: for a Government Entity, sovereign non-competing transactions are excluded by Article 4(1)(a) whatever the date. The Federal Tax Authority announcement of 29 September 2026 summarises the revenue-based schedules; for the government phase, read Article 5(1)(c) directly. Our deadlines guide and the key dates on our home page show all three categories.
Other exclusions that can overlap
Article 4(1)(a) is not the only exclusion a public-sector group may need to consider. Replaced Article 4(1) also excludes, for 24 months starting 1 January 2027, Business Transactions between members of the same VAT Tax Group; our Tax Group exclusion guide explains that item and its limits. Article 5(2) of Decision 244/2025 keeps B2C transactions, and persons engaged exclusively in them, outside the system until a further ministerial decision. Each exclusion has its own conditions, and meeting one does not imply meeting another. The legislation map shows which decision contains which rule.
Penalties and what remains unconfirmed
Violations and administrative penalties under the eInvoicing legislation are set by Cabinet Decision No. 106 of 2025, explained in our Cabinet Decision 106/2025 penalties guide. Suppliers should read it alongside their own category dates. We have not confirmed whether or how Cabinet Decision 106/2025 applies to Government Entities themselves, so this guide does not say that it does or that it does not.
The following points were not resolved in the sources we reviewed and should be checked against current official publications:
- Which specific Government Entity activities qualify as sovereign and non-competing under the VAT Law.
- Whether a particular government-owned company or commercially run public body meets the Article 1 definition.
- How invoices to a Government Entity are handled between a supplier’s go-live date and 1 October 2027.
- Whether or how Cabinet Decision 106/2025 applies to Government Entities.
- Technical and data requirements specific to public-sector purchasing, which are outside the scope of this guide.
Transaction triage matrix: classify the direction before deciding scope
Use this matrix as an initial review aid, not as a legal determination. It applies the distinctions discussed above to common operating scenarios. The transaction's actual facts, the legal status of each party and any other applicable exclusion must still be checked against the current instruments.
| Scenario | Initial reading | Evidence to collect | Next action |
|---|---|---|---|
| A Government Entity charges a fee for an activity it performs in a sovereign capacity and that does not compete with the private sector. | Potentially excluded under Decision 243/2025, Article 4(1)(a), as replaced. All conditions require factual assessment. | Legal identity of the entity, description of the activity, statutory basis, fee terms and documented competition analysis. | Record the rationale and obtain qualified UAE tax advice if the sovereign-capacity or competition test is uncertain. |
| A Government Entity sells a service on commercial terms in a market with private providers. | Do not assume the exclusion applies. The non-competition condition may not be met. | Service description, customer terms, comparable private offerings and the relevant VAT analysis. | Refer the classification to the responsible tax or legal reviewer before relying on Article 4(1)(a). |
| A private business sells goods or services to a ministry or authority. | Article 4(1)(a) does not exclude the supplier's sale merely because the customer is a Government Entity. | Supplier's legal identity, its revenue category, transaction facts and any independently applicable exclusion. | Assess the supplier's own implementation timetable and coordinate invoice handling with the customer and ASP. |
| A Government Entity purchases goods or services from a supplier that has already gone live. | The supplier's timetable may apply before the Government Entity's implementation date. The reviewed sources do not settle every pre-implementation recipient-handling detail. | Supplier's go-live date, customer implementation plan, ASP instructions and current official guidance. | Agree an operational process with the supplier and ASP; do not invent a statutory exception or substitute process. |
| A government-owned company conducts a commercial transaction. | Government ownership alone does not establish that the company meets the defined term Government Entity. | Constitutional or legal status, applicable Cabinet treatment for VAT purposes, entity documents and transaction facts. | Obtain a documented status assessment before applying the Government Entity timetable or exclusion. |
| A transaction is between members of the same VAT Tax Group. | Review the separate Tax Group exclusion and its conditions; do not treat it as part of the sovereign-transaction test. | Tax Group membership, effective dates, parties to the transaction and the current wording of Article 4(1)(f). | Assess the separate exclusion independently and document its applicable period and limits. |
These are screening examples, not findings about any named entity or transaction. The facts listed are suggested evidence for internal review, not a statutory document checklist. For the underlying rules, see the scope and exclusions guide, the Tax Group exclusion guide and the voluntary participation guide.
Suggested transaction-classification record
Keep one record for each material transaction type or documented activity category. Where an entity performs both sovereign and commercial activities, avoid applying a single organisation-wide conclusion to every transaction. The fields below are a suggested internal record format, not a Ministry-prescribed form.
| Field | What to record |
|---|---|
| Record owner and review date | Responsible business owner, tax reviewer, date assessed and next review date. |
| Parties and direction | Legal names, evidence of Government Entity status where relevant, and whether the transaction is conducted by or supplied to the public body. |
| Transaction description | What is supplied, the contractual basis, commercial terms and the system or ledger where it is recorded. |
| Potential legal basis | Decision number, article and paragraph considered, including any separate exclusion assessed. |
| Sovereign-capacity assessment | Facts supporting or contradicting the conclusion; do not record only a label such as "government service". |
| Competition assessment | Whether comparable private-sector providers exist and what evidence supports the assessment. |
| Conclusion and confidence | Preliminary classification, reviewer, unresolved assumptions and whether specialist advice is required. |
| Implementation consequence | Applicable category and dates where confirmed, ASP coordination needed, and any unresolved exchange or receipt procedure. |
| Evidence and change history | Official source versions, supporting documents, decision rationale, approvals and events that trigger reassessment. |
Reopen a classification when the service changes, commercial terms change, a new competitor enters the market, the legal entity's status changes, a relevant instrument is amended, or new official guidance addresses an open question. Preserve the previous conclusion and the reason for the change instead of silently overwriting the record.
A checklist for both sides
- Read the primary texts. Keep copies of Decisions 243/2025, 197/2026 and 244/2025 and note the date you read them.
- Confirm classification. Establish whether the public body concerned meets the Article 1 definition of Government Entity.
- Map transactions. For a Government Entity, separate sovereign non-competing activities from all others; for a supplier, treat sales to public bodies as in scope unless a specific exclusion applies.
- Apply the right dates. Suppliers use their revenue category; Government Entities use Article 5(1)(c).
- Plan the gap period. Agree with each counterparty how invoices will flow while one side is live and the other is not.
- Check ASP accreditation. Reconfirm current accreditation under Decision 168/2026 before relying on a provider.
- Log open questions. Record unresolved points and revisit them when the Ministry of Finance eInvoicing programme page publishes new material.
- Take advice. Ask a qualified UAE tax adviser to review conclusions that rely on the sovereign-capacity test.
Our free eInvoicing readiness assessment can help organise these steps.
Frequently asked questions
Is a Government Entity completely outside UAE eInvoicing?
No. Article 4(1)(a) excludes only Business Transactions conducted in a sovereign capacity that are not in competition with the private sector. Other Business Transactions of the entity are not excluded by that item, and Article 5(1)(c) gives Government Entities their own implementation timetable.
Are my sales to a ministry excluded?
Not by Article 4(1)(a), which covers transactions conducted by the Government Entity, not sales to it. On our reading such a sale is not a B2C sale either. Check whether any other specific exclusion applies on its own terms.
Can a supplier wait until 1 October 2027 because its customer is a Government Entity?
No. A supplier follows its own revenue-based category. The government dates apply to the Government Entity, not to the businesses that sell to it.
Did Decision 66/2026 or Decision 197/2026 change the government dates?
Decision 66/2026 replaced only Article 5(1)(a) of Decision 244/2025. Decision 197/2026 amended Decision 243/2025, not Decision 244/2025. The government dates in Article 5(1)(c) remain 31 March 2027 for ASP appointment and 1 October 2027 for implementation.
Where are the defined terms explained?
Our glossary of key terms covers Government Entity, Business Transaction and the other defined terms, and our eInvoicing FAQ gives short answers with links to the detailed guides.
Official sources used in this guide
- Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System (MoF, English PDF)
- Ministerial Decision No. 197 of 2026 amending Decision 243/2025 (MoF, English PDF)
- Ministerial Decision No. 244 of 2025 on the implementation of the Electronic Invoicing System (MoF, English PDF)
- Ministerial Decision No. 66 of 2026 amending Decision 244/2025 (MoF, English PDF)
- Ministerial Decision No. 168 of 2026 on ASP eligibility and accreditation (MoF, English PDF)
- Cabinet Decision No. 106 of 2025 on eInvoicing violations and penalties (MoF, English PDF)
- MoF announcement on amendments to the eInvoicing regulations, 19 October 2026
- MoF announcement on Decision 168/2026 and ASP accreditation, 9 October 2026
- FTA announcement on ASPs and persons subject to the eInvoicing system, 29 September 2026
- MoF eInvoicing programme page and legislation index
Important notice
This article is general educational information published by MINSEONG.COM, an independent website. It is not legal or tax advice, is not an official government publication, and does not determine whether any entity, activity or transaction is subject to the UAE Electronic Invoicing System. Decisions 243/2025 and 197/2026 were read on 23 October 2026; other official sources were last reviewed on 22 October 2026. Later instruments or guidance may change the position. Check current Ministry of Finance and Federal Tax Authority publications and consult a qualified UAE tax adviser before making decisions. See all our guides.