UAE E-Invoicing: The Technical & Compliance Deep-Dive

Six invoice types, eight special transaction scenarios, domestic reverse charge, mandatory field requirements, multi-currency rules, data retention, and the implementation details every finance and IT team needs to get right.

Based on the UAE E-Invoicing Guidelines V1.0 and UAE E-Invoice Mandatory Fields V1.0 · Updated February 2026

The FTA’s guidelines — particularly the detailed mandatory fields specification — contain a number of
provisions that are straightforward to miss in a high-level overview but critical to get right during implementation. This article covers six areas that deserve careful attention: the full set of invoice types,
the eight special transaction scenarios, domestic reverse charge categories, the mandatory field requirements and how they work, operational rules around currency and rounding, and data retention obligations.

1. The Six Invoice Types — Including Self-Billing

The guidelines define six distinct invoice types, each with its own type code. Most businesses will only use two or three in practice, but understanding the full set — particularly the self-billed variants — is important for businesses operating in industries where buyer-initiated billing is standard.

Self-Billing: What Changes Operationally

In a self-billing arrangement, the buyer is responsible for transmitting the invoice through the einvoicing network — not the supplier. The buyer’s ASP handles transmission. This reversal of responsibility has operational implications both parties need to understand before go-live:

• The supplier’s system must be configured to receive invoices from the network rather than generate them outward.
• Both parties need a shared understanding of which transactions fall under the self-billing arrangement and which do not.
• The buyer needs confirmation that the transaction type code on self-billed invoices is correctly flagged — an incorrectly coded self-billed invoice looks like a standard supplier invoice in the FTA’s data.

2. The Eight Special Transaction Scenarios

The guidelines identify eight transaction categories with specific technical handling requirements. These
are not rare edge cases — several apply to a significant proportion of UAE businesses. Incorrect coding in these scenarios is one of the most common implementation failures.

The technical mechanism that distinguishes these transactions is the Transaction Type Code: an 8-digit
binary string (a sequence of zeros and ones) embedded in every e-invoice, where each digit position flags a specific transaction characteristic. Your ASP maps your transaction categories to the correct code during configuration — but they can only do so correctly if you have accurately identified and communicated your transaction types.

2.1 Free Zone and Designated Zone Transactions

Transactions involving UAE Designated Zones — the technical VAT term for most free zones — require additional invoice fields not present on standard mainland-to-mainland invoices. When goods or services cross between a Designated Zone and the UAE mainland, or between two different Designated Zones, the invoice must include beneficiary details: information about the ultimate recipient of the goods where they differ from the contracting buyer.

The transaction type code must include the Designated Zone flag. Free zone businesses need to ensure their ASP configuration applies this flag automatically to the correct transaction categories and captures the beneficiary data fields.

2.2 Deemed Supply

A deemed supply is a transaction UAE VAT law treats as taxable even where there is no commercial sale — for example, business assets used for personal purposes, gifts above the de minimis threshold, or goods transferred without consideration. These must still be reported through the e-invoicing network.

Because there is no real commercial buyer, deemed supply invoices are transmitted to a predefined FTA-managed endpoint: 0235:9900000097. This is a placeholder Peppol address maintained by the FTA to receive these transactions.

2.3 Margin Scheme Supplies

The VAT margin scheme applies to certain second-hand goods, antiques, works of art, and collector’s items, where VAT is calculated on the profit margin rather than the full sale price. On a margin scheme e-invoice, the VAT amount shown is zero — but the invoice must include the specific margin scheme tax category code.

This distinction is critical. A zero-VAT margin scheme invoice is indistinguishable from a zero-rated or exempt supply without the category code. The FTA uses this code to understand that VAT has been accounted for separately under the margin scheme; its absence makes the transaction appear to be a missing tax declaration.

2.4 Summary Invoices

A summary invoice consolidates multiple supplies to the same customer within a single billing period — typically a calendar month. E-invoicing supports this format. The invoice data must clearly reflect the summary period and, where applicable, reference the individual underlying supplies.

2.5 Continuous Supply

Services provided on an ongoing basis — utility services, software licences, maintenance retainers, professional service agreements — are classified as continuous supplies. The transaction type code includes a dedicated flag for this category, providing the FTA with context when reviewing the invoice data stream.

2.6 Agent Billing

When an agent issues invoices on behalf of a principal — a commission agent acting in a supplier’s name, for example — the e-invoice must reflect the actual seller and buyer, and the agent billing flag must be set in the transaction type code. The agent does not appear as the supplier; the principal does.

