Merchant Cash Advance Underwriting

Merchant cash advance underwriting is the review a funder runs on a merchant's bank statements to decide whether to advance capital against future revenue, and on what terms. Because repayment comes out of daily or weekly deposits rather than a scheduled loan payment, the decision rests on true revenue, balance behavior, NSF and negative days, and whether the merchant already has advances stacked on top of each other. Credit scores matter far less here than they do in bank lending. The account is the credit file.

This article walks through what an MCA underwriter actually checks, the four numbers that decide the deal, how stacking is detected, and where funders lose money by reading a statement wrong.

Last updated July 2026.

What is merchant cash advance underwriting?

Merchant cash advance underwriting is the process a funder uses to evaluate a business's ability to repay a purchase of future receivables. The funder buys a fixed dollar amount of the merchant's future revenue at a discount, then collects it back through a percentage of daily or weekly deposits called the holdback. There is no fixed maturity date and no amortization schedule, so traditional credit analysis does not fit. Instead the underwriter answers a narrower question: does this account generate enough consistent revenue, with enough balance cushion, to surrender a slice of every deposit without the business failing?

That is why an MCA file looks nothing like a bank credit memo. There is rarely a spread of tax returns, often no financial statements, and the personal credit pull is a screening filter rather than the decision. What the underwriter has is three to twelve months of business bank statements, and everything is derived from them.

How do MCA underwriters evaluate a merchant?

Underwriting runs through a credit box: a set of thresholds the merchant either clears or does not. The specific numbers vary by funder and by position, but the categories are near universal.

An underwriter reads these together, not in isolation. A merchant with $95,000 of monthly revenue and eleven NSF events is a worse risk than one with $60,000 and none, because the second account has room and the first does not.

What is true revenue and why does it matter?

True revenue is the merchant's actual sales, calculated by stripping out every credit that is not money the business earned. It is the single most important number in MCA underwriting and the one most often computed wrong, because the deposit column on a statement is not a revenue line.

A merchant showing $180,000 of monthly deposits might have $110,000 of real sales once you remove the credits below. Size a holdback against the $180,000 figure and the merchant defaults, not through dishonesty but because the money was never theirs to remit.

Any tool or analyst that hands you a revenue figure without showing which credits were excluded, and why, is asking for trust it has not earned. The exclusions are where the judgment lives.

How many months of bank statements do MCA funders require?

Most funders require three to six months of business bank statements for a first position, and many ask for twelve on larger advances or seasonal businesses. Three months is enough to see current revenue and balance behavior. It is not enough to see a seasonal trough, so a landscaping company underwritten off May through July will look far stronger than it is in January. Twelve months exposes both the trend and the low point, which is why renewal and higher-dollar files usually demand it.

Missing statement periods are themselves a signal. A gap in the sequence is either a filing lapse or a month the merchant would rather you not see, and both deserve a question before funding.

How do funders detect stacking from bank statements?

Stacking is when a merchant takes a second or third advance while an existing one is still outstanding, and it is the largest single driver of MCA default. Each new position takes another slice of the same daily deposits, and past a certain point the merchant cannot fund payroll.

Detection is pattern matching on the debit column. Advance repayments look distinctive: a fixed amount, hitting Monday through Friday or every Thursday, under an ACH descriptor that often reveals nothing. A $487.50 debit landing every business day is not a utility bill. The work is to group debits by counterparty, match descriptors against known funder ACH patterns, and total the combined daily burden across every position found. A merchant already surrendering 22% of daily deposits to two funders has almost no room for a third, whatever the revenue says.

Doing this by hand means recognizing hundreds of funder descriptors from memory across a twelve month statement set. It is exactly the work that gets skipped at 6pm on a Friday, which is precisely when the stacked deals get funded. Our guide to detecting loan stacking from bank statements covers the descriptor patterns in detail.

What is a holdback and how is it set?

The holdback is the percentage of daily deposits the merchant remits to the funder until the advance is repaid. It typically runs from roughly 8% to 20% of daily card and deposit volume, though the range varies widely by funder and position. Unlike a loan payment, it flexes: a slow week remits less, a strong week remits more, and the payback period stretches or compresses accordingly.

Setting it is an affordability test against verified numbers. Take true monthly revenue, subtract the existing daily burden from any stacked positions already detected, and confirm that what remains still covers payroll, rent and the merchant's own operating costs after your holdback comes out. The holdback the account can carry, not the holdback the merchant will agree to, is the correct one. Note that the holdback is a percentage, while the factor rate determines total payback, and the two are frequently confused by merchants and brokers alike.

Some funders write the same credit as a revenue share rather than a fixed daily debit, so the payment flexes with collections. The structures are compared in revenue based financing vs MCA, and the funder-side workflow is the same set of statement metrics run through revenue based financing underwriting software.

What disqualifies a merchant from a cash advance?

Most funders decline on the account rather than the credit report. Recurring disqualifiers include a high count of NSF events, typically more than three to five in a month depending on the credit box; frequent negative days showing the account routinely runs to zero; a sharp revenue decline across the statement period; too few deposit days to support daily remittance; existing stacked positions consuming most of the daily deposits; and open bankruptcy or active tax liens against the business.

NSF events and negative days are not interchangeable, and treating them as one number hides information. An NSF is a returned item with a fee attached, meaning something bounced. A negative day is an account that dipped below zero and recovered, often through overdraft protection. The difference between NSF and negative days tells you whether the merchant is out of money or merely poorly timed.

How long does MCA underwriting take?

Funding decisions are often quoted in hours, and same-day funding is a competitive requirement in the space. What consumes the time is not the decision, it is the file preparation: submissions arrive from brokers as emailed zip files and photographed PDFs, someone identifies which document is which, and an analyst tallies deposits and hunts for positions by hand across several hundred transactions per month.

Funders shorten that path from both ends. On the intake side, the attachments and key fields can be pulled out of the submission emails automatically instead of opened one at a time. On the analysis side, extracting every transaction, classifying credits into true revenue, counting NSF and negative days and grouping advance debits by counterparty is mechanical work that software does consistently and an analyst does inconsistently at volume.

Automating the statement review

The metrics an MCA decision needs are all derivable from the statements, which means the underwriting bottleneck is extraction and classification rather than judgment. LenderAnalyzer's merchant cash advance software reads three to twelve months of statements in one pass and returns true monthly revenue net of transfers and financing proceeds, deposit frequency, average daily balance, NSF and negative day counts by month, and every detected advance payment grouped by funder with its combined daily burden. Every figure traces back to the transaction it came from, so a reviewer can check the exclusions rather than trust them.

Funders comparing tools in this category usually evaluate it alongside intake-first platforms; our Heron Data alternative comparison is honest about which bottleneck each one solves. You can run a real submission through the analyzer at the top of that page and see the full metrics set before you commit to anything.