Electronic invoice in United Arab Emirates

How to Prepare Your Business for the UAE Mandate: A step-by-step breakdown of ASP selection, PINT-AE conversion, and penalty avoidance during the phased 2027 implementation.

Select a country

Overview

The UAE has adopted its mandatory e-invoicing framework, and the pilot and voluntary phase opened on 1 July 2026. Mandatory adoption runs through 2027 in three steps. The architecture is a decentralised Peppol CTC model with a tax fifth corner — DCTCE, Decentralized Continuous Transaction Control and Exchange.

The invoice travels between the accredited providers of seller and buyer, while tax data goes to the Federal Tax Authority (FTA) in parallel. No prior approval from the tax authority is required, so this is not a classic clearance model. The mandatory format is PINT-AE on UBL 2.1 XML; PDFs, scans, images, Word files and emails are not electronic invoices. B2C is excluded for now — and a general OpenPeppol certification is not enough to serve local clients.

0235:TIN

the UAE Tax Identification Number scheme — a 10-digit TIN as the endpoint

PINT-AE

UBL 2.1 Invoice and CreditNote — CII is not a permitted syntax

One ASP

a business appoints a single provider for both sending and receiving

Timeline

Two dates matter for every business: when it must have appointed a provider, and when it must be live. They are months apart, and the first one has already moved once.

Already in force

1 July 2026

Pilot and voluntary use open

Anyone wanting to move early can already exchange PINT-AE invoices and report to the FTA. Voluntary adopters get one concrete benefit — see Penalties.

Still ahead

30 October 2026

Large businesses must have appointed an ASP

For businesses with revenue at or above AED 50 million. This date was originally 31 July 2026 and was extended by Ministerial Decision No. 66 of 2026, announced in May 2026 after an assessment of market readiness and feedback on pricing and provider availability.

1 January 2027

Large businesses go live

The go-live date for the AED 50 million group was not moved by the extension — only the appointment deadline was. The compliance window has therefore narrowed, not lengthened.

31 March 2027 → 1 July 2027

Everyone else

Businesses with revenue below AED 50 million appoint a provider by 31 March 2027 and go live on 1 July 2027.

31 March 2027 → 1 October 2027

Government entities

Public bodies appoint by 31 March 2027 and go live on 1 October 2027 — the latest of the three groups, which creates the B2G asymmetry.

Material still showing 31 July 2026 is out of date on that point. Ministerial Decision No. 66 of 2026 moved the appointment deadline for large businesses to 30 October 2026 while leaving 1 January 2027 untouched. B2C remains excluded with no published date — introducing it would require a new ministerial decision.

Who is in scope

The scope is broader than VAT, which is the first thing that surprises companies arriving from Europe. The mandate covers persons conducting business in the UAE regardless of VAT registration, unless a specific rule excludes the transaction. Timing is set by revenue, not by tax status.

Domestic B2B — included regardless of

—Whether the supplier is VAT registered

—Whether the buyer is VAT registered

—Whether a Tax Invoice or only a Commercial Invoice is required

—Whether the buyer is ready to receive a Peppol invoice

What sits outside

B2CSupplies to individuals not carrying on business are excluded until a separate ministerial decision. Selling online does not convert B2C into B2B — the "supply through e-commerce" field in PINT-AE classifies the channel, not the counterparty

Sovereign activityGovernment transactions carried out in a sovereign capacity and not competing with the private sector. Ordinary commercial procurement by public bodies, including through procurement portals, is in scope

Import reverse chargeImports of Concerned Goods and Concerned Services where the recipient accounts for VAT under the import reverse charge — see Export and import

VAT groups get a grace period

Transactions between members of the same UAE VAT group stay in scope but benefit from a 24-month transitional grace period, from 1 January 2027 to 31 December 2028. After that the rules apply in full to intra-group business transactions.

One more trap for foreign groups: a company with no place of residence in the UAE that is nonetheless required by UAE VAT legislation to issue a UAE Tax Invoice must issue that invoice as an eInvoice. Having no UAE establishment is not, by itself, an exemption.

The five-corner model

Five participants: the supplier, its Accredited Service Provider (ASP), the buyer's ASP, the buyer, and the FTA as recipient of the tax data.

01 The supplier passes the data to its ASP

02 The ASP validates it and, where needed, converts it into PINT-AE XML

