- A UAE Tax Invoice must carry the supplier's name, address and 15-digit TRN — and the recipient's where the recipient is registered. That has been the rule since 2018; what changes on 1 January 2027 is that the first cohort's invoices are validated field by field before they move.
- TRN validation is free: the FTA's public verification tool on tax.gov.ae takes the 15-digit number, no login, and returns the registered legal name in English and Arabic. The test that matters is not "does the TRN exist" — it is "does the returned name match your master record".
- Your e-invoicing participant identifier is a different number: the 10-digit TIN, the first 10 digits of your Corporate Tax TRN — not your VAT TRN. Two identifiers, two failure modes, both live in the same party records.
- Under the five-corner model you are a Recipient as well as an Issuer, and the FTA receives Tax Data from both sides. A vendor master full of unverified TRNs stops being a housekeeping item and becomes a reconciliation exposure.
TRN validation is the cheapest risk reduction available to a UAE finance team this quarter. One free lookup per counterparty, against the Federal Tax Authority's own register, settles the field that anchors both ends of every tax invoice you issue or receive. Yet on most of the vendor and customer masters we audit, nobody can say when — or whether — that lookup was ever done. With the Accredited Service Provider appointment deadline on 30 October 2026 and go-live on 1 January 2027, this is the piece of the programme you can finish before your integration project even starts.
What the law already requires
Start from the standing rule, because it predates e-invoicing entirely. Article 59 of the VAT Executive Regulation — Cabinet Decision No. 52 of 2017, as amended, most recently by Cabinet Decision No. 100 of 2024 — requires a Tax Invoice to show the supplier's name, address and Tax Registration Number, and the recipient's name, address and TRN where the recipient is a registrant. The TRN is the 15-digit number the FTA issues on VAT registration. None of this is new law; it is the law your invoices are meant to satisfy today.
The e-invoicing mandate — Ministerial Decisions No. 243 and 244 of 2025, amended by Ministerial Resolution No. 66 of 2026 — changes the enforcement mechanics, not the principle. The Ministry of Finance's mandatory field list (version 1.0, 23 February 2026) defines 51 mandatory fields on an electronic Tax Invoice, party identifiers on both sides among them, and under the five-corner model each invoice is validated field by field between your provider, your counterparty's provider and the FTA. A wrong identifier no longer produces a quietly imperfect PDF. It produces a rejection, logged on both sides. The UAE compliance page covers the mandate's scope and dates in full.
Two identifiers, not one
The party records that carry the TRN also have to carry a second number, and confusing the two is the single most common defect we find in otherwise tidy masters. Your 15-digit VAT TRN is a field on the invoice. Your participant identifier — the address your entity answers to on the network — is the TIN: a 10-digit number, being the first 10 digits of your 15-digit Corporate Tax TRN. Inside a Tax Group the trap tightens: each member uses its own TIN, not the group representative's. We keep a full account of the identifier rules, and the rework they cause, in the field-by-field guide.
For master data purposes the consequence is simple: party records need both identifiers held as separate, validated fields — not one number keyed into whichever box was on screen, and not a spreadsheet column titled "TRN" that nobody can date.
How to validate a TRN, step by step
The FTA operates a public TRN verification service on tax.gov.ae. It asks for the 15-digit number and a security check — no login, no account, no fee — and returns the registrant's legal name in English and Arabic. The procedure for one record:
1. Check the shape before you check the register. Fifteen digits, no letters, no spaces. Anything else — 14 digits, a trailing letter, a number pasted with its label — fails before it reaches the tool.
2. Run the number through the FTA tool. An active TRN returns a registered legal name. An invalid or deregistered one returns nothing usable. Both outcomes are information.
3. Match the returned name against your master — character for character. This is the step that separates validation from theatre. A TRN that belongs to somebody is not evidence it belongs to your counterparty. Trade name where the register holds legal name, "LLC" against "L.L.C", the wrong entity from the same group — every one of these is a live mismatch sitting behind a lookup that "passed".
4. Record the evidence. Date of check, returned name, who ran it. A validation nobody wrote down expires the moment the person who ran it changes jobs.
A TRN that verifies is not a record that matches. The tool returns a name; the audit is whether your master agrees with it.
The audit, at master scale
One record takes a minute. The estate is the project. The sequence we run on vendor and customer masters together — because under the exchange model you will be issuing to one and receiving from the other:
1. Extract every party record with a tax identifier field — customers, suppliers, one-time vendors, the intercompany partners everyone forgot are counterparties too.
2. Classify before you verify. Records with no TRN where the counterparty is plainly VAT-registered; TRNs failing the 15-digit shape test; duplicate counterparties carrying conflicting TRNs; free-text identifiers with labels or spaces baked in. In our audits these four classes usually surface most of the eventual rework, before a single lookup is run.
3. Verify the survivors against the FTA register, and log the returned names. The public tool answers one number per query, so at estate scale this is a scheduled workflow with an owner — not an afternoon with a browser tab.
4. Chase the mismatches as remediation, not curiosity. Name mismatches route to the counterparty for confirmation of their registration certificate; deregistered TRNs route to procurement and finance for a decision, because a supplier who quietly deregistered is a commercial fact, not a data defect.
5. Close the loop in the ERP — merged duplicates, both identifiers in their own validated fields, and a rule that no new party record goes live unverified. Remediation without an entry gate is a treadmill; our data practice exists mostly because of that sentence.
Why this decides money, not formatting
On the payable side, your input VAT recovery rests on holding valid tax invoices — documents that carry your supplier's correct TRN and your own. On the receivable side, an invoice issued against a wrong buyer TRN is an invoice your registered customer's systems have every reason to bounce. And once Tax Data Documents flow to the FTA from both ends of every exchange, the authority holds a live, field-level view of who invoiced whom, under which registrations — a shift we examined in "The FTA sees your numbers first". Rejection logs make the same point from the other direction: when e-invoices fail, the log reads as a master data audit, and party identifiers sit at the top of it.
Where this sits on the clock
From 21 September 2026, first-cohort businesses — annual revenue of AED 50 million or more — have 39 days to the 30 October ASP appointment deadline and 102 days to mandatory issuance on 1 January 2027. Businesses below the threshold follow on 1 July 2027, government entities on 1 October 2027. The Ministry's register listed 54 accredited service providers and 8 more in final assessment when we checked it on 21 September; the week-by-week roadmap covers how the appointment and the data work run in parallel. One note of precision we repeat wherever providers come up: ClayDesk is not a UAE-accredited ASP — what we operate today is GoRoute, a certified Peppol Access Point under ID POP000991 (held by ClayDesk LLC), and we advise on selection provider-independently.
The useful property of TRN validation is that none of it waits for that selection. The work is provider-independent, it transfers with you whichever ASP you appoint, and every mismatch you close now is a rejection you do not debug in January — on the e-invoicing practice we sequence it first for exactly that reason. If you want the wider readiness picture, the 25-point checklist scores party data as its first section, and ClayDesk Assure runs the same checks against your actual extracts.
Registers and specifications are revised without ceremony. This page carries a visible last-verified date for that reason — check the FTA's verification service and the Ministry of Finance's primary documents before relying on any number or deadline here.