UAE E-Invoicing ASP: How to Choose an Accredited Service Provider

What an ASP does, and what it does not

The UAE model is a Peppol five-corner exchange. Your system creates the invoice, your provider validates it against PINT AE and sends it to the buyer's provider, the buyer's provider delivers it, and the tax data goes to the Federal Tax Authority. Decision 168 of 2026 defines the electronic invoicing service as sending, receiving and exchanging e-invoices, e-credit notes and related documents under the Peppol framework. That is the whole of the accredited role.

Three things sit outside it. The provider does not decide whether your invoice data is complete; the 51 mandatory fields have to be present in the system that creates the invoice, and the provider rejects what fails validation. The provider is not, by virtue of accreditation, integrated with your software; integration is a product feature or a separate piece of work. And the provider is not your tax adviser; VAT treatment remains your responsibility.

Under the Decision the provider also verifies you as an end user with the Authority and onboards you, which is how your appointment is recorded. The Ministry's Central Register holds both the list of accredited providers and the list of end users each one has onboarded. In practice this means your choice of provider is a registered relationship, not a private software subscription, and changing provider later is a formal step.

Reading the Ministry of Finance list

The list is published on the Ministry's website and updated as providers are accredited. On 22 October 2026 it had two tables. The first listed 70 accredited providers in alphabetical order, each with a six-digit accreditation number, website and contact details. The second listed 3 providers that had completed pre-approval under the earlier Decision 64 of 2025 and were in the final production assessment, with full accreditation to follow on completion. The count will have moved by the time you read this, which is the point: the list, not a count, is the reference.

The mix of providers is wider than invoicing specialists. Alongside Peppol network operators and e-invoicing platforms, the list includes audit and tax advisory firms, a logistics group's digital arm, a utility-owned data company and several ERP and accounting software vendors. That breadth is why the accreditation alone is a weak filter: it establishes eligibility, not fit.

Is your ERP vendor on the list, and does it matter?

This is the most common question we hear, and the answer needs two parts. On the 22 October 2026 list, the accredited entities included SAP Middle East & North Africa LLC, Tally Software Solutions FZCO, Zoho Software Trading LLC and Focus Softnet. Odoo, Oracle, Microsoft, Intuit, Sage and Xero did not appear as accredited entities on that date.

The first part of the answer is that a vendor's presence on the list means that legal entity is accredited to provide the exchange service. It does not say which of its products or versions are connected to that service, whether an older on-premise version is covered, or on what commercial terms. A business on an older release of an accredited vendor's software should ask those questions directly rather than assume the accreditation reaches it.

The second part is that absence from the list is not a problem in itself. The mandate requires the invoice to reach the Authority through an accredited provider; it does not require the provider to be the vendor of the software that created the invoice. An Odoo, Dynamics, QuickBooks or custom-built system can pass its invoice data to any accredited provider through an integration, which is the arrangement most businesses with an established ERP will end up with. The decision then becomes which provider to integrate with, and the questions below apply.

What accreditation covers under Decision 168 of 2026

Ministerial Decision No. 168 of 2026 took effect on 1 October 2026 and repealed Decision No. 64 of 2025. The eligibility conditions carried over largely intact; the main structural change is that the earlier two-stage path of pre-approval followed by accreditation has been replaced by a single accreditation process with testing built into it, with a 30-day transition for providers that held pre-approval. For a buyer, the Decision is useful because it says exactly what the Ministry has already checked.

Accreditation is valid for two years from grant (Article 13). The provider applies for renewal at least 70 business days before expiry with evidence of continued compliance, including the ISO/IEC 27001 certification and the insurance (Article 15). The Ministry may also request information or records to monitor ongoing compliance (Article 14). A provider that misses the renewal window, or fails to fix the reasons for a rejected renewal, loses the accreditation at expiry and its links to the businesses it represents are revoked.

Termination is separate from expiry. Under Article 16 the Ministry may terminate an accreditation where the provider no longer meets the conditions, or where documented end-user complaints establish a breach of its obligations. The provider has to notify its clients within 5 business days and is delisted within the same period. A provider terminated for non-compliance cannot reapply for two years.

Two points follow for the buyer. First, the Ministry has already checked the security certifications, the financial standing and the insurance, so the due-diligence effort is better spent elsewhere. Second, because the accreditation can end, the contract needs an exit clause that covers it.

The Ministry's own selection questions

The Ministry of Finance published a short guidance note, Considerations for Selecting an Accredited Service Provider, in February 2026. It is a list of questions rather than a scoring method, grouped under experience, product ownership, integration and data, compliance and security, support and SLAs, pricing and scalability. The questions worth putting in writing to a shortlisted provider are these.

