Every obligation in FTA Decision No. 13 of 2026 ultimately rests on one unglamorous asset: the vendor master. Which suppliers are in scope, which have crossed the AED 100,000 and AED 375,000 thresholds, whose verification has lapsed, which risk indicators have fired — every one of those questions is answered from vendor and transaction data, or not answered at all.
And here is the uncomfortable truth most UAE enterprises will discover in the first week of scoping: the vendor master was never built to answer questions like these.
The Conditions That Break the Calculation
None of the following are exotic. They are the ordinary state of vendor data in businesses that have grown, merged, migrated ERPs, or simply operated for a decade:
Duplicate vendor records — the same supplier under two spellings, or created fresh by a new buyer who didn't find the existing record. Spend splits across the duplicates, and a supplier genuinely above AED 100,000 shows as two suppliers below it. The aggregation test silently passes a relationship it should have caught.
Inconsistent legal names and missing identifiers — trade names where legal names should be, absent or unvalidated TRNs, no trade licence number captured at all. Decision 13 asks you to verify a specific legal person against official records; a vendor record that cannot be confidently matched to that legal person cannot anchor the verification.
No linkage to licence data — Article 4(3)(b) requires verifying that supplies fall within a supplier's licensed activities. That test presupposes you know what the licence says. A vendor master with no licence reference has no join to make.
Inactive records never purged — inflating the apparent population, obscuring which relationships are live, and turning every population count into an argument.
The Calculation Itself Is Harder Than It Looks
Even on clean data, the Article 6 aggregation is not a report most systems run today. It is a rolling twelve-month supplier-level total — not a financial-year figure — recomputed as invoices arrive, because a supplier can cross the threshold mid-year and change the status of every subsequent small invoice. And it has a forward-looking limb: supplies expected to exceed the threshold over the next twelve months are equally in scope, which means contracted and planned spend has to inform the calculation, not just posted history.
Annual spend by vendor, most businesses can produce. A continuously updating rolling view with a defensible forward expectation is a different capability — and from 1 October 2026 it is the capability on which scope determination depends.
The New Attributes the Vendor Record Needs
Beyond fixing what exists, Decision 13 implies vendor master attributes that most schemas simply do not carry: verification status and date, verification expiry against the twelve-month refresh cycle, the threshold tier the supplier sits in, risk-indicator observations over a rolling window — address changes and key-personnel changes are now facts a buyer needs to be able to observe — and linkage from the vendor record to the evidence that verification happened. A vendor master that cannot say "verified, on this date, by this person, evidence here, expires then" cannot operate the refresh cycle the Decision requires.
Data Quality Now Has a Deadline
The usual approach to master data quality is progressive improvement — clean as you go, fix on touch. Decision 13 changes the economics of that patience, because several of the facts involved are point-in-time. The address recorded against a supplier in October 2026 is evidence about October 2026; the corrected address entered in 2028 is not. A vendor base scoped on broken data produces a broken in-scope population, and every verification decision downstream inherits the error. Remediation before the effective date is worth disproportionately more than remediation after it.
The encouraging flip side: this is a bounded, well-understood class of work, and businesses preparing for UAE e-invoicing have every reason to do it once — the same clean supplier identity data serves both programmes.
How Contiqa Can Help
Contiqa Systems runs vendor master diagnostics specifically against the Decision 13 tests: where duplicates and identity gaps distort the threshold calculations, what the true in-scope population is, and what the vendor record needs to carry to operate verification sustainably. Contact Contiqa Systems to find out what your vendor data can — and cannot — currently tell you.
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.