Wire recall and fraud claims

How do we handle a wrong or fraudulent wire report so the recall reaches the beneficiary bank in minutes and the claim is decided on the record?

Treat the report as a race and a case at once. When a sender reports a wrong or fraudulent wire, Callvu identifies them, prefills the wire, classifies the claim (sender error, business email compromise, account takeover, scam), sends the recall request to the beneficiary bank through the wire channel immediately, takes the sender's statement on their phone, routes the fraud team's decision on liability and reimbursement, tracks the recovery, and records the outcome in the core and the fraud case.

In scopeComplex: multi-party handoffsCallvu moves: chase and verify, classify, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 6, 2026.

The problem today

The recall is a phone call to the wire room, and the money left the beneficiary account an hour ago.

Today, without Callvu

A business controller realizes the vendor's new bank details in yesterday's email were a fraud. They call the branch. The branch calls the wire room. The wire room drafts a recall message. By the time it reaches the beneficiary bank, the funds have been moved. The customer then asks who is liable, and the answer depends on facts nobody wrote down at the time.

Under UCC Article 4A the sender's bank is bound by a payment order it accepted if it was verified under a commercially reasonable security procedure, and the sender's remedy for a fraudulent order depends on whether the procedure was followed; an error by the sender in the beneficiary's account number is the sender's loss if the bank paid to the number. Recovery depends on the beneficiary bank's cooperation and speed. A recall is a request, not a right, and minutes decide it.

Business email compromise, elder scams and account takeover produce the same report with different liability. A process that classifies at intake preserves the facts and the options.

How it runs

From the requestto the system of record.

A sender reports a wrong or fraudulent outgoing wire in any channel. Callvu identifies the sender, prefills the wire from the wire system, records the report time, and opens the case.

Customer: Reports the wire, states what happened, and signs the statement on their phone.
Wire room: Sends the recall through the wire channel from the case and tracks the beneficiary bank's response.
Fraud team: Classifies the loss, decides liability and reimbursement in the Decision Desk, and files the reports the facts require.
Beneficiary bank: Receives the recall request and returns the funds, holds them, or declines.
Callvu: Prefills, classifies, sends the recall at once, chases the statement, routes the decision, tracks recovery and records.

Prefill and recall at once
The wire (amount, date, beneficiary, beneficiary bank, the security procedure used, who initiated and approved) is prefilled from the wire system. The recall request, in the format the wire channel requires and with the reason code, goes to the beneficiary bank the moment the report is authenticated, before the statement is signed. The time sent is recorded.
Classify the claim
The claim is classified: sender error (wrong account number or beneficiary), business email compromise (fraudulent instructions), account takeover (an order the sender did not make), or a scam the sender was induced into. The classification sets the liability analysis under Article 4A and the bank's policy, the reports the facts require, and the evidence to collect.
Chase and verify
The sender's statement, prefilled, is signed on a process-controlled screen. The evidence for the classification (the fraudulent email, the device and session data, the callback and dual approval records from the original wire, a police report) is collected with links and from the bank's own systems.
Decide
The fraud team receives the case in the Decision Desk with the wire, the classification, the security procedure record, the evidence and the recovery status, and chooses among the allowed outcomes: reimburse, reimburse in part, deny with the reason under Article 4A and the account agreement, or hold pending recovery. The decision and the person are recorded.
Track recovery and write back
The beneficiary bank's responses (funds held, returned, unavailable) are tracked, the returned funds are credited, the decision is posted, and the case with the recall time, the evidence, the decision and the recovery is written to the core and the fraud case. A SAR and a report to the authorities run from the case where the facts require.

Where it ends: The recall reached the beneficiary bank minutes after the report, the sender's statement and the evidence are on the case, liability was decided on the record, and the recovery is tracked to its end. The Decision Trace shows the classification and the decision; the Audit Trace shows the recall time and every step.

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.

Regulations

