An e-invoicing deadline involves more than choosing a software package. Your finance team needs reliable customer data, your systems need a tested exchange process, and somebody needs to own rejected documents after launch. Treating these as separate workstreams makes the transition easier to manage.
Start with two dates: when your organisation must appoint an Accredited Service Provider (ASP), and when it must implement the system. They are separate milestones. An appointment confirms your provider choice; it does not establish that every invoice scenario is ready for production.
The current rollout dates
The following dates apply to persons within the relevant scope. Ministerial Decision 244 of 2025 establishes the rollout, while Ministerial Decision 66 of 2026 changes the first revenue group's ASP appointment date to 30 October 2026. Its implementation date remains 1 January 2027.
| Group | Appoint an ASP by | Implement by |
|---|---|---|
| Revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
The pilot and voluntary implementation both began on 1 July 2026, with pilot participation subject to written agreement. The decision defines revenue using gross income for the most recent accounting period. It also excludes business-to-consumer transactions, and businesses conducting only those transactions, until a further ministerial decision. Check your specific position against the decision's definitions and scope, rather than classifying yourself from a marketing label such as “SME”.
Work backwards from a successful transaction
Write down what “ready” means before creating a project calendar. A useful acceptance test follows a transaction from its original accounting entry through validation, exchange, reporting and reconciliation. Include a credit note and a failed transaction as well as a straightforward sale.
For example, a distributor might produce invoices in an ERP but maintain customer identifiers in a separate spreadsheet. Its critical dependency is clean, consistent master data. Adding an integration before resolving that inconsistency simply moves the error into a faster process.
- Finance: identify document types, approval steps, tax treatments and the people responsible for corrections.
- Technology: establish the source system, export or connection method, field mapping and monitoring requirements.
- Operations: confirm who handles delivery failures, status enquiries and customer communications.
- Project lead: record dependencies and require evidence before marking a milestone complete.
Make provider selection a controlled handover
Ask shortlisted providers to demonstrate your own sample documents. A generic demonstration may look convincing while leaving partial credits, foreign currency or missing customer details unexplored. Obtain clear answers about onboarding inputs, testing access, support responsibilities and how transaction records can be exported.
Reserve time for exceptions and people
A project plan that ends at a successful API response is incomplete. Give the accounts team a simple procedure for identifying rejected documents, finding the underlying issue and deciding the correct next action. Check that leave cover and escalation contacts are available during busy periods.
Before launch, rehearse a missed acknowledgement, an incorrect customer identifier and a temporary outage. Record who investigates each case and what evidence they retain. After launch, review unresolved exceptions regularly and compare transaction records with the accounting system.
Keep a short decision log during testing. Record agreed field mappings, known limitations and the person who approved each workaround. This gives a new team member enough context to support the process without reconstructing decisions from old email threads.
The aim is a repeatable daily process with visible ownership. To discuss your organisation's preparation priorities with EMteja, contact support@infocustechnologiesllcfz.com.