How to appoint an Accredited Service Provider

Every business in scope of the UAE Electronic Invoicing System has to appoint an ASP. There is no self-service route, no direct connection to the Federal Tax Authority (FTA), and no exemption for businesses that already run good invoicing software. Corner 2 of the five-corner model is an accredited provider, and it is not optional.

What surprises people is that the appointment is not something the provider does to you. The Ministry of Finance's guidance is specific: the onboarding process is initiated by the person or government entity, through EmaraTax, not by the ASP.

The order of operations

1. Work out your date. If your annual revenue is AED 50 million or more, you appoint by 30 October 2026 and go live on 1 January 2027. Below that threshold, you appoint by 31 March 2027 and go live on 1 July 2027. Government entities appoint by 31 March 2027 and go live on 1 October 2027. The October 2026 date replaced 31 July 2026 in a May 2026 amendment to Ministerial Decision No. 244 of 2025.

2. Do the gap analysis before you talk to anyone. Identify the categories of electronic invoice your transactions actually require, and the data points each one needs. Then confirm your accounting, ERP or invoicing system can produce them. This is not a formality. It is the step that determines whether the rest of the project takes six weeks or six months, and it is the step most often skipped because it produces no artefact anyone can put in a board pack.

3. Choose from the Ministry's list. ASPs are accredited by the Ministry under Ministerial Decision No. 64 of 2025. The Ministry maintains a Central Register: the list of ASPs, and the list of end users onboarded by those ASPs. As of the Ministry's May 2026 announcement, 32 service providers had been approved, with more in the final stages of accreditation. That number has almost certainly changed. Check the register rather than a directory, including ours.

4. Contract. You finalise the contract and fulfil all commercial obligations with the ASP before onboarding. Not during. The sequence is deliberate.

5. Get a TIN, if you do not have one. Your Peppol participant identifier is your tax identification number. If you are registered with the FTA for any tax type, your TIN is the first ten digits of your TRN. If you are in scope for e-invoicing but not required to register for any tax, you still register with the FTA to obtain a TIN. If you are part of a tax group, your TIN is derived from your own TRN, not the group representative's.

6. Onboard via EmaraTax. The account administrator of the taxable person initiates onboarding to the contracted ASP's system through the FTA's EmaraTax platform. You then create a profile on the ASP's system and obtain your Peppol participant identifier through them.

7. Agree the operational detail. How invoice data reaches the ASP. How you receive confirmation messages for exchange and for tax data reporting. How you receive inbound invoices issued to you by suppliers. Where data is hosted and what security requirements apply. Each of these is a line on the Ministry's own readiness checklist, which is a fair signal that each is a place where implementations stall.

8. Test. End to end, in both directions, including failure paths. The gap between appointment and go-live exists for this and for nothing else.

9. Go live, and agree a governance model first. Specifically, how errors get resolved during and after go-live, and who does what when an invoice is rejected.

One ASP, and what that constrains

A person or government entity onboards with a single ASP for all their e-invoicing requirements. Tax group members each onboard individually, each with their own TIN and their own Peppol participant identifier, and different group members may sit with different ASPs.

This single-provider rule is worth thinking through before you sign. Your ASP becomes the sole path between your invoices and the tax authority. Switching later means re-onboarding through EmaraTax, and it means whatever your contract says about exit.

What to ask an ASP, and what the answers tell you

Most procurement checklists for this ask about price per invoice and uptime. Both matter. Neither is where the risk sits.

"Which UAE legal entity is accredited?" Accreditation attaches to a specific legal entity on the Ministry's Central Register. Group companies, regional arms and local partners are not interchangeable. Ask for the exact registered name and confirm it against the register yourself. If a provider is reluctant to give you a name you can look up, that is your answer.

"Are you accredited, or pre-approved?" These are distinct stages under MD 64 of 2025, and the language in the market is loose. Some providers on the pre-approved list describe themselves as accredited. Ask for the current status in writing.

"Who generates the UUID?" Per the Ministry's responsibility table, the ASP does. Each electronic invoice gets a UUID to guarantee uniqueness and prevent duplication. If a provider tells you that is your job, they have not read the framework.

"Who looks up the buyer's participant identifier?" The ASP performs the lookup. But gathering the buyer's Peppol participant identifier in the first place is the supplier's responsibility, not the ASP's. Providers who blur this line will hand you a data problem in month one and call it a customer issue.

