Letter of explanation for large deposits and credit items
How do we get a signed letter of explanation and sourcing documents for each flagged deposit or credit inquiry, and get the underwriter's decision on the record?
Make each flag its own request with its own evidence. When asset verification flags a large deposit or the credit report shows an inquiry, Callvu creates a request to the borrower for a signed explanation and the sourcing documents the guideline accepts for that kind of deposit (or the statement that no new credit was opened), reads and matches what comes back, and routes the underwriter's decision in the Decision Desk: source accepted, deposit excluded from funds, or more needed. The decision and the evidence sit on the loan.
In scopeComplex: multi-party handoffsCallvu moves: classify, chase and verify, decide, write back
Last updated November 7, 2026.
The problem today
The letter of explanation says 'savings', and the underwriter accepts it or does not depending on the day.
The underwriter conditions the loan for an explanation of a deposit and an inquiry. The processor emails the borrower. A letter comes back saying the money was from savings, unsigned, with no document. The underwriter asks again. The borrower is annoyed. At the end, the deposit is accepted on a signed letter that explains nothing, and the quality control review flags the file.
The guidelines are specific about what sources are acceptable and what documents prove them: a gift needs a letter and transfer evidence; a sale needs the contract and the proceeds; a transfer needs the other account; a loan is a liability to count. An inquiry needs a statement that no new credit was obtained, or the new liability. The explanation is the borrower's; the evidence is what clears it.
A structured request gets both in one go.
How it runs
From the requestto the system of record.
Asset verification flags a deposit above the threshold, or the credit report shows an inquiry within the lookback. Callvu opens a request per flag.
- Borrower
- Explains each flagged item on a structured screen, signs, and uploads the sourcing documents.
- Processor
- Sees each request's status and reviews only what the matching could not resolve.
- Underwriter
- Decides each flag in the Decision Desk with the explanation and the evidence.
- Callvu
- Creates the requests, reads and matches the responses, routes the decision and records it.
Classify each flag
A deposit flag carries its date and amount; the borrower is asked to choose the source type (gift, sale of an asset, transfer from another account, bonus or commission, tax refund, loan, other), and the source type sets the documents the guideline accepts. An inquiry flag asks whether new credit was obtained and, if so, for the terms.
Chase and verify
The borrower completes the explanation on a structured screen, signs it, and uploads the documents for the chosen source; each is read on arrival and matched to the deposit (the amount and date on the transfer, the sale proceeds against the deposit, the donor's statement for a gift). A mismatch is sent back with what is needed.
Decide
The underwriter decides each flag in the Decision Desk with the explanation, the evidence and the match result, and only the allowed outcomes: accept the source, exclude the deposit from the funds to close, count a new liability, or request more. The decision and the reason are recorded.
Write back
The signed explanation, the documents, the match and the decision are filed to the loan in the LOS under the condition they clear, and the asset and liability totals are updated for underwriting.
Where it ends: Every flagged deposit and inquiry has a signed explanation, the sourcing documents the guideline accepts, and the underwriter's recorded decision on the loan. The Decision Trace shows the source classification, the match and the decision; the Audit Trace shows each request and response.
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
A link to the borrower per flag, from the asset verification or the credit review.
The back office
The processor sees only unresolved matches; the underwriter decides with the evidence in front of them.
The Decision Desk
- The underwriter decides each flag in the Decision Desk with the explanation, the evidence and the match, and only accept the source, exclude the deposit, count a liability, or request more.
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 does the borrower have to provide?
For each flagged deposit, a signed explanation with the source type and the documents the guideline accepts for that source; for an inquiry, whether new credit was obtained and the terms if so.
Can a signed letter alone clear a deposit?
No. The evidence is matched to the deposit, and the underwriter decides with both in view.
What are the underwriter's options?
Accept the source, exclude the deposit from the funds to close, count a new liability, or request more, each recorded with a reason.
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.