How Milestone Bank's Capital Raise Reveals the Underwriting Depth Gap in MCA Lending

Institutional Capital Is Raising the Bar for MCA Underwriting

When Milestone Capital Partners closed its $11.5 million corporate note financing in June 2026, the headline looked routine. Another specialty finance platform raising growth capital. But the details underneath tell a different story about what institutional investors now expect from the funders they back.

Milestone's proceeds are earmarked to support continued growth in commercial specialty finance. That growth depends on deal quality. And deal quality, in the eyes of institutional capital, is measured not by volume or velocity alone but by the depth and traceability of underwriting decisions. For MCA funders competing for this kind of capital, that distinction matters enormously.

MCA underwriting best practices have long emphasized speed. Get the application in, pull a bank statement, check the basics, fund fast. That approach worked when the capital stack was simpler, when funders relied on their own balance sheets or syndication networks that operated on trust. It doesn't work when a BMO or Goldman Sachs is sitting on the other side of the table, asking for documentation that proves every funded deal was properly diligenced.

This article breaks down what the institutional capital shift means for MCA underwriting workflows, where the most common depth gaps live, and how funders can close them without slowing down.

What the Underwriting Depth Gap Actually Looks Like

Surface-Level Verification Is No Longer Enough

Most MCA funders verify bank statements. Few verify them well. The typical workflow involves receiving a PDF from a broker, scanning the first and last pages for average daily balance and monthly deposits, and making a gut decision informed by experience. That process might catch obvious red flags, but it leaves enormous blind spots.

Institutional investors auditing deal portfolios don't just ask whether bank statements were reviewed. They ask how. They want to see which fields were extracted, whether the extraction was automated or manual, what anomalies were flagged, and whether the underwriter documented their reasoning. When those questions surface and the answer is "our guy looked at it," the conversation gets uncomfortable fast.

The depth gap shows up in three specific areas. First, incomplete data extraction. Many funders pull only headline numbers from bank statements, ignoring transaction-level detail that reveals NSF patterns, recurring debt payments to other funders, or seasonal revenue swings. Second, missing audit trails. When a deal goes bad and the capital partner wants to understand what happened, funders without structured documentation can't reconstruct the decision. Third, inconsistent process. Different underwriters apply different standards to different deals, making portfolio-level risk assessment nearly impossible.

Why Speed Versus Depth Is a False Choice

The reflex in MCA lending is to treat speed and depth as opposing forces. If you dig deeper, you slow down. If you move fast, you skip steps. That framing made sense when "depth" meant manually reviewing every line item on a six-month bank statement. It doesn't make sense when AI-powered extraction can parse a 180-page PDF in seconds and surface the exact data points an underwriter needs.

Platforms like Let's Submit are built around this principle. Upload the documents, let AI extract business info, financials, and owner details automatically, then review and edit what the system surfaces. The underwriter's job shifts from data entry to data validation, which is both faster and more thorough. The audit trail is built in because every extraction, every edit, and every decision is tracked.

This matters beyond internal efficiency. When a capital partner audits a portfolio, they can see exactly what data was available at the time of the decision, who reviewed it, and what was flagged. That transparency is what institutional investors are buying when they fund specialty finance platforms. As we explored in our analysis of how investment-grade capital raises the stakes for MCA bank statement verification, the bar is only moving in one direction.

Stacking Detection Requires Transaction-Level Depth

One of the most consequential depth gaps involves stacking detection. When a merchant has multiple active advances from different funders, the risk of default compounds dramatically. Catching stacking before funding requires more than checking a database of UCC filings. It requires analyzing bank statement transactions for recurring debit patterns that match the payment structures of other MCA products.

This is where surface-level verification fails most visibly. A funder who reviews only monthly totals will miss the daily or weekly ACH debits that signal an existing advance. An AI extraction layer that categorizes every transaction and flags patterns consistent with MCA payments gives the underwriter a fighting chance to catch stacking before it becomes a loss.

The deBanked coverage of 1 Global Capital's $40 million loss on a single dealership deal is a case study in what happens when concentration risk meets shallow underwriting. That loss wasn't caused by a lack of bank statements. It was caused by a failure to extract, analyze, and act on the signals those statements contained.

Building an Institutional-Grade Underwriting Workflow

Closing the depth gap doesn't require hiring twenty more underwriters or licensing enterprise software that takes six months to implement. It requires rethinking how data flows through the underwriting process and where automation adds real value.

The first step is centralizing document intake. When applications arrive via email attachments, broker portals, and text messages simultaneously, documents get lost and versions get confused. A single intake mechanism, whether it's a secure upload link sent to the applicant or a dedicated email inbox that captures submissions automatically, eliminates the chaos at the top of the funnel. Let's Submit handles both approaches: funders can share a branded upload link with applicants or forward application emails to a dedicated inbox, and the platform captures everything in one place.

