Insights E-Invoicing
VAT Group Invoice UAE: How E-Invoicing Works for Grouped Entities
How UAE VAT-grouped entities issue, consolidate and report e-invoices across member companies — intra-group exemption to 1 January 2029, then full PINT AE flow.
Key takeaways
- VAT group = one TRN, one representative member, one consolidated VAT return
- Each member keeps its own trade licence, TIN-based Peppol address, and accounting records
- Intra-group invoices are in scope under MD 243; a 24-month grace period from 1 January 2027 defers compliance to 1 January 2029
- External invoices follow the same rollout as standalone businesses — based on the group's consolidated revenue
- Representative member files one VAT return; e-invoice data must reconcile to that consolidated position
A VAT group invoice in the UAE works differently from a standalone company’s invoice, and e-invoicing is about to make that difference far more visible. UAE VAT grouping — sometimes called tax grouping — has long been one of the most useful structural tools for Dubai SMEs. Combine two or three related companies under a single TRN through VAT group registration in the UAE, file one consolidated 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 Decision 243 of 2025 and Ministerial Decision 244 of 2025, and the penalty framework in Cabinet Decision 106 of 2025, grouped entities need to understand exactly how PINT AE e-invoicing 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. If you would rather have this scoped and run for you, our e-invoicing setup support in the UAE covers multi-entity ASP onboarding and group master-data cleanup end to end.
1 Jan 2029
End of the intra-group grace period
What is a UAE VAT group?
A UAE VAT group (a tax group for VAT purposes) under Federal Decree-Law No. 8 of 2017 and the related Cabinet decisions is a single taxable person, made up of two or more legally separate UAE entities under common control that meet the FTA’s economic, financial and organisational tests for VAT group registration in the UAE. The group has one TRN, one representative member who files on behalf of all the others, and one consolidated VAT return per period. The eligibility criteria for creating a VAT group, and the process to register it, sit with the FTA — this guide picks up after registration, at the point where each member has to start issuing e-invoices.
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. In other words, UAE VAT grouped entities keep their separate invoicing identity even while filing under a single consolidated return.
One further separation is worth stating outright, because finance teams routinely assume the two travel together. A VAT group is not an accounting consolidation. The FTA’s tests for grouping look at common control and at economic, financial and organisational ties; they are not the control tests that decide whether a subsidiary is consolidated into your group’s financial statements. So it is entirely normal to have a subsidiary that sits inside the VAT group but is equity-accounted rather than consolidated, or a consolidated subsidiary left outside the VAT group because it did not meet the FTA’s criteria. Map the two populations side by side once, in writing. Where the lists diverge, that gap is exactly where intragroup invoices go missing at period end.
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 “not yet required” 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.
Where the relief actually lives — and where it does not
This is the single most misquoted point in UAE e-invoicing commentary, so it is worth being exact. The relief is not an exclusion in Ministerial Decision 243 of 2025. Article 4 of that Decision lists the excluded business transactions — sovereign government activity, international passenger transport by an airline where an electronic ticket is issued, ancillary airline passenger services documented by an Electronic Miscellaneous Document, international transport of goods by an airline under an airway bill for 24 months, and financial services that are exempt or zero-rated under Article 42 of the VAT Executive Regulation. Intra-group transactions are not on that list.
The relief lives in the UAE Electronic Invoicing Guidelines issued by the Ministry of Finance. Section 6.3.2 states that under MD 243 of 2025 “Business Transactions carried out between members of the same VAT group fall within scope and are not excluded solely by reason of being intra-group,” and section 6.3.2.1 records that MD 244 of 2025 “does not contain any provision addressing the applicability of Electronic Invoicing on intra-group transactions.” What the Guidelines then grant is a temporary grace period of “twenty-four (24) months commencing on 01 January 2027,” during which the MD 243 obligations “will not be required to be implemented” for those transactions.
| Question | The answer, and where it comes from |
|---|---|
| Are intra-group transactions in scope? | Yes — MD 243 of 2025, as confirmed at section 6.3.2 of the UAE Electronic Invoicing Guidelines |
| Are they an Article 4 exclusion? | No. Article 4 of MD 243 lists sovereign activity, specified airline services and exempt or zero-rated financial services. Nothing about groups |
| Does MD 244 defer them? | No. The Guidelines state MD 244 contains no provision on intra-group transactions |
| So what defers them? | A grace period granted in the Guidelines: 24 months commencing 1 January 2027 |
| Does the grace period remove them from scope? | No. The Guidelines say it “affects the timing of compliance only” |
| What happens on 1 January 2029? | The requirements apply in full, in accordance with the group’s applicable mandatory implementation phase |
The practical consequence of that distinction is about risk, not semantics. A grace period published in guidance can be revised, extended or narrowed by a further version of the same guidance — the document is already at version 1.1 — whereas an exclusion written into a Ministerial Decision would need a new Decision to change. Groups planning a 2028 migration should build in a check of the current Guidelines version rather than treating 1 January 2029 as immovable.
Three invoice flows to map
Once the mandate is live for a group, three distinct invoice flows need to be mapped and handled separately.
| Flow | Format requirement | Who transmits it |
|---|---|---|
| Member-to-external customer | PINT AE XML via ASP — mandatory from group’s deadline | The issuing member, through the group’s ASP |
| External supplier to member | PINT AE XML received via ASP — mandatory from supplier’s deadline | The supplier’s ASP transmits, group’s ASP receives |
| Member-to-member (intra-group) | In scope, but compliance not required during the grace period to 1 January 2029 | No external transmission required in the window — book-to-book entry |
| Member-to-external customer with no Peppol ID | PINT AE XML, plus a conventional tax invoice for the buyer | The Guidelines require the predefined endpoint 0235:9900000098 on the electronic invoice |
| Member exporting outside the UAE | PINT AE XML; the tax invoice for VAT purposes is the electronic invoice | Where the overseas buyer has no Peppol ID, the predefined endpoint 0235:9900000099 is mandatory |
The first two are conventional. The third is where most VAT groups will under-prepare. The last two are the ones that surface late in testing, because they only appear when a member starts invoicing a counterparty that is not yet on the network — which, through 2027, will be most of them.
The Guidelines also settle a question groups ask early: because the revised definition of a tax invoice in the VAT Decree-Law now includes an electronic invoice, a supplier may not need to issue a separate tax invoice when it sends an electronic invoice to a buyer that has implemented e-invoicing, provided the document meets Article 65 of the Decree-Law and Article 59 of the VAT Executive Regulation. Where the buyer has not implemented yet, a regular tax invoice is still required in addition.
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.
| Category | ASP appointment deadline | Mandatory go-live | Source |
|---|---|---|---|
| Revenue ≥ AED 50,000,000 | 30 October 2026 | 1 January 2027 | MD 244 of 2025, Article 5(1)(a), as amended by Ministerial Decision 66 of 2026 |
| Revenue < AED 50,000,000 | 31 March 2027 | 1 July 2027 | MD 244 of 2025, Article 5(1)(b) |
| Government entities | 31 March 2027 | 1 October 2027 | MD 244 of 2025, Article 5(1)(c) |
| Voluntary adoption | Any time from 1 July 2026 | Immediate, with full technical compliance | MD 244 of 2025, Article 4 |
| Pilot programme | Taxpayer Working Group only | Commenced 1 July 2026 | MD 244 of 2025, Article 3(4) |
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.
Note the first row carefully. Article 5(1)(a) as originally issued set that appointment deadline at 31 July 2026; Ministerial Decision 66 of 2026, issued 6 May 2026, moved it to 30 October 2026. Any plan, checklist or vendor proposal still working to the July date is reading the superseded text. The 1 January 2027 go-live was not moved.
This trips up groups that mentally allocate deadlines per legal entity. The FTA does not. One TRN, one revenue figure, one deadline.
Two further points from MD 244 are easy to miss and both affect groups. Business-to-consumer transactions are not subject to the Electronic Invoicing System at all until the Minister decides otherwise, and a person engaged exclusively in B2C transactions is outside the system — so a retail-facing member of an otherwise B2B group may have very little to transmit. And Article 5(1)(d) closes the loop: once the three phases are complete, any person or government entity subject to the system must appoint an ASP and implement it, with no residual category left outside.
Peppol IDs when one VAT TRN covers many members
Every party on the Peppol network needs a participant identifier, its address on the routing system. Under the FTA’s design, that identifier combines the UAE scheme code (a fixed value of 0235) with the party’s Tax Identification Number (TIN) — the first 10 digits of its Corporate Tax TRN.
Inside a VAT group, that creates a routing question: the members share one VAT TRN, so how does the network know whether an inbound invoice is destined for Member A or Member B?
The answer is that the Peppol identifier is not built on the shared VAT TRN at all. The Ministry of Finance has confirmed that even inside a tax group, each member’s TIN is the first 10 digits of its own Corporate Tax TRN — not the group representative’s. Each member therefore has a distinct End Point (scheme code 0235 plus its own TIN), registered separately by the ASP, and inbound invoices route to the correct member on that basis. Outbound invoices carry the issuing member’s own End Point, even though the VAT is accounted for by the group as a whole.
The shared VAT TRN is not the routing address. Each member routes on its own TIN — the first 10 digits of its own Corporate Tax TRN.
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, wrong or missing member TINs 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).
What non-compliance costs, per member
Penalties do not consolidate the way the VAT return does. Cabinet Decision No. 106 of 2025 sets the administrative penalties for breaches of the e-invoicing legislation, and they attach to the issuer or recipient — which, inside a VAT group, means the individual member company, not the representative member. Six members that all miss an ASP appointment are six exposures, not one.
| Violation | Administrative penalty |
|---|---|
| Failure by the issuer to implement the Electronic Invoicing System, including failure to appoint an ASP within the timeline set by the Minister | AED 5,000 for each month or part month of delay |
| Failure by the issuer to issue and transmit an electronic invoice to the recipient through the system within the timeline | AED 100 for each electronic invoice, capped at AED 5,000 per calendar month |
| Failure by the issuer to issue and transmit an electronic credit note through the system within the timeline | AED 100 for each electronic credit note, capped at AED 5,000 per calendar month |
| Failure by the issuer to notify the FTA of a system failure within the timeline | AED 1,000 for each day of delay or part thereof |
| Failure by the recipient to notify the FTA of a system failure within the timeline | AED 1,000 for each day of delay or part thereof |
| Failure by the issuer or recipient to notify the appointed ASP of changes to data registered with the FTA within the timeline | AED 1,000 for each day of delay or part thereof |
Two features of that table shape how a group should sequence its rollout. The AED 5,000-a-month implementation penalty runs per member and does not stop accruing until the member is live, so the cheapest member to onboard is the next one — deferring the small subsidiaries is a false economy. And the daily AED 1,000 notification penalties are the ones a group is most likely to trigger accidentally, because they are administrative: a member changes its registered address or authorised signatory, nobody tells the ASP, and the clock starts.
Cabinet Decision No. 106 of 2025 also carves out voluntary adopters: its provisions do not apply to a person who issues, transmits, shares, exchanges or reports electronic invoices on a voluntary basis. A group that goes live early, before its mandatory date, is testing without penalty exposure under that Decision — which is a genuine argument for using the voluntary window from 1 July 2026 rather than waiting.
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
- Register the member’s own End Point with the ASP (scheme code 0235 plus its TIN)
- 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. Two adjacent flows are worth reading alongside this one: how self-billed invoices work under UAE e-invoicing when a member is the recipient, and how summary tax invoices consolidate high-volume supplies to a single grouped customer.
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:
- Confirm the deadline category and consolidated revenue position
- Run a master-data audit across all member companies
- Shortlist ASPs and lock in pricing under a multi-entity master agreement
- Plan the parallel run and decide on the intra-group migration approach
- 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 advice on how your specific group structure should approach the e-invoicing rollout, our e-invoicing setup advisory for UAE VAT groups works alongside your ASP selection, not against it. You can also contact Velmont Crest directly to scope a multi-entity readiness review.
Disclaimer: Velmont Crest is a DED-licensed UAE accounting firm providing advisory, preparation and compliance support services. We are not the Federal Tax Authority, the Ministry of Finance, a law firm, an FTA-registered tax agent, or an Accredited Service Provider. The UAE e-invoicing framework is being implemented in phases and the supporting guidance has already been revised — verify the current position against the Ministerial Decisions and the current version of the UAE Electronic Invoicing Guidelines before acting, and take advice specific to your group structure.
References
- Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System — UAE Ministry of Finance
- Ministerial Decision No. 244 of 2025 on the Implementation of the Electronic Invoicing System — UAE Ministry of Finance
- Ministerial Resolution No. 66 of 2026 amending Ministerial Resolution No. 244 of 2025 — UAE Ministry of Finance
- UAE Electronic Invoicing Guidelines, version 1.1 (1 June 2026) — UAE Ministry of Finance
- Cabinet Decision on Violations and Administrative Penalties for the Electronic Invoicing System — UAE Ministry of Finance
- UAE Ministry of Finance — eInvoicing initiative
Frequently asked questions
- Does a UAE VAT group need to issue e-invoices between member companies?
- Not in practice until 1 January 2029, but the reason matters. The Ministry of Finance's UAE Electronic Invoicing Guidelines state plainly that under Ministerial Decision 243 of 2025 transactions between members of the same VAT group fall within scope and are not excluded merely for being intra-group, and that Ministerial Decision 244 of 2025 contains no provision on intra-group transactions at all. What the Guidelines then grant is a temporary grace period: for 24 months commencing 1 January 2027, the e-invoicing obligations under MD 243 are not required to be implemented for transactions between members of the same VAT group. It affects timing only. When it expires, the requirements apply in full.
- Where does the 1 January 2029 intra-group date actually come from?
- From section 6.3.2.1 of the UAE Electronic Invoicing Guidelines published by the Ministry of Finance, not from the legislation. The Guidelines grant a grace period of 24 months commencing 1 January 2027 for business transactions carried out between members of the same VAT group, which runs out at the end of 2028. That is worth knowing because a grace period in guidance is a different kind of instrument from an exclusion in a Ministerial Decision. Cite the Guidelines, keep the version you relied on, and re-check it before you plan around the date — the Guidelines have already been revised once.
- Does the intra-group grace period start later for a smaller VAT group?
- No, and this is the detail that catches groups under the AED 50 million threshold. The Guidelines fix the grace period at 24 months commencing 1 January 2027 for intra-group transactions generally; they do not tie the start to each group's own mandatory phase. A group whose external go-live is 1 July 2027 therefore gets roughly eighteen months of intra-group relief, not twenty-four. Plan the intra-group migration against 1 January 2029 as a fixed date rather than as a rolling two-year window from your own go-live.
- Which deadline applies to a VAT group — based on which company's revenue?
- On the group's consolidated revenue, treated as one taxable person — not on any single member. AED 50 million or more across all members, and the group appoints an ASP by 30 October 2026 and goes live on 1 January 2027. Under AED 50 million, it's 1 July 2027 with ASP appointment by 31 March 2027.
- Does each member company need its own ASP, or can the group share one?
- A single ASP provider can serve every member under one master agreement, but each member is onboarded separately and registered as its own End Point. The identifier each member needs is its own Peppol participant ID — the UAE scheme code (fixed value 0235) plus that member's own Tax Identification Number, which is the first 10 digits of its own Corporate Tax TRN, not the group representative's TRN. Most ASPs onboard multiple entities under one agreement and bill per member.
- How does the VAT return reconcile to PINT AE data when one TRN covers multiple companies?
- The representative member files one consolidated return for everyone. The FTA aggregates PINT AE data by TRN, so that return total should equal the sum of every external invoice all members issued under the group TRN. Intra-group invoices net out in the return and, until 1 January 2029, never hit the FTA's real-time feed in the first place.
- Must every member of a UAE VAT group use the same accredited service provider?
- No. The Ministry of Finance's UAE Electronic Invoicing Guidelines are explicit that each member of a tax group needs to be onboarded for e-invoicing in its own right, that each member has its own TIN used to generate its individual Peppol participant identifier, and that the members may each onboard with a different ASP. A single master agreement across the group is usually simpler to administer and to reconcile, but it is a commercial preference rather than a requirement. Onboarding itself is initiated through the FTA's EmaraTax system by the account administrator of the taxable person, after the contract with the chosen ASP is finalised.
- What are the penalties if a UAE VAT group member misses its e-invoicing obligations?
- Cabinet Decision No. 106 of 2025 sets them, and they attach to the individual issuer or recipient rather than to the group. Failure to implement the system, including failure to appoint an accredited service provider within the timeline, is AED 5,000 for each month or part month of delay. Failure to issue and transmit an electronic invoice or an electronic credit note through the system on time is AED 100 each, capped at AED 5,000 per calendar month for each. Failure to notify the FTA of a system failure, or to notify your ASP of changes to your registered data, is AED 1,000 for each day of delay. The Decision does not apply to persons who adopt e-invoicing voluntarily.
- What changes when a member leaves or joins a UAE VAT group during the rollout?
- A joining member has to be onboarded to the group's ASP before its next external invoice goes out. A departing member needs its own TRN, its own ASP contract, and possibly a fresh Peppol participant identifier from the FTA. Map either change at least 30 days ahead in the group's master entity register — the onboarding queue tightens badly as deadlines close in.
Filed under: VAT Group UAE, PINT AE, E-Invoicing, Intra-Group, FTA
Published
