LEGISLATION
Multi-Entity and Intercompany Invoicing Under UAE E-Invoicing Rules
For a corporate group, e-invoicing is not just a change of file format. It is a project about legal identities, participant IDs and transaction routing. The UAE Electronic Invoicing System exchanges structured invoice data instead of PDFs, Word files, scans or emailed images, so every entity in the group must stay individually identifiable — even when the technology behind it is centralized.
reading time: 8 min
SOURCES: MOF, FTA OFFICIAL PUBLICATIONS
august 2026
aiverix research
Many UAE businesses invoice in currencies other than the dirham — a trading company billing an overseas supplier in US dollars, a services business invoicing a European client in euros, or a group company settling accounts in a foreign currency. E-invoicing does not stop you from doing this. But it adds one specific rule that your invoicing tool needs to handle correctly.
How does a company with multiple UAE legal entities handle e-invoicing?
Each in-scope legal person must be onboarded separately, even if the whole group runs on one shared platform. The Participant Identifier is derived from the Tax Identification Number (TIN): for a taxpayer holding a Tax Registration Number (TRN), the TIN is the first 10 digits of that TRN. A member of a VAT Tax Group uses its own TIN, not the TIN of the Tax Group representative.
Multi-entity e-invoicing means issuing, receiving and controlling structured electronic invoices for several legal persons under common ownership, while compliance is preserved at entity level. In practice:
Multi-entity e-invoicing means issuing, receiving and controlling structured electronic invoices for several legal persons under common ownership, while compliance is preserved at entity level. In practice:
-
Point 1
each Tax Group member is onboarded individually and receives its own Peppol Participant Identifier; -
Point 2
each in-scope person appoints one Accredited Service Provider (ASP) for both sending and receiving its invoices; -
Point 3
members of the same Tax Group may appoint different ASPs.
Several enterprise resource planning (ERP) or accounting systems can still run through a single operating layer. What must stay correct at entity level is the seller and buyer identity, the invoice data, the VAT logic, the reporting and the retrievable records.
Centralization simplifies governance, but it does not merge separate regulatory identities. The MoF guidelines are explicit on this point: businesses must assess whether their accounting, ERP and invoicing systems can actually generate and extract the required e-invoice data.
How does intercompany invoicing work under UAE e-invoicing rules?
An in-scope Business Transaction between separate group companies normally follows the standard structured B2B exchange framework. Transactions inside the same VAT group currently have specific timing relief.
Intercompany invoicing is billing between separate legal persons within one corporate group. It covers management-fee recharges, shared-service charges and internal sales or cost allocations. The MoF guidelines expressly name operational and management-cost recharges to related parties as examples that can qualify as Business Transactions.
Intercompany invoicing is billing between separate legal persons within one corporate group. It covers management-fee recharges, shared-service charges and internal sales or cost allocations. The MoF guidelines expressly name operational and management-cost recharges to related parties as examples that can qualify as Business Transactions.
The MoF Electronic Invoicing Guidelines state that Business Transactions between members of the same VAT group remain in scope — they are not excluded simply because they are intra-group. A 24-month grace period does apply, starting 1 January 2027: during that window, the electronic invoicing obligations under Ministerial Decision No. 243 of 2025 do not have to be implemented for those transactions. The relief changes the timing of compliance, not the scope of the system.
For all other related-party transactions, finance teams must preserve the correct seller and buyer identifiers, the applicable VAT treatment and the commercial data. E-invoicing changes how invoice data is structured, exchanged and reported. It does not replace the underlying VAT analysis, the accounting, the payment process or the reconciliation between group companies. Official guidance also makes clear that electronic invoicing requirements and VAT invoice requirements are distinct, even though they interact.
What does the UAE 5-corner Peppol model mean for groups?
The 5-corner model routes each electronic invoice through the supplier and buyer sides of the Peppol-based network, while tax data is reported to the Federal Tax Authority (FTA) as Corner 5. Peppol is an interoperability framework for standardized electronic document exchange through service providers. The five corners are the supplier, the supplier’s ASP, the buyer’s ASP, the buyer and the FTA.
The flow works like this:
The flow works like this:
-
Step 1
The supplier sends invoice data to its ASP. -
Step 2
The ASP validates the data and, where needed, converts it to the UAE-standard XML format. -
Step 3
The ASP transmits the electronic invoice to the buyer’s ASP and reports tax data to the FTA in parallel. -
Step 4
The buyer’s ASP validates the document and delivers it to the buyer. -
Step 5
The framework adds electronic confirmations and receiving-side tax-data reporting.
For groups, identity mapping is the critical part. A central ERP may create thousands of invoices, but every transaction must leave under the correct supplier and arrive at the correct buyer. The official Peppol Participant Identifier uses the prefix 0235 followed by the entity’s 10-digit TIN, so ERP company codes, TINs, TRNs and Peppol IDs have to map to each other without error.
What are the common compliance pitfalls for multi-entity groups?
The main risks are mixed entity identities, incorrect tax or network identifiers, inconsistent VAT logic and unreconciled internal transactions. These problems multiply when several ERP systems or automated recharge engines feed one platform, because the official framework still identifies and onboards every person separately.
The most common pitfalls are:
The most common pitfalls are:
- sending a document under another group member’s TIN, TRN or Peppol Participant Identifier;
- using the VAT Tax Group representative’s identity when a member has its own TIN-based e-invoicing identity;
- keeping inconsistent supplier, customer, tax-code or legal-name data across group systems;
- combining flows without entity-level status monitoring and retrievable records;
- treating every related-party charge as exempt, or overlooking the 24-month same-VAT-group grace period.
These are the practical control implications of the MoF requirements on separate participant identities, entity onboarding and source-system readiness. MoF guidance states that in-scope persons must ensure their accounting software, ERP or invoicing systems can generate the required data. Group testing should therefore cover recharges, credit notes, rejected documents, corrections and reconciliation — not only straightforward external sales.
How does Aiverix support multi-entity UAE groups?
We built Aiverix for exactly this situation: several legal entities and several ERP systems running through one platform, with entity-level handling left intact.
Our e-invoicing platform handles multi-entity setups, multiple ERP systems and multi-format invoice flows from a single operating layer. Each entity keeps its own TRN management and entity-level reporting, while the group gets a consolidated audit view. Aiverix is an FTA-accredited ASP and a certified Peppol Access Point.
Technically, we support REST API, SFTP and file exchange, with connectors for major ERP and accounting systems including SAP, Oracle, Microsoft Dynamics, QuickBooks, Xero, Zoho, Sage, Odoo and Tally. The platform validates invoices against FTA rules, transmits them through Peppol, and gives you a compliance dashboard, document management and secure archiving for the full statutory retention period (5 years for VAT, 7 years where UAE Corporate Tax applies).
For a group, this centralizes monitoring without erasing entity boundaries: ERP company codes map to the correct tax and Peppol identity, while your finance team tracks acknowledgements and exceptions from one place. Regulatory onboarding still applies to each in-scope person — the platform architecture and the FTA/MoF entity structure have to work together rather than replace one another.
Our e-invoicing platform handles multi-entity setups, multiple ERP systems and multi-format invoice flows from a single operating layer. Each entity keeps its own TRN management and entity-level reporting, while the group gets a consolidated audit view. Aiverix is an FTA-accredited ASP and a certified Peppol Access Point.
Technically, we support REST API, SFTP and file exchange, with connectors for major ERP and accounting systems including SAP, Oracle, Microsoft Dynamics, QuickBooks, Xero, Zoho, Sage, Odoo and Tally. The platform validates invoices against FTA rules, transmits them through Peppol, and gives you a compliance dashboard, document management and secure archiving for the full statutory retention period (5 years for VAT, 7 years where UAE Corporate Tax applies).
For a group, this centralizes monitoring without erasing entity boundaries: ERP company codes map to the correct tax and Peppol identity, while your finance team tracks acknowledgements and exceptions from one place. Regulatory onboarding still applies to each in-scope person — the platform architecture and the FTA/MoF entity structure have to work together rather than replace one another.
Frequently Asked Questions
Each in-scope legal person should be onboarded separately and use its own TIN-based Peppol Participant Identifier. A group can still connect multiple ERPs to one platform and monitor invoice status centrally. The key is to preserve the correct seller, buyer, tax data and records for every entity, rather than treating the whole group as a single e-invoicing participant.
An in-scope Business Transaction between separate group companies follows the structured electronic exchange framework unless a specific timing rule or exclusion applies. Transactions between members of the same VAT group stay in scope but receive a 24-month grace period from 1 January 2027. Once that relief expires, the applicable electronic invoicing requirements apply in full.