UAE E-Invoicing: What DIFC and Free Zone Companies Must Do by 30 October

The UAE Electronic Invoicing System is live. The pilot programme and voluntary adoption window opened on 1 July 2026, following the Ministry of Finance's confirmation on 30 June that the full five-corner ecosystem was operational. For businesses with annual revenue of AED 50 million or more, the deadline to appoint an Accredited Service Provider (ASP) is now 30 October 2026, extended from 31 July by Ministerial Decision No. 66 of 2026. The go-live date of 1 January 2027 did not move.

General guides cover the timeline well enough. What they skip is the question that actually occupies finance teams in the DIFC, ADGM and other free zones: which entities in the group are in scope, what happens to intra-group recharges, and how e-invoice data interacts with transfer pricing and the audited accounts free zone regulators already require. This article works through those questions and ends with a 90-day plan.

The framework in one paragraph

The regulation requires structured electronic invoices for business-to-business and business-to-government transactions, exchanged and reported through a five-corner model: the supplier, the supplier's ASP, the buyer's ASP, the buyer, and the Federal Tax Authority. Invoices use the PINT AE format, the UAE customisation of the Peppol International invoice model, validated against the Ministry of Finance data dictionary. The legal basis is the October 2024 amendments to the VAT and Tax Procedures decree-laws (Federal Decree-Laws No. 16 and 17 of 2024), Ministerial Decisions No. 243 and 244 of 2025, Cabinet Decision No. 100 of 2025 amending the VAT Executive Regulation, and Cabinet Decision No. 106 of 2025 on penalties. ASP eligibility sits in Ministerial Decision No. 64 of 2025 as amended by Ministerial Decision No. 56 of 2026.

A PDF, a scanned document or an emailed invoice is not an electronic invoice under this regime. From your mandatory date, in-scope invoices must be issued and transmitted through your ASP within 14 days of the business transaction date.

Timeline

The Ministry has described the October extension as a final adjustment. We would plan on that basis.

Who is in scope: the free zone entity checklist

Most commentary describes the mandate as applying to "VAT-registered businesses". That is the practical Phase 1 population, but it is not quite how the rules are drafted. Ministerial Decision No. 243 of 2025 frames the system around persons conducting business in the UAE and their business transactions, with specific exclusions, rather than around VAT registration as such. Onboarding runs through EmaraTax using the entity's Tax Identification Number, and the guidance indicates that a person in scope but not registered for any tax must register with the FTA to obtain a TIN. Sources differ on how far this reaches for entities with no taxable supplies, so for anything other than a VAT-registered trading company, confirm against the FTA's current guidance before deciding an entity is out.

Working through the typical DIFC and free zone entity types:

• Operating companies and regulated firms. In scope on the normal timetable. If the entity is near the AED 50 million threshold, document how and for which year revenue has been measured, and confirm the basis against the FTA's guidance.
• Holding companies. A holding company whose only receipts are dividends may have nothing to issue. It almost certainly has something to receive: audit, registered office, legal and group services charges. Receiving is part of implementation; suppliers will use a placeholder identifier for domestic buyers until you have onboarded.
• SPVs and prescribed companies. An SPV earning rent, licence fees or interest is making supplies. Commercial rent is standard-rated; the decision excludes financial services that are exempt or zero-rated under Article 42 of the VAT Executive Regulation. Mixed flows need a line-by-line view, not an entity-level assumption.
• Foundations. A foundation holding family assets with no trading activity is unlikely to issue business invoices, but will receive them from council members, its registered agent and advisers. Any charge it makes to underlying entities needs checking.
• Fund vehicles and managers. Management fees charged by a manager to a fund are supplies of services, and in our experience are in scope where the manager is VAT-registered. The fund may benefit from the financial services exclusion for its own supplies, but still needs to receive invoices from its administrator, auditor and custodian.
• Free zone transactions generally. The Ministry's guidelines list free zone transactions among eight special scenarios with their own field and issuance rules, alongside deemed supplies, margin scheme, summary invoices, continuous supplies, agent billing, e-commerce and exports.

The safe approach is an entity-by-entity register: name, TRN or TIN status, revenue, what it issues, what it receives, applicable exclusions, and the resulting phase. If you already maintain a DIFC compliance calendar for the group, the e-invoicing register belongs alongside it.

Intra-group recharges in DIFC and ADGM structures

A typical free zone structure has a holding company, a licensed operating entity, one or more SPVs, and a shared services entity charging management fees, secondment costs and cost-plus recharges to the rest of the group. Three things follow from the rules as published.

First, the regulation requires that each legal person is onboarded in its own right. Members of a tax group use their own TRN in their participant identifier, not the representative member's. Group-wide implementation is a provider and integration decision, not a consolidation of the obligation.

Second, transactions between members of the same VAT group stay in scope but get a 24-month grace period from 1 January 2027. That defers the obligation to around January 2029; it does not remove it. Groups that are not VAT-grouped, which in our experience includes many DIFC structures, get no deferral and their intercompany invoices follow the normal timetable.

Third, data on those recharges will reach the FTA in structured form in near real time, from both the issuing and receiving side. That is a very different position from a PDF management fee invoice raised at year-end and matched to a transfer pricing file months later.

Transfer pricing and corporate tax consistency

UAE corporate tax applies the arm's length principle to related-party transactions, and the interaction with e-invoicing is practical. The line descriptions, pricing bases, currencies and party identifiers your ASP transmits are the data the FTA will hold when it reviews your transfer pricing disclosure and local file. In our experience the recurring problems are avoidable:

