A verification of deposit is worth something because of who handled it. The lender asks the institution directly, the institution signs it and returns it, and the borrower never touches the form. That chain is the evidence. When the institution will not play — because the branch stopped doing them, because the account is online-only, or because the borrower banks somewhere with no correspondent desk — the file needs a substitute that carries the same weight.
Statements can carry it. What they cannot do is carry it half-way: a set that covers six weeks, or is missing the page with the ending balance, or arrives as four screenshots, is not a lighter version of a verification. It is a document with a hole in it, and the whole file waits for the hole to be filled.
What the letter contains that the statement must reproduce
The rules differ between programmes, so the checklist below follows Fannie Mae's Selling Guide, which is the version most often quoted back at a processor. Substitute your own programme's wording if it differs; the shape is the same everywhere.
| Element | Why the reviewer needs it | Where it usually hides |
|---|---|---|
| Name of the depository institution | Establishes who is confirming the balance | Letterhead of page one only — later pages carry just a footer |
| Borrower as the account holder | Links the money to the person being underwritten | Joint accounts and trade names that do not match the application |
| At least the last four digits of the account number | Distinguishes two accounts at the same bank | Removed by the borrower when redacting a statement |
| The period the statement covers | Decides whether the coverage requirement is met | Shown as a cycle end date only, with the start implied |
| Every deposit and withdrawal | Allows the balance to be recomputed | Truncated statement with a batching line such as 14 other items |
| The ending balance | The only figure that ties the set together | Summary box, which can disagree with the last transaction row |
The fifth row is where most sets fail. Statements truncated with an "other transactions" line look complete and cannot be recomputed, which makes them closer to a summary than to evidence. Ask for the extended version before the reviewer does.
The coverage period and the stale-statement problem
In that framework a purchase file needs the most recent full two months of activity and a refinance the most recent full month, with the latest full quarter where the account reports quarterly. The period is measured from the statement cycle, not from when the file was assembled, which produces the recurring end-of-file problem: statements collected at application are two cycles old by the time the file is ready.
The remedy written into the same framework is a recent bank-generated form showing the last four digits, the balance and a date, requested when the newest statement is more than 45 days older than the application. It is a supplement, not a replacement: it re-dates the balance, and the statements still carry the history.
The two checks that prove a statement set is complete
Completeness is the part a reviewer can test in ten seconds, which is exactly why they test it first.
Per statement: previous balance + deposit - withdrawal = row balance
At the end: last row balance = ending balance printed in the summary
Across months: closing balance (month N) = opening balance (month N+1)If the last row and the summary box disagree, the page is truncated or a row was dropped — both are invisible on a scan and obvious on the arithmetic. If a month-to-month link is short by exactly one month's activity, a statement is missing rather than misread. And if the link is short by an amount that matches nothing at all, that is the moment to stop and read the pages before sending anything to a reviewer.
Where the borrower-supplied statement still needs a second source
A statement downloaded by the borrower is normally acceptable in form. It is not independent in origin. For files where the balance is doing real work — a down payment, a reserve requirement, a closing condition — the point of a verification of deposit was never the numbers on the page; it was that the institution vouched for them. A statement set proves consistency, and consistency is not the same as authenticity.
That distinction decides which substitute is good enough. A gift letter with three months of statements is usually plenty. A file where the funds have to be seasoned for two months and the whole purchase depends on them is the case for a direct verification or an accepted vendor, because a careful borrower could produce consistent statements and a bank would not.
When not to use us
- You need the institution to confirm anything. We read documents. We cannot call a bank, and an extraction result is not a verification of deposit.
- The account is with an institution that still issues Form 1006 promptly. Order the form; it is a stronger document than any substitute.
- You need one balance on one page. Read it, write it down, and note the date. The conversion earns its cost across a set of statements you will actually recompute.
Where SheetParser fits
Upload the set and each statement is checked against its own arithmetic: the running balance is recomputed row by row, the summary figure is compared to the last row, and consecutive months are chained so a gap appears as a gap rather than as a wrong number. Rows that do not close, and pages that look truncated, come back on a review list with the page they sit on, and the printed text of every cell is kept alongside the numeric value rather than replaced by it.
What that gives you is a set you can send with a statement of what was checked, rather than a set you hope is complete. If the same statements are also supporting income, the deposit-to-income workflow starts from the same month-by-month tie-out, and the continuity check covers the gap analysis in more detail.