How Auto-Decline Waterfalls Help Lenders Scale Underwriting

I was talking recently with the leadership team at a merchant cash advance lender, and one number in that conversation stuck with me. They decline roughly 90 percent of the applications that come through their pipeline. In merchant cash advance, where a business receives a lump sum in exchange for a percentage of its future sales, that is not an unusual figure. Underwriting standards in this space are tight, application volume is high, and a large share of applicants simply do not clear the bar. What made the conversation worth writing about was not the decline rate itself. It was what they had built around it.

Twenty-five percent of their total application volume is now being automatically declined before an underwriter ever opens the file. No manual review, no phone call, no judgment call. The system evaluates stated application data alongside cash-flow signals pulled from their OCR and data parsing vendor, runs that information against a set of underwriting rules configured in Salesforce, and sends a decline notice automatically. The underwriter who would have spent twenty or thirty minutes reviewing that file instead spends that time on an application that actually warrants their experience and discretion. Their stated goal is to keep expanding that percentage, not because they want to decline more people, but because they want their underwriting team spending its limited hours exclusively on the decisions that require a human being to make a judgment call.

The Problem Every Growing Alternative Lender Eventually Hits

If you run underwriting at a specialty or alternative lending shop, you already know the tension. Volume grows because the business is succeeding. Origination is doing its job, marketing is doing its job, and applications are coming in faster than they used to. But underwriting headcount cannot grow at the same rate. Underwriters are expensive to hire, expensive to train, and hard to find with the right combination of risk judgment and product knowledge. So the natural question becomes: how do we process more applications without proportionally growing the underwriting team?

Most lending organizations answer that question the same way at first. They try to make their existing underwriters faster. They build better queues, cleaner document checklists, faster document requests. Those are worthwhile improvements, but they treat every application as if it deserves equal underwriting attention. In a market where 90 percent of applications are ultimately going to be declined, that assumption is expensive. It means your most experienced, highest-paid underwriting talent is spending a meaningful share of its time confirming what the data could have told you automatically.

The lenders who have actually solved this problem did not make their underwriters faster. They changed what reaches an underwriter in the first place. That is the real operational shift behind an auto-decline system: it is not an efficiency tool bolted onto underwriting, it is a triage layer that sits in front of underwriting and decides which applications deserve human time at all.

Why the Instinct to Pull Everything Upfront Is the Wrong One

When most lending operations first consider building automated screening, the instinct is to go big. Pull a comprehensive report on every application the moment it arrives — background check, UCC filing history, a default database search, the full financial picture. It feels thorough. It feels like the safe, complete way to build a screening system. It is also the most expensive way to do it, and at volume, that expense compounds quickly.

The lenders who have engineered this well took a different approach. They built a waterfall. Rather than pulling every available data source on every application, they identified the two or three signals that are most predictive of an automatic decline — a hit in a default database, a specific type of UCC filing that signals prior distress, a cash-flow pattern in the bank data that reliably indicates an inability to repay. Those signals get pulled first, and only those signals. That initial pull might cost fifty cents to a dollar per application. If the application clears that first screen, the system automatically triggers the next layer of data collection. If it does not clear, the application is declined immediately and the more expensive comprehensive report is never purchased at all.

The math is straightforward once you see it laid out. If a lender is processing several thousand applications a month and 60 to 70 percent of those applications would have failed on the first one or two data points anyway, pulling a full report on all of them means paying full price to confirm a decision the cheapest data point already made. Sequencing the pulls so that the most predictive and least expensive signals are checked first means the expensive, comprehensive data only gets purchased on applications that have already demonstrated some baseline viability. Over a year, that difference shows up directly in operating cost. It also shows up in how much underwriting capacity is freed up, because every application that declines on the first data point never enters a queue at all.

The Real Question Is Sequencing, Not Just Data

This is the part of the conversation I think gets missed most often when lending organizations talk about automation. The question is rarely just what data should we use to make a decision. Most experienced underwriting teams already have a good sense of which data points matter. The more important and more overlooked question is in what sequence that data gets used, at what cost, and at what stage of the process each signal gets checked.

