The get-paid playbook: how to collect a late invoice without torching the relationship

You did the work. You sent the invoice. It’s been six weeks. The client is friendly, responsive about everything except this, and every time you think about following up you feel like you’re the one being rude. Meanwhile your rent is not friendly, and it is not flexible.

Late payment isn’t usually malice. It’s friction and priority: your invoice is sitting in someone’s approval queue behind forty other things, and nobody at that company gets fired for paying you in 60 days instead of 15. The fix isn’t nerve. It’s a system that makes paying you the path of least resistance, and non-payment progressively more expensive than payment. This playbook is that system — the terms that prevent the problem, the invoice design that removes excuses, a seven-step escalation ladder with exact scripts, the worked math on when to walk, and the six mistakes that keep people unpaid.

Part 1 — Prevention: the four terms that decide everything

Ninety percent of collection problems are created before the work starts. Four clauses do the heavy lifting, and all four belong in writing — contract, statement of work, or at minimum an email the client replies “approved” to.

• A deposit. 30–50% up front for new clients, non-refundable, work starts on receipt. This is the single highest-leverage term you have. A client who won’t pay a deposit is showing you exactly how the final invoice will go — for free.
• Net terms with a real date. “Net 15” is weaker than “Payment due 15 August 2026.” Humans respond to dates, not intervals. Net 30 is the common default; net 15 is entirely normal for solo operators and worth asking for.
• A late fee. 1–1.5% per month is a typical range in commercial contracts. Its real job isn’t revenue — it’s giving your later emails something to point at that isn’t your feelings. (Enforceability varies by jurisdiction and consumer-vs-business context; check your local rules, and treat this playbook as operational advice, not legal advice.)
• A stop-work clause. “Work pauses on any invoice more than 15 days past due and resumes within two business days of payment.” This converts a moral argument into a scheduling fact, and it is the only leverage that reliably works on a client who still wants things from you.

Two more prevention moves that cost nothing. Milestone billing: split anything over a month into 2–4 invoices, so your maximum exposure is one milestone, not the whole project. Find the payer: on day one, ask “Who processes invoices, and is there a PO number or portal I should use?” The person who hired you is frequently not the person who pays you, and an invoice sent to the wrong human is an invoice that ages quietly for a month.

Part 2 — The invoice: remove every excuse

An invoice is a form that a stranger in accounts payable has to process without asking anyone a question. Every ambiguity is a delay. Yours needs: a unique invoice number; issue date and a due date written as a calendar date; the PO or reference number they gave you; a one-line description per item that matches the language in the contract; the total in bold; payment instructions with every detail needed to complete a bank transfer; and the late-fee line restated.

• Send it the day the milestone completes, not at month end. Your invoice enters the queue by arrival date; a week of your own delay is a week added to the end.
• Send it to AP and cc your contact. The contact is your ally and your escalation route; AP is the machine that actually pays.
• Offer the payment method they prefer, even if it costs you a little. A 2–3% card fee on money you receive in four days beats zero fee on money you receive in ninety.
• Attach it as a PDF and put the key facts in the email body. Some approval workflows never open attachments.

Part 3 — The ladder: seven steps, with scripts

The principle: start warm and administrative, escalate on a fixed schedule, and never skip a rung. Predictability is what makes it work — you are demonstrating that this process runs whether or not anyone feels awkward. Send every step from the same email thread so the history is visible.

Step 1 — Three days before due (the pre-nudge). The highest-return email in the whole ladder, because it catches problems before they become lateness.

• “Hi [name] — quick heads-up that invoice #1042 ($4,800) is due Friday the 15th. Anything you need from me to get it processed on time? Happy to re-send it to whoever handles AP.”

Step 2 — Day 1 past due (assume a glitch). No accusation. You’re helping.

• “Hi [name] — invoice #1042 came due yesterday and I don’t see it landed yet. Re-attaching in case it got stuck. Could you confirm it’s in the payment run?”

Step 3 — Day 7 (get a date). Stop asking for payment; start asking for a commitment you can hold them to.

• “Hi [name] — following up on #1042, now a week past due. Can you tell me the date it’s scheduled to be paid? If there’s a hold-up on your end I’d rather know now so I can plan around it.”

Step 4 — Day 14 (pick up the phone). Email is easy to defer; a live human is not. Call your contact, and if they don’t know, ask to be transferred to AP. Then — and this is the part people skip — send a summary email within the hour: “Good to talk. Confirming what we agreed: #1042 goes out in the 28th payment run.” A verbal promise you didn’t write down is not a promise.

