Join our Newsletter — 33% off our NHI Course
Home› Guides› KYC vs KYB: When Business Verification Must Sit…
Guide Fraud Prevention

KYC vs KYB: When Business Verification Must Sit on Top

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 17 min read
On this page

Most onboarding failures with business customers happen because a firm verified the company and never properly verified the people who own and run it, or verified a person and never noticed there was a company behind them. Know your customer (KYC) proves that a natural person is real and is who they claim to be. Know your business (KYB) proves that a legal entity exists, works out who ultimately owns and controls it, and confirms who may act for it. This guide is about the decision between them: when individual KYC is enough, when KYB has to be layered on top, how deep the ownership work must go, and how the threat model changes from synthetic identities to shell companies and nominee directors. It is for fraud, onboarding and compliance leads and product teams. The mechanics of each check live in the Identity Proofing and KYC Guide and the KYB Guide; this page does not repeat them.

Key takeaways

  • KYB is not an alternative to KYC, it contains it. Every serious KYB regime ends with natural persons: beneficial owners, a senior managing official where no owner can be found, and the individual acting for the entity, each verified as a person.
  • The customer's legal form decides the trigger, not the size of the account. A sole trader trading under their own name is usually a KYC case; a limited company, partnership or trust with one employee is a KYB case.
  • Ownership depth is set by law and risk together. The 25% ownership test in US and EU rules is a floor for identification, and control by other means, nominee arrangements and higher risk push the work deeper.
  • Registry data is a claim, not evidence. UK and EU rules both say a register alone does not discharge beneficial owner verification, and the EU requires discrepancies to be reported back to the register.
  • The classic KYB failure is verifying the company but not its controllers. A registry match proves nothing about the applicant's authority.

The short answer

Use KYC alone for a natural person contracting in their own name, including most sole traders. Add KYB whenever the customer is a legal person or arrangement: a company, LLP, partnership, trust, foundation or association. Once KYB applies, you still run KYC, but on a different set of people: the beneficial owners, the senior managing official where no owner is identified, and anyone who opens, administers or instructs on the account.

DimensionKYC (individual)KYB (business)
SubjectA natural personA legal entity plus the natural persons who own, control or act for it
Core questionIs this person real, and are they the person applying?Does this entity exist, who ultimately owns and controls it, and is the applicant authorised to act?
Primary evidenceIdentity documents, authoritative data sources, biometric comparison, electronic identificationCompany registries, constitutional documents, ownership declarations, legal entity identifiers, plus KYC on each relevant person
Headline threatImpersonation, stolen identity, synthetic identity, injected or deepfake mediaShell and front companies, nominee directors, layered ownership, company identity hijacking, fake merchants
Assurance referenceNIST SP 800-63A-4 identity assurance levels (IAL1 to IAL3)AML beneficial ownership rules: FATF Recommendation 24, Regulation (EU) 2024/1624, UK MLR 2017 regulation 28, 31 CFR 1010.230

Decision criteria: when KYB must sit on top of KYC

Three questions, answered in order before any document is requested, decide the route.

  1. What is the customer's legal form? If the contracting party is a legal person or legal arrangement, KYB applies. Under 31 CFR 1010.230(e)(1) that includes corporations, LLCs, general partnerships and comparable foreign entities. UK MLR 2017 regulation 28(3) sets specific measures for a body corporate.
  2. Is the entity in an exempt or reduced category? Some customers need less ownership work. The US rule excludes regulated financial institutions, public issuers and several other categories (1010.230(e)(2)), and applies only the control prong to some pooled vehicles and nonprofits (1010.230(e)(3)). UK regulation 28(5) disapplies the board and ownership structure measures for companies listed on a regulated market. Exemptions remove ownership steps, never the entity or authority checks.
  3. What does your AML obligation and risk appetite require? A regulated firm follows its customer due diligence rules. A platform that is not an obliged entity, such as a SaaS marketplace or a gig platform paying out to businesses, still benefits from KYB where fraud, sanctions or payout risk is high, but may set a lighter standard. See the Identity Verification Requirements Map for which regimes apply to which sectors.

Edge cases that cause misrouting

