Aggressive collections can win an invoice and lose an account worth ten times that. Here's how to structure escalation without burning a relationship.
B2B collections is a fundamentally different discipline from consumer collections — and the escalation logic should reflect that. When a consumer account goes 60 days past due, the financial relationship is probably the only relationship at stake. When a B2B customer goes 60 DPD, there may be a five-year commercial relationship, an active sales negotiation, an open service ticket, and a sales rep who will call the AR manager personally if they think the collections team is about to damage the account. The invoice is real. The account value is also real. The escalation ladder has to account for both.
Most AR teams we encounter don't have a formal escalation ladder — they have a dunning cadence (a sequence of reminders) and then an informal escalation when those reminders don't work, which usually means someone making a phone call or forwarding the situation to a sales rep with no structured handoff. That informality is the problem. Without a defined escalation structure, every high-stakes situation gets handled by whoever happens to be paying attention that day, with inconsistent tone, inconsistent timing, and no tracking of what was done or what was promised.
What an Escalation Ladder Is (and Isn't)
An escalation ladder defines, in advance, the sequence of increasing intensity in collections outreach — who contacts the customer, through what channel, with what message, at what trigger point. It's not a punitive framework. The goal isn't to threaten or pressure; it's to create consistent, proportionate responses to late payment that preserve the commercial relationship while still recovering the receivable.
Critically, the escalation ladder is not the same as the dunning cadence. Dunning handles the automated, low-intensity early follow-up — the net-30 reminder, the first-notice email, the second-notice email. The escalation ladder picks up when dunning hasn't resolved the situation and a human decision-maker needs to get involved. Most AR operations need both, and they serve different purposes.
The Four Rungs
A workable B2B escalation ladder has four distinct levels, with defined triggers for moving between them:
Rung 1: AR specialist direct contact (0-20 DPD)
The first human escalation step: an AR specialist calls or emails the customer's AP contact directly. The tone is neutral and helpful — "just wanted to confirm receipt of invoice #8821 and check if there are any questions on the billing." No pressure language, no urgency signals. The purpose is to confirm the invoice is in queue and surface any dispute or administrative issue (PO mismatch, approval hold, wrong billing address) before it becomes a 45-DPD problem.
Trigger: Invoice is 5-15 DPD and automated dunning has not received any response. Or invoice has elevated payment-slip risk signal even while still current.
Rung 2: Senior AR contact with payment commitment ask (20-40 DPD)
The conversation shifts. The AR team lead or senior AR specialist contacts the customer, by phone if possible, and asks directly for a payment commitment date. The tone is professional and factual: the invoice is now [N] days past due, we need a confirmed date. If the customer surfaces a dispute at this stage, it gets routed to a structured dispute resolution process with a timeline — not an open-ended "we'll look into it."
Trigger: Invoice is 20-40 DPD with no payment or payment plan confirmed. No active dispute in queue.
Rung 3: Cross-functional escalation — AR + Sales (40-60 DPD)
This is where most AR teams lack structure. When a material invoice (typically anything above a defined threshold, such as $10,000 or whatever represents top-decile invoice value for the portfolio) crosses 40 DPD without resolution, sales should be looped in. Not to take over collections, but to provide context: is there an active renewal negotiation? Is the customer having a known operational issue? Is the AR situation related to a service dispute the sales rep already knows about?
The handoff to sales needs to be structured — not a forwarded email chain, but a one-page summary of the collections history (attempts made, responses received, what was promised and not delivered) that gives the sales rep what they need to have a productive conversation. Sales should then have a defined window (5-7 business days) to either resolve the payment or report back that the situation requires direct AR escalation regardless.
We are not saying sales should run collections. That's a failure mode, not a solution. The purpose of Rung 3 is to use the commercial relationship as a lever — once — before moving to formal escalation. If the sales conversation doesn't produce payment or a concrete payment plan, it moves to Rung 4.
Rung 4: Formal collections action (60+ DPD)
At 60 DPD with no payment, payment plan, or active dispute in resolution, the account moves to formal collections treatment. This may mean: placing the account on hold for new orders, sending a formal demand letter (drafted or reviewed by legal), referral to a third-party collections agency, or initiation of small claims / commercial arbitration depending on invoice size. The specific action depends on portfolio policy and invoice size.
Critically, Rung 4 should not be reached without the account having been worked through Rungs 1-3 in sequence. Jumping to formal collections on a first offense for a long-tenured customer is a relationship-destroying mistake that AR teams occasionally make when they don't have a defined ladder and someone pulls the wrong lever at the wrong time.
Account Relationship Value as an Escalation Input
The escalation ladder described above is the default for mid-tier accounts. High-value accounts — customers representing 5% or more of annual revenue — warrant modified treatment at every rung. Specifically: earlier Rung 1 trigger (5 DPD rather than 15), direct AR manager involvement at Rung 2 rather than specialist, mandatory CFO or VP Finance notification at Rung 3, and legal review before any Rung 4 action.
The modification isn't because high-value accounts get a pass on payment. It's because the cost of mishandling a high-value account relationship — through premature escalation, the wrong tone at the wrong rung, or collections pressure during an active commercial negotiation — is asymmetrically high. The AR team needs to be operating with that asymmetry explicitly acknowledged in their escalation rules, not discovering it after the fact.
What Makes Escalation Ladders Fail
Three failure modes are common in practice. First, trigger points that are too vague — "when the invoice has been outstanding long enough" is not a trigger. Define the DPD threshold and the minimum amount explicitly, and make them part of the formal process documentation, not AR tribal knowledge. Second, escalation without a handoff protocol — passing an account from AR to sales without the relevant collections history is guaranteed to produce a duplicate outreach that confuses the customer and undermines credibility. Third, no tracking of escalation activity — if there's no record of what was done at each rung and what was committed by the customer, the next AR specialist or manager who touches the account is working blind.
The escalation ladder is only as useful as the discipline with which it's followed and documented. Inconsistency — escalating fast on small accounts, letting large ones drift because nobody wants to escalate a good customer — is how AR portfolios accumulate aged receivables that nobody can explain at the quarterly review.
Tying Escalation to Prediction
One of the structural problems with reactive escalation ladders is that they kick in after an invoice is already overdue. The more effective approach — the one that preserves relationships better — is to route accounts toward earlier, lower-intensity escalation steps before they hit the 30-DPD threshold. This requires knowing which invoices are trending toward late payment while they're still current.
When Cashvyne flags an invoice with elevated 60 DPD probability at day 10, the appropriate response isn't to skip to Rung 3. It's to move to Rung 1 immediately — a friendly, low-pressure confirmation call — which often surfaces a dispute or administrative issue that can be resolved before the invoice goes overdue. The same invoice, handled reactively at 35 DPD, requires a harder conversation, creates more friction, and has a lower recovery rate. Earlier, softer intervention is almost always better for the relationship and better for the AR outcome. The escalation ladder doesn't change — the entry point into it does.