Payment Reminder Automation: Get Paid Without Awkward Calls

Most owners hate chasing money. You don't want to annoy a good customer, your accountant feels awkward calling a senior buyer, and the salesperson says "abhi naya order chal raha hai, mat poochho". So the dues sit. Payment reminder automation takes the awkwardness out: polite, accurate reminders go out on a fixed schedule, on WhatsApp and email, and a person only steps in when the system says so. This guide covers the policy, the schedule, the wording and the setup.

Why dues pile up

In most businesses I look at, late payment is rarely a customer refusing to pay. It's usually one of these:

• The invoice never reached the right person in the buyer's accounts team.
• Nobody reminded them, so it wasn't on this week's payment list.
• Payment terms were never written down, so "30 days" became "whenever".
• Your own team was unsure whose job it was to follow up.

Every one of these is a system problem. That's good news, because systems can be fixed without changing customers.

Step 1: Write a one-page credit policy

Automation needs rules to follow. Before you set up any reminder, write down:

• Standard terms: for example, 30 days from delivery, or advance for new customers.
• Credit limits: how much each customer type can owe at one time.
• Who approves exceptions: a longer period or a higher limit needs a named person's approval.
• The hold rule: at what point new orders stop until old dues are cleared, for example 30 days past the due date.
• Who owns collections: accounts sends reminders; the salesperson calls at a set stage; the owner steps in only at the last stage.

Print the terms on every quotation, order confirmation and invoice. Customers can't object to a rule they agreed to at the start. The credit policy template gives you a ready format.

Step 2: Know your legal position

If you're a registered micro or small enterprise, the law is on your side. Under the MSMED Act, buyers must pay within the agreed period, and that period can't exceed 45 days from acceptance. Late payments attract interest, and buyers have tax reasons to pay you on time. I explain these rules, and how to use them politely, in the Udyam benefits most owners never use. Put your Udyam number on your invoices so the buyer's accounts team knows.

Confirm how the rules apply to your contracts with your CA before quoting them to a customer.

Step 3: Set the reminder schedule

A good schedule starts before the due date and gets firmer slowly. Here is a common pattern for 30-day terms:

Illustration: adjust the days to your own terms and customer types.

These are the same stages as the free payment reminder tool, which shows how much cash is stuck by age and writes a polite message for each stage. The day-15 call is the one step where a person speaks instead of a message going out.

The schedule stops the moment payment is recorded. That is the single most important rule. A reminder after a customer has paid is the fastest way to lose their goodwill.

Step 4: Get the wording right

Good reminders are short, specific and polite. Each one should include the invoice number, the amount, the due date and an easy way to pay. A few examples:

Before due: "Namaste Sharma ji, a quick reminder that invoice 1245 for ₹86,400 is due on Friday. Payment details are below. Thank you for your continued business."

7 days overdue: "Hello Sharma ji, invoice 1245 for ₹86,400 was due last Friday and is still open in our records. Could you share the expected payment date? If it's already paid, please send the reference and we'll update it."

30 days overdue: "Dear Sharma ji, invoice 1245 for ₹86,400 is now 30 days past due. As per our agreed terms, we'll need to clear this before dispatching new orders. Please let us know the payment date by Monday."

Illustration: names and amounts are made up.

The full set, including the version that refers to the 45-day rule, is in the payment reminder templates.

Step 5: Set up the automation

You need three pieces working together:

1. A source of truth for dues. Your accounting software or ERP, with invoices, due dates and payments recorded daily. If payments are entered once a week, reminders will be wrong.
2. A messaging channel. The official WhatsApp Business API for WhatsApp reminders, using approved utility templates, plus email. Customers must have agreed to receive messages from you; add that line to your order form.
3. A connection between them. A daily sync that picks up open invoices, checks the schedule and sends the right message. It also creates a call task for the salesperson at day 15 and alerts the owner at day 30.

Add a payment link or UPI details to every reminder. The easier it is to pay, the faster people pay. My post on setting up WhatsApp Business automation explains templates, opt-in and the API in more detail.

Step 6: Review receivables weekly

Automation handles the routine. Every Monday, accounts shares a one-page view of receivables by age: current, 1–30 days, 31–45 days, over 45 days. The owner looks only at the top ten amounts over 45 days and the customers on hold. Five minutes, not an afternoon.

Put "receivables over 45 days" on your main dashboard as well; it belongs next to sales and cash in the one-page dashboard.

To see how much cash is tied up in dues, and what collecting faster would free, try the free debtor days and working capital calculator.

Handling the replies

Reminders start conversations. Decide in advance how your team handles the common answers, so nobody improvises.

• "Kal kar denge" or a promised date. Record the promised date against the invoice and pause reminders until the day after. If the date passes, the next reminder mentions it: "You'd mentioned payment by the 12th."
• "Already paid." Ask for the payment reference, check it the same day and reply. If it was paid, apologise and fix the entry. If not, say so politely with the details.
• A dispute about quality, quantity or rate. Stop the reminders for that invoice and pass it to the salesperson with a deadline to resolve. Reminders on a disputed invoice only make the customer angrier.
• Part payment. Record it, send a thank-you with the balance amount, and let the schedule continue on the balance.
• No reply at all. That's what the day-15 call is for. Silence usually means the invoice is stuck with someone, not that the customer won't pay.

Once dues come in on time, plan your cash a few weeks ahead rather than month by month. The 13-week cash plan shows what's coming in, what's going out and when you'll be short.

A worked example

Illustration only: hypothetical numbers to show the arithmetic, not a client result.

Say you bill ₹60 lakh a month on 30-day terms, but customers pay in 60 days on average. That means about ₹1.2 crore is outstanding at any time. If reminders bring the average down to 45 days, outstanding drops to about ₹90 lakh. That's ₹30 lakh released into your bank, once, without a single new sale. At 12% interest on working capital, that's roughly ₹3.6 lakh a year you no longer pay the bank.

Mistakes to avoid

• Reminders with wrong amounts. Reconcile before you automate. One wrong reminder to a big customer will make the team switch the system off.
• No hand-over to a person. Automation opens the conversation. At some point a human must call.
• Exceptions agreed on the phone and never recorded. If the owner gives a customer 60 days, record it, or the system will chase them at day 31.
• Threatening language too early. Firm is fine. Threats in the first reminder spoil relationships that were never at risk.
• Selling more to customers who don't pay. Use the hold rule. Sales that don't turn into cash are not sales.

Where this fits

Collections are part of the Measure & Run layer of the Self-Running Business System: money in the bank is the number every other number serves. If you'd like reminders built into your accounting and WhatsApp setup, see the Conversion System (WhatsApp automation and follow-up), or take the free Automation Scorecard to see where else cash is leaking.