WorkflowCustomer Onboarding & KYC

Beneficial Ownership Verification

Beneficial ownership verification that finds every 25% owner through every layer, with the math and the proof on file

See one case, screen by screen ↓
Watch with transcript →

Built forKYC analystsKYC quality reviewersRelationship managersBSA officersInternal auditors

The Problem Today

Customers certify their own owners and count direct stakes only, so an owner behind a holding company is missed.

5.5 h
of staff time on one layered ownership certification our estimate
20 min
FinCEN assumed per new entity account, before any layered owners published

Stakes multiplied by hand

  • Certificate
  • Agreements
  • Ledgers
  • Registries
  • Arithmetic checked lateA wrong multiplication can reach an open account
  • No federal registry to checkDomestic companies no longer report their owners to FinCEN

The Solution

  1. The documents readCertification, agreements, ledgers and registries; each stake cited
  2. Each layer multipliedStakes multiplied along each path and added; loops solved exactly
  3. Checked against the formA second agent recomputes on its own; the form left an owner off
  4. Analyst decides, QC approvesOwners verified and screened; a correction drafted for the customer

Built-in controls

  • Each percentage cites its page
  • Maker and checker are different people
  • Need-to-know access, numbers masked

What You Get

Fewer exam findings for a missing owner, and business customers open with less back-and-forth.

0.7 h
of staff time on that same certification, with the agents our estimate
  • Each reason on recordWhy each person was or was not verified, in the file
  • Loops and nominees flaggedCircular stakes solved; shared agent addresses spotted
  • Hours back on each fileAgents read, chart and check the math; people decide
In short

What is Beneficial Ownership Verification?

Beneficial ownership verification is how a bank identifies and verifies each person who owns 25% or more of a legal-entity customer, directly or indirectly, and one person who controls it, under the FinCEN CDD Rule (31 CFR 1010.230). Beneficial Ownership Verification does this work with seven agents: they read the certification and the entity's documents, build the ownership tree twice on two models, write out each person's math with its sources and verify each owner's identity. A KYC analyst records the decision and a QC reviewer approves it.

AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →

Updated

The problem

Beneficial ownership the certification misses, one holding company down

Beneficial ownership verification starts with the customer's own arithmetic. Under the FinCEN CDD Rule a bank must identify and verify each person who owns 25% or more of a legal-entity customer, directly or indirectly, and one person who controls it. The customer signs a certification, and customers usually count the stakes they hold directly. A person who reaches 25% through a family holding company is easy to miss, because the form does not ask anyone to multiply.

So the KYC analyst draws the chart by hand. For a layered entity that means the operating agreement, each member's own agreement, the membership ledger, the cap table and registry extracts, then multiplying along each path on paper or in a spreadsheet. Nobody checks that arithmetic until QC, sometimes after the account is open, and the file rarely says why each person was or was not identified. Since March 2025 domestic companies no longer report their owners to FinCEN, so the bank's own file is the record, and since February 2026 FinCEN's relief order lets a bank verify once at the first account. That file has to be right.

estimated41daysbusinesses wait, on average, to open a bank account
estimated87%of corporate treasurers have abandoned an account application
typical20minutesFinCEN assumed per new legal-entity account for its owners, before any layered structure
Where the analyst and QC hours go on one layered certificationestimated
By hand5.5 hours
With the solution0.7 hours
  • Reading the certification, operating agreements, ledgers and registry extracts1 → 0.1 h
  • Drawing the structure and multiplying stakes through each layer1.5 → 0.1 h
  • Checking the arithmetic and the reason for each person below 25%1 → 0.1 h
  • Verifying each owner's identity and screening OFAC0.8 → 0.1 h
  • Writing to the customer about what the certification gets wrong0.5 → 0.1 h
  • Recording the decision, QC review and keying the owners into the core0.8 → 0.3 h

Estimated split of the people's working time on one certification with at least one layer of indirect ownership, by hand and with the agents. It leaves out the time spent waiting on the customer. Our arithmetic, kept modest.

How it works

The tree built twice, then set against the certification

What comes in
Certification inEach document in the file · certification, agreements, ledgers, registries
Agents at work
Document Reader agentevery stake, cited
Then
Ownership Builder agentthe tree, the math
Ownership Checker agentrecomputes on another model
Then
Structure Risk agentloops, nominees, trusts
Identity Verification agentCIP elements, OFAC
Then
Relief and Outreach agentsre-verification, requests
A person decides
KYC Analyst and QCthe analyst records; QC approves
What comes out
Ownership tree with the math
Verification decision with reason
Corrected certification request
One case, step by step

