The Getting Paid Playbook: turn an overdue invoice into cash without torching the account

Almost nobody loses money because a client refused to pay. They lose it because an invoice sat in an inbox that belonged to the wrong person, for eleven weeks, while the only human who cared about it sent three apologetic emails and then gave up.

Unpaid invoices are rarely a conflict. They are an operations failure wearing the costume of a conflict — which is why they feel awful to chase and why most people chase them badly. You send a soft nudge, get nothing, wait longer than you should, then send a harder one that reads as aggressive because it arrived out of nowhere after a month of silence.

This playbook replaces that with a ladder: a fixed sequence of contacts, on fixed days, with escalating specificity and one pre-written script per rung. You do not decide how to feel about it each time. The ladder decides. That is the entire trick.

Part 1 — The mental model: three reasons an invoice goes unpaid

Before you chase, classify. The right move is completely different in each case, and 90% of bad collections behaviour comes from applying the wrong one.

• Friction (roughly 60% of late invoices). The invoice is missing a PO number, went to a person who left, has the wrong entity name, or landed outside the accounts-payable system. Nobody is refusing. The document simply cannot travel. Fix: resend correctly, to the right address, in the right format. This should take one email.
• Forgetting (roughly 30%). It is in the system, approved, and sitting in a payment run that nobody has triggered. Fix: a specific, dated, named ask — not a reminder. “Can you confirm it’s in Friday’s run?” beats “just following up.”
• Funding (roughly 10%). They do not have the cash, or they are stretching you deliberately to fund working capital. Fix: a payment plan with a written schedule, and a change to how you work going forward. This is the only category where the relationship is genuinely at stake, and it is the one people wrongly assume they are in from day one.

Assume friction until proven otherwise. It is both the most likely explanation and the one that keeps your tone right.

Part 2 — Before you send: the seven fields that decide whether you get paid on time

Collections starts before the invoice exists. Run this checklist once, fix your template, and a meaningful share of your late payments disappear permanently.

1. The exact legal entity name of the payer, matching their records. “Acme Inc.” instead of “Acme Holdings LLC” can bounce an invoice silently.
2. A PO or reference number if they use one. In a mid-sized company, an invoice without a PO is not late — it is invisible.
3. A named human plus the AP inbox. The inbox pays it; the human unsticks it. You need both, and you should have collected both before you started the work.
4. Terms stated as a date, not a duration. “Due 30 September 2026” is enforceable in a person’s calendar. “Net 30” is a trivia question about when the clock started.
5. The deliverable named in their language. The approver often is not the person you worked with. “Q3 brand refresh — phase 2” gets approved; “Professional services” gets queried.
6. One payment method that requires zero setup. Every extra step — a portal login, a new vendor form, a bank verification call — adds days.
7. A late-fee clause you actually reference. Typically 1.5% monthly, or statutory interest where it applies. It is not there to earn you money. It is there so that the phrase “interest starts accruing Monday” is a fact rather than a threat.

Part 3 — The ladder

Fixed days, fixed channels, escalating specificity. Day 0 is the due date.

• Day −3 — The pre-note. Email to AP, copy the human. One line, friendly, no ask. This is the highest-leverage message in the ladder and almost nobody sends it.
• Day +1 — The confirmation. Not a chase. You are confirming receipt and asking one closed question: is it in the system, and which payment run is it in?
• Day +7 — The named ask. Reply on the same thread, add the human to the To line. Ask for a date.
• Day +14 — The switch to voice. Phone the AP contact. Email has failed twice; keep using it and you are just building an archive of your own patience.
• Day +21 — The escalation. New thread, your commercial contact’s manager or the budget owner. Neutral subject line. State facts, state the consequence, request a date.
• Day +30 — The statement of account. Formal document, all outstanding invoices, interest applied, a deadline seven days out, and a named next step if the deadline passes.
• Day +45 — The stop. Pause work in writing. Not as punishment — as the natural consequence of an unfunded account. This is the rung that actually moves money, and the one most people never reach.
• Day +60 to +75 — Hand it off. Formal demand letter, collections agency, or small-claims filing depending on size. Past 90 days, recovery rates fall off a cliff, so the decision itself has a deadline.

Part 4 — The scripts

Day −3, the pre-note. “Hi — invoice 1084 ($12,400, Q3 brand refresh phase 2) is due Thursday 3 September. Nothing needed if it’s already scheduled; just flagging so it doesn’t sit. Happy to resend in any format your system prefers.”

Day +7, the named ask. “Hi Priya — invoice 1084 was due last Thursday and I haven’t seen it clear. Two quick questions: is it approved in your system, and which payment run is it scheduled for? If something’s blocking it on my end — PO number, entity name, format — tell me and I’ll fix it today.”

