If your business turns over AED 50 million or more, you have until 30 October 2026 to appoint an Accredited Service Provider.
That date is worth reading twice, because it changed. The original deadline was 31 July 2026. The Ministry of Finance extended it in May 2026 after reviewing market readiness. If your team has been working to no date at all, you have roughly three months.
The go-live date did not move. Mandatory compliance for that first wave still begins on 1 January 2027, which leaves about five months for an ERP implementation with a fixed external deadline.
This is not a software upgrade you can hand to your accountant in December. The number of businesses discovering that at the same time is about to become a constraint on availability. Here is what the mandate requires, what your enterprise software has to do that it probably cannot today, and a realistic sequence for the next ninety days.
The dates that apply to you
The Ministry of Finance issued Ministerial Decisions 243 and 244 of 2025 in September 2025, establishing the framework and the phased rollout. KPMG’s summary sets out the structure. The rollout runs in waves determined by revenue.
Wave 1, revenue of AED 50 million or more. Appoint an ASP by 30 October 2026. Go live 1 January 2027.
Wave 2, revenue below AED 50 million. Appoint an ASP by 31 March 2027. Go live 1 July 2027.
Wave 3, government entities. Appoint an ASP by 31 March 2027, with implementation following later in 2027.
The pilot phase opened on 1 July 2026 and voluntary participation is available now. Scope covers business to business and business to government transactions. B2C sits outside the mandate for the moment, and there are transitional exemptions in areas such as certain zero-rated financial services and international freight.
One point that catches people. If you are a Wave 2 business selling to a Wave 1 customer, that customer needs to receive structured invoices from January 2027. Your deadline on paper is July 2027. Your commercial deadline may be six months earlier, because a large client will not keep accepting PDFs from you once their own system rejects them.
This is an ERP problem, not an invoicing problem
The UAE has adopted a decentralised continuous transaction control and exchange model built on Peppol, using a UAE-specific invoice specification called PINT AE.
In practice that means a chain. Your enterprise software generates a structured XML invoice conforming to PINT AE. Your Accredited Service Provider validates it against the schema, applies a qualified electronic signature, and transmits it across the Peppol network. The Federal Tax Authority receives its copy in real time. Your customer’s ASP delivers the invoice into your customer’s system.
Two consequences follow, and both are frequently missed.
Your ERP cannot talk to the FTA directly. No accounting package can, whatever a vendor tells you. Odoo cannot. SAP cannot. QuickBooks and Zoho cannot. An ASP is a mandatory layer, not optional middleware, and only providers on the Ministry of Finance approved list are legally valid. The list carries more than forty accredited providers as of mid-2026 and continues to grow, so verify current status on the Ministry portal before you sign anything.
A perfect PDF is now worthless. From your go-live date, emailing a beautifully formatted, VAT-compliant PDF tax invoice does not discharge your obligation for in-scope transactions. The legal document is the structured XML.
That is why this lands on whoever owns your enterprise software rather than on your finance team alone. The compliance requirement is expressed almost entirely in data structure.
What your ERP has to do that it probably cannot today
Run this as a gap analysis before you talk to any vendor.
Generate PINT AE compliant XML. Not a CSV export, not a PDF, not a custom XML format your developer invented in 2019. The Mandatory Fields specification published alongside the Electronic Invoicing Guidelines in February 2026 sets out required invoice type codes, transaction flags, seller and buyer identifiers, tax category breakdowns, and line-level attributes.
Hold clean master data. This is where most projects actually fail. Every customer needs a valid Tax Registration Number in the right field. Every product or service line needs correct classification. Missing or malformed TRNs are among the most common rejection causes, and a rejected invoice means your customer never received it and your cash collection has stopped.
Handle the awkward document types. Credit notes must be electronic. Advance invoices must be cross-referenced to their final invoice, a requirement clarified in rulebook version 1.1 issued in June 2026. If you work in contracting or real estate development, retention billing has its own treatment. Milestone billing, variation orders, and self-billing arrangements all need mapping.
Connect to your ASP and manage exceptions. Rejected invoices need a queue, an owner, and a resolution process. Without one, rejections sit unnoticed and your receivables age quietly.
Archive compliantly. Invoice data must be retained and retrievable by the FTA under the Tax Procedures Law, stored in a manner that preserves integrity.
Work through that list honestly and most UAE mid-market systems fail at least three points. The master data problem alone typically takes longer to fix than the technical integration.
Odoo e-invoicing: what it covers and what it does not
Odoo has become the default choice for a lot of UAE mid-market businesses that want an ERP implementation without enterprise licensing, and it is a reasonable fit for this mandate. Its UAE fiscal localisation maps VAT treatments, credit notes, and self-billing to local requirements, and PINT AE compliant XML generation is achievable through the accounting module with the right configuration or a connector.
Be clear about the boundary, though.
Odoo e-invoicing is not a compliance product on its own. Odoo is corner one of the model, your system of record. It still needs an accredited ASP to validate, sign, and transmit. Several ASPs offer tested Odoo connectors, which shortens the build considerably, but the ASP relationship is a separate contract and a separate decision.
The configuration work is real. Mapping TRN and VAT fields, aligning product classification, adapting your invoice numbering, building the exception queue, and testing every document type your business actually issues. Implementations in this space commonly run eight to twelve weeks for a straightforward setup, and considerably longer if master data is poor or your Odoo instance carries heavy customisation from an earlier project.
If you are running an older Odoo version, budget for the upgrade as part of the same programme rather than as a separate project next year.
How to choose an ASP
Five criteria, in order of importance.
Confirmed accreditation. Check the Ministry of Finance list directly rather than taking a sales claim at face value. Accreditation requires Peppol certification and, following the May 2026 clarification, evidence that the solution has been operating for at least two years.
Proven integration with your ERP. A tested connector for your specific platform and version is worth more than a generic API and a promise.
Transparent pricing. Understand whether you are paying per invoice, per subscription, or both, and model it against your actual annual volume rather than a headline rate.
Security posture. ISO 27001 or equivalent, and clarity on where invoice data is stored, given the archiving requirement sits under UAE law.
UAE-based support. When an invoice rejects on a Thursday afternoon and your customer is chasing, response time matters more than the contract discount you negotiated.
One risk worth planning for. If your ASP loses accreditation or suffers an outage, your ability to issue valid invoices stops with it. Ask what the migration path looks like before you need it.
A realistic ninety-day sequence
For a Wave 1 business, working backwards from 1 January 2027, this is the shape of a sensible programme.
Weeks 1 to 3. Assess. Confirm your wave. Audit current invoice output against the PINT AE data dictionary. Run a master data health check on TRNs and product classification. List every document type you issue, including the unusual ones.
Weeks 3 to 6. Select. Shortlist three ASPs, test the connector claim rather than accepting it, and sign before 30 October.
Weeks 6 to 12. Build. Configure the ERP, map the fields, handle document types, build the exception queue, and integrate with any surrounding systems.
Weeks 12 onwards. Test in the pilot. This is the part to protect. The voluntary pilot running through the second half of 2026 lets you push real invoice flows and discover your rejection patterns without penalty exposure. Businesses that go live during the pilot window are outside the penalty regime for that period.
December. Train and cut over. Finance team, sales admin, and anyone who touches an invoice.
Skip the pilot and you will discover your edge cases in January, in production, with penalties attached. Reported penalty structures for non-compliance run to several thousand dirhams monthly under the 2025 penalty schedule, though you should confirm current figures with your tax advisor rather than relying on any published summary, including this one.
How Fitch Technologies helps
We handle this as an ERP implementation, because that is what it is. Gap analysis against the PINT AE specification. Master data remediation, which is usually the unglamorous majority of the work. Odoo configuration and connector build. ASP shortlisting on your behalf. Pilot testing across your real invoice types before the deadline, not after it.
Because our development and managed services teams work here in Dubai, the same people who build it support it in January when something rejects and somebody needs an answer that hour.
The scarce resource is calendar, not budget
Every Wave 1 business in the UAE is working to the same two dates. The accredited providers, the Odoo partners, and the integration specialists serving this market are finite, and demand is concentrated into a single quarter.
The businesses that come out of this cleanly will be the ones using the pilot phase for what it exists for, which is finding out what breaks while breaking it costs nothing. The ones that treat 30 October as the start of the project rather than a milestone inside it will be testing in production, in January, on live customer invoices.
You have the dates. The gap analysis takes a fortnight and tells you which of those two you are.
Book a free e-invoicing readiness assessment with our Dubai team →
This article is general information, not tax or legal advice. Fitch Technologies is not a tax advisory firm. The e-invoicing framework is actively evolving and at least one deadline has already been amended. Confirm current dates, thresholds, and penalty provisions against the Ministry of Finance and Federal Tax Authority publications and with your tax advisor before acting.
