How Merchant Growth's $195M Credit Facility Reshapes Bank Verification Software for Funders

Institutional Credit Expansions Are Rewriting Verification Standards

When Merchant Opportunities Fund, in collaboration with Merchant Growth, announced the expansion of its BMO credit facility to $195 million, the headline told one story. The operational reality tells another. A facility of this size means that every deal in the portfolio faces a level of documentation scrutiny that most alternative lenders never planned for when they built their intake workflows. For funders watching this development in 2026, the signal is clear: bank verification software for funders is no longer a convenience tool. It is a prerequisite for accessing institutional capital.

The expansion follows Merchant Growth's earlier $150M milestone, which we analyzed in detail when examining how automated bank statement analysis supports lenders scaling credit capacity. What makes the jump to $195M different is the institutional expectations that come with it. BMO is not a warehouse lender willing to accept PDF folders and spreadsheet summaries. They want structured data, consistent extraction, and audit trails that trace every document from merchant upload to underwriting decision.

Most funders reach this crossroads somewhere between $50M and $150M in facility size. Below that threshold, manual processes can survive. Above it, they cannot. The question is whether your verification infrastructure was built for the portfolio you have today or the one your capital partners will demand tomorrow.

The Documentation Infrastructure Gap at Scale

What Institutional Capital Partners Actually Audit

Funders often assume that institutional credit partners care about default rates and portfolio performance above all else. That is true at the approval stage. But during ongoing facility management, the focus shifts to process integrity. Capital partners want to see that the funder's underwriting decisions rest on verified, traceable data.

This means every bank statement that informed a funding decision needs a clear chain of custody. When was it uploaded? By whom? What data was extracted? Did a human review the extraction? Were there discrepancies flagged? These are the questions that come up during facility audits, and they are the questions that manual verification workflows cannot answer consistently.

Consider a funder processing 200 applications per month. Each application includes three to six months of bank statements, a signed application, tax returns, and potentially voided checks or lease agreements. At that volume, the documentation overhead is not a staffing problem. It is a systems problem. Hiring more analysts does not create structured audit trails. It creates more opportunities for inconsistency.

Where Manual Verification Breaks Down

The failure mode is predictable. A funder operating with email-based document collection and manual data entry can produce underwriting decisions quickly when volume is low. But as the portfolio grows, three things happen simultaneously.

First, document collection becomes fragmented. Bank statements arrive via email, fax, broker portals, and sometimes text message. There is no single repository, and no consistent metadata attached to each document. Second, extraction quality varies by analyst. One underwriter might pull average daily balance from page two of a bank statement. Another might calculate it differently from the transaction register. Third, the audit trail disappears. When a capital partner asks to see the source documents behind a specific funding decision six months later, the funder scrambles through email threads and shared drives.

This is exactly the problem that async bank verification platforms solve. Let's Submit, for instance, gives each applicant a single secure upload link where they submit all required documents. The platform timestamps every upload, applies AI-powered extraction to pull business information, financials, and owner details, and creates a structured record that persists through the life of the deal. The funder's team reviews and edits the extracted data before approving, but the underlying audit trail is automatic.

Structured Data as a Facility Compliance Requirement

The distinction between extracted data and structured data matters here. Many funders use some form of OCR or document scanning to pull numbers from bank statements. That produces extracted data. But institutional capital partners need structured data, meaning data organized in consistent fields, tagged to specific documents, and exportable in formats that integrate with their own risk systems.

When a facility provider like BMO reviews a portfolio, they are not reading individual bank statements. They are analyzing aggregate data across hundreds or thousands of funded deals. If the funder's verification software produces inconsistent field labels, missing metadata, or unstructured text dumps, the portfolio-level analysis fails. The capital partner either imposes additional reporting requirements, which cost the funder time and money, or reduces the facility size to account for the documentation risk.

This is why the move from $150M to $195M is significant. It suggests that Merchant Growth's documentation infrastructure passed the test. For other funders aspiring to similar facility expansions, the implication is direct: invest in verification infrastructure before approaching capital partners, not after.

Verification Depth as a Competitive Advantage for Capital Access