03 The invoice goes over Peppol to the buyer's provider — and simultaneously the supplier's ASP sends a Tax Data Document to the FTA

04 The buyer's ASP revalidates, delivers to the buyer and produces its own Tax Data Document

05 Supplier, buyer and both providers receive technical processing confirmations

Not clearance

The FTA issues no prior authorisation for each invoice, the supplier does not wait for approval before delivering to the buyer, and delivery and tax reporting run in parallel rather than in sequence. The business document moves between private accredited Access Points. The UAE is therefore much closer to Peppol DCTCE five-corner reporting than to the Italian SdI or Latin American pre-authorisation.

On "real time" — say near, not instant

The Ministry of Finance states that the state should receive data in near real time, and the supplier's ASP sends the Tax Data Document at the same moment as the invoice. But the published core legislation sets no universal SLA in seconds or minutes — Ministerial Decision No. 243 provides that the specific tax transmission deadline is set by the minister. Describe the UAE as transaction-level near-real-time reporting, and do not claim that current public rules already require transmission within seconds.

What is fixed is the issuing deadline: within the period required by VAT legislation where the supplier is a VAT Registrant, and otherwise no later than 14 days from the date of the Business Transaction.

B2G and unconnected buyers

Supplies of goods and services to government entities are expressly in scope — as are G2B and G2G. But two dates must be kept apart: the date the private supplier must connect, and the date the government entity must connect.

A private supplier with revenue above AED 50 million must issue eInvoices to a government customer from 1 January 2027 — even though that customer is not obliged to be live until 1 October 2027. The buyer's connection status does not relieve the supplier of its own obligation.

What to do when the buyer is not connected

The transitional mechanism applies to any unconnected buyer, government or otherwise. The supplier must:

01 Generate the structured XML and submit it into the system as normal

02 Use the technical endpoint 0235:9900000098 for the unconnected domestic buyer

03 Additionally give the buyer an ordinary tax invoice — a PDF, for instance — until it can receive a legally valid XML

That third step is not a courtesy. It is what lets the buyer support its input VAT recovery during the transition.

PINT-AE and formats

The national specification is PINT-AE, the UAE country customisation of the Peppol International Invoice model. It defines the semantic model, mandatory fields, VAT rules, UAE-specific transaction flags, seller and buyer identification rules, the Schematron validation rules, the requirements for Invoice and Credit Note, and the rules for tax reporting through the Tax Data Document.

Business documentsOASIS UBL Invoice 2.1 and OASIS UBL CreditNote 2.1

Tax transmissionA separate Peppol Tax Data Document with its own namespace urn:peppol:schema:taxdata:1.0, reusing OASIS UBL 2.1 components

UN/CEFACT CIINot a permitted UAE syntax. The official PINT-AE specifications require UBL Invoice and UBL CreditNote

EN 16931 is not a legally binding national standard in the UAE. The compliance criterion is PINT-AE — not Peppol BIS Billing 3.0 EU and not a national CIUS of EN 16931. PINT-AE uses the international Peppol semantic structure and many concepts resemble the European model, so technical mapping is feasible. But no EN 16931, XRechnung or Factur-X document automatically satisfies UAE requirements: conversion and validation against PINT-AE, including the local fields and rules, is required.

Where the PDF sits

A PDF is not an electronic invoice for UAE purposes — and neither is a Word file, an image, a scanned copy or an ordinary email. The legally and technically significant document is the structured XML.

A PDF may be used as a visualisation of the XML, as an attachment to the structured document, or as an ordinary tax invoice during the transition while the buyer is unconnected. It does not replace the mandatory PINT-AE XML or the tax transmission through the ASP. Worth noting for anyone comparing with Saudi Arabia: a QR code or barcode is not required on a UAE eInvoice.

Identifiers

The UAE has a dedicated Peppol Electronic Address Scheme: 0235 — UAE Tax Identification Number. The endpoint is formed as 0235:<10-digit TIN>.

Two reserved endpoints worth memorising

0235:9900000098The unconnected domestic buyer

0235:9900000099The foreign buyer with no Peppol ID

These are what make the UAE model workable in a market that is not yet fully connected: an obligation to issue a structured invoice does not depend on the counterparty being reachable.

Peppol and the Ministry of Finance

Peppol is the central infrastructure of UAE eInvoicing. Invoices move between Accredited Service Providers over the Peppol network, and the Tax Data Documents use the same infrastructure.

