Collections Process for Indian Small Businesses: Ageing, Ownership and Escalation

A business with a serious receivables problem usually has an order acceptance problem. Orders are taken from customers with no agreed limit, terms are assumed rather than agreed, and existing overdue balances are visible to nobody at the moment the next order is accepted. By the time the invoice ages, the exposure has already been created and the only remaining tools are chasing and goodwill.

The single highest value control is therefore a check at order stage: agreed credit limit, current outstanding, and anything overdue. Where those three are on the customer record and checked automatically, exposure stops growing quietly. Where they live in someone head, it does not.

Produce it weekly, on the same day, and work it as a list rather than reading it as a report. Each bucket is a different task with a different owner and a different tone.

The disputed row deserves attention. A dispute stops the clock in the customer mind and often in yours, and disputes left unresolved are how invoices reach a hundred and twenty days. Give every dispute an owner and a resolution deadline of a few days, and record the outcome, because a pattern of disputes from one customer is either a quality problem or a delaying tactic and you need to know which.

A surprising share of delay is self inflicted. The invoice missing the customer purchase order number, so it cannot be matched. A delivery acknowledgement that was never returned. A tax split that does not match what the customer expects. An invoice emailed to a salesperson rather than to the accounts payable system. Each of those gives the customer a legitimate reason to wait, and each is entirely within your control.

Fix it at source: capture the purchase order number at order entry as a required field, deliver the invoice on the day of despatch to the correct recipient, and reconcile delivery acknowledgements weekly rather than at month end.

Define the steps, the timing and the owner for each, then follow them consistently. Reminder before due. Reminder on due date. Call at seven days. Formal email to accounts at twenty one days with the buyer copied. Relationship call at thirty days. Supply hold at the defined threshold. Final notice with a deadline. Then the decision: payment plan, settlement, or formal recovery.

The critical design point is that the last rung must be real. A business that sends final notices and never acts on them has trained its customers precisely, and the sequence loses its effect for every other customer who talks to that one.

Track days to pay per customer over time, not just current overdue amounts. A customer who consistently paid at thirty five days and is now paying at seventy is signalling something about their own cash position, often before any conversation acknowledges it. That is the moment to reduce exposure quietly: tighten the limit, ask for part payment in advance on the next order, or slow supply. Waiting until the aged bucket is large removes all of those options.

If salespeople are paid on invoiced revenue, they will bring in orders whose collectability is somebody else problem. Tying at least part of the incentive to collected revenue, or holding a portion until payment, changes the conversation at order stage in a way that no policy document achieves. It is uncomfortable to introduce and it is the single structural change most likely to reduce bad debt in a small business.

Operationally, the customer record, the outstanding balance, the reminder sequence and the conversation history need to be in one place. HelloGrowthCRM keeps GST invoicing, payment reminders and the full conversation trail on the customer record with credit limits visible at order stage, which mostly matters because the person accepting the next order can see the exposure without asking anyone.

Related reading for Indian businesses: CRM in India, best CRM for India, CRM for small business, WhatsApp CRM, features, and India pricing.