Key Takeaways
- New York City's new revenue-based loan program explicitly acknowledges that traditional lending fails seasonal businesses, validating the MCA model and raising the bar for verification rigor.
- When a city government builds revenue-based financing into its economic development toolkit, private MCA funders face higher expectations for how they assess and document cash flow.
- Bank verification software for funders must now parse seasonal revenue patterns, not just monthly averages, to stay competitive with public-sector alternatives.
- Automated bank statement analysis that flags seasonal dips as risk instead of recognizing them as normal cycles leads to false declines and lost deals.
- Let's Submit helps funders collect and extract bank statement data asynchronously so underwriters can focus on interpreting seasonal patterns rather than chasing documents.
NYC Just Validated Revenue-Based Financing. Private Funders Should Pay Attention.
New York City's Department of Small Business Services recently promoted its NYC Future Fund, a revenue-based loan program built around a simple premise: traditional loans do not work for businesses whose revenues shift with the seasons. Commissioner Kenny Minaya framed the program as filling a gap that conventional bank lending leaves wide open, with loans starting at $2,000 and repayment tied to actual monthly revenue.
For MCA funders and ISO brokers, this is not just a policy announcement. It is a competitive signal. When a municipal government builds revenue-based financing into its economic development infrastructure, it tells the market that this model is mainstream, legitimate, and here to stay. But it also raises a pointed question: if a city program can underwrite seasonal businesses intelligently, why can't every private funder?
The answer, for many shops, is that their bank verification software for funders was never designed to think in seasonal terms. Most tools pull monthly averages, flag dips as red flags, and move on. That approach worked when the goal was simply confirming deposits. It breaks down when the merchant's revenue follows predictable seasonal curves and the funder needs to distinguish a January slowdown from a business in decline.
This article breaks down what NYC's program signals for private MCA operations, why seasonal cash flow analysis is now a table-stakes capability, and how funders can retool their verification workflows without slowing down their pipeline.
Why Seasonal Revenue Breaks Traditional Bank Verification
Flat Averages Miss the Full Picture
Most bank statement analysis workflows calculate a simple monthly average: total deposits divided by number of months. For a landscaping company that does $150,000 in June and $30,000 in January, that average lands somewhere around $90,000. The number looks reasonable. But an underwriter relying on it will either over-advance based on peak months or decline the deal based on trough months, depending on which statements happen to land in the review window.
The NYC Future Fund explicitly addresses this problem by tying repayment to actual revenue in a given period. Private funders can do the same thing, but only if their verification infrastructure captures enough months of data and surfaces the seasonal pattern clearly. Four months of bank statements, the standard MCA ask, barely covers one season. If those four months happen to be May through August for a ski resort town restaurant, the underwriter sees peak performance and no hint of the winter cliff.
Why AI Extraction Matters for Seasonality
Automated bank statement analysis catches seasonal patterns that manual review routinely misses. When AI extraction parses deposits across multiple months, it can flag month-over-month variance, identify recurring seasonal dips, and compare the current cycle against prior-year patterns if enough history is available. A human reviewer scanning PDFs for deposit totals rarely performs this kind of longitudinal analysis under time pressure.
The difference matters most at the margins. A merchant doing $80,000 per month on average but swinging between $40,000 and $120,000 is a fundamentally different risk profile than one doing a steady $80,000. The average is identical. The cash flow volatility is not. Cash flow data depth separates winning MCA underwriting from guesswork, and seasonal analysis is where that depth shows up most clearly.
The Document Collection Bottleneck Gets Worse With More Months
Asking for four months of statements is already a friction point. Asking for six or twelve, which is what proper seasonal analysis requires, multiplies the dropout risk. Merchants abandon applications when the document request feels burdensome. Every additional upload step costs conversion.
This is where asynchronous collection becomes critical. Instead of requiring a merchant to gather all statements in one sitting, a platform like Let's Submit sends a secure upload link that the merchant can return to on their own time. Statements land in one place. AI extraction pulls the numbers automatically. The underwriter sees a clean, structured view of revenue by month without having manually organized a single PDF. The merchant experiences a two-minute task. The funder gets the data depth seasonal analysis demands.
What Public-Sector Revenue-Based Lending Means for Private Funders
Legitimacy Comes With Scrutiny
The NYC Future Fund is not competing with MCA funders on volume. Its loan sizes start small and its reach is limited to New York City businesses. But its existence sends a message to regulators, journalists, and merchants: revenue-based financing can be done responsibly, with transparent terms and repayment tied to actual performance. That framing puts pressure on private funders whose underwriting appears less rigorous.
In 2026, with New York appellate courts already scrutinizing revenue-based financing structures, funders cannot afford to look like they are guessing at cash flow. Every deal file needs to demonstrate that the advance amount was calibrated to real, verified revenue, not a ballpark figure from a phone call. Bank verification software that produces a clean, auditable extraction of monthly deposits is no longer a nice-to-have. It is the documentation layer that stands between a funder and a regulatory challenge.
Merchant Expectations Are Rising
When a merchant hears that the city offers revenue-based loans with flexible repayment, they start expecting every funder to understand their seasonal reality. The merchant who runs a catering company and applies for an MCA in October does not want to explain why her September numbers were double her February numbers. She expects the funder to already know that catering peaks in event season.
Funders who can demonstrate that understanding, by asking the right questions and collecting the right documents upfront, close faster. Funders who treat a seasonal dip as a red flag and request explanations lose the deal to the shop down the street that recognized the pattern immediately. The competitive advantage is not just speed. It is intelligence. And that intelligence starts with what the bank statements actually reveal when analyzed properly.
Seasonal Patterns Unlock Better Renewal Decisions
Seasonality analysis does not just improve initial underwriting. It transforms renewal velocity. A funder who knows that a landscaping merchant's revenue dips every winter can proactively offer a renewal in March, right as cash flow rebounds, instead of waiting for the merchant to call in distress during January. This is precisely the kind of post-funding data gap that costs MCA lenders on renewal decisions. Closing that gap requires storing and analyzing the bank statement data from the original deal, not just the approval decision.
The NYC program's repayment model, which adjusts with revenue, is essentially a built-in renewal mechanism. Private funders can replicate that advantage by using their bank verification data to anticipate merchant needs rather than react to them.
Frequently Asked Questions
How does seasonal revenue affect MCA underwriting?
Seasonal revenue creates cash flow variance that standard monthly averages obscure. An MCA underwriter who relies on a four-month average may over-advance during peak season or decline a healthy business during its natural trough. Proper seasonal analysis requires at least six months of bank statement data, ideally twelve, and extraction tools that surface month-over-month deposit trends rather than a single aggregate number. Funders who account for seasonality make more accurate advance decisions and experience lower default rates on merchants with cyclical revenue.
What is bank verification software for funders?
Bank verification software for funders is a category of tools that automate the collection, extraction, and analysis of merchant bank statements during MCA underwriting. These platforms typically allow funders to send secure upload links to merchants, parse PDF or image-based statements using AI, and extract key fields like monthly deposits, average daily balances, and NSF counts. The goal is to replace manual data entry and phone-based verification with a structured, auditable digital workflow. Let's Submit is one such platform, combining asynchronous document collection with AI-powered extraction to deliver clean application data without manual processing.
Why do NYC's revenue-based loans matter for MCA funders?
NYC's Future Fund matters because it normalizes revenue-based financing as a legitimate, government-backed lending model. This raises merchant expectations for how private funders assess and accommodate seasonal cash flow. It also gives regulators a benchmark for responsible revenue-based lending practices. Private MCA funders who cannot demonstrate equivalent or superior underwriting rigor risk both competitive disadvantage and regulatory scrutiny. The program signals that repayment tied to actual revenue is becoming a market standard, not a niche alternative.
How many months of bank statements do you need for seasonal cash flow analysis?
Four months of bank statements, the typical MCA requirement, is insufficient for meaningful seasonal analysis. Six months captures half a revenue cycle, which helps but still misses the full picture. Twelve months is ideal because it covers a complete annual cycle and reveals year-over-year patterns. The challenge is that requesting more months increases merchant dropout during application intake. Asynchronous collection tools mitigate this by letting merchants upload documents at their own pace through a secure link, reducing the friction that kills conversion rates on longer document requests.
Conclusion
New York City building revenue-based financing into its small business lending infrastructure is not a threat to MCA funders. It is a signal. The market is moving toward cash flow-aware underwriting, and funders whose bank verification workflows still rely on flat monthly averages are falling behind. Seasonal analysis, deeper document collection, and AI-powered extraction are no longer optional capabilities. They are the baseline.
Let's Submit gives funders the infrastructure to collect more bank statement data with less merchant friction and extract the seasonal patterns that drive better decisions. Visit letssubmit.ca to see how asynchronous verification and AI extraction fit into your underwriting workflow.