An Accredited Service Provider transmits your e-invoices to your customer and the Federal Tax Authority. Choosing one comes down to six things: the transaction types it supports, who builds the connection to your system, how rejections come back, where your data sits, what onboarding asks of you, and how the price moves with volume.
What an Accredited Service Provider does, and what it does not
In the UAE model your invoice does not travel from you to your customer. It goes from your system to your accredited provider, from there to your customer’s provider, and to the Federal Tax Authority at the same time. That is the five-corner shape, and it is why the provider is a licensed participant rather than a piece of software you install. UAE e-invoicing on Odoo sets out what the mandate requires and where Odoo stands today.
Here is the part that decides how much the choice matters: a provider transmits what you hand it. It does not clean your customer records, decide which tax category a product belongs to, or turn a free-text emirate into a code. Around sixty providers are accredited and you may appoint exactly one, so the decision is real — but it is a decision about transmission, validation feedback and the commercial relationship, not about whether your data is ready.
Which is why selection and preparation run side by side rather than one after the other. Companies that treat the appointment as the project discover late on that their invoices fail on master data, and the provider is the wrong party to complain to. If you want the sequencing argument at length, the 30 October deadline post covers the order to do things in.
The six questions that actually separate providers
Price is the easiest thing to compare and the least useful. These six are harder to ask and they are what you will care about a year in.
Does it support every transaction type you actually use?
There are eight transaction types in the mandate — free zone, exports, deemed supplies, reverse charge, margin scheme, summary invoicing, continuous supply and agent billing — and each one changes what is mandatory on the document. A provider whose onboarding covers the standard domestic sale beautifully may have thin support for the one type that happens to be a large share of your revenue. Work out which types you use first, from your own invoices rather than from memory, then ask each provider to confirm support for exactly those.
Who builds and owns the connection to your system?
Some providers offer a connector for your ERP, some expect an integrator to build against their interface, and some will quote you both without being clear which you are buying. Ask directly: is there a supported connector for your version, who maintains it when either side changes, and if it is built bespoke, does the work belong to you. A connection built as a thin layer that generates and validates the document inside your system before anything leaves it is worth more than one welded to a single provider’s interface, because it survives you changing your mind.
What happens when an invoice is rejected?
This is the question most often skipped and most often regretted. A rejection needs to arrive somewhere a human will see it, in language that names what failed, attached to the invoice it belongs to. Ask what the rejection message looks like, whether it reaches your system or only a portal, whether anyone is notified, and who is responsible for the invoice until it is accepted. A provider that hands you a rule number and no context has moved the work to you without saying so.
Where does your invoice data sit, and for how long?
You have a retention obligation measured in years, and the archive is part of what you are buying. Ask where the data is stored, who can read it, what happens to it if you leave, and whether you can export the whole archive in a form that is useful without that provider. If data residency is a genuine constraint for your group — some are, most are not — raise it at the first call rather than the last, because it narrows the list quickly. Companies with a hard requirement to keep records inside their own estate sometimes end up looking at on-premise systems for the surrounding processing too, which is a bigger conversation than e-invoicing.
What does onboarding actually require from you?
Onboarding runs through EmaraTax and there are steps only you can take, with a tax identity only you control. Ask what the provider needs from you, in what order, how long their side typically takes once they have it, and what the common hold-ups are. Then put that against your own deadline rather than theirs. A provider who cannot describe the hold-ups has either not done many or is not telling you.
How does the price behave when your volume changes?
Per-document pricing is normal and reasonable. What matters is the shape: what a credit note counts as, what a rejected-and-resubmitted invoice counts as, whether there is a floor you pay in a quiet month, and what happens the month a big customer doubles its orders. Ask for the price at your current volume and at twice it. If the second number is uncomfortable to produce, you have learned something useful.
Not sure which provider fits your Odoo?
Send us your entity list, your transaction types and your invoice volume. We will tell you which questions will decide the answer for you, and which providers are worth the call.
Book the Two-Day AssessmentHow to run a shortlist when the time is short
If you are in the first wave the appointment deadline is 30 October 2026 and go-live is 1 January 2027, with the Ministry of Finance having said no further extensions will be granted. That is not long enough for a leisurely procurement, and it is long enough to avoid picking blind.
Start from your own invoices, not from a provider list. Pull ninety days of real invoices and credit notes. Count the transaction types. Note the currencies, the free-zone customers, the intercompany lines, the channels that issue an invoice without going through finance. That document is your requirement, and it takes a day.
Then cut the list on fit, not on marketing. Three or four providers that clearly support your transaction types and your system is a better shortlist than ten that might.
Ask the six questions above on a call, in that order. Written answers to the rejection question and the exit question are worth asking for. Whether a provider will give you those in writing tells you as much as the answers.
Run the data clean-up in parallel from day one. TRNs on VAT-registered customers, the emirate as a code on every address, classification codes on products, units of measure mapped to the standard list, every tax mapped to exactly one category. None of that depends on which provider you choose, and all of it decides whether the first real invoice passes.
Appoint, then validate with real documents. Sample invoices pass. Your actual ones are where the failures live, and you want to find them well before go-live rather than after it.
The selection mistakes that cost the most later
Buying on price per document. It is the number easiest to compare and rarely the number that hurts. The cost that bites is a rejection process your finance team cannot work with, or an integration nobody will own in eighteen months.
Letting the provider decide your scope. Scope is per legal entity, and a group can have one entity in the first wave and three in the second. Work that out yourself, with your tax adviser, before anyone quotes.
Treating the appointment as the finish line. It is the start of the integration and the data work, not the end of the project.
Forgetting the channels outside finance. A point-of-sale till, a second system in a subsidiary, a billing script somebody wrote — if it issues an invoice, it is in scope. Find them before you design the integration, not after. If one of those systems is customer-facing, the same mapping problem shows up in your CRM and customer records, which is usually where the missing TRNs actually live.
Stacking the upgrade on top. If you have a postponed version upgrade or a chart-of-accounts restructure waiting, this is not the moment. Do the mandate on what you run today. The question of what Odoo supports today goes into why.
Where we would tell you to slow down
If you are not in the first wave, your appointment date is later and there is a reasonable case for doing the data work now and the provider decision afterwards. Paying for a connection before your customer records can pass validation means paying twice for the same project, and we have said so to companies who wanted to start immediately.
If your invoice volume is small and your transaction types are simple, you may not need the integration conversation at all in the first round — a provider’s own interface, used by a person, is a legitimate answer for a while. It becomes the wrong answer as volume grows, and you should know which side of that line you are on rather than assume.
And if a supplier quotes you a price before asking which legal entities are in scope, which transaction types you use, what is customised in your system and which channels issue invoices, that quote is a guess. The number will change. Better to find that out now.
Being straight about our own position
We are not an Accredited Service Provider and we do not intend to become one. We work on the integration side, connecting systems to the provider a company chooses, and we also do ongoing Odoo support and maintenance. So we have an interest in integration work existing, and you should weigh what we say with that in mind and get a second view.
What we will not do is tell you which provider to appoint as though there were one right answer. There is not. There is a right answer for your transaction types, your volume, your system and your constraints, and the honest version of this advice is a list of questions rather than a recommendation.
Nothing here is tax or legal advice. The mandate’s detail belongs to the Ministry of Finance and the published PINT AE specification, and your thresholds, scope and filing obligations belong to your own tax adviser.
Where to start
Pull ninety days of invoices and count your transaction types. That one exercise tells you more about which provider fits than any comparison table, and it is the same work the integration will need anyway. Then ask three providers the six questions, and start the master data clean-up the same week — because that part is yours whichever way the selection goes.