Many UAE businesses already “send invoices electronically”: they create a PDF in their accounting software and email it. Under the UAE’s e-invoicing system, that is not an e-invoice. Getting this distinction right is the first step in preparing for the 2027 deadlines.
The short definition
An e-invoice in the UAE is an invoice issued, sent and received as structured electronic data in an approved format, exchanged through Accredited Service Providers (ASPs), with tax data reported to the Federal Tax Authority (FTA).
“Structured” is the key word. A structured invoice is data that a computer can read field by field: the supplier’s Tax Registration Number, the customer’s details, each line item, the VAT rate, the totals. A PDF only looks like an invoice to a human. Software cannot reliably read it without guessing.
What is not an e-invoice
- A PDF invoice, even if it was generated by accounting software
- A scanned or photographed paper invoice
- A Word or Excel file
- An invoice typed into the body of an email
- An image of an invoice sent on WhatsApp
You can still send these to customers as a courtesy copy, but for transactions in scope they do not satisfy the e-invoicing requirement on their own.
The format: PINT-AE on Peppol
The UAE uses PINT-AE, the UAE’s version of the Peppol International invoice specification. Peppol is an international network and set of standards for exchanging business documents, already used in many countries. PINT-AE defines which fields a UAE invoice must contain and how they are coded so that every ASP and the FTA reads them the same way.
You will not need to write XML yourself. Your accounting or ERP system, or your ASP, produces the file. What you need to do is make sure your system holds the information PINT-AE asks for, in a clean and consistent way.
How an invoice travels: the five-corner model
The UAE has adopted what is often called a five-corner model:
- You (the supplier) create the invoice in your system.
- Your ASP checks it against the PINT-AE rules and sends it across the network.
- Your customer’s ASP receives it.
- Your customer receives the invoice in their system.
- The FTA receives the tax data reported by the ASPs.
The practical result is that you never send invoices straight to the FTA, and your customer never has to open an attachment and retype it. The data flows from one system to the other.
Which transactions are in scope
The mandatory system covers invoices between businesses (B2B) and from businesses to government (B2G). Invoices to consumers (B2C) are not in the mandatory scope for now. Credit notes follow the same rules as the invoices they correct; see credit notes under UAE e-invoicing.
What this means for you in practice
Check your software. Ask your accounting software provider whether it supports PINT-AE and which ASPs it connects to. Many cloud systems are building direct integrations.
Clean your customer data. Every B2B customer needs a correct legal name, address and Tax Registration Number where they have one. Duplicates and missing TRNs cause rejections.
Look at your item and tax codes. Each line must carry the right VAT treatment: standard-rated, zero-rated, exempt or out of scope. If your system lumps these together, fix it now.
Find your deadline. Use our e-invoicing deadline checker to see whether you are in the January 2027 or July 2027 group.
Common questions
If I send a PDF and an e-invoice, which one is the legal invoice?
For in-scope transactions, the structured e-invoice exchanged through the network is the one that counts. A PDF can accompany it for convenience.
Can my customer refuse a PDF once e-invoicing is mandatory?
Once both of you are in scope, your customer will expect to receive the invoice through their ASP, and their systems will be set up for that.
Do I need a separate ASP from my customer?
You each appoint your own ASP. The network connects them, in the same way that different email providers can send messages to each other.
