In this guide 6 sections
Tally records what a retailer owes. It does not record when the shopkeeper promised to pay or when your van next reaches that town. Those facts live in WhatsApp and memory. A retailer wise ageing with promise dates and collection rounds puts them next to the balance.
What a ledger balance leaves out
A Tally balance is accurate. It says a shop in Almora owes a given amount across several bills. It cannot say whether the shopkeeper has said he will pay on Friday. That gap matters.
That promise usually arrives as a voice note or a short message to the salesman. It sits in a phone. When the salesman is on leave, the promise leaves with him. Nobody else knows. The accountant, the owner and the new salesman all see the same Tally figure and make three different guesses about it.
The accountant then chases the full balance, including bills the shop never disputed, and the shopkeeper feels pestered. The owner sees a large number and no story behind it. Decisions on credit holds, discounts and the next consignment are then taken on instinct instead of facts about each shop.
- Promised payment date and amount
- Reason for delay, such as a damaged carton or a short delivery
- Who made the promise and when
- Next visit date for that route
- Cheque or transfer details once paid
Why hill routes make this worse
A shop in Pithoragarh is not reached by a quick trip. The van goes on a set round, perhaps once a fortnight, through Nainital, Almora and beyond. Roads close in the rains and a visit slips by a week.
Retailers know this. They time their payments to the van. They hold cash for the day the salesman arrives. A balance that ignores the route calendar looks overdue when it is simply waiting for the visit.
Collection also depends on small local cycles. A tourist season, a market day or a wedding month changes when a shop has cash. A weekly ageing from the ledger cannot see any of that, because it knows only invoice dates and receipt dates. It never sees the season, the road or the shopkeeper’s plans.
Build the retailer wise ageing
Start from the Tally outstanding, listed by retailer and bill. Group the bills into age bands based on invoice date. Add the credit limit and the terms agreed with that shop. Note which bills are against a damaged or short delivery, since those are disputes rather than dues and should not be chased in the same call.
Next to each retailer, add three columns that Tally does not hold: promised date, promised amount and next route visit. These are filled by the salesman or the dispatcher after each contact.
The sheet now answers a different question. It no longer asks who owes us at all. It asks who has promised, who has gone quiet and who we meet before the promise falls due.
Plan the collection round with the ageing
Before each van leaves Haldwani, print or open the list for the route. The driver and salesman see which shops owe, which promised and which bills are in dispute. They carry the right statements.
After the round, the salesman records receipts, new promises and any stock return. The accountant posts the receipt in Tally as before. The ageing and the ledger now move together.
Overdue becomes a smaller, sharper list. Calls drop. On Monday the owner can sit with the sheet for twenty minutes and see which route, salesman and handful of shops hold the real risk. Shops that promised and kept the promise need no call. Shops that missed twice go to the owner.
- Print the route list a day before departure
- Carry statements for the oldest bills first
- Record receipts and promises at the shop, not at night
- Escalate after two missed promises
Keep Tally and add a layer beside it
You do not have to replace Tally. It stays the book of record for accounts and tax. A small layer beside it takes the bill list by export or integration and holds the promises and routes.
Check your first month by comparing the total in the ageing with the Tally outstanding. They must match to the rupee. Differences point to unposted receipts or credit notes. Fix them first. A sheet that disagrees with the books will be ignored by the accountant within a week, however well it is designed.
This week, pick ten retailers on one hill route and write down their promise dates from the WhatsApp chats. That list is your first ageing.
Retailer ageing and promise sheet
Rows run one per retailer. Columns: retailer, town, route, credit limit, outstanding from Tally, bills in age bands, promised date, promised amount, dispute note, next van visit, last contact and owner. A footer row checks the total against the Tally outstanding.
Open a blank worksheet to printQuestions owners ask
Why does Tally not show promised payment dates?
Tally is an accounting book. It records vouchers and balances. A promise is a conversation, not a voucher, so it has no natural place in the ledger.
Do we need to stop using Tally?
No. Keep Tally for accounts and returns. Add a separate layer for promises and routes, fed by the bill list from Tally.
Who should record the promise?
The salesman or dispatcher who spoke to the retailer, at the time of the call or visit. Recording it at night from memory loses detail.
How do we know the ageing is correct?
Total it and compare with the Tally outstanding for the same date. A mismatch usually means a receipt or credit note has not been posted.