NSFs and Negative-Balance Days: What They Tell Underwriters
Overdrafts and returned items are not automatic deal-killers, but they are the first thing a reviewer counts. Count them yourself, in context, before anyone else does.
A merchant swears the business is doing great. Then you open the statements and see eleven insufficient-funds fees in the last thirty days and the balance sitting below zero for most of a week. The merchant is not necessarily lying about sales. But something about how cash moves through that account is under strain, and every underwriter on your panel will notice within a minute.
NSFs and negative-balance days are among the clearest stress signals on a statement. They are also easy to miscount and easy to misread without context. A broker who counts them accurately, understands what drove them and explains them plainly gives the file its best fair chance. A broker who ignores them wastes everyone's time, including the merchant's.
Pre-flight summary
- Count NSF events and negative-balance days separately, month by month, with a written method.
- Recent activity matters far more than old activity; lead with the trend.
- Always identify what bounced, because bounced funding remittances are a serious warning.
- Disclose and explain NSFs up front instead of leaving them for the underwriter to find.
- Sometimes the most responsible advice is for the merchant to wait and stabilise first.
Leg 01Two different signals that often travel together
An NSF, or non-sufficient-funds event, happens when a payment is presented and the account cannot cover it. The bank either returns the item unpaid or pays it and charges an overdraft fee, depending on the account. Either way, there is usually a fee line on the statement, and sometimes a returned-item line as well.
A negative-balance day is simpler: a day the account closed below zero. A business can have negative days without NSFs, if the bank covers payments through overdraft, and it can have NSFs on a day the balance ends positive, if a large deposit lands after a payment bounced. Track both separately. Together they describe how often the business runs out of room and how long it stays there.
Leg 02How to count them without fooling yourself
Counting sounds trivial until you try. Banks label these events differently, and one bounced payment can generate two or three lines. Pick a consistent method and apply it to every month, then write the method down on the file so anyone reviewing it understands your numbers.
- Search each statement for fee descriptors: NSF, overdraft, returned item, insufficient funds.
- Group lines that belong to the same underlying payment so one event is counted once.
- Record the date and amount of each event, not just the total.
- Mark each day the closing balance was negative, using the daily balance section if the bank provides one.
- Tally NSF events and negative days separately for each calendar month.
- Note the deepest negative balance and how many days in a row it lasted.
Leg 03Why the most recent month carries the most weight
Underwriters generally care far more about the last thirty to sixty days than about four months ago. Consider two hypothetical merchants with eight NSFs each across a four-month file. The first had all eight in the oldest month, during a slow season, and has been clean since. The second had none until last month, then eight. Same total, opposite stories.
The first business appears to have recovered. The second is trending into trouble, possibly because a new obligation started pulling from the account. Lay your monthly counts side by side and the direction becomes obvious. That direction, more than the total, is what you should lead with when you describe the file.
Eight NSFs in an old slow month and eight NSFs last month are not the same file.
Leg 04Find out what caused them
Every cluster of NSFs has a cause, and the statement often tells you what it was. Look at what was being paid when the account came up short. If the bounced items are daily debits from another funding provider, the business may already be carrying more than it can handle, which is a serious caution against adding another position. If the shortfalls hit the same day each month just before a large customer payment arrives, it may be a timing mismatch rather than a structural problem.
Ask the merchant directly. Real explanations exist: a major client paid sixty days late, a one-time equipment repair, a bank error later reversed. Get the explanation, and where possible a document that supports it, and attach both to the deal.
- Bounced items that are existing funding remittances
- Shortfalls that line up with payroll or rent dates
- A single event such as a disputed charge or bank error
- A drop in deposits that started the same month the NSFs did
Leg 05Presenting a file that has them
Do not hide them, round them down or leave them for the underwriter to discover. Put the monthly counts, the trend and the merchant's explanation at the top of your submission notes. That framing tells the lender you have read the file and are not wasting their time, and it lets them decide quickly whether it fits their guidelines.
Also be straight with the merchant. A business with recent heavy NSF activity may get fewer or smaller offers, or none, and adding a daily remittance to an account already bouncing payments can make things worse for them. Sometimes the responsible advice is to wait a couple of months, stabilise the account and come back with a cleaner picture. That conversation earns trust and often earns the deal later.
FundPilot's statement underwriting counts NSFs and tracks balances per month, and links each figure to the statement page it came from, so your summary and the evidence sit together on the deal. Your notes on the merchant's explanation live on the same record, which keeps the context intact if a manager or another broker picks up the file.
Leg 06Matching the file to the right lenders
Funders differ in how much NSF activity they will accept, and their tolerance can change over time. Rather than guessing, keep each lender's current guidelines in your system and compare the file against them before submitting. Sending a file with heavy recent NSFs to a funder that clearly declines them helps no one and can wear down a relationship you need for your next deal.
This is where lender matching earns its place. In FundPilot, guideline scoring compares the file's figures against each lender's stated criteria, so you send to the funders whose guidelines the merchant actually fits, and every reply threads back onto the deal.
Questions from the floor
Is there a standard number of NSFs that disqualifies a file?
There is no universal number. Each funder sets its own tolerance, and it may depend on the size of the request, the merchant's time in business and how recent the events are. Rather than relying on a rule of thumb, check each lender's current guidelines and present the counts clearly so the funder can decide. Treat any figure you hear secondhand as something to confirm.
Do overdraft-protection transfers count as negative days?
If the bank automatically moved money from a linked account to cover a shortfall, the operating account may never close negative, but the business still ran out of room. Note those transfers in your summary and remove them from revenue, since they are internal movements. Being transparent about them is more useful to the lender than a clean-looking balance line.
Can a merchant with recent NSFs still get funded?
Sometimes, depending on the cause, the trend, the rest of the file and each funder's guidelines. Nobody can promise an outcome. What you can do is present the file honestly, match it to lenders whose criteria fit, and talk with the merchant about whether adding a new remittance is wise right now. If it is not, helping them wait is the right call.
General information only — not legal, tax or financial advice. Rules for telemarketing, texting, recording, disclosures and data retention vary and change; confirm current requirements with qualified counsel.
Connecting flights