What NSF Transactions Tell You About a Business
Non-sufficient funds (NSF) transactions — sometimes called bounced payments or returned items — occur when a business's account lacks the funds to cover a payment that has been presented. In MCA underwriting, NSF transactions are one of the most important signals in a bank statement, and one of the most commonly misunderstood.
An NSF is not inherently disqualifying. But the pattern, frequency, timing, and amounts of NSF transactions can tell you a great deal about the financial health and management discipline of the business you are considering funding.
Reading NSF Frequency
The first question every underwriter should ask is: how often are NSFs occurring?
- Zero NSFs in 90 days: This is the ideal scenario. The business maintains sufficient balances to cover all outgoing payments. It suggests strong cash management and predictable cash flow.
- One to two NSFs in 90 days: Generally acceptable, especially if the amounts are small and the NSFs appear to be isolated incidents rather than part of a pattern. A single bounced subscription payment or a timing mismatch with a deposit is not uncommon for small businesses.
- Three to five NSFs in 90 days: This is a yellow flag. It suggests the business is operating with thin margins and may struggle to absorb the additional daily or weekly holdback of an MCA position. Closer scrutiny is warranted.
- Six or more NSFs in 90 days: This is a red flag in most underwriting frameworks. Frequent NSFs indicate chronic cash shortages, poor financial management, or both. Funding a business in this condition carries elevated risk of default.
NSF Amounts Matter Too
Not all NSFs are created equal. Consider the difference between these two scenarios:
Scenario A: A restaurant has two NSFs in 90 days, both for a $14.99 software subscription that was mistimed against a deposit. Total NSF exposure: under $30.
Scenario B: A construction company has two NSFs in 90 days, both for supplier payments exceeding $5,000. Total NSF exposure: over $10,000.
Both businesses show "two NSFs in 90 days" — but they tell very different stories. Scenario A suggests a minor timing issue. Scenario B suggests the business may not have the cash flow to meet its core operational obligations.
Context Is Everything
Seasonal Businesses
Canadian businesses are often subject to significant seasonality. A landscaping company in Ontario will naturally have lower cash flow in December than in July. A ski rental shop in British Columbia shows the opposite pattern. The key is understanding whether NSFs align with a predictable seasonal pattern or occur during what should be peak revenue period. An NSF during peak season is a much stronger negative signal than one during a known slow period.
One-Offs Versus Patterns
A single NSF surrounded by 89 days of clean transactions is very different from NSFs that recur at regular intervals. Look for patterns:
- Do the NSFs cluster around the same time of month (e.g., when rent is due)?
- Are the same payees being bounced repeatedly?
- Do NSFs increase in frequency over the 90-day window, suggesting a deteriorating situation?
A business with three NSFs in month one and zero in months two and three may have resolved a temporary crunch. A business with escalating NSFs is likely heading in the wrong direction.
NSFs on MCA Holdbacks
Pay particular attention to NSFs on existing MCA holdback payments or loan repayments. These indicate the business is already struggling to service current debt — and adding another position will likely make things worse. This is a strong indicator of stacking risk.
The Problem with NSF Data in PDF Statements
Here is where things get complicated for underwriters relying solely on PDF bank statements: NSF transactions are among the easiest items to remove from a doctored statement.
Because NSFs often appear as single line items with a standard bank description (such as "NSF — RETURNED ITEM" at RBC or "NON-SUFFICIENT FUNDS" at TD), they can be cleanly deleted from a PDF without leaving obvious formatting gaps. The running balance can be adjusted accordingly, producing a statement that looks clean to both manual review and automated analysis.
NSF transactions are the easiest line items for a fraudster to remove — and the most important line items for an underwriter to see. This creates a dangerous blind spot in PDF-only verification.
Why Live Portal Access Gives You More Accurate NSF Data
When an applicant navigates their banking portal in a screen recording, the transaction history displayed is pulled directly from the bank's database. Deleted or modified transactions in a PDF do not affect what appears in the online portal. If a business had seven NSFs last month, those seven NSFs will be visible in the portal's transaction history — regardless of what the submitted PDF shows.
This is one of the strongest arguments for supplementing PDF review with portal verification. You are not relying on a document the applicant controls. You are looking at the data the bank holds.
Using Guided Recording to Surface NSF Patterns
One challenge with portal verification is ensuring the applicant shows the screens where NSF transactions would be visible. An applicant aware of their NSF history might scroll quickly past relevant dates or skip certain months entirely.
Guided recording addresses this by directing the applicant through specific date ranges and transaction views. Exact Balance's guided recording mode, for example, instructs applicants to navigate to their full 90-day transaction history and scroll through it at a readable pace. Several Canadian banks, including BMO and Scotiabank, offer dedicated "returned items" or "service charges" views that aggregate NSF fees — and guided recording steps can direct applicants to show these screens as well, ensuring lenders get the NSF data they need without relying on the applicant to volunteer it.
Building NSF Analysis Into Your Underwriting Framework
Here is a practical framework for incorporating NSF analysis into your underwriting decisions:
- Count and categorize. Tally NSFs by month and by amount. Separate small-value NSFs (under $100) from large-value ones.
- Identify patterns. Map NSFs against the calendar. Do they cluster around specific dates? Do they correlate with known business cycles?
- Cross-reference with deposits. Check whether NSFs occurred during periods of low deposit activity or whether they happened even when revenue was flowing.
- Compare PDF to portal. If you have both a PDF statement and a portal recording, compare the NSF count. Any discrepancy is an immediate red flag for document manipulation.
- Factor into pricing. Rather than treating NSFs as a binary pass/fail, consider building them into your risk pricing. A file with moderate NSF activity might still be fundable at a higher factor rate.
The Bottom Line
NSF transactions are among the most informative data points available to MCA underwriters — but only if you can trust the data you are seeing. PDF statements give you one version of the story. Live portal verification gives you the bank's version. For Canadian MCA lenders processing meaningful volume, incorporating portal-based NSF verification into the underwriting workflow is not just a fraud prevention measure — it is a fundamental improvement in the accuracy of your credit decisions.
The businesses you fund deserve thorough analysis, and your portfolio deserves the protection that comes from seeing the full picture.