It is the first question every finance director asks about FTA Decision No. 13 of 2026, and it deserves a careful answer: if we perform every prescribed measure, document everything properly, and a fraud somewhere in the supply chain later comes to light anyway — is our input tax deduction protected?
The honest answer has three parts, and each part matters to how you design your response.
Part One: Compliance Removes the Deeming Route
Article 54 bis(3) of the VAT Law operates in one direction. It provides that a Taxable Person who did not verify its supplies in accordance with the Authority's prescribed measures shall be considered to have been required to be aware of a connection to Tax Evasion. It contains no converse limb providing that a person who did verify is deemed innocent of constructive knowledge.
So performing and documenting the Decision 13 measures closes the deemed route into a constructive-knowledge finding. What remains is the ordinary test: the Authority would need to establish, on the actual circumstances of the supply, that the business should have been aware of the connection — and even then, refusal under Clause 2 is discretionary rather than automatic. Two features of the wider framework are relevant here. Article 51 of the Tax Procedures Law places the burden of proof in cases of Tax Evasion on the Authority. And nothing in the framework suggests a business that took genuine, documented care will be treated as if it had not.
Part Two: The Protection Operates Through the Evidence
Decision 13 contains no provision making compliance conclusive — it is not drafted as an automatic statutory shield, and it would be an overreach to describe it as one. The protection it offers is evidential: a complete, contemporaneous, good-quality verification file is the strongest protection the framework makes available, and in the ordinary case — where the business genuinely did not know and nothing in the circumstances pointed the other way — it should preserve the deduction.
This is exactly how the equivalent protection works in systems that have litigated the question for twenty years. In the European Union, the Court of Justice held in Kittel and Recolta Recycling (2006) that traders who take every precaution that can reasonably be required of them must be able to rely on the legality of their transactions without risking their right to deduct. In the United Kingdom, the Court of Appeal in Mobilx (2010) confirmed that the authority bears the burden of proving the trader's state of knowledge. In all three systems, the practical rule is the same: the file is the defence, and the quality of the file decides the outcome.
Part Three: The File Cannot Substitute for Attention
There is a boundary, and international experience marks it clearly. A completed set of forms will not assist a business that filed them while the circumstances of the transaction pointed plainly the other way. A price far below market with an explanation no reasonable buyer would accept sits inside the constructive-knowledge test whatever the paperwork says. The UK Court of Appeal put it memorably in Mobilx: even a trader who has asked appropriate questions is not entitled to ignore circumstances whose only reasonable explanation is fraud.
The instruction that follows is the same in every jurisdiction: build the file, keep it contemporaneous, and never let a completed procedure substitute for actually reading the transaction in front of you.
What This Means for Your Design
Three design consequences follow directly from the legal position.
Evidence quality is the objective, not form completion. The question a reviewer will ask years from now is not whether a checklist existed but whether the record shows questions asked, answers considered, and anomalies addressed. Those are different deliverables.
Contemporaneity is non-negotiable. Several of the required facts — a meeting before the supply, an address verified on a date, twelve-month risk indicators — exist only at the moment of the transaction. A file assembled retrospectively is a different, and much weaker, thing.
Judgement has to stay in the loop. Because the residual test is about what the circumstances would have told a reasonable business, the programme cannot be pure automation. The workable model concentrates human judgement on the exceptions while systematic checks clear the ordinary population — and the design question is where that line sits for your business.
Getting those three things right — at realistic cost, across a real vendor base, before 1 October 2026 — is precisely the problem worth taking seriously now.
How Contiqa Can Help
Contiqa Systems designs Decision 13 responses around the question that will actually be asked: can this business show, years after the fact, that it neither knew nor should have known? From defence-file design to evidence architecture and the governance that keeps it alive, Contiqa builds the position you will one day need to stand on. Contact Contiqa Systems to test how your current process would hold up.
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 and case law (working from the unofficial English translation of UAE instruments) and does not constitute tax or legal advice. Obtain advice on your specific circumstances before acting.