Appointed an ASP but Not Integrated? A UAE E-Invoicing Go-Live Plan for 1 January 2027

If your business had revenue of AED 50 million or more, it had to appoint an Accredited Service Provider (ASP) by 30 October 2026 and must issue e-invoices from 1 January 2027. Appointing the provider was the easy part. The work left is making your ERP produce complete PINT AE data, testing every invoice type with the provider, and deciding who fixes rejections. From early November that is about eight weeks, and it fits if the data gap assessment starts now.

This plan is for finance and IT teams in that position. It follows the four steps in the Ministry of Finance’s UAE Electronic Invoicing Guidelines (understand the requirements, select an ASP, test, go live), turned into dated weeks, with who does what and the checks we would want passed before 1 January.

The eight-week plan

Each row overlaps the next, because the slowest step - cleaning master data - runs alongside the build. The last column is the evidence that a step is really finished.

Two practical squeezes: the National Day holiday in early December and year-end leave both fall inside the testing window, and your provider is onboarding many other large businesses at the same time. Book test slots with the ASP early.

Step 1: Finish onboarding and agree the data route

Onboarding is started by you, not the provider. Your EmaraTax account admin opens the E-INVOICING tile, selects the provider you have contracted with and is passed to its portal to complete the process. Once that is done, the ASP issues your Peppol participant identifier, which is built from your Tax Identification Number (TIN): the first 10 digits of your 15-digit TRN.

Two points from the guidelines catch groups out. Each member of a VAT Tax Group is onboarded separately, with its own TIN, and members may use different providers. And each business onboards with only one ASP for all its e-invoicing.

In the same week, agree in writing how invoice data will reach the provider and how confirmations come back. A ready-made connector for your ERP, a documented API you integrate with, and a file upload you automate yourself are three very different projects. Our guide to which accounting systems support UAE e-invoicing shows what the main systems offer.

Step 2: Find the data gaps first

The Ministry’s mandatory fields list (version 1.1, 28 October 2026) sets 51 fields for an electronic tax invoice. Most ERPs already hold the majority. The gaps are usually the same ones:

• Customer identifiers. A valid TRN or legal registration number for each buyer, held in its own field rather than typed into an address line.
• The invoice transaction type code. Eight flags for free zone, deemed supply, margin scheme, summary invoice, continuous supply, disclosed agent billing, e-commerce and exports.
• Tax categories and AED amounts. A category on every line, and the VAT and line amounts in dirhams even on foreign-currency invoices.
• Goods and service codes. Goods need an HS classification code and services a service accounting code (SAC) under the UAE validation rules.
• Credit notes. A reason code and a reference to the original invoice.

Do it document type by document type, not field by field. A system that produces a perfect standard tax invoice can still fail on every credit note. Our article on PINT AE validation rules and rejection fixes lists the rules behind each of these.

Who does what: you, your ASP and your integrator

The guidelines are clear that the compliance obligation stays with the supplier even though the ASP does the exchange. This split comes from section 5.2 and Appendix 3 of the guidelines; the integrator column is the work that usually needs one when your ERP has no ready connector.

Step 3: Test every invoice type, both directions

The guidelines list six things to test with your provider before go-live. Put each through the test environment with real examples from your own invoicing, not a single sample:

1. Your system transmitting invoice data to the ASP.
2. The ASP issuing the invoice to the buyer.
3. You receiving the confirmation that the exchange succeeded or failed.
4. You receiving an e-invoice issued by one of your suppliers.
5. The ASP reporting tax data to the FTA.
6. You receiving the confirmation that tax reporting succeeded or failed.

Include every document type you actually issue: credit notes, self-billed invoices, exports, free zone supplies, summary and continuous-supply invoices, and invoices in foreign currency.

Step 4: Go/no-go checklist for late December

Before 1 January, each of these should be a yes:

• Onboarding with your ASP is complete in EmaraTax, and your participant identifier is live.
• Every legal entity that issues invoices is onboarded with its own TIN, including each member of a VAT Tax Group.
• Customer master data holds a TRN or legal registration number and a participant identifier for every B2B buyer.
• Every line carries a tax category (S, Z, E, O or AE), and every item is classed as goods or services with its code.
• Each document type you actually issue has passed end-to-end testing, credit notes included.
• Rejections come back into the system that issued the invoice, with a named person responsible for clearing them.
• Invoices from your suppliers arrive and can be posted without re-keying.
• You can issue a PDF tax invoice as well, for buyers who are not on the network yet (see below).

After go-live, an e-invoice or electronic credit note has to be issued and transmitted within 14 business days of the transaction, under Ministerial Decision No. 197 of 2026. That is the window your rejection process has to work inside.

Most of your buyers will not be live until July

Businesses below AED 50 million go live on 1 July 2027, so from January to June many of your customers will not be on the network. For those buyers, the guidelines say you issue the e-invoice to the predefined endpoint 0235:9900000098 and also issue a regular tax invoice, such as a PDF. Your process needs both paths, and a way to switch each customer over when it goes live.

One exclusion helps groups: under Ministerial Decision No. 197 of 2026, transactions between members of the same VAT Tax Group are excluded from e-invoicing for 24 months from 1 January 2027.

If you missed the 30 October appointment

Failing to appoint an ASP is part of the first violation in Cabinet Decision No. 173 of 2026, which replaced Cabinet Decision No. 106 of 2025: failure to implement the e-invoicing system. The penalty is AED 5,000 for the first instance and AED 5,000 for each month or part of a month it continues, capped at AED 50,000 in any 12 consecutive months.

We found no separate late-appointment procedure in the published documents. The practical route is the same as everyone else’s, done faster: contract with a provider, onboard through EmaraTax, and run steps 2 to 4 in parallel. Ask your tax adviser how the penalty applies to your dates.

What makes eight weeks too short

• Several entities or systems issue invoices. Each needs onboarding, mapping and testing.
• Invoices come out of bespoke or legacy software with no connector for your provider.
• Master data is incomplete. Collecting TRNs and participant identifiers from hundreds of customers takes calendar time, not engineering time.
• Unusual document types such as self-billing, margin scheme or disclosed agent billing.
• High inbound volume that has to post into accounts payable automatically.

If two or more apply, put your energy into the invoice types that cover most of your volume first, and agree the plan for the rest with your adviser.

Mistakes we see in the last weeks

• Testing one standard invoice and calling it done. Credit notes and foreign-currency invoices fail differently.
• Expecting the ASP to repair data. It validates and rejects; it does not fill in a missing TRN.
• Forgetting the inbound side. Your suppliers’ e-invoices will arrive through your ASP from day one.
• No owner for rejections. Errors land in a portal nobody checks while the 14-day clock runs.
• Switching off PDFs too early. Buyers not yet on the network still need a regular tax invoice.

Where we fit

We are not an ASP. We build the layer between your systems and the one you have appointed: UAE e-invoicing integration that maps your data to PINT AE, checks it before it leaves your system and brings rejections back to the people who can fix them. If you have appointed a provider and the integration has not started, tell us what your invoicing runs on and we will tell you honestly whether 1 January is realistic.

Go-live questions

Regulatory details in this article were checked against Ministry of Finance publications on 6 November 2026. Dates and rules can change, so confirm your obligations with your tax adviser or your Accredited Service Provider. This is general information, not tax advice.

Official sources: Ministry of Finance - eInvoicing · UAE Electronic Invoicing Guidelines · Ministerial Decision No. 66 of 2026 · Ministerial Decision No. 197 of 2026 · Cabinet Decision No. 173 of 2026