How David Roitblat's Merchant Retention Strategy Depends on Bank Verification Software for Funders

Merchant Retention Is the Real Growth Engine for MCA Funders

David Roitblat, CEO of Better Accounting Solutions, recently published a detailed argument on deBanked about building long-term merchant relationships that drive repeat business. His core thesis is simple: the MCA companies that win are not the ones closing the most first deals. They are the ones bringing merchants back for second, third, and fourth funding rounds. Acquisition costs shrink. Default rates drop. Margins expand.

Roitblat's advice centers on communication, transparency, and service quality. Those are necessary. But what he does not address is the operational infrastructure that makes repeat funding possible at scale. Specifically, how do you verify that a returning merchant's cash flow still supports a new advance? How do you do it fast enough that the merchant does not walk to another funder? And how do you do it without subjecting your team to the same manual document chase that slowed down the original deal?

The answer is bank verification software for funders, purpose-built for the MCA workflow. Without it, merchant retention strategies remain theoretical. With it, they become a repeatable system. This article breaks down how verified cash flow data powers every stage of the merchant retention lifecycle and why 2026 is the year funders must close the gap between relationship intent and operational capability.

Why Retention Economics Demand Continuous Bank Verification

The True Cost of Losing a Merchant to a Competitor

Every MCA funder knows that acquiring a new merchant through a broker network costs significantly more than renewing an existing one. Broker commissions, marketing spend, and underwriting labor for a first-time deal can consume 15 to 25 percent of the advance amount. A renewal, by contrast, should require a fraction of that effort because you already know the merchant.

The problem is that "knowing the merchant" is only as useful as your data. If six months have passed since the original advance, the bank statements you reviewed during underwriting are stale. The merchant's revenue patterns may have shifted. New debts may have appeared. Seasonal fluctuations may have altered the cash flow profile entirely. Without fresh, verified bank data, your underwriting team is essentially starting from scratch, which means the renewal takes nearly as long as the original deal.

This delay is where merchants disappear. A returning merchant who expects a quick renewal but instead gets asked to re-submit three months of bank statements, wait for manual review, and answer the same questions they answered before will accept a competing offer. Roitblat is right that relationships matter, but relationships do not survive operational friction.

Building a Longitudinal Cash Flow Profile

The most sophisticated MCA funders are moving beyond point-in-time bank verification toward longitudinal cash flow profiles. Instead of treating each funding round as an isolated underwriting event, they maintain a continuous financial picture of each merchant. Every set of bank statements, every verified deposit pattern, and every revenue trend line feeds into a cumulative profile.

This approach requires bank verification software that stores, categorizes, and compares financial data across time periods. When a merchant comes back for a renewal, the funder does not start from zero. The system already contains historical cash flow data, and the underwriter only needs to verify the most recent period against established baselines. AI-powered transaction categorization flags meaningful changes: a new recurring payment that looks like a competing MCA, a drop in average daily balance, or a shift in deposit frequency that signals a business model change.

As we explored in our analysis of how repeat merchant funding depends on smarter bank verification software for funders, this longitudinal approach cuts renewal underwriting time by more than half while simultaneously improving risk accuracy. The funder who can say "we already know your financials, let us just confirm the last 90 days" wins the deal every time.

Asynchronous Collection Eliminates the Friction That Kills Renewals

The single biggest operational failure in merchant retention is the document collection process. A merchant who had a positive first experience will still abandon a renewal if the re-application process is painful. Email chains requesting specific bank statement formats, follow-up messages about missing pages, phone calls to clarify which accounts to include: all of this friction accumulates.

Asynchronous bank verification solves this by decoupling document submission from underwriter availability. The merchant receives a single secure link. They upload their statements on their own time, from any device. The system validates document completeness, extracts data automatically, and queues the application for review. No back-and-forth. No scheduling conflicts. No deals dying in someone's inbox over a weekend.

Let's Submit was built specifically for this workflow. A returning merchant can upload their latest bank statements through the same portal they used for their first deal. The platform's AI extraction engine parses the documents, cross-references the data against the merchant's historical profile, and presents the underwriter with a pre-populated review screen highlighting only what has changed. The entire renewal process, from document request to underwriter review, can happen in hours instead of days.

How AI-Powered Verification Supports Each Retention Stage

Pre-Renewal: Detecting When a Merchant Is Ready

The best time to offer a renewal is before the merchant starts looking for one. Funders who wait for inbound requests are already behind. AI-powered bank statement analysis, applied to historical data, can estimate when a merchant's current advance will be substantially repaid and when their cash flow supports additional capital.

This is not speculative. Transaction pattern analysis on verified bank data can identify the repayment trajectory with high confidence. When the system detects that a merchant is approaching the renewal window, it can trigger an automated outreach. The merchant receives a pre-populated application link, and because their historical data is already on file, the submission is lightweight. This proactive approach, driven entirely by verified financial data, is what turns bank verification from a compliance function into a revenue generation tool.

Renewal Underwriting: Speed Without Sacrificing Accuracy

Speed is the competitive weapon in renewal underwriting. But speed without accuracy creates defaults, and defaults destroy the economics that make retention profitable in the first place. The tension between velocity and diligence is where most funders struggle.

