Guide
Setting Up a UAE eInvoicing Technology Provider or ASP
The short answer
The Ministry of Finance sets the UAE's eInvoicing framework and accredits service providers; the Federal Tax Authority runs the exchange and the EmaraTax system through which businesses select one. The permission that matters is Accredited Service Provider (ASP) status under Ministerial Decision No. 64 of 2025 — a different thing from a standard technology trade licence, which a company can hold without ever touching the regulated exchange. The question that decides the route is simple: does the company exchange invoices as one of the four corners, or does it supply software to someone who does?
The four-corner model and who decides your role
The exchange works on a four-corner model: Corner 1 is the supplier issuing the invoice, Corner 4 is the customer receiving it, and the two exchange structured invoice data through accredited intermediaries rather than emailing a PDF. Corner 5 reports the same data to the Federal Tax Authority for tax purposes, and this reporting corner went live ahead of the pilot that began on 1 July 2026.
A business cannot simply declare itself part of this chain. An ASP is accredited by the Ministry of Finance, and a client picks its ASP by entering a commercial agreement and selecting it through the Federal Tax Authority's EmaraTax system. If a company's product only prepares or displays invoice data without carrying it across the exchange, it is not acting as Corner 1, 4 or 5, and accreditation is unlikely to apply — but that is a question about what the software actually does, not what the trade licence calls it.
What the Ministry of Finance and Federal Tax Authority actually require
Three ministerial decisions carry the legal weight here. No. 243 of 2025 established the eInvoicing system; No. 244 of 2025 set its implementation procedures; No. 64 of 2025 sets who can become an Accredited Service Provider and how. The Federal Tax Authority defines eInvoicing narrowly: structured invoice data issued and exchanged electronically, which excludes a PDF or an emailed invoice however neatly formatted.
For businesses with annual revenue above AED 50 million, the Ministry has fixed two dates: appoint an ASP by 30 October 2026 — extended in May 2026 from an original 31 July 2026 deadline — and have the system running by 1 January 2027. The Ministry has said other revenue bands and government entities follow a later schedule, but at the time of writing it published that schedule as an image on its own portal rather than as text, so this guide does not repeat a specific date for a business under the AED 50 million threshold. Check the Ministry's live eInvoicing portal before relying on one.
By May 2026 the Ministry had already approved 32 service providers, with more in the final stages of accreditation, and had amended the rules so a UAE company can partner with an international provider to bring in the underlying technology and know-how.
Vendor, integrator or ASP: structure decisions that change the answer
Fix which model the business actually is before comparing jurisdictions, because each answers to a different part of the regime.
- ERP or accounting-software vendor, selling tools that produce compliant data but sitting outside the exchange itself.
- Systems integrator, connecting a customer's ERP to an ASP without becoming one.
- Accredited Service Provider, carrying invoices through the exchange as Corner 1, 4 or 5 on a client's behalf.
- Compliance, archiving or analytics layer, built around the data once it has already moved.
A build, partner or white-label decision follows from this. The May 2026 amendment that allows local companies to partner with international providers exists because most UAE entrants are not building exchange infrastructure from zero; they are licensing or white-labelling it. That choice changes who the Ministry accredits, who signs the client contract, and who carries the compliance risk if the underlying technology fails — three separate questions a single company name can obscure.
How money and liability move through the exchange
A bank assessing this business wants to see recurring software or transaction revenue, not a one-off trade licence, and will ask who is liable when an invoice is rejected or mis-transmitted — the vendor, the integrator, the ASP or the client. Put that allocation in the client contract before the first invoice moves, not after a dispute.
Where the business is funded by investors or an international technology partner, the source of the funding and the structure of the partnership matter to both the bank and to the Ministry's accreditation review; document source of funds alongside the technical application rather than afterwards. A banking readiness assessment before accreditation is sought tends to surface these questions earlier, when they are still cheap to answer. Cost here is not one headline number: it is built in layers across formation, accreditation and ongoing compliance, and the Velarozone fee for working through them is itemised in the engagement letter — see how Velarozone works.
What commonly goes wrong
- Marketing as an approved ASP, or implying accreditation, before the Ministry has granted it.
- Treating a structured invoice exchange as equivalent to emailing a PDF, which the Federal Tax Authority's own definition excludes.
- Leaving liability for a rejected or mis-transmitted invoice undefined in the client contract.
- Assuming a software trade licence alone satisfies a client's revenue-threshold obligation.
- Building a white-label partnership without documenting which entity the Ministry is actually accrediting.
From accreditation to daily operation
Accreditation is not a one-off event. The Ministry reviews it, so the technical team, the data-hosting arrangement and the support model need to stay as described in the application, not drift once a client is onboard. Key technical and compliance staff usually need UAE residence visas tied to the operating entity, and the company itself registers for corporate tax and VAT like any other UAE business — eInvoicing accreditation sits alongside ordinary tax obligations rather than replacing them.
A documented operating plan that separates the accreditation renewal calendar from the routine trade licence renewal gives the business one calendar to manage instead of two that quietly diverge. Where the exchange role sits in one entity and software development in another — common in partner or white-label structures — treat that as a complex ownership question to resolve before either entity applies.
