In this guide 6 sections
Phone calls work while you have ten buyers. A Tally outstanding list shows who owes what but not who promised what. A collections module records promise dates, ageing and statements, so a call to a retailer in Lucknow or Jaipur starts from the last conversation, not from zero.
Why distant retailers are harder to chase
A shop in Karol Bagh can be visited. A retailer in Meerut or Ludhiana cannot, not every week. Distance turns collection into a phone game. Phone games favour the buyer who stops answering, because nobody can stand at the counter, wait for the cheque to be written and watch the signature go on.
Your salesman knows the history. He remembers who promised Friday and who blamed a bank holiday. When he is away on a sales trip or leaves for a competitor, that memory goes with him. The next person starts every call by asking what is pending.
The real cost is not the call. It is calling blind. A list, no notes.
Phone calls alone
Calling costs nothing and builds relationships. For a handful of retailers it is enough. The weakness is memory. Nobody can track forty retailers across Uttar Pradesh, Haryana, Punjab and Rajasthan, each with its own festival season and cash cycle.
Notes live in a diary, a WhatsApp thread or a head. Two people call the same shop in one week and hear two different stories. The shop owner notices and learns that nobody is keeping score.
Phone follow-up also depends on mood. Moods change. Easy accounts get called, difficult ones get postponed.
- Works for a small, stable list of buyers
- No shared record of promises
- Depends on one person’s memory
- Hard to hand over when staff change
The Tally outstanding list
Tally’s bills receivable report is accurate about balances. It shows each unpaid invoice, its date and the days overdue. Many wholesalers print it every Monday and work down the page.
What it does not hold is the conversation. There is no field for a promise date, no reminder when that date passes and no record of who called. Teams add a column in Excel, and now there are two files to keep in step.
Statements are manual too. You export the ledger, tidy the columns in Excel, save a PDF and attach it to a message. Each statement goes out separately. Forty parties mean forty exports.
- Reliable balances and invoice-wise ageing
- Printable party statements
- No promise date or call log
- Excel side sheets that drift from the books
A collections module
A collections module reads the same invoices but adds the missing layer. Each call is logged with a promise date and an amount. When the date passes without payment, the retailer moves to a follow-up list on its own.
Ageing buckets show where the money is stuck. Statements go out by email or WhatsApp in one run. Receipts matched against invoices clear the promise automatically, so the list stays honest.
Check that it syncs from Tally rather than asking for double entry. Test it with a receipt posted two days late, because that is when most collection lists start to lie. Otherwise the clerk gets a third place to type.
- Promise dates with reminders
- Ageing by 30, 60 and 90 day bucket
- Bulk statements and payment links
- Call history visible to everyone
Choosing for your size
Count your credit customers outside Delhi and the number of people who call them. If one person handles under twenty buyers, a Tally list and a diary may hold. Beyond that, memory fails fast.
Also ask who will read the data, and how often. A salesman needs today’s call list with the last promise beside each name. The owner wants the oldest dues and the broken promises on one Monday screen, not a printout.
Before deciding, take your top fifteen overdue retailers and write down the last promise made to each. If you cannot find five of them, you already have your answer.
Retailer collections tracker
A one-page tracker with a row per retailer. Columns: party name, city and state, oldest unpaid invoice, balance, days overdue, last call date, caller, promise date, promised amount, outcome and next action date. A header block lists the weekly review time and the escalation rule for broken promises.
Open a blank worksheet to printQuestions owners ask
Can we keep using Tally and add a collections tool?
Usually yes. The tool should read invoices and receipts from Tally and write nothing back, so your books stay the single source of truth.
How often should we call a retailer with an old due?
Call on the promise date, not on a fixed calendar. A missed promise gets a call the next working day.
Are party statements worth sending?
Yes. A statement lists every open invoice, which settles most disputes about what is unpaid before the argument starts.
What about retailers who never answer?
Log each attempt, then move to a written reminder and a visit or a call from the owner. Rules for escalation should be agreed in advance.