The Collections Escalation Ladder, From Reminder to Stop Work
Collections works when the next step is already decided, and stalls when each overdue invoice becomes a fresh conversation.
Companies believe collections is a persistence problem. It is a decision problem. The reason an account sits at ninety days is almost never that nobody telephoned. It is that every time somebody did telephone, the next move after the call was undecided, so the account went back on the list and was telephoned again the following week by a person with no more authority than they had the first time.
A customer works this out quickly. If the fourth reminder looks exactly like the first, then the reminders are not a sequence, they are a mailing, and the only cost of ignoring them is deleting an email.
So the ladder below is designed backwards, from the last rung. Decide in advance what happens when a customer does not pay, write it down, agree who is allowed to authorise each step, and then work up from the bottom. Almost nobody reaches the top rung once the bottom rungs are visibly attached to it, which is the entire mechanism.
Three things have to be true before any of this works
The ladder fails on a bad foundation, and it fails silently, because the calls still happen and the account still does not pay.
The invoice was correct, and it was delivered to a place the customer processes from. An invoice sitting outside the customer’s system is not overdue, it is absent, and no amount of escalation moves it. That is a billing problem, and it is settled in the invoicing calendar rather than here.
One person owns the ledger. Not the account manager. This is the recommendation people resist and it is the one that decides the outcome, because an account manager holds the relationship and will trade the balance to protect it every single time, usually by agreeing to something nobody in finance hears about. Give the account manager a role on the ladder, at a specific rung, with a specific job. Do not give them the ledger.
The terms are actually in the contract. Escalating against terms the customer never agreed to produces a conversation about the terms rather than about the money, and you lose a fortnight to it.
The ladder
Day counts below are an example spacing, to be calibrated against your own cycle and your own contracts. The sequence and the escalation of authority are the parts to copy. What you should not do is calibrate the spacing so generously that the whole ladder finishes after the point at which the balance stops being collectable in practice.
| Rung | Trigger | Action | Who acts | Substance of what is said | Authority to move to the next rung |
|---|---|---|---|---|---|
| 0 | Invoice issued | Delivery confirmation, and for portal customers, confirmation the invoice was accepted into their system | Finance, automated where possible | Nothing. This is a check, not a contact. | Automatic |
| 1 | A few days before due date | Courtesy note confirming the invoice is scheduled for payment and asking for the expected payment date if it is not | Finance, automated | A question with a date in the answer, not a reminder | Automatic |
| 2 | First day past due | Written reminder, naming the invoice, the amount and the date it was due | Finance | Factual. No apology, no softening, no explanation of why you are writing. | Automatic |
| 3 | Roughly a week past due | Telephone call to the accounts payable contact, followed the same day by a written note of what was agreed | Finance | Ask for a payment date, and if one is given, confirm it in writing. A date in writing is the object of this rung. | Automatic |
| 4 | A promised date passes, or roughly a fortnight past due with no date given | The account manager contacts their relationship contact, not accounts payable, and finance stays on the written record | Account manager, briefed by finance | The commercial relationship has a problem and the account manager is raising it. Not a chase. | Finance lead |
| 5 | Roughly three weeks past due | Statement of account issued with a written notice that new work or new orders are held pending payment | Finance lead | The consequence is named and dated. Naming it without a date makes it advisory. | Finance lead, with the owner informed |
| 6 | The date in rung 5 passes | New work held. Nothing new starts. Work already in progress continues. | Finance lead executes, delivery leads informed | A short written notice of what has been held and what will release it | Owner |
| 7 | Roughly six weeks past due, or earlier where exposure is growing | Service suspension or work stoppage under the contract, with the notice the contract requires | Owner decides, finance executes | Whatever the contract provides for and no more | Owner, in writing |
| 8 | Suspension has run its course | The matter leaves finance | Owner, with the company’s lawyer | Out of scope for this piece and for this firm | Owner, with legal advice |
Rung 8 is a boundary rather than a step. Formal demand, collection agencies and litigation are legal decisions with consequences that outlast the balance, and they belong to the company’s own lawyer. We do not draft demand correspondence, we do not select or instruct agencies, and we do not advise on whether to sue. What finance owes rung 8 is the file: every invoice, every proof of delivery, every written exchange on the ladder, and every date. A clean file is the whole of the contribution and it is worth more than an opinion.
Rung 6 is the one to design first
Rung 6 and rung 7 are the reason the ladder works, and they are the two that companies leave blank because they are uncomfortable. Leaving them blank is not neutral. It converts every rung below into a suggestion, and customers can tell the difference between a sequence that ends somewhere and one that ends in a further email.
Design them in this order.
Decide what “held” means, concretely, before you need it. Held new work is not the same as suspended service, and conflating the two is how a company that meant to apply gentle pressure accidentally breaches its own contract. Held new work usually means no new orders accepted, no new projects scheduled, no additional users provisioned. Existing obligations continue.
Check what the contract actually permits, and on what notice. This is the step that gets skipped, and the answer is frequently that the contract permits less than the company assumed, or permits it only after a notice period nobody has been running. Find that out when nothing is overdue.
Decide who is exempt, in advance and in writing. Some customers will not be stopped, for reasons that are entirely legitimate: a contractual obligation, safety, a regulated service, a relationship the owner has decided to carry. Write the exemption down as an exemption. An undocumented exemption granted in the moment becomes a precedent, and the second customer will hear about the first.
Decide who bears the operational consequence. Stopping work on a customer costs your own delivery team an interruption and sometimes a person’s utilisation for a week. If nobody has agreed to absorb that in advance, the stop will be argued about at the moment it is supposed to happen, and it will not happen.
The dispute switch
The single most common way a ladder wastes effort is chasing a balance the customer has no intention of paying because they are disputing the underlying work, and nobody in finance knows.
Build the switch explicitly. The moment a customer raises a dispute, in any form, on any rung, the invoice leaves the collections ladder and enters a different process with a different owner and a different clock.
| Field on the dispute record | Why it is there |
|---|---|
| Date raised, and on which rung it surfaced | A dispute that first appears at rung 5 is usually not a dispute |
| The specific amount in dispute, isolated from the rest of the invoice | The undisputed balance stays on the ladder. This is the part companies forget, and it is the part that gets paid. |
| Who in delivery owns the resolution, with a date | A dispute without a named owner ages exactly like an unpaid invoice, but invisibly |
| The commercial decision when resolved: credit, rework, or hold the position | Somebody has to actually decide, and it is not finance |
| Date closed, and how | Closes the loop and puts the balance back on the ladder at the right rung |
Two rules make the switch honest. A dispute raised for the first time at a late rung, on an invoice that has been sitting quietly for weeks, is usually a delaying tactic rather than a dispute, and it should be recorded as raised late, because the pattern across a year is the finding. And the undisputed portion of an invoice never stops being collectable. Splitting the balance is a five minute job and it is the difference between collecting most of it now and none of it later.
Where the ladder feeds the numbers
The forecast side is direct. An account on rung 4 or above has no reliable payment date, and the treatment of it in the cash model is covered in the 13-week cash forecast piece, which is unambiguous about what to do with a disputed balance.
The reporting side is where most companies present collections badly. A single average collection statistic is the usual choice and it is the least useful thing available, because it is dominated by whichever two large customers happened to pay in the period and it moves for reasons that have nothing to do with how the ledger is being worked.
Report the ladder instead. The monthly reporting pack carries a short collections page with four things on it.
- The count and value of accounts on each rung, this month against last month. Movement up the ladder is the signal, not the total balance.
- Every account at rung 5 or above, named, with the amount, the date it reached that rung, and the next dated action.
- Promises made and promises kept in the month. A customer who gives a date and misses it twice is a different problem from a customer who is slow, and the ladder should treat them differently.
- The dispute log, with the age of the oldest open dispute. This is the number that predicts next quarter’s collections problem, and it is the one nobody looks at.
Point 3 is worth building even if you build nothing else. Recording the date a customer promised and the date they actually paid takes seconds at the time and produces, within a quarter, a factual basis for deciding which customers to believe. That is more valuable than any measure of the ledger in aggregate.
Running the ladder in a company with three people in finance
The version above assumes finance, a finance lead, an account manager and an owner. Most companies at this size have fewer, so the roles collapse. What must not collapse is the authority column.
The bookkeeper can perform rungs 1 through 3 entirely, and should, because they are mechanical and they benefit from being unemotional. Rung 4 needs whoever holds the relationship. Rungs 5 and 6 need someone senior enough that the customer understands the company has looked at the account, and if that is the owner, then it is the owner and the ladder is shorter. Rung 7 is always the owner.
The one arrangement to avoid is the common one, where the owner personally performs every rung. It costs the owner’s time on the cheap rungs, it removes the escalation entirely because the customer is already talking to the top of the company at day one, and it teaches everybody that unpaid invoices are the owner’s problem to solve.
What we do not do
We do not write the demand letter, choose the agency or advise on the litigation, because those are legal steps and the company’s lawyer takes them. We do not run a ladder against an invoice we cannot prove was delivered and accepted. We do not let a customer negotiate the ladder itself, which is what an unrecorded promise of leniency amounts to. And we do not escalate a disputed balance, because escalating a dispute converts a solvable delivery problem into an unsolvable commercial one, usually within a single telephone call.