The UAE Ministry of Finance extended in May 2026 until 30 October the deadline for companies with revenue above AED 50 million to contract an Accredited Service Provider (ASP). However, the effective mandatory date of the regime remains fixed at 1 January 2027. Barely two months between signing with the provider and being in real production.
That gap is what deserves close attention. And it’s what is currently shaping the real pace of projects already underway.
Why the Extension Gives Less Margin Than It Seems
Many companies have read the extension as a breath of fresh air. That’s a misreading.
The regulator has not softened the regime. It has recognized that the provider market was not ready to absorb the concentrated demand expected for July, and has moved that peak three months forward. The project’s operational timeline has not changed.
A company that signs with its ASP in October begins the integration project with less than twelve weeks until mandatory compliance. And that assumes three optimistic scenarios that rarely occur simultaneously:
- That the ERP responds on schedule
- That the Peppol schema configuration works on the first try
- That the reporting to the Federal Tax Authority produces no incidents in pre-production
For a company with multiple entities, different ERPs per subsidiary, or non-consolidated invoicing processes, that’s too much optimism at once.
Why the Project Is Not an IT Project
A significant portion of the delays we’re seeing in implementations already underway don’t come from technical issues. They come from how the project is framed internally within the company.
Companies that treat this as an IT matter discover late that it affects cross-functional areas: tax, purchasing, sales, treasury, and master data. Each has its own decision cycle, and any of them can block progress.
The prior checklist that should be closed before sitting down with an ASP:
- Inventory of operation types (B2B, B2G, intercompany, cross-border)
- Real state of master data for customers and suppliers
- Technical compatibility of the ERP with Peppol schemas
- Commercial contracts with invoicing clauses that may require amendment
Without this map in place, implementation moves blindly, deadlines shift, and negotiation with the provider starts at a disadvantage because the company cannot describe its own scope.
The Ministry’s Pilot: The Underused Lever
Since April 2026, the UAE Ministry of Finance has maintained a voluntary pilot of the five-corner model that allows companies to exchange Peppol invoices before the mandatory launch.
It’s probably the most underused tool of the entire process. It allows companies to:
- Detect ERP incompatibilities in real conditions
- Validate tax mapping with real volume
- Test reporting to the FTA without penalties if something fails
- Surface incorrectly mapped tax codes, XML validation rejections, or electronic signature issues
The incidents that appear in the pilot are exactly those that in production generate fines and payment blocks. Companies that join now arrive at January 2027 with the system validated and the operation broken in. Those that wait for the fourth quarter will be testing in production, with real customers.
Coordination with the Parent Company: The Blind Spot for International Groups
For Spanish-speaking companies with group structure — parent in the country of origin and subsidiary operating in the Emirates — there is an additional layer that often stays out of the initial conversation with the local ASP.
If the Emirati entity issues invoices to the parent or to other group subsidiaries, Peppol compliance in the UAE has to coordinate with the e-invoicing regime of the country of origin. In Spain, for example, Verifactu is already in force, and mandatory B2B invoicing under the Ley Crea y Crece is on the near horizon. In other Spanish-speaking countries there are equivalent systems with their own technical timelines.
They are different systems, with different technical rules and calendars. They are not interoperable by default.
Resolving both compliance regimes in silos — each subsidiary contracting on its own — is a decision that pays for years: cost duplications, recurring intercompany reconciliation issues, incorrectly applied withholdings, and consolidated reports that don’t match.
The reasonable alternative is to design the tax and technological architecture from the group level, with a joint perspective, before each subsidiary signs with its provider.
What We’re Seeing in the Market
Several patterns worth considering are emerging in recent weeks:
- Upward pressure on ASP implementation fees
- Early signs of acceptance filters by providers with the largest market share
- Companies with complex structures being rejected or postponed by providers who can’t keep up
The extension to 30 October will provide administrative margin for companies running late. The project itself, however, still takes as long as it took: around twelve months well-executed.
The Real Decision Window
For a company operating in the UAE that hasn’t yet started the process, the reasonable window to have an ASP signed and an internal plan closed is closing in the next six to eight weeks.
After that, three things get worse at the same time:
- The implementation cost rises
- The availability of experienced consultants drops
- The bulk of the effort coincides with the fiscal year-end, the worst time to put finance into a critical project
How Can We Help You?
If your company is within the AED 50 million threshold and hasn’t yet defined how to address compliance, at Setup in the UAE we can help you review your specific situation: current state of the project, ASP selection, coordination with the parent company, and internal project design.
Speak with an expert → Calculate the costs of operating in the UAE →
Sources: Ministry of Finance UAE, Federal Tax Authority (FTA), official communications on the UAE e-invoicing regime.