CustomerRouteWhy
Sole trader using a trading nameKYC on the individual, plus checks that the trading name and activity matchNo separate legal person exists; the individual is the customer
Single-director, single-shareholder companyKYB, with KYC on the director who is also the ownerThe company is the customer even if one person stands behind it
Trust or foundationKYB style work on the arrangement: settlor, trustees, beneficiaries, protector as the applicable rule defines themOwnership is defined by role, not shareholding
Freelancer paid through a personal services companyKYB on the company, KYC on the personPayments go to the entity, and the entity is what is screened

How deep the ownership work must go

Ownership is where KYB costs time. Build the policy from the strictest regime you operate under and record which rule each step satisfies.

RegimeOwnership testControl testFallback when no owner is foundVerification standard
US: 31 CFR 1010.230Each individual owning 25% or more of the equity interests, directly or indirectly (up to four people)A single individual with significant responsibility to control, manage or direct the entity, such as a CEO, CFO or managing memberThe control prong always applies, so there is always at least one personRisk based procedures, minimum the same as for individual customers; may rely on the customer's information unless facts make it unreliable
EU: Regulation (EU) 2024/1624 (AMLR)Direct or indirect ownership of 25% or more of the shares or voting rights (Article 52); a lower threshold may be set for higher risk categoriesControl via other means (Article 53), including the right to appoint or remove most of the board, veto rights, and control through agreements, family relationships or nominee arrangementsThe entity states why no owner can be identified and gives details of its senior managing officials (Article 63(4))Identification and verification under Article 22, generally before the relationship starts (Article 23)
UK: MLR 2017 regulation 28Beneficial owner as defined in the regulations; reasonable measures to verify (28(4))Understand the ownership and control structure (28(3A))Treat the senior person responsible for managing the body corporate as beneficial owner, with written records of every step (28(6) to 28(8))Relying solely on registrar information does not satisfy 28(4) (28(9) to 28(9A))

The EU AMLR applies from 10 July 2027; until then national rules transposing the AML directives apply. In the United States, FinCEN's beneficial ownership reporting by companies is a separate regime from bank customer due diligence: FinCEN states that a final rule effective 14 August 2026 made permanent the March 2025 exemption of US companies and US persons from reporting. That narrows what the FinCEN register will hold, and does not remove a bank's own duty under 1010.230 to identify and verify beneficial owners of legal entity customers.

Going beyond the threshold

  • Look through, not just at: indirect ownership through intermediate companies counts. Map each layer to natural persons and record the percentage arithmetic, because two 20% holdings through related vehicles can make one person a 25% owner.
  • Control without shares: a person who can appoint the board, holds veto rights or directs a nominee is a beneficial owner under AMLR Article 53 even with no shareholding. Ask for shareholder agreements in higher risk cases.

Threat models compared

KYC: fake or borrowed people

  • Stolen identity: a real person's details and documents used by someone else. Countered by proving the applicant owns the evidence: biometric comparison, liveness, binding to an authenticator.
  • Synthetic identity: a fabricated person built from a mix of real and invented data. NIST SP 800-63A-4 describes IAL1 as designed to limit synthetic identities and automated enrolment attacks by validating core attributes against authoritative or credible sources, and makes a death records check mandatory for all proofing.
  • Injected and deepfake media: SP 800-63A-4 expects remote processes to control against injected or forged media. See Document Verification vs Liveness Detection.

KYB: fake or borrowed companies

  • Shell companies: real, validly registered entities with no genuine operations, used to hold accounts and move funds. A registry check passes because the company really exists. Detect through activity checks (trading history, declared turnover against volume) and links to other applications.
  • Nominee directors and shareholders: people paid to appear on the register while someone else controls the company. The registered director passes KYC perfectly, which is the point. Counter with control questions, nominee declarations, and checks for a director who appears on an implausible number of companies.
  • Layered and offshore ownership: chains of entities across jurisdictions where registers are thin or closed. FATF's March 2023 Recommendation 24 guidance promotes a multi-pronged approach to ownership information for this reason.
  • Company identity hijacking: fraudsters impersonate a legitimate company, or change its registered details, to open accounts or redirect payments. The entity checks out because it is real; the applicant is not authorised. This is why UK regulation 28(10) requires verifying that the person acting for the customer is authorised, and verifying their identity from a source independent of both that person and the customer.

The failure mode: verifying the company but not its controllers

