The Same Mandate, Two Different Buyer Profiles
Mainland entities and free zone entities are both subject to the UAE e-invoicing mandate. Same Phase 1 / Phase 2 dates, same PINT AE format, same Peppol network. But the operational details differ enough that the right ASP for a mainland-only business may not be the right ASP for a free zone or mixed structure. This post walks through what changes - and what does not - so your procurement scorecard reflects your actual setup.
What Is the Same
- The mandate applies to both. Free zone status is not an exemption.
- PINT AE is the format for both. Same Peppol BIS Billing 3.0 base, same UBL XML.
- The 4-corner Peppol model is the routing channel for both.
- The FTA receives reporting from both.
- The AED 50M revenue threshold applies per legal entity, regardless of where the entity sits.
- The ASP appointment deadline (30 October 2026 for Phase 1) applies to both.
What Is Different
1. VAT Categorisation Complexity
Mainland-to-mainland transactions are typically straightforward: standard 5 percent unless an item is zero-rated or exempt. Free zone transactions add categories:
- Designated zone to designated zone supply of goods - may be out of scope
- Designated zone to mainland - standard 5 percent
- Non-designated free zone treatment - effectively mainland for VAT
- Goods vs services distinction in designated zones (services typically do not benefit from the out-of-scope treatment)
Each combination has a specific PINT AE tax category code. Your ASP must handle the categorisation logic, not punt it back to you.
2. Customs and Cross-Border References
Free zones operating in import-export (especially designated zones like JAFZA and KIZAD) routinely reference customs declarations and Bill of Entry numbers on invoices. PINT AE supports these via specific reference fields. Mainland operations rarely need this. If you are in this category, ask the ASP to demonstrate customs reference handling in their sandbox.
3. Multi-Entity Group Structures
It is very common for a UAE group to operate one mainland LLC plus one or more free zone entities under common ownership. Intra-group transactions between these entities are real PINT AE invoices, not internal transfers. The ASP must support:
- One subscription, multiple entities each with their own TRN and Peppol participant ID
- Distinct invoice numbering per entity
- Cross-entity AR-to-AP flow visibility (you raise an invoice in Entity A; it lands as a bill in Entity B; both are reported to the FTA correctly)
Mainland-only buyers often miss this requirement when picking an ASP because their procurement was scoped for a single entity. Six months later they realise they need to add a free zone subsidiary and discover the ASP charges per entity.
4. Legal Entity Documentation
Free zone entities are licensed by free zone authorities (DMCC, JAFZA, ADGM, RAKEZ, etc.) rather than the Department of Economic Development. The ASP needs to handle the licence reference and any free-zone-specific identifiers, not just a trade licence number.
5. Audit and Inspection Reach
The FTA has audit jurisdiction over both. Free zone authorities additionally have their own compliance regimes that may interact with your invoice data. Confirm with your ASP that the archive is accessible if a free zone authority audit requests historical documents.
The Buyer Profile Matrix
Profile A — Mainland Only
Simplest case. Look for an ASP that handles standard mainland VAT scenarios well and has a strong ERP connector for your stack. Free-zone-specific features are not required.
Profile B — Single Free Zone Entity (Non-Designated)
DMCC, DIFC, ADGM. Effectively mainland for VAT. The ASP needs to recognise the zone status (so addresses and references are formatted right) but the tax categorisation logic is the same as mainland.
Profile C — Single Free Zone Entity (Designated)
JAFZA, Hamriyah, KIZAD. Out-of-scope handling for inter-designated-zone goods, customs reference support, careful goods vs services distinction. Ask for sandbox demonstration of these patterns specifically.
Profile D — Mixed Mainland + Free Zone Group
The most demanding case. You need everything in profiles A, B, and C, plus multi-entity subscription, intra-group invoice handling, and clear entity-level reporting. This is where ASP selection most affects long-term cost and operability.
Questions to Ask Specifically About Your Free Zone Setup
- How do you handle designated zone vs non-designated zone classification on the supplier side?
- Can you reference customs declarations and Bill of Entry numbers in PINT AE?
- For my multi-entity group, is pricing per entity or per subscription?
- How is invoice numbering managed when each entity has its own series?
- Do you have customer references in JAFZA, DMCC, ADGM specifically?
- How quickly can I add an additional entity if my group restructures?
- If a free zone authority requests historical invoices, what is the export process?
How InvoiceNet Handles Free Zones
InvoiceNet operates from DMCC and supports the full range of UAE entity structures including mainland LLC, designated free zone, non-designated free zone, and mixed group setups. Multi-entity subscriptions are priced for groups, not punished for them. Talk to us about your specific entity map and we will run the buyer's checklist with you against your real configuration.