Beneficial ownership of a layered hotel LLC and the owner left off its form

A hotel group organized as an LLC, running nine boutique hotels, applies to a commercial bank for an operating account and treasury services. Its president certifies one 25% owner, the founder at 34%, and signs as the control person. Here is what happens next in the working solution.

A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.

  1. 01Two days after it was certified

    Each certification, with what the agents found

    KYC analyst

    The analyst's queue holds four lanes: 23 need the analyst, 71 are ready to record, 14 are waiting on customers and 10 are with QC. Each row is one sentence the agents wrote: this file's missing owner, a cold-storage company whose ownership loop puts one person at 26.1%, and a restaurant group where the two agents disagree. Three files are due by 5:00 p.m., and one builder's file is past its service level and escalated.

    This month so far: 812 certifications, 98.6% decided on time, 41 discrepancies found before opening.

  2. 02Mid-morning

    The ownership tree, built twice

    Ownership Builder and Ownership Checker agents

    The Document Reader agent has read 9 documents and found 10 stakes and 6 holders. The Ownership Builder agent built the tree, 3 layers deep, and the Ownership Checker agent recomputed each percentage from the documents on a different model. Each arrow carries its stake and a source chip, and each person shows the multiplication: one family member holds 18% directly plus 60% of the family holding company, which holds 15%, so 18% + 60% × 15% = 27.0%.

    Both agree to the decimal · 6 of 6 holders · tolerance 0.05 pp.

  3. 03Line by line

    The certification against the evidence

    KYC analyst

    Each person sits on one row: certified, evidence, working and result. The founder at 34% agrees, and the control person agrees. The family member at 27.0% is not listed. Another member of the family holding company, two minority owners and the employee trust sit below 25%, each with the working recorded.

    The note on screen: the bank cannot rely on the certification as signed, because its own documents show a 25% owner who is not on it.

  4. 04Minutes later

    A corrected-certification request, approved before it is sent

    Outreach agent, then KYC QC reviewer

    The Outreach agent drafted the letter to the company's president: add the missing owner at 27%, explained from the company's own operating agreements, with identity details asked for that owner only. The analyst submitted it, a QC reviewer approved it eleven minutes later, and it went through the client portal with the relationship manager copied.

    The agent's checks: one person to add, the customer's own documents only, no internal or restricted information, plain language.

  5. 05That afternoon

    The corrected certification arrives, and it matches

    Document Reader and Identity Verification agents

    The president signs the corrected certification naming the founder at 34% and the missing owner at 27%. Two minutes later the agents compare it with the tree: 2 of 2 owners match and the control person is unchanged. The next step on the screen is one button: record the verification decision.

  6. 06Right after

    Each owner's identity verified, with the difference explained

    Identity Verification agent

    The three people each show the four identity elements: name, date of birth, address and ID number. Dates of birth and ID numbers are masked, and a reveal asks for a reason. One address is marked Explained, because the identity service still held the owner's prior address. OFAC screening finds no match for the people or the entities.

    Match scores 0.99, 0.98 and 0.97 · OFAC lists as of that morning.

  7. 07Late afternoon

    Recorded by the analyst, approved by QC

    KYC analyst and KYC QC reviewer

    The analyst records the decision: Verified, with a reason code, corrected certification received and matches, the evidence checklist at 7 of 7. QC approves 13 minutes later. Only then are 2 beneficial owners and 1 control person written to the client lifecycle system and the core banking system, inside the 2-day service level.

    The person who records a decision cannot approve it.

  8. 08Each version

    The tree as it stood on each date

    Internal auditor

    Five versions run from “As certified” to “Approved and written” two days later. Each says what changed, why and by whom, and the tree can be exported as of any date. It is kept until 5 years after the account closes.

  9. 09For the examiner

    One sealed pack with the math and the trail

    BSA Officer

    Each action by people and agents is on the audit trail with its evidence and reason. The examiner pack collects the 9 documents and each tree version, masks dates of birth and ID numbers, attaches each decision with its maker and checker, writes the trail and seals it: 46 pages and a CSV with a fingerprint. Internal audit and BSA Officer packs sit alongside.

