Going live by 1 January 2027: an 8-week e-invoicing plan for large UAE businesses

What has to be in place on 1 January 2027?

From that date, every in-scope business transaction needs an e-invoice, and every cancellation, price reduction, refund or administrative or numerical error needs an electronic credit note, issued and transmitted through your ASP (MD 243/2025, Art. 6(1) and 6(2)) and reported to the FTA through the same ASP (Art. 6(6) and 6(7)). MD 244/2025 adds that you must complete the onboarding process and meet the technical requirements of the Ministry and the FTA (Art. 5(3)).

You are a recipient from day one too. Suppliers who are live will send you e-invoices, and MD 243/2025 requires you to process them through the system (Art. 6(3)). Cabinet Decision No. 173 of 2026 penalises a recipient that implemented e-invoicing but does not keep up its obligations as a recipient (table, row 1(b)).

In practice that means four things working on the day: a contract and onboarding with one ASP for each company, a Peppol Participant Identifier, invoice and credit-note data that leaves your systems complete, and a way to receive and process the e-invoices your suppliers send.

Sources: ^[5][1][3]

Not appointed an ASP yet? What should you do this week?

Start with the Ministry of Finance's published list of accredited providers and its paper on considerations for selecting an accredited service provider. Shortlist providers that can take data from your systems, ask each for a dated onboarding and testing plan to 1 January, and sign. The Guidelines require the contract to be final, with its commercial obligations met, before you onboard to the ASP's system through EmaraTax (Appendix 1, §13.2).

On penalties, read the texts as they stand. Cabinet Decision No. 173 of 2026, which repeals CD 106/2025 from the day after its publication in the Official Gazette, lists not implementing e-invoicing, "including the failure to appoint an Accredited Service Provider", at AED 5,000 for the first instance plus AED 5,000 for each month or part of a month it continues, capped at AED 50,000 in any 12 consecutive months (table, row 1(a)). The Guidelines say penalties apply from the date a person must mandatorily implement (§8.2). Neither text says whether a business that missed 30 October 2026 is exposed from 31 October 2026 or from 1 January 2027: ask your ASP or tax adviser.

Sources: ^[9][8][4][3]

What should weeks 1 and 2 cover (2 to 15 November)?

Scope and access. Map every company in your group, its TRN and its revenue for the most recent accounting period, which is how MD 244/2025 defines revenue (Art. 1). Check that each company's details in EmaraTax, such as trade licence, address and contact details, are up to date before onboarding (Guidelines, Appendix 3). Then onboard: the account admin starts it in EmaraTax, you continue on the ASP's portal, and the ASP shares your Participant Identifier, 0235 followed by your 10-digit TIN, once onboarding is complete (Appendix 1, §13.2; Appendix 3).

Use the same two weeks to list your transaction types, because the Guidelines ask for a gap analysis of the e-invoice categories each transaction needs (Appendix 1, §13.1(c)). There are six: electronic tax invoices and tax credit notes, their self-billed versions, commercial invoices and electronic credit notes (§10.1). Sales that need no tax invoice, such as exempt or out-of-scope supplies, are made on commercial invoices, and these too must become e-invoices (§10.2.1).

Sources: ^[1][4]

What should weeks 3 and 4 cover (16 to 29 November)?

Data. Make sure your accounting or ERP systems can produce every data point an e-invoice needs. The Mandatory Fields V1.1 (28 October 2026) list them for an electronic tax invoice and, separately, for a commercial e-invoice, and the Guidelines ask you to plan any data migration this needs (Appendix 1, §13.1(c)).

Customers. Collecting each buyer's Participant Identifier is the supplier's job (§5.2), so start now. For customers who will not be live on 1 January and have no Participant Identifier, such as many businesses under AED 50 million whose date is 1 July 2027, the e-invoice carries the predefined endpoint 0235:9900000098. For a tax invoice to a buyer that has not implemented e-invoicing, you send a regular tax invoice such as a PDF as well (§10.2.2).

Credit notes and changes. Check that your system keeps the link between each credit note and the invoice it corrects: one electronic tax credit note can reference several past tax invoices, and a credit note can cover only part of an invoice (§12.2). And name the person who tells your ASP when your data registered with the FTA changes; the rule and the penalty are in the questions below.

Sources: ^[7][4]

What should weeks 5 and 6 cover (30 November to 13 December)?

Connect and test. Agree with your ASP how the data for each invoice reaches it, how you receive confirmation messages, and how you receive through it the e-invoices your suppliers send (Appendix 1, §13.3(a)). Complete any integration between your systems and the ASP's in time, and adjust internal approval workflows if needed (§13.3(b)).

Then test the whole chain, not only sending: data to your ASP, delivery to a buyer, the confirmation on the exchange, an e-invoice received from a supplier, the tax-data reporting to the FTA, and the confirmation on that reporting (§13.3(c)). Include a credit note, a sale to a buyer with no Participant Identifier and, if you export, an export. Voluntary e-invoicing has been open since 1 July 2026, and voluntary use is outside the penalties decision (MD 244/2025, Art. 4; CD 173/2026, Art. 2(2)).

Sources: ^[4][1][3]

What should week 7 cover (14 to 20 December)?

Errors and owners. Before going live, set up a governance model with your ASP on how errors are resolved during and after go-live (Appendix 1, §13.4(a)): who reads a rejection, who fixes the data, who resends, and how fast. Agree with your ASP on data hosting and data security requirements, an item on the Ministry's readiness checklist (Appendix 2).

Run that checklist line by line, and brief everyone who posts invoices: your ASP validates the data you send before anything is exchanged (§5.1, step 2), so a missing customer identifier or tax code can stop an e-invoice. Leave room for year-end closing.

Sources: ^[4]

What happens in week 8 and on 1 January (21 December to 1 January)?

Freeze changes to master data and invoice templates, confirm with your ASP the checks you will both watch on the day, and agree how invoices around the switch are handled, for example December supplies invoiced in January. From 1 January, start the exchange, sending and receiving, and the reporting, and monitor issues with your ASP for timely resolution (Appendix 1, §13.4(b) and (c)).

After go-live, keep your ASP updated when your circumstances change, such as registering for VAT, joining or leaving a tax group or deregistering, through the EmaraTax reverification or offboarding processes (Appendix 1, §13.5).

Sources: ^[4]

What changes for tax groups and several companies?

Each member of a tax group onboards on its own, with its own TIN, the first 10 digits of its own TRN rather than the representative's, and its own Participant Identifier. Members may choose different ASPs, but each onboards with only one (Guidelines, Highlights; Appendix 1, §13.2).

Transactions between members of the same tax group have a 24-month grace period from 1 January 2027 (MD 197/2026, Art. 2, the new Art. 4(1)(f) of MD 243/2025). The Guidelines stress that it changes the timing only: intra-group transactions stay in scope, and sales to anyone outside the group follow your normal date (§6.3.2). Plan the intra-group flows now, even if they start later.

Sources: ^[4][6]

Where Vattora fits, and when you do not need it

Vattora fits weeks 3 to 6. It reads posted invoices and credit notes from your accounting system, builds each one as a checked PINT AE e-invoice, sends it to the ASP you appointed and shows you the status that comes back. Vattora connects to the ASP you choose through that provider's API; each link is built and tested in the provider's test environment before your first real invoice. Several ERPs that large businesses run are still connectors in testing, so check the real status of yours on the systems page before you plan around it. You do not need Vattora if your ERP vendor's own e-invoicing route or your ASP's tools already cover your systems. It does not receive e-invoices for you today: that side stays with your ASP.