The Peppol Authority

The UAE Ministry of Finance is the national Peppol Authority. It sets the Peppol Authority Specific Requirements, runs pre-approval and accreditation of ASPs, maintains the Central Register, publishes the list of approved providers and coordinates the national PINT-AE specification.

The FTA is the tax authority — it issues TINs and receives the tax data. It does not replace the Ministry of Finance in the Peppol Authority role, and confusing the two leads to approaching the wrong body for accreditation.

Export and import

Exporting from the UAE

Exports of goods and services are in scope, with no separate date — the obligation starts with the supplier's own phase. The UAE supplier issues a PINT-AE eInvoice, reports the data to the FTA, sends the document over Peppol where the foreign recipient is Peppol-capable, and otherwise uses 0235:9900000099. The eInvoice can also be used in the customs process. This applies equally to exports within the GCC, to the EU and elsewhere. A UAE company providing IT services to a client in France, for example, must produce a PINT-AE eInvoice and report to the FTA.

Importing into the UAE

Imports of Concerned Goods and Concerned Services where VAT is accounted for by the recipient under the import reverse charge are excluded. A foreign supplier does not have to produce a UAE PINT-AE invoice merely because its UAE customer self-accounts for import VAT.

Distinguish that from domestic reverse charge on certain goods. On a domestic supply falling under domestic reverse charge, the UAE supplier must issue an eInvoice — without VAT, and stating the basis on which reverse charge applies. Import reverse charge is out; domestic reverse charge is in.

ViDA

ViDA does not apply directly, since the UAE is not an EU member state — a UAE–EU transaction is an export or import, not an intra-EU supply, and there is no separate UAE ViDA deadline. Where a group has a company, fixed establishment or VAT registration in the EU, that European entity may fall under national EU mandates and future ViDA rules in its own right. That neither replaces nor removes the PINT-AE requirements for the UAE side of the business.

ASP accreditation

This is the strictest provider regime among the Peppol-based markets. A general OpenPeppol certification is the starting condition, not the entitlement — serving the UAE mandate requires separate accreditation by the Ministry of Finance.

What accreditation requires

—A UAE business licence — either a UAE-registered legal entity, or a foreign entity recognised in its home country and licensed to do business in the UAE

—Corporate Tax registration and, where applicable, VAT registration

—Paid-up capital of at least AED 50,000

—Two years' demonstrated experience — after the 2026 amendment this may relate to the PSP product and the company actually operating it, rather than necessarily to the applicant

—ISO/IEC 27001 and ISO 22301

—Three types of insurance, issued by insurers operating in the UAE — professional indemnity, crime cover at AED 5 million and cyber fraud cover at AED 5 million

—PINT-AE interoperability, onboarding, EmaraTax API, PKI and TDD reporting testing, plus a production trial

—100 free eInvoice exchange and reporting operations per year per end client

—Accreditation runs for two years

Third-party products and outsourced development or operation are permitted — but the accredited provider retains full responsibility to the Ministry of Finance. And the insurance requirement is the quiet obstacle for a European provider: the policies must come from insurers operating in the UAE, which is not something an existing group programme usually satisfies.

Local presence and data location

Fully remote operation by a foreign company without a UAE business licence is not provided for. In practice a local company, branch or another permitted licensed form is needed. No requirement for a dedicated official electronic mailbox of the European kind was found, and no separate requirement to appoint an independent local tax representative specifically for the ASP role beyond being licensed to do business in the UAE.

Data residency — narrower than it first reads

The Ministerial Decision speaks formally of keeping data within the State. But the official Guidelines v1.1 clarify that servers, databases and cloud infrastructure may sit inside or outside the UAE, provided the integrity and security of the records is ensured, documents can be produced rapidly to the FTA, the data is fully reproducible and readable, and any special requirements for critical or regulated information are met. There is therefore no general absolute obligation to host all ASP infrastructure physically in the UAE.

One client-side rule that shapes any commercial proposal: a business must appoint one ASP for both sending and receiving. Splitting accounts payable and accounts receivable between two different providers is not generally permitted.

Archiving

Retention in the UAE follows the general tax record-keeping rules rather than a separate e-invoicing figure, and the period differs by record type — real estate records in particular run considerably longer than ordinary business records. Confirm the exact term for the specific documents and years with a UAE adviser rather than applying a single number.

