UAE E-Invoicing Go-Live Checklist for Finance Teams

My UAE e-invoicing guide for Odoo explains what the mandate is, and my ASP integration guide explains how an Odoo database reaches the network. This page is the piece in between that finance teams keep asking me for: the run sheet. It is the list I walk a finance controller through, stage by stage, with the boxes you need ticked before the ASP deadline, before go-live and on every working day after it.

Print it, put a name next to every line, and work through it in order. Most of it is finance work, not IT work. The checklist assumes Odoo, but most lines apply whatever system raises your invoices.

Print this checklist

Where the clock stands on 19 October 2026

The dates come from Ministerial Decision No. 244 of 2025, with the Phase 1 appointment date moved from 31 July to 30 October 2026 by Ministerial Decision No. 66 of 2026. The Federal Tax Authority repeated both Phase 1 dates on 29 September 2026.

"Revenue" here means gross income for your most recent accounting period, based on your financial statements. The obligation sits with each legal entity, so a group can have one entity on the January 2027 timeline and another on July 2027. For scope, exclusions and the full phase logic, use the pillar guide. This page assumes you already know which phase you are in.

Stage 1: Readiness and ownership

Before anyone touches configuration, finance needs to know exactly what it issues, from where, and who signs off. In my experience the projects that slip are the ones where nobody owns this list.

• Confirm the phase for each legal entity from its latest financial statements, and write both deadlines (ASP appointment and implementation) on the plan.
• Name one finance owner, one IT or system owner and an executive sponsor. Agree who has the final say on tax treatment.
• List every document type you issue: tax invoices, commercial invoices (sales that need no tax invoice), tax credit notes, credit notes, self-billed invoices, summary invoices, milestone and retention billing, and advance-payment invoices.
• Flag the scenarios the guidelines treat specially: free zone parties, deemed supplies, margin scheme, summary invoices, continuous supply, disclosed agent billing, e-commerce and exports. One invoice can carry more than one.
• List every system that raises invoices: Odoo, point-of-sale, a billing tool, a spreadsheet, a Word template on someone's desktop. Each one is either brought into scope or retired.
• Separate business-to-consumer sales, which are outside the system for now, from B2B and B2G sales, which are in.
• Review exclusions and grace periods with your tax advisor. The Ministry now refers to Decision No. 243 of 2025 “and its amendments”, so work from the current text, not the original.
• Check every self-billing arrangement: self-billed e-invoices need the buyer to be on the system, and the buyer may be on a later timeline than you.
• Log in to EmaraTax and check your trade licence, address and contact details are up to date. Confirm who holds the account admin login, because onboarding starts there.
• Agree a budget and a sign-off date for the whole plan, working back from the implementation date rather than the appointment date.

The Ministry's own guidelines include a short readiness checklist in Appendix 2. Everything on it is covered in this page, broken into tasks you can assign.

Stage 2: Master data clean-up in Odoo

Validation is decided by data, not by your invoice template. The Ministry's mandatory fields document lists 51 mandatory fields for an electronic tax invoice and 49 for a commercial e-invoice, and every one of them has to come from somewhere reliable in Odoo. This is the stage that takes longest, so start it first.

Customers and vendors