1. How long has the entity been a Peppol service provider, and when was it accredited in the UAE? The guidance asks both. A provider that joined Peppol for the UAE mandate has less exchange history than one operating in Europe or Singapore for years, which is not disqualifying but is worth knowing.
2. Is the product its own, or a third party's? Decision 168 allows a provider to run on a third-party product and to outsource operation of it. The guidance asks who provides support and maintenance. If support is subcontracted, ask who you call and what the response time is.
3. Does it integrate with your current ERP, accounting or invoicing system? The guidance asks about APIs, data formats and integration support. Ask for a reference client on your system and version, and ask whether the PINT AE field mapping is the provider's work or yours.
4. Where is the e-invoicing data stored, in the UAE or overseas? Decision 168 requires the product to comply with end-user hosting, storage, archival and residency requirements, which means the obligation can be yours to specify. Ask for the hosting location in writing.
5. Which certifications does it hold, and what are the security measures? ISO/IEC 27001 for the product and ISO 22301 are accreditation conditions, so expect both. Ask what else, and ask about the incident response process.
6. What are the support response times and the uptime SLA? An invoice that cannot be exchanged on the day it is issued is a compliance problem, not just an inconvenience. Ask for the SLA document, not a summary.
7. What is the pricing model, and what is outside it? Subscription, per document, tiered, or bundled with software. The guidance recommends that the 100 free invoices per year be written into the contractual terms. Ask for the full list of chargeable items.
8. How does the service scale, and what is the roadmap? Volume growth, a second entity, a second country. Peppol-based mandates are spreading across the GCC, and a provider already operating in Saudi Arabia or Oman may matter to a group.

Pricing: what the 100 free invoices cover

The commitment is specific. Article 9 of Decision 168 of 2026 has the provider declare that it will provide 100 free e-invoice exchange and reporting services per annum to each end user, counted from the date of that end user's agreement. The same condition existed under Decision 64 of 2025, so it is not new, but it is now the floor each accredited provider has agreed to. For a business that issues fewer than 100 invoices a year, the exchange and reporting fall inside that allowance.

The commitment covers the exchange and the reporting. It does not cover the integration that gets invoice data out of your system, the onboarding and end-user verification, any portal or software subscription, support beyond the exchange, or archival services. Those are legitimate charges, and they are where quotations from two accredited providers can differ by a wide margin for the same volume. The guidance note's own question, “are there any hidden fees or additional costs?”, is the one to ask.

Contract terms that follow from the Decision

Because accreditation is a two-year, renewable, terminable status, a few terms belong in any ASP contract regardless of the provider.

• Accreditation status and notice. A warranty that the entity is currently accredited, and an obligation to notify you of any renewal rejection, termination or voluntary withdrawal within the Decision's 5-business-day period or sooner.
• Exit and data return. What the provider returns, in what format, and within what period if the accreditation ends or you choose to move. Article 16 requires a withdrawing provider to offboard its end users before its accreditation is terminated; the contract should say what that offboarding includes.
• The 100 free documents, written in. The Ministry's guidance recommends this explicitly.
• Data location and retention. Where the data is hosted and for how long it is retained, consistent with the record-keeping period under UAE tax procedures law.
• Version and upgrade responsibility. If the provider supplies the ERP connector, who updates it when your ERP or PINT AE changes release, and at whose cost.
• Validation failures. How rejected documents are reported back to your system, and how quickly, since a rejected invoice has not been issued for compliance purposes.

A short implementation sequence for a business keeping its ERP

1. Confirm your phase and date. Revenue of AED 50 million or more: appoint by 30 October 2026, mandatory from 1 January 2027. Under AED 50 million: appoint by 31 March 2027, go live 1 July 2027. Dates per Decisions 243 and 244 of 2025 as amended by Decision 197 of 2026; re-check against the Ministry before planning around them.
2. Check your invoice data before you choose a provider. The 51 mandatory fields have to be present in the system that creates the invoice. Gaps in buyer TRNs, addresses by emirate, item descriptions and line-level VAT data are the usual findings, and they take longer to fix than the provider selection.
3. Shortlist from the current MoF list using the eight questions above, with the integration question first. Three providers is enough.
4. Get quotations at your real volume over three years, with the free allowance and each other charge itemised.
5. Sign with the contract terms above, then let the provider verify and onboard you with the Authority.
6. Connect, test and go live. Send real documents in the test environment, including a credit note and a foreign-currency invoice, before the first live exchange.

Frequently asked questions