Who it’s for

Five seats around one legal-entity certification

Five people at a commercial bank who carry one certification: what their week looked like, and what it looks like now.

KYC analyst
Records each decision, as the maker
Before
Verifies 25 to 30 certifications a day and builds the ownership chart by hand for each layered one, multiplying stakes in a spreadsheet.
Now
Opens a tree already built twice, with each person's working and each factor's source, and spends the time on the gap and the request.
KYC quality control reviewer
Approves requests and decisions, as the checker
Before
Samples files later, often after the account is open, and redoes the arithmetic to see whether it holds.
Now
Approves each customer request before it is sent and each decision before the customer record changes, with the evidence checklist in view.
Commercial relationship manager
Keeps the client informed
Before
Relays requests to the client by email with no standard wording, and chases the reply while the account waits.
Now
Is copied on one approved request in plain words and sees its status, without restricted notes or decision buttons.
BSA officer
Owns the CDD procedure
Before
Answers examiners for why each owner was, or was not, verified, from files that hold a checkbox rather than the reasoning.
Now
Sets the ownership line by risk, approves each threshold change, and hands examiners a sealed pack with the math and the trail.
Internal auditor
Tests CDD files each quarter
Before
Wants the tree as it stood on the day the account opened, and gets the file as it stands today.
Now
Steps through each version of the tree by date, with what changed, why and by whom, and builds a separate pack for audit.
The agents

Two agents compute each stake; five more read, verify and draft

The tree is built twice from the documents, and the certification is checked against it; the analyst decides and QC approves.

Document Reader agent

Reads the certification, operating agreements, membership ledgers, cap tables, trust agreements and registry extracts, and extracts each stake and officer designation with its exact passage and page.

  • Never infers a stake that is not written
  • Marks a missing page as missing
Ownership Builder agent

Builds the ownership tree and computes each person's effective ownership through all layers: it multiplies along each path, adds the paths, solves loops exactly and writes the working out.

  • Rounds only at the last step
  • Never settles a holder alone
Ownership Checker agent

Recomputes each effective percentage independently, from the documents, on a different model, and compares its result with the Builder's only after its own is written.

  • Never sees the Builder's numbers first
  • Holds the file for an analyst if any holder differs by more than 0.05 percentage points
Structure Risk agent

Flags circular ownership and solves the loop, nominee signs such as one registered-agent address behind several entities, trusts and their trustees, and articles that allow bearer shares.

  • Flags and explains; never decides a customer is a risk
  • Hands enhanced due diligence to the BSA Officer
Identity Verification agent

Verifies each person to identify with the CIP elements, screens people and entities against OFAC, and explains each discrepancy.

  • Masks identifiers
  • Never clears a potential OFAC match; it goes to the sanctions team
Relief agent

Decides, for an existing customer opening another account, whether FinCEN's 2026 relief order means no re-verification is owed, and records the customer's confirmation and the reason.

  • Any red flag, a refused confirmation or a high risk rating means re-verify
  • An analyst confirms every determination
Outreach agent

Drafts the request for a corrected certification in plain words and reads the customer's reply on arrival, comparing it with the tree.

  • Never sends without QC approval
  • Never includes internal or restricted information
KYC Analyst

Records; a QC Reviewer approves.

Ask in plain words

Plain-word questions on an owner, a stake or a deadline

Ask about a person, a percentage or a deadline, or say what to prepare. Each answer points to the document and the rule. These answers use the sample data.

Why is the missing owner above 25%?

The owner holds 18% of the company directly and 60% of the family holding company, which holds 15% of the company. 60% × 15% = 9%, and 18% + 9% = 27.0%. The rule counts ownership held directly or indirectly. The Checker agent reached 27.0% on its own, from the same documents.

Why isn't the 40% member of the holding company identified?

That member holds 40% of the family holding company: 40% × 15% = 6.0% of the company, below the 25% line. The company is rated moderate risk, so the bank's 10% line for high-risk customers does not apply. The working is recorded with its reason code.

What if this customer were rated high risk?

The bank's procedure lowers the line to 10% for high-risk customers. The two minority owners, at 10.5% each, would then be identified and verified, and the trust at 12% would be reviewed through its trustee. The holding company member at 6.0% would stay below the line.

Which certifications are due today?

