UAE e-invoicing after Decision 168: what changes if your shortlisted ASP was only pre-approved before October

01What actually changed on 1 October 2026

The first practical change is simple: the UAE no longer uses the earlier pre-approval step as the buyer’s main signal. The Ministry of Finance said the new framework introduced by Decision 168 removed the pre-approval stage and moved to a direct accreditation process. Under that model, service providers must complete the defined assessment and testing requirements before accreditation is granted.

The second change is transitional, and this is where many shortlists broke. The Ministry also said providers that had received preliminary approval under Decision 64 of 2025 had up to 30 days from 1 October 2026 to complete accreditation requirements under the new framework. If they did not satisfy those requirements within that period, the preliminary approval would be terminated, and a new application would not necessarily be required unless the Ministry decided otherwise. In plain terms, a provider that looked viable in September 2026 could be a different risk in November 2026.

The third change is that buyer validation now has to rely on the current official list, not on historic sales material. The Ministry’s Accredited Service Providers page is expressly maintained under Article 13 of Decision 168 and is updated periodically. If a provider is not on that list now, your procurement and legal teams should treat that as a live issue, not a paperwork gap.

• Old question: were they pre-approved under the earlier framework?
• Current question: are they accredited now under Decision 168?
• Critical date: 1 October 2026, when Decision 168 took effect
• Transition window: 30 days from 1 October 2026 for previously preliminarily approved providers

02Is a pre-approved ASP still safe to contract

Sometimes yes, but only if you answer two separate questions. First, is the provider currently accredited under the post-October framework. Second, does its delivery model still fit your risk appetite, ERP landscape and go-live timetable.

A provider that was pre-approved earlier may well have completed the new accreditation path and be a good choice. The problem is that you cannot infer that outcome from an old shortlist deck, a proposal issued before October, or references to the Ministry’s earlier pre-approved list that still appear on the FTA e-invoicing page. That page still links to background material on pre-approved providers, but it also points businesses to the Ministry portal as the official source of current programme information.

So the right answer for a CFO is not ‘switch immediately’ or ‘stay put automatically’. It is ‘pause and re-validate’. If the provider is on the current accredited list, can show the accreditation number published by the Ministry, and your contract is updated to the current framework, the provider may still be perfectly safe to contract. If it is not on the current list, or the commercial team keeps talking about former pre-approval rather than present accreditation, you should assume more diligence is required before signing.

• Do not rely on a pre-October proposal alone
• Match the provider name against the current MoF accredited list
• Ask for the exact accreditation number used on the MoF listing
• Check whether the proposed operating model changed since your first shortlist review

03What to re-check in the contract, before legal says yes

Decision 168 matters because it sharpens accountability. The Ministry’s announcement says the flexibility introduced by Ministerial Decision No. 56 of 2026 remains in place, so service providers may use third party Peppol service provider products and may outsource development, operation or management of those products or elements of the service. But the same announcement also says the accredited provider retains full responsibility for compliance and service delivery.

That point should appear clearly in your contract. If the provider is effectively reselling another platform, your agreement still needs one accountable counterparty for compliance obligations, operational performance, incident management and regulatory updates. A weak contract will blur that line, especially where the vendor says its network, validation engine or Peppol access point is provided by a third party.

At minimum, ask legal and procurement to review whether the agreement now ties payment milestones and production acceptance to current accreditation, not past pre-approval. If your shortlist was built before October, old contract drafts may still use obsolete language. That is exactly the sort of issue that creates disputes later when onboarding slips or defects appear during ERP integration.

• State that the provider is currently accredited under the UAE framework
• Include the provider’s accreditation number and legal entity name
• Make the accredited provider contractually responsible even if third party components are used
• Require notice if accreditation status, subcontracting model or product stack changes
• Tie go-live acceptance to passed tests and agreed support readiness, not only to configuration completion

04What finance and ERP teams should re-test, even if the vendor has not changed

The accreditation framework changed, but your ERP integration risks did not disappear. In some cases they increased, because your team may now be working to an older scope agreed before the current framework was live. The Federal Tax Authority describes the UAE model as a decentralised 5-corner framework in which the service provider validates invoice fields against the UAE data dictionary before exchange over the Peppol network and reports tax data to the authorities. That means your test plan needs to prove more than transport, it needs to prove validation, exchange and reporting behaviour across realistic invoice cases.

