Key Takeaways
- Sixty-one percent of deals in a new Wells Fargo-backed fund go toward refinancing existing MCAs, creating a distinct underwriting challenge that requires deeper bank statement analysis than first-position deals.
- Refinancing underwriters must layer historical MCA repayment patterns on top of standard cash flow analysis, a task that overwhelms manual review processes.
- Bank verification software for funders must evolve to flag prior MCA obligations, daily debit patterns, and net cash flow after existing remittances to accurately assess refinancing eligibility.
- Institutional capital entering the MCA refinancing space raises the documentation bar, and funders who cannot produce audit-ready verification trails will lose access to these credit facilities.
MCA Refinancing Is No Longer a Side Play
When sixty-one percent of a fund's deals go toward refinancing existing merchant cash advances, that is not a niche strategy. It is the strategy. Founders First Capital Partners recently announced a $19 million capital raise for one of its small business financing funds, with Wells Fargo among the investors. The stated goal: consolidate and refinance existing MCAs at lower costs for merchants. For funders, brokers, and underwriters watching from the origination side, the implications are significant. Refinancing deals demand a fundamentally different approach to bank verification software for funders than first-position advances do.
A first-position MCA underwriter cares about gross revenue, deposit consistency, and time in business. A refinancing underwriter cares about all of that plus how much cash is already being siphoned by existing funders. The bank statements tell the story, but only if the verification process is built to read it. This article breaks down exactly how the MCA refinancing boom changes what funders need from their verification stack, what institutional investors expect to see, and where most manual processes fall short.
Why Refinancing Underwriting Demands More From Verification
Detecting Layered MCA Obligations in Bank Statements
The core challenge of refinancing underwriting is obligation detection. When a merchant has one or more active MCAs, their bank statements will show daily or weekly ACH debits that represent remittance payments. These debits reduce the merchant's actual disposable cash flow, which is the number that matters for determining whether a refinancing advance is viable.
Manual reviewers can sometimes spot these debits, but consistency is the problem. A merchant with three stacked MCAs from different funders will show three separate recurring debit patterns, each with slightly different amounts, frequencies, and payee names. Some funders use payment processors that obscure the debit source. Others split remittances across multiple transactions. In 2026, the complexity of stacked MCA repayment schedules has outpaced what a human reviewer can reliably parse in a reasonable timeframe.
This is where smarter bank verification catches stacking patterns that manual review misses. AI-powered extraction can categorize recurring debits, flag known MCA payment processor names, and calculate net cash flow after all existing obligations. The difference between gross deposits and net disposable cash is the entire underwriting decision for a refinancing deal.
Calculating Net Disposable Cash Flow
First-position underwriting often relies on a straightforward calculation: average monthly deposits multiplied by a factor rate, discounted by a holdback percentage. Refinancing underwriting adds a critical variable. You need to subtract the total daily remittance burden from the merchant's revenue before applying any factor.
Consider a merchant doing $90,000 per month in deposits with two active MCAs pulling $1,200 per day combined. That is roughly $36,000 per month in existing obligations, leaving $54,000 in net disposable revenue. An underwriter who looks only at the $90,000 top line and offers a $100,000 advance is making a dangerous mistake. The merchant's actual capacity to support a new remittance is based on the $54,000 figure, and even that requires a cushion for operating expenses.
Bank verification software for funders handling refinancing volume must automate this net cash flow calculation. Let's Submit's AI extraction pulls average monthly revenue, average daily balance, and NSF counts directly from uploaded bank statements, giving underwriters a clean starting point. For refinancing deals, the extracted data makes it immediately visible whether the merchant's cash flow can support a new position or if the existing stack is already too heavy.
Meeting Institutional Documentation Standards
The Wells Fargo involvement in the Founders First fund signals something important. Institutional capital demands institutional-grade documentation. When a bank like Wells Fargo puts money into a fund that originates MCA refinancing deals, the fund managers need to demonstrate that every deal in the portfolio was underwritten with verifiable, auditable data.
This means the days of screenshot bank statements and manually keyed spreadsheets are numbered for any funder that wants access to institutional credit facilities. As we explored in our analysis of how investment-grade capital raises the stakes for MCA bank statement verification, the documentation bar is rising across the industry. Funders who cannot produce a clean audit trail from document collection through extraction and underwriting decision will find themselves locked out of the cheapest capital.
Async document collection platforms like Let's Submit solve this by creating a traceable chain from the moment a merchant uploads their bank statements through AI extraction and review. Every document is encrypted, timestamped, and stored on Google Cloud infrastructure with role-based access controls. The result is a verification record that satisfies both the funder's internal compliance team and the institutional investor's audit requirements.
What the Refinancing Boom Means for Your Verification Stack
The Founders First raise is not an isolated event. Multiple forces are driving MCA refinancing volume higher. SBA programs have introduced waiting periods for merchants seeking to refinance MCAs through government-backed loans, pushing many borrowers toward private refinancing options instead. State-level regulatory pressure, including disclosure requirements in New York, Virginia, and Connecticut, is making the total cost of stacked MCAs more visible to merchants, which increases demand for consolidation.
For funders positioned as refinancing specialists, the operational challenge is throughput. Refinancing deals require more documentation review than first-position deals. You need the same bank statements, but you also need to analyze them more deeply. If your verification process adds two or three days to each deal because an underwriter has to manually trace ACH debits and calculate net cash flow, you are losing deals to competitors who have automated those steps.
The competitive advantage belongs to funders who can collect documents asynchronously, extract key data points with AI, and present a clean application to their underwriting team within hours rather than days. This is especially true for refinancing, where the merchant is often motivated to move quickly because their existing MCA stack is creating cash flow pressure. A merchant paying $1,200 per day in combined remittances is not going to wait a week for you to process their paperwork.
Speed matters, but accuracy matters more in refinancing. AI fraud detection that catches fabricated cash flow patterns becomes even more critical when the merchant has an incentive to understate their existing obligations. A merchant drowning in stacked MCAs may be tempted to provide selective bank statements that exclude accounts where remittances are being debited. AI-powered verification can flag inconsistencies such as deposits that appear in one account but correspond to debits missing from the submitted statements, or revenue patterns that are suspiciously smooth compared to industry norms.
Frequently Asked Questions
How do MCA funders verify existing obligations before refinancing?
MCA funders verify existing obligations primarily through bank statement analysis. They look for recurring ACH debit patterns that indicate active MCA remittances, cross-reference those debits against known payment processor names, and calculate the total daily or weekly remittance burden. Automated bank statement analysis tools can categorize these debits and compute net disposable cash flow after all existing obligations, giving underwriters a clear picture of refinancing viability without manual line-by-line review.
Why does institutional capital in MCA funds require better bank verification?
Institutional investors like banks and credit funds require audit-ready documentation for every deal in a portfolio. They need to verify that underwriting decisions were based on authentic, traceable financial data. This means funders must maintain encrypted, timestamped records of every bank statement collected, every data point extracted, and every underwriting decision made. Manual processes that rely on emailed PDFs and spreadsheet calculations rarely meet these standards, which is why funders pursuing institutional credit facilities are adopting automated verification platforms.
What is net disposable cash flow in MCA refinancing?
Net disposable cash flow is the merchant's total revenue minus all existing MCA remittance payments and essential operating expenses. Unlike gross deposits, which only show top-line revenue, net disposable cash flow reveals how much capacity the merchant actually has to support a new advance. For refinancing deals, this number is the most important figure in the underwriting decision. Bank verification software calculates it by identifying and subtracting all recurring MCA-related debits from total monthly deposits.
How does async document collection speed up MCA refinancing deals?
Async document collection allows merchants to upload bank statements, IDs, and signed applications from their phone or computer at any time, without scheduling a call or visiting a branch. For refinancing deals, where merchants are often under cash flow pressure and motivated to move quickly, this eliminates days of back-and-forth. Platforms like Let's Submit send the merchant a secure upload link via text, and AI extraction begins immediately once documents arrive. The underwriting team receives a clean, pre-populated application instead of raw PDFs.
Conclusion
The institutional money flowing into MCA refinancing is not a temporary trend. It reflects a structural shift in how the industry's best-capitalized players view the market. Funders who want to participate, either as originators feeding these funds or as direct refinancing lenders, need bank verification software that goes beyond basic document collection. They need automated obligation detection, net cash flow calculation, and audit-ready documentation trails.
Let's Submit was built for exactly this kind of workflow. Merchants upload their bank statements through a secure link, AI extraction pulls revenue, balances, NSFs, and recurring debits into a structured application, and your team reviews clean data instead of raw PDFs. Visit letssubmit.ca to see how async verification fits into your refinancing pipeline.