Three by 5:00 p.m.: this hotel group, with an owner missing; a cold-storage company whose ownership loop puts one person at 26.1%; and a restaurant group where the two agents disagree on one member. A fourth file is past its service level and with the team lead.

The screens

Ownership tree, certification check and decision screens

From the working solution, on its sample data. Pick one to see it large.

The ownership tree, with the math written outThe tree: each stake with its source, each person's working such as 18% direct + 60% × 15% = 27.0%, the 25% line, the control person, and two agents agreeing on all six holders.
The certification queueCertifications in four lanes, each with the agents' one-line finding, filters for discrepancies, layers, structure signs, relief and disagreements, and the service-level clocks.
The beneficial ownership certification against the evidenceCertified against the documents, person by person: one owner agrees, one 27.0% owner is missing, and why the bank cannot rely on the certification as signed.
The corrected-certification request, for QC approvalThe drafted letter to the customer, the agent's five checks on it, and the maker-and-checker chain: nothing is sent until QC approves.
The reply, read and matchedThe corrected certification signed and compared with the tree two minutes later: both owners match and the control person is unchanged.
UBO verification of each owner's identityThe four CIP elements for each person to identify, identifiers masked behind a logged reveal, one address difference explained, and OFAC screening of people and entities.
The verification decisionRecorded with a reason code and a 7 of 7 evidence checklist, approved by QC, then written to the client lifecycle system and the core.
The tree as of any dateFive versions from as certified to approved and written, each with what changed, why and by whom, exportable as of any date.
Structure signs that can hide an ownerCircular ownership solved exactly (24.0% ÷ 0.92 = 26.1%), one registered-agent address behind six entities, a trust whose trustee must be identified, and bearer shares held.
Existing customers under the FinCEN CDD rule reliefNew accounts for existing customers, each with the last verification, the customer's confirmation and whether re-verification is owed: six not owed, three to re-verify.
The audit trail and the examiner packEach action by people and agents with its evidence, and a sealed examiner pack: 46 pages and a CSV, identifiers masked, maker and checker on each decision.
Roles and separation of dutiesSix roles with what each can and cannot do, and a locked rule that maker and checker are always different people.
Governance

Beneficial ownership verification under two models and two people

Two computations must agreeThe Builder and the Checker compute each holder separately, on two models. Nothing is settled until they agree within 0.05 percentage points; a disagreement is held for an analyst with both workings and the passages that differ.
Each percentage cites its sourceEach stake on the tree and each factor in a person's working opens the passage it came from: Schedule A, an operating agreement section, a ledger or a registry extract. Opening a source is logged.
Maker and checker are two peopleThe KYC Analyst records each decision and the QC Reviewer approves it. The same applies to each request sent to a customer and each change to the customer record, and the BSA Officer approves threshold changes.
Agents with written limitsAgents do not settle an owner alone, send to a customer without approval, clear a potential OFAC match or decide risk. Prompts and models are versioned, and a human override always takes a reason code.
Need-to-know, masked and confidentialDates of birth and ID numbers are masked, and each reveal asks for a reason and is logged. Restricted BSA information stays off customer-facing views, customer requests and the relationship manager's view.
Each version, kept and exportableAll actions by people and agents are on the audit trail, the tree is kept as of each date, and records are kept 5 years after the account closes. Examiner, internal audit and BSA Officer packs are sealed with a fingerprint.
Configuration

Beneficial ownership lines, tolerances and clocks, set by the BSA officer

The lines, tolerances and clocks each certification is checked against are settings. Each change is a new version with its author, and thresholds need the BSA Officer.

SettingDefaultChoose from
Ownership line25%25% · 20% (it can be lowered, never raised)
Line for high-risk customers10%10% · 15% · 20%
Two computations must agree within0.05 percentage points0.05 · 0.01 percentage points
Look through every layerOn, lockedNo depth limit; loops are solved, not cut
Certification to approved decision2 business days1 · 2 · 3 business days
Escalate to the team lead4 business hours left4 · 8 business hours
Customer reminders2 and 5 business days2 and 5 · 3 and 7 business days
Mask dates of birth and ID numbersOnOn · Off; a reveal asks for a reason and is logged
Connections

Systems the ownership tree reads from and writes back to