2.7 E-Commerce Supply

E-commerce platforms and marketplaces facilitating supplies on behalf of third-party sellers have specific obligations under UAE VAT rules. The e-invoicing framework includes a dedicated e-commerce flag in the transaction type code. Platform operators need to work closely with their ASP to ensure marketplace-facilitated transactions are correctly coded and transmitted, particularly where the underlying seller may not themselves be VAT-registered.

2.8 Export Transactions

Exports — goods or services leaving the UAE — present a structural challenge: overseas buyers typically do not have UAE Peppol Participant IDs. The solution is a predefined FTA-managed export endpoint: 0235:9900000099.

When invoicing an overseas customer without a UAE Peppol address, this is the endpoint the e-invoice is transmitted to. The FTA receives the transaction data. This does not replace your commercial invoice to the buyer — that continues through your normal channels. The e-invoice via the Peppol network is the reporting mechanism, not the delivery mechanism.

Zero-rated export supplies still require all invoice fields to be populated, with the correct zero-rate tax
category applied and the export endpoint coded correctly.

3. Domestic Reverse Charge: The Categories That Get Missed

The UAE applies domestic reverse charge VAT to a specific set of goods — meaning the supplier charges zero VAT and the buyer accounts for VAT in their own return. On an e-invoice, these transactions must carry the reverse charge tax category code. Without it, a zero-VAT reverse charge invoice is indistinguishable from a zero-rated supply, which carries entirely different VAT treatment.

The four domestic reverse charge categories:

>Electronic devices — mobile phones, computers, tablets, and similar equipment.
• Precious metals and stones — gold, silver, platinum, diamonds, and similar commodities in raw or processed form.
• Oil and gas — when supplied between businesses within the UAE market.
• Metal scrap and offcuts — trading in recyclable metal materials.

Businesses in these sectors need to ensure their product catalogues and ASP configuration correctly map these goods to the reverse charge category. A finance team that manually selects VAT categories at invoice time is a risk point; the mapping should be automatic based on product classification.

4. Mandatory Fields: What the Specification Actually Requires

Tax Invoices require 51 mandatory fields. Commercial Invoices (from non-VAT-registered businesses) require 49 — the difference being two AED-denominated amount fields that only apply where VAT is being charged. Both invoice types share the same structural groupings.

Invoice-Level Fields

Every invoice requires a unique invoice number (non-repeating within your business), the invoice date, an Invoice Type Code (380 for invoices, 381 for credit notes), the currency code, and the 8-digit binary Transaction Type Code described earlier. Where payment terms apply, the payment due date is mandatory. For invoices in foreign currencies, the exchange rate must be recorded.

Seller and Buyer Information

Both parties require identical field sets: legal name, Peppol Participant Identifier (electronic address), legal registration ID and type (typically trade licence number and type code), tax ID (VAT registration number, if applicable), and address including street name, city, emirate (as the region field), and country code.

For the seller, the tax ID is always required on a Tax Invoice. For the buyer, it is required only if the buyer is VAT-registered. If a buyer does not have a UAE Peppol Participant ID — an unregistered entity or foreign buyer — use the appropriate predefined endpoint rather than leaving the field blank.

Financial Totals

Four totals are mandatory: total amount without tax, total VAT amount, total amount with tax, and amount due (which may differ from the total with tax if prepayments or advances apply). On Tax Invoices, these totals must also be expressed in AED where the invoice is denominated in a foreign currency.

Tax Breakdown

For each tax category appearing on the invoice — standard rate, zero rate, exempt, reverse charge, out of scope, or margin scheme — a separate breakdown row is required showing the category code, taxable amount, VAT rate, and VAT amount. If an invoice spans multiple categories (standard-rated and exempt supplies to the same buyer on one invoice, for example), each category gets its own breakdown row.

Line Items

Each invoice line requires: a line ID number, quantity, unit of measure, net line amount, unit price, applicable tax category and rate, item name, and item description. For Tax Invoices, each line also requires the VAT amount for that line in AED, and the total line amount in AED.

A note on HSN codes: International product classification codes (Harmonised System Nomenclature) are listed as optional in the current specification. The FTA has indicated they may become mandatory in a future phase. Configuring your systems to include them now is advisable.

5. Tax Groups, Intra-Group Transactions, and Non-UAE Businesses

Tax Group Onboarding

