Beneficial ownership certification update
How do we update beneficial ownership on a business account when ownership or control changes, with a new certification and verified owners?
Make the update a case that starts from the change. When the business reports a change, or a trigger reveals one, Callvu prefills the current ownership, asks the business to certify what changed, identifies and verifies each new owner on their own phone, and writes the updated owners and certification to the entity record in the core and the BSA system.
In scopeSimpleCallvu moves: prefill, chase and verify, write back
Last updated November 6, 2026.
The problem today
The business changed hands a year ago, and the bank's record still names the old owners.
A company is sold, a partner buys out another, a new managing member takes control. The bank learns of it from a signature card update, a loan renewal, or not at all. When it does, a banker emails a blank certification form, the business returns it incomplete, and the new owner's identification arrives from a different email address weeks later.
The CDD rule requires the bank to update beneficial ownership information when it detects a change, on a risk basis, including identifying and verifying each new beneficial owner. A certification on file that names the wrong owners is the finding examiners look for first on legal entity customers.
The update touches two systems. The core holds the entity and its signers; the BSA system holds the owners and the risk rating. An update made in one and not the other is two records that disagree.
How it runs
From the requestto the system of record.
The business reports a change of ownership or control, or a trigger event (a signer change, a loan renewal, a KYC refresh, a document showing new owners) opens the case. Callvu prefills the current beneficial ownership record.
- Business customer
- The authorized representative certifies the updated ownership and control; each new owner identifies themselves on their own phone.
- Deposit operations
- Reviews exceptions and sees every entity with its current certification.
- Callvu
- Prefills, collects the certification, chases and verifies each new owner, and writes the update to the core and the BSA system.
Prefill the current record
The entity, its current beneficial owners (ownership prong and control prong) and the last certification date are prefilled from the BSA system and the core. The representative marks who is removed, who is added, and whether the control person changed.
Certify the change
The authorized representative completes the beneficial ownership certification for the updated ownership: each individual with 25 percent or more of the equity and one individual with significant control, with name, date of birth, address and identification number. The certification is signed on a process-controlled screen.
Chase and verify each new owner
Each new owner receives a link, provides an identification document, and is verified and screened against the government lists. The case shows who has not responded and for how long. A removed owner needs nothing from them.
Decide and write back
A verified update with no screening hit is written to the BSA system (owners, certification, date) and to the core (entity record) together. A screening hit or a verification exception routes to the BSA team in the Decision Desk before anything is written.
Where it ends: The entity's beneficial owners, the new certification and each owner's verification are current in the BSA system and the core, with the date and the trigger recorded. The Decision Trace shows what changed and how it was verified; the Audit Trace shows every request and answer.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The business reports the change in any channel, or a trigger in the bank's own systems opens the case. The representative and each new owner act on their own phones.
The back office
The BSA team receives only the exceptions. Both systems are updated from one certified record; nobody re-keys the owners twice.
The Decision Desk
- A screening hit or a verification exception on a new owner goes to the BSA team in the Decision Desk with the entity, the certification and only the allowed outcomes.
- An owner who has not responded is nudged, and the case escalates rather than lapsing.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
Questions
What buyers ask next,answered plainly.
Does the whole certification have to be redone?
The representative marks what changed against the prefilled record and signs a new certification for the updated ownership. New owners are verified; removed owners need nothing.
What opens an update?
The business reporting a change, or a trigger event in the bank's own systems: a signer change, a loan renewal, a KYC refresh, or a document that shows new owners.
Which system is the record?
The BSA system for the owners and the certification; the core for the entity record. Both are written from the same case.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.