UAE e-invoicing changes what an invoice is. Once the Federal Tax Authority (FTA) system goes live, an invoice stops being a PDF you email to a customer. It becomes structured data that leaves your business through an Accredited Service Provider (ASP). For most companies, the ERP, the billing tool and sometimes the online shop have to change with it. We write integrations for a living, so our focus here is the software.
Under UAE e-invoicing, every in-scope invoice and credit note goes out as XML through an ASP, which also reports the tax data to the FTA. Your systems have to hold the mandatory fields, send each invoice, process accept and reject messages and keep the records. Businesses with revenue of AED 50 million or more go live on 1 January 2027, and the rest follow in July or October 2027.
The first UAE e-invoicing deadline passed on 30 October 2026. By then the largest businesses had to appoint an ASP, and they go live in a few weeks. The dates and fields here come from Ministry of Finance (MoF) documents as they stood in November 2026.
When UAE e-invoicing starts and who it covers
Two 2025 ministerial decisions set the rules. Decision 243 sets out the obligations and Decision 244 sets the phases. Later ministerial decisions amended both, a Cabinet decision sets the penalties, and the MoF e-invoicing page lists them all.
Go-live dates by revenue
Decision 244 opened a pilot and voluntary implementation on 1 July 2026. Decision 66 of 2026 then moved the ASP deadline for the largest businesses from 31 July to 30 October 2026.
| Group | Appoint an ASP by | Live by |
|---|---|---|
| Revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
Revenue here means gross income for the most recent accounting period. Decision 244 also keeps business-to-consumer transactions out of the system until the Minister decides otherwise. The MoF guidelines print 31 October in their own phasing table, so get your ASP to confirm the date if one day matters to you.
Who falls under UAE e-invoicing
Decision 243 covers any person conducting business in the UAE, minus a list of exclusions. According to the MoF, it applies regardless of VAT registration. So a business under the VAT threshold can still fall in scope.
The exclusions cover sovereign government activity, certain airline transactions and VAT-exempt or zero-rated financial services. Transactions inside a tax group stay out of UAE e-invoicing for 24 months from 1 January 2027. Free zone companies do not appear in the list, and the invoice data model even carries a free zone flag.
How an invoice moves through the network
The five-corner model behind UAE e-invoicing
The MoF guidelines describe a five-corner model. You are corner 1 and your ASP is corner 2. The buyer’s ASP, the buyer and the FTA make up corners 3 to 5. Your software only ever talks to your own ASP. That ASP validates the data, converts it to the UAE XML standard where needed, passes it on and reports to the FTA.
Two things follow for developers. The guidelines say the e-invoice carries no QR code or barcode, so the QR-coded PDF you print today does not count. Confirmation messages also travel back along the chain, and your system needs somewhere to store them.
Some buyers will not have onboarded yet. For them, the guidelines name a predefined endpoint, 0235:9900000098, and ask for an ordinary PDF Tax Invoice as well. Exports to a buyer with no Peppol ID go to 0235:9900000099 instead. We keep both as configuration values so a change doesn’t need a new release.
What is a Peppol ID, and who issues yours
The guidelines also call it the endpoint ID. It takes the form 0235 followed by your 10-digit Tax Identification Number (TIN). The TIN is the first 10 digits of the Corporate Tax TRN. The guidelines describe the identifier as issued by the FTA during onboarding, and your ASP passes it to you once onboarding is complete.
On the software side, the TIN and endpoint belong on every legal entity record, next to the TRN. Each customer record needs that customer’s endpoint ID, or a flag saying they have none. Don’t work out a buyer’s endpoint from their TRN. Use the value the buyer gives you.
What UAE e-invoicing asks of your ERP
Mandatory fields and master data
Most of the work lands in master data first. The mandatory-fields document, version 1.1 of 28 October 2026 , lists 51 fields for an electronic Tax Invoice. Many come from customer and item records, which older systems tend to fill badly.
Seller and buyer each need a name, a tax identifier and an address with a city and country subdivision. The legal registration identifier must carry a type, such as a trade licence, an Emirates ID or a passport. Every item needs a name, a description, a unit of measure code and a tax category.
Each invoice also carries a transaction type code. It combines flags for free zone, deemed supply, margin scheme, continuous supply, exports and a few other cases. Your system has to set them from order data. The Tax Invoice also wants the VAT amount and line amount in AED on every line, even for a USD invoice.
UAE e-invoicing covers credit notes too. Decision 243 requires one for cancellations, reduced or returned consideration and administrative or numerical errors. Amended Article 6 sets 14 Business Days from the Date of Business Transaction for issuing an e-invoice or credit note, and a VAT registrant also has to meet the invoicing timeline in the VAT Law.
Sending invoices through the ASP
A UAE e-invoicing integration usually takes one of two shapes. Either your ERP sends data through an API or file exchange the ASP defines, or the ASP supplies a connector.
We design these around asynchronous results. Your ASP can accept an invoice that the buyer’s ASP later rejects, so posted and delivered become two separate statuses. The guidelines also make each business responsible for a UUID on every invoice, so retries should be idempotent.
Retention follows the Tax Procedures Law under amended Article 11. The guidelines give five years following the tax period for a taxable person, longer in some cases. The old “within the State” wording has gone from Article 11, so ask your ASP where the archive copy lives.
Online shops that sell to companies
As of November 2026, consumer-only shops sit outside UAE e-invoicing. Plenty of UAE shops sell to companies as well, though. A marketplace seller with corporate customers will issue invoices in scope, and so will a distributor with a trade portal.
For those shops, the new rules reach into checkout and the order record. Checkout has to collect the buyer’s TRN or TIN, trade licence and address as separate fields, then validate them. A business-account flag lets consumer and company orders follow different paths. Shipping, discounts and cash on delivery adjustments all have to map to invoice lines that add up exactly. Test the rounding with real orders.
The framework supports Arabic and English. If you send bilingual documents, keep the XML apart from the presentation layer. We have written before about connecting a CRM to an ERP , and the same rule holds here. Each field has one owning system, and every other system reads from it.
Testing a UAE e-invoicing integration
The guidelines list what testing should cover. You send an invoice through your ASP and get a success or failure message back. You also receive a supplier invoice through the network, and the ASP confirms its report to the FTA. Give receiving as much attention as sending, because Decision 243 gives recipients obligations too. We would start from a test plan like this one.
| Test | What to prove |
|---|---|
| Standard B2B sale | Invoice accepted, confirmation stored, ledger status updated |
| Free zone customer | Transaction type flag set, tax category correct |
| Export | Export flag set, endpoint rule for a buyer without a Peppol ID applied |
| Foreign currency sale | VAT and line amounts in AED present and consistent |
| Credit note | Linked to the original invoice, issued within the deadline |
| Rejection by buyer ASP | Status changes, user gets an alert, correction path works |
| Duplicate submission | Retry does not create a second invoice |
| Inbound supplier invoice | Received through the ASP and routed to accounts payable |
Error handling takes most of an integration budget. The happy path is the cheap part, and our breakdown of what a custom API costs goes into why.
Connector, configuration or a custom adapter
Start with what your ERP vendor already ships for UAE e-invoicing. If it offers an ASP connector or an update with the new fields, configuring that is usually quickest. Check it handles the transaction type flags, and get the version number from the vendor.
Bespoke or older invoicing systems need a different plan. A small adapter that builds the payload and talks to your ASP can cost less than replacing the whole system. Our notes on whether to build or buy go through that decision.
To pick an ASP for UAE e-invoicing, start with the official list and the selection guidance on the MoF e-invoicing page. Then ask each candidate about test environments, how rejections come back and what happens during an outage.
Penalties for missing the UAE e-invoicing deadline
Cabinet Decision 173 of 2026 sets the penalties. A first failure to implement the system or appoint an ASP costs AED 5,000. Another AED 5,000 follows for each month or part of a month it continues. Those fines stop at AED 50,000 in any 12 consecutive months. Each e-invoice the issuer fails to issue and transmit costs AED 100, up to AED 5,000 per calendar month, and missing credit notes carry the same rate and cap. Failing to tell your ASP about changes to the data registered with the FTA costs AED 250 per day, up to AED 5,000 per calendar month.
Where we fit in
We build the pieces between an ERP, a shop and an ASP. On a typical UAE e-invoicing project, we audit your data against the mandatory fields and write the adapter. We also build a test suite from your real invoice scenarios, plus the status screens finance staff use. Send us your ERP, invoice volume, ASP and go-live date through our software development service page. We’ll tell you what we can realistically deliver before your phase starts.