On this page
As of September 2026, the UAE Federal Tax Authority maintains an official list of accredited Access Service Providers (ASPs) on its portal at tax.gov.ae. These are the only providers legally authorised to transmit e-invoices on behalf of UAE businesses under the mandatory e-invoicing framework. To find the current list, log in to the FTA portal and navigate to the e-invoicing section. The number of accredited providers has grown through 2026 as more technology companies completed the FTA's technical and compliance vetting process. Accreditation means the FTA has verified that a provider can receive, process, and relay invoices in the required PINT-AE format. It does not mean every accredited ASP is equally well-suited to your business, your ERP system, or your invoice volume. Reading the list correctly and knowing what questions to ask each provider is where the real work begins.
What the FTA Accredited ASP List Actually Tells You (and What It Doesn't)
The accredited ASP list published by the FTA is primarily a compliance filter. A provider's presence on the list confirms one thing: the FTA has tested that provider's ability to handle the technical transmission of PINT-AE-structured invoices and found it acceptable. Accreditation is a floor, not a ceiling. It tells you who is allowed to operate, not who will perform best for your specific situation.
What the list does not tell you:
- Whether an ASP has deep integration with your ERP or accounting software
- What their API documentation looks like and how mature it is
- How they handle invoice rejections, resubmissions, and error resolution
- What their uptime SLA is and what remedies exist if they miss it
- Whether they support the invoice volumes your business generates at peak periods
- What their pricing structure looks like for businesses at your transaction scale
Treating accreditation as the sole selection criterion is a shortcut that regularly causes businesses to re-platform within 12 months of going live.
How the PINT-AE Standard Shapes Every ASP Relationship
The PINT-AE specification is the structured data format that underpins UAE mandatory e-invoicing, derived from the international PEPPOL Invoice (PINT) standard and localised for UAE tax requirements. Every invoice transmitted through an accredited ASP must conform to this structure before the ASP will accept it.
This is the point most businesses underestimate when they read the accredited ASP list. The list implies a clean handoff: your business sends invoices, the ASP handles them. In practice, the handoff only works if your invoice data is already correctly structured and validated before it arrives at the ASP.
Most ERP systems, including widely used platforms that have not been specifically built for PINT-AE compliance, produce invoice data in their own internal formats. The gap between that format and what an accredited ASP expects is real and requires active work to close. Some ASPs offer mapping tools as part of their service. Others do not. Understanding which category your shortlisted ASP falls into is one of the first questions to resolve.
Reading the List: A Practical Framework for Comparison
When you look at the FTA accredited ASP list in 2026, you will see provider names and, in some cases, basic contact or categorisation information. The comparison work happens outside the list itself. Below is a structured way to evaluate the providers you shortlist.
| Evaluation Criterion | What to Ask the ASP | Why It Matters |
|---|---|---|
| ERP Integration | Do you have a native connector for my ERP, or API only? | Native connectors reduce integration time significantly |
| PINT-AE Mapping Support | Do you accept non-PINT-AE input and map it yourself? | Determines whether you need middleware upstream |
| Error Handling | How are rejected invoices surfaced and resolved? | Rejection workflows directly affect your DSO and compliance record |
| Audit Trail | What documentation do you provide per invoice transmission? | Required for VAT audit readiness |
| Volume Pricing | How does pricing scale above 1,000 invoices per month? | Many providers have steep tier jumps |
| Uptime SLA | What is your guaranteed uptime, and what is the remedy for breach? | Critical for businesses with time-sensitive invoicing cycles |
The single most revealing question you can ask a shortlisted ASP is how they handle a PINT-AE validation failure at the point of submission. A provider that can walk you through their exact rejection, notification, and resubmission workflow in concrete terms has clearly solved this problem before. A provider that gives a vague answer almost certainly leaves that burden with your team.
The Hidden Layer: Why ASP Selection Alone Is Not Enough
Choosing an accredited ASP is necessary but not sufficient. The gap that most businesses do not anticipate sits between their existing systems and the ASP's intake requirements.
Businesses using diverse or non-specialised ERP systems face the highest risk of invoice rejection at the ASP layer, because their systems were not built to produce PINT-AE output natively.
This is where a middleware platform becomes operationally relevant. A middleware layer sits between your ERP and your chosen ASP, ingesting invoices in whatever format your system produces, running validation checks against the PINT-AE structure, performing the mapping, and then handing a compliant invoice to the ASP with a full audit trail attached. The ASP never sees a malformed invoice, and your ERP does not need to be rebuilt.
This architecture also changes the long-term economics of ASP selection. When a middleware platform handles the integration logic, the ASP becomes a more interchangeable component. If the ASP you chose in 2026 becomes uncompetitive on pricing or reliability in 2027, migration is significantly less painful because the hard integration work lives in the middleware layer, not in a custom build tied to a specific ASP's API.
Kodowo, for example, is built specifically for this role in the UAE e-invoicing chain. It ingests invoices from ERP and accounting systems regardless of their native format, validates and maps them to the PINT-AE structure, and handles the ASP handoff with a full audit trail. The key design decision is ERP-agnosticism: Kodowo does not require your business to be on a specific accounting platform to get compliant output to your chosen ASP.
Criteria That Should Drive Your Final ASP Decision
Once you have eliminated providers that cannot handle your ERP's output, or have confirmed you will use a middleware layer that makes that question moot, the decision narrows to operational and commercial factors.
Technical Maturity of the API
Accredited ASPs vary considerably in how mature their developer documentation is. If your internal team or a third-party integration partner will be building the connection, the quality of the API documentation, the availability of a sandbox environment, and the responsiveness of technical support are concrete differentiators. Ask to see the API documentation before signing anything.
Transparency on Rejection Rates
A provider that tracks and shares data on invoice rejection rates at the FTA clearance stage is giving you genuinely useful information. A provider that cannot or will not share this data is either not tracking it or is not proud of the number. Either interpretation is worth noting.
Commercial Terms and Contract Flexibility
Several businesses that went live in early 2026 under the initial mandatory rollout phases signed ASP contracts before they had a clear view of their monthly invoice volumes. They then found themselves in pricing tiers that were significantly more expensive than anticipated, with multi-year lock-in. Short initial contract terms, or contracts with clear volume-based pricing bands you can verify independently, protect you during the first year of operation.
Local Support and UAE-Specific Compliance Knowledge
Some ASPs on the FTA accredited list are UAE-headquartered operations with deep local compliance knowledge. Others are international providers that added UAE accreditation to an existing global product. Neither category is automatically better, but UAE-specific providers tend to be faster to respond when the FTA issues updated technical guidance, which it has done multiple times through 2025 and 2026 as the mandatory framework matured.
Putting It Together: A Decision Sequence That Avoids Common Mistakes
The most expensive mistake in ASP selection is making the ASP decision before answering the middleware question. Businesses that approach the problem in this order tend to have cleaner outcomes:
- Audit your ERP's current invoice output format and confirm whether it can produce PINT-AE-compliant data natively.
- If it cannot, decide whether you will use a middleware platform to handle validation and mapping before the ASP receives anything.
- With the middleware question resolved, shortlist ASPs from the FTA accredited list based on the criteria above.
- Run a technical pilot with your top two candidates using real invoice data from your system before signing a contract.
- Confirm audit trail documentation, rejection workflows, and escalation contacts in writing before go-live.
The accredited ASP list is the starting point of this process, not the answer to it. Reading it correctly means understanding what it confirms and what evaluation work still belongs to you.
Frequently asked questions
- How often does the FTA update its accredited ASP list?
- The FTA updates the accredited ASP list on a rolling basis as new providers complete the accreditation process. Businesses should check the official FTA portal directly before finalising any ASP contract, since a provider that was accredited at announcement may have had its status changed. Never rely on a third-party copy of the list that lacks a clear date.
- Can I switch ASPs after going live with UAE e-invoicing?
- Yes, switching ASPs is technically possible, but it requires re-establishing API connections, re-validating your invoice formats, and ensuring your audit trail is preserved through the transition. Businesses that use an ERP-agnostic middleware layer find switching easier because the middleware absorbs most of the integration work, leaving the ASP as a more interchangeable component.
- Does my ASP handle PINT-AE mapping, or do I need to do that myself?
- Most accredited ASPs expect to receive invoices that are already structured in a valid PINT-AE format. If your ERP does not natively produce PINT-AE output, the mapping responsibility falls on you or a middleware platform before the invoice ever reaches your ASP. Assuming your ASP will fix upstream data problems is one of the most common and costly mistakes in UAE e-invoicing implementations.
- What is the difference between an ASP and a middleware platform like Kodowo?
- An accredited ASP is the FTA-approved channel through which your invoices are transmitted to and cleared by the authority. A middleware platform sits upstream of that, taking invoices from your ERP or accounting system, validating them, and mapping them to the PINT-AE structure required before the ASP can accept them. The two roles are complementary, not interchangeable.