How Lightspeed's 73% MCA Revenue Growth Exposes the Bank Verification Bottleneck for Funders

A 73% Revenue Surge Reveals What Breaks First

When Lightspeed Capital reported 73% year-over-year growth in MCA revenue during its most recent quarterly earnings, the headline number dominated industry coverage. But the more revealing metric sat one line below: merchant cash advances outstanding grew only 12%, while the payback period declined to seven months. That combination tells a story about velocity. Lightspeed is cycling through more deals faster, not simply accumulating a bigger portfolio. For every funder watching from the sidelines, the implication is clear. The verification infrastructure that worked at last year's volume will not survive this year's pace.

Bank verification software for funders sits at the center of this pressure. Every new deal requires bank statements. Every renewal, which now arrives a month sooner on average, requires fresh ones. Multiply that across a growing merchant base and the math becomes uncomfortable. Manual review teams that could handle 50 files a day are suddenly staring at 80, then 120, with no proportional increase in headcount budget. The bottleneck is not underwriting judgment. It is the mechanical process of collecting, parsing, and organizing financial documents before judgment can even begin.

This article breaks down why the Lightspeed growth signal matters for every MCA funder's operational stack, where the verification bottleneck actually forms, and what a scalable alternative looks like in practice.

Why Shorter Payback Periods Compound the Verification Problem

The Renewal Velocity Math

A payback period declining from eight months to seven may sound marginal. It is not. Consider a funder with 500 active merchants. At an eight-month payback, each merchant becomes eligible for renewal 1.5 times per year. At seven months, that figure jumps to 1.7 times. Across 500 merchants, that is roughly 100 additional renewal-ready files per year, each requiring updated bank statements, fresh cash flow analysis, and a new risk assessment. The funder did not acquire 100 new merchants. The existing portfolio simply spun faster.

As we explored in our analysis of how Lightspeed's growth proves the case for automated bank statement analysis, this velocity effect is the hidden driver behind operational strain. Revenue growth looks great on an earnings call. Behind the scenes, operations teams are drowning in documents.

Where Manual Workflows Break

Most MCA funders still rely on some version of the same process: a broker or merchant emails bank statements as PDF attachments, an intake coordinator downloads them, names the files, uploads them to a shared drive or CRM, and flags them for an underwriter. Each step introduces delay and error. A mislabeled file sits unnoticed for hours. A three-month statement set arrives missing page two of month two. The merchant gets a callback request, which goes to voicemail, which delays the deal by another day.

None of these failures are dramatic. They are incremental. But at scale, incremental delays compound into systemic slowdowns. When Lightspeed or any high-growth funder pushes volume up by 73%, those five-minute delays across hundreds of files translate into days of lost throughput per week. The underwriting team is not slow. The pipeline feeding them is clogged.

Document Collection, Not Underwriting, Is the Real Bottleneck

Industry conversations tend to focus on underwriting speed. Faster credit models, better scoring algorithms, AI-assisted decisioning. These matter. But they assume the underwriter already has clean, complete, structured data to work with. In 2026, the more common failure mode is upstream. The merchant never uploaded the right documents. The broker forwarded a partial set. The bank statement PDF is a photograph of a screen, not an actual export.

The bottleneck is not the decision. It is the data preparation that precedes the decision. This is precisely why reducing manual data entry in MCA lending has become a strategic priority rather than a nice-to-have operational improvement. Every minute spent chasing documents is a minute an underwriter could spend evaluating risk.

What Scalable Bank Verification Actually Looks Like

Asynchronous Document Collection

The first principle of scalable verification is removing the funder from the document collection loop entirely. Instead of waiting for emailed attachments, a funder sends the merchant a single secure upload link. The merchant uploads bank statements, voided checks, tax returns, and any other required documents at their convenience. No email threads. No missing attachments. No back-and-forth about file formats.

This asynchronous model is the core of what Let's Submit provides. A funder generates a link, shares it with the merchant or broker, and the platform handles intake. Documents arrive in a structured queue, automatically associated with the correct application. The funder's team never touches a file until it is ready for review.

AI Extraction Replaces Manual Parsing

Once documents land in the system, the second bottleneck is parsing. A human reviewer opening a 90-page bank statement PDF, scrolling to find monthly totals, cross-referencing deposit patterns, and typing figures into a spreadsheet is performing work that AI handles in seconds. Modern document extraction models, trained specifically on financial documents, can identify statement periods, ending balances, total deposits, total withdrawals, NSF occurrences, and average daily balances without human intervention.

The distinction between general-purpose OCR and purpose-built financial document AI matters enormously here. A generic text extraction tool will pull characters off a page. A model trained on bank statements understands that the number in the upper right of a Chase statement page means something different from the number in the lower left of a Wells Fargo summary. Let's Submit's AI-powered extraction is built for this specificity, parsing business info, financials, and owner details from the document formats MCA funders actually encounter.

