Returned deposit item handling
How do we handle a returned deposited item so the charge-back, the customer notice and the account decision happen the same day?
Treat the return as an event that runs its own process. When an item comes back, Callvu classifies the return reason, charges the item back with the fee the schedule allows, sends the customer the notice with the item and the reason, checks the account for a resulting overdraft or a hold decision, routes a redeposit or a hold to deposit operations where policy requires, and records the charge-back and the notice in the core.
In scopeSimpleCallvu moves: classify, write back
Last updated November 6, 2026.
The problem today
The item came back on Tuesday, the customer found out on Friday from an overdraft fee.
A deposited check is returned unpaid. Deposit operations works the return file in the morning, charges the account back, and prints a notice that goes out in the next mail run. The customer, who spent against the deposit, learns of it from the overdraft fees. Whether the return should trigger an exception hold on future deposits, or a redeposit attempt, is a judgment made differently on different days.
Reg CC sets the rules on both sides: the paying bank's return deadlines and the notice of nonpayment for large items, and the depositary bank's right to charge back and to place an exception hold on an account with a redeposited check or repeated overdrafts. The charge-back fee is a disclosed term. The customer notice is how the bank proves the customer was told.
Most returns are routine and identical. The ones that matter are the ones that signal fraud or a pattern, and they are found by reading the whole file.
How it runs
From the requestto the system of record.
A returned item arrives in the bank's return file from the clearing channel. Callvu picks up each item with its return reason and the depositor's account.
- Deposit operations
- Sees every return with its classification and action, and decides the cases the policy reserves in the Decision Desk.
- Customer
- Receives the notice with the item, the reason and the amount charged back, and any hold notice.
- Callvu
- Classifies, charges back, notifies, checks the account, routes exceptions and records.
Classify the return
The return reason (insufficient funds, account closed, stop payment, refer to maker, altered or fictitious, duplicate presentment, endorsement) and whether this is a first or a redeposited return are classified. The classification sets the action: charge back and notify, redeposit where the reason and the policy allow it, or route to the fraud team for an altered or fictitious item.
Charge back and notify
The item is charged back to the account with the fee the account's schedule discloses, and the notice with the item image, the reason, the amount and the fee goes to the customer the same day in the channel they consented to.
Decide on the account
Callvu checks the consequences: an overdraft caused by the charge-back, a pattern that qualifies for a Reg CC exception hold on future deposits (a redeposited check, repeated overdrafts), or a relationship the policy treats differently. A hold decision or a redeposit goes to deposit operations in the Decision Desk where policy requires; otherwise the rule applies.
Write back
The charge-back, the fee, the notice, the hold decision and any redeposit are written to the core and the item record, and a return that signals fraud opens a fraud case with the item attached.
Where it ends: The item is charged back with the disclosed fee, the customer was notified the same day, the account consequences were decided by rule or by a person, and every step is recorded in the core. The Decision Trace shows the classification and the decisions; the Audit Trace shows the notice and the writes.
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 return file from the clearing channel is the front door. The customer meets the process in the notice.
The back office
Deposit operations sees every return with its action and decides only the reserved cases. The core carries the charge-back, fee, notice and hold from Callvu.
The Decision Desk
- A hold decision the policy reserves, a redeposit request, or a return on a relationship account goes to deposit operations in the Decision Desk with the item, the account history and only the allowed outcomes.
- An altered or fictitious item goes to the fraud team as a case, with the image attached.
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.
When does the customer find out?
The same day the return is processed, with the item image, the reason and the amount, in the channel they consented to.
Can a returned check be redeposited?
Where the return reason and the bank's policy allow it. The decision is recorded, and a redeposited check can carry a Reg CC exception hold with its notice.
What happens with a suspected fraudulent item?
The classification opens a fraud case with the item attached, and the account check decides whether a hold is warranted.
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.