Getting Paid Without Chasing
Invoicing at the moment of delivered value, reminder schedules that never sound annoyed, and the calm escalation policy — collection as machinery instead of evenings.
There's a job in your practice nobody applied for: the evening accounts-receivable clerk. It's staffed by you, at 9pm, drafting your third differently-worded gentle reminder to a client you like, about an invoice from six weeks ago, trying to find the phrasing that gets you paid without making the relationship weird. The job pays nothing, corrodes goodwill in both directions, and exists for exactly one reason: collection is running on personality instead of machinery.
The pillar named the pattern; this guide installs the fix for its longest tail.
The collection system, entire: invoice at the moment value lands (not month-end); terms short and stated from the start; reminders on a fixed schedule that fires automatically and never sounds annoyed (because machines aren't); and one calm escalation policy applied identically to everyone. The design goal isn't toughness — it's that no step ever again depends on you feeling brave on a weeknight.
Invoice timing: the gratitude window
Every day between delivering the value and requesting the money weakens the request. Invoice on delivery — the report sent, the filing accepted, the treatment done — and payment rides the gratitude; invoice at month-end and you're a creditor interrupting someone's budgeting. The month-end batch habit is pure assembly gap: when work completed is an event your systems can see, invoice sent becomes its automatic consequence, and the timing problem stops existing.
Terms: short, stated, boring
Net-30 is a convention from paper-cheque logistics, not a law of professional courtesy. For most practice work, due on receipt or net-7, stated on the quote, restated on the invoice — with the payment link making compliance a tap — is entirely normal now. Terms surprise no one when they've never been hidden; the awkwardness practices fear lives almost entirely in changing terms mid-relationship, which is why the right moment to fix yours is with the next new client, in writing, from the first quote.
Reminders: the machine's best role
The reminder sequence is where automation earns its keep morally as well as practically: a machine sends the day-before-due note, the day-after note, the day-seven note — identical for every client, unfailingly polite, incapable of passive aggression, and sent, which the 9pm version often isn't. Three well-written templates, scheduled once: "a reminder this falls due tomorrow — link below"; "this seems to have slipped past its date — the link again, and do say if anything's wrong"; "following up once more — if there's an issue with the invoice or the work, reply and we'll sort it." Notice the third message's move: it opens the door to the real reasons invoices stall — a question, a quibble, a cash crunch — which surface far sooner when raising them doesn't require confessing to a person.
Escalation: one policy, zero decisions
Past the sequence, the failure mode is case-by-case agonising — every overdue account becomes a fresh emotional negotiation with yourself. Replace it with policy, decided once on a calm day: at X days, a personal call (often revealing a fixable problem, not a deadbeat); at Y, work pauses with notice; at Z, the formal route your jurisdiction provides. Applied identically to everyone, the policy protects relationships — clients experience consistency, not judgment — and the record does the tracking, so nothing depends on how assertive you feel.
Questions practices actually ask
Automatic reminders feel cold for a relationship business. Colder than the alternative? The resentment of unpaid work leaks into relationships far more corrosively than a polite scheduled note ever could. Warmth belongs in the work and the check-ins; consistency belongs in collections.
A long-standing client always pays, just slowly. Rock the boat? Slow-but-certain still costs float and every-month attention. The gentle path: the payment link and new terms with the next engagement, framed as a practice-wide update — which it is. Grandfathered chaos helps no one, including them.
When is it worth writing an invoice off? When the collection cost — formal steps, your hours, the relationship rubble — exceeds the number. The policy should name that threshold too; below it, close the account, decline the next engagement, and reclaim the headspace.
What number tells me this is fixed? Days-to-paid, tracked: the gap between invoice sent and money received, averaged monthly. When the machinery lands, that number drops in the first cycle — and the evening clerk job quietly disappears.
Part of Get Paid — the money chain.