Some values can only be judged against a source outside the enterprise: a tax id against the tax authority, a registered name against the company registry, an address against the postal service, a bank account against the bank, a party against a sanctions list.
| Field | Service | What comes back | On a mismatch |
|---|---|---|---|
| Tax id, VAT number | The tax authority's check service, per country | Valid or invalid, the registered name and address, a reference | The corrector proposes the registered name; an invalid id quarantines the record |
| Registered name, status, officers | The company registry | The legal name, the status (active, dissolved), the registration number | A dissolved status quarantines; a name difference becomes a proposal with the registry as basis |
| Address | Postal validation and geocoding | The deliverable form of the address, or a correction | The corrected address is proposed; an undeliverable address is a finding |
| Bank account | Account verification (name and account match), IBAN and BIC checks | Match, partial match, no match; the checksum result | No match holds the record under the two-person rule; treasury decides |
| Party | Sanctions and watch lists | A hit with the list and the score, or clear | A hit blocks the record and notifies compliance; the block is a policy floor |
| Product codes | Classification and tariff services | The current code and its description | A retired code is proposed for replacement with the successor |
A verified value carries four things: the service that verified it, the date, the reference the service returned, and the result. They are stored beside the value on the golden record, shown on hover in the grid and returned by the API on request. A timeliness rule reads the date and asks for a fresh verification when the value ages: twelve months for bank details on the showcase estate, three years for addresses.
Because the evidence is on the record, an audit question is a query: every supplier bank change in the quarter, with its verification reference and the two people who approved it. On the showcase estate that query returned 412 changes, every one verified, and zero payments to an account changed within the previous seven days.
| when | who | field | before | after | why | entry |
|---|---|---|---|---|---|---|
| Sep 12 | verifier L2 | supplier 100482 · tax id | unverified | valid · VAT-88213 | tax authority · registered name matches | #87,410 |
| Sep 12 | verifier L2 | supplier 100482 · address | 12 Mill Lane, LS1 2AB | 12 Mill Lane, LS1 4AB | postal service · postcode corrected | #87,411 |
| Sep 12 | verifier L1 | supplier 100913 · bank account | ···· 1234 | held: no match | bank verification · treasury two-person | #87,412 |
| Sep 13 | treasury (2) | supplier 100913 · bank account | ···· 1234 | ···· 1298 | supplier letter on file · both stamps | #87,590 |
Tax-authority checks per country, company registries, postal validation, bank account verification and sanctions screening are configured as tools with a mode; the connector library lists the providers, and a provider is a configuration, so a preferred one can be added.
Most services charge per call, so the verifier is scheduled: on change for the weighted fields, on a calendar for ageing, and on request from the grid. The daily budget is a guard like any other.
Yes: the same services run at creation on the entry points, so a supplier is verified before its record exists in the ERP.
The record is blocked, compliance is notified, and the block is a policy floor: no level of autonomy and no steward can lift it; compliance does, with a reason.
Bring one domain and two systems. In a week the sources are profiled, the ten costliest fields are under rules, the first corrections are written back with their acknowledgements and the publish gate is on.