The most common and most expensive KYB gap is a flow that confirms the entity in a registry, screens the company name, and stops. Every KYB attack above passes it. It shows up in four forms:

  1. Applicant never proofed: the person filling in the form is taken at their word because the company is real. Proof the applicant like a personal customer and tie them to the entity by register match, signed mandate or a verified director.
  2. Owners named but not verified: the customer declares owners and the firm records the names without verifying identities. US 1010.230 allows reliance on the customer's information only absent facts that make it unreliable, and the minimum verification for each owner matches that used for individual customers.
  3. Owners verified once, never again: ownership changes after onboarding and nobody notices. AMLR Article 26 sets update intervals of one year for higher risk customers and five years for others, and trigger events such as a director change should prompt review sooner. See Perpetual KYC.
  4. Screening the entity, not the people: sanctions and politically exposed person checks run on the company name only. Ownership based sanctions tests mean owners must be screened too. See CDD, EDD, PEP and sanctions screening.

Controls for each layer

ControlApplies toWhat it provesWhat it does not prove
Document authenticity checksKYC, and KYC within KYBThe evidence is genuine and unalteredThat the applicant owns it
Biometric comparison with livenessKYC, and KYC within KYBThe live applicant matches the document holderThat the person has authority over a company
Company registry lookupKYBThe entity is registered, its status, number, address and recorded officersThat the register is accurate, or who really controls the entity
Legal entity identifier and vLEIKYBA standard entity identifier; with vLEI, cryptographically verifiable role credentials for people acting for the entityBeneficial ownership beyond what the issuer verified
Ownership mapping and declarationsKYBA recorded structure down to natural persons with percentagesTruth of the declaration without corroboration
Authority to act checkKYBThe applicant is entitled to bind the entityAnything about the owners
Ongoing monitoring and re-screeningBothChanges in people, ownership and behaviour are caught after day oneThat onboarding was correct

GLEIF describes the verifiable LEI (vLEI), standardised as ISO 17442-3 in 2024, as credentials issued to specific persons in specific roles by Qualified vLEI Issuers, so one cryptographic check covers the entity, the person and their role. It can replace a manual mandate review for the authority question, not the ownership work. Companies House has made identity verification mandatory for UK directors and persons with significant control since 18 November 2025; a verified register entry raises confidence in a director, but under regulation 28(9A) it still cannot be your only source for beneficial owner verification.

Designing the combined onboarding flow

  1. Classify first: capture legal form, jurisdiction of incorporation and registration number before anything else, and route to KYC or KYB automatically.
  2. Proof the applicant: run KYC on the person in front of you, at the assurance level your risk assessment sets, whatever route the customer takes.
  3. Confirm the entity: look up the registry, compare name, number, status and address, and pull recorded officers and owners as claims to test.
  4. Prove authority: match the applicant to a recorded officer, or collect a mandate or board resolution, or accept a role credential.
  5. Map ownership: collect a structure chart and declarations, look through intermediate entities, compare with the register and record discrepancies.
  6. Verify the people: run KYC on each beneficial owner (or the senior managing official, with records of why), proportionate to risk.
  7. Screen everyone: entity, owners, directors and signatories against sanctions, PEP and adverse media sources.
  8. Decide and record: approve, approve with enhanced monitoring, request more evidence, or decline. AMLR Article 21 expects a firm that cannot complete due diligence to refrain from the relationship and consider a suspicious transaction report.
  9. Monitor: subscribe to registry change feeds where available, set review dates by risk, and re-screen on list updates.

Back-test the flow on a sample of existing business customers before switching it on: it shows how many files would fail the new authority and ownership steps and sizes remediation. Keep the old flow behind a switch for the first release so a routing defect can be rolled back.

Worked scenarios

Scenario 1: the marketplace seller. A marketplace pays out to sellers. Occasional individual sellers go through KYC with document and liveness checks. A seller registering as a limited company triggers KYB: registry lookup, a check that the applicant is a recorded director, and KYC on owners above threshold. When payouts jump far above declared turnover, monitoring flags it and review finds the director listed on dozens of new companies sharing one address. The nominee pattern was invisible to KYC because the director\'s identity was genuine.

