MINSEONG / GUIDES

A UAE eInvoicing readiness project plan: data, systems, exception processes and ownership, workstream by workstream

Published 23 October 2026 · Official sources last reviewed 22 October 2026 · 10 min read

Most writing about UAE eInvoicing explains the law: who is in scope, which dates apply and what an accredited service provider (ASP) is. Finance teams also need something more ordinary: a project plan. Who does what, in which order, and what has to be finished before the provider is appointed and before go-live? This guide turns the eight areas of our free eInvoicing readiness check into eight internal workstreams, and orders them by working backwards from the official dates.

The workstreams are an editorial planning framework, not an official checklist from the Ministry of Finance (MoF) or the Federal Tax Authority (FTA). Where the law says something specific, we say which decision says it and link to the official text. Where the official position is not confirmed in the sources we have reviewed, especially technical specifications and data fields, we say so instead of guessing. We do not name or compare providers, and we do not estimate costs.

Start from the dates: your planning anchors

Every plan needs fixed points. For UAE eInvoicing they come from Article 5 of Ministerial Decision 244/2025, with Article 5(1)(a) replaced by Ministerial Decision 66/2026. Each category has two milestones: the date by which a person subject to the system must appoint an ASP, and the later date by which eInvoicing must be implemented.

Planning anchors by category (Decision 244/2025 as amended by Decision 66/2026)
Category	Appoint an ASP by	Implement by
Annual revenue AED 50 million or more	30 October 2026	1 January 2027
Annual revenue below AED 50 million	31 March 2027	1 July 2027
Government entities	31 March 2027	1 October 2027

The gap between the two milestones differs. For the revenue category of AED 50 million or more it is about two months (30 October 2026 to 1 January 2027); for the category below AED 50 million it is about three months (31 March 2027 to 1 July 2027); for Government Entities it is about six months (31 March 2027 to 1 October 2027). That gap is the time for onboarding and testing with the provider after appointment, so most internal preparation should be done before the appointment date, not after it.

The dates apply to persons subject to the system. A revenue figure only tells you which timetable applies if you are subject; it does not decide that you are. Our guides to the deadlines, the AED 50 million revenue threshold and the Government Entity timeline explain each category, and the key dates summary on our home page shows them at a glance.

Workstream 1: counterparty master data

What the work is

The first question in the readiness check asks whether you can reliably identify your customers and suppliers. In a structured system an invoice is exchanged as data, so the details of the parties have to be correct, complete and held consistently in one place. Duplicate customer records, outdated addresses and identifiers kept only in emails become rejected or disputed invoices later.

Practical tasks

Extract the active customer and supplier lists from each system that issues or receives invoices.
Find duplicates, missing values and records that differ between systems, and agree who owns corrections.
Flag counterparties whose classification matters for scope, such as Government Entities, members of your VAT Tax Group, and consumers.
Set a rule for maintaining new records so the clean-up does not decay before go-live.

Which identifiers and party details the official data model requires is set by the technical specifications. Those specifications are not covered in this guide, so treat any field list as unconfirmed until you have checked it against current official material and your provider.

Workstream 2: structured invoice data

The second question asks whether invoice details are stored as structured, usable data rather than only as PDF files. The FTA has described eInvoices as exchanged in a structured electronic format, but we have not reviewed the field-by-field technical requirements, and Article 7 of Ministerial Decision 243/2025 on technical matters is outside what this site has recorded. So the practical task here is a gap analysis, not a mapping to a field list we cannot confirm.

Identify where line items, quantities, prices, tax amounts, discounts and references to earlier invoices actually live.
Note anything that exists only in free text, attachments or spreadsheets outside the main system.
Once your provider or the official specifications give you the required data, map each item against it and record the gaps.

Clean data here also helps the exception workstream, because credit notes depend on being able to point back to the original transaction accurately. Our customer and supplier master data readiness guide sets out how to inventory, de-duplicate and assign owners to counterparty records before connecting to an ASP. Use the go-live testing checklist to exercise ordinary invoices, data errors, credit-note flows and recovery scenarios with recorded evidence.

