How Merchant Growth's $240M Credit Expansion Proves MCA Funders Need Bank Verification Software for Funders

A $240M Credit Facility and the Verification Problem It Exposes

When Merchant Opportunities Fund announced its collaboration with Merchant Growth to expand their credit facility to $240 million, the Canadian alternative lending market got a clear signal: institutional capital is available for funders who can deploy it responsibly at scale. But the announcement also exposes a problem that rarely makes the press release. Deploying $240M in merchant cash advances requires reviewing thousands of bank statements, IDs, void cheques, and signed applications. The question every operations leader at a growing funder should be asking right now is whether their bank verification software for funders can keep pace with their capital.

This is not a hypothetical concern. In 2026, the gap between available capital and operational throughput is the binding constraint for most mid-market MCA funders. Earlier this year, Merchant Growth's facility sat at $195M. The jump to $240M, a 23% increase, means proportionally more applications flowing through intake, more bank statements to parse, and more fraud signals to catch. If the verification workflow stays manual, the only way to keep up is to hire, and hiring underwriters is slow, expensive, and introduces inconsistency.

This article breaks down what a credit facility expansion of this magnitude demands from a funder's verification stack, why manual processes become a liability at scale, and how asynchronous bank verification software closes the gap.

Why Capital Expansion Stresses Verification Workflows

The Throughput Ceiling of Manual Bank Statement Review

A single MCA application typically requires four months of bank statements, a government ID, a void cheque, and a signed application. An experienced underwriter can manually review and extract data from one complete file in 20 to 40 minutes, depending on statement complexity, the number of accounts, and whether the documents arrive as clean PDFs or phone photos of printed pages. At that pace, one underwriter processes 12 to 20 files per day.

Scale that against a $240M facility. If the average advance is $75,000, the funder needs to originate roughly 3,200 deals per year to deploy the capital. Factor in a 30% approval rate, and the intake team is reviewing over 10,000 applications annually, or about 40 per business day. That is two to three full-time underwriters doing nothing but initial document review, before any credit analysis even begins.

The math gets worse when you account for incomplete submissions. Industry data consistently shows that 40% to 60% of initial document packages arrive missing at least one required item. Every incomplete submission triggers a follow-up cycle: emails, calls, texts, waiting. Each cycle adds one to three days and consumes time that could be spent on fundable deals. As we explored in our analysis of how Merchant Growth's earlier $195M credit facility reshaped bank verification demands, the operational burden compounds faster than headcount can address it.

What Institutional Capital Partners Actually Audit

Credit facility providers do not simply write a check and walk away. The institutional investors behind a $240M facility, whether they are pension funds, family offices, or structured credit desks, conduct periodic audits of the funder's origination and underwriting practices. These audits increasingly focus on three areas that directly implicate verification workflows.

First, document provenance. Auditors want to see that bank statements were collected directly from the merchant or a verified source, not forwarded through a chain of brokers where tampering can occur. Second, data accuracy. If the funder's underwriting model relies on average monthly revenue of $92,400, the auditor wants to trace that number back to the raw bank statement and confirm the extraction was correct. Third, consistency. A manual process where one underwriter rounds deposits differently than another introduces variance that auditors flag.

Bank verification software for funders addresses all three concerns by creating an auditable chain of custody from the moment a merchant uploads a document through extraction, review, and export. Let's Submit, for example, generates a timestamped record of every document received, every field extracted by AI, and every human review action taken. That kind of trail is not a nice-to-have when your capital partner is a $240M credit facility. It is a requirement.

Fraud Risk Scales With Volume

A larger portfolio means a larger target. As funders expand their origination volume to deploy a bigger facility, they inevitably encounter more fraudulent applications. Fabricated bank statements, inflated deposit figures, synthetic identities, and stacking schemes all become statistically more likely as the application funnel widens.

Manual review catches obvious fabrications, but it struggles with sophisticated fraud. A well-crafted fake bank statement might use the correct bank logo, proper formatting, and plausible transaction descriptions while subtly inflating daily ending balances. Human reviewers who process dozens of statements per day develop fatigue and pattern blindness. AI-powered document verification, by contrast, applies the same scrutiny to the 40th statement of the day as it does to the first. It flags font inconsistencies, metadata anomalies, and deposit patterns that deviate from expected distributions for a given business type.

We covered this dynamic in detail when examining how MCA lenders detect fabricated cash flow patterns with AI fraud detection. The core insight holds: fraud detection at scale is a software problem, not a staffing problem.

How Asynchronous Verification Solves the Scale Problem

The traditional MCA document collection process is synchronous. A broker or sales rep contacts the merchant, requests documents, waits for them to arrive by email, reviews them for completeness, follows up on missing items, and then forwards the package to underwriting. Every step requires a human in the loop, and every handoff introduces delay.

