VAT Group Invoice UAE: How E-Invoicing Works for Grouped Entities

UAE VAT grouping has long been one of the most useful structural tools for Dubai SMEs. Combine two or three related companies under a single TRN, file one VAT return, and net out intra-group sales so VAT is only charged on transactions with outside customers. With the UAE e-invoicing rollout now confirmed under Ministerial Decisions 243 and 244 of 2025 and the penalty framework in Cabinet Decision 106 of 2025, grouped entities need to understand exactly how PINT AE flows across member companies, and how the intra-group transition window to 1 January 2029 actually works.

This guide explains how a UAE VAT group should issue, consolidate and report e-invoices once the mandate hits, which deadlines apply to grouped entities, and what to do during the 24-month intra-group grace period.

So what is a UAE VAT group?

A VAT group under Federal Decree-Law No. 8 of 2017 and the related Cabinet decisions is a single taxable person for VAT purposes, made up of two or more legally separate UAE entities under common control that meet the FTA’s economic, financial and organisational tests. The group has one TRN, one representative member who files on behalf of all the others, and one consolidated VAT return per period.

Each member company keeps its own trade licence, its own legal personality and its own commercial obligations. The group designation is a VAT concept; it does not collapse the underlying companies. A holding company in DMCC, a trading company in Dubai mainland and a logistics subsidiary in JAFZA can sit inside the same VAT group while remaining three distinct legal entities for every other purpose.

That distinction matters once e-invoicing arrives, because PINT AE invoices are issued by legal entities, even though tax is reported for the group.

Why the FTA treats grouped entities differently

The FTA’s design choice here is a pragmatic one, and to be fair, the right one. If a VAT group runs 60 intra-group invoices a month (service charges, management fees, intercompany cost recharges), pushing all of them through Peppol on day one would flood the network with transactions that net to zero VAT anyway. The 24-month window to 1 January 2029 lets groups spend their early effort on external invoices, where the FTA actually has revenue at stake.

But “exempt from PINT AE format” is not “exempt from documentation”. Intra-group invoices still need to support the consolidated VAT return, the audit trail and any future FTA review. They simply do not have to be transmitted through an accredited service provider during the transition window.

Three invoice flows to map

Once the mandate is live for a group, three distinct invoice flows need to be mapped and handled separately.

The first two are conventional. The third is where most VAT groups will under-prepare.

Which deadline applies to your group?

The mandatory deadline is set by the consolidated revenue of the group, not by any single member. Same threshold logic the FTA uses for VAT registration and filing frequency.

If your three group members each turn over AED 20 million on their own, you are over the AED 50 million threshold once consolidated, and you sit on the large-business deadline with ASP appointment due 30 October 2026.

This trips up groups that mentally allocate deadlines per legal entity. The FTA does not. One TRN, one revenue figure, one deadline.

Peppol IDs when one TRN covers many members

Every party on the Peppol network needs a participant identifier, its address on the routing system. The FTA’s design uses the first 10 digits of the TRN, plus an FTA-issued scheme identifier, as the base address.

Inside a VAT group, that creates a routing question: if all members share one TRN, how does the network know whether an inbound invoice is destined for Member A or Member B?

The FTA solution is a member-specific suffix appended to the group’s TRN-based identifier. The representative member registers each underlying member during ASP onboarding; the ASP then routes inbound invoices to the correct member’s accounting system based on the suffix. Outbound invoices carry the issuing member’s full identifier — the group TRN base, plus the member suffix — even though the VAT credit accrues to the group as a whole.

“

The group TRN is the tax address; the member suffix is the routing address. Both belong on every external invoice.

When the FTA feed and the consolidated return drift apart

Once the group is live, the FTA’s real-time data feed will show every external invoice issued or received under the group TRN. The representative member’s quarterly VAT return must reconcile to that feed, line by line, by member.

The reconciliation logic is:

• Output VAT = sum of all PINT AE invoices issued by all members to external customers
• Input VAT = sum of all PINT AE invoices received from external suppliers by all members
• Intra-group sales = excluded from both sides (until 1 January 2029, these are not in the feed at all)
• Adjustments (credit notes, debit notes, bad debt relief) = applied to the issuing or receiving member’s records

Most accounting platforms — Zoho Books, Xero, QuickBooks, Tally, Odoo, SAP, Microsoft Dynamics 365 — can produce a member-level VAT subledger. The representative member then consolidates those subledgers into the group return. Where the data does not match the FTA feed, the discrepancy almost always sits in three places: TRN mismatches on customer master data, missing member suffixes on Peppol identifiers, or intra-group transactions accidentally routed through the ASP.

