Back to research

Tax Planning

UAE Tax-Group Transactions and Electronic Records: A Planning Guide for 2027

The UAE’s revised eInvoicing rules give Tax Group members temporary relief for certain internal transactions while preserving broad record-retention and accessibility duties. Businesses should redesign their intercompany controls before implementation begins.

By Nomadic Tax Institute research team · 5-8 min read · Published

The planning opportunity

The UAE’s updated eInvoicing framework creates a limited planning opportunity for businesses operating through a registered Tax Group. Ministerial Decision No. 197 of 2026 provides a temporary exclusion for business transactions between Persons that are members of the same Tax Group. The exclusion applies for 24 months beginning 1 January 2027, during which qualifying transactions are treated as Excluded Transactions.

This is not a general exemption from accounting, VAT, or transfer-pricing discipline. It is an eInvoicing treatment for a defined category of intercompany transactions. Companies should therefore avoid assuming that every invoice between related UAE entities is automatically excluded.

Build a transaction matrix

A practical matrix should classify each transaction by:

  • Whether both parties are members of the same UAE Tax Group;
  • Whether the transaction is a business transaction within the scope of the decision;
  • Whether the transaction is domestic, cross-border, or connected with a non-group entity;
  • Whether the transaction requires a tax invoice, credit note, or other supporting document under separate rules;
  • Whether the transaction must still be recorded for accounting, VAT, corporate tax, audit, or transfer-pricing purposes.

The matrix should be approved by tax, finance, legal, and technology teams. It should also be embedded in ERP workflows so that an exclusion is not applied merely because two entities share a parent company.

Record storage has become more flexible—but not optional

The amendment removes the previous requirement that electronic invoice and credit-note data be stored within the UAE. The replacement focus is functional: records must be retained for the period prescribed under the Tax Procedures Law and made available to the Federal Tax Authority upon request.

This permits businesses to consider regional or global cloud architecture, but only after confirming access rights, disaster recovery, retention periods, audit trails, and the ability to export records in a usable format. A foreign-hosted system that cannot quickly produce complete records may still create compliance risk.

Example control framework

A group could configure its ERP to apply the temporary exclusion only where both tax-registration numbers are validated against an approved Tax Group list. A monthly exception report could then identify transactions where the exclusion was used despite a missing registration number, changed group membership, or unusual transaction type.

Recommended actions

  1. Obtain the current Tax Group membership list.
  2. Map all intercompany invoice flows.
  3. Document the legal basis for each exclusion.
  4. Test record retrieval from the proposed storage environment.
  5. Preserve supporting documents even where an eInvoice is not required.
  6. Reassess the process before the temporary exclusion expires.

The central lesson is that reduced eInvoicing friction does not eliminate the need for reliable tax data, documented controls, and accessible records.

Sources

1mof.gov.ae
ministry-of-finance-amends-electronic-invoicing-regulations-to-ease-the-burden-… (opens in a new tab)
2mof.gov.ae
Ministerial-Decision-No.-197-of-2026-–-Amending-Certain-Provisions-of-Ministeri… (opens in a new tab)
3mof.gov.ae
einvoicing (opens in a new tab)