How do MCA funders avoid defaults?
Most merchant cash advance defaults are visible in the bank statements before the deal is funded. They come from a payment sized against revenue the business does not really have, stacked on obligations the merchant did not disclose. Avoiding them is mostly a matter of measuring the existing burden honestly and sizing against what is left.
What actually causes MCA defaults?
- Undisclosed stacking. Three simultaneous positions debiting daily leave nothing for a fourth, whatever the application says.
- Revenue that is not revenue. Transfers, loan proceeds and double-counted processor settlements inflate deposits and every ratio built on them.
- Thin liquidity. A business can post good monthly revenue and still run a minimum balance near zero, which is where a daily debit does its damage.
- Seasonality read as growth. Three strong months in the right part of the year is not a trend.
- Altered documents. If the statement was edited, none of the above can be measured at all.
Which signals predict default risk in bank statements?
Five figures do most of the work, and they are more useful together than separately.
- Negative days across the period, and the worst count on any single statement.
- Minimum balance — not the average, which hides the trough the payment has to clear.
- NSF and overdraft counts, which show whether existing obligations are already straining the account.
- Existing daily burden — every detected advance, totalled, against the revenue it is drawn from.
- Revenue consistency month to month, to separate a steady business from one trending down.
How do you size a payment the merchant can survive?
Start from true revenue rather than stated revenue, apply your holdback rate to get a daily capacity, then subtract what is already committed. What remains is the honest ceiling — and it is frequently smaller than the requested amount implies.
Then test it. Simulating a proposed payment against the account’s historical end-of-day balances shows how often it would have caused a shortfall over the period you can actually see. Read that conservatively: those balances already absorbed whatever the merchant was paying at the time, so the headroom you are measuring sits on top of existing obligations rather than replacing them.
What should you do with a marginal deal?
Declining is not the only answer, and reflexively declining marginal files costs volume that a smaller structure would have earned safely.
- Fund less. A materially smaller advance at a shorter term often clears where the requested amount does not.
- Attach stipulations. A full accounting of existing positions, or a payoff of one, changes the arithmetic before you commit.
- Verify the business independently when the identity signals are weak — an entity that cannot be corroborated is a different risk from a thin one.
- Return for information rather than deciding on a file you know is incomplete.
How does automation help?
Not by deciding for you. The parts worth automating are the ones people get wrong under volume: parsing every transaction, separating true revenue, finding every repeating funder debit, and doing the arithmetic the same way on every file. That consistency is what makes a portfolio’s default rate a function of policy rather than of who happened to underwrite the deal.
See how cash flow underwriting works, or walk the whole process in the MCA Verify user guide.
Frequently asked questions
What is a typical MCA default rate?
It varies widely by funder, paper grade and position, and any single published figure should be treated sceptically. What is consistent is the direction: default rates rise sharply with the number of simultaneous positions and with negative-day counts in the months before funding.
Is stacking always a decline?
No — but undisclosed stacking is a different question from disclosed stacking. A merchant who discloses two positions and shows the capacity to service a third is a credit decision. A merchant whose statements show three positions against one disclosed is a disclosure problem first.
How many negative days is too many?
That is a policy question rather than a universal threshold, and it should be set as policy and applied consistently. What matters more than the count is where the negative days fall: clustered around existing debit dates is a capacity signal, scattered is a cash management one.
Can you catch altered statements before funding?
Often, yes — by checking that each statement’s arithmetic reconciles, that closing balances match the next opening balance, and that the document itself shows no signs of editing. See how lenders detect doctored bank statements.
Curious what your last few defaults looked like before funding? Bring them to a demo — running defaulted files back through the analysis is the fastest way to see what was already visible.