Payment Follow-Up Scripts: What to Say at Each Stage, Written Out

Three mistakes account for most of it. Starting late, so your invoice misses the payment run and waits for the next one. Chasing the wrong person, usually the buyer rather than whoever processes payments. And escalating tone instead of substance, which turns a routine administrative matter into a relationship problem that is then harder to resolve than the payment itself.

The scripts below assume the opposite: start early, address the right person, stay neutral, and add facts rather than feeling as time passes. Adapt the wording to how you normally speak, since a message that sounds nothing like you reads as a template and is treated as one.

The scripts here are for conversations. For the written reminders that go out between them, there are 25 payment reminder messages for WhatsApp, SMS and email, from three days before the due date to the final notice.

Timing: three to five working days before due. Channel: whichever the customer normally uses. Purpose: catch missing paperwork and approvals before they cause a delay.

Script: Hello Rakesh, a quick note that invoice 2043 for 84,500 rupees falls due on Friday 12 May. Do let me know if you need another copy, a signed delivery challan, or if it should go to a different person for approval. Happy to send whatever helps.

Timing: the due date itself. Channel: email with the invoice attached, plus a short message if that is how you usually communicate.

Script: Hello Rakesh, invoice 2043 for 84,500 rupees is due today. Could you confirm whether it has been scheduled for payment, or let me know if anything is holding it up? Payment details are on the invoice, and I am attaching a copy for convenience.

Note the question. A statement invites no reply. A direct question about scheduling gets an answer more often than any amount of polite restatement, and the answer, even a bad one, tells you what to do next.

Timing: seven days past due. Channel: a call first, then written confirmation of whatever was said.

Call opening: Hello Rakesh, calling about invoice 2043 for 84,500 rupees, which was due on the twelfth. I wanted to check whether it is in this payment run, and if not, who I should speak to in accounts.

Written follow-up the same day: Hello Rakesh, thank you for speaking just now. To confirm, you expect payment of invoice 2043 by 25 May and will check with Priya in accounts if there is any delay. I will follow up on the twenty sixth if I have not heard.

Timing: around twenty one days past due, or immediately after a promise is broken. Channel: email to the accounts contact with your buying contact copied.

Script: Hello Priya, invoice 2043 for 84,500 rupees, dated 12 April with thirty day terms, is now twenty one days overdue. Rakesh confirmed on 21 May that payment was expected by the twenty fifth. Could you let me know the payment date, or whether there is a query on the invoice that I can resolve today? If a part payment is easier at this stage, please tell me and I will work with that.

Around thirty days, the person who owns the customer relationship should call, and the purpose is different from the accounts sequence. It is to find out what is actually happening. Is there a dispute nobody raised? Is the customer in difficulty? Is a specific approver away? The framing should be genuinely helpful: I wanted to check whether there is a problem at your end that we can work around, because we would rather sort it out with you than keep sending notices.

This call resolves a substantial share of aged invoices, partly because it surfaces disputes that were never communicated and partly because a human conversation with someone the customer knows is harder to ignore than a message.

Script: Hello Priya, invoice 2043 for 84,500 rupees, due 12 May, remains unpaid at forty five days. We wrote on 12, 19 and 26 May and spoke with Rakesh on 21 May, when payment was promised for 25 May. Unless payment is received or a written payment plan is agreed by 5 June, we will place the account on hold for further supply and refer the matter to our recovery process. If there is a difficulty we can accommodate, please call me today and I will do what I can.

Two rules for this message. Everything in it must be true, including the consequence, because a threatened step you never take is worse than no threat. And the offer to help must be genuine and remain open, since a payment plan that recovers the money over three months is a far better outcome than a recovery process that recovers less, later, and ends the relationship.

Consistency more than wording. The same steps at the same intervals for every customer, every time, so that your business becomes the one that follows up predictably. Record every contact and every promise against the customer, so whoever picks up the file next knows exactly what has been said. And keep the tone level throughout, because the sequence is doing the escalation and the language does not need to.

Operationally this needs the invoice, the conversation history and the follow-up tasks in one place. HelloGrowthCRM keeps payment reminders as sequences on the customer record with WhatsApp, calls and email logged together and GST invoicing attached, which mostly matters because the third reminder is far more effective when the person sending it can see exactly what was promised on the call two weeks ago.

Related reading on payments and customer operations: CRM in India, WhatsApp CRM, CRM for small business, sales automation, features, and built-in dialer.