A business owner with NSF activity on their business bank statements is not automatically declined on a bank statement commercial loan. What decides the file is which kind of NSF it is, what caused it, and — the part almost nobody plans for — how the overdraft was cured.
Our guideline treats NSF, overdraft protection transfers, zero balances and negative balances as one family of events that must be carefully reviewed, because they are read as a sign of the borrower's inability to manage expenses and pay creditors. That is a review trigger, not a decline trigger. But the review has structure, and the structure is knowable in advance. If you are going to spend money on an appraisal and a third-party report, it is worth knowing which category your statements fall into before you start.
This page is only about that decisioning. The bank statement program itself — what it is, how many accounts you may use, which deposits are excluded, and how deposits become qualifying income — is covered separately in [Can Venmo and Cash App deposits qualify a commercial loan](/blog/can-venmo-and-cash-app-deposits-qualify-a-commercial-loan). Read that one for program mechanics. Read this one for what happens when the account went negative.
What actually counts as an NSF
Start with the definition, because two of its consequences are counterintuitive.
An NSF occurs when a demand for payment — a check — cannot be honored due to insufficient funds in the account from which the instrument was drawn.
From that definition, our guideline draws two lines that catch people out in opposite directions.
The first line is unfavorable and surprises borrowers who think their bank protected them. Overdrawn accounts are considered NSF, regardless of whether or not an overdraft protection account exists. The event is the negative balance, not the bounced item.
The second line is favorable and surprises borrowers who think every returned check is a mark against them. Returned checks that do not result in a negative balance are not considered NSF.
| What the statement shows | Is it an NSF? |
|---|---|
| A check you wrote could not be honored for insufficient funds; the account went negative | Yes |
| The account went negative and overdraft protection covered it, so nothing was returned | Yes — overdrawn accounts are considered NSF regardless of whether overdraft protection exists |
| A check you deposited from a customer was returned, and the account never went negative | Not an NSF |
| A check you deposited was returned and the account went negative as a result | An NSF, but the cause may still be considered |
That last row is the one that keeps files alive, and it gets its own section below.
Overdraft protection is a banking product, not an underwriting shield
Overdraft protection links your operating account to a second account or a line so the bank moves money automatically when the balance would go below zero. From the outside, nothing bounced. Your vendor was paid. Nobody called you.
None of that changes the file. Our guideline names overdraft protection transfers in the same sentence as NSF, zero balances and negative balances as activity that must be carefully reviewed. The transfer itself is visible on the statement, and it is part of what is being examined.
There is a second consequence that matters more than the first. Because the transfer is visible, the review can see where the covering money came from. That visibility is not incidental — it is exactly what the next test grades.
The cause test: whose failure was it
Our guideline allows that return check situations which result in an NSF may still be considered, and gives a specific example: the NSF is due to a bounced accounts receivable deposit.
The mechanics of that scenario are worth spelling out, because it is common in trades, wholesale, staffing and any business that invoices rather than collects at the point of sale. You deposit a customer's check. The bank makes some or all of it available. You pay your own obligations against that balance. The customer's check comes back. Your account goes negative, and the negative balance was created by your customer's failure, not by your own account management.
That distinction is the entire basis for the exception. The guideline's underlying concern is the borrower's ability to manage expenses and pay creditors. An A/R bounce is not evidence of that failing.
Read the hedging exactly as written: the NSF may still be considered. That is discretion, not a defined carve-out, and it is not automatic. It is exercised on evidence, which means the burden is yours.
What that evidence looks like in practice is the bank's returned-item notice identifying the deposited check, the invoice it was paying, and whatever came next — the replacement payment, the collection, or the write-off. Our guideline does not specify a required document set for this situation. It names the example and leaves the file to make its case, so send more rather than less.
The cure test: how the overdraft was made whole
This is the part of the review that most borrowers have never heard of, and it is the part that most often separates two files with identical NSF counts.
Our guideline draws a distinction between overdrafts and NSF covered with other business funds — business savings, sweep accounts — versus the use of a credit line, credit card or personal funds to cover the NSF. And it adds a hard condition on top: in order to qualify, there cannot be a fee associated with curing the overdraft default.
There are two independent tests in that sentence. Where the cure came from, and whether it cost anything.
Where the cure came from
| How the overdraft was cured | How it reads |
|---|---|
| Transfer from a business savings account | Other business funds — the favorable side of the distinction |
| Automatic sweep from a business sweep account | Other business funds |
| Draw on a business line of credit | Credit line — the unfavorable side |
| Credit card advance | Credit card — unfavorable |
| Deposit from the owner's personal account | Personal funds — unfavorable |
The logic holds up under scrutiny, which is why it is worth understanding rather than memorizing.
A sweep from business savings says the business had the money and the timing was off. Cash existed; it was in the wrong drawer for a day. That is a treasury problem.
A credit line draw says the business did not have the money and had to borrow it to stay current. That is a liquidity problem.
A deposit from the owner's personal account says the business did not have the money and the owner did. That is a business-cash-flow problem being solved by a household.
Same negative balance on the same statement, three different answers to the question the file is actually asking: does this operating business generate enough cash to service a new commercial mortgage.
Whether the cure carried a fee
The fee clause is the sharpest sentence in the section and there is no soft reading of it. In order to qualify, there cannot be a fee associated with curing the overdraft default.
A cure that carried a fee does not meet the standard as written. Our guideline states the rule; it does not enumerate which fee types count, name amounts, or describe a waiver process. So do not assume your bank's particular label for the charge gets you around it, and do not assume a refunded fee is the same as no fee. If you are not sure what your bank assessed, the statement will tell you — the line item is usually posted the same day or the next business day as the negative balance.
Zero balances and negative balances stand on their own
NSF is not the only trigger in that paragraph. Zero and negative balances are named separately, which means an account can draw scrutiny without a single item ever being returned.
The review is also finer-grained than most borrowers expect. A 2024 revision to the bank statement cash flow analysis specifically updated it to include daily, monthly and zero balances. That is a day-level read of the account, not a month-end snapshot. A month that closes at a comfortable number can still contain three weeks near zero, and that pattern is visible.
Adjacent to this is a separate provision with real consequences. Low beginning, daily, monthly and/or ending balances may require additional documentation up to and including full tax returns — 1040s, 1065s or 1120s. Note what that is and what it is not. It is not a decline. It is an escalation in documentation, and for a self-employed owner who chose the bank statement program precisely because their returns show aggressive deductions, that escalation can matter more than the NSF events themselves.
How many NSFs are too many
Our guideline does not answer this with a number, and it would be dishonest to give you one.
There is no stated maximum count of NSF events, no per-month cap, and no defined lookback inside the twelve months that is treated more leniently than the rest. What the guideline says is that this activity must be carefully reviewed and will be scrutinized. If someone quotes you a hard threshold — three NSFs, or none in six months — they are quoting a different program's overlay, a general-purpose article, or nothing at all.
What that silence actually means is that the outcome turns on the pattern rather than the tally: how many events, how recent, what caused each one, how each was cured, and what the balance trend looks like around them.
Which is why two files with the same NSF count can land in completely different places. One event eleven months ago, caused by a customer's returned deposit, cured by an automatic sweep from business savings with no fee, on an account whose balances trend upward, is a different file from six events in the last quarter cured by credit card advances on an account that spends half of every month near zero. The count is identical. Nothing else is.
What to do with the statements you already have
The single most useful thing you can do before applying is the review itself. Pull your own twelve months and mark every day the account touched zero or went below it. Most owners have never done this and are wrong about their own count in both directions.
Then, for each marked day, write down two things: the cause, and the cure. That is precisely the file the underwriter is going to assemble. Assembling it first costs you nothing and removes the round of questions that otherwise adds a week.
A few specifics worth acting on.
The window moves. The requirement is the trailing twelve consecutive months of business bank statements. That window slides forward with the calendar. An event that sits in month eleven today is outside the window in two months. If your worst quarter is also your oldest quarter and nothing forces you to close now, time is on your side.
Document A/R bounces when they happen. Returned-item notices, the customer invoice, and evidence of what was eventually collected. This is the only cause the guideline names as potentially acceptable, so make it easy to see.
Fix the plumbing prospectively. If you are going to link an account for overdraft coverage, link a business savings account and ask your bank in writing whether the transfer carries a fee. A no-fee sweep from business savings is the version of this that reads well. A line of credit linked for the same purpose is the version that does not.
Stop curing from personal funds. It is the instinct of every owner who does not want a check to bounce, and under this program it is the worst available option for the file.
Where this sits in the rest of the file
NSF review is one input among several, and it does not move the other requirements. The guideline does not tie NSF activity to the credit or reserve standards, and neither should you.
For reference, so you can see the whole picture at once: the program requires a minimum FICO of 650 for the guarantor the file is priced on — the guarantor with the highest middle score — and a minimum FICO of 640 for all other borrowers and guarantors. Post-closing liquid reserves are six months of the qualifying principal-and-interest payment for the subject property, and the guideline lists six months for purchase, rate/term refinance and cash-out refinance alike. Income comes from twelve consecutive months of business bank statements.
The connection between NSF activity and reserves is worth noticing even though the guideline does not state one. An account that hovers near zero is an account that is unlikely to independently demonstrate six months of liquid reserves. Files that struggle on one of these often struggle on the other, and the underlying condition is the same.
What this page does not do
This page explains how NSF events, overdraft protection transfers, zero balances and negative balances are evaluated under our small balance commercial bank statement program. It is not an approval, a pre-approval, a rate quote, or a commitment to lend, and reading it does not put you in the program.
It does not tell you whether your particular NSF history is acceptable. That is a judgment made on your actual statements against the full file, and no article can make it for you.
It does not cover the bank statement program's structure — the account rules, the excluded deposit categories, or the arithmetic that turns deposits into qualifying income. That is the companion page linked at the top.
It does not address property-side underwriting: condition, occupancy and stabilization, appraisal, environmental, or the tier your property type falls into. It does not address pricing, loan amount, LTV, or which document program your file ultimately belongs in.
It does not state a maximum acceptable number of NSF events, because our guideline does not state one. Any number you have seen elsewhere did not come from this program.
And it is not legal, tax or accounting advice. Questions about how to characterize a transfer on your books, or what your bank's fee disclosures obligate them to do, belong with your accountant or your attorney.
Guideline SBC 08/03/2026 · Reviewed August 31, 2026
Published September 1, 2026 · Updated September 1, 2026
How to use this guide
This article is educational guidance, not an offer or commitment to lend. Rules, property facts, credit, leverage, documentation, and full underwriting still control any actual scenario.