Don’t treat 2029 as a runway, even though it is

The honest answer for most groups: do not treat the 1 January 2029 deadline as a real deferral. Once your external invoicing is on PINT AE, your accounting system is already capable of generating intra-group invoices in the same format. Leaving them on PDF buys you two ongoing headaches. There’s the reconciliation drag at year-end, because auditors and the FTA both prefer one consistent format across all sales rather than a hybrid of PINT AE plus PDF. And there’s the permanent dual workflow, where your accounts team has to remember which counterparty is a group member and route invoices accordingly.

A cleaner path is to migrate intra-group invoices to PINT AE format alongside the group’s mandatory deadline, even though you are not required to. Most ASPs charge per external transaction; intra-group invoices typically incur no marginal cost on the Peppol network because both endpoints sit inside the same ASP contract.

Cases where the deferral genuinely helps: groups still finalising their internal cost-allocation methodology, groups going through member-restructuring during 2026-2027, and groups whose intra-group volume vastly exceeds external volume (rare, but it happens in management holding structures).

A member joins or leaves mid-rollout

E-invoicing adds operational steps to what was previously a tax-only event.

When a new member joins, you need to:

• Update the group’s FTA VAT group registration to add the member
• Have the ASP onboard the member as a new participant under the group TRN
• Issue the member its Peppol identifier suffix
• Migrate the member’s accounting data into the group’s consolidated chart of accounts
• Update the master customer and supplier records on the new member’s old TRN

When a member leaves, you need to:

• File the group amendment with the FTA
• Obtain a new standalone TRN for the departing member
• Sign a new ASP contract for the departing member as a standalone taxable person
• Reissue all existing customer and supplier records under the new TRN
• Plan a clean cut-over date so no invoice falls between two TRNs

Both events should be planned at least 30 days in advance once the mandate is live. The ASP onboarding queue tightens as deadlines approach.

A setup checklist

Use this checklist as you scope your implementation.

• Confirm consolidated group revenue and the resulting mandatory deadline
• Map every member’s legal name, trade licence number and accounting system
• Confirm the representative member’s responsibilities for ASP contracting
• Shortlist ASPs that support multi-entity onboarding under one master agreement
• Map all intra-group flows by counterparty and decide whether to migrate them in parallel
• Update master data: customer TRNs, supplier TRNs, addresses, electronic addresses
• Reconfirm transfer pricing files where intra-group recharges support the consolidated return
• Run a parallel-run period of at least 60 days before mandatory go-live
• Define the year-end reconciliation routine between member subledgers and the FTA feed

Where groups sit in the wider rollout

The intra-group exemption is the only structural carve-out in the rollout. Every other category — B2B, B2G, government-to-government, free-zone-to-mainland — is in scope on the standard timeline. Even branches of foreign companies operating in the UAE under a single trade licence are treated as one taxable person for the timeline, regardless of how the head office handles invoicing in its home country.

For groups that also need to think about credit notes, reverse charge accounting, and the PINT AE field map, those rules apply per invoice — not per group. A credit note from Member A to an external customer follows the PINT AE format. A credit note from Member A to Member B follows the intra-group exemption until 1 January 2029.

How Velmont Crest helps

If your group’s consolidated revenue is over AED 50 million, your real deadline is 30 October 2026 to appoint an ASP, with mandatory go-live on 1 January 2027. That leaves four to seven months of usable lead time as at mid-2026. Use it to:

1. Confirm the deadline category and consolidated revenue position
2. Run a master-data audit across all member companies
3. Shortlist ASPs and lock in pricing under a multi-entity master agreement
4. Plan the parallel run and decide on the intra-group migration approach
5. Map the year-end reconciliation routine that will run from Q1 2027 onwards

If your group is under AED 50 million, your runway is longer, but the ASP capacity squeeze in early 2027 will be tight. Booking your onboarding slot in late 2026 is the safer path.

The PINT AE rollout is the cleanest opportunity in years to fix the master-data debt most UAE groups have accumulated since VAT registration in 2018. Done well, it leaves the group on a single consolidated VAT return that reconciles to the FTA feed every quarter without manual intervention. Done late, it creates reconciliation work that compounds every period.

For tailored advisory on how your specific group structure should approach e-invoicing rollout, contact Velmont Crest — we work alongside your ASP selection, not against it.