When to Escalate: A Collections Cadence Playbook

Most collections processes escalate reactively — someone notices an account is badly overdue and decides, in the moment, what to do about it. That works fine for the accounts anyone would have caught anyway. It fails quietly for the accounts nobody happened to look at that week, and it produces wildly inconsistent outcomes for the accounts that did get noticed, depending entirely on who was watching and how they were feeling that day.

A cadence fixes this by turning "what do we do about this account" into "what step comes next," decided in advance rather than improvised under pressure. Here's how to structure one, and where the thresholds should actually sit.

Start with DBT, not a calendar date

Days Beyond Terms (DBT) measures how many days a payment is overdue relative to the agreed terms — the number that matters isn't the calendar date an invoice was due, it's how far past that date the account currently sits. Commercial credit bureaus report DBT as a dollar-weighted average across a portfolio, but the same concept works at the individual invoice level: an invoice due Net 30 that hasn't been paid by day 45 is sitting at 15 DBT, full stop, regardless of what else is happening on the account.

Anchoring your cadence to DBT instead of a fixed calendar schedule matters because it's the only version of "how overdue is this" that stays accurate no matter when the invoice was issued. A cadence built on DBT escalates every account the same way, on the same logic, whether the invoice went out in January or June.

Why escalating thresholds work — even before you enforce them

The core idea behind a staged cadence isn't just organizational tidiness. Escalating consequences change behavior before the harshest consequence is ever actually applied. A customer who receives a clear, specific warning that a credit hold is coming in two weeks has a real incentive to resolve the balance before that happens — and critically, that incentive exists whether or not the hold would have actually been enforced. The threat of a harder consequence does real work on its own, as long as it's specific, credible, and consistently followed through on often enough that customers believe it.

This is also why vague, generic reminders tend to underperform: a reminder that just says "your account is overdue" carries no information about what happens next. A reminder that says "if this isn't resolved by [date], your account will be placed on credit hold" gives the customer something concrete to act on — and a reason to act now rather than later.

The three-tier structure

A cadence built around three escalation points, each triggering a materially different consequence, tends to work well for wholesale distribution accounts:

30 DBT — Credit hold

This is the first firm consequence, and it should be the first one, because it protects you from extending further exposure to an account that's already showing it can't keep current. A credit hold doesn't need to be dramatic — it simply means no new orders ship until the balance is addressed. It's also the easiest escalation to reverse cleanly and immediately once the account pays, which matters for preserving the relationship.

60 DBT — Bureau-reporting warning, and a shift in tone

At 60 DBT, the account has now missed two full cycles of resolution opportunity, and the conversation needs to change in two ways.

First, the account should be warned that continued non-payment may be reported to a commercial credit bureau — a consequence that follows the business well beyond this one invoice, since a bureau-reported delinquency affects how every other supplier evaluates that company going forward. This warning carries real weight even for accounts that, in practice, might not end up reported every time; the threat of a harder, longer-lasting consequence tends to change behavior on its own, independent of exactly how often it's followed through on.

Second — and this is a meaningful shift — this is the point where outreach should stop demanding the full past-due balance and start offering a structured payment arrangement instead. A partial, scheduled payment is a better outcome than continued non-payment, and offering one proactively signals good faith rather than rigidity. This isn't leniency for its own sake; it's a recognition that an account 60 days out may genuinely be working through a cash-flow problem rather than simply refusing to pay, and a payment plan gives them a realistic path back to good standing instead of an all-or-nothing demand that just produces silence.

90 DBT — Collection agency or legal referral

By 90 DBT, internal outreach has had two full escalation cycles to produce a resolution. If it hasn't, the account moves to a third-party collection agency or legal proceedings, depending on the size of the exposure and the relationship's likelihood of continuing. This is also the point where, for most distributors, the cost-benefit of continued internal effort shifts — specialized recovery resources tend to outperform continued internal chasing once an account has proven unresponsive through two prior escalation stages.

Warn 14 days before every escalation — every time

Each of the three thresholds above should be preceded by a warning sent 14 days in advance, not a surprise notice delivered the day the consequence takes effect. The warning should do three specific things: state clearly what's about to happen, state the exact date it happens, and state exactly what the customer needs to do to prevent it. Vague urgency doesn't accomplish this — a specific deadline and a specific required action do.

When the threshold actually arrives, the message that follows should do a different, equally specific job: confirm that the escalation has now taken effect, briefly remind the customer what led to it, and state clearly what needs to happen next to resolve it. Customers who feel blindsided by an escalation are more likely to get defensive than cooperative — customers who were warned clearly, on schedule, and then see that warning followed through on tend to take the next one seriously.

A sample cadence

Day (DBT)	Action
16	Warning: credit hold in 14 days if unresolved
30	Credit hold takes effect
46	Warning: bureau-reporting risk in 14 days; payment arrangement offered proactively
60	Bureau-reporting warning delivered; payment plan actively negotiated
76	Warning: agency/legal referral in 14 days if unresolved
90	Referred to collection agency or legal proceedings

One important exception: disputes and active promises to pay

None of the above should apply to an invoice under active dispute, or an account that has already made a specific promise to pay by a given date. Continuing to escalate against a customer who's disputing a charge in good faith, or who's already committed to a payment date, damages the relationship for no benefit and makes the eventual resolution harder, not easier. The cadence should pause automatically the moment a dispute is logged or a promise is made — and resume, with appropriate escalation, only if that promise is broken.

Keep it professional, regardless of the stage

Commercial collections aren't governed by the same consumer-protection rules that apply to personal debt collection, which gives businesses more latitude in how they pursue overdue accounts — but that latitude is not an invitation to threaten or harass. A collections process that stays professional and specific at every stage protects the relationship, protects your reputation as a creditor, and tends to produce better resolution rates than escalating tone alone ever does.

Automating what should be automatic

Every piece of the cadence above — the DBT tracking, the 14-day warnings, the escalation messaging, the automatic pause on disputes and promises — is mechanical enough to run without a person manually deciding to send each one. That's precisely where most internal collections processes break down in practice: not because the logic is wrong, but because consistently executing six precisely-timed touchpoints per delinquent account, across an entire portfolio, doesn't scale past a small handful of accounts done by hand.

That's the specific problem Thor's Collections is built to solve — automated, escalating outreach tied to each account's actual days-beyond-terms, with disputes and promises to pay tracked and automatically paused, so the cadence above runs the same way, every time, without anyone having to remember the next step.

If you want to see this cadence running against your own aging report, book a free demo and we'll walk through it live.