Getting the sequence wrong produces one of two bad outcomes. Either the lender pulls everything upfront and pays for a level of diligence that most applications never needed, or the lender pulls too little upfront and lets applications advance further into the process than they should, consuming underwriter time before the disqualifying signal ever surfaces. Getting the sequence right means the cheapest, most predictive signals act as a first filter, the moderately predictive and moderately priced signals act as a second filter, and the expensive comprehensive diligence is reserved for the smaller pool of applications that have already proven themselves worth that expense.

This is also where the value of an auto-decline waterfall extends beyond merchant cash advance. Any alternative lending operation processing meaningful volume against a lean underwriting team faces the same structural problem. Working capital lenders, equipment finance companies, small business lenders, and other specialty finance operations all deal with a similar reality: a sizable share of inbound applications will not qualify, and the cost of determining that should not require the same resources as approving a loan. The specific data points will differ by product and by risk model, but the discipline of identifying which signals are cheapest and most predictive, then sequencing data pulls accordingly, applies broadly.

What This Requires Operationally

None of this works as a one-time project. The lender I spoke with did not build their waterfall once and walk away. They are actively working to expand the percentage of applications that get automatically declined, which means they are continuously testing which signals are the strongest predictors of an eventual decline, and adjusting the rules that govern the automated decision. That requires a few things to be true operationally.

First, the underwriting rules need to live somewhere that is visible and adjustable without engineering intervention every time. If a rule change requires a developer to modify code, the feedback loop between what underwriting is learning and what the system is doing slows down dramatically. Rules configured directly in the lending platform, where risk and underwriting leadership can see and adjust the logic, keep that loop tight.

Second, the data has to actually reach the decision engine in a usable form. This lender’s system is pulling stated application data alongside cash-flow signals from an OCR and data parsing vendor. That only works because the parsing output is structured well enough to feed directly into an underwriting rule rather than requiring someone to read a PDF and manually determine what the cash-flow pattern indicates. A lot of lending operations have the data sources they need but not the integration layer to make that data usable at the moment a decision needs to be made. That gap is often the real obstacle to building an effective waterfall, more so than a lack of underwriting rules or ideas.

Third, the decline communication itself needs to be automatic and immediate. Part of what makes this operationally valuable is not just that the underwriter never touches the file, it is that the applicant gets a fast answer instead of sitting in a queue for days waiting for a human to eventually determine what the data already indicated. Borrower experience and operational efficiency are not competing goals here. A fast, automatic decline is a better experience for an applicant who was never going to qualify than a slow one, and it frees capacity for the applications that deserve real attention.

Where Human Judgment Still Belongs

It is worth being direct about what this approach is not. It is not a system designed to replace underwriter judgment on the applications that matter. It is a system designed to make sure underwriter judgment is spent where it belongs. The lender in this conversation was clear that their underwriting team’s time is now concentrated on the applications that have passed initial screening and actually warrant discretion — the deals where the data is mixed, where context matters, where a person with experience needs to weigh competing signals and make a call that a rule set cannot make on its own.

That distinction matters because it is easy to conflate automated screening with a broader push to remove underwriters from the process. That is not what is happening in the operations that have done this well. The automation is handling the clear-cut cases, the applications that would have been declined regardless, just more slowly and more expensively without it. The judgment calls, the applications that sit in genuine gray areas, are still going to a person. If anything, this approach makes the underwriter’s role more valuable, not less, because it removes the repetitive, low-judgment work and leaves the decisions that actually require their experience.

The Broader Lesson for Scaling Lending Operations

Every alternative lender I talk to is thinking about growth, and almost every one of them is thinking about it in terms of volume, marketing reach, or new products. Fewer of them are thinking about it in terms of the sequencing question this lender had already solved. As application volume increases, the cost of screening every application with the same level of diligence increases right alongside it, and at some point that cost structure becomes the limiting factor on how much growth an underwriting team can actually absorb.

The lenders who are scaling most efficiently right now are not necessarily the ones with the most sophisticated underwriting models. They are the ones who have taken the time to map out their decline reasons, identify which two or three signals catch the majority of those declines, and build the sequence and the systems to check for those signals first, automatically, before anything more expensive or more human gets involved. That is not a flashy operational change. It does not show up in a press release. But it is the kind of decision that determines whether a lending operation can double its volume without doubling its underwriting team, and that is exactly the kind of leverage every growing lender should be looking for.