MCA Default Rates: What the Number Actually Hides

MCA default rates get thrown around in board decks and ISO pitches like they mean one thing, but ask three funders how they define a default and you will get three different answers. Some count a file as defaulted the day a merchant stops paying. Others wait until the file goes to legal or gets sold to a collection agency, which can be months later and after a restructure or two. If your default rate looks clean compared to a competitor, check whether you are measuring the same event. A fund that renews distressed merchants into new advances before they technically default will show a lower default rate and a worse underlying book, and nobody on the outside can tell the difference from the headline number alone.

The fix that actually helps on the desk is tracking by vintage, not by blended portfolio. Pull every advance funded in a given month and follow that cohort through its full term, then compare it to the cohort funded the month before and the month after. A blended default rate across the whole book can look stable while one vintage is quietly rotting, usually because underwriting loosened for a few weeks to hit a funding target, or because a batch of files came from a broker who was pushing volume over quality. I have seen a fund with a flat trailing default rate for a year discover, once they broke it out by vintage, that three specific months were carrying almost all the losses. Those three months traced back to a single ISO relationship that got cut the following quarter.

Vintage tracking also forces you to be honest about what a default actually represents in terms of stacking and timing. A merchant who defaults in month two of a six month term behaved very differently than one who paid cleanly for four months before going dark. The first case usually points to a file that should never have been approved, maybe a cash flow pattern that was already thin or a prior advance balance that was underreported. The second case often points to something that happened after funding, a new stack from another funder, a seasonal drop, a dispute with a processor. Both show up as the same default in a blended rate, but they call for different responses. One is an underwriting miss. The other is a portfolio monitoring miss, and it tells you whether your post funding checks are catching new debt before it compounds.

None of this requires new software or a change in your approval criteria. It requires discipline in how you log the default date, the vintage, and the stacking position at the time of default, then actually reviewing that data by cohort instead of as one trailing number. At Ultimate Underwriting we tell funds the same thing every time this comes up: a default rate you cannot break down by vintage and cause is not a metric, it is a headline. Build the habit of asking what is inside the number before you decide what the number means.