Day +21, the escalation. Subject: “Invoice 1084 — 21 days overdue, need a payment date.” Body: “Hi Marcus — bringing you in because I’ve not been able to get a payment date through AP. Invoice 1084, $12,400, delivered 5 August, approved by Priya on 11 August, due 3 September. Nothing is disputed as far as I know. I need a specific date this week. Under our terms interest begins accruing on 24 September, and I’d much rather not apply it. Who should I be talking to?”

Day +45, the stop. “Hi Marcus — invoice 1084 is now 45 days overdue with no payment date. I’m pausing work on the phase 3 scope from Monday until the account is current. I’m not looking to make this difficult and I’ll restart the day it clears — but I can’t keep funding delivery against an unpaid balance. If there’s a cash-flow issue, say so and I’ll write you a payment schedule today.”

Notice what none of these do: apologise for asking, use the word “just”, or explain your own financial situation. Your cash-flow position is not their decision input, and offering it invites them to weigh their convenience against your hardship. State the fact, the consequence, and the date.

Part 5 — The escalation call, in twelve minutes

1. Minute 0–1. Name the purpose. “I’m calling about invoice 1084, 21 days overdue. I want to leave this call with a date.”
2. Minute 1–4. Ask, then be quiet. “What’s holding it?” Then stop talking. Silence here is worth more than any argument; people fill it with the actual reason.
3. Minute 4–8. Classify. Friction, forgetting, or funding — from Part 1. Solve the one you are in, not the one you feared.
4. Minute 8–10. Get the commitment. A date and an amount. “Soon” is not a commitment. “Next payment run” is not a commitment until you know the run date.
5. Minute 10–12. Close the loop in writing. “I’ll send a note confirming: $12,400 on 26 September.” Send it within the hour. An unwritten promise is a feeling; a written one is a record.

Part 6 — Six failure modes

• Chasing the wrong person. Your day-to-day contact usually cannot pay you and often cannot even see the invoice. Find AP by day 7 or you are just venting at a friend.
• The apology spiral. “So sorry to bother you again” teaches the reader that your request is an imposition they may decline. Delete it.
• Stacking silent reminders. Four identical “just following up” emails are not four contacts. They are one contact, ignored four times. Every rung must change channel, recipient, or specificity.
• Threatening what you will not do. If you mention interest, apply it. If you say you will pause work, pause it. One empty threat converts the whole ladder into noise, permanently.
• Letting it pass 90 days. Recovery rates collapse with age, and so does your leverage: the longer you keep delivering unpaid, the more clearly you have signalled that payment is optional.
• Fixing the invoice, not the terms. A client who paid at day 60 once will pay at day 60 forever unless something structural changes — a deposit, a milestone schedule, or a price that accounts for the float. If you are carrying them, the cost of that money belongs in the price.

Part 7 — Make it not your job

The goal is a system that runs whether or not you feel like running it.

1. Build the ladder into your calendar or invoicing tool the day you issue the invoice. All eight rungs, scheduled, with the script pasted into each. If a payment lands, you cancel the rest. Manual chasing means you chase the clients you like least, last.
2. Keep a one-line aging list — invoice, amount, day count, next rung, next date. Ten seconds a day. Anything older than 30 days gets read out loud, to yourself, once a week.
3. Change the terms for repeat offenders. 50% deposit, milestone billing, or work paused automatically at day 45. Announce it as policy, not as punishment: “From October, all projects start with a 50% deposit.”
4. Price the float. If a client reliably pays at day 60 on net-30 terms, they are borrowing from you for a month at 0%. Either fix the behaviour or charge for the loan.

Worked example

A three-person design studio, $12,400 invoice, net 30, client is a 400-person software company. Day −3 pre-note goes to AP and the account lead: no reply, which is normal. Day +1 confirmation reveals the real problem — the invoice was never entered, because it was addressed to the trading name rather than the registered entity. Corrected and resubmitted the same day; the clock effectively restarts, but the studio now has a documented submission date. Day +7 named ask gets a reply: approved, scheduled for the 26th. It clears on the 26th.

Total elapsed effort: eleven minutes across three emails. Under the old approach — three soft nudges to the account lead, who could not see the AP system at all — that invoice sits until someone eventually notices in November. The money was never in dispute. Only the routing was.

Your first week

• Monday. List every outstanding invoice with its day count. Do not analyse; just get the number in front of you.
• Tuesday. For anything past due, identify the correct AP address and approver name. This alone will explain several mysteries.
• Wednesday. Send the correct rung for each — not the rung you feel like sending, the one the day count dictates.
• Thursday. Fix the invoice template against the seven fields in Part 2.
• Friday. Schedule the full ladder for every open invoice, and decide which two clients get new terms next quarter.

Getting paid is not a negotiation and it is not a favour. It is a routing problem with a deadline attached — and routing problems reward whoever is most specific.