Back to Blog

How OnDeck's Growth Confidence Data Reshapes AI Underwriting for Merchant Cash Advance Renewals

Key Takeaways

  • OnDeck's latest data shows 93% of SMBs expect revenue growth, creating a wave of renewal and second-position MCA demand that manual underwriting cannot absorb.
  • AI underwriting for merchant cash advance must evolve beyond initial decisioning to handle renewal-specific signals like deposit velocity drift, seasonal revenue normalization, and existing obligation detection.
  • Platform lenders like Shopify and Square maintain sub-4% loss rates partly because their AI models continuously ingest transaction data between funding cycles, a capability independent funders must replicate.
  • Funders who treat renewal underwriting as a copy-paste of the original file are mispricing risk; AI-driven delta analysis between funding cycles closes that gap.
  • Let's Submit's async document collection and AI extraction pipeline lets funders capture updated bank statements from returning merchants without slowing the renewal cycle.
TL;DR: OnDeck's 93% SMB growth confidence metric signals a renewal-heavy funding cycle that exposes the limits of manual underwriting. AI underwriting for merchant cash advance must now handle renewal-specific risk signals, including deposit velocity changes between funding cycles, stacking detection on returning merchants, and seasonal revenue normalization. Funders who automate this delta analysis with tools like Let's Submit close renewals faster while maintaining portfolio quality.

The Renewal Wave That Manual Underwriting Cannot Handle

AI underwriting for merchant cash advance has mostly been discussed in the context of first-touch origination: a new merchant applies, bank statements get parsed, and a funding decision is made. But a different challenge is building momentum in 2026. OnDeck's most recent SMB growth confidence data shows that 93% of small businesses expect revenue increases over the next year. That confidence translates directly into demand for additional capital. Merchants who received a first advance six or nine months ago are coming back, and they are coming back faster than underwriting teams can process them.

This is not the same problem as scaling cold originations. Renewal underwriting carries its own complexity. The merchant's financial profile has shifted since the original file was approved. New obligations may exist. Revenue patterns may have changed seasonally or structurally. A funder who simply re-approves the same merchant at the same terms, without analyzing what changed between cycles, is accumulating hidden risk. And a funder who forces the merchant through a full re-application from scratch loses the deal to a competitor who moves faster.

The gap between those two extremes is where AI underwriting earns its value. Not by replacing human judgment, but by surfacing the specific deltas that matter between funding cycles so an underwriter can make a faster, better-informed decision.

Why Renewals Break Manual Underwriting Workflows

The False Familiarity Problem

When a returning merchant lands on an underwriter's desk, there is a natural temptation to treat the file as pre-approved. The business name is familiar. The original funding performed well. The merchant is asking for more, which feels like validation. This false familiarity is one of the most common sources of mispriced renewals in the MCA industry.

Between the first advance and the renewal request, a lot can change. The merchant may have taken a second position from another funder, creating a stacking situation that did not exist during the original underwrite. Monthly revenue may have shifted due to seasonality, a lost contract, or a new revenue stream that inflates deposits without improving collectability. NSF patterns may have emerged or worsened. The daily balance trajectory may have flattened even as gross deposits remained stable.

Manual underwriting struggles with this because it requires the analyst to remember, or re-read, the original file and then manually compare it against fresh bank statements. That comparison is tedious, error-prone, and slow. When renewal volume spikes, as it does when SMB confidence is high, the comparison step gets compressed or skipped entirely. As we explored in our analysis of how post-funding data gaps cost MCA lenders on renewal decisions, the absence of structured inter-cycle data is one of the largest unaddressed risk factors in the industry.

Deposit Velocity Drift Between Cycles

One of the most predictive signals for renewal risk is deposit velocity drift: the rate at which deposits are arriving compared to the original underwrite period. A merchant who was receiving 22 deposits per month during the first funding cycle but now shows 14 has experienced a structural shift, even if the total dollar volume of deposits has not changed dramatically. Fewer, larger deposits often indicate customer concentration risk. More frequent, smaller deposits may suggest a shift to a lower-margin revenue model.

AI-powered bank statement analysis can detect these patterns automatically by comparing the current submission against the extracted data from the original file. The system flags the velocity change, quantifies its magnitude, and presents it alongside the revenue delta. An underwriter who receives this comparison can make a risk-adjusted renewal decision in minutes rather than spending an hour re-reading two sets of statements side by side.

This is precisely the kind of extraction and comparison that Let's Submit's AI pipeline handles. When a returning merchant uploads their latest four months of bank statements through an async collection link, the system parses the documents, extracts deposits, daily balances, and NSF counts, and surfaces those figures alongside the data from the original application. The underwriter sees what changed, not just what the current numbers look like in isolation.

Stacking Detection on Returning Merchants

Stacking is always a concern in MCA, but it is especially dangerous on renewals because the funder already has capital deployed. Detecting a new daily ACH debit that was not present during the original funding cycle is critical. Manual detection requires the underwriter to scan every page of the new statements looking for unfamiliar recurring debits, a process that is both slow and unreliable when statement formatting varies across banks.

AI models trained on MCA transaction patterns can classify recurring debits by type, distinguishing between merchant processor settlements, loan payments, MCA remittances, and ordinary business expenses. When a new MCA-pattern debit appears on a renewal file that was not present on the original, the system flags it as a potential stack. This does not replace the underwriter's judgment about whether the stack is acceptable, but it ensures the stack is never invisible.

For funders processing high renewal volumes, this automated stacking check is the difference between portfolio-level risk management and deal-by-deal guesswork. We covered the mechanics of this detection process in detail in our piece on how to prevent MCA stacking fraud with smarter bank verification.

