UAE E-Invoicing Go-Live: Practical Steps After Appointing Your ASP

If your business has UAE revenue of AED 50 million or more and you appointed your Accredited Service Provider (ASP) by 30 October 2026, you now have about 50 days before e-invoicing becomes mandatory on 1 January 2027.

Signing with an ASP is the start of the project, not the finish. The ASP moves your invoices across the Peppol network and reports the tax data to the FTA. What it cannot fix is incomplete master data, an ERP that cannot produce the required fields, or finance teams who do not know what to do when an invoice is rejected.

The cost of getting it wrong is now defined. Under Cabinet Decision No. 106 of 2025, failing to implement the system costs AED 5,000 per month or part month. Each invoice or credit note not issued and transmitted through the system costs AED 100, capped at AED 5,000 per calendar month. Failing to notify the Authority of a system failure costs AED 1,000 per day.

The steps below draw on what worked, and what failed, in mandates that went live before the UAE: Saudi Arabia (FATOORA), Italy (SdI), Malaysia (MyInvois), Singapore (InvoiceNow on Peppol) and Belgium’s 2026 Peppol mandate.

1. Lock the scope: every entity, TRN, invoice type and flow

List every legal entity and TRN in scope, including VAT groups and branches. Then map every outgoing and incoming document type: standard tax invoices, simplified invoices issued to businesses, credit notes, self-billing, continuous supplies, advance payments, disbursements and intercompany charges.

• Confirm which flows are B2B and B2G (in scope) and which are B2C (currently outside the system).
• Identify every place an invoice is created today: ERP, billing platforms, point-of-sale, Excel, manual Word templates, sub-ledgers in branches. Manual invoices are the most common gap found at go-live in every country.

2. Close the data gaps against the PINT AE data dictionary

The UAE uses the Peppol PINT AE specification. Run a field-by-field gap assessment of your ERP output against it: buyer and seller TRN/TIN, Peppol participant ID, addresses, item classification, tax category codes, exemption reasons, currency, payment terms and references to original invoices for credit notes.

• Customer and supplier master data is the single biggest risk. Cleanse TRNs, legal names and addresses now and validate them against the FTA records.
• Collect your customers’ Peppol identifiers. A customer who is not yet reachable on Peppol is an operational question you must answer before 1 January, not after.
• Global lesson: Malaysia and Belgium both saw large rejection volumes in the first weeks caused by bad buyer IDs, not by technology.

3. Decide the integration pattern and freeze ERP changes

Agree with your ASP how invoices leave your system: direct API, connector or middleware, file drop, or the ASP’s portal for low-volume entities. Choose one pattern per entity and document it.

• Set a code freeze for ERP and billing changes from early December that are not e-invoicing related.
• Make sure invoice numbering stays unique and sequential per entity, and that the ERP stores the ASP’s acknowledgement and status against each invoice.

4. Redesign the sales-side process: issue, transmit, track, correct

Write the new order-to-cash procedure. Who issues, when, and how is status checked? What happens when the ASP or the buyer’s corner rejects an invoice?

• A rejected or failed invoice must be corrected and re-sent quickly. Build a daily exception queue owned by a named person.
• Stop issuing manual or PDF “tax invoices” for in-scope supplies. A PDF can still travel as a visual copy, but the structured e-invoice is the legal document.
• Define the rules for credit notes. Under Cabinet Decision 106, a missing electronic credit note is penalised in the same way as a missing invoice.

5. Redesign the purchase side: receive, validate, book

E-invoicing is two-way. From 1 January you will receive structured invoices from suppliers through your ASP.

• Decide whether incoming e-invoices feed directly into accounts payable for automatic matching to purchase orders and goods receipts.
• Agree how input VAT recovery will be supported. Treat the received structured e-invoice as your primary evidence and keep your document-retention policy aligned.
• Tell your top suppliers what you expect: your Peppol ID, PO number on every invoice, and the cut-off date after which paper or PDF tax invoices will be queried.
• Global lesson: Italy’s SdI showed the biggest long-term benefit sits on the purchase side, through faster matching and fewer disputes. Plan for it now.

6. Test end to end with real scenarios, not just a connection test

A successful “hello world” message to your ASP proves very little. Build a test pack of 30 to 50 real scenarios and run them through to the FTA reporting corner in the ASP’s test environment.

• Include: zero-rated, exempt and out-of-scope lines, reverse charge, discounts and rebates, multi-currency invoices, partial and full credit notes, advance payments, intercompany charges and invoices to free zone entities.
• Test negative cases on purpose: wrong TRN, missing mandatory field, duplicate invoice number, an unreachable buyer.
• Get Tax to sign off the VAT treatment of each test result, and IT to sign off the technical flow.

7. Reconcile e-invoices to the VAT return

From January, the FTA will see your invoice data in near real time. Any difference between what your ASP reported and what you file in your VAT return becomes visible.

• Build a monthly three-way reconciliation: ERP ledger, ASP transmission log, and VAT return boxes.
• Investigate differences before filing, not after an FTA query.
• Global lesson: in Saudi Arabia and Italy, authorities moved within a year or two from receiving data to using it for pre-filled returns and risk-based audits. Assume the FTA will do the same.

8. Prepare a business-continuity and system-failure plan

Write down what happens if your ERP, your connector or your ASP is down at month-end.

• Define how outages are detected, who decides it is a “system failure”, and who notifies the FTA. Late notification carries its own daily penalty of AED 1,000.
• Agree a backlog procedure: invoices queued and transmitted in order once the system is back.
• Check your ASP contract for service levels, uptime, support hours over weekends and year-end, data retention and exit terms.

9. Train people, communicate externally, and run a hypercare period

Train the people who touch invoices: billing, AR, AP, sales coordinators, branch staff and the tax team. Give each role a one-page guide on what changes.

• Send written notices to key customers and suppliers in November and December.
• Run a four-to-eight week hypercare period from 1 January with daily status checks, a rejection dashboard and a fast escalation route to the ASP.
• Hold a post-go-live review at the end of January and again after the first VAT return period that includes e-invoices.
• Global lesson: go-live day is rarely the problem. The first month-end close and the first VAT filing are where gaps show up.