AI-powered bank statement OCR resolves this tension by handling the labor-intensive work instantly. Transaction categorization, balance trend calculation, deposit pattern analysis, and negative day identification all happen within minutes of document upload. The underwriter's role shifts from data entry to judgment: reviewing flagged anomalies, assessing business context, and making the approval decision.

This hybrid model, where AI does the extraction and pattern detection while humans make the final call, is exactly the approach we described in our discussion of why humans fail at underwriting and why AI alone won't fix MCA lending. Neither pure automation nor pure manual review produces optimal outcomes. The combination does.

Post-Funding: Ongoing Risk Surveillance Through Verified Data

Merchant retention does not end at approval. The post-funding period is where defaults incubate, and early detection is the difference between a managed risk and a write-off. Funders who collect bank statements only at origination and renewal are flying blind between funding events.

Progressive funders are implementing periodic bank statement collection throughout the advance lifecycle. Not as an invasive surveillance measure, but as a value exchange: merchants who provide quarterly or semi-annual bank statements get access to faster renewals, higher advance amounts, or preferential pricing. The data feeds back into the longitudinal profile, creating an increasingly accurate picture of the merchant's financial health.

When this data reveals deterioration, the funder has options. They can restructure the advance, adjust the remittance schedule, or simply hold off on offering a renewal. Without the data, the only signal is a missed payment, which is far too late. As the Federal Reserve's research on small business financial health consistently shows, cash flow volatility is the primary predictor of small business distress, and the only way to monitor it reliably is through verified bank data.

Turning Verification Into a Retention Playbook

Roitblat's framework emphasizes that retention requires intentionality. Funders cannot accidentally retain merchants. They must design systems and processes that make returning easier than leaving. Bank verification software is the operational backbone of that system.

Consider the full lifecycle. A merchant applies through a broker. The funder collects bank statements via a secure upload link, extracts data with AI, underwrites the deal, and funds. Six months later, the system identifies the merchant as renewal-ready. An automated message goes out with a pre-populated upload link. The merchant submits their latest statements in minutes. The AI engine compares new data against the historical profile, flags any material changes, and presents a streamlined review to the underwriter. The renewal is approved the same day. The merchant never had a reason to shop around.

This is not hypothetical. This is what Let's Submit enables right now. The platform's applicant-facing upload portal, AI-powered extraction, and dashboard tracking were designed for exactly this kind of iterative relationship. Each interaction with the platform adds to the merchant's verified data profile, making every subsequent interaction faster and more informed.

The funders who are still treating bank verification as a one-time gate, something to get through at origination and forget about, are leaving their most profitable revenue stream unprotected. In a market where broker loyalty is thin and merchant switching costs are low, the funder with the fastest, most frictionless renewal process wins. And that process starts with bank verification software built for the way MCA actually works.

Frequently Asked Questions

How does bank verification software improve merchant retention for MCA funders?

Bank verification software improves merchant retention by creating a continuous, verified financial profile for each merchant across multiple funding cycles. Instead of restarting the underwriting process from scratch with every renewal, funders can reference historical bank data, compare it against new submissions, and approve renewals significantly faster. This speed and convenience reduces the likelihood that merchants will seek funding elsewhere. Additionally, longitudinal cash flow data helps funders offer appropriately sized advances, which reduces default risk and strengthens the merchant relationship.

What is asynchronous bank verification and why does it matter for MCA renewals?

Asynchronous bank verification allows merchants to submit their bank statements through a secure online portal at any time, without needing to coordinate with an underwriter in real time. For MCA renewals, this eliminates the back-and-forth email chains and phone calls that slow down the process and frustrate returning merchants. The merchant uploads documents on their own schedule, AI extracts the relevant data automatically, and the underwriter reviews a pre-processed application. Platforms like Let's Submit are built around this asynchronous model, making renewals as simple as sharing a single link.

Can AI detect cash flow problems before an MCA default occurs?

Yes. AI-powered bank statement analysis can identify early warning signs of cash flow deterioration by comparing current transaction patterns against historical baselines. Indicators include declining average daily balances, reduced deposit frequency, new recurring outflows that suggest competing advances, and increasing negative balance days. When these patterns are detected between funding cycles, funders can take proactive steps such as adjusting remittance terms or delaying renewal offers, rather than discovering problems only after payments are missed.

How often should MCA funders collect bank statements from active merchants?

Leading funders collect bank statements at least quarterly from merchants with active advances, in addition to the standard collection at origination and renewal. This cadence provides enough data to detect meaningful cash flow changes without creating an excessive burden on the merchant. Many funders incentivize ongoing submission by offering faster future renewals or improved terms to merchants who maintain up-to-date financial documentation. The key is to frame periodic collection as a benefit to the merchant rather than a surveillance mechanism.

Conclusion

Merchant retention is not a soft skill problem. It is an infrastructure problem. The funders who retain the most merchants are the ones who make every interaction, from first application to fifth renewal, faster and easier than the last. That requires bank verification software purpose-built for the MCA lifecycle: asynchronous document collection, AI-powered extraction, longitudinal cash flow profiling, and seamless renewal workflows.

Let's Submit provides exactly this infrastructure. One secure link for document collection. AI that extracts and compares financial data across funding cycles. A dashboard that tracks every merchant from first submission to renewal approval. If your retention strategy depends on relationships, make sure your operations can keep up. Visit letssubmit.ca to see how async bank verification fits into your workflow.