What Platform Lenders Get Right About Renewal Underwriting

The reason Shopify Capital can originate $1.4 billion in a single quarter while maintaining normalized loss rates, and the reason Square Loans has kept cohort losses below 4% through multiple economic cycles, is not simply that they have better data at origination. It is that they have continuous data between originations. Federal Reserve research on SMB financing access confirms that data continuity is one of the strongest predictors of lending performance, and platform lenders possess it by default.

When a Shopify merchant requests a second advance, Shopify does not need to ask for bank statements. It already knows the merchant's daily sales, refund rate, average order value, and chargeback history in real time. The renewal decision is essentially a delta calculation performed against a continuously updated baseline. There is no document collection step. There is no extraction step. There is no comparison step. The model simply evaluates whether the merchant's trajectory supports additional capital.

Independent MCA funders cannot replicate this infrastructure overnight. They do not sit inside the merchant's payment processing stack. But they can approximate the delta-analysis advantage by structuring their document collection and AI extraction workflows to preserve and compare data across funding cycles. This is the core architectural principle behind Let's Submit's approach: every document that passes through the system becomes part of a persistent merchant profile. When the merchant returns for a renewal, the system does not start from zero. It starts from the last known state and highlights what moved.

The competitive implication is clear. Funders who treat every renewal as a brand-new application are doing twice the work for half the insight. Funders who treat renewals as structured comparisons against a known baseline are making faster decisions with better risk calibration. As deBanked reported on Square's continued low loss rates, the advantage compounds over time because each funding cycle adds signal to the model.

Building a Renewal-Ready AI Underwriting Workflow

Implementing AI underwriting for merchant cash advance renewals does not require a full platform rebuild. It requires three specific capabilities layered onto an existing origination workflow.

First, persistent merchant data. The output of every bank statement extraction, including deposits, balances, NSFs, and classified debits, must be stored in a way that is queryable by merchant identity. When the merchant returns, the system retrieves the prior extraction and uses it as the comparison baseline. Without this persistence, every renewal is a cold start.

Second, automated delta reporting. The AI extraction engine must not only parse the new statements but also generate a structured comparison against the prior cycle. This comparison should include changes in average monthly revenue, changes in deposit count and velocity, new or removed recurring debits, shifts in daily balance floor, and changes in NSF frequency. Presenting these deltas in a standardized format lets underwriters absorb the renewal risk profile in seconds rather than minutes.

Third, async document collection that does not create friction for returning merchants. A merchant who funded with you six months ago should not have to fill out a full application again. They should receive a link, upload their latest four months of statements, and be done. Let's Submit's upload links are designed for exactly this scenario: the merchant taps a link from their phone, drops the PDFs or photos, and the system handles the rest. The funder's underwriting team sees the extracted data, the delta report, and the original file data all in one view.

Together, these three capabilities turn renewal underwriting from a bottleneck into a competitive advantage. The funder who can re-underwrite a returning merchant in hours rather than days captures the deal before the merchant shops it to a competitor.

Frequently Asked Questions

What is AI underwriting for merchant cash advance renewals?

AI underwriting for merchant cash advance renewals is the application of machine learning and automated document analysis to evaluate returning merchants seeking additional funding. Rather than treating a renewal as a new application, AI systems compare the merchant's current bank statements against data extracted during the original funding cycle. This delta analysis surfaces changes in revenue, deposit patterns, daily balances, and existing obligations, allowing underwriters to make faster, more accurate renewal decisions.

How do MCA funders detect stacking on renewal applications?

MCA funders detect stacking on renewals by using AI transaction classification to identify recurring debits in the merchant's latest bank statements that were not present during the original funding period. AI models trained on MCA payment patterns can distinguish between merchant cash advance remittances, term loan payments, and ordinary business expenses. When a new MCA-pattern debit appears, the system flags it for underwriter review, ensuring stacking is visible before additional capital is deployed.

Why do platform lenders like Shopify and Square have lower MCA loss rates?

Platform lenders maintain lower loss rates because they have continuous access to merchant transaction data between funding cycles. They do not rely on periodic bank statement submissions to understand a merchant's financial trajectory. This real-time data feed allows their AI models to detect risk changes immediately, rather than discovering them only when the merchant applies for a renewal. Independent funders can approximate this advantage by preserving extracted data from each funding cycle and running automated comparisons when the merchant returns.

How does async document collection speed up MCA renewals?

Async document collection speeds up renewals by eliminating the back-and-forth of email attachments and phone follow-ups. The merchant receives a secure upload link, submits their latest bank statements from their phone or computer, and the documents are automatically parsed and compared against prior cycle data. This process can happen outside business hours and does not require a live conversation, which means the underwriting team receives a complete, extracted renewal file by the time they start their workday.

Conclusion

The 2026 SMB confidence surge is not just an origination opportunity. It is a renewal stress test. Funders who built their workflows around first-touch underwriting are discovering that renewal volume exposes a different set of gaps: missing inter-cycle data, invisible stacking, and false familiarity that leads to mispriced deals. AI underwriting for merchant cash advance closes these gaps by turning every renewal into a structured comparison against a known baseline, not a manual re-read of a familiar name.

Let's Submit gives funders the infrastructure to collect updated documents from returning merchants asynchronously, extract the numbers with AI, and surface the deltas that matter. If your renewal pipeline is growing faster than your team can process it, visit letssubmit.ca to see how async verification and AI extraction fit into your workflow.

Ready to streamline your application intake?

Automate document collection and data extraction for MCA applications. Faster processing, fewer errors.

Get Started Free