Chasing payment after an invoice ages means negotiating. The change that works is moving the first conversation before the due date, when the money still exists.
The standard collection process is: invoice goes out, due date passes, someone starts calling.
By the time you call, the retailer has already spent that money on their next purchase. You are no longer collecting — you are negotiating for a place in a queue of people they owe.
The fix is not to chase harder. It is to move the first conversation to before the due date, when the cash still exists and the decision has not yet been made.
| When | Purpose | Tone |
|---|---|---|
| 3 days before due | Heads-up, so cash gets set aside | Informational |
| On the due date | The actual ask, with a payment link | Direct |
| 5 days after | Escalation, naming a real consequence | Firm, still factual |
Three touches around a due date is the ceiling. Beyond that, automation is the wrong instrument — a fourth unanswered message means the account needs a phone call or a visit.
What the first message looks like:
Invoice INV-2291 for ₹18,400 is due on 12 August. Pay now: [link]
Note what is missing: no "gentle reminder", no apology, no "hope this finds you well". Softening language makes the message read as optional, and optional messages get ignored.
Set the dates with the Credit Days Calculator so nothing falls due on a Sunday, when collection realistically slips anyway.
The third touch should state something specific that you will actually do:
Pick one you are willing to enforce every time. The failure mode is announcing a consequence, not applying it, and then wondering why reminders stopped working — retailers compare notes, and one unenforced threat devalues the whole sequence.
Most distributors extend credit by feel and discover the exposure later.
A workable rule, set per retailer in advance:
The point of setting these in advance is that enforcement stops being a personal decision at the counter. "The system will not release it" is a far easier conversation than "I have decided not to trust you".
Worked example, to re-run with your own numbers.
Suppose you carry ₹12,00,000 in receivables and your working capital costs 15% a year.
That is the visible part. The larger cost is the capital itself — ₹12,00,000 sitting in receivables is stock you cannot buy and schemes you cannot fund. Pull average collection in by six days and roughly ₹19,700 of capital frees up across the year.
Put your own figures into the Working Capital Calculator to see whether your current ratio supports the credit you are extending at all.
Not every account deserves the same attention. Once your receivables list is longer than about forty accounts, sort it by exposure × days late and work the top of the list.
The accounts that matter are large and slow. Small and slow is an irritation; large and fast is fine. Large and slow is where a bad debt comes from, and it is usually visible months in advance in the payment pattern.
The three-touch schedule is rules over data you already have — invoice date, amount, due date, payment status. It needs no AI and no new systems beyond a way to send the messages. The mechanics are in three WhatsApp workflows that move money.
What should stay human: the conversation when the schedule fails, the decision to extend a limit, and the judgement about whether a struggling retailer is a temporary problem or a permanent one.
Automating the routine touches is what makes room for those conversations to happen properly, instead of your time going on the first reminder to forty people.
Most collection problems are decisions made months earlier, at the point of granting credit rather than chasing it.
Three things worth establishing before a new retailer gets terms:
Start smaller than they ask. A limit that grows with demonstrated payment behaviour is easier to manage than one you have to claw back. Nobody resents earning more credit; everyone resents losing it.
Write down the terms. Not a contract — a message stating the limit, the period, and what happens if it is exceeded. The value is that the conversation happened once, in calm conditions, and can be referred back to.
Check how they pay others. Your salesman on that beat usually knows. That informal signal is more predictive than anything on paper for a shop with no formal credit history.
Defaults are rarely sudden. They are usually visible for months in a pattern nobody was watching.
Signals worth flagging, in rough order of seriousness:
The first is the most useful because it is the earliest and the easiest to measure — it is just invoice date to payment date, which your billing system already has.
At some point automation runs out and someone has to have a difficult conversation. Three things make it go better.
Go in person, not by phone. For a genuinely stuck account, presence changes the dynamic more than any message.
Ask what happened before proposing anything. Most stuck accounts have a specific cause — a family expense, a landlord, a competitor's credit. The cause determines whether this is a payment plan or a write-off.
Offer a structure, not an ultimatum. A schedule they can actually meet recovers more than a demand they cannot. Partial recovery from a shop that keeps trading beats full recovery from one that shuts.
Not every rupee is collectable, and treating every account as recoverable is its own cost.
At some point the effort of chasing exceeds the expected recovery — the salesman's time, the management attention, the goodwill on the rest of the beat. Deciding that threshold in advance, as a policy rather than in the moment, keeps collections from consuming attention the growth tactics in seven growth tactics for FMCG distributors need.
The questions distributors ask about collections.
Make it bookkeeping rather than confrontation. A message stating the invoice number, amount and agreed due date, sent on a predictable schedule, does not feel personal — and when it is visibly automated, nobody feels singled out. The relationship damage comes from irregular, escalating, personal chasing, not from consistent reminders.
Only if you will actually do it. An announced consequence that is never applied teaches every retailer that the whole sequence can be ignored, and it spreads — retailers talk. Better to set a consequence you are willing to enforce, such as the next order shipping against payment, and apply it consistently.
The financing cost of the delay plus the risk of never collecting. If working capital costs you 15% a year, an extra 15 days on ₹50,000 is roughly ₹300 — small per invoice, meaningful across a book, and the real damage is the capital you could not deploy elsewhere.
The FlowKartAI team builds WhatsApp-native ordering for Indian B2B distributors and the kirana stores they serve. We write about distribution economics, GST compliance, and the practical side of putting AI in front of retailers who have never opened an app.
FlowKartAI parses natural language WhatsApp messages into ERP-ready orders in seconds.
मुफ़्त डेमो आज़माएं