Incoming wire exceptions

How do we clear incoming wires that fail to post, with the beneficiary research, the OFAC check and the post-or-return decision inside the day?

Make the exception a case with a cutoff. When an incoming wire does not post (a name and account mismatch, a closed account, a missing beneficiary, a sanctions screening hit), Callvu classifies the reason, runs the research against the core and the screening result, asks the customer to confirm where the policy allows, routes the post-or-return decision to the wire room in the Decision Desk with the cutoff visible, and posts or returns the funds with the record.

In scopeSimpleCallvu moves: classify, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 6, 2026.

The problem today

The wire sits in the exception queue, the customer calls about missing money, and the return goes out on day three.

Today, without Callvu

An incoming wire names a beneficiary whose account number does not match, or an account that closed last month, or an OFAC screening flags a name. It lands in the wire room's exception queue. Someone researches it when they can, calls the branch, and the branch calls the customer. The funds are posted late or returned late, and the sender's bank asks why.

The rules push in different directions. UCC Article 4A lets the beneficiary's bank rely on the account number if it does not know of a conflict, but the bank's policy may require research. OFAC requires a hit to be resolved before the funds move, and a true match means a block and a report within ten business days. Fedwire and the correspondent networks have their own return conventions and the bank's own cutoff.

Most exceptions are clerical. The ones that are not need the record of what was checked.

How it runs

From the requestto the system of record.

An incoming wire fails the automatic posting rules in the wire system. Callvu picks it up with the reason and opens the exception case with the day's cutoff.

Wire room: Decides post, return or hold in the Decision Desk with the research and the screening result in front of them.
Customer: Where the policy allows, confirms the expected wire and the sender on their phone.
Callvu: Classifies, researches against the core, attaches the OFAC result, chases confirmation, routes the decision with the cutoff, posts or returns and records.

Classify the exception
The reason is classified: a name and account number mismatch, a closed or restricted account, an incomplete beneficiary, a currency or format issue, or a sanctions screening hit. Each reason sets the research, whether customer confirmation is allowed, and the allowed outcomes.
Chase and verify
Callvu searches the core for the beneficiary by name, account and other identifiers, attaches the screening result (and for a hit, the match details), and where the policy allows, asks the named customer to confirm the expected wire and the sender through a link. The case shows the cutoff and the time left.
Decide
The wire room decides in the Decision Desk: post to the identified account, return to the sender with the reason, or hold for the sanctions review. A sanctions hit that is a true match blocks the funds and opens the OFAC reporting process; a false positive is cleared with the reason recorded.
Write back
The wire is posted or returned in the wire system and the core, the customer is told, the sender's bank receives the return message where applicable, and the case with the research, the screening and the decision is recorded.

Where it ends: The wire was posted to the right account or returned with the reason, before the cutoff, with the research and the screening result on the record. The Decision Trace shows the classification and the decision; the Audit Trace shows every step and time.

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

OFAC screening (31 CFR part 501 and the sanctions programs): A funds transfer that involves a blocked person or a sanctioned country must be blocked or rejected, not returned to the sender in the ordinary way; blocked property is reported to OFAC within 10 business days and annually. A screening hit must be resolved before the funds move, and a false positive is cleared with the reason recorded.
UCC Article 4A: beneficiary identified by name and number (UCC 4A-207): If a payment order identifies the beneficiary by both name and account number and they refer to different persons, the beneficiary's bank may rely on the number if it does not know of the conflict; a bank that does know must not pay on the number alone. The research and its result determine what the bank knew.
Funds transfer recordkeeping and the Travel Rule (31 CFR 1020.410 and 1010.410): The beneficiary's bank retains the payment order information it receives and, for transfers above the threshold, the originator and beneficiary information; the exception case keeps the order and the research with it.
Fedwire and correspondent return conventions and the bank's cutoff: Returns go through the same channel with the reason, and the bank's daily cutoff sets when a decision must be made so the return or posting is same-day.

Company policies

The exception reasons, the research steps and whether a customer may confirm an expected wire are the bank's wire policy and are applied by Callvu.
No funds move on a sanctions hit until it is resolved; a true match blocks and reports.
The post-or-return decision is made before the cutoff, with the time left visible.
The wire system and the core are the systems of record; the case holds the research and the decision.

Controls

Reason classification setting research and outcomes.
Core search for the beneficiary with the result attached.
Screening result attached, with true-match blocking.
Customer confirmation through a link where allowed.
Decision Desk with cutoff countdown.
Posting or return recorded with the reason.

Clocks and deadlines

Daily cutoff: The decision is made before the bank's wire cutoff; the case counts down to it.
OFAC blocked property report: Within 10 business days of blocking.
Record retention: Five years for the payment order information.

Documents and checks

The incoming payment order and the posting failure reason
The core search result for the beneficiary
The screening result and, for a hit, the resolution
The customer's confirmation where obtained
The wire room's decision with reason
The posting or return record

In the Decision Trace

The exception reason and the research it required.
The screening result and how a hit was resolved.
The decision, the person and the reason, against the cutoff.

In the Audit Trace

The wire's receipt and the exception time.
The research steps and the confirmation request.
The Decision Desk step with the time.
The posting or the return message.

The handoff

Between the front doorand the back office.

The front door

The wire system's exception queue is the front door; the customer meets the process only where a confirmation is allowed.

The back office

The wire room decides with the research done and the cutoff visible, instead of doing the research by phone.

The Decision Desk

The wire room decides post, return or hold in the Decision Desk with the research, the screening result and only the allowed outcomes for the reason.
A sanctions true match routes to the OFAC reporting process from the case.

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.

Can the bank post on the account number alone?

Under UCC Article 4A, if it does not know of a conflict between the name and the number. The research result is what the bank knows, and the wire room decides with it in view.

What happens on an OFAC hit?

The funds do not move until the hit is resolved. A true match blocks the funds and opens the reporting process; a false positive is cleared with the reason recorded.

How is the cutoff kept?

The case counts down to the bank's wire cutoff, and the wire room is nudged so the posting or return is same-day.

Related processes

Wire recall and fraud claims International remittance transfers ACH returns and notifications of change 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.