UAE E-Invoicing: What Changes for Your Software

UAE e-invoicing replaces PDF and paper invoices between businesses, and between businesses and government, with structured XML invoices. Each one is sent through an Accredited Service Provider (ASP) over the Peppol network and reported to the Federal Tax Authority (FTA). Businesses with revenue of AED 50 million or more must appoint an ASP by 30 October 2026 and go live on 1 January 2027; everyone else in scope follows in 2027. For your software, that means new data fields, a live connection to an ASP, and credit-note discipline your current system may not enforce.

What is UAE e-invoicing?

The Ministry of Finance (MoF) defines an eInvoice as structured invoice data that is issued and exchanged electronically between supplier and buyer and reported electronically to the FTA. Its eInvoicing page is explicit that a PDF, Word file, image, scan or email is not an eInvoice. The MoF calls that page the only official source on the programme.

The format is PINT AE, the UAE version of the Peppol International invoice specification, backed by a national data dictionary. Under the UAE Electronic Invoicing Guidelines v1.1, e-invoices are XML, and unlike Saudi invoices they carry no QR code or barcode.

How does the 5-corner Peppol model work?

The UAE calls its model Decentralised Continuous Transaction Control and Exchange (DCTCE), usually shortened to the "5-corner model". You never send invoices straight to the FTA. Your ASP does the exchange and the reporting. Based on the MoF guidelines, the flow is:

1. Corner 1 (supplier) sends invoice data from its ERP or billing system to its ASP in an agreed format.
2. Corner 2 (supplier's ASP) validates the data, converts it to PINT AE XML if needed, and sends it over Peppol to the buyer's ASP.
3. In parallel, Corner 2 reports tax data to Corner 5, the FTA's central data platform.
4. Corner 3 (buyer's ASP) validates the invoice, confirms receipt to Corner 2, and also reports tax data to Corner 5. If validation fails, it tells Corner 2 and Corner 5, and does not report.
5. Corner 4 (buyer) receives the invoice in its own system, in whatever format it agreed with its ASP.
6. Confirmations flow back. The FTA confirms to both ASPs, which pass the confirmations on to supplier and buyer.

Each business must use one ASP for both sending and receiving invoices. The ASP generates a UUID for every invoice, but the supplier stays responsible for every value on it. The MoF publishes the list of accredited service providers, and its October 2026 programme presentation reports 65 accredited providers at that point.

When does UAE e-invoicing become mandatory?

The phases are set by Ministerial Decision No. 244 of 2025. The large-business ASP deadline was later moved from 31 July 2026 to 30 October 2026 by Ministerial Decision No. 66 of 2026. The FTA restated both phase dates in a 29 September 2026 announcement.

"Revenue" means gross income for your most recent accounting period, based on your financial statements. The MoF presentation adds that a newly established company should use projected revenue for the current financial year. These dates are current as of this post's publish date. The large-business deadline has already moved once, so check the MoF eInvoicing page before you commit to a plan.

Who and what is in scope?

Under Ministerial Decision No. 243 of 2025, e-invoicing applies to every person conducting business in the UAE, for every business transaction, unless excluded. The guidelines confirm three things:

• Covered: B2B, B2G, G2B and G2G invoices and credit notes, including supplies on government tender contracts. VAT registration status does not matter.
• Not covered for now: B2C. Sales to individuals who are not in business are outside the system until the Minister decides otherwise.
• Excluded transactions (as rewritten by Ministerial Decision No. 197 of 2026, in force from 1 October 2026): sovereign government activity, international airline passenger tickets and related ancillary services, VAT-exempt and zero-rated financial services under Article 42 of the VAT Executive Regulation, airline cargo under an airway bill for 24 months, and transactions between members of the same VAT tax group for 24 months from 1 January 2027.

Exports are in scope: a Dubai trader selling to a retailer in Kuwait still issues a UAE e-invoice.

What must your ERP or invoicing system change?

An ASP can convert formats, but it cannot invent data your system never captured. Check each item below against your ERP or billing tool.

Master data

• Your own Peppol ID. It is the scheme code 0235 followed by your 10-digit Tax Identification Number (TIN), which is the first 10 digits of your TRN. Members of a VAT group use their own TIN, not the group representative's.
• Customer participant IDs. The guidelines make the supplier responsible for collecting the buyer's Peppol ID. Add the field to customer records and to your onboarding form.
• Legal registration details, including the trade licence number, its type, and the issuing authority name, which has no code list and must be typed in.

Invoice data

The MoF's mandatory fields document lists 51 mandatory fields for an electronic tax invoice. The ones legacy systems most often lack:

• invoice type code and transaction type flags
• a tax category code on every line (standard, zero-rated, exempt, out of scope, reverse charge)
• unit of measure codes
• VAT and line totals in AED on each line, even when you invoice in USD or SAR
• a payment means code

You cannot add custom optional fields to PINT AE. Industry-specific needs have to be agreed with your ASP.

Process rules

• Corrections only by credit note. Decision 243 requires an electronic credit note when a sale is cancelled, the price is reduced, goods or money are returned, or there is an administrative or numerical error. Lock posted invoices against editing.
• Fourteen business days. Decision 197 sets the deadline at 14 business days from the date of the transaction. VAT-registered issuers must also meet the tax invoice timing in the VAT law.
• Unregistered buyers. If a UAE buyer has no participant ID yet, use endpoint 0235:9900000098 and also send a regular tax invoice. For export buyers without a Peppol ID, use 0235:9900000099.
• Status handling. Your system needs to store ASP confirmations and rejections per invoice, and show someone the failures. A rejected invoice is not an issued invoice.
• Accounts payable. You will receive XML too. Supplier bills should flow from your ASP into AP matching, not be re-typed from a PDF.
• Retention. Keep records for the Tax Procedures Law period (generally five years after the tax period), stored wherever you like as long as they can be produced to the FTA.

If invoices are created in several places, each source must feed the ASP. The discipline that keeps COD remittances reconciled applies: one record per transaction, no retyping.

UAE e-invoicing readiness checklist

Work through these in order. The first three are the ones the 30 October deadline depends on.

1. Confirm your phase. Take revenue from your latest financial statements and check it against the AED 50 million threshold.
2. Check your TIN and EmaraTax details. Make sure your trade licence, address and contacts are up to date in EmaraTax. Register for a TIN if you have no tax registration.
3. Select and contract an ASP from the MoF list, then start onboarding through EmaraTax. The guidelines say the business, not the ASP, starts this step.
4. Get your Peppol participant ID from your ASP.
5. Map your data to the 51 mandatory fields and find the gaps in item, customer and tax code masters.
6. Build the integration from your ERP or billing system to the ASP's API or file interface, including the return path for confirmations.
7. Collect customer Peppol IDs and flag customers who will still need a PDF.
8. Review self-billing arrangements, since self-billed e-invoices need the buyer to be on the system.
9. Test end to end with your ASP: standard invoices, credit notes, exports, zero-rated and exempt lines.
10. Write the go-live runbook: who watches rejections, who fixes them, and how fast.

Failure to implement can lead to administrative penalties, the FTA says. The MoF's October 2026 presentation marks Cabinet Decision No. 106 of 2025 on penalties as repealed. Check the current penalty decision on the MoF page before relying on any figure quoted elsewhere.

UAE e-invoicing vs Saudi ZATCA Fatoora

If you invoice in both countries, do not assume one integration covers both. The models are different.

Saudi details come from ZATCA's What is E-Invoicing page and its Detailed Guidelines. Saudi Arabia is still widening Phase 2. In Wave 25, announced 24 July 2026, ZATCA targets taxpayers whose VAT-subject revenue exceeded SAR 187,500 in any of 2022 to 2025, with integration due by 1 February 2027.

For a group with Dubai and Riyadh entities, the practical design is one internal invoice record with two outputs: PINT AE to the ASP, and Fatoora clearance or reporting for Saudi invoices. Keep AED and SAR ledgers separate, as you would for VAT on imports.

Where software help fits

The ASP handles Peppol. The hard part is upstream: clean master data, invoices from every system you use, and a loop for rejections. If your invoicing sits in an older ERP or several disconnected tools, Quickship's Software Development service builds integrations that connect the tools you already use, so data is entered once rather than typed twice. Whoever builds it, start with the data mapping.