Why MCA Underwriting Guidelines Need Exceptions Built In

MCA underwriting guidelines are supposed to create consistency, but the funds that get burned are usually the ones that treat their guidelines as unbreakable law rather than a starting position. I have sat in enough credit committee meetings to see the same mistake repeated: an underwriter flags a file that technically fails the written criteria, the file gets killed automatically, and nobody asks whether the exception makes sense. Good guidelines are written with enough structure to keep decisions consistent across a team, but with enough room to let an experienced underwriter use judgment on the files that do not fit neatly into a box.

The fix is to write your guidelines in two layers instead of one. The first layer is the hard floor, the things that are true kill criteria no matter what. If a merchant has an active bankruptcy, if the bank statements show forged deposits, if the business has been open for two months and claims revenue that cannot be verified, there is no exception that saves that file. Those rules should be short, unambiguous, and rarely revisited. The second layer is the softer guidance, the stuff that tells an underwriter what normal looks like so they can recognize when something is abnormal but still fundable. NSF days, holdback percentage relative to average daily balance, stacking position, these are places where a file can miss the stated range and still be a good credit if the underwriter understands why.

I worked with a shop once where the written guideline said no more than a handful of NSF days in a thirty day window, full stop. A renewal file came in from a merchant who had been performing well for over a year, paying every advance down early, but had six NSF days in one month because of a one time payroll tax issue they could document with a letter from their accountant. The guideline said decline. The underwriter on the file wanted to approve it based on history and documentation, but had no mechanism to do that without going around the policy entirely, which made the whole team nervous about ever bending a rule again. That is the real cost of guidelines with no built in flexibility: not that bad files get funded, but that good underwriters stop trusting their own judgment and start rubber stamping the document instead of reading the file.

When we help funders at Ultimate Underwriting rebuild their underwriting guidelines, we spend most of the time on that second layer, writing down not just the numbers but the reasoning behind them, so that an underwriter three years from now understands why the range exists and when it is safe to step outside it. Guidelines that explain the why behind a number train better underwriters than guidelines that just hand down the number. A written range without written reasoning turns into a rule nobody can safely break, even when breaking it is clearly the right call.