Scenario 2: the business bank account. A bank onboards an LLC under 31 CFR 1010.230. The person opening the account certifies one 60% owner and a managing member under the control prong, and both are verified as individuals. Six months later a registry change feed shows a new member; a trigger rule reopens the file, finds a new 30% owner, verifies and screens them. Without the trigger the file would have been wrong until the next scheduled review.

Scenario 3: the impersonated supplier. A payments firm receives an application from a well known, long established company. Registry data matches perfectly. The applicant is not a recorded officer and supplies a mandate letter. The firm calls the company on a number taken from an independent source, not the application, and learns nobody there applied. The company was real; the controller check, not the entity check, stopped the fraud.

Small and large organisations

  • Small firms and platforms: buy KYC and registry lookups as services, keep ownership mapping manual for the minority of complex cases, and spend analyst time on authority and nominee signals rather than on simple single-owner companies. See the Identity Verification Buyer's Guide.
  • Large regulated firms: run a single customer and party model where each natural person is verified once and linked to every entity they own or control, so a director of ten customers is proofed once and screened once.

Where identity fits: business accounts after onboarding

Once verified, a business has many identities acting for it: administrators, staff, API keys and AI agents. KYB proves who could act on day one, not who acts later. Give customers delegated administration, require strong authentication for administrators, re-verify when signatories change, and govern customer-created API credentials as non-human identities with owners and expiry. See the B2B CIAM and Organisation Management Guide and the API Key Management Guide.

Detection and measurement

  • Routing accuracy: share of business customers sampled in QA that were onboarded through the correct route.
  • Controller coverage: share of active business customers where the applicant, every beneficial owner (or a recorded senior managing official) and every signatory has a verified identity on file.
  • Fallback rate: share of corporate files relying on a senior managing official instead of a beneficial owner, by segment.
  • Register discrepancy turnaround: time from discrepancy found to report filed, against the 14 calendar day expectation where AMLR applies.
  • Review currency: share of business customers whose ownership data is within its review interval for their risk rating.
  • Post-onboarding fraud by route: confirmed fraud losses on business accounts within 12 months of onboarding, split by which checks were run.

Common failure patterns

  • Treating every small business as a person: routing single-director companies through consumer KYC because the flow is faster, so the entity is never checked or screened.
  • Stopping at 25%: ignoring control by other means, so a nominee-backed controller with no shares never appears in the file.
  • Fallback as default: analysts naming a senior managing official on routine files because ownership is slow to map, rather than after exhausting other means.
  • Duplicated people, inconsistent results: the same director verified differently across five customer files, so a sanctions hit on one is missed on the others.

Framework mapping

FrameworkReferenceRelevance
FATFRecommendation 24 and March 2023 guidance on beneficial ownership of legal personsInternational standard for adequate, accurate and up to date ownership information
EU AMLRRegulation (EU) 2024/1624, Articles 20 to 26, 51 to 53, 63Customer due diligence, beneficial owner definition, thresholds, ongoing monitoring
UKMoney Laundering Regulations 2017, regulation 28Body corporate measures, beneficial owners, senior managing official, authority to act
US31 CFR 1010.230Beneficial ownership of legal entity customers at covered financial institutions
NIST SP 800-63A-4IAL1 to IAL3, fraud controlsAssurance level for proofing each natural person
NIST SP 800-53 Rev 5IA-12 Identity Proofing, IA-12(2) Identity EvidenceControl language for proofing users of an organisation's systems
NIST CSF 2.0PR.AA-02Identities are proofed and bound to credentials based on the context of interactions

Practitioner checklist

  • Capture legal form as a structured field and route legal entities to KYB automatically.
  • Proof the applicant as an individual on every route, and record how their authority to act was confirmed.
  • Write the ownership policy against the strictest regime you operate under, including control by other means.
  • Corroborate registry data with independent evidence and report discrepancies where required.
  • Verify every beneficial owner, or record why a senior managing official is used and every step taken.
  • Screen owners, directors and signatories, not only the entity name.
  • Set review intervals by risk and add trigger reviews on ownership, director and signatory changes.
  • Keep one verified record per natural person linked to every entity they own or control.

Standards and references

Related NHI Mgmt Group resources: KYB Guide · Identity Proofing and KYC Guide · Identity Verification Requirements Map · Account Opening and Application Fraud Guide. This guide summarises legal requirements for orientation and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.