Workstream 3: inventory of invoice-issuing systems

The third question asks whether you know which system creates your invoices. In many businesses the honest answer is several: an ERP or accounting application, a billing tool for one business line, manual invoices prepared in a spreadsheet, and occasional invoices raised by a branch or an agent. Each of these is a separate route to the eInvoicing system, and each needs an owner and a plan.

List every place an invoice or credit note can be created, including manual and one-off processes.
Record the volume, the business unit and the person responsible for each route.
Decide which routes will be retired, consolidated or connected, and note where invoices are raised on your behalf.

Article 8 of Decision 243/2025 deals with agents and Article 9 with self-billing, which is permitted only where both parties are VAT Registrants. If either applies to you, list those flows separately; our guide to Issuer and Recipient obligations under Article 6 and Article 9 explains them.

Workstream 4: external integrations

The fourth question asks whether your systems can exchange data with external services. Article 6(7) of Decision 243/2025 provides that the Article 6 obligations are carried out via an accredited service provider, so each issuing route identified in workstream 3 needs a way to pass invoice data to the provider and to receive incoming invoices.

Ask each software vendor what export, connector or interface options exist and how they are documented.
Identify routes with no automated option, such as manual spreadsheets, and decide how they will be handled.
Plan how incoming invoices from suppliers will reach your accounts payable process, because the Recipient must also process invoices through the system under Article 6(3). Our accounts payable and Recipient guide covers the buyer-side steps.

The technical method of connecting to a provider varies by provider and system and is not described in the official sources we have reviewed. Confirm it during provider selection rather than assuming a particular approach.

Workstream 5: approvals, corrections and credit notes

The fifth question is about exceptions. Article 6(2) of Decision 243/2025 lists four cases in which an Electronic Credit Note is issued: cancellation of the transaction, a reduction in consideration, a return of consideration, and an administrative or numerical error. Each of those already happens in your business today, probably through a mix of approvals, emails and manual adjustments.

Timing rules to build into the process

Article 6(4) says that an Issuer who is a VAT Registrant follows the timeline in the VAT Law. Article 6(5), as replaced by Ministerial Decision 197/2026, sets fourteen Business Days from the Date of Business Transaction, subject to Article 6(4). We have not recorded the number of days in the VAT Law timeline, so confirm it with your tax adviser before you set internal service levels.

Document each exception flow from trigger to approved credit note, with the responsible person at each step.
Decide who can approve corrections and how quickly, so the approval chain does not cause you to miss the applicable timeline.
Test unusual cases, such as partial returns, before go-live, not only standard invoices.

Workstream 6: a named project owner

The sixth question asks whether there is a clear owner for the transition. eInvoicing touches finance, tax, IT, sales, procurement and outside advisers. Without one accountable person, decisions on data ownership, system changes and the provider contract tend to wait for each other.

Name one owner with the authority to make or escalate decisions.
Set up a small working group with representatives from each affected function.
Agree a regular status review and a single list of open decisions and risks.
Record key decisions in writing, including how you determined your category and scope.

Workstream 7: confirming scope and timetable

The seventh question asks whether you have checked your applicable rollout and scope. This is the workstream that decides whether the other seven are needed and on which timetable, so it should start first, even though it rarely finishes first.

Confirm whether you are subject to the system under Decision 243/2025 as amended, and whether any of your transactions are excluded. Our transaction scope guide and sector exclusions guide cover Article 3 and Article 4.
Check the B2C exclusion in Article 5(2) of Decision 244/2025 carefully if you sell to consumers; it covers B2C transactions and persons engaged exclusively in them, not mixed businesses as a whole. See the B2C exclusion guide.
If you are in a VAT Tax Group, note that Decision 197/2026 treats transactions between members as Excluded Transactions for 24 months starting 1 January 2027. Our guide to the Decision 197/2026 changes explains this and the record-keeping changes.
Fix your revenue figure using the Article 1 definition in Decision 244/2025 and record the basis.