• Every B2B customer and vendor has a TRN in the partner's tax ID field where one exists. It belongs in that field, not in a note or a custom field nobody maintains.
• The partner name is the registered legal name, not the trading name sales typed when they created the record.
• Addresses are complete: address line, city, emirate (Odoo's State field) and country.
• Buyers' Peppol participant identifiers are being collected. The guidelines make gathering them the supplier's job, and the identifier is based on the buyer's TIN, the first 10 digits of its TRN.
• For free zone customers, you know who the beneficiary is when it differs from the customer, because the e-invoice needs both.
• Duplicate partners are merged before go-live, so one buyer does not appear under three spellings.

Your own company records

• Each company in the database has its legal name, TRN, full address and trade licence number, plus the name of the licensing authority, which the issuer fills in by hand.
• If you run several companies in one database, each has its own sequence prefix, TRN and onboarding. My multi-company guide covers the free zone and mainland split.

Products, taxes and amounts

• Every invoiced line has an item name and a description. Free-text lines with no product are reviewed.
• Units of measure you invoice in are mapped to codes from the PINT AE code list.
• Every tax maps to exactly one of the six tax categories in the guidelines: standard rate, zero rated, exempt, out of scope, reverse charge or margin scheme. Domestic reverse-charge invoices carry a narrative and the type of goods. My Odoo UAE VAT guide covers the tax setup itself.
• Every invoice gets a due date and a payment means, because both are mandatory fields.
• Foreign-currency invoices can show the VAT and total per line in AED, and currency rates follow the Central Bank rate the guidelines refer to.
• Invoice numbering is unique per company and journal, with no shared prefixes and no cancel-and-reuse habits.

If your history is messy, fix the records you will invoice next quarter first and archive the rest. The same principles as a migration apply, and my data migration guide covers how to clean before you move.

Stage 3: Choosing and onboarding your ASP

Appointing a provider is a contract and an EmaraTax step. Integrating with it is a project. The FTA's sequence is clear: select a provider, contract and integrate with it, then complete the procedures on EmaraTax.

Shortlist and select

• Shortlist only from the Ministry's list of Accredited Service Providers. When I checked on 19 October 2026 (page stamped 18/10/2026) it listed 67 accredited providers, plus 3 pre-approved providers still in final assessment. Pre-approved is not the same as accredited.
• Score each candidate against the Ministry's Considerations for Selecting an ASP: time as a Peppol service provider, UAE presence, whether the product is its own or a third party's, who provides support, integration options (APIs and formats), where the data is stored, security certifications, uptime and support SLAs, pricing model and scalability.
• Add the Odoo questions: which integration route they support, who owns the field mapping at your next Odoo upgrade, how rejections and confirmations come back into Odoo, and how supplier e-invoices will arrive in your vendor bills. The ASP integration guide explains the three routes.
• Appoint one ASP per legal entity for both sending and receiving. In a VAT group, each member onboards with its own TIN and may choose a different provider.
• Agree data hosting and data security terms in writing, including who stores the e-invoices and for how long.
• Sign the contract and meet the commercial terms. The guidelines require this before you onboard on EmaraTax.

Onboard through EmaraTax

• The account admin of the taxable person opens the E-INVOICING tile in EmaraTax, selects the contracted ASP and clicks “Proceed to ASP” to finish onboarding on the provider's portal. The business starts this, not the provider.
• If an entity has no TIN yet, it registers with the FTA first to get one.
• The ASP issues your Peppol participant identifier. Record it against each company in Odoo.
• Keep evidence of the appointment date for each entity on file.

Stage 4: Mapping and testing

Testing is where compliance stops being a slide deck. Use the voluntary window: the guidelines say e-invoicing penalties do not apply to invoices issued voluntarily, so the weeks before your mandatory date are the cheapest time to find mistakes.

• Agree with the ASP how invoice data reaches them, how success and failure confirmations come back, and how supplier e-invoices are delivered to you.
• Map each mandatory field to its source in Odoo, and note who fixes it when it is empty. You cannot add your own optional fields to PINT AE, so agree any special requirements with the ASP.
• Reconfigure approval workflows so invoices are approved before they are sent. Once an e-invoice is out, the fix is a credit note, not an edit.
• Test the full loop the guidelines describe: Odoo sends data to the ASP, the ASP delivers to the buyer, you get the exchange confirmation, you receive a supplier e-invoice, the ASP reports tax data to the FTA, and you get that reporting confirmation.
• Build a rejection drill: a user sees the rejection in Odoo, fixes the cause and resubmits, and someone checks it was accepted.

Test cases I would not go live without

• A standard-rated tax invoice, and a commercial invoice for a sale that needs no tax invoice.
• Mixed lines: standard, zero-rated and exempt on one invoice.
• A foreign-currency invoice with AED amounts per line.
• A full credit note and a partial credit note, each referencing the original invoice, plus one credit note covering several invoices.
• An advance-payment invoice followed by a final invoice for the balance only, as in Appendix 5 of the guidelines.
• Retention billing and milestone or continuous-supply billing, if you use them.
• A free zone customer with a different beneficiary, a domestic reverse-charge sale, and a deemed supply if you have any.
• An invoice to a buyer who is not yet on the system.
• A deliberately broken invoice (missing TRN, unmapped tax) to prove the rejection drill works.

Stage 5: Cut-over

Pick the cut-over date yourself and make it earlier than your mandatory date. Go-live week is the wrong time to discover the sales team still emails PDFs from a template.

• Freeze changes to taxes, journals, sequences and invoice layouts for the cut-over period.
• Post or cancel open draft invoices. Agree with your ASP and tax advisor how to handle credit notes against invoices issued before go-live.
• Close the side doors: retire any spreadsheet, template or tool that can still issue an in-scope invoice outside Odoo.
• Keep the PDF path for buyers who are not on the system yet. The guidelines say they still need a regular tax invoice in addition to the e-invoice.
• Agree the error-handling model with the ASP before go-live: contacts, escalation, support hours and who resubmits.
• Tell customers what is changing and collect any missing Peppol identifiers. Tell suppliers how their e-invoices should reach you.
• Brief the team on the issuing deadline in Decision No. 243 of 2025 (as amended). An invoice left sitting in draft is no longer just a cash-flow problem; it can become a compliance one.
• Put a hypercare roster in place for the first two to four weeks, with finance and IT on the same daily call.

If e-invoicing lands in the middle of a wider rollout, plan it as one workstream in the overall plan. My implementation timeline shows where hypercare fits.

Stage 6: After go-live

Go-live is when the checking starts. This is the routine I hand over to finance teams once hypercare ends.

Daily

• Every invoice and credit note posted yesterday has a successful exchange confirmation and a tax data reporting confirmation from the ASP.
• The count of posted documents in Odoo matches the count the ASP confirms. Chase any gap the same day.
• Rejections are cleared and resubmitted, and the cause is logged.
• Supplier e-invoices received through the ASP have reached vendor bills.

Monthly

• Review the rejection log by root cause and fix the master data behind repeat failures.
• Reconcile your Odoo VAT return figures with the e-invoice data your ASP reported. The Ministry expects e-invoicing to pre-fill certain VAT return fields in time, so differences should be explained, not ignored.
• Check for new legislation, guideline versions and PINT AE releases. The OpenPeppol PINT AE billing specification was at version 1.0.4 when I checked, and HSN codes are optional for now, with a date for making them mandatory to be announced.

Whenever something changes

• Notify your ASP in writing within five business days of the FTA confirming a change to your registered data (Article 5 of Decision No. 243 of 2025). Use the EmaraTax reverification or offboarding process for changes such as joining or leaving a VAT group.
• If the ASP has a service disruption, make sure it notifies the FTA and resends every pending e-invoice once service is back.
• Keep e-invoices and associated data retrievable for the Tax Procedures Law retention periods. An ASP can store them for you under contract, but the legal obligation stays with you.
• Re-run the test cases after every Odoo upgrade or connector update before live invoicing resumes. My upgrade guide explains why connectors are where upgrades break.

A note on penalties

I am not quoting penalty amounts on this page. Cabinet Decision No. 106 of 2025 set the original e-invoicing penalties. The Ministry's October 2026 programme presentation lists it as repealed and names Cabinet Decision No. 173 of 2026 as the current penalties decision, but that text was not on the Ministry's e-invoicing page when I checked on 19 October 2026. What is clear from the guidelines is that e-invoicing penalties start from your mandatory implementation date, and that the separate VAT penalties for tax invoicing failures still apply. Read the current decision at source before you brief your board.

Where Odoo fits

Odoo's electronic invoicing documentation for version 20.0 does not list the United Arab Emirates among the countries eligible for Peppol registration in Odoo, and the UAE fiscal localization page does not cover e-invoicing. So on Odoo, the route to the network runs through your ASP, which is why this checklist spends so long on data and testing. Odoo does the invoicing, and the ASP handles validation, delivery and FTA reporting. Your finance team still owns the result. The same data discipline feeds your corporate tax reporting in Odoo, so the clean-up pays off twice.

Frequently asked questions

Related reading

Start with the parent guide, UAE e-invoicing 2026–2027 and what it means for your Odoo ERP, then the three ways to connect Odoo to an Accredited Service Provider. For the configuration underneath, see Odoo UAE VAT setup, UAE corporate tax in Odoo and Odoo data migration. For the people side, see how to choose an Odoo partner in the UAE and why Odoo implementations fail. All guides are on the guides index.