Asynchronous bank verification flips this model. Instead of chasing documents, the funder sends the merchant a secure upload link. The merchant opens it on their phone, sees exactly what is needed (four months of bank statements, a government ID, a void cheque, a signed application), and uploads everything in one session. No app to download. No account to create. Just a mobile-optimized page that accepts PDFs, photos, and even camera captures of paper statements.

Let's Submit was built around this async workflow. When a lead expresses interest, the platform's AI sales rep, Sabbie, can text the merchant a secure upload link during the initial conversation, before a human advisor even gets involved. By the time the callback is scheduled, the bank statements are already uploaded, parsed by AI, and organized into a clean application. The underwriter who takes the call is looking at extracted revenue figures, daily balances, NSF counts, and time in business, not a pile of unorganized PDFs.

This is what it looks like to match verification throughput to a $240M deployment pace. The capital is there. The merchants are there. The bottleneck is the intake process, and async verification removes it.

Why the Canadian Market Amplifies These Pressures

Merchant Growth operates primarily in the Canadian market, where the MCA landscape has distinct characteristics that intensify the verification challenge. Canada's consumer-driven banking framework is still evolving, meaning open banking data feeds that American funders increasingly rely on are not yet universally available north of the border. Canadian funders still depend heavily on uploaded bank statements as the primary verification artifact.

At the same time, regulatory scrutiny in Canada is tightening. Provincial courts have shown willingness to challenge MCA pricing, and lenders face growing pressure to demonstrate that their underwriting processes are thorough and fair. A $240M credit facility with institutional backing raises the stakes further. If a funded deal goes bad and the underwriting file shows sloppy verification, the reputational and legal exposure compounds.

Canadian funders expanding their credit facilities in 2026 face a unique combination of pressures: high document dependency, emerging regulatory risk, and institutional audit expectations. Bank verification software purpose-built for this environment is not optional. It is the infrastructure layer that makes the capital deployable.

Frequently Asked Questions

What is bank verification software for funders?

Bank verification software for funders is a category of tools that automate the collection, validation, and analysis of bank statements and financial documents during the MCA underwriting process. These platforms typically offer secure document upload portals, AI-powered data extraction that pulls revenue, deposit, and balance figures from raw statements, and fraud detection features that flag anomalies like altered documents or inconsistent transaction patterns. The goal is to replace manual data entry and email-based document chasing with a streamlined, auditable workflow that scales with origination volume.

Why do credit facility expansions require better verification processes?

Credit facility expansions require better verification because the capital providers behind those facilities audit the funder's origination and underwriting practices. A $240M facility means more deals need to be originated, which means more bank statements to review, more fraud to catch, and more data accuracy to maintain. Institutional investors expect consistent, traceable verification workflows. Manual processes introduce variance, errors, and gaps that auditors flag, potentially jeopardizing the facility itself. Automated verification creates the consistency and audit trail that capital partners demand.

How does async document collection speed up MCA underwriting?

Async document collection speeds up MCA underwriting by removing the back-and-forth between sales reps and merchants. Instead of emailing requests and waiting for responses, the funder sends a secure upload link that the merchant completes on their own time, typically from their phone. Documents are uploaded, validated for completeness, and parsed by AI before an underwriter ever touches the file. This can compress the intake cycle from days to hours, because the merchant controls the pace and the software handles the organization. Let's Submit integrates this async collection directly into the lead engagement workflow, so documents arrive alongside the callback booking.

How do MCA funders detect fabricated bank statements at scale?

At scale, MCA funders detect fabricated bank statements using AI-powered document verification that analyzes both the visual characteristics and the financial content of uploaded statements. AI models check for font consistency, metadata integrity, logo accuracy, and formatting patterns that match known bank templates. On the financial side, machine learning algorithms evaluate whether deposit patterns, daily balances, and transaction descriptions are consistent with the stated business type and revenue. These checks run automatically on every uploaded document, catching fabrications that a fatigued human reviewer might miss after processing dozens of files in a single day.

Conclusion

Merchant Growth's credit facility expansion to $240M is a milestone for the Canadian MCA market. It is also a proof point for an industry-wide reality: capital is not the constraint anymore. The constraint is the operational infrastructure needed to deploy that capital responsibly, quickly, and at scale. Bank verification software for funders is the layer that turns available capital into funded deals without proportionally scaling headcount or risk.

Let's Submit provides exactly this layer. From AI-powered outreach that books callbacks and collects documents in the same conversation, to automated extraction that turns raw bank statements into clean, auditable applications, the platform is built for funders who are scaling. Visit letssubmit.ca to see how async verification fits into your workflow and keeps your origination pace matched to your capital.