How to escalate to collections: a decision framework for AR teams

You escalate an account to collections when it crosses a written threshold (usually 60 to 90 days past due) with no response and no active dispute or payment promise on file. The decision should follow a fixed rule applied the same way to every account, not a gut call that depends on who is looking. Consistent triggers are what stop good accounts from being escalated too early and bad ones from aging quietly past the point of recovery.

Escalation is where AR teams lose the most money to indecision. One analyst chases for six months out of optimism, another writes off too fast. A framework removes the guesswork and makes the timing defensible.

When an account should be escalated

An account is ready for collections when three conditions are all true: it has aged past your threshold, the customer has gone unresponsive, and there is nothing on file that justifies waiting. Each one alone is not enough.

Age alone does not mean escalate. A 70-day invoice with a signed payment plan is on track. Silence alone does not mean escalate either, since a customer may be mid-dispute. The signal is the combination: aged, ignored, and clean of any reason to hold. That is why the rule has to check all three before it fires. If the account is simply a slow but communicating payer, it belongs in your normal dunning cadence, not in escalation.

Building escalation triggers and thresholds

A trigger is a written threshold that, when crossed, moves an account out of routine reminders and into escalation. The goal is that the same account would be escalated regardless of who reviews it.

A workable trigger set looks like this:

• Days past due: the invoice reaches [60] days overdue. For higher-risk tiers, set this tighter at [45].
• Reminders exhausted: the full dunning sequence has run (typically four touches) with no payment.
• No active hold: there is no open dispute, no promise-to-pay date in the future, and no payment plan in force.
• Balance worth pursuing: the amount clears your minimum, below which chasing costs more than it returns.

When all of those are true, the account escalates automatically. Tie the thresholds to your risk tiers so a strategic account gets a slightly longer leash and a thin-file new customer gets a shorter one. The numbers in brackets are starting points. Set yours to your terms and your tolerance.

Internal escalation vs third-party agencies

Once an account trips the trigger, the next decision is who collects: your own team, a third-party agency, or an attorney. The right answer depends on the account's age, the balance, and how much the relationship is still worth.

• Internal collections. Keep it in-house while the relationship matters and your team has capacity, usually for accounts under 90 days past due. You keep full control and pay no contingency fee, but it costs your team's time.
• Third-party agency. Hand off when the account is badly aged, unresponsive, or the balance justifies the fee. Agencies take a contingency cut, commonly 15 to 50 percent of what they recover, higher for older and smaller debts. You trade margin for recovery on accounts you would otherwise write off.
• Attorney or legal action. Reserve for large balances where the customer can pay but will not, and the paper trail is solid. It is the slowest and most expensive path, so the balance has to justify it.

A clean internal escalation often resolves the account before it ever needs an agency. Many of these cases overlap with how you deal with non-paying customers and how you handle delinquent accounts by risk tier, so the escalation rule should sit on top of that tiered playbook, not replace it.

Handoff checklist and documentation

Most escalations stall because the receiving party (internal manager, agency, or attorney) does not have the full picture. A complete handoff is the difference between recovery and a dead file. Run this checklist before any account leaves your desk.

Collections handoff checklist

Account and invoice
[ ] Customer legal name, contact name, phone, and email
[ ] Every open invoice number, date, amount, and current balance
[ ] Late fees and interest applied to date
[ ] Original credit terms agreed (and signed contract if available)

Communication history
[ ] Every reminder sent, with dates and the version sent
[ ] Notes from every call, with dates and who spoke
[ ] Any promise-to-pay dates the customer gave and missed
[ ] Any dispute raised, what it covered, and how it was resolved

Decision record
[ ] The trigger that fired and the date it fired
[ ] Confirmation no active dispute or payment plan is open
[ ] Who approved the escalation and when
[ ] The recovery path chosen (internal, agency, or legal) and why

When to use this: complete it the moment an account trips your escalation trigger, before you contact an agency or send a final demand. A documented trail also protects you if the dispute later goes legal, since it shows you followed a consistent, good-faith process.

Costs and trade-offs of each path

Escalation is never free, and the cheapest-looking path is not always the right one. Three costs trade against each other.

The relationship. Sending a customer to an agency usually ends the commercial relationship. For an account you still want to sell to, an internal escalation that stays firm but professional protects future revenue.

The fee. An agency's contingency cut means you net less than the face value, sometimes far less on old debt. On a small balance, the fee plus your own time can exceed what you recover, which is why a minimum balance belongs in your trigger.

The time. Legal action recovers the most on a winnable case but ties up months and attorney fees. The longer a debt ages before you escalate, the lower the odds of recovery, so the cost of waiting is real too. Weigh all three against the balance before you choose the path.

How Rex automates escalation decisions

The reason escalation is inconsistent is that it depends on a person noticing the right account at the right moment, across a full ledger, while doing everything else. That is exactly the work that slips.

Rex is an AI accounts receivable agent that applies your escalation rules to every account automatically. It watches each invoice against your triggers (days past due, reminders exhausted, no active hold, balance over the minimum) and acts the instant an account qualifies, instead of waiting for someone to spot it. It assembles the full handoff package as it goes, so the documentation is ready the moment escalation fires. When an account needs a human decision, like whether a strategic customer should go to an agency, Rex escalates it to a person with the complete history attached. The consistent rules run continuously, so escalation timing no longer depends on who happened to be looking.

See how Rex runs escalation by the same rules on every account, every day.