"What happens to an invoice the receiving ASP rejects?" In the five-corner model, the recipient's ASP validates and confirms electronically to your ASP. On failure, it confirms the failure to your ASP and to the FTA, and no tax data is reported. You want to know exactly how that failure surfaces in your systems, how quickly, and who is expected to act.

"How do we get invoice data to you?" This is the question that determines whether the project is an integration or a workaround. Some providers accept a structured API payload. Some want a file drop. Some want you to type into their portal. If your invoices originate in Zoho Books, QuickBooks Online, Xero, Microsoft Dynamics 365 Business Central, or a spreadsheet, the honest answer to "can you connect to that" is the difference between a two-week onboarding and a permanent manual process. This is the problem Nazm exists to solve: we connect those systems to an accredited provider, so the answer is an integration rather than a workaround.

"Can you handle our awkward transactions?" Self-billing. Disclosed agent billing. Margin scheme. Continuous supplies. Exports. Deemed supplies. Reverse charge. Free zone movements. Summary invoices. Each has a defined treatment in PINT AE and each is a place a thin implementation falls over. If your business does any of them, ask for a worked example in XML, not a slide.

"How do you handle industry-specific fields?" You are not permitted to add optional fields of your own into PINT AE. If you need something the specification does not carry, the Ministry's instruction is to discuss it with your ASP. That means the answer to this question is a genuine differentiator between providers rather than a formality.

The traps

The appointment deadline is not the project deadline. Extending the appointment date to 30 October 2026 without moving the 1 January 2027 go-live compressed the integration window for first-wave businesses from about five months to about nine weeks. A business that appoints on 29 October has bought itself a very expensive Christmas.

Accreditation is not capability. An ASP is accredited to transmit and report. Nothing in accreditation certifies that they can read your accounting system, map your chart of accounts, or handle a margin scheme line. Those are commercial capabilities, and they vary enormously.

Third-party delivery is now explicitly allowed. The Ministry amended MD 64 of 2025 in May 2026 to enable the provision of technology solutions in collaboration with third-party providers, with the stated aim of letting national companies partner with international ones and transfer technical know-how. Practically, this means the entity that is accredited and the entity that builds the software you actually touch may be different, by design and with the Ministry's blessing. Ask who is doing what, and ask where liability sits when a mapping error produces an invalid invoice.

Your compliance obligation does not transfer. The Ministry's responsibility table is blunt about this. ASPs are engaged by suppliers to carry out exchange and reporting activities, but the compliance obligation remains with the supplier, or with the buyer in the case of self-billed invoices. Calculating every invoice value is yours. Exchanging and reporting is yours. You have outsourced the mechanism, not the duty. Read the indemnity clause with that in mind.

Ongoing changes are your job. Register for VAT, join a tax group, leave one, deregister, close down: each is a change you must promptly tell your ASP about, handled through EmaraTax reverification or offboarding. Failure to notify the ASP of changes to data registered with the FTA carries AED 1,000 per day of delay under Cabinet Decision No. 106 of 2025.

If you are still choosing

Two useful heuristics.

Ask each shortlisted provider to send you a schema-valid PINT AE XML document for the single most complicated transaction your business does, with your data in it. Some will do it in a day. Some will not do it at all. This tells you more than any reference call.

Then ask what happens on 2 January 2027, when several thousand businesses go live in the same week and something in the network is slow. Ask about the system failure notification obligation, which is theirs to help you meet and yours to be fined for missing.

---

Sources

• Ministerial Decision No. 64 of 2025 on the eligibility criteria and Accreditation procedure for Service Providers under the Electronic Invoicing System, as amended
• Ministerial Decision No. 244 of 2025, as amended
• Cabinet Decision No. 106 of 2025, annexed table
• UAE Electronic Invoicing Guidelines V1.0, Ministry of Finance, 23 February 2026, sections 3, 5.2, 9, 12.2 and Appendices 1 and 2
• Ministry of Finance, "Ministry of Finance announces targeted amendments to eInvoicing system decisions," 10 May 2026
• Ministry of Finance Central Register of Accredited Service Providers

Verified against primary Ministry of Finance sources on 9 July 2026. Provider accreditation status changes. Confirm on the Central Register before you sign anything.

Related

• The penalty-free window
• The 2026 to 2027 e-invoicing timeline
• UAE e-invoicing penalties, explained properly
• PINT AE explained

Tools

• Accredited Service Provider directory
• Peppol participant lookup