The alternative lending market in 2026 is increasingly divided between funders who can access institutional capital and those who cannot. Platform lenders like Shopify and Square have enormous data advantages because they verify cash flow through their own payment processing systems. Independent MCA funders do not have that luxury. Their verification depends entirely on the documents merchants provide and the systems used to process those documents.

We explored this dynamic when analyzing how Parafin's 50,000 funded businesses expose the verification gap for independent MCA funders. Platform lenders verify in real time because they control the transaction data. Independent funders verify asynchronously because they rely on uploaded documents. The question is whether async verification can reach a level of depth and consistency that satisfies institutional capital partners.

The answer is yes, but only with purpose-built infrastructure. Generic document management tools were not designed for MCA underwriting workflows. They lack the AI extraction models trained on bank statement formats, the secure applicant-facing upload portals, and the real-time tracking dashboards that let underwriting teams monitor application status from submission to approval.

Let's Submit was built specifically for this use case. The platform provides two document intake paths: a secure upload link that funders share with applicants, and a dedicated email inbox that automatically captures forwarded application documents. Both paths feed into the same AI extraction engine, which pulls standardized fields from every document type. The result is a consistent, auditable data set that scales with origination volume.

For funders negotiating credit facility expansions, the ability to demonstrate this kind of infrastructure is a differentiator. Capital partners are not just buying the portfolio. They are buying confidence in the process that created it. As we noted when examining how MCA audit readiness demands automated bank statement analysis, the funders who invest in verification infrastructure before the audit always fare better than those who scramble to assemble documentation after the fact.

The $195M facility expansion is not just a milestone for one company. It is a benchmark for the industry. Funders who want institutional capital need to ask themselves whether their bank verification workflows can withstand the scrutiny that comes with nine-figure credit lines. If the answer is uncertain, the time to fix it is before the next capital conversation, not during it.

Frequently Asked Questions

Why do institutional lenders audit bank verification processes?

Institutional lenders audit bank verification processes because they need confidence that the portfolio data they are underwriting is accurate and consistently sourced. A credit facility is ultimately a bet on the funder's ability to originate quality deals. If the underlying bank statement data is unreliable, inconsistently extracted, or missing audit trails, the facility provider bears hidden risk. Auditing verification processes lets capital partners assess not just portfolio performance but the operational integrity behind every funded deal.

What is the difference between extracted data and structured data in MCA underwriting?

Extracted data is raw information pulled from a document, such as a dollar figure scanned from a bank statement. Structured data goes further by organizing that information into consistent, labeled fields that can be queried, compared across deals, and exported into external systems. For MCA underwriting, the difference matters because capital partners and auditors need portfolio-level analysis, which requires structured data. Platforms like Let's Submit produce structured outputs from AI extraction, ensuring that every field maps to a standard schema regardless of which analyst reviewed the application.

How does async bank verification support credit facility expansion?

Async bank verification supports credit facility expansion by creating scalable, auditable document collection workflows that do not require real-time merchant interaction. Instead of scheduling calls or waiting for faxed documents, funders send applicants a secure upload link where they can submit bank statements and other documents at their convenience. Every upload is timestamped and processed through AI extraction, producing the consistent audit trail that institutional capital partners require during facility reviews.

What should MCA funders look for in bank verification software?

MCA funders should look for bank verification software that provides secure applicant-facing upload portals, AI-powered data extraction with human review capabilities, real-time application tracking, and exportable audit trails. The software should be built specifically for MCA and alternative lending workflows rather than adapted from generic document management tools. Integration with CRM systems and the ability to handle multiple document types, including bank statements, tax returns, and identification documents, are also critical for scaling origination without adding manual overhead.

Conclusion

Merchant Growth's $195M BMO credit facility expansion marks a clear inflection point for the alternative lending industry. Institutional capital is available, but it comes with documentation expectations that manual verification workflows cannot meet. Funders who want to compete for nine-figure facility lines need bank verification infrastructure that produces structured, auditable data at scale.

Let's Submit provides the async document collection, AI-powered extraction, and real-time tracking that funders need to meet institutional standards without adding headcount. Visit letssubmit.ca to see how the platform fits into your verification workflow and positions your operation for the capital conversations ahead.