What is retained is the PINT-AE XML — the PDF visualisation is not the record

The Tax Data Documents and the technical processing confirmations belong with the invoice — they are what evidences that reporting actually happened

Records must remain fully reproducible and readable and be producible to the FTA rapidly — the same standard the Guidelines apply to ASP infrastructure

Because the invoice never passes through a central government platform, no state repository holds a copy on your behalf. In a five-corner model the FTA receives tax data, not the business document — an important distinction when planning what the archive must be able to produce.

Penalties

Cabinet Decision No. 106 of 2025 sets the administrative penalties. They are modest by regional standards but accumulate monthly and daily rather than per incident.

Late implementation or no ASP appointedAED 5,000 for each month or part of a month of delay

eInvoice not sent on timeAED 100 per invoice, capped at AED 5,000 a month

Electronic Credit Note not sentAED 100 per credit note, capped at AED 5,000 a month

Late notification of a system failureAED 1,000 per day or part of a day — separately for the supplier and for the recipient

Late notification to the ASP of changed registration dataAED 1,000 per day or part of a day

A genuine incentive worth putting in front of a client: these penalties do not apply to persons who connect voluntarily before their own mandatory date. With the pilot open since 1 July 2026, early adoption buys a penalty-free run-in period as well as a calmer project.

Input VAT

The answer changes depending on where in the rollout you are, which is why a single sentence about it is usually wrong.

Once both parties are connected

If the PINT-AE eInvoice contains all the mandatory Tax Invoice particulars, it is the tax invoice. No additional PDF or paper Tax Invoice is required.

During the transition

Where the buyer is not yet connected, the supplier must also issue an ordinary Tax Invoice, such as a PDF. The Guidelines tie this directly to the buyer's ability to support input VAT recovery and deductions.

So it is not accurate to say the XML eInvoice is the sole basis for VAT deduction from the beginning of the rollout. The precise formulation: once the transaction and the parties fall under mandatory eInvoicing, a proper PINT-AE eInvoice becomes the required form of the Tax Invoice — but while the buyer remains unconnected, an ordinary Tax Invoice is additionally needed to support the deduction.

How we help

The UAE is a Peppol market, so more of a European platform transfers here than to any clearance country — but the accreditation is a national project in its own right:

Conversion from EN 16931, Peppol BIS or ERP data into PINT-AE UBL 2.1, validated against the Schematron rules

The Tax Data Document alongside the invoice, on both the sending and receiving side

Addressing on 0235:TIN, with the reserved endpoints for unconnected domestic and foreign buyers

The transitional dual output — structured XML plus an ordinary Tax Invoice for buyers not yet live

Correct handling of domestic reverse charge, and correct exclusion of import reverse charge

Export invoices for GCC, EU and other destinations, alongside the European profile the buyer needs

Connection by API, SFTP and CSV, with ERP and IDoc source data

Frequently asked questions

When exactly do I have to comply?

Two dates apply to you. Businesses at or above AED 50 million revenue must appoint an ASP by 30 October 2026 and go live on 1 January 2027; below that threshold, appoint by 31 March 2027 and go live on 1 July 2027; government entities appoint by 31 March 2027 and go live on 1 October 2027. Note that Ministerial Decision No. 66 of 2026 moved the large-business appointment deadline from 31 July to 30 October 2026 without moving the 1 January 2027 go-live — so the window is shorter, not longer.

Does the FTA approve my invoice before I send it?

No. The UAE uses a decentralised Peppol five-corner model: the FTA issues no prior authorisation, you do not wait for approval before delivering to the buyer, and delivery and tax reporting run in parallel. Your ASP sends the Tax Data Document at the same moment as the invoice, and the buyer's ASP produces its own after revalidating. The Ministry of Finance describes this as near real time, but no universal SLA in seconds or minutes appears in the published core legislation — the specific deadline is left to the minister.

I am not VAT registered. Am I still in scope?

Very likely yes. The mandate covers persons conducting business in the UAE regardless of VAT registration, unless a specific rule excludes the transaction, and domestic B2B is included regardless of either party's VAT status, whether a Tax Invoice or only a Commercial Invoice is required, or whether the buyer can receive a Peppol invoice. A company with no place of residence in the UAE that is nonetheless required to issue a UAE Tax Invoice must issue it as an eInvoice — having no UAE establishment is not an exemption.

What if my customer is not connected yet?