Client lifecycle management systemcases, documents and the client portal for requests and replies
Core banking systemthe customer record: beneficial owners and control person, written after QC approval
Corporate registry data serviceregistry extracts for each entity in the tree
Document imagingoperating agreements, ledgers, trust agreements and IDs, each page cited
Identity verification servicethe CIP elements for each person to identify
OFAC screening servicepeople and entities, against the current lists
What it changes

Files computed twice and corrected certifications decided within a day

Each figure carries its label: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
100%
of legal-entity files with two independent computations that agree before any owner is settled
Every file
computed twice
target
0
the design goal for accounts opened with a 25% owner missing from the certification and no recorded reason
target
1business day
from certification to approved decision when it needs correcting, against a 2-day service level

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate, or a vendor figure (a 2024 vendor survey of corporate treasurers: 41 days on average to open a business account, 87% having abandoned an application) · “typical” = published figures (FinCEN's regulatory flexibility analysis for the CDD Rule: about 20 minutes per new legal-entity account). The staff hours are our estimate from the chart above: 5.5 hours by hand and 0.7 hours with the agents on one layered certification. Rules named for context: the FinCEN CDD Rule, 31 CFR 1010.230 (25% owners, one control person, five-year records); the CIP rule, 31 CFR 1020.220; FinCEN exceptive relief order FIN-2026-R001 (February 13, 2026); FinCEN's interim final rule on beneficial ownership information reporting (March 2025). Names on the screens are sample data.

Questions

Beneficial ownership answers on indirect stakes, trusts and the relief order

What is beneficial ownership verification?

Beneficial ownership verification is how a bank identifies and verifies each person who owns 25% or more of a legal-entity customer, directly or indirectly, and one person who controls it, under the FinCEN CDD Rule (31 CFR 1010.230). Beneficial Ownership Verification does this work with seven agents: they read the certification and the entity's documents, build the ownership tree twice on two models, write out each person's math with its sources and verify each owner's identity. A KYC analyst records the decision and a QC reviewer approves it.

How does it calculate indirect beneficial ownership through a holding company?

It multiplies the stakes along each path, adds the paths and rounds only at the end: 18% held directly plus 60% of a holding company that owns 15% is 27.0%. A loop is solved exactly rather than cut, so in a sample cold-storage company a single pass gives 24.0% and the loop gives 26.1%. A second agent on a different model recomputes each holder from the documents, and the two must agree within 0.05 percentage points.

What happens when the two agents disagree?

The file is held for an analyst with both workings side by side. In a sample restaurant group the Builder reached 25.0% for one member from the operating agreement and the Checker 24.6% from the cap table, which leaves out units issued to that member a few days before the table was dated. The analyst chooses the governing document, the agreement or the cap table, or asks the customer, records a reason and an override code, and QC approves.

What happens when a beneficial ownership certification is wrong?

The certification is compared with the evidence, person by person, with each difference in plain words. The Outreach agent drafts the corrected-certification request from the customer's own documents, a QC reviewer approves it before it is sent, and the reply is read and compared with the tree when it arrives.

Does it apply FinCEN's 2026 relief for existing customers?

Yes, file by file. For an existing customer opening another account, the Relief agent reads the prior verification, the customer's confirmation and any facts that would reopen it, and says whether re-verification is owed under FIN-2026-R001 of February 13, 2026. Any red flag, a refused confirmation or a high risk rating means re-verify, and an analyst confirms every determination or overrides it with a reason.

Who is the beneficial owner when a trust owns 25% or more?

Under the CDD Rule, the trustee counts for the ownership prong. The Structure Risk agent finds the trust and its trustee in the documents: in a sample dental practice a family trust holds 40%, so its trustee must be identified and verified.

Can an agent settle an owner or write to the customer on its own?

No. The agents propose, show their working and cite their sources; they do not settle an owner alone, send anything to a customer without approval, clear a potential OFAC match or decide risk. The KYC Analyst records each decision, a QC Reviewer who did not make it approves it, and the BSA Officer approves threshold changes.

What goes into building it for our bank?

The Agentic Solution Engine builds and deploys it from your requirements and documents: your CDD procedure, your reason codes and a sample of past certifications and entity files. It goes live once each quality gate has passed. We will walk you through it on your own certifications first.

Test beneficial ownership verification
on certifications you approved.

We'll run Beneficial Ownership Verification on a sample of your own past certifications and entity documents.