The UAE E-Invoicing ASP List: Every Pre-Approved Provider, and How to Read It (2026)

At some point this year, someone is going to tell your finance team to "appoint an ASP from the Ministry of Finance (MoF) e-invoicing ASP list before the deadline." The list is public. The deadline is fixed. The penalty for missing it is AED 5,000 a month. On paper it reads like a procurement chore: open the list, pick a name, sign.

The list currently holds 39 names. Every one of them clears the exact same compliance bar. So the instruction that sounds like a five-minute job is the part most businesses get wrong, because the document that tells you who is allowed to operate tells you nothing about who fits.

What the list actually is

The Ministry of Finance publishes one official list of pre-approved eInvoicing service providers, under Article 15 of Ministerial Decision No. 64 of 2025, which sets the eligibility criteria and accreditation procedure for service providers. That decision is the rulebook for who gets on the list and how.

Here is the distinction that almost every other article blurs. "Pre-approved" is not the same as "accredited." Pre-approval means a provider has met the requirements to operate, pending final accreditation. Final accreditation is granted separately under Article 16, on successful completion of accreditation testing. A name on the list is necessary. It is not, on its own, sufficient. Treat accreditation status as a production requirement and ask about it directly.

What an ASP even does

An Accredited Service Provider is not optional middleware you could route around. It is the only authorised channel between your business and the UAE's e-invoicing infrastructure. Businesses do not connect to the Federal Tax Authority (FTA) directly. Every in-scope invoice passes through an ASP.

The UAE runs a Peppol-based decentralised model, often called the five-corner model. Your system hands invoice data to your ASP, which validates it against the PINT-AE standard (the UAE's structured XML format), routes it across the Peppol network to your customer's ASP, and reports the tax data to the FTA in parallel. A PDF emailed to a client is not an e-invoice. Neither is a scan or a paper original. Only structured data exchanged through an ASP in the approved format counts.

The list: 39 pre-approved providers (June 2026)

Below is the full MoF pre-approved list as published, alphabetical, current as of June 2026. The Ministry updates it periodically, so treat this as a snapshot and verify against the live page before you act.

For the authoritative, always-current version with full contact details, see the Ministry of Finance page: Pre-Approved eInvoicing Service Providers.

Why the list won't choose for you

That table gives you almost nothing to decide on, by design. Every provider meets the same floor: PINT-AE validation, Peppol routing, near-real-time FTA reporting, status confirmations, record retention. None of it separates one from another. The difference between a good fit and an expensive mistake lives entirely above the floor. We have covered how to judge that separately, in Demanding More from Your ASP. This article is the map of who exists. That one is how to judge them.

A buyer-side way to read the list

You do not need a consultant to do a first pass. You need a short set of questions you can hold every shortlisted provider against.

1. Accreditation status, not just pre-approval. Ask where the provider is in the Article 16 process and whether they are cleared for production. This is the single question most buyers skip.
2. ERP fit. A native, proven connector to your accounting system costs far less in integration time than a bridge built for the first time on your project.
3. Your own data readiness. Most rejected invoices are dirty master data: a wrong TRN (Tax Registration Number), a missing buyer Peppol ID, a tax classification that does not match the supply. At AED 100 per rejected invoice, a sloppy data set becomes a recurring tax.
4. Security, uptime, and support. You are routing every invoice through this provider for years. Ask about uptime, outage handling, and who answers when an invoice fails at month-end.
5. Pricing model. Per-document, tiered, or flat. The right structure depends on your invoice volume, and the cheapest headline rate is not always the cheapest outcome.
6. Cross-border footprint, if it applies. If you have KSA operations or a GCC supply chain, a provider already live across multiple Peppol jurisdictions can handle those flows without a second vendor.

The timeline, and the cost of getting it wrong

The mandate arrives in phases, set out in Ministerial Decision No. 244 of 2025.

The large-business appointment deadline moved from 31 July to 30 October 2026 in May, while go-live stayed at 1 January 2027. That gap is not slack; it is the room onboarding and testing eat. A voluntary pilot opens on 1 July 2026. For now the mandate covers B2B and B2G; B2C is out of scope until a later phase. Penalties are set out in Cabinet Decision No. 106 of 2025:

Voluntary participants are not penalised until they fall into mandatory scope. The headline figures look survivable in isolation, but the real risk is a botched go-live where invoices reject at volume and the daily and monthly fines stack while your finance team firefights an integration that was never ready. The fine is the visible cost. The operational mess behind it is the expensive one.