Re-test master data mapping, tax logic and error handling first. If you are already in build, compare your original mapping workbook and interface assumptions against the current vendor design. This is where a good API integration review and a proper quality engineering pass help, because many failures are not legal questions, they are field-level mismatches, missing codes and broken exception flows.

If your contract is already signed or close to signature, freeze the minimum artefacts your ERP team must control before external testing expands. The sequencing in UAE e-invoicing contract signed in November 2026: what ERP teams must freeze first is useful here, especially if your finance lead thinks vendor onboarding alone will de-risk the programme.

• Positive test cases: standard tax invoices, credit notes, customer variations, item variations
• Negative test cases: missing mandatory fields, wrong tax identifiers, invalid code values, rejected transmissions
• Operational test cases: retries, duplicate prevention, failed acknowledgements, late corrections
• Business test cases: invoice cancellation paths, AP receipt handling, month-end surge volumes
• Control test cases: audit trail, user roles, evidence retention, reconciliation between ERP, ASP and tax reporting

05Questions to put to any ASP that was shortlisted before October

Buyers often ask whether a pre-approved provider became accredited. That is necessary, but not enough. You also need to know what changed inside the provider’s own delivery model during the transition. The Ministry’s amendments in May 2026 aimed to widen technical options and competitive pricing, and they allowed collaboration with third party providers. That creates flexibility, but it also means two providers with similar demos may have very different accountability and operational depth.

Ask direct questions and insist on documentary answers. A serious provider should be able to answer without deflecting into marketing language or generic Peppol explanations.

If you need independent help structuring that review, this sits naturally inside a governance and compliance workstream, because the task is to convert regulatory change into contract controls, test evidence and operating ownership.

• Are you currently listed on the Ministry of Finance accredited ASP page, under what legal entity name and accreditation number?
• Were you previously pre-approved, and if so, what changed in your product, operating process or subcontracting model during accreditation?
• Which parts of the service are your own, and which are provided by third parties?
• If a third party component fails compliance, transport or reporting, who owns the incident, remediation and customer communication?
• What exact ERP adapters, APIs or file interfaces are supported for our environment, not in theory but in production references?
• What evidence do you provide from testing: validation results, rejected message traces, acknowledgement logs, reconciliation outputs?
• What happens if your accreditation status changes after contract signature?
• What exit assistance do you provide if we must switch provider before or after go-live?

06How to decide whether to stay with the old shortlist or reopen it

Do not reopen the market by default. That burns time. Instead, score your existing shortlisted provider against four gates: current accreditation, contractual accountability, ERP fit and evidence from testing. If it passes all four, staying put is often the lower risk path. If it fails one of the first two gates, reopening the shortlist is usually justified.

For most CFOs, the highest-risk pattern is not an unaccredited provider in isolation. It is a provider that says accreditation is ‘in progress’, offers a contract that limits responsibility because another platform does the heavy lifting, and expects your ERP team to discover the gaps in testing. That combination increases schedule risk and leaves finance carrying the operational consequences.

If you do reopen the shortlist, keep the process narrow. Use the current Ministry list as the starting pool, ask the same accountability and testing questions of each vendor, and compare only on current-state evidence. Do not let a provider win because it was advanced in a pre-October sales cycle. If you need to stabilise the selection and delivery path quickly, a short technology consulting or assurance exercise can help your team separate accreditation risk from integration risk without restarting the whole programme.

• Stay with the shortlist if the provider is accredited now, contractually accountable, technically fit and test-ready
• Reopen the shortlist if current accreditation is absent, ambiguous or dependent on future milestones
• Reopen the shortlist if accountability is split across unnamed third parties
• Reopen the shortlist if the provider cannot define a realistic test plan and support model for your ERP and finance operations

07The practical buyer position in November 2026

As of Friday, 6 November 2026, the safest buyer position is clear. A provider that was only pre-approved before October is not automatically unsafe, but pre-approval on its own is no longer a safe basis for contract award. Decision 168 took effect on 1 October 2026, removed the pre-approval stage, and gave previously preliminarily approved providers 30 days to meet the new accreditation requirements. That means the transition window has already passed.

So your action now is operational, not theoretical. Check the provider against the current Ministry list. Update the contract to reflect current accreditation and single-point accountability. Re-test the ERP to ASP path against current validation and exchange behaviour. Then decide.

If you want a second pair of eyes on the controls, test scope or vendor wording, SyncTrix can support the review as an engineering and compliance task, especially where ERP integration, vendor accountability and delivery readiness all overlap.