← Blog · Compliance

Beneficial Ownership: Unwrapping Corporate Layers in KYB

PrivateKYCBot Team · September 11, 2026 · 3 min read

Beneficial Ownership: Unwrapping Corporate Layers in KYB

Onboarding a business is not onboarding a person. Behind every corporate customer sits a chain of holding entities, nominees, and shareholders that eventually resolves to human beings. Ultimate Beneficial Owner (UBO) identification is the process of collapsing that chain until you reach the natural persons who own or control the entity. Most frameworks — including the EU's AML directives and FATF Recommendation 24 — set the standard threshold at 25% ownership or control, though higher-risk sectors often apply 10%.

Ownership Is Not the Same as Control

Two tests run in parallel, and a UBO can qualify under either one. Ownership is arithmetic: multiply the percentages down each branch of the tree. A person holding 60% of Company A, which holds 50% of your customer, controls 30% — above the 25% line. Control is behavioral and harder to compute:

  • Voting rights that diverge from equity, such as dual-class shares.
  • Board appointment powers or veto rights written into shareholder agreements.
  • Nominee arrangements where the registered holder acts for someone else.
  • Senior managing officials — the fallback UBO when no natural person meets the ownership threshold.

A structure engineered to keep every branch under 25% is itself a risk signal. Deliberate fragmentation across five holders at 20% each leaves no UBO on paper, which is precisely why the control test and the managing-official fallback exist.

Building and Verifying the Tree

Start with a registry pull where one exists, but treat it as a claim, not a conclusion. Corporate registers vary widely in quality: some jurisdictions verify filings, many simply record what was submitted, and a few publish nothing on ownership at all. Reconcile the registry against documents the customer provides — articles of incorporation, share registers, and shareholder agreements — and flag any gap between the two.

Each layer adds work. A three-tier structure spanning three jurisdictions can require verification against three registries, translation of two document sets, and screening of every intermediate entity for sanctions exposure. Once you reach the natural persons, each identified UBO needs the same individual verification you apply to any customer: identity document checks, sanctions and PEP screening, and adverse media review. A UBO who never signs up directly still has to prove who they are.

This is where a chat-based flow helps. Rather than emailing forms to a corporate contact and waiting days for a scanned packet, you can route each identified individual through a Telegram or WhatsApp verification session, collect their document and selfie in that channel, and tie the result back to the entity file. Data minimization matters here too: you need the UBO's identity confirmed, not the entire beneficial-ownership graph copied into every downstream system.

Keeping the Picture Current

Ownership changes without notifying you. A share transfer, a new investor, or a restructuring can move someone above or below the threshold overnight. A UBO record verified at onboarding and never revisited decays quietly. Tie refreshes to events — funding rounds, registry filing updates, changes in signatories — rather than a fixed calendar. Where you hold verified identity data on individual UBOs, apply configurable retention so records tied to a person who exits the structure are not kept longer than your policy and applicable law require.

Documenting the Determination

Examiners rarely dispute the final list of names; they dispute how you arrived at it. Record the reasoning, not just the outcome:

  • The ownership calculation for each branch, with source percentages.
  • Which test — ownership, control, or managing-official fallback — qualified each UBO.
  • The documents and registry snapshots relied on, with retrieval dates.
  • Screening results for every entity and person in the chain.

A defensible UBO file reads as a traceable argument: this is the structure we found, this is how we resolved it to people, and this is what we checked on each of them. The names are the conclusion — the method is what withstands review. This article is general information, not legal advice; calibrate thresholds and procedures to your own regulatory obligations.

General information, not legal advice. Talk to your compliance counsel for guidance on your specific obligations.