Ten weeks is enough time to run a procurement; it is not enough time to discover, after signing, that nobody inside the business owns the tax determination the ASP will transmit.
The appointment deadline for UAE businesses with revenue of AED 50,000,000 or more now falls on 30 October 2026, following the amendment of Article 5 of Ministerial Decision No. 244 of 2025 by Ministerial Decision No. 56 of 2026. The go-live date of 1 January 2027 was not moved. Businesses below that threshold appoint by 31 March 2027 and go live by 1 July 2027; Government Entities appoint by 31 March 2027 and go live by 1 October 2027. Much of the market has read the extension as breathing room on a vendor selection. It is better understood as a governance decision wearing a procurement disguise.
Every Deadline Names the Taxpayer
Ministerial Decision No. 244 of 2025 places the obligation to appoint an Accredited Service Provider on the Registrant, not on the provider market. Each of the dates above names the taxpayer as the party carrying the obligation. The ASP performs the transmission; the taxpayer carries the deadline.
That asymmetry holds after go-live. Federal Decree-Law No. 8 of 2017 makes the Registrant liable for its VAT position — the accuracy of the tax treatment, the completeness of the invoice record, and the defensibility of the classification behind every line. Nothing in Ministerial Decision No. 243 of 2025, Ministerial Decision No. 244 of 2025 or Ministerial Decision No. 64 of 2025 shifts that liability to the Service Provider. Accreditation establishes that a provider is authorised to participate in the UAE Electronic Invoicing ecosystem. It establishes nothing about whether the enterprise’s tax positions flowing through that provider are right.
The Boundary the Contract Cannot Move
Every ASP relationship divides responsibility along a boundary, whether the contract states it explicitly or not. On one side sits technical responsibility: conformant transmission of Electronic Invoices and Electronic Credit Notes through the PEPPOL Interoperability Framework, uptime, PINT-AE schema and schematron validation, security of data in transit and at rest, and, where the ASP performs it, verification of End Users with the Authority. On the other side sits tax responsibility: the classification applied to each transaction, the accuracy of the master data feeding the invoice, the evidence trail behind every position, and the defensibility of the whole under audit.
PINT-AE schematron validation confirms structure. The fields are present, the codes come from the permitted lists, the document parses. It says nothing about whether the tax category code reflects the correct VAT treatment, whether the Emirate-level place-of-supply determination is accurate, or whether a reverse-charge transaction has been correctly identified. A provider whose platform passes every conformance test will transmit a structurally perfect, substantively wrong invoice without a single validation failure, because validation was never designed to catch that class of error. The Green Dashboard Paradox™ names the pattern: a technically green status masking an incorrect tax treatment.
The accountability boundary therefore runs through the enterprise’s own control environment rather than through the service agreement. No indemnity clause converts a tax underpayment into the ASP’s liability before the Federal Tax Authority; the assessment lands on the Registrant regardless of how cost is allocated between the parties. What a well-drafted contract can do is align commercial consequence with the risk each party actually controls.
Which Part of Ten Weeks Is Compressible
The procurement itself compresses. Requests for proposal run in parallel, scoring accelerates, legal review can be resourced. What does not compress is the internal decision about who owns tax determination, who owns exception response when a transmission fails or a counterparty rejects, and who owns the evidence behind each position once the programme structure dissolves. Those questions have to be answered by named people with standing authority, and answering them takes longer than signing.
Settle them before the contract. An enterprise that names those owners first will write a better contract, because it will know precisely which obligations it is asking the provider to carry and which it was always going to carry itself. This holds in every PEPPOL-based regime that routes exchange through certified providers; the UAE framework simply puts a date on it.