Collection policy: stages, timing and call scripts
Most late payments are not refused — they are forgotten. A collection policy is a schedule: which message goes out on which day, who makes the call, and when the conversation stops being friendly. Without it, every overdue invoice restarts the same awkward conversation.
5 documents free. PDF, photo or XML — data out as CSV, Excel or JSON.
Five stages, fixed days
Day -3: short reminder before the due date. Goal is not to nag but to confirm the invoice reached the right inbox and is queued for payment.
Day 0: due-date message. Today is the date, confirm the payment or give a new one.
Day +7: ask for the reason — missing document, approval, cash. The reason decides the next step.
Day +14 to +21: call plus a written summary with the amount, days overdue and any contractual interest.
Day +30: formal demand with a response deadline. After that it stops being a payment issue and becomes a decision for the owner.
Who does what
Account manager: stages 1-3. They know the contact and can agree a date.
Bookkeeper: the numbers — statement of account, overdue calculation, confirming the payment never arrived.
Owner: stage 4-5 — the call that asks when the money comes, and the decision to stop supplying.
If nobody owns the stage, the whole thing lands on one person at the end of the month and gets done badly.
Call scripts by week
Week one, friendly: "Hi, this is Anna from DueBuddy about invoice 218 for 2,400 — it was due Friday. Is it queued, or is something missing on our side?"
Week two, factual: "Invoice 218 is now nine days past due. I want to log the correct date in our system — can you confirm when it is scheduled?"
Week three, firm: "We still have no payment and no date. I need a specific date today, otherwise I pass this to our formal process on Friday."
Three questions that return any call to a date: When was it approved? Who releases the payment? What date can you commit to?
End every call by repeating the date back and sending it in writing the same day. A date that exists only in a phone call does not exist.
Wording that works, wording that backfires
Works: "as agreed", "to keep your account in good standing", "so we can plan delivery".
Backfires: "final warning" in the first message, legal threats you will not carry out, and any amount that is not in the contract.
Never invent interest. If the contract has no rate, say so and ask for the principal.
How we do it
DueBuddy sends reminders from your own name on your schedule — before the due date, on the date, and after. It stops when the money arrives.
No auto-dialers and no calls at 8am. The phone call is still yours to make; we just make sure the written trail exists before you pick it up.
Frequently asked
How many reminders before it becomes harassment?
Three or four written reminders over a month, each with new information, is normal business. Repeating the same message daily reads as pressure and usually delays payment.
Should the bookkeeper make collection calls?
Better not: the bookkeeper has the numbers but not the commercial leverage. Prepare the statement, let the account manager call.
What if the client asks for a payment plan?
Get it in writing with dates and amounts, confirm what happens if one instalment is missed, and keep shipping decisions separate.
Read next
DueBuddy — invoices and reminders, without the enterprise contract