Sales Follow-Up
WhatsApp Payment Reminder Messages: Before Due Date, Overdue and After Payment
A useful reminder makes the invoice easy to identify and the next step clear. It also stops when the account no longer needs a reminder.
A customer receives a payment reminder ten minutes after paying. Another gets the same message while waiting for a corrected invoice. Neither problem is solved by making the wording more polite. The reminder needs the right information behind it.
A payment reminder message on WhatsApp should identify the ordinary business invoice, explain the action and give the customer a way to flag an issue. The examples below are for your own routine customer invoices, not debt collection services or regulated financial products.
Check the invoice before writing the message
Confirm the invoice reference, amount, currency, due date and current status. Check whether a payment is pending reconciliation, whether the customer raised a dispute and whether another colleague already agreed a revised date.
Use an authorized, trustworthy payment destination. Do not ask customers to send card details, passwords or payment codes in chat. A reminder should make the legitimate process easier, not create a new security risk.
Before the due date
Hello [name], a quick reminder that invoice [reference] for [amount and currency] is due on [date]. You can review the invoice and payment options at [approved link]. Please let us know if any invoice detail needs correcting.
Send a pre-due reminder only when it is useful for your agreed process. A customer with an established payment schedule may not need repeated messages. Replace all placeholders and check the resulting text before using it.
When an ordinary invoice is overdue
Hello [name], our records show invoice [reference], due on [date], is still open. Could you confirm the expected payment date, or let us know if there is an issue with the invoice? If you have already paid, we’ll check the status before sending another reminder.
Keep the wording factual and proportionate. Do not add invented penalties, threats or artificial deadlines. If the account needs a formal collections or legal process, this generic sales workflow is not a substitute for the appropriate professional process.
When the customer says they have paid
Thanks for letting us know. We’ll check invoice [reference] with our accounts team and update you once the payment is reconciled. We have noted your reply so the team can review it before any further reminder.
Only say reminders are paused if your process actually pauses them. A customer’s message is a reason to investigate; it is not automatically proof that funds have settled. Keep “reported paid,” “pending reconciliation” and “confirmed paid” distinct.
After payment is confirmed
Thank you, [name]. Payment for invoice [reference] has been confirmed. Your receipt is available at [approved link]. Please let us know if you need help with the next step.
Do not claim confirmation before checking the authoritative payment record. Avoid turning a simple receipt into an unrelated promotional message.
Build stop conditions into the workflow
| Event | Action to define |
|---|---|
| Payment confirmed | Stop the invoice reminder sequence. |
| Payment reported but not matched | Send to accounts review before further reminders. |
| Invoice disputed or corrected | Pause the old sequence and assign an owner. |
| Revised date agreed | Update the schedule and retain the agreement. |
| Recipient asks to stop WhatsApp messages | Respect the request and use an appropriate agreed route. |
Check Meta’s policy, including restrictions on debt collection. These drafts are not approved templates. For Platform messages outside the service window, review the template requirements.
Connect reminders to the right business state
Before automating, establish which system owns invoice status and how the team confirms changes. Do not assume a CRM conversation can independently verify a payment. Discuss reminder triggers and stop conditions with SHVYA, using fictional invoices to map the process before connecting real customer activity.
