Know your business is a phrase that sounds simpler than it is. The regulatory obligation is clear enough: before entering a commercial relationship with a legal entity, verify who it is, who controls it, and whether either of those answers should give you pause. The operational reality is that most KYB processes answer a different and easier question: who does Companies House say controls this company, at the first layer, right now.
That is not the same thing. And the gap between those two questions is where most compliance failures live.
What a KYB check typically covers
A standard KYB process confirms that the company is registered and active, looks up its directors and persons with significant control, screens those individuals against sanctions lists and politically exposed persons databases, and records the result. Executed well, this takes minutes; with the right tooling it can run automatically at onboarding. The check produces a record, and the record demonstrates that due diligence was done.
For most straightforward counterparties, this is sufficient. A company with one or two individual shareholders, no international holding structure, and directors who come back clean on screening is genuinely lower risk, and the process reflects that correctly. The system works for the cases it was designed around.
When the PSC is a company
The problem starts when the PSC is not a natural person. Companies House allows a company to be the PSC of another company. That is not unusual; it is the normal structure for most companies that have ever taken investment, been acquired, or been set up by a group that already operates through a holding vehicle. When the PSC of your counterparty is a company, the register gives you the name of that company. It does not give you the name of the person who controls that company.
A KYB check that stops there has identified the first layer of a chain of unknown depth. The person who ultimately controls the counterparty, the one the regulation is asking you to identify, is somewhere above that layer. How far above depends on how the structure is organised. In a simple case it is one lookup: the PSC of Company B is an individual. In a more complex case it is five lookups, three jurisdictions, and a holding vehicle in a territory with a thin public register. In both cases, the first-layer check produced the same output: a record with a company name where a person's name should be.
Why most processes stop there anyway
Resolving through a corporate chain is manual work. Each layer is a separate query, against a different record, in a potentially different jurisdiction, with a different data format. A five-layer structure spanning two jurisdictions is a morning's work if you know what you are doing; it is a half-day's work if you do not, and it is easy to stop before you finish because each layer looks like completion until you notice the entity at the end is still a company. The incentive is to stop at the first unambiguous result, declare the check done, and move on.
This is not a failure of intent. It is a structural consequence of doing chain resolution by hand. The process is designed around the easy case, and the hard case exposes the gap. A regulator reviewing the check two years later will not ask how long it took. They will ask whether you knew who controlled the entity, and whether you checked.
Historical state is a separate problem
Even a correctly completed chain resolution only describes the ownership structure as it stands today. If the question is about a transaction that completed eighteen months ago, or a relationship that was formed when the counterparty had a different ownership structure, the current state of the register is the wrong answer. Reconstructing what the chain looked like on a specific past date requires reading through filing amendments in sequence, across every entity in the chain. That work is rarely done, because it is slow and because the process was not designed to ask for it.
For transaction work and investigations into historic relationships, this is the gap that produces the most consequential errors: a chain that looks clean today, checked against a current register, returned as evidence of due diligence on a transaction where the relevant question was what the structure looked like at closing.
The defensible process
A defensible KYB process answers three questions: who ultimately controls this entity, when was that ownership established and by what document, and has the structure changed since the relationship began. Answering the first requires resolving through the chain to a natural person. Answering the second requires linking each step to the filing that established it. Answering the third requires monitoring, not a one-time check at onboarding.
None of that is incompatible with speed; the question is whether the resolution work is done by the compliance team against raw register records or by a data layer that has already resolved the chain and attached provenance to each step. Briefed Atlas is built for the second approach: resolved beneficial ownership, with the source filing behind every record, queryable as it stood on any past date. For a fuller account of what a complete KYB process covers, see the Atlas KYB reference.