UAE e-invoicing timeline: dates and preparation for small businesses
Review the UAE e-invoicing rollout dates, the October 2026 changes and a preparation checklist for businesses above and below AED 50 million in revenue.
For a UAE business preparing for e-invoicing, there are three separate questions: whether its transactions are covered, when it must appoint an accredited service provider, and when it must start using the system. A supplier contract does not complete an integration, and an attractive PDF invoice does not establish that structured invoice data has been exchanged and reported correctly.
As checked on 26 October 2026, the immediate appointment deadline for in-scope businesses with annual revenue of AED 50 million or more is 30 October 2026. Their mandatory implementation date is 1 January 2027. The smaller-business and government phases follow later. The dates below explain which milestone belongs on the calendar and what a finance team should actually prepare.
Identify your phase before buying a solution
The starting framework covers persons conducting business in the UAE in relation to B2B and B2G transactions, with specific exclusions. Check the legal entity, its revenue category and its transaction types together. A business below the VAT registration threshold should not assume that this alone excludes it from e-invoicing; the scope assessment is a separate exercise.
The current timetable combines Ministerial Decision 244 of 2025 with the amendment in Ministerial Decision 66 of 2026.
| In-scope category | Appoint an accredited service provider by | Mandatory implementation |
|---|---|---|
| Annual revenue of 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 |
Exactly AED 50 million belongs in the first row. The original 31 July 2026 large-business appointment date was superseded; an old presentation can therefore contain an obsolete deadline even when the January implementation date remains correct. The MoF September update confirms the amended position.
The pilot and voluntary implementation phase began on 1 July 2026. B2C transactions, and persons exclusively conducting those transactions, remain outside mandatory implementation until a later ministerial decision specifies otherwise. A mixed business should assess its B2B activity rather than applying the consumer exclusion to every invoice it issues.
Understand what the provider must exchange
The official MoF portal describes an eInvoice as structured data issued and exchanged electronically and reported to the FTA. A Word document, scan, image, email or PDF alone does not meet that description. This matters when a software demonstration shows only that a familiar invoice layout can be generated.
Ask the provider to demonstrate an invoice passing through validation, delivery and reporting, with the resulting status visible to your team. Include the correction process: a rejected invoice must reach someone who can identify the incorrect field, fix the underlying record and follow the appropriate resubmission procedure. A file successfully leaving an accounting system is not sufficient evidence that the whole exchange succeeded.
For example, an illustrative trading company may create all invoices as PDFs but keep customer tax identifiers in a separate spreadsheet. Its first implementation task is to join those records reliably. Changing the PDF template while leaving customer data incomplete would leave the main operational problem unresolved.
Apply the October amendments precisely
The 19 October MoF announcement explains Ministerial Decision 197 of 2026, effective from 1 October. Transactions between members of the same Tax Group receive a temporary exclusion for twenty-four months starting on 1 January 2027. This is transaction-specific relief, not a general postponement for every sale made by every group member.
The amendment also removes the previous UAE-only storage requirement and the system-failure provisions, including the two-business-day FTA notification requirement. Businesses still have to retain required records for the applicable statutory period and provide them to the FTA when requested. An overseas hosting option therefore still needs workable access, retrieval and export arrangements.
Provider accreditation has also changed. Ministerial Decision 168 of 2026, effective from 1 October, replaces the older accreditation framework and removes its pre-approval stage. Check the provider’s actual legal name and accreditation number against the MoF accredited-provider register. A vendor’s historical announcement of preliminary approval should not be treated as current full accreditation.
A practical plan for the appointment deadline
An illustrative distributor with annual revenue of AED 60 million and in-scope business sales needs two tracked deliverables: provider appointment by 30 October 2026 and a working implementation by 1 January 2027. Assign a finance owner for the first and a named business and technical owner for the second. Keep evidence of the appointment and clarify the remaining onboarding steps with the provider and the official process.
Before signing, ask for a documented scope covering invoice volumes, credit notes, integration responsibilities, support response, testing, reporting statuses and record export. Establish who fixes source-data errors and who investigates a transmission failure. Agree how records can be retrieved if the relationship ends. These are practical contract and continuity questions, not additional statutory deadlines invented by this article.
A business with AED 8 million of annual revenue has a later phase, but it can use the extra preparation time to clean customer data and test unusual transactions. Waiting until the appointment date to discover that invoice numbers are duplicated across branches creates avoidable work.
Build a test pack from your actual invoicing process
Start with a small representative sample: a normal domestic business invoice, a discount, a credit note referring to an earlier invoice, a foreign-currency invoice where relevant, and a deliberately incomplete customer record. For each sample, retain the expected outcome, provider response and resolution of any error. Use test data or the provider’s designated test environment rather than generating accidental production obligations.
Check legal names, tax identifiers, invoice references, dates, currencies, amounts, tax categories and the link between a credit note and its original document. Compare those fields with the ordinary VAT invoice checklist, while recognising that ordinary invoice documentation and structured exchange are related but distinct requirements.
Finish with an exception rehearsal: who notices a rejection, where the team records it, who approves the correction and how the final status is confirmed. Save the evidence with your corporate-tax records using the retention rules applicable to each record type. TaxAI can support bookkeeping preparation; verify a separate accredited transmission solution for e-invoicing. The AI-answer verification workflow is useful when checking any deadline or exemption quoted by software.
Sources checked on 26 October 2026. Business examples are illustrative; apply the current official rules to the relevant entity and transactions.