• Intercompany agreements describing a cost-plus service fee while the invoices show a flat monthly amount with no reference to the agreement or mark-up.
• Recharges raised annually in a lump sum when the underlying supply is continuous. The guidelines treat continuous supplies and summary invoices as special scenarios, and the 14-day window runs from the transaction date as defined in the decision, the earlier of the transaction date and the payment date.
• Foreign currency invoices between UAE entities. VAT and the total payable must be stated in AED at the Central Bank rate, and that conversion must reconcile to the accounts.
• Free zone entities relying on Qualifying Free Zone Person status on qualifying income. Structured invoice data is a permanent, dated record of what was supplied to whom: helpful evidence if descriptions and counterparty identifiers are right, unhelpful if they are vague or inconsistent with the corporate tax return.

The invoice data model, the intercompany agreements, the transfer pricing file and the corporate tax computation should all be built from the same master data. Our overview of UAE corporate tax for DIFC companies covers the underlying rules; e-invoicing is the mechanism that will make inconsistencies visible.

Accounting systems and audited accounts

The ASP sits between your accounting or ERP system and the Peppol network; the business does not connect to a government platform. The quality of what leaves your system is therefore your responsibility, and the ASP will return invoices that fail validation against the data dictionary and the Mandatory Field Requirements specification.

For DIFC and ADGM entities, which already produce audited IFRS financial statements, e-invoice data becomes a third dataset that must reconcile with the VAT returns and the audited accounts. Three checks are worth building in before go-live:

• Master data. Customer and supplier records need legal names, TRNs or TINs, Peppol identifiers and addresses that match the FTA register. Trading names and stale TRNs will be the most common validation failures.
• Chart of accounts mapping. Every revenue and recharge line needs a tax category code, unit of measure and invoice type code. Where the accounting system cannot hold these, the mapping lives in the ASP layer and someone has to own it.
• Cut-off and completeness. Because both the issuing and receiving ASP report to the FTA, revenue in the audited accounts that cannot be tied to transmitted invoices, or an invoice register that does not agree to the VAT return, will be a question at audit and at any FTA review. If the group is mid-restructuring, timing matters more; our guide to restructuring a UAE group covers how contracts and invoicing entities move during a reorganisation.

Choosing an ASP: how to think about the decision

Atlas does not act as an Accredited Service Provider and does not sell e-invoicing software. Where clients ask for a view on providers, that comes through the group's advisory relationships and is specific to the client's systems, so we will not name providers here. What we can set out is how to frame the decision.

The regulation requires that the provider appears on the Ministry of Finance register of Accredited Service Providers published under Article 16 of Ministerial Decision No. 64 of 2025. The Ministry has published a list of pre-approved providers and indicated that final accreditation follows the accreditation procedure, so check both at the point of signing. Accreditation requires Peppol certification, ISO/IEC 27001 and a track record of operating an e-invoicing system.

Beyond accreditation, in our experience the questions that separate a good fit from a poor one for a free zone group are:

• Can one provider environment onboard several legal entities with separate TINs, and connect to more than one accounting system?
• How does it handle the special scenarios free zone groups actually use: continuous supplies, summary invoices, agent billing, exports and free zone transactions?
• What does it return when validation fails, and how quickly? With 14 days to issue and two business days to report a system failure, exception handling determines whether those windows are workable.
• Where is data hosted, and can you extract your invoice archive if you change provider later?
• What is the lead time from signature to first successful test transmission? For a 30 October appointment and 1 January go-live, this decides whether there is any testing window at all.

Appointing the provider is the regulatory deadline. Being able to issue and receive on 1 January is the operational one, and the second is harder.

A practical 90-day plan

The appointment deadline is under two months away for Phase 1 businesses and go-live is 120 days out. A 90-day plan starting now lands with a month to spare.

Days 1 to 30: scope and data

• Build the entity register, assign each entity to a phase, and confirm revenue measurement for any entity near AED 50 million.
• Map invoice flows per entity: issued and received, intercompany and third party, and which special scenarios apply.
• Check that invoice descriptions, pricing bases and frequencies agree with the intercompany agreements and transfer pricing file. Fix whichever is wrong.
• Clean master data against the FTA register, confirm EmaraTax access for every entity, and identify any entity that needs a TIN.

Days 31 to 60: appoint and integrate (appointment by 30 October)

• Shortlist providers against the criteria above, test them on your actual accounting systems, and appoint before 30 October. Keep the appointment evidence.
• Onboard each entity through EmaraTax and complete the chart of accounts mapping to tax category, unit of measure and invoice type codes.
• Agree ownership: finance for data and reconciliation, IT for integration, tax for codes and exceptions, and a named person for FTA notifications.

Days 61 to 90: test and reconcile

• Run test transmissions under the voluntary window, which sits outside the penalty regime until your mandatory date, starting with one entity and the highest-volume flow. Test receipt as well as issuance.
• Reconcile the test invoice register to the general ledger and a draft VAT return.
• Document exception handling: rejected invoices, credit notes, system failure notification within two business days, and updates to registered data within five business days.
• Train accounts payable and receivable teams, and brief the auditors on the new dataset. Multi-entity groups should treat the first entity as a controlled test and replicate.

Where Atlas fits

Our involvement is on the finance and structuring side: confirming scope across a DIFC or ADGM group, tidying intercompany invoicing so it is consistent with transfer pricing and the audited accounts, maintaining the mapping and reconciliations once live, and coordinating onboarding with the provider the client has chosen. If you would like readiness work folded into your existing accounting and tax services from Atlas, or a scoping review of which entities are in and out, contact us before the October deadline rather than after it.

This article reflects the legislation and Ministry of Finance guidance published as at 3 September 2026. Technical specifications continue to be updated; confirm the current position against the FTA's guidance before acting on any specific point.