UAE e-invoicing: what the mandate requires and how to get ready

• Structured data, not a PDF

  An eInvoice is invoice data in a structured format that systems can process automatically. The Ministry says PDFs, Word files, scans, images and emails are not eInvoices, even when they look like one.

• Every business transaction

  Any person doing business in the UAE is in scope for every business transaction unless excluded. The guidelines say this applies whatever your VAT registration status and whether or not you are established in the UAE.

• One ASP, both directions

  You appoint one Accredited Service Provider for sending (accounts receivable) and receiving (accounts payable). The obligation stays with you; the ASP is how you meet it.

• Invoices and credit notes

  Electronic credit notes are required when a transaction is canceled, the price is reduced, consideration is returned, or an administrative or numerical error is corrected.

• Issued within 14 days

  An eInvoice or credit note must go through the system within 14 days of the transaction date. For VAT registrants, the VAT Law timeline for tax invoices applies.

• Reported to the FTA

  Both your ASP and your buyer's ASP report tax data to the Federal Tax Authority. You notify the FTA within 2 business days if a system failure stops you meeting your obligations.

Sources: [1] [2] [5]

The Phase 1 appointment deadline was 31 July 2026 in the original decision. Ministerial Decision No. 66 of 2026 moved it to 30 October 2026; the go-live date did not change. Transactions between members of the same VAT group get a 24-month grace period from 1 January 2027. If you adopt voluntarily, e-invoicing penalties apply only from your mandatory date.

Sources: [3] [4] [5] [9]

Sources: [2] [3] [5]

1. 1Your team

   Corner 1: supplier

   Your ERP or billing system sends the invoice data to your ASP in a format you agree with them.

2. 2ASP

   Corner 2: supplier's ASP

   Validates the data, converts it to PINT AE XML if needed, sends it to the buyer's ASP, and reports tax data to the FTA.

3. 3ASP

   Corner 3: buyer's ASP

   Validates the invoice and sends a confirmation back to Corner 2. If it fails, both Corner 2 and the FTA are told.

4. 4Your team

   Corner 4: buyer

   Receives the invoice from its ASP in an agreed format and processes it in accounts payable.

5. 5FTA

   Corner 5: Federal Tax Authority

   Receives tax data from both ASPs and confirms receipt. Confirmations flow back to the supplier and the buyer.

PINT AE is the UAE profile of Peppol International (PINT): PINT AE Billing, PINT AE Self-Billing and a UAE Tax Data Document are published on the Peppol documentation site. Your Peppol participant ID is 0235 followed by your 10-digit TIN, which is the first 10 digits of your TRN. UAE eInvoices carry a UUID and no QR code, and the framework supports Arabic and English.

Sources: [1] [5] [6] [10]

Sources: [6] [10]

Sources: [2] [5]

• Automated

  Master data cleanup

  Check every customer and supplier record for a valid 15-digit TRN, derive the TIN, find missing trade license numbers and emirates, and flag duplicates before onboarding.

  A person decides: approving each change to a vendor or customer record.

• Automated

  ERP field mapping

  Map your ERP tax codes, units and document types to PINT AE tax categories, codes and transaction flags, then test the mapping on last quarter's invoices.

  A person decides: your finance or tax lead signs off the mapping table.

• Automated

  Checks before submission

  Run each outgoing invoice against the mandatory-field list and your own rules before it reaches the ASP, so problems are fixed in the ERP and not after a rejection.

  A person decides: releasing invoices that fail a check you have marked as judgment.

• Automated

  Exception handling

  When a status message reports a failure, an agent reads the error, classifies it, drafts the fix or the credit note, and routes it to the right owner with the context attached.

  A person decides: whether to correct, credit or re-issue.

• Automated

  Inbound invoice processing

  Structured eInvoices are matched to purchase orders and receipts. PDF invoices from suppliers who are not live yet go through document intelligence into the same queue.

  A person decides: approving mismatches above your tolerance.

• Automated

  Readiness testing

  Replay a sample of past invoices through the mapping and checks to find which customers, items and scenarios would fail, months before your go-live date.

  A person decides: prioritizing which gaps to fix first.

For example, a distributor issuing 3,000 invoices a month with a 4% failure rate has about 120 invoices a month to fix by hand. That queue is what we design for. We usually leave unusual tax treatments such as deemed supplies and the margin scheme to your tax adviser once, then turn their answer into a rule.

1. 1Scenox

   Gap analysis

   List every invoice type and scenario you issue and receive, and check your ERP can produce each mandatory field.

2. 2Your team

   Choose and contract an ASP

   Pick from the Ministry's published list, sign the contract, then onboard through EmaraTax and get your participant ID.

3. 3Scenox

   Clean the master data

   Fix TRNs, legal registration IDs and addresses for customers and suppliers, with each change approved.

4. 4Scenox

   Map and pre-validate

   Build the ERP-to-PINT AE mapping and the checks that run before invoices leave.

5. 5ASP

   Test with your ASP

   Exchange test invoices, receive confirmations, and agree who fixes which errors.

6. 6Scenox

   Go live and run the queue

   Monitor confirmations, work the exception queue and report weekly on failures by cause.

Sources: [5] [8]