UAE VAT Tax Groups do not connect to the e-invoicing network as a single entity. Each member must onboard separately with its own Tax Identification Number and its own Peppol Participant Identifier. The group’s shared Tax Registration Number does not serve as a network address for the group.

For large corporate structures with multiple registered entities, this means the implementation is not one onboarding exercise but potentially dozens. Project teams that plan for a single group-level integration will significantly underestimate the workload.

The Intra-Group Grace Period

A meaningful concession in the regulations: transactions between entities within the same corporate group benefit from a 24-month grace period from 1 January 2027. Intra-group invoicing does not need to comply with e-invoicing requirements until January 2029.

This grace period applies only to intra-group transactions. Sales and purchases with parties outside the group — customers, suppliers, partners — are subject to the standard mandatory dates. The grace period should not be used to slow preparations for external transaction compliance.

Non-UAE Businesses

A non-UAE business is in scope if it is legally required to issue Tax Invoices under UAE VAT law — for example, because it has a fixed establishment or taxable presence in the UAE. Being headquartered overseas does not create an exemption if the entity’s UAE activities generate invoicing obligations under UAE law.

6. Multi-Currency Invoicing, Rounding, and Data Retention

Multi-Currency Invoicing

If you invoice in a currency other than UAE Dirhams, the e-invoice must include AED-equivalent amounts alongside the foreign currency figures. This applies to the invoice totals and, on Tax Invoices, to the VAT amount and the line-level amounts as well. The AED conversion must use the exchange rate applicable on the invoice date.

Businesses invoicing internationally at scale need to ensure their systems can automatically populate both the foreign currency fields and the corresponding AED equivalents at the point of invoice generation — not as a manual step applied afterwards.

Rounding

Rounding to two decimal places is permitted at the invoice total level only. Amounts at individual line level and at the tax category breakdown level must carry full precision and must not be rounded. Only the final invoice totals are rounded.

This rule exists so that invoice totals can be mathematically reconciled from the line items. A common implementation error is to apply rounding in the accounting system at the line level, causing the invoice total to diverge from the sum of the lines when processed by the network validator. Build rounding into your system at the correct stage, and confirm reconciliation in testing.

14-Day Transmission Requirement

All invoices and credit notes must be transmitted through the e-invoicing network within 14 days of the transaction date. This deadline applies to the network transmission — not just the issuance of a document to the buyer. Businesses with high transaction volumes need to ensure their systems generate and transmit invoices promptly rather than batching them at the end of a period.

Data Retention

The retention periods for e-invoice records are:

• VAT-registered businesses: 5 years from the end of the tax period in which the invoice was issued.
• Non-VAT-registered businesses: 5 years from the end of the calendar year in which the invoice was issued.
• Real estate transactions: 7 years, reflecting the higher-value and long-term nature of property.

Records must be retrievable by the FTA on request. Physical storage location is flexible — records do not
need to be held within the UAE — but they must be accessible when requested. Cloud-based storage is
acceptable provided access can be demonstrated.

Implementation: What to Do With This Information

The items covered in this article represent the layer of the e-invoicing mandate that determines whether your implementation works correctly from day one or generates a stream of validation failures. The actions they suggest are straightforward but specific:

1. Audit your transaction types. Map every category of supply your business makes against the eight special scenarios and the tax category types. Identify which transactions need special endpoint routing, which require the reverse charge code, and which carry additional field requirements.
2. Confirm your self-billing arrangements. If any suppliers or buyers operate on a self-billing basis, establish which party will transmit the invoice through the network and configure accordingly.
3. Brief your ASP on every transaction category. The Transaction Type Code must be correctly configured for each type of transaction your business makes. This cannot be done accurately without a complete transaction audit.
4. Build AED conversion into your invoicing workflow. For foreign-currency invoices, the AED equivalent must be generated automatically at invoice creation — not manually applied later.
5. Implement rounding correctly. Confirm that your systems apply rounding at the invoice total level, carry full precision at line and category level, and that totals reconcile from line items.
6. Plan your Tax Group onboarding as a multi-entity project. Do not assume a single group connection. Each legal entity needs its own TIN and Peppol ID configuration.
7. Separate the intra-group grace period from your external compliance deadline. The grace period to January 2029 is useful breathing room for internal billing — it should not delay readiness for external transactions.
8. Set up compliant data retention from go-live. Confirm retention periods, storage accessibility, and retrieval capability before the mandatory date.