Structured Data Feeds the Underwriting Queue

The output of this process is not a stack of PDFs waiting for human interpretation. It is structured, tabular data: monthly revenue figures, deposit counts, average balances, identified debits from other funders. This data can be reviewed by an underwriter in minutes rather than hours. It can also be exported to a CRM, fed into a scoring model, or flagged automatically when certain risk thresholds are breached.

For funders processing hundreds of deals per month, the difference between receiving raw PDFs and receiving structured data is the difference between scaling and hiring. One approach requires proportionally more staff as volume grows. The other holds staffing flat while throughput increases.

Real-World Implications for Growing Funders

Lightspeed's numbers are a leading indicator, not an outlier. The broader MCA market is experiencing similar dynamics. As deBanked reported, the combination of rising revenue and shorter payback periods reflects an industry-wide acceleration in funding velocity. Funders across the market, from mid-size shops processing 200 deals a month to larger operations north of 1,000, are encountering the same constraint: their front-end document workflows cannot keep pace with their back-end appetite for deals.

The competitive consequences are real. A funder who takes 48 hours to collect and process a complete submission package loses to a funder who does it in four. Brokers notice. They route deals to the funder who funds fastest, not the one who offers the best rate. As we discussed in our coverage of why MCA lenders lose deals to slow application intake, speed-to-fund is increasingly the primary competitive differentiator, and it starts long before an underwriter makes a credit decision.

Consider the renewal scenario specifically. A merchant whose payback period just completed is, at that exact moment, the most likely to accept a new offer. They are cash-flow positive relative to the previous advance, their business is presumably performing well enough to have repaid on schedule, and they have an established relationship with the funder. But if the renewal process requires re-submitting three months of bank statements via email, waiting for a coordinator to log them, and then waiting again for an underwriter to review them manually, the window closes. A competing funder with a faster intake process captures that merchant instead.

The Federal Reserve's small business lending data confirms that alternative lenders are capturing an increasing share of SMB financing. As that share grows, the funders with infrastructure built for scale will consolidate their advantage. Those still running on email-and-spreadsheet workflows will find themselves unable to process the volume their sales teams generate.

Frequently Asked Questions

What is bank verification software for MCA funders?

Bank verification software for MCA funders is a category of tools that automate the collection, parsing, and analysis of merchant bank statements during the underwriting process. Instead of manually reviewing PDF bank statements, funders use these platforms to extract key financial data, such as monthly deposits, average balances, and NSF counts, automatically. The best solutions also handle document intake through secure upload links or email forwarding, eliminating the need for manual file management.

Why does a shorter MCA payback period increase verification volume?

A shorter payback period means each merchant completes their advance faster and becomes eligible for renewal sooner. If a funder's average payback drops from eight months to seven, the same portfolio generates roughly 12% more renewal opportunities per year. Each renewal requires fresh bank statements and a new underwriting review. Without automated verification, this increased cycle speed overwhelms manual processes and creates operational backlogs that slow funding times.

How does asynchronous document collection speed up MCA funding?

Asynchronous document collection removes the funder from the back-and-forth of email-based submissions. Instead of waiting for a merchant to reply with attachments, the funder sends a single secure link where the merchant uploads all required documents on their own schedule. The documents are automatically organized and associated with the correct application. This eliminates delays caused by missing files, mislabeled attachments, and email thread confusion, often cutting days from the intake timeline.

Can AI accurately extract data from bank statement PDFs?

Yes, but accuracy depends on the model's training data. General-purpose OCR tools often struggle with the varied layouts of bank statements from different institutions. Purpose-built AI models trained specifically on financial documents achieve significantly higher accuracy because they understand the structure and context of bank statement data. These models can identify statement periods, balances, transaction categories, and anomalies that generic tools miss. Platforms like Let's Submit use this type of specialized extraction to deliver review-ready data to underwriting teams.

Conclusion

Lightspeed Capital's 73% MCA revenue growth is not just a headline. It is a signal that the entire industry's deal velocity is accelerating, and verification infrastructure must keep up. Shorter payback periods, faster renewals, and growing merchant bases all compound the document processing workload. Funders who continue to rely on manual intake workflows will hit a ceiling that no amount of underwriting talent can overcome.

The solution is not incremental. It requires rethinking how documents enter the pipeline in the first place. Asynchronous collection, AI-powered extraction, and structured data output are not future-state aspirations. They are table stakes for any funder planning to grow in this market. Visit letssubmit.ca to see how async verification and AI extraction can remove the bottleneck between your merchants and your underwriters.