If your business is registered in DMCC, JAFZA, DIFC, or ADGM, you may be operating under the assumption that your free zone status offers some form of shelter from the UAE’s new e-invoicing mandate. It does not. Under Cabinet Decision No. 64 of 2025 and the supporting Ministerial Decisions No. 243 and 244 of 2025, free zone companies e-invoicing in UAE obligations are identical to those of mainland entities. There is no carve-out for free zone status in the legislation.
This blog explains what the mandate means for each of these four major zones, where the real compliance challenges lie, and what your finance team should be doing right now.
The Federal Tax Authority (FTA) requires all persons doing business in the UAE to issue structured electronic invoices for B2B and B2G transactions. This applies regardless of whether a company holds Qualifying Free Zone Person (QFZP) status, operates within a Designated Zone, or is registered for VAT.
The phased rollout follows a revenue-based threshold:
Cabinet Decision No. 106 of 2025 sets the penalty framework. This includes AED 5,000 per month for failure to appoint an ASP or implement the system, and AED 100 per document for late transmission (capped at AED 5,000 per month).
The compliance path is the same for every entity: issue invoices in the PINT-AE format (Peppol International Invoice, UAE Profile), transmit them through an ASP on the Peppol network, and allow real-time tax data reporting to the FTA through the 5-corner model.
DMCC (Dubai Multi Commodities Centre) hosts over 25,000 member companies, many of them in commodities trading, professional services, and re-export operations. For most DMCC-registered businesses, the challenge is not awareness of the mandate. It is operational readiness.
Commodity trading firms frequently deal with multi-currency invoicing, cross-border counterparties, and high transaction volumes. Each invoice must now carry line-level VAT classification (standard-rated, zero-rated, or exempt), comply with the UAE data dictionary, and flow through an ASP in structured XML. Companies that currently rely on PDF invoices or manual Excel-based processes face significant data mapping and system integration work.
For DMCC entities using ERP platforms like SAP, Oracle, or Zoho, the gap is typically in PINT-AE field mapping and ASP connectivity. For those on lighter accounting tools or custom-built systems, a middleware layer or API-based integration may be the most practical path forward.
JAFZA (Jebel Ali Free Zone Authority) is one of the largest trade and logistics hubs in the region, with a concentration of manufacturing, warehousing, and distribution operations. Many JAFZA companies issue thousands of invoices per month across multiple buyer categories, including mainland entities, other free zone businesses, and international clients.
The specific complexity for JAFZA entities lies in Designated Zone treatment. Goods moving between Designated Zones may attract different VAT treatment than goods moving from JAFZA to the mainland. Under the e-invoicing framework, every invoice must accurately reflect this at the line-item level. Errors in tax classification can trigger validation failures at the ASP level, meaning the invoice never reaches the buyer.
JAFZA businesses that supply government entities should note that B2G invoicing falls under Phase 1, regardless of the supplier’s revenue. If your buyer is a federal or emirate-level public body, your compliance timeline may be earlier than expected.
DIFC (Dubai International Financial Centre) operates its own legal framework, regulator (the DFSA), and court system. This creates a unique compliance layer for DIFC-registered entities. While DIFC has its own data protection regime, e-invoicing falls under the federal FTA framework, not the DFSA.
This distinction matters for multi-entity groups. A holding company in DIFC with subsidiaries on the mainland or in other free zones must ensure that each entity’s invoicing system connects to an ASP independently. Intercompany invoices between a DIFC entity and a mainland subsidiary are B2B transactions under the mandate and must flow through the Peppol network in PINT-AE format.
For DIFC firms in asset management, consulting, or fintech, invoice volumes tend to be lower but the data accuracy requirements are just as strict. The 50-plus mandatory fields in the PINT-AE schema include buyer and seller identifiers, tax registration numbers, and detailed line-level tax breakdowns. Even a firm issuing 50 invoices a month must get every field right.
A readiness assessment that maps your current invoicing workflow against the PINT-AE data dictionary is the most effective first step.
ADGM (Abu Dhabi Global Market) mirrors DIFC in structure, with its own Financial Services Regulatory Authority and separate data protection regulations. Like DIFC, ADGM entities fall under the FTA for e-invoicing purposes. There is no separate ADGM e-invoicing regime.
ADGM-registered companies are concentrated in financial services, wealth management, and professional advisory. Many of these firms serve clients across the UAE and GCC, which means their invoicing must handle both domestic and cross-border scenarios. Cross-border B2B invoices to GCC buyers are expected to fall within scope from Phase 2 onwards, with PINT-AE as the mandatory format.
For ADGM entities, the operational challenge often sits with ERP compatibility. Firms using QuickBooks, Xero, or Sage may find that their default invoice templates lack several mandatory PINT-AE fields. Bridging this gap requires either an ERP upgrade, a middleware connector, or a managed compliance service that handles format conversion and ASP transmission on the company’s behalf.
Regardless of which zone you operate from, the preparation steps are consistent. First, confirm your phase allocation based on annual revenue and transaction type. Second, audit your current invoicing workflow against the PINT-AE data dictionary requirements. Third, evaluate your ERP or accounting system’s ability to generate structured XML output. Fourth, shortlist and appoint an ASP before the relevant deadline. Fifth, run end-to-end testing, including validation checks, before go-live.
Companies that lack in-house tax technology expertise or are running on legacy systems benefit most from working with an advisory partner who understands both the regulatory framework and the practical realities of ERP integration. This is especially true for multi-entity groups operating across different free zones, where each entity may sit on a different system and face different VAT treatment scenarios.
The October 2026 ASP appointment deadline may feel distant. But once you factor in vendor evaluation, system configuration, data mapping, user acceptance testing, and staff training, the preparation window is already tight.
No. Under Ministerial Decision No. 243 of 2025, all persons doing business in the UAE must comply with the e-invoicing mandate. This includes companies registered in DMCC, JAFZA, DIFC, ADGM, and every other UAE free zone. Free zone status, Designated Zone treatment, or QFZP eligibility does not create an exemption from the invoicing format requirements. B2B and B2G invoices must follow the same PINT-AE structure as mainland entities.
Phase 1 companies (annual revenue of AED 50 million or more) must appoint an Accredited Service Provider by 30 October 2026 and implement e-invoicing by 1 January 2027. This deadline applies equally to mainland and free zone businesses, as confirmed by the Ministry of Finance’s amendment to Ministerial Decision No. 244 of 2025. The mandatory go-live date has not changed despite the ASP appointment extension.
E-invoicing in the UAE is governed by the Federal Tax Authority, not by free zone regulators like the DFSA (DIFC) or FSRA (ADGM). While DIFC and ADGM maintain their own legal and data protection frameworks, the e-invoicing mandate is a federal tax obligation. Every DIFC and ADGM entity issuing B2B or B2G invoices must use the PINT-AE format and transmit through an ASP on the Peppol network, just like any mainland business.
Designated Zone VAT relief applies to specific goods movements, not to invoicing format. A JAFZA or DMCC company operating within a Designated Zone must still issue e-invoices in PINT-AE XML through an ASP. The difference is in the VAT classification applied at the line-item level. Goods moving between Designated Zones may be treated differently for VAT than goods entering the mainland. Accurate tax category mapping is critical to avoid ASP-level validation failures.
Yes, in most cases. Companies do not need to replace their accounting software. However, standard QuickBooks or Zoho invoice templates typically lack several mandatory PINT-AE fields. The solution is either an ERP configuration update, a middleware connector, or a managed service that extracts invoice data and converts it to PINT-AE XML before transmitting it through the ASP. A compliance gap assessment is the recommended starting point.
