Accounting, Payroll, CFO & E-Invoicing · UAE E-Invoicing
ASP Selection Advisory
The Federal Tax Authority's e-Invoicing programme is built on a decentralised Continuous Transaction Control (DCTC) model — businesses do not submit invoices directly to the FTA.
Chartered Accountants · Dubai · Since 1986
ASP Selection Advisory is the structured evaluation and selection of the Accredited Service Provider(s) a UAE business will use to comply with the Federal Tax Authority's e-Invoicing mandate. Under the UAE's e-Invoicing framework, invoices are not submitted to the FTA directly by taxpayers; instead, the model follows a five-corner Continuous Transaction Control design in which the seller's ERP or accounting system connects to an FTA-Accredited Service Provider, that ASP validates and structures the invoice to the PINT-AE (Peppol International, UAE localisation) data standard, exchanges it with the buyer's own ASP over the Peppol network (the same decentralised exchange infrastructure used in Peppol-based e-invoicing jurisdictions elsewhere), and both ASPs report the transaction data to the FTA. Every taxable person within scope of the mandate must therefore contract with, integrate to, and rely on at least one accredited ASP — and in practice, many groups with multiple entities, ERPs, or business lines end up evaluating whether one ASP serves the whole group or whether different entities need different providers.
The FTA publishes and maintains an accreditation framework and a list of Accredited Service Providers who have passed its technical, security, and compliance certification. Accreditation confirms an ASP is permitted to operate in the exchange chain — it does not mean every accredited ASP is a good fit for every business. ASPs differ materially in their pricing model (per-invoice, subscription, or volume-tiered), the ERPs and accounting platforms they natively connect to (SAP, Oracle NetSuite, Microsoft Dynamics, Zoho Books, Tally, and dozens of mid-market and regional systems all have varying levels of native versus middleware-dependent connectivity), their support for the specific invoice types a business issues (standard tax invoices, credit and debit notes, self-billing, summary invoices for high-volume retail, and cross-border transactions), their archiving and record-retention capability against the UAE's document-retention rules, and their operational maturity — uptime history, error-handling and rejection-resolution workflow, and whether they have live production experience with UAE-based taxpayers rather than only pilot or sandbox engagements.
Selecting the wrong ASP creates real operational exposure. An ASP that cannot cleanly connect to your ERP forces a costly middleware build or manual re-keying of invoice data — precisely the manual step the mandate is designed to eliminate, and precisely the step most likely to introduce data errors that trigger validation failures. An ASP with weak support responsiveness leaves your invoicing process exposed the moment a validation exception, a Peppol delivery failure, or an FTA reporting error occurs, and under a continuous transaction control model, invoicing effectively cannot proceed if the ASP link fails. And because e-Invoicing readiness sits alongside — not instead of — ongoing VAT compliance under Federal Decree-Law No. 8 of 2017, an ASP selection that is not properly aligned to how your business actually issues invoices, credit notes, and self-billed documents can quietly create VAT reporting inconsistencies that only surface at FTA review.
At PNPC Global, ASP selection sits at the intersection of technical, commercial, and tax advisory work. We do not resell ASP software or receive referral commissions from any provider — our evaluation is built on the same independent scoring framework we use across the FTA's accredited provider list, weighted to each client's actual ERP environment, invoice volume and type mix, group structure, and internal IT resourcing. The output is a documented, defensible selection with the commercial and technical rationale in writing — a record that matters if your board, your group finance function, or your auditor later asks why a particular ASP was chosen over the alternatives.
When ASP Selection Advisory is the right engagement
Your business falls within the scope of the UAE e-Invoicing mandate and has not yet contracted with an FTA-Accredited Service Provider
You operate more than one legal entity, ERP system, or business line in the UAE and need to determine whether a single ASP can serve the group or whether entity-specific providers are required
Your current ERP or accounting platform (SAP, Oracle, Microsoft Dynamics, Zoho Books, Tally, or a bespoke system) has unclear or unconfirmed native connectivity to the ASPs on the FTA's accredited list
You have received competing sales pitches from multiple ASPs or software resellers and need an independent, non-commissioned evaluation before committing to a multi-year contract
Your invoice volume, invoice-type mix (standard invoices, credit/debit notes, self-billing, summary retail invoices), or cross-border transaction pattern is complex enough that a generic ASP comparison will not surface the real differentiators
You are already committed to a specific ERP transformation or migration project and need ASP selection sequenced correctly against that timeline rather than bolted on afterward
Your group has UAE entities alongside entities in other Peppol-based e-invoicing jurisdictions and wants to evaluate whether a common ASP relationship is commercially and technically viable across markets
Your internal IT or finance team lacks the bandwidth or specialist knowledge to evaluate ASP technical documentation, pricing structures, and integration scope independently
You want the ASP decision documented with a clear evaluation trail — scoring criteria, shortlist rationale, and selection basis — for board approval, group finance sign-off, or future audit reference
When a lighter-touch approach may suffice
Your ERP vendor already has a single, pre-integrated ASP partnership specific to your platform with no meaningful commercial alternative worth evaluating — in that case a focused contract and scope review, rather than a full market evaluation, is proportionate
You are a very small, single-entity business with simple, low-volume invoicing and a common accounting platform that already has clear, well-documented ASP connectivity — a lighter comparison of two or three shortlisted providers may be sufficient rather than a full weighted evaluation
You have not yet confirmed whether your business is within the current scope or timeline of the e-Invoicing mandate — that scoping question should be resolved first through an e-Invoicing Impact Assessment before ASP selection begins
Your business already has a functioning, contracted ASP relationship that is working technically and commercially, and the only question is a routine renewal rather than a re-evaluation of alternatives
You want PNPC to simply recommend 'the best ASP' without input on your ERP landscape, transaction volumes, or invoice types — a generic recommendation without that context is not a defensible selection basis and is not something we will provide
The decision has already been made at group or parent-company level with no scope for a UAE-specific alternative, and the only remaining task is technical integration support rather than provider selection
You are looking for the ASP itself to build or customise your ERP's invoicing workflow — that is an ERP implementation project; ASP selection advisory evaluates and selects the provider, it does not replace ERP configuration work
ASP Selection Advisory vs related UAE e-Invoicing and accounting engagements
| Feature | ASP Selection Advisory | UAE e-Invoicing Impact Assessment | ASP Integration Support | VAT Functional Gap Analysis |
|---|---|---|---|---|
| Primary purpose | Evaluate and select the FTA-Accredited Service Provider(s) best suited to the business | Determine mandate scope, timeline, and readiness gaps at a high level | Technically implement and go live with the chosen ASP connection | Assess whether existing VAT processes align to e-Invoicing-driven data requirements |
| Typical sequencing | After impact assessment confirms scope; before integration begins | First — establishes whether and when the mandate applies | After ASP is selected — builds the live technical connection | Can run in parallel with or after ASP selection |
| Core deliverable | Scored ASP shortlist, selection recommendation, and documented rationale | Readiness report covering scope, gaps, and a phased roadmap | Live, tested ERP-to-ASP connection and go-live sign-off | Gap report on VAT data, invoice fields, and process alignment |
| Depth of ERP involvement | Assesses ERP compatibility as a selection criterion, not a build task | High-level review of ERP and systems landscape | Deep, hands-on technical configuration and testing | Reviews VAT-relevant data fields within the ERP |
| Commercial focus | Central — pricing models, contract terms, and total cost of ownership compared across ASPs | Limited — commercial impact is noted but not compared across vendors | Minimal — commercial terms are already agreed by this stage | Not a commercial exercise — focused on process and data accuracy |
| Who typically needs it | Any business about to contract with an ASP for the first time, or reconsidering an existing one | Any business unsure whether, when, or how the mandate applies to them | Businesses that have already selected an ASP and need it connected | Businesses wanting to confirm VAT processes will hold up once e-Invoicing goes live |
| Best paired with | e-Invoicing Impact Assessment beforehand; ASP Integration Support afterward | ASP Selection Advisory as the immediate next step | SOPs, Governance & Controls to embed the process once live | ASP Selection Advisory and Integration Support as part of the same programme |
These five engagements form a natural sequence for most UAE businesses preparing for e-Invoicing: assess impact and scope, select the ASP, close VAT/data gaps, integrate technically, then embed governance and controls. PNPC scopes each stage independently so clients who already have work done in one area are not charged to repeat it.
How PNPC runs an ASP Selection Advisory engagement for a UAE business
| # | Stage & What PNPC Does | CA Advice Generic IT Consultants Rarely Give | Timeline |
|---|---|---|---|
| 1 | Scoping call — confirm mandate applicability, entity structure, ERP landscape, and whether an e-Invoicing Impact Assessment has already been completed | We check whether the client's group structure means multiple ASPs might genuinely be needed (different ERPs per entity, different transaction volumes) before assuming a single-provider answer is correct | Day 1 |
| 2 | ERP and systems landscape review — document every system that currently issues or receives invoices, including any legacy or manual processes running alongside the core ERP | We specifically ask about shadow processes — invoices raised outside the main ERP by a branch, a project site, or a subsidiary — since these are the connections most often missed in a pure IT-led selection | Week 1 |
| 3 | Invoice volume and type profiling — quantify monthly invoice volume, the mix of standard invoices, credit/debit notes, self-billing arrangements, and any summary or high-volume retail invoicing patterns | Pricing models across ASPs diverge sharply once volume and invoice-type mix are known — a per-invoice model that looks cheap at low volume can be materially more expensive at scale, and vice versa | Week 1 |
| 4 | FTA-Accredited Service Provider longlist compilation — the current FTA accreditation list is reviewed and filtered against the client's ERP, volume, and jurisdictional footprint | We track which ASPs have live UAE production experience versus sandbox-only or newly accredited status, since operational maturity matters as much as accreditation itself | Week 1–2 |
| 5 | Technical connectivity assessment — for each shortlisted ASP, native connector availability to the client's specific ERP version is confirmed directly with the provider, not assumed from marketing material | We push providers to confirm connectivity in writing for the client's exact ERP version and module set, since a generic 'SAP-compatible' claim can still mean a costly custom build for a specific configuration | Week 2–3 |
| 6 | Commercial comparison — pricing structure, contract term, minimum commitment, support SLA, and total cost of ownership are compared on a standardised basis across the shortlist | We normalise pricing models (per-invoice, tiered, flat subscription) onto the client's actual projected volume so the comparison reflects real cost, not headline rate | Week 2–3 |
| 7 | Weighted scoring and shortlist — technical fit, commercial terms, support responsiveness, operational track record, and archiving/retention capability are scored against criteria weighted to the client's priorities | We keep the weighting model transparent and adjustable so the client can see exactly why one ASP scores above another, rather than receiving a single unexplained recommendation | Week 3 |
| 8 | Reference and due diligence checks — where practical, existing UAE clients of shortlisted ASPs are referenced for real-world integration experience and support quality | We ask specifically about validation-error resolution turnaround and Peppol delivery failure handling, since these operational details rarely appear in vendor sales material | Week 3–4 |
| 9 | Selection recommendation and rationale document — a written recommendation with the scoring matrix, shortlist comparison, and clear rationale, suitable for board or group finance approval | We document the rejected alternatives and why, not just the winner — this protects the client if the decision is questioned later by an auditor, a new CFO, or a parent company | Week 4 |
| 10 | Contract and SLA review support — key commercial and service-level terms in the proposed ASP contract are reviewed against the client's operational needs before signature | We flag data ownership, exit/migration terms, and liability allocation clauses specifically, since these are the terms most often overlooked when a contract is reviewed only for price | Week 4–5 |
| 11 | Handover to integration — the selection package is handed to the client's IT team or to PNPC's ASP Integration Support engagement, with the technical connectivity findings carried forward so nothing is re-investigated | We ensure the connectivity and volume assumptions used in selection are the same figures used in integration scoping, avoiding a mismatch between what was evaluated and what gets built | Week 5 |
A single-entity business with one ERP and a clear invoice profile can typically complete ASP selection in three to four weeks. Groups with multiple entities, ERPs, or jurisdictions take longer, since each additional system or entity requires its own connectivity and volume assessment before a group-wide or entity-specific recommendation can be made responsibly.
Trade licence and Certificate of Incorporation for each UAE entity in scope
Group structure chart showing all UAE entities, their ERPs, and any overseas parent or sister entities also affected by e-Invoicing-equivalent mandates
VAT registration certificate(s) and TRN(s) for each entity
List of entities currently issuing or receiving invoices, including any entity not yet formally confirmed as within e-Invoicing scope
Name, version, and hosting model (on-premise, cloud, hybrid) of every ERP or accounting system used to issue or receive invoices
List of any middleware, integration platform, or custom API layer already in use between the ERP and external systems
Details of any legacy or manual invoicing processes running alongside the core ERP (branch-level, project-site, or subsidiary-level)
IT contact and technical documentation access for each ERP, to support the connectivity assessment stage
Monthly and annual invoice volume by entity, covering standard tax invoices, credit notes, and debit notes
Details of any self-billing arrangements currently in place with suppliers or customers
Summary or consolidated invoice patterns for high-volume retail, F&B, or point-of-sale operations, where applicable
Cross-border invoicing volume and pattern, including exports and any transactions with entities in other e-invoicing-mandated jurisdictions
Copies of any proposals, quotes, or draft contracts already received from ASPs or software resellers
Details of any existing software or middleware vendor relationships that could affect ASP connectivity decisions
Current accounting software support and maintenance contract terms, to check renewal timing against the e-Invoicing selection timeline
Name and role of the internal IT and finance leads responsible for the e-Invoicing programme
Any board or group-level approval requirements or budget constraints affecting ASP selection
Prior e-Invoicing Impact Assessment output, if already completed, including scope confirmation and identified readiness gaps
How the ASP relationship is managed after selection, across the e-Invoicing compliance lifecycle
| Phase | Triggered By | PNPC CA Guidance | Risk If Ignored |
|---|---|---|---|
| Selection & Contracting | ASP shortlist finalised and recommendation approved | PNPC supports contract and SLA review before signature, checking data ownership, exit terms, and liability allocation alongside price. | A contract signed on price alone can leave the business locked into unfavourable exit terms or unclear liability if the ASP link fails. |
| Technical Integration | ASP contracted, integration project begins | Connectivity assumptions used during selection are carried into integration scoping so nothing is re-investigated, and a realistic testing window is agreed before go-live. | Selection findings not carried forward into integration lead to rework, delays, and a mismatch between what was evaluated and what is actually built. |
| Go-Live & Parallel Run | Mandate effective date or internal readiness milestone | A parallel run period, validating ASP-processed invoices against the ERP's own records before fully relying on the ASP path, is strongly recommended before decommissioning any manual fallback. | Going live without a parallel run risks invoicing disruption if validation failures or Peppol delivery issues surface only under real transaction volume. |
| Ongoing Operational Monitoring | Continuous, post go-live | PNPC reviews ASP performance — validation error rates, delivery failures, support ticket turnaround — against the SLA agreed at contracting. | An underperforming ASP that is not monitored against its SLA erodes invoicing reliability quietly until a material disruption forces an unplanned re-selection. |
| Volume or ERP Change | Business growth, new entity, or ERP migration | ASP fit is reassessed whenever transaction volume changes materially or the underlying ERP is upgraded or replaced, since the original selection criteria may no longer hold. | An ASP chosen for a prior ERP or volume profile can become the wrong fit silently, especially on pricing, as the business scales. |
| Contract Renewal | ASP contract term nearing expiry | PNPC reviews whether the original selection rationale still holds or whether the market (including newly accredited providers) warrants a fresh comparison before automatic renewal. | Automatic renewal without review can lock in outdated pricing or miss materially better alternatives that have entered the accredited list since the original selection. |
| Regulatory Update | FTA updates the e-Invoicing framework, PINT-AE standard, or accreditation requirements | PNPC monitors FTA updates and flags any change requiring ASP-side action, contract amendment, or reassessment of the selected provider's continued suitability. | An ASP that does not keep pace with an FTA framework update can put the taxpayer's own compliance position at risk, even though the taxpayer did not cause the gap. |
| Multi-Entity Expansion | New UAE entity incorporated or new ERP deployed within the group | The existing ASP relationship is assessed for extension to the new entity before defaulting to a separate, uncoordinated selection process. | Uncoordinated ASP selection across group entities creates unnecessary cost duplication and inconsistent invoicing data standards across the group. |
ASP selection is not a one-time decision that can be filed away once signed. The relationship needs periodic review against SLA performance, volume changes, ERP changes, and the evolving FTA accreditation landscape, since e-Invoicing compliance depends on the ASP link continuing to function reliably for the life of the mandate.
What is an Accredited Service Provider (ASP) under the UAE e-Invoicing mandate?
An ASP is an entity certified by the Federal Tax Authority to sit in the invoice exchange chain between a taxpayer's ERP or accounting system and the buyer's own ASP, validating invoices against the PINT-AE data standard, exchanging them over the Peppol network, and reporting transaction data to the FTA. Under the UAE's decentralised Continuous Transaction Control model, taxpayers do not submit invoices to the FTA directly — every in-scope invoice must pass through an accredited ASP.
Do we need to select an ASP even if our ERP vendor already recommends one?
You should still evaluate the recommendation rather than accept it by default. ERP vendors often have a commercial partnership with a specific ASP, which can be a genuinely good fit, but the recommendation is rarely independent of that commercial relationship. An independent comparison against your actual volume, invoice-type mix, and pricing sensitivity confirms whether the vendor-recommended ASP is actually the best fit or simply the path of least resistance for the vendor.
Can we use more than one ASP for different entities in our group?
Yes, and for groups with genuinely different ERPs, transaction volumes, or business lines across entities, using more than one ASP can be the right answer rather than forcing a single provider across an incompatible landscape. The decision should be made deliberately, weighing the operational simplicity of a single group-wide relationship against the better technical or commercial fit of entity-specific providers.
How is ASP pricing typically structured, and how do we compare providers fairly?
ASPs commonly price on a per-invoice basis, a tiered volume subscription, or a flat monthly/annual fee, sometimes with a minimum commitment. A per-invoice price that looks cheapest in isolation can be more expensive than a subscription model once your actual projected volume is applied, and vice versa. A fair comparison normalises every shortlisted ASP's pricing against your specific projected volume and invoice-type mix, not the provider's headline rate.
What happens if our chosen ASP cannot connect natively to our ERP?
Where native connectivity does not exist, the options are typically a middleware or API layer built to bridge the ERP and the ASP, a manual or semi-manual data export/import process (which reintroduces the error risk the mandate is meant to eliminate), or selecting a different ASP with confirmed native connectivity. Confirming connectivity before contracting, rather than after, avoids discovering this gap during integration when switching providers is far more disruptive.
How long does ASP selection typically take?
For a single-entity business with one ERP and a reasonably well-understood invoice profile, ASP selection typically takes three to four weeks from scoping to a documented recommendation. Groups with multiple entities, ERPs, or jurisdictions take longer, since each additional system requires its own connectivity and volume assessment before a responsible recommendation can be made.
Does PNPC receive referral fees or commissions from any ASP?
No. PNPC's ASP Selection Advisory is an independent evaluation service. We do not resell ASP software, and our recommendation is based on the client's own weighted scoring criteria — technical fit, commercial terms, operational track record, and support quality — rather than any commercial arrangement with a provider.
What should we check about an ASP's operational track record, not just its accreditation?
Accreditation confirms an ASP meets the FTA's technical and security certification — it does not guarantee operational maturity. Worth checking specifically: how long the provider has been live with UAE taxpayers in production (versus sandbox or pilot only), typical validation-error resolution turnaround, Peppol delivery failure handling, uptime history, and whether the provider has genuine experience with your specific ERP and invoice-type mix rather than only similar-sounding platforms.
What is PINT-AE and why does it matter for ASP selection?
PINT-AE is the UAE's localisation of the Peppol International invoicing data standard — the structured data format every e-Invoicing-compliant invoice must conform to before it can be validated and exchanged. An ASP's ability to correctly map your ERP's invoice data into PINT-AE format, including UAE-specific fields such as VAT treatment and TRN details, is a core technical evaluation criterion, not a peripheral one.
Can we switch ASPs later if our first selection turns out to be a poor fit?
Yes, but switching is more disruptive than getting the initial selection right, since it involves re-establishing technical connectivity, migrating any archived invoice data the ASP holds, and managing a transition period without disrupting live invoicing. Exit and data-portability terms should be reviewed in the original contract precisely so a future switch, if needed, is not unnecessarily difficult or costly.
Does ASP selection need to happen before or after our e-Invoicing Impact Assessment?
After. An Impact Assessment first confirms whether, when, and to what extent the e-Invoicing mandate applies to your business, and surfaces the ERP, process, and data gaps that need addressing. ASP selection then proceeds with that scope and readiness picture already established, rather than selecting a provider before understanding what the business actually needs it to do.
How does ASP selection interact with our existing VAT compliance processes?
The ASP handles invoice validation, exchange, and FTA reporting, but the underlying VAT treatment applied to each invoice — the rate, the exemption or zero-rating basis, the place-of-supply determination — is still the taxpayer's responsibility under Federal Decree-Law No. 8 of 2017. An ASP does not correct incorrect VAT treatment in your source data; it validates that the data is structurally complete and correctly formatted. A VAT Functional Gap Analysis alongside ASP selection confirms the underlying VAT data feeding the ASP is itself accurate.
What internal resources do we need to commit during ASP selection?
At minimum, a finance lead who understands current invoicing volume and processes, and an IT contact who can speak to the ERP's technical configuration and respond to connectivity questions from shortlisted ASPs. For larger or multi-entity businesses, input from each affected entity's finance or operations lead is needed to accurately profile invoice volume and type across the group.
What does PNPC deliver at the end of an ASP Selection Advisory engagement?
A written selection recommendation including the shortlisted ASPs evaluated, the weighted scoring matrix used, the commercial and technical comparison, and a clear rationale for the recommended provider — including why alternatives were not selected. This document is suitable for board or group finance approval and stands as a defensible record of the decision basis.
PNPC ASP Selection Advisory vs a typical ASP-led or reseller-led selection
| Dimension | PNPC ASP Selection Advisory | Typical ASP or Reseller-Led Selection |
|---|---|---|
| Independence | No referral fees or resale commissions from any ASP | Often commission-linked to the specific provider being recommended |
| Evaluation basis | Weighted scoring across technical, commercial, and operational criteria specific to your business | Sales-led comparison, typically favouring the provider running the pitch |
| ERP connectivity confirmation | Written, ERP-version-specific confirmation obtained before recommendation | General compatibility claims often taken at face value |
| Commercial modelling | Pricing normalised against your actual projected volume and invoice mix | Headline pricing compared without adjustment for your real usage pattern |
| VAT and tax alignment | Reviewed alongside your VAT compliance position, not treated as a purely IT decision | Rarely connects the ASP decision back to underlying VAT data accuracy |
| Documentation | Full scoring matrix and rationale, including rejected alternatives, for board or audit reference | Often limited to a single recommended provider with little comparative record |
| Continuity | Same firm available for impact assessment, integration support, and ongoing monitoring | Engagement typically ends once a sale is closed |
What the PNPC package includes
- 01
ERP and systems landscape review across all in-scope UAE entities
- 02
Invoice volume and type profiling, including credit notes, self-billing, and summary invoicing
- 03
FTA-Accredited Service Provider longlist filtered to your ERP and jurisdictional footprint
- 04
Written, ERP-version-specific connectivity confirmation obtained from each shortlisted ASP
- 05
Normalised commercial comparison across pricing models and projected volume
- 06
Weighted scoring matrix covering technical fit, commercial terms, operational track record, and support quality
- 07
Reference and due diligence checks with existing UAE clients of shortlisted providers, where practical
- 08
Documented selection recommendation with full rationale, suitable for board or group finance approval
- 09
Contract and SLA review support, covering data ownership, exit terms, and liability allocation
- 10
Handover package for ASP Integration Support, carrying forward all connectivity and volume findings
- 11
Alignment check against your existing VAT compliance position and data accuracy
- 12
Access to PNPC's e-Invoicing Impact Assessment and SOPs, Governance & Controls services as a coordinated programme
Talk to PNPC before you sign an ASP contract — an independent, documented selection now is far cheaper than a mid-mandate switch later.
Jurisdiction
Free zone, mainland & offshore
Ready to get started?
Tell us about your requirement — a UAE specialist responds within 24 hours.