Closing funds wire verification
How do we confirm the settlement agent's wire instructions through a verified channel before funds move, so a changed email cannot redirect the closing funds?
Never fund on instructions that arrived by email. Callvu takes the settlement agent's wire instructions through its verified onboarding record or a secure link bound to the agent's known contact, confirms them by an independent channel (a call to the number on file, not the number in the email, or a verified portal), compares them with the instructions on prior transactions with that agent, flags any change, holds funding until the verification is recorded by a named person, and tells the borrower how to verify their own wire.
In scopeComplex: multi-party handoffsCallvu moves: chase and verify, decide, write back
Last updated November 7, 2026.
The problem today
The 'updated wire instructions' email came from the settlement agent's address, and the closing funds went to a fraudster.
Business email compromise targets closings because the money is large and the deadline is real. A compromised or spoofed email from the settlement agent, the title company or the lender's own closer sends new wire instructions a day before closing. The funder, under time pressure, uses them. The funds are gone within hours.
The defense is procedural: instructions come only through a verified channel, every change is confirmed by an independent call to a known number, and funding waits for a named person's recorded verification. Under UCC Article 4A the lender's own security procedure for its outgoing wires is the standard its bank holds it to; for the closing wire, the lender is the sender and bears the loss of a wire it sent to the wrong account.
The procedure exists at most lenders. The process is what makes it run every time.
How it runs
From the requestto the system of record.
The closing is scheduled and the funder needs the settlement agent's wire instructions for the closing funds. Callvu opens the verification case.
- Settlement agent
- Provides the instructions through the verified channel and confirms them on the independent call.
- Funder
- Records the verification and releases the wire only on a recorded verification by the named person.
- Borrower
- Receives the lender's guidance on verifying their own funds-to-close wire.
- Callvu
- Takes instructions through the verified channel, compares, flags, routes the verification and holds funding.
Chase and verify the channel
The instructions are requested from the settlement agent through the agent's verified onboarding record (the known bank account on file) or a secure link bound to the contact details verified at onboarding; instructions received by email are not accepted as instructions and trigger the verification instead.
Classify changes
The instructions are compared with the agent's record and prior transactions: the bank, the account name and number, the routing number; any change, or a first transaction with the agent, is classified as requiring independent confirmation.
Decide: independent confirmation
A named person calls the agent at the number on file (never a number in the email or the instructions), confirms the account details read back, and records the call (the person, the number, the time, the confirmer) in the Decision Desk; the outcomes are verified, or not verified with a hold. The agent's record is updated only on a verified change.
Write back and fund
The verified instructions, the comparison and the confirmation record are written to the loan, the funding process releases on them, and the borrower is sent the lender's guidance on confirming their own wire by calling a known number.
Where it ends: The closing funds went to instructions received through a verified channel and confirmed by a named person on an independent call, with the record on the loan, and a changed instruction could not have redirected them. The Decision Trace shows the channel, the comparison and the confirmation; the Audit Trace shows every step and person. The systems named here stay the system of record; Callvu writes to them and keeps the trace.
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 settlement agent's verified record or a secure link bound to it; an email is a trigger, not a source.
The back office
The funder releases only on a recorded verification; the agent's record stays clean.
The Decision Desk
- The named person records the independent confirmation in the Decision Desk with only verified or not verified (hold) as outcomes; a not-verified case escalates before the closing date.
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.
What happens to wire instructions received by email?
They are not used. They trigger the verification: the instructions are taken through the verified channel and confirmed by a named person on an independent call to a number on file.
Is every closing verified?
Every change and every first transaction with an agent is confirmed by call; every funding releases only on a recorded verification.
What about the borrower's wire?
The borrower receives the lender's guidance on confirming their funds-to-close instructions by calling a known number, from the process.
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.