How to Choose an Accredited Service Provider for UAE E-Invoicing: Questions, Contract Terms and ERP Connection
Every UAE business in scope for e-invoicing must contract an Accredited Service Provider, and the largest ones had to do so by 30 October 2026. Here is how to pick one, what the contract should say, and why the ERP side is the bigger piece of work.
Choosing an Accredited Service Provider is the one e-invoicing decision with a hard regulatory date. Businesses with revenue of AED 50 million or more had to appoint one by 30 October 2026, and failure to do so falls under Cabinet Decision No. 106 of 2025, at AED 5,000 per month or part month of delay. Yet the ASP contract is the smaller half of the job. This guide covers what an ASP does, what to ask before signing, and why the ERP integration decides the outcome.
Key takeaways
- An ASP validates, transmits and receives structured e-invoices on the Peppol-based five-corner network and passes tax data to the FTA. It does not fix your ERP data.
- AED 50M+ businesses had to appoint an ASP by 30 October 2026. Phase 2 businesses should contract one well before 1 July 2027.
- Ask ten questions before signing: ERP connectors, sandbox, pricing model, uptime and support hours, data residency, buyer-side receiving, archive, onboarding time, group entities and exit terms.
- Pricing is typically per invoice, tiered or flat. The right model depends on your invoice volume and how it varies.
- The ERP integration, master data and credit-note handling take more effort than the ASP contract itself.
What an ASP does, and what it does not
The UAE model is decentralised. There is no single government portal that every invoice is uploaded to. Instead, a supplier's ERP sends a structured invoice in the PINT AE format (a UBL-based XML profile) to the supplier's ASP. The ASP validates it, delivers it to the buyer's ASP over the Peppol network, and reports the tax data to the Federal Tax Authority in near real time. The buyer's ASP delivers the invoice to the buyer. That is the five-corner model.
So an ASP is a validation, transport and reporting layer. It will reject an invoice that fails the schema or business rules, and tell you why. It will not generate correct invoice data in the first place. Customer TRNs, Peppol identifiers, tax codes, credit-note references and document numbering all come from your ERP. If those are wrong, the problem lands back with your finance team.
The deadline, and who it applies to
Phase 1 of the mandate starts on 1 January 2027 for businesses with revenue of AED 50 million or more, and those businesses were required to appoint an ASP by 30 October 2026. Phase 2 starts on 1 July 2027 for everyone else. The scope is B2B and B2G transactions, covers VAT-registered and non-VAT-registered businesses for in-scope supplies, and includes many free zone companies. B2C is out of scope for now.
If you are in Phase 1 and have not yet contracted an ASP, sign one now and document the decision. If you are in Phase 2, use the time well: selection takes two to four weeks when done properly, and the integration that follows takes longer. Businesses that adopt voluntarily ahead of their mandatory date are excluded from the penalty regime, which is a real incentive to move early.
The 10-question ASP checklist
Every accredited provider has passed the same Ministry of Finance accreditation, so accreditation itself does not differentiate them. These questions do.
- Which ERP connectors do you have, and are they live? Ask for a named connector for your platform, whether Odoo, SAP Business One, NetSuite, Dynamics 365 or another. "We have an API" is not the same as a maintained connector with customers on it.
- Is there a sandbox we can test against before go-live? You need to send real invoice shapes, including credit notes and multi-currency documents, and see the validation results before anything is live.
- What is the pricing model: per invoice, tiered or flat? Get the full schedule, including setup fees, minimums, overage rates and what counts as a document (do rejections and credit notes count?).
- What are your uptime commitments and support hours in UAE time? Month-end falls on your calendar, not theirs. Ask for a written service level and an escalation route that works on a Thursday afternoon in Dubai.
- Where is our data stored and processed? Confirm data residency, backup locations and who can access invoice content. Your auditors and some customers will ask.
- Do you handle buyer-side receiving? You will receive e-invoices from suppliers as well as send them. Ask how inbound documents reach your ERP and your accounts payable workflow.
- How long are invoices archived, and how do we retrieve them? Tax records must generally be kept five years after the tax period, longer for real estate. Check whether the ASP archive meets this and whether you can export everything in bulk.
- What is the realistic onboarding time? Ask for the steps from signature to first live invoice, and who on your side has to be involved at each step.
- How are group entities handled? Each legal entity needs its own registration and Peppol identifier. Ask whether one portal and one contract covers the group, and how pricing works across entities.
- What are the exit terms? If you switch ASP, you need your archive, your identifiers and a clean handover. Get the notice period, data export format and any exit fees in writing.
What the contract should cover
The contract should state the service level, support hours, data residency, archive period, per-entity scope, exact pricing schedule and exit provisions. It should name the ERP connector and who maintains it when the ERP or the PINT AE specification changes. A short appendix listing the invoice types you issue (standard, credit notes, debit notes, self-billed) avoids surprises later.
Pricing models compared
Three models are common. None is universally better; the right one depends on how many documents you issue and how steady that volume is.
| Model | How it works | Suits | Watch for |
|---|---|---|---|
| Per invoice | A unit charge for each document transmitted or received | Low or unpredictable volumes, early-stage groups | Whether rejections, credit notes and inbound documents are charged; cost rises with growth |
| Tiered | Bands of included volume, with a step up at each threshold | Mid-volume businesses with seasonal peaks | Overage rates above the band; being pushed into a higher tier by a few busy months |
| Flat | A fixed annual or monthly fee regardless of volume | High, stable volumes and multi-entity groups | Minimum terms, per-entity add-ons and what happens if volume drops |
Ask each shortlisted provider to price the same scenario: your actual document count from the last twelve months, split by entity and by inbound and outbound. That makes the quotes comparable.
Why the ERP integration is the larger job
In our projects, the ASP contract takes days. The ERP work takes weeks. The ERP has to produce a complete, valid PINT AE document for every in-scope transaction, which means customer master data with correct TRNs and Peppol identifiers, product tax codes mapped to the UAE VAT categories, credit notes that reference the original invoice, and a reliable transmission with status tracking so finance can see what was accepted and what was rejected.
Readiness is six jobs: confirm scope and date; choose and contract the ASP; clean master data; make the ERP produce compliant structured invoices and handle credit notes; integrate ERP to ASP and test end to end; train the team and set controls. The ASP choice is one of six. On Odoo and most mid-market platforms, the remaining five are where the project time goes, and where a UAE e-invoicing readiness review pays for itself by finding the data and process gaps before the first rejection does.
A practical sequence
Confirm your phase. Shortlist two or three ASPs with a live connector for your ERP. Send the ten questions and the same pricing scenario to each. Run a sandbox test with real invoice shapes. Sign, then start the ERP and master data work immediately, because that is the critical path to go-live.
Not sure which ASP fits your ERP, or whether your invoices will pass once it is connected?
Book a readiness review with a senior Kaido consultant. We map your invoice flows, shortlist ASPs that have a connector for your ERP, and tell you exactly what has to change before go-live.
Book a discovery call