Skip to content
Aashna Jain

What is KYB, and how is it different from KYC?

3 min readFor buildersTrust and riskTRUST AND RISK · 18 OF 19

A person has one face. A company can have nine owners, four of them companies, and one of them is the point.

Follow it up until it stops being a company
The merchantHolding coParent, offshoreno public registerownerthe actual owner25%the line

You are not verifying a company. You are verifying the person at the top of it.

What you are actually looking for

Three things, and only one of them is paperwork.

That the entity exists and is in good standing, which is a register lookup and is the easy part.

Who ultimately owns or controls it. This is the ultimate beneficial owner, and most regimes set a threshold, commonly twenty-five percent, above which a natural person must be identified and verified as an individual. Below that threshold, control can still trigger the requirement, because a person who directs the business matters whether or not they hold shares.

That the stated business is the real business. A registered wholesaler whose transaction pattern looks like gambling settlement is the whole reason this function exists.

Why it is genuinely harder than KYC

A person resolves. There is one of them, they have a document, and the document either matches or does not.

A company recurses. The shareholder of your applicant is another company, whose shareholder is a third, and somewhere up that chain is a jurisdiction whose register is not public, not machine readable, or not accurate. You are trying to reach a natural person through a structure that may have been designed specifically to make that difficult.

Then the data quality problem. Company registers disagree with each other, are updated on different cycles, and record names in formats that do not match. A significant part of any KYB operation is reconciling records that all claim to describe the same entity and do not agree.

And it never finishes. Ownership changes without telling you. KYB is a monitoring obligation, not an onboarding event, and the teams that treat it as a form to complete discover this during an audit.

The tradeoff nobody escapes

Every KYB decision is a trade between onboarding speed and the quality of what you let in, and it cannot be optimised away, only placed deliberately.

The way through is not to make one checkpoint faster. It is to tier. Verify enough to permit limited activity, then deepen the check as the business does more. A company processing small volumes in a low-risk category does not need the same scrutiny on day one as one that has asked for high limits in a category that attracts fraud.

The mistake I would flag hardest is treating KYB as a compliance gate bolted to the front of a product. It is a risk function that runs continuously, and it needs to be able to change its mind after approval.

Checking a person is checking a passport. Checking a company is being handed a set of nesting dolls, told the smallest one is a person, and discovering that the third doll was made in a country that does not let you open dolls.

Where you meet it

Every marketplace that took a week to approve a seller. Every business bank account application that asked for a shareholder register. Every platform that froze a merchant's payouts and cited a review nobody could explain.

Building this? A second pair of eyes on the architecture is what the advisory is for. →

Get the next one in your inbox.

New fundamentals and one memo every two weeks.

Or subscribe on Substack ↗