The second step is automating extraction with purpose-built AI. General-purpose OCR tools can read text from a PDF, but they don't understand the structure of a bank statement. They don't know that a line labeled "ACH Debit" on a Chase statement means something different from "Electronic Withdrawal" on a Wells Fargo statement. Purpose-built extraction models trained on financial documents produce structured, reliable data that underwriters can actually use. We covered this distinction in depth in our piece on how purpose-built AI models outperform general LLMs in MCA document verification.

The third step is building review workflows that create documentation as a byproduct. When an underwriter reviews extracted data in a structured interface, their edits and approvals become the audit trail. There's no separate step to "document the decision." The documentation happens automatically as part of the work. This is the kind of workflow institutional investors love because it produces consistent, auditable records without adding friction to the process.

The fourth step is connecting underwriting output to downstream systems. Extracted data that lives in a standalone tool creates another silo. Data that flows into a CRM, a syndication platform, or a portfolio management system becomes part of the institutional infrastructure that capital partners expect. Let's Submit's Salesforce integration, for example, lets funders sync extracted data to leads with a single click, keeping the underwriting record connected to the deal lifecycle.

What Capital Partners Actually Audit

Understanding what institutional investors look for during portfolio reviews helps funders prioritize their underwriting improvements. Based on patterns across the specialty finance space, capital partners consistently focus on several dimensions.

They examine whether the funder verified the merchant's identity and business legitimacy beyond the application form. They check whether bank statements were analyzed for consistency with stated revenue. They look for evidence that existing obligations were identified and accounted for in the advance amount. They evaluate whether the funder's process is consistent across deals or varies depending on who handled the file.

Funders who can produce structured extraction reports, timestamped review records, and flagged anomaly documentation for every deal in the portfolio will find capital conversations much easier. Those who can't will face either higher costs of capital or, increasingly, closed doors.

The Milestone note is a $11.5 million signal. But it sits alongside larger moves, including Merchant Growth's $195 million BMO facility expansion and Enova's $420 million securitization amendment. Each of these transactions implicitly raises the documentation standard for every funder in the market.

Frequently Asked Questions

What are MCA underwriting best practices when raising institutional capital?

MCA underwriting best practices for institutional capital include automated bank statement extraction with transaction-level detail, structured audit trails that document every underwriting decision, consistent processes across all deals regardless of the underwriter, and stacking detection through ACH debit pattern analysis. Capital partners expect to see that the funder verified identity, confirmed revenue against bank deposits, identified existing obligations, and documented the rationale for every advance amount.

How does AI improve MCA bank statement verification?

AI improves bank statement verification by parsing full transaction histories from PDF statements, categorizing each transaction by type, flagging patterns consistent with existing MCA obligations, and identifying anomalies such as NSF spikes or sudden deposit drops. Unlike manual review, AI extraction is consistent across every file and creates a structured data record that serves as both an underwriting input and an audit artifact. Platforms like Let's Submit use AI extraction to shift the underwriter's role from data entry to data validation.

Why do institutional investors care about underwriting documentation?

Institutional investors care about underwriting documentation because it is their primary mechanism for evaluating portfolio risk after the fact. When a deal defaults, the investor needs to determine whether the loss resulted from market conditions or underwriting failure. Without structured documentation showing what data was available, what was analyzed, and what decision was made, every default looks like an underwriting failure. Comprehensive documentation protects both the funder's reputation and their access to future capital.

Can MCA funders maintain speed with deeper underwriting?

Yes. The speed penalty from deeper underwriting comes primarily from manual data entry and manual document review. When extraction is automated and review interfaces are structured to surface only the data points that matter, underwriters can make better decisions in less time. The bottleneck in most MCA operations is not the analysis itself but the time spent hunting for information across scattered documents and email threads. Centralizing intake and automating extraction eliminates that bottleneck entirely.

Conclusion

The gap between what institutional capital demands and what most MCA funders deliver in underwriting documentation is real and growing. Every corporate note, every securitization amendment, and every credit facility expansion tightens the standard. Funders who invest in structured extraction, consistent processes, and built-in audit trails will find themselves on the right side of that trend. Those who don't will watch their capital options narrow.

Let's Submit gives MCA funders the infrastructure to close this gap without sacrificing speed. AI-powered extraction, centralized document intake, real-time tracking, and complete audit trails turn every deal into an institutional-grade underwriting file. Visit letssubmit.ca to see how async verification and automated extraction fit into your workflow.