Step 5 — Day 21 (invoke the stop-work clause). The first real consequence, delivered flatly.

• “Hi [name] — #1042 is now 21 days past due. Per our agreement, I’m pausing work on [project] until it clears, and applying the 1.5% monthly late fee from today. I’d much rather keep going — send confirmation of payment and I’ll pick straight back up. Who else should I be talking to about this?”

Step 6 — Day 30 (escalate above your contact). Loop in your contact’s manager, the finance lead, or the founder. Keep it factual and free of adjectives — no anger, just a chronology: invoice date, amount, due date, and the dates of each follow-up. Facts travel up an org chart; frustration doesn’t.

Step 7 — Day 45 (formal demand). A short letter, sent by email and post, stating the amount, the dates, the accrued fee, a payment deadline (typically 7–14 days), and what happens next: collections or a small-claims filing. Keep it under 200 words and unemotional. A surprising share of long-stalled invoices clear at this step, because it’s the moment the file moves from “annoyance” to “liability.”

Part 4 — A worked example

You invoice $6,000 on 1 June, net 15, due 16 June. Silence. Ladder runs: pre-nudge 13 June, glitch email 17 June, date request 23 June, phone call 30 June (contact says “it’s in the queue” — you write it down), stop-work 7 July, escalation to the finance lead 16 July.

On 16 July you learn the actual problem: your invoice never had a PO number, so it was never entered. Six weeks of silence caused by one missing field. You re-issue with the PO, and it’s paid on 24 July. Total cost to you: roughly two hours of chasing plus eight weeks of cash-flow damage — all preventable by one question in week one.

That is the median outcome, and it’s why the calm ladder beats the angry email. The most common cause of non-payment is not refusal. It’s a broken step in a process nobody is watching. Your job is to be the person watching it.

Part 5 — When it doesn’t clear: the actual options

• Small claims court. Designed for exactly this: no lawyer required, filing fees usually modest, limits vary widely by state or country (commonly somewhere between $5,000 and $25,000 in the US). You need your contract, the invoice, and the email trail — which is precisely what the ladder produced. Filing itself often triggers payment.
• A collections agency. Typically takes a substantial cut of what it recovers and effectively ends the relationship. Rational for genuinely dead invoices; a bad first resort.
• A lawyer’s demand letter. Often a flat fee, and sometimes the cheapest thing on this list per dollar recovered, because letterhead changes how the file is read.
• Write it off. A real option. If the amount is small and the hours to recover it are many, take the deduction, keep the lesson, and stop paying rent to the memory. Run the math honestly: at your rate, what is ten more hours of chasing worth against the odds of collecting?

Whatever you choose, choose on a deadline you set in advance — day 60, day 90 — rather than drifting. Unresolved invoices cost more in attention than in dollars. If the missing cash is threatening your own bills, deal with that separately and immediately: extend your runway and renegotiate what you owe rather than letting one client’s process failure cascade into your credit history.

Part 6 — Six failure modes

• Apologising for asking. “So sorry to bother you again…” frames payment as a favour. Bill your client, don’t petition them. Warm and factual, never apologetic.
• Waiting for a round number of weeks. Every day of silence teaches the client your invoices can wait. The pre-nudge and the day-1 email are the two cheapest emails you will ever send.
• Keeping the work going “to stay on good terms.” Delivering more unpaid work doesn’t build goodwill; it removes the only reason to pay you. The stop-work clause exists so this decision is already made.
• Only ever emailing the friendly contact. They frequently have no control over payments and every incentive to keep telling you it’s coming. Get to AP and to their manager.
• Sending the angry email. It ends relationships and rarely accelerates anything, because whoever reads it is not the person who chose not to pay you. Chronologies work; adjectives don’t.
• Re-signing the chronic late payer at the same terms. A client’s payment history is data. Repeat offenders get 50% up front and net 15, or they get a polite no — and your capacity goes to better-priced work instead.

The one-page version

• Before: deposit, dated due date, late fee, stop-work clause, and the AP contact identified in week one.
• At delivery: invoice same day, to AP, cc the contact, PO number included, PDF plus details in the body.
• Then, on schedule: −3 days pre-nudge → day 1 glitch → day 7 get a date → day 14 call and confirm in writing → day 21 stop work → day 30 escalate → day 45 formal demand.
• By day 60–90: decide — claims court, demand letter, or write-off. Decide; don’t drift.
• Always: warm, factual, scheduled. The system does the confronting so you don’t have to.