UAE e-invoicing API (PINT AE)

Send UAE e-invoices in PINT AE through the Complyance e-invoicing API, and find out which transactions need them. Start with your company's registration details and the type of document you need to send.

The UAE uses PINT AE, its Peppol e-invoice specification. An e-invoice is structured data exchanged electronically; a PDF or scanned invoice alone is not an e-invoice. Your integration maps your invoice data to GETS, the common format used across countries. Complyance checks the data against the selected UAE document type and returns a document identifier for tracking delivery.

Who is in scope?

The UAE Ministry of Finance guidelines say e-invoicing applies to people conducting business in the UAE for business transactions, whether or not they are VAT-registered, unless specifically excluded. The guidelines include transactions between businesses and government entities. Transactions involving consumers who are not conducting business are outside this scope. Consult the Ministry’s current guidance for exclusions and the phased implementation timetable; do not use this page to determine a legal start date.

How a UAE e-invoice travels: the five corners

The UAE exchanges e-invoices between five parties, called corners in the Ministry of Finance’s E-Invoicing Guidelines:

Corner	Who
1	The supplier: your company.
2	The supplier’s accredited service provider (ASP).
3	The buyer’s ASP.
4	The buyer.
5	The Federal Tax Authority (FTA).

Your ASP exchanges the e-invoice with the buyer’s ASP over Peppol, and reports the invoice’s tax data to the FTA. When you send a UAE invoice through Complyance, you act as corner 1; delivery to corners 3 and 5 happens after Unify’s 200. The Invoice Portal and the document’s status use these terms:

You see	What it means
Submitted to C3	The e-invoice has been handed to the buyer’s ASP. Delivery is in progress.
TDD XML	The tax data document: the invoice’s tax data as reported to the FTA.
MLS	A message level status: the answer from the buyer’s ASP or the FTA saying whether it accepted the e-invoice or its tax data.

A UAE document reaches final_valid in the API, and Compliant in the Invoice Portal, when both the buyer’s ASP and the FTA have accepted it. If either rejects it, the document becomes final_invalid (Non-compliant). The Invoice MLS XML and TDD MLS XML downloads in Documents hold those answers.

Prepare a UAE document

Onboard the company with its tax identification number (TIN), branch and invoice source.
Choose a UAE invoice or credit note type. Ordinary, out-of-scope and self-billed documents have different requirements; check the PINT AE Billing specification or Self-Billing specification for the applicable transaction.
Use the UAE field reference for required GETS fields and their PINT AE terms, and UAE code lists for allowed coded values.
Prepare a sandbox request and correct any validation findings before relying on the document. An HTTP 200 response confirms validation and storage, not final delivery. Check the document status with its returned documentId.
When your sandbox results are correct, follow the UAE go-live checklist.

If you have a PDF but no structured invoice data, map the original invoice fields into GETS before submission; uploading a PDF is not a substitute for the UAE e-invoice. Start with UAE onboarding.

Official sources

Source	What it covers
Ministry of Finance e-invoicing page	All UAE e-invoicing publications and the implementation timetable.
UAE E-Invoicing Guidelines V1.1, 1 June 2026	Scope, the five-corner model, business categories and document types.
Electronic Invoice Mandatory Fields V1.0, 23 February 2026	The fields a UAE e-invoice must carry.
Ministerial Decision No. 243 of 2025	The decision on the Electronic Invoicing System.
Federal Tax Authority legislation	UAE tax laws and decisions.
PINT AE Billing and PINT AE Self-Billing	The e-invoice specifications, rules and code lists.