KYB: Verifying Businesses Before You Verify Their People

Know Your Business (KYB) is the corporate counterpart to individual KYC, and it is often where onboarding stalls. A business customer is not a single identity but a cluster of registrations, documents, signatories, and owners. Verifying it means confirming the entity exists, is authorized to trade, and is controlled by people you can screen. Get the sequence wrong and you either onboard shell companies or bury legitimate clients in duplicate requests.

What KYB Actually Confirms

A defensible KYB file answers four questions before any individual check runs:

• Existence: the entity is registered and active in its jurisdiction, matched against an official registry rather than a self-declared name.
• Legal form: LLC, partnership, trust, or listed company — each carries different ownership transparency and documentation.
• Status: not dissolved, struck off, or in insolvency, checked against the registry's current record.
• Authority: the person opening the account can bind the business, evidenced by board resolutions, articles, or a signatory mandate.

Registry coverage varies widely. The UK's Companies House and the EU's interconnected BRIS offer structured data; many jurisdictions still return scanned PDFs or nothing machine-readable. Build for graceful degradation: automated lookup where an API exists, structured document upload where it does not.

Documents You Need — and Those You Don't

The instinct to collect everything creates retention liability without improving assurance. Anchor the request list to the entity's legal form. A single-member LLC needs its certificate of incorporation and a proof of address; a multi-layer holding structure needs shareholder registers and, potentially, audited accounts. Typical core artifacts include:

• Certificate of incorporation or registration extract
• Articles of association or operating agreement
• Register of directors and shareholders
• Proof of registered address
• Tax identification number

Each document should map to a specific verification purpose. If you cannot state which risk a file mitigates, do not collect it. Where documents contain more than you need — a full shareholder register when you only require the controlling tier — capture the relevant fields and apply data minimization so the raw file is not retained longer than the verification requires. Configurable retention lets you hold incorporation proof for the account lifetime while purging supporting scans on a shorter schedule.

From Entity to Individuals

KYB does not replace individual KYC — it scopes it. Once the corporate structure is mapped, three categories of people require verification: directors, authorized signatories, and beneficial owners above the ownership or control threshold, commonly 25% but lower in higher-risk regimes. Each becomes an individual subject for identity verification and screening against sanctions and adverse-media lists.

This is where chat-based collection reduces friction. Rather than emailing a signatory a portal link and waiting, the verification flow can reach directors and owners directly on Telegram or WhatsApp, collect their identity documents in a channel they already use, and return status to the compliance queue. For distributed ownership structures spanning multiple countries, meeting each person where they are cuts days off the cycle. General guidance on thresholds and control tests should be confirmed against your applicable regulations rather than treated as universal.

Keeping KYB Current

Corporate structures change more quietly than individuals move house. Directors resign, shares transfer, and holding companies restructure without notifying you. A static KYB file decays within months. Tie refresh to observable events rather than fixed calendars where possible:

• Registry filings indicating director or ownership change
• Changes in trading address or registered agent
• Sanctions or adverse-media hits on any linked individual
• Material shifts in transaction volume or counterparties

Log every check, its source, and its timestamp so the file reconstructs the state of knowledge at each decision point. A KYB record that shows what you knew, when, and why you acted is the difference between a manageable regulator conversation and an unexplained gap. Treat the corporate file as a living object, not a one-time gate.