Direct answer: If your UAE business is within the e-invoicing system and its annual revenue is AED 50 million or more, the Federal Tax Authority (FTA) says you must appoint an Accredited Service Provider (ASP) by 30 October 2026 and implement the system by 1 January 2027. The FTA restated these dates on 25 October 2026. Businesses below AED 50 million have later deadlines: appoint by 31 March 2027 and implement by 1 July 2027. First confirm that the business and transaction types fall within scope; then assess the 50 million threshold, select an eligible provider, and map the invoice data and software changes needed.
Verification date: 26 October 2026. This guide uses official Ministry of Finance (MoF) and FTA materials. It explains the published requirements but is not tax or legal advice.
What changed this week?
The underlying e-invoicing framework and phased dates were published earlier. The current development is the FTA’s 25 October reminder: the first group’s provider-appointment deadline is now only days away. The FTA says in-scope persons with annual revenues equal to or above AED 50 million must appoint an ASP no later than 30 October 2026 and implement e-invoicing by 1 January 2027. The next group, whose annual revenues are below AED 50 million, has until 31 March 2027 to appoint a provider and until 1 July 2027 to implement. These are published compliance dates, not a proposed timetable. See the FTA notice dated 25 October 2026 and the MoF announcement of the 2025 decisions.
For a Dubai or UAE business in the first group, the decision is no longer whether to start planning. It is whether provider appointment, contract, systems mapping and implementation work are on a credible path to the dates. An unintegrated accounting package, a spreadsheet invoice process or an email exchange of PDFs should be treated as a readiness issue to investigate immediately.
Who needs to act now?
The system is not simply an obligation for every person who issues any kind of document called an invoice. The MoF describes the system as applying to business-to-business (B2B) and business-to-government (B2G) transactions, subject to specified exclusions. The detailed scope and exclusions are set out in the official Ministerial Decision No. 243 of 2025 and associated guidance; check the current FTA UAE e-Invoicing resource page, which links the legislation and the MoF’s provider information.
The AED 50 million threshold separates the implementation timetable; it does not by itself determine whether a business or transaction is in scope. A company with lower revenue should not infer that it is exempt. Conversely, a business should not infer that every transaction, every customer type or every entity in a group has the same treatment. A person with a mixed operating model should review each legal entity and transaction flow against the decision and exclusions.
The relevant official concept is an electronic invoice that is structured data, issued and exchanged through the system. The FTA states that a PDF, Word document, image, scan or email is not an e-invoice simply because it is delivered electronically. A PDF may still be part of a customer-facing workflow, but it is not the structured e-invoice required by the system. Read the FTA’s definition on its official e-invoicing page.
Published deadlines at a glance
Annual revenue of AED 50 million or more
Appoint an ASP by 30 October 2026 and implement e-invoicing by 1 January 2027. Confirm appointment status and escalate contract or integration gaps now.
Annual revenue below AED 50 million
Appoint an ASP by 31 March 2027 and implement the system by 1 July 2027. Use the runway to map entities, invoice flows, data quality and systems.
The table summarizes the FTA’s 25 October 2026 notice. It does not replace the legislation. Where a group has multiple entities, unusual transactions, reorganisations, mixed revenue streams or possible exclusions, do not apply a group-wide shortcut without checking the legal position and the relevant decision. Confirm the revenue measurement and entity treatment with a UAE tax adviser or the FTA’s published guidance where the answer affects the deadline.
What the system changes in day-to-day operations
Moving to structured e-invoicing is not just a software purchase. The required exchange needs accurate business and transaction data to pass between the issuer, its ASP, the recipient and the reporting system. The official MoF overview says invoices and electronic credit notes must carry prescribed data and that both issuers and recipients perform their obligations through appointed ASPs. A credit note may be required where a transaction is cancelled, consideration is reduced, a refund is made, or an administrative or numerical error occurs, subject to the detailed rules.
That has practical consequences for a growing UAE company. Finance teams may need to standardize customer identifiers, tax registration details, item and service descriptions, units, currencies, payment terms and invoice references. Operations teams should check whether approved quotations, delivery records, purchase orders, project codes and acceptance steps produce the information finance needs. IT or an outsourced software provider needs to understand where data originates and whether it can be transmitted in the required structure. These are implementation actions to prepare for the law, not additional legal requirements asserted by this article.
For founders entering the UAE, the launch plan should include invoice readiness alongside licence activity, premises, banking and tax registrations. A company that can legally trade but cannot reliably generate the required invoice data may face avoidable disruption when it becomes subject to the system. Review THRAVOT’s existing Company Formation and UAE Market Entry pages for the broader sequencing of setup and launch decisions.
Practical readiness plan
1. Decide scope at the legal-entity and transaction level
List each UAE legal entity, its licence and operating activity, the customer types it bills, the invoice and credit-note flows it uses, and any government transactions. Identify B2B and B2G flows and compare them against Ministerial Decision No. 243 of 2025 and its exclusions. Do not use VAT registration, a free-zone licence, a mainland licence or an accounting-software subscription as a substitute for this scope review.
2. Confirm the correct implementation band
Gather the revenue information and period records needed to test the applicable threshold for each relevant person. If ownership, group reporting, a recent acquisition or a restructuring complicates the calculation, record the issue and obtain advice before deciding which date applies. Keep the basis and source documents with the compliance file. This is a prudent control; the exact legal test should be taken from the current decision and guidance.
3. Check provider status and appoint deliberately
Review the MoF’s official list of pre-approved or accredited service providers linked from the FTA e-invoicing page. Ask each candidate to confirm its current status, the entities and transaction types its service can handle, integration requirements, onboarding lead time, support coverage, data-export arrangements, fees, service levels and exit process. An announcement or sales presentation is not proof that a provider is currently accredited. Do not select solely on price if the service cannot fit the company’s ERP, accounting system or billing workflow.
4. Map data and integration before promising a go-live date
Document how an invoice is created, approved, transmitted, corrected and archived. Identify duplicate customer records, missing fields, inconsistent product codes, manual spreadsheets and credit-note workflows. Ask the ASP and software vendors to demonstrate a test case using the company’s actual transaction patterns, with sensitive data handled appropriately. Confirm who owns exception handling when an invoice fails validation or a system is unavailable. The FTA’s latest notice tells affected persons to select an ASP, contract and integrate, and complete the relevant procedures on EmaraTax; treat those as connected workstreams.
5. Assign owners and evidence
Name a business owner, finance lead, software contact and adviser. Keep the provider appointment confirmation, signed scope, data map, test results, open-issue list, training record and implementation decision together. Schedule a management review before the applicable deadline. If a gap threatens the timetable, escalate it early to the provider and obtain advice on the available compliant route; do not assume that a contract alone completes implementation.
What the published rules say about penalties
The FTA’s 25 October notice says the administrative penalty for delay in implementation, including failure to appoint an ASP within the prescribed deadline, is AED 5,000 for each month or part of a month. The amount appears in the table annexed to Cabinet Decision No. 106 of 2025. That decision also lists separate penalties for other failures, such as missing electronic invoices, credit notes and system-failure notifications, with their own conditions and limits.
This guide does not calculate a business’s exposure or say that every late or incorrect event automatically results in a particular assessment. The legal decision and implementing rules govern, and the facts matter. The sensible response is to use the published penalty as a reason to document and resolve gaps, not to rely on informal assumptions or wait for an enforcement contact.
What is still uncertain for an individual business?
The FTA’s notice confirms the revenue bands and dates, but it cannot settle every entity’s scope from a short description. The detailed decisions, transaction facts, exclusions, group structure and applicable revenue test all matter. The FTA page itself points readers to the MoF portal as the official source for the system’s introduction. If an adviser’s summary, software vendor’s marketing page or online article conflicts with the legislation, compare the primary documents and seek a written, transaction-specific view.
Further operational details may also depend on the provider and the current EmaraTax procedures. Confirm the active provider list, onboarding and activation steps, supported invoice scenarios, technical specifications and any updates directly against the latest MoF/FTA material before spending or changing systems. This article is verified on 26 October 2026 and should be rechecked before acting on a future date.
Recommended next steps for UAE founders
If you are in the AED 50 million-or-more band, treat 30 October 2026 as an urgent appointment milestone: check your scope and band, choose a currently eligible ASP, record the appointment, and agree a credible integration plan towards 1 January 2027. If you are below AED 50 million, use the longer runway to complete entity and transaction mapping, compare suitable providers, clean master data and test the workflow before the March and July 2027 milestones. If your classification is uncertain, do not pick the later dates by assumption.
For founders still setting up or restructuring a UAE operation, e-invoicing is one part of launch readiness. Map it with licence scope, customer route, finance systems and regulatory obligations before committing to a setup path. THRAVOT’s UAE Market Entry service and Company Formation service pages explain the relevant planning routes. They do not replace legal, tax or technology-provider advice.
Frequently asked questions
1. What is the nearest UAE e-invoicing deadline?
For persons subject to the system whose annual revenues are AED 50 million or more, the FTA states that an ASP must be appointed by 30 October 2026. Implementation is due by 1 January 2027. The lower-revenue group has later dates.
2. When must a UAE business below AED 50 million appoint a provider?
The FTA’s 25 October 2026 notice says persons subject to e-invoicing with annual revenues below AED 50 million must appoint an ASP by 31 March 2027 and implement the system by 1 July 2027.
3. Does a PDF invoice sent by email count as an e-invoice?
No. The FTA defines an e-invoice as structured invoice data exchanged electronically through the system. It expressly says unstructured PDFs, Word files, scans, images and emails are not e-invoices.
4. Does the AED 50 million test decide whether I am in scope?
No. The threshold is used for phased timing in the FTA notice. Scope depends on the legislation, transaction type and any applicable exclusions. Review Ministerial Decision No. 243 of 2025 and the official MoF/FTA guidance for each relevant entity.
5. Is a UAE free-zone company automatically outside the system?
Do not assume that. A free-zone licence by itself does not answer whether the person or its transactions fall within the e-invoicing rules. Check the legal scope and exclusions, the actual invoicing flows and the entity’s facts with an appropriate adviser.
6. What should I ask an e-invoicing provider before signing?
Confirm current accreditation or pre-approval status, coverage of your transaction types, system integrations, onboarding time, fees, support, data access/export, test procedures, exception handling and exit terms. Verify provider status against the official MoF list linked from the FTA e-invoicing page.
7. What penalty applies for missing the ASP or implementation deadline?
The FTA states that AED 5,000 applies for each month or part-month of delay in implementation, including failure to appoint an ASP on time. Cabinet Decision No. 106 of 2025 contains the penalty table and separate rules for other violations. Get advice on how it applies to your circumstances.
Plan your UAE launch with the e-invoicing workstream included
Use THRAVOT’s Market Entry Diagnostic to map your business model, setup route and launch-readiness questions, including the invoice processes that need to be checked with your tax and technology advisers. If you prefer to discuss the route before completing it, message THRAVOT on WhatsApp.