A bad bank statements mortgage file can still close when the problem is explainable, isolated and documented. A one-time NSF fee or a sourced cash deposit usually clears with a letter. A pattern, such as repeated overdrafts, a falling balance or an undisclosed loan payment, needs time or a different structure, and some problems end the file.
What makes bank statements bad in a mortgage underwriter's eyes?
Bank statements look bad to an underwriter when they show behavior that weakens repayment ability or leaves money unexplained. The cause is rarely one item. It is a pattern, an undisclosed obligation, or a deposit with no source. The statements themselves are only a record of what the borrower did.
Underwriters read statements for five kinds of trouble:
- NSF and overdraft events. A returned item or an overdraft fee suggests the borrower ran out of money. One in twelve months is a footnote. Several in a quarter is a pattern.
- Large or unusual cash deposits. Cash that cannot be tied to a paycheck, a sale or a withdrawal elsewhere has no paper trail, and a lender cannot count it.
- A falling balance. If the ending balance drops month after month, the borrower may be spending more than they earn, and reserves may be thinner than the application claims.
- Gambling debits. Frequent casino, sportsbook or betting-app charges raise a question about how stable the borrower's cash is, whatever the dollar amount.
- Payments to lenders the application never mentioned. A monthly payment to a lender that is not on the credit report or the loan application points to a debt that is missing from the debt-to-income ratio.
A statement can also be bad for a reason that has nothing to do with the borrower. A missing page, a cropped screenshot or a statement from the wrong account makes the file unreadable even when the money behavior is fine. Those problems are fixed by sending a better document, and the broker pre-submission review of borrower statements is where a broker should catch them.
Bad is relative to the program
The same statement can pass one program and fail another. Programs set their own tolerance for NSF events, their own lookback and their own view of cash deposits. A conventional file that needs a clean two-month history reads a bumpy March differently than a twelve-month bank statement program that averages deposits across a year. Ask the lender's guideline, not a rule of thumb, before you tell a borrower a statement is a problem. Uneven deposits are also normal for a business owner, and reading self employed bank statements shows how to tell a seasonal dip from a real decline.
What the underwriter wants to see instead
An underwriter wants a statement that supports the story on the application: income that arrives on a schedule, expenses the borrower can cover, enough left over for the down payment and reserves, and no surprises. When the file has a surprise, the underwriter wants it named by the borrower in writing and backed by a document. How a lender reads a clean file is covered in what mortgage lenders look for on bank statements.
Letters of explanation that rescue bad bank statements
A letter of explanation is a short signed statement from the borrower that says what a statement item was, why it happened and what proves it. It rescues a file when the item is isolated and a document backs it up. It does not rescue a pattern, and it never replaces a source document.
What a useful letter contains
A letter that works is specific. It names the date, the amount and the transaction as the statement shows it, then answers three questions:
- What was this item?
- Why did it happen?
- What document proves it, and is that document attached?
Compare two letters about the same $4,500 cash deposit. The first says "this was money from a friend." The second says "On March 9 I deposited $4,500 in cash. I sold a used pickup truck to a private buyer on March 8. The bill of sale and a copy of the signed title transfer are attached." The second gives the underwriter something to check. The first gives them nothing.
Items a letter usually fixes
A letter tends to clear problems that are one-time, small against the borrower's income and easy to document:
- A single NSF or overdraft fee with a reason, such as a payroll deposit that posted a day late.
- A cash deposit tied to a sale, a refund or a withdrawal from another account the borrower also holds.
- A transfer between the borrower's own accounts, shown by matching entries on both statements.
- A payment to a lender, once the borrower names the debt and the file adds it to the debt-to-income ratio.
Items a letter does not fix
A letter does not turn a pattern into an accident. Five NSF fees in six months is not explained by a sentence about a busy season. A letter also cannot source money that left no record, and it cannot make a gambling habit disappear. If the underwriter asks for a letter and the honest answer is "I do not know where that came from," the borrower should say so to the broker before anything is written.
Who writes it
The borrower writes the letter and signs it. A broker can draft questions and suggest structure, but putting words in a borrower's mouth that the borrower did not say creates a worse problem than the one being explained. Read the draft back to the borrower and ask if every sentence is true.
Where the letter goes
Send the letter with the supporting document in the same upload, labeled with the statement month it refers to. Underwriters work from a list of conditions, and a letter that arrives alone, weeks later, forces another round. What lenders ask for after submission is covered in statement conditions during mortgage approval.
Waiting out bad statement months before a mortgage application
Waiting means holding the application until the bad months roll out of the lookback window or a clean run builds behind them. It fits problems that are real but temporary, such as a cluster of overdrafts after a job loss, and it fails when the borrower keeps the same habits.
How the window works
Most programs look at a fixed number of months of statements, commonly two for a conventional purchase and twelve or twenty-four for a bank statement program. A bad month inside that window is read. A bad month outside it is not. If a borrower had three NSF events in a single bad quarter and the program looks at twelve months, waiting nine months moves the quarter out of view. Confirm the lookback in the lender's own guideline before you promise the borrower a date.
What the borrower should do in the meantime
Waiting only helps if the borrower changes what the statements show. Useful steps, in order of impact:
- Keep the balance above the level where overdrafts happen, even if that means moving the due dates on recurring bills.
- Turn on low-balance alerts and stop using the overdraft line as spending money.
- Deposit all income into one account the lender will see, rather than spreading it across several.
- Avoid large cash deposits, new debt and moving money between accounts without a record.
- Pull the statements monthly and read them the way an underwriter would.
When waiting is the wrong advice
Waiting is wrong when the problem is not in the window, such as a missing page or an undisclosed debt. It is also wrong when the rate market or a purchase contract sets a deadline the borrower cannot move. In that case the broker should ask whether another program with a longer lookback, or a different lender with a looser tolerance, fits the file better. The guide to comparing bank statement lenders shows how to line lenders up on lookback and overlays.
A short example
Suppose a borrower has two overdrafts in January and one in February of last year, then a clean run since. Under a program that counts occurrences over the last twelve months, the file shows three events until January rolls off, then one. The broker can submit now with a letter, or wait two months and submit with a cleaner picture. Which is better depends on the lender's limit and the closing date, not on the broker's guess.
Which bad bank statements end a mortgage file?
A mortgage file ends when the statements show a problem that no letter, wait or restructure can fix. That means income or funds that cannot be verified, an undisclosed debt that pushes the borrower past the limit, or statements that contradict the application in a way the borrower cannot explain.
Common endpoints:
- Unsourced large deposits the borrower cannot trace. If the money has no origin, the lender cannot count it toward funds to close or reserves, and the file may fall short.
- An undisclosed loan that breaks the debt-to-income limit. Adding the hidden payment to the ratio can push the borrower over the maximum, and the file has no room to adjust.
- Statements that conflict with the application. Deposits that do not match claimed income, or a business that shows far less activity than the borrower stated, make an underwriter doubt the whole file.
- Altered or incomplete documents. A statement that looks edited, or pages removed to hide activity, ends the conversation with that lender.
- Reserves or income that fall under the program minimum. If the numbers are simply too low, no explanation changes arithmetic.
Fix, wait or decline
The triage table below is an example of how a broker might map each problem to a response. The responses are a starting point, since each lender sets its own limits.
| Problem on the statements | Example situation | Usual response |
|---|---|---|
| NSF cluster | Four NSF fees in three months | Wait out the window, or find a program with a higher limit |
| Single NSF or overdraft | One fee, payroll posted late | Explain with a letter and the pay record |
| Cash deposits | $4,500 cash, sale of a truck | Explain with a letter and a bill of sale |
| Cash deposits with no source | $9,000 cash, no record | Restructure so the money is not needed, or decline |
| Falling balance | Ending balance down every month for six months | Wait, rebuild reserves, or restructure the loan amount |
| Gambling debits | Frequent betting-app charges | Explain the pattern; expect a harder review, and decline if the lender will not accept it |
| Undisclosed loan payment | Monthly payment to a lender not on the application | Disclose, add to the ratio, and re-run the file |
Restructure as a third option
Between explaining and declining sits restructuring. A smaller loan amount, a larger down payment from documented funds, a co-borrower with a cleaner history or a different program can turn a failing file into a passing one. A broker should model the change before suggesting it. Run the numbers with the debt added, the unsourced money removed, or the income trimmed to eligible deposits, and see whether the file still works.
TrueBankFlow lists NSF fees, overdrafts and out-of-pattern deposits with the date and statement line, and recalculates the averages when the broker includes or excludes a deposit. The decision about the file stays with the underwriter.
Bad statement problems a broker should never hide
A broker should never hide a bad statement problem, because the lender will find it, and hiding it turns a fixable file into a fraud question. Disclose early, bring the explanation and the proof, and let the lender decide with the full picture.
Why hiding fails
Lenders see the same statements the broker sees. A missing page is noticed because running balances do not connect. A deposit left out of a summary is noticed because the underwriter adds the lines up. A loan payment omitted from the application is noticed because it appears on the statement as a debit with a payee name. Once an underwriter finds one thing that was not disclosed, every other item in the file is read with suspicion, and the delay costs more than the original problem.
What disclosure looks like
Disclosure is a short, factual note with the file. For example: "Borrower had two overdraft fees in January and one in February. The attached letter explains both. Balances have been above $3,000 since March." That note takes a minute to write, tells the underwriter where to look, and shows the broker has already checked.
Questions to ask the borrower first
Before the file goes out, a broker should ask:
- Are there any payments on these statements to a lender or card that is not on the application?
- Are there any deposits you cannot document?
- Are there any accounts that are not in this package?
- Did you withdraw or move money since the last statement?
Ask them once, plainly, and write down the answers. Borrowers who are not asked often assume the lender will not notice. The detailed deposit questions are in the guide to which questions a broker asks the borrower about deposits.
Rules for NSF fees
How many NSF fees are too many depends on the program. The counting rules, including whether the lender counts occurrences or fees, are in NSF tolerance limits on bank statement programs. Read them before you tell a borrower their file is fine or doomed.
A broker's own exposure
A broker who submits a file knowing it hides a problem puts their own license and reputation at risk, not only the borrower's loan. The safe habit is simple: every problem in the statements is either explained in the file or fixed before submission. If the borrower will not allow it, the broker should step away from the file.
To start a review on your own files, see TrueBankFlow for early access.