← Back

The cases a name check was not built to catch

From Anières

A lot of what we're building is for the cases the name check was never going to catch.

A clean name-hit report is not the same as a clean file. The class of cases a name check was never built to catch is larger than most buyers assume: entities not themselves listed but majority-owned by parties who are, structures that reach a listed party through two or three ownership hops, control relationships that do not show up as ownership at all. All of these sit deliberately outside the perimeter of a standard screening product, and none of them stop existing when the product returns green.

A serious system spends most of its time in that under-layer. Who owns what, through what, with whom, since when. Structures are designed to make that question harder. Reading them is part research, part software, part patience. None of it is a single query.

What the model side is for is joining things up at a scale a person cannot. A holding company in one place, a shareholder filing in another, a director change in a third, an old archive that mentions both. Each piece is small; the point is the joint reading.

The honest version, for a private client, is that a clean name is not the same as a clean counterparty. It shows up regularly: the check comes back fine, the structure does not. That gap is where the actual work lives.

A name is the easy part; the structure underneath is the part most reports do not really read.

The class of cases a name check was never going to catch is larger than most buyers assume. Entities that are not themselves listed but are majority-owned by parties who are, structures that reach a listed party through two or three ownership hops, and control relationships that don't show up as ownership at all; all of these sit outside the shape of a standard screening product.

The general point is that a tool designed for one question will confidently return an answer to a different question if you ask it. The answer will look correct. Knowing what a tool was actually built to catch, and what sits deliberately outside its perimeter, is a lot of what expertise in any field turns out to be.

Written alongside work at Anières: exposure mapping, cross-reference, and standing-report systems for private clients.