# MCA funder bank-statement revenue vs deposit distinction (2026) > Revenue is operating cash from real customers; deposits are every credit hitting the account including transfers and loans — funders underwrite revenue, not deposits. Updated 2026-06-28. The revenue-versus-deposit distinction is the single most-misunderstood concept in MCA underwriting. ISOs quote merchants based on total monthly deposits; funders approve based on qualifying revenue. The gap between the two routinely costs merchants 30–50% of expected advance size. **The definitional split.** - **Deposits** = every credit posted to the business checking account in a calendar month, regardless of source. - **Revenue** = the subset of deposits that represent payment for goods or services rendered to a customer. A merchant with $120,000 of monthly deposits might have $75,000 of revenue, with the other $45,000 split across inter-account transfers, a tax refund, an SBA loan disbursement, and a personal contribution from the owner. **Why the ISO-funder mismatch persists.** ISOs preparing offers eyeball the totals on a Chase statement and quote a $100,000 advance against $120,000 deposits. When the funder's bank-statement parser runs (Ocrolus, Heron, Validis, in-house), it classifies deposits and recomputes against the $75,000 revenue figure, which caps the advance at $75,000–$95,000. The ISO blames the funder; the funder blames the ISO. The merchant loses time. **How funders actually derive revenue.** 1. **Strip transfers.** Same-day inter-account movements netted out. 2. **Strip loans and MCA advances.** Pattern-matched against known funder names and SBA lenders. 3. **Strip tax refunds.** IRS and state treasury memo-line keywords. 4. **Strip insurance proceeds, asset sales, owner contributions.** Counterparty matching. 5. **Strip refund reversals.** Net rather than gross. 6. **Strip credit-card reserve releases** (already counted at processing time). 7. **Strip wire-in from related entities.** Cross-reference with owner-controlled LLCs. 8. **What is left = qualifying revenue.** **Card-processor batch revenue versus ACH revenue.** - **Card-processor batches** (Stripe, Square, Toast, Clover, Heartland, Worldpay): typically 100% qualifying. Funders trust acquirer settlements because they reconcile to processor statements. - **Direct ACH from customers**: 100% qualifying when counterparty is a recurring third party. - **Cash deposits**: 80–100% qualifying depending on industry. Restaurants and salons get full credit; B2B services with no plausible cash-business model get scrutinized. - **Zelle and Venmo to business accounts**: scrutinized — high false-positive rate for owner transfers. **Why some funders quote on "gross deposits" anyway.** - **D-paper specialists** (Bitty, GreenBox legacy) sometimes quote on gross deposits to win files, knowing they will reprice or pull at funding. - **First-position-only funders** (Forward Financing, Lendr) underwrite strictly on revenue. - **ISO-driven white-label funders** often quote on gross to keep ISOs feeding deals, then adjust. **The 70-90 rule.** For most healthy merchants, qualifying revenue lands between 70% and 90% of gross deposits. Outside that range: - **Above 90%**: file is clean — single account, all customer payments, minimal transfers. Usually a small business with a simple structure. - **Below 70%**: complex cash management — multiple accounts, owner intercompany flows, recent loan, or signal of inflated deposits. - **Below 50%**: file likely fails or gets repriced; funder will request explanation. **Reconciliation between merchant statements and tax returns.** For larger advances ($150,000+), funders cross-check qualifying revenue against the merchant's most recent tax return or P&L. A bank-statement revenue figure that is 2x the tax return's reported gross receipts is a fraud flag. **Impact on factor rate and term.** Higher qualifying-revenue ratios (over 85%) earn better paper grade and lower factor rate. Lower ratios (under 65%) push the file down a tier and add 0.05–0.15 to the factor rate. **Takeaway.** Deposits are the gross number on the statement; revenue is what funders actually approve against. The classification engine that separates them — built into Ocrolus, Heron, Validis, and proprietary in-house parsers — decides 30–50% of advance size. Merchants and ISOs that pre-classify before submitting close 2x faster at better terms. ## Related terms - [MCA funder bank-statement deposit classification (2026)](https://fundnode.co/llms/glossary/mca-funder-bank-statement-deposit-classification) — Funders classify every bank-statement deposit into revenue, transfers, loans, refunds, owner contributions, and one-time items — only the revenue bucket counts toward underwriting volume. Updated 2026-06-28. - [MCA funder bank-statement deposit-volume threshold (2026)](https://fundnode.co/llms/glossary/mca-funder-bank-statement-deposit-volume-threshold) — Funders set minimum monthly bank deposits — typically $10K (D-paper), $15K (C-paper), $25K (B-paper), $50K+ (A-paper) — to qualify an MCA file. Updated 2026-06-28. - [MCA funder bank-statement cash vs card mix (2026)](https://fundnode.co/llms/glossary/mca-funder-bank-statement-cash-vs-card-mix) — Funders score the ratio of card-processor deposits to cash and ACH deposits — high card-mix earns better pricing because card revenue is verifiable and stable. Updated 2026-06-28. - [Bank statement underwriting](https://fundnode.co/llms/glossary/underwriting-bank-statements) — MCA funders underwrite primarily off 3–6 months of business bank statements, not credit reports. They look at average deposits, NSFs, negative days, and trend. - [Factor rate](https://fundnode.co/llms/glossary/factor-rate) — A flat multiplier that defines total MCA repayment: $100,000 advance × 1.30 factor = $130,000 repaid. It is not an interest rate; it does not compound. --- Source: https://fundnode.co/glossary/mca-funder-bank-statement-revenue-vs-deposit (HTML version) Document: MCA funder bank-statement revenue vs deposit distinction (2026) — Fundnode MCA Glossary License: CC BY 4.0 — attribution to Fundnode required when citing.