In most UAE enterprises, FTA Decision No. 13 of 2026 will arrive on the tax manager's desk with a covering note: new VAT requirement — please handle. That routing is understandable, and it is the first mistake of the programme. Very little of what the Decision requires can actually be performed by a tax function — and a response designed as if it could will produce a false sense of completion.
Look at Who Performs the Acts
Walk through the obligations and ask, for each one, who in your organisation actually holds the facts and executes the step.
Meeting a natural-person supplier before the supply; collecting identity and incorporation documents; verifying that premises exist and match the claimed activity — that is vendor onboarding, owned by procurement. Assessing whether a price is off-market, and whether a supply falls within a supplier's licensed activities — procurement again, because that is where the market knowledge lives. Checking each incoming supply's circumstances, recalculating whether a supplier has crossed the aggregation thresholds, confirming the supplier's verification has not lapsed — accounts payable. Ensuring payment is electronic, to the supplier's own account, in its country of incorporation, with exceptions documented — treasury and payment operations. Building the rolling twelve-month aggregation, linking evidence to vendors and transactions, keeping records complete and retrievable to the standard FTA Decision No. 4 of 2026 sets — IT and data.
What remains with tax is the interpretation, the scoping decisions, the exception approvals, the defence-file design and the accountability for the outcome. Substantial — but it is the smaller share of the work by hours, and none of it lands inside the tax calendar. It lands inside procure-to-pay, on transaction time.
The Diffusion Problem
This creates a structural tension worth naming precisely: tax carries the consequence; other functions perform the acts. If verification lapses in procurement, or a payment control is bypassed in treasury, the cost arrives on the input tax line — years later, in a tax audit, addressed to the head of tax. Meanwhile the transaction that does the damage generates no alert anywhere: a vendor onboarded without a premises check, paying an off-market price through an intermediary, passes through a conventional P2P process without incident. Nothing fails visibly. That is exactly why it will be missed.
Goodwill does not solve this; allocation does. Somebody has to decide — explicitly, in writing — who is responsible for each measure, who is accountable for each outcome, what tax has the right to approve, and what happens when a check fails or a supplier refuses. It is no accident that Article 5(4) of the Decision requires exactly such a documented allocation as a statutory deliverable.
Five Dimensions, One Programme
Seen whole, Decision 13 is a five-dimensional problem. The tax reading determines what must be done and what a defensible position is. The technology stack determines whether controls can run at transaction speed rather than in spreadsheets. The data determines whether the in-scope population can even be identified — the rolling aggregation is a calculation most vendor masters cannot currently support. The process determines whether checks sit at the moments where the facts are available. And governance determines who owns it, who decides, and whether the programme still operates in its second year.
A response built in one dimension fails in predictable ways. A vendor questionnaire without the data layer cannot identify who should receive it. A screening tool without governance produces alerts nobody owns. A policy document without process design describes a control that does not operate. Each looks like progress; none survives contact with an audit.
What This Means for How You Start
The starting point is not a template and not a tool. It is a cross-functional scoping exercise with the authority to bind procurement, finance, treasury, IT and tax to one design — because the obligation will be discharged in their processes or not at all. Enterprises that have been through e-invoicing readiness will recognise the shape: what looks like a tax compliance requirement is, in substance, a business transformation with a tax consequence.
How Contiqa Can Help
Cross-functional obligations fail in the gaps between functions — and that is precisely where Contiqa Systems works. Contiqa designs Decision 13 programmes across all five dimensions, tax through governance, so that every measure has an owner, every owner has the facts, and the tax function is accountable for a control environment that actually exists. Contact Contiqa Systems to structure your response before 1 October 2026.
Track how UAE businesses are responding to this Decision as it takes effect — visit the Decision 13 Tracker on this site.
This article is general commentary on published legislation (working from the unofficial English translation) and does not constitute tax or legal advice. Obtain advice on your specific circumstances before acting.