Quote → invoice → payment follow-up → expenses → cash flow. All business names and figures below are synthetic examples.
Make the payment request match the record
A useful follow-up says which invoice is unpaid, how much remains, when payment was agreed and what response would help. Check the bank or payment record first. An invoice total and an outstanding balance are different if a customer has paid part of the amount.
Worked example: follow up on INV-DEMO-001
Continue the fictional ₹18,000 workshop project. Assume the full amount remains unpaid, the agreed due date is 6 November 2026, and the customer has agreed to communicate by WhatsApp. These are example terms, not statutory payment deadlines.
Example message: “Hi Example Client, invoice INV-DEMO-001 for ₹18,000 is due on 6 November 2026. Our records show ₹18,000 outstanding. Please confirm the expected payment date, or let us know if any document is missing. Thank you.”
Use the payment-reminder template, replace the brackets and verify the recipient before sending. Copy message only copies text. Neither the template nor the WhatsApp Link Maker sends a message automatically.
Keep a small follow-up log
| Record | Synthetic example |
|---|---|
| Invoice / amount due | INV-DEMO-001 / ₹18,000 |
| Agreed due date | 6 November 2026 |
| Customer response | Payment expected 10 November 2026 |
| Next review | Check receipt on 10 November before another reminder |
If ₹5,000 arrives, reconcile it to this invoice and update outstanding to ₹13,000 before the next message. Do not resend a reminder for the original ₹18,000. This balance calculation is a record-keeping example; the Invoice Generator does not maintain a receivables ledger.
Let the response change your cash forecast
A confirmed later date belongs in the cash forecast. If the customer disputes scope, separate the dispute from the undisputed amount and retain the agreed documents. If no date is confirmed, flag the receipt as uncertain rather than treating it as cash already available.
The due-date planner can save your chosen review date locally. It does not send alerts or add a calendar event. Use your own calendar if you need a notification.
Before you copy or send
- Match the invoice number and customer to your records.
- Deduct receipts already matched to this invoice.
- State a specific agreed date and verified payment route.
- Check the recipient and communication permission.
- Record the response and update expected cash timing.
Late charges, statutory remedies and contract changes are outside this operational example. Obtain appropriate advice before adding them to a demand.
Printable working checklist
- ☐ Match customer and invoice reference
- ☐ Reconcile payments and calculate the actual outstanding amount
- ☐ Use the agreed due date, not an assumed statutory deadline
- ☐ Verify payment instructions and recipient
- ☐ Personalise the reminder and send only through an agreed channel
- ☐ Record the promised date or dispute and update the cash forecast
This guide describes the current tools and an original synthetic workflow. It is not tax or legal advice. Editorial policy · Report a correction