You still issue. Generate the structured XML and submit it as normal, use the technical endpoint 0235:9900000098 for an unconnected domestic buyer or 0235:9900000099 for a foreign buyer with no Peppol ID, and additionally give the buyer an ordinary tax invoice — a PDF, for instance — until it can receive a legally valid XML. That last step is what allows the buyer to support its input VAT recovery during the transition. The buyer's status never relieves you of your own obligation.

Will my EN 16931 or XRechnung invoice work?

Not automatically. EN 16931 is not a legally binding national standard in the UAE — the compliance criterion is PINT-AE, not Peppol BIS Billing 3.0 EU and not a national CIUS of EN 16931. PINT-AE uses the international Peppol semantic structure, so technical mapping is feasible, but conversion and validation against PINT-AE including the local fields and rules is required. The permitted syntaxes are OASIS UBL Invoice 2.1 and UBL CreditNote 2.1; UN/CEFACT CII is not a UAE syntax.

Can I serve UAE clients from my European Access Point?

Not on OpenPeppol certification alone — that is the starting condition, not the entitlement. You need Ministry of Finance accreditation, which requires a UAE business licence (a local entity, or a foreign entity licensed to do business in the UAE), Corporate Tax and where applicable VAT registration, AED 50,000 paid-up capital, two years' experience of the product, ISO/IEC 27001 and ISO 22301, three insurances from insurers operating in the UAE, full testing including EmaraTax and PKI, and a production trial. Accreditation runs two years. Fully remote operation without a UAE licence is not provided for.

Must all data be hosted in the UAE?

No — and this reads more restrictively in the decision than it turns out to be. The Ministerial Decision speaks of keeping data "within the State", but Guidelines v1.1 clarify that servers, databases and cloud infrastructure may sit inside or outside the UAE provided record integrity and security are ensured, documents can be produced rapidly to the FTA, the data is fully reproducible and readable, and any special requirements for critical or regulated information are met. There is no general absolute obligation to host all ASP infrastructure physically in the UAE.

What does it cost to get it wrong?

Under Cabinet Decision No. 106 of 2025: AED 5,000 for each month or part month of late implementation or failure to appoint an ASP; AED 100 per invoice or credit note not sent on time, capped at AED 5,000 a month; and AED 1,000 per day or part day for late notification of a system failure — separately for supplier and recipient — or of changed registration data to your ASP. Crucially, these penalties do not apply to those who connect voluntarily before their mandatory date, which makes the pilot a genuinely worthwhile route.

Summary

The UAE is building the most European-looking system outside Europe: decentralised Peppol exchange between accredited providers, with the FTA as a fifth corner receiving tax data in parallel rather than approving anything in advance. PINT-AE on UBL 2.1 is the mandatory format, the address is 0235:TIN, and PDFs, scans and emails are not invoices.

The pilot has been open since 1 July 2026. Large businesses must appoint a provider by 30 October 2026 — extended from July — and go live on 1 January 2027, with smaller businesses following on 1 July 2027 and government entities on 1 October 2027. Scope reaches beyond VAT registrants, and B2C is excluded until a new ministerial decision.

For a European provider this is the market where the platform transfers but the licence does not. Accreditation demands a UAE business licence, capital, ISO 27001 and ISO 22301, and three insurances from insurers operating in the UAE — a national project rather than a country switch. The compensations are real: data may be hosted abroad, PINT-AE maps from EN 16931 with work rather than reinvention, and clients who join the pilot early are exempt from the penalties.

Resources

Ministry of Finance — eInvoicing The Peppol Authority's programme hub: the legislation, the guidelines and the PINT-AE specification Pre-approved eInvoicing Service Providers The official ASP list, updated periodically — the place to check before the 30 October appointment deadline Accreditation of eInvoicing Service Providers The application route and the business and technical documentation an ASP must submit Ministerial Decision No. 64 of 2025 (PDF) The eligibility criteria and accreditation procedure for Service Providers, in the original text FAQs — accreditation of eInvoicing Service Providers The Ministry's answers on outsourcing, third-party products, insurance and the testing stages Federal Tax Authority The TIN, EmaraTax and the VAT rules behind the Tax Invoice particulars and input VAT recovery

Need support with e-invoicing compliance?

As a certified Peppol Access Point we provide solutions for sending and receiving electronic invoices securely across Europe — including format conversion, validation and integration with national systems.

Start your free trial