[.green-span]Revenue-based financing underwriting: how lenders evaluate deals[.green-span]
Revenue-based financing underwriting: how lenders evaluate deals
Introduction
Revenue-based financing underwriting evaluates how durable the revenue stream that repays the advance is: its recurrence, predictability, retention, and customer concentration. Lenders measure it with connected bank, payment, and accounting data. They then size the facility and repayment cap to that revenue instead of leaning on collateral or a credit score.
That shift changes the whole credit process. Repayment rises and falls with sales, so the core question becomes how confident you are that revenue will keep arriving at today's level.
This guide covers what RBF underwriters evaluate, which data sources matter, how facilities get sized and capped, and how the 5 C's of credit apply. It closes with a step-by-step workflow, common pitfalls, and answers to frequent lender questions.
What revenue-based financing underwriting evaluates
RBF repays from a share of future revenue until a fixed cap is reached. Lighter Capital describes the cap as a "1.x" multiple applied only to the original amount, which creates a flat fee. Underwriting therefore centers on whether that revenue will hold up.
Revenue durability comes first
Durability is the probability that revenue keeps arriving at a predictable pace. Underwriters break it into four measurable signals.
- Recurrence: the share of revenue from subscriptions, contracts, or repeat buyers, often tracked as MRR and ARR.
- Predictability: month-over-month consistency, with low volatility in deposits and balances.
- Retention: churn, gross revenue retention (GRR), and net revenue retention (NRR) show whether the customer base holds and expands.
- Concentration: how much revenue depends on a few customers, since one lost account can break repayment.
Provider criteria reflect these signals. Lighter Capital's published fit criteria include at least $15K in monthly recurring revenue, "multiple, diverse customer accounts," and minimal churn. Stripe Capital weighs a growing business, a steady processing record, a large customer base, and a low dispute rate.
No regulator or standards body publishes industry-wide NRR, GRR, or concentration thresholds for RBF. Each lender sets its own limits based on portfolio performance and risk appetite.
Margin and EBITDA provide context
Margin matters, but mostly as a floor. Lighter Capital, for example, lists gross margin over 50% among its criteria. Above that floor, durability drives selection.
Consider two borrowers. One runs thin margins on steady, diversified subscription revenue. The other posts high margins on lumpy, project-based sales from three clients. The first is usually the better RBF fit, because the cap is repaid from revenue, and steady revenue makes repayment timing predictable.
EBITDA adds context on burn and runway. Lighter cites 12 to 18 months of cash runway.
Connected data replaces static documents
RBF underwriting runs on live financial data. Capchase asks applicants to connect banking, accounting, and subscription management platforms, according to its Stripe partner listing. Stripe's model is "based on the payment volume that you process on Stripe," with optional bank linking.
Cash-flow data has research support. A June 2025 FinRegLab study of 38,000+ fintech small-business loans found that adding cash-flow variables improved default prediction across all segments analyzed. Deposits and balances were the strongest variables. The study covered term-type loans, not RBF specifically.
How facilities are sized and structured
Three levers define an RBF facility: advance size, revenue share, and repayment cap. Published terms vary widely by provider, risk, and term. Treat every figure below as illustrative, not an industry standard.
- Advance size: Founderpath's guide, updated April 2026, describes advances of "typically 3-5x" monthly recurring revenue.
- Revenue share: The same Founderpath guide puts the share "usually between 2% and 8%" of revenue.
- Repayment cap: Founderpath describes a cap "typically 1.1x to 1.5x" the advance. Lighter's February 2026 illustration shows a $500K advance with a 1.2 cap, repaid as $600K over three years.
RBF products also differ in structure. Some use fixed monthly payments instead of a revenue share, as Founderpath's own revenue financing product does.
Stripe Capital structures repayment as a withheld share of sales, with the total equal to the advance plus a flat fee. Its loan products also carry minimum payments.
How RBF reweights the 5 C's of credit
The 5 C's still apply to RBF, but their weights shift sharply toward capacity.
- Capacity: the dominant factor, since revenue level, durability, and growth determine approval and size.
- Character: shown through KYB, payment history, dispute rates, and how the business manages existing obligations.
- Capital: read through cash balances and runway rather than owner equity.
- Collateral: a minor factor in most structures, since the revenue stream is the repayment source.
- Conditions: sector exposure, customer concentration, and the stack of financing already on the books.
Where Lendflow fits
Lendflow provides the data, decisioning, and automation infrastructure behind revenue-based and sales-based products, including MCAs and purchase of receivables.
- Connect data and route deals: Lendflow Connect aggregates data and routes deals across 75+ lenders and financing types through one integration.
- Decide 85% faster: Lendflow Intelligence turns credit and business data into decisions with configurable decision models.
- Review documents 80% faster: Lendflow Automate runs Doc Analyzer on bank statements and tax returns. Industry Map classifies NAICS codes, and Trust Score adds explainable composite risk.
A seven-step revenue-based financing underwriting workflow
A repeatable workflow keeps RBF decisions consistent as volume grows. These seven steps take a deal through funding and into ongoing monitoring.
- Run intake, KYB, and fraud checks. Verify the business entity, its owners, and its industry before pulling financial data. Classify the business by NAICS code, since sector shapes revenue behavior and eligibility.
- Connect bank, payment, and accounting data. Request consented connections to bank accounts, payment processors, billing platforms, and accounting systems. Extract structured data from uploaded bank statements and tax returns where connections are unavailable.
- Measure revenue durability. Calculate MRR and ARR, growth, volatility, churn, GRR, NRR, and top-customer concentration. Flag low balances, deposit drops, and rising dispute rates.
- Size the facility. Set the advance as a multiple of monthly revenue or a share of annual revenue, using your own program parameters. Discount for concentration, volatility, and short operating history.
- Price the deal and set the cap. Choose a revenue share that keeps payments affordable in a weak month. Set the cap to reflect risk and expected repayment term.
- Deliver the required disclosures. Several states require commercial financing disclosures, and some name "sales-based financing" specifically. Generate state-specific disclosures before signing, and confirm applicability with counsel.
- Monitor revenue and obligations. Keep data connections live after funding. Watch for revenue declines, new financing on the bank statement, and changes in customer mix that affect repayment pace.
Automate the data-heavy steps
Steps 1 through 3 carry the most manual work. Document extraction, industry classification, and composite risk scoring can run automatically as each application arrives. Teams can then concentrate review time on sizing and edge cases.
Route declines to a second look
A deal that misses one program's criteria may fit another lender's appetite or a different financing type. Decline waterfalls route those applications onward, so qualified borrowers are less likely to leave without an offer.
Keep decisions explainable
Every sizing and pricing decision should trace back to specific data points. Explainable scoring makes it easier to answer borrower questions, audit outcomes, and tune models as portfolio data accumulates.
Best practices and common pitfalls
Strong RBF programs share a few habits. Each one below pairs a practice with the mistake it prevents.
Underwrite revenue quality ahead of margin
High margins can mask lumpy, concentrated revenue. Use margin as a floor, then let recurrence, retention, and predictability drive the decision.
Measure customer concentration on every deal
A borrower with one dominant customer carries risk that averages hide. Set a concentration limit and reduce advance size as concentration rises.
Stress-test the revenue share
A share that works in an average month can strain a borrower in a slow one. Model payments against the weakest recent months, and confirm the business can still cover operating costs.
In 2024 survey data from the Federal Reserve's 2025 Report on Employer Firms, 51% of small employer firms cited uneven cash flows as a challenge.
Validate connected data against documents
Connected data and uploaded documents should tell the same story. Reconcile bank deposits with reported revenue, and investigate gaps before sizing the advance.
Refresh data before every decision
Statements from three months ago can miss a recent revenue drop. Pull fresh data at decision time and again before any renewal or top-up.
Account for existing debt and stacking
Existing obligations reduce the revenue available for repayment. In the same report's 2024 survey data, 41% of denied or partly approved firms cited too much existing debt, up from 22% in 2021. The survey covers all small employer firms and is not specific to RBF.
- Scan bank transactions for recurring debits to other financing providers.
- Treat undisclosed obligations found in the data as an underwriting signal.
- Recheck for new obligations during monitoring.
Treat disclosure compliance as part of the product
Venable LLP listed ten states with commercial financing disclosure requirements as of March 2026. Some of these states' laws expressly cover sales-based financing. Coverage depends on structure, size, location, and exemptions, so consult counsel before launch.
Conclusion
Revenue-based financing underwriting asks one central question: will the revenue that repays this advance keep arriving? Lenders answer it by measuring recurrence, predictability, retention, and concentration in connected bank, payment, and accounting data.
Sizing, revenue share, and caps then follow from that durability. Collateral and credit scores play a smaller role, and capacity becomes the dominant C of credit.
The lenders who scale RBF well build repeatable workflows with live data, explainable decisions, and state-aware disclosures. Lendflow supports that work with data aggregation through Connect, configurable decisioning through Intelligence, and document automation through Automate.
FAQs
What does revenue-based financing underwrite?
RBF underwrites the durability of a business's revenue stream. Lenders assess recurrence, predictability, retention, and customer concentration, since repayment comes from a share of future revenue.
How is an RBF facility sized?
Sizing is often expressed as a multiple of monthly revenue or a share of annual revenue. Terms and structures vary by provider, and some products use fixed payments. Founderpath's guide, updated April 2026, describes advances of "typically 3-5x" MRR as an illustrative example.
Can a high-margin business be a poor fit for RBF?
Yes. A high-margin business with lumpy or concentrated revenue can be a weaker fit than a thin-margin business with steady, diversified recurring revenue.
Does existing debt affect RBF eligibility?
Yes. Existing obligations reduce the revenue available to repay a new advance. Lenders review bank transactions for payments to other financing providers and factor them into sizing.
What documents and data do RBF lenders need?
Most lenders request KYB details, bank account connections, payment processor data, and accounting or billing system access. Bank statements and tax returns can fill gaps where live connections are unavailable.