If the defined terms are unfamiliar, our glossary of key terms explains them in plain English. Where your position is unclear, take qualified UAE tax advice; this guide does not determine scope for any business.

Workstream 8: criteria for choosing an ASP

The eighth question asks whether you have criteria for selecting an accredited service provider. On 9 October 2026 the MoF announced Ministerial Decision 168/2026, in force from 1 October 2026, which removed the former pre-approval stage and introduced direct accreditation. A provider described as pre-approved under the earlier rules is therefore not shown to be accredited under the current framework.

Reconfirm each shortlisted provider's current accreditation through official channels.
Check that the provider supports every issuing route and system from workstreams 3 and 4.
Ask for a realistic onboarding and testing timetable that fits the gap between your two dates.
Compare service levels, security arrangements, support and contract terms on the same criteria for every candidate.

Our guide to choosing and appointing an ASP under Decision 168/2026 covers this workstream in more detail. To decide which internal team owns each workstream and handoff, see our functional responsibility matrix for Finance, Tax, AP, AR and IT.

Putting it in order: working back from your dates

The workstreams overlap, but their dependencies suggest an order. The sequence below is an editorial suggestion for a team that has not yet started.

Immediately: name the owner (workstream 6) and start confirming scope and category (workstream 7). Everything else depends on these two.
Next: run the system inventory (workstream 3) and the master data review (workstream 1) in parallel, because both are needed to brief providers properly.
Before the ASP appointment date: complete the integration review (workstream 4) and the invoice data gap analysis (workstream 2) far enough to compare providers, and appoint an accredited provider against your criteria (workstream 8).
Between appointment and go-live: map data to the requirements your provider and the official specifications set, document and test exception flows (workstream 5), train staff and run end-to-end tests.

For the category of AED 50 million or more, the ASP appointment date of 30 October 2026 is very close, so steps one to three are urgent if they are not already done. For the other two categories there is more room, but the window between appointment and go-live is still short for testing, so it is safer to finish the internal work early.

Checklist

Owner and working group named, with a list of open decisions.
Scope, exclusions and category confirmed and documented, with advice where needed.
All invoice and credit note issuing routes listed, including manual and agent flows.
Customer and supplier records cleaned, with an owner for ongoing maintenance.
Invoice data gaps recorded, to be mapped against official and provider requirements.
Integration options confirmed with each software vendor.
Credit note and correction flows documented against the Article 6 cases and timelines.
Provider accreditation reconfirmed under Decision 168/2026 and appointment made by your date.
End-to-end testing and staff training scheduled before your implementation date.

Frequently asked questions

Is this the official list of things to do?

No. The eight workstreams are an editorial framework based on our readiness check. The binding rules are in the ministerial decisions, which the MoF lists on its eInvoicing programme page.

Which data fields does a UAE eInvoice need?

This guide does not list them. Field-level requirements belong to the technical specifications, which we have not reviewed. Check current official material and confirm with your provider.

Can we appoint a provider before our data clean-up is finished?

Yes. The appointment date is a legal milestone and should not slip while data work continues. A good inventory and gap analysis simply makes the provider discussion faster and more accurate.

We only sell to consumers. Do we need this plan?

Persons engaged exclusively in B2C transactions are excluded under Article 5(2) of Decision 244/2025 until a further ministerial decision. Mixed businesses need to check their position separately. Keeping a light plan in place is sensible because the exclusion is temporary.

How much will it cost?

Costs depend on your systems, volumes and provider. We do not publish estimates or provider names.

For a calendar version of this plan for the category below AED 50 million, see our month-by-month roadmap for businesses below AED 50 million.

Official sources used in this guide

Important notice

This guide is general information prepared by MINSEONG.COM, an independent website. It is not legal or tax advice, it is not an official government publication, and it does not determine whether any business or transaction is subject to the UAE eInvoicing system. The project workstreams and sequence are editorial suggestions. The official texts were last reviewed on 22 October 2026; rules may change after that date. Always check the current Ministry of Finance and Federal Tax Authority publications and consult a qualified UAE tax adviser before making decisions. See all our guides or try the readiness check.