UCC Article 4A: authorized and verified payment orders (UCC 4A-202 and 4A-203): A payment order received by the bank is effective as the customer's order if it was authorized, or if the bank accepted it in good faith in compliance with a commercially reasonable security procedure agreed with the customer. If the order was not authorized and the procedure was followed, the customer bears the loss unless it proves the order was not caused by a person with access to its facilities; the bank's record of the security procedure on the original wire is the evidence.
UCC Article 4A: erroneous orders and misdescribed beneficiaries (UCC 4A-205 and 4A-207): A sender who gives a beneficiary account number that does not match the beneficiary's name bears the loss if the beneficiary's bank paid to the number without knowing of the conflict; a sender's error in the amount or the beneficiary is the sender's loss if the security procedure would not have caught it. Recovery is by recall and restitution, not by right.
Cancellation and amendment of payment orders (UCC 4A-211): A payment order may be cancelled or amended with the receiving bank's agreement after acceptance; the recall request is that request, and the beneficiary bank's cooperation governs the outcome.
BSA suspicious activity reporting (31 CFR 1020.320) and FinCEN business email compromise guidance: A fraudulent wire meeting the threshold is reported on a SAR within 30 days of detection; FinCEN's advisories ask for specific indicators on business email compromise, which the classification captures.

Company policies

The recall goes out the moment the report is authenticated, before any statement or decision.
The classification and the security procedure record from the original wire are the basis of the liability decision.
The reimbursement outcomes and who may decide them are the bank's fraud policy, applied in the Decision Desk.
A SAR and law enforcement reporting run from the case where the facts require.
The core and the fraud case are the systems of record; the wire system holds the original order and the recall.

Controls

Authentication and prefill from the wire system.
Immediate recall with the time recorded.
Classification setting the liability analysis and the evidence list.
Statement signed on a process-controlled screen.
Security procedure record attached from the original wire.
Decision Desk outcomes limited to the policy.
Recovery tracking and SAR referral.

Clocks and deadlines

Recall: Sent on authentication of the report; the minutes to send are on the record.
SAR filing: Within 30 calendar days of detection where the threshold is met.
Decision: On the policy's service level, with the sender told the status and the recovery updates as they arrive.

Documents and checks

The original wire with its security procedure, initiator and approver records
The recall request and the beneficiary bank's responses
The sender's signed statement
The evidence for the classification (emails, session data, callback records, police report)
The fraud team's decision with reason
The credit, the recovery record and the SAR reference where filed

In the Decision Trace

The classification and the liability analysis it set.
The security procedure record and whether it was followed.
The decision, the person and the reason.
The recovery outcome.

In the Audit Trace

The report and its time.
The recall sent and each response.
The statement signature and each upload.
The Decision Desk step and the postings.

The handoff

Between the front doorand the back office.

The front door

Any channel, including the branch where the customer first calls. The report is authenticated and the recall is sent before the customer hangs up.

The back office

The wire room sends from the case; the fraud team decides with the evidence and the security procedure record in front of them.

The Decision Desk

The fraud team decides liability and reimbursement in the Decision Desk with the wire, the classification, the evidence and the recovery status, and only the allowed outcomes.
A case the orchestrator flags (for example, a pattern across wires) is escalated before the decision.

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.

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Banca Transilvania automated more than 100 workflows with Callvu.

BNK-04

Bank Leumi digitized all loan application and servicing workflows within six months, and dozens more processes since.

BNK-01

Questions

What buyers ask next,answered plainly.

How fast does the recall go out?

The moment the report is authenticated, from the case, through the wire channel, with the time recorded. The sender's statement follows; it does not gate the recall.

Who is liable for a fraudulent wire?

It depends on the classification and whether the bank's security procedure was followed under UCC Article 4A. The case attaches the procedure record from the original wire and the fraud team decides with the policy's outcomes.

What if the beneficiary bank will not return the funds?

The responses are tracked on the case, the fraud team decides on reimbursement with that status in view, and the sender is told. Law enforcement reporting runs from the case.

Related processes

Account takeover recovery Incoming wire exceptions International remittance transfers Try it in the sandbox All banking and credit unions 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.