A payment recovery dashboard should show a distributor the parties who owe money as of this morning, the open bills, how many days each party takes to pay, which team member owns the chase, and a daily brief that names promises due today, follow-ups due today, and overdue parties nobody has chased. The Recovery view lives inside the Collect tab, is switched on per company on request, and the brief is shared by hand through the phone's share sheet. At 8:40 an owner in Guwahati opens the card, sees one promise of ₹45,000 due today from a Barpeta chemist, and a line that three overdue parties have no recovery owner yet. Habits sits in Reports+. Bills are bill-by-bill outstanding. A promise is marked missed only after the promised date has passed and no receipt has landed in Tally for that party, with allowance for sync lag. This article walks that morning through the four tabs, the follow-up log, the Team board, and the company-wide reminder cadence.
Key Highlights
- A payment recovery dashboard for a distributor is the Recovery view inside Collect: four tabs named Parties, Bills, Habits and Team, switched on per company on request
- The daily brief card names promises due today, follow-ups due today, promises proven missed, receipts awaiting confirmation, top overdue parties, or an explicit All clear, and is shared as text through the phone's share sheet
- A promise is marked missed only after the promised date has passed and no receipt has landed in Tally for that party, with allowance for sync lag
In This Article
- What should a payment recovery dashboard show a distributor?
- The 8:40 card
- Parties, Bills, Habits, Team
- The follow-up log and a proven missed promise
- The Team board and the parties nobody has chased
- Reminder cadence as a company setting
- Frequently Asked Questions
What should a payment recovery dashboard show a distributor?
The owner already knows the book total from Outstanding receivables on mobile. At 8:40 the useful question is narrower: who owes, on which bills, how do they actually pay, who on the team owns them, and what is due from yesterday's promises before the first retailer call.
Those four tabs plus the brief are the payment recovery dashboard. Parties is receivables ageing by party, as of today, with ageing slabs the user can edit. Bills is the same money cut bill by bill. Habits is payment behaviour per customer, how many days they take to pay and the median days, and it sits in Reports+. Team is the people doing the work: Recovered, Outstanding, Speed as median days to collect, dealers worked, promises kept and missed and open, a rank, a company roll-up, and a line that names overdue parties nobody has chased.
Without those four together, the morning is a printed outstanding list and a WhatsApp thread titled "vasuli", which is still how Indian distributors manage collections in a lot of shops. The list will match Tally. It will not name who promised ₹45,000 yesterday, whether that money landed, or which of the 90-day parties has had no call, no WhatsApp, no visit.
The 8:40 card
The daily brief is a card the owner opens in the app. It names what the morning is actually about: promises due today, follow-ups due today, promises proven missed, receipts awaiting confirmation, and the top overdue parties. When none of those apply, it says All clear.
On a Tuesday in August the card for a Guwahati FMCG book might read like this. One promise due today: Barpeta Chemist, ₹45,000, logged yesterday after a call, next action today. Two follow-ups due: a Dibrugarh kirana that had no answer on Saturday, and a Tezpur grocer marked disputed on a rate difference. One promise proven missed: a Nalbari party who said Friday and whose ledger still shows no receipt. Three overdue parties with no recovery owner.
That card is the morning. The owner does not start by scrolling 280 ledgers. He starts with the six lines that can move today. If he wants the accountant or a salesman to see the same six lines, he shares the brief as text through the phone's share sheet, WhatsApp, email, anywhere the phone can send text. The share is manual. There is no automatic morning send.
The receipts-awaiting-confirmation line is the one that stops a false chase. Money may have landed last night and Tally may not have it yet. The brief names that gap instead of treating every open bill as a person who has not paid.
Parties, Bills, Habits, Team
Open Collect, open Recovery, and the four tabs are the whole dashboard.
Parties is the ageing the owner already understands, grouped by customer, as of today. The slabs are editable, so a book that runs 21-day terms is not forced into a 30-day first bucket. This is the same job a receivables ageing view on mobile does, read here as the working list rather than as a monthly print.
Bills is the same outstanding cut voucher by voucher. A party at ₹1,20,000 is three invoices, not a mood. The chemist who promised ₹45,000 yesterday promised against a named bill, and Bills is where that bill sits until a receipt allocates against it.
Habits is the behaviour behind the ageing. Two parties can both sit at 62 days and be different jobs. One always takes 60 to 70 days and then pays the full bill. The other used to pay in 25 and has stretched to 62 for the first time this year. Habits shows days-to-pay and median days per customer. It is part of Reports+. It is the tab that stops you treating a slow-and-honest retailer the same as a slipping one.
Team is covered on its own below, because the Monday conversation lives there. Each party can also carry a recovery owner, a team member, reassigned from the app when a route changes or a salesman leaves. Attribution is the same problem a salesman wise collection report has to solve: a receipt does not carry a person's name unless the party does.
Tally stays the book of record. The Recovery view reads the same parties and bills. It does not replace the ledger.
The follow-up log and a proven missed promise
Every party can carry a follow-up log. Each entry has a channel, call, WhatsApp, in person, or other, an outcome, a next-action date, and an optional promised amount and promised date. Entries are append-only. A newer promise supersedes the older one. Nobody edits Friday's "kal bhej dunga" into a different sentence on Tuesday. They add today's entry, and today's promise is the one that counts.
Outcomes stay in plain language: paid, promised, no answer, disputed. Four labels are enough to run a morning.
The Barpeta chemist example is the whole mechanic. Monday 7 PM, the owner calls, the chemist says ₹45,000 tomorrow. The log records channel call, outcome promised, promised amount ₹45,000, promised date Tuesday. Tuesday 8:40 the brief shows that promise as due today. If a receipt for that party has landed in Tally by then, the chase is over. If it has not, the owner still treats it as due, not as broken, until the date has passed.
A promise is marked missed only after the promised date has passed and no receipt has landed in Tally for that party, with allowance for sync lag. It is proven missed, not flagged the minute the clock crosses midnight. A UPI credit at 11:40 PM that reaches Tally at 8:10 AM is a payment, not a broken word. The lag is why the brief also names receipts awaiting confirmation.
The log is what makes days sales outstanding a conversation instead of a ratio. DSO moving from 58 to 64 is a company number. "Three promises missed this week, all on Ramesh's parties" is a Tuesday plan.
The Team board and the parties nobody has chased
Team is a set of cards with sort chips, not a sortable table. Each member's card carries Recovered, Outstanding, Speed as median days to collect, dealers worked, promises kept, missed and open, and a rank. There is a roll-up line for the company. There is a line that names overdue parties nobody has chased.
That last line is the one owners underrate. A book of 180 parties will always have a total overdue figure. The figure does not tell you which of those parties has had zero follow-up. The nobody-has-chased line does. On the Tuesday card it might be three names, a Nagaon retailer at 94 days, a Goalpara grocer at 71, and a Tinsukia party at 88, none of them with a recovery owner and none with a log entry this month.
The Monday conversation changes once that line exists. Without it, the meeting is collection thoda tight karo. With it, the owner says: these three have not been touched, Ramesh takes Nagaon and Goalpara, I will take Tinsukia, reassign the recovery owner in the app before you leave. Next Monday the same cards show whether Recovered moved, whether promises were kept, and whether the nobody-has-chased line shrank.
Speed is median days to collect, not a feeling that Ramesh is "good at vasuli." Two salesmen can recover ₹6 lakh in a month and have very different Speed if one collected 20-day money and the other collected 90-day money. The card puts that next to Outstanding so the recovered figure has a denominator.
The Salesman app for Tally is the field half of the same job: the rep at the counter, seeing his own parties. Recovery's Team tab is the owner's half: who recovered, who is slow, and who has not been asked.
Reminder cadence as a company setting
The dashboard is the morning. Reminders are the rest of the week, and they are a company-wide setting, not a per-party one. You do not set the chemist to every day and the grocer to every seven. You pick one cadence for the company.
There are four presets. Every day. Every 2 days. Every 3 days, which is the default. Every 7 days. Each preset has its own before-due nudge and overdue schedule. There is also a custom cadence: 1 day before due, on the due date, then every N days, with N between 1 and 90.
The Tuesday decision for that Guwahati book is usually whether the default of every 3 days is still right. A book that has slipped, DSO up, 90-plus growing, often moves to every 2 days for a month. A quiet book stays on every 3 or every 7. The setting is the same kind of once-and-done choice as scheduled payment reminders, sitting next to the option to send payment reminders automatically off Tally due dates.
WhatsApp reminders can carry a UPI payment link once payment collection is active, after KYC. They do not carry a link on every reminder by default. When collection is on, the rail is 0% MDR on UPI collections, no transaction cap, no monthly fee. Across the platform that is 100+ businesses and ₹17Cr+ collected monthly.
Reminders and statements go from the Takkada business number, shown as queued in the app, or via Send from my WhatsApp from the owner's own number. The sender question is the one sending from your own WhatsApp number exists to answer: a retailer opens a chat from a number he already has saved. A Payment reminder from Tally still starts from the invoice and the due date already in the books. The Recovery view does not replace that. It tells the owner, at 8:40, which of those reminders and which of those calls actually need a person today.
On that Tuesday the ageing report still shows ₹18 lakh overdue. The Recovery view also shows the ₹45,000 promise, the missed Nalbari date, and the three names nobody has chased. Tally keeps the bills. The owner keeps the chase.
Frequently Asked Questions
Q: What should a payment recovery dashboard show a distributor?
A: A payment recovery dashboard should show a distributor four tabs together: Parties as ageing by customer, Bills as bill-by-bill outstanding, Habits as days-to-pay and median days per customer, and Team as recovered, outstanding, speed, and overdue parties nobody has chased. It should also show a daily brief card naming promises due today, follow-ups due today, promises proven missed, receipts awaiting confirmation, and top overdue parties, or All clear.
Q: Where is the payment recovery dashboard in the app?
A: It is the Recovery view inside the Collect tab, with Parties, Bills, Habits and Team. Recovery lives in Collect, as a view, switched on per company on request.
Q: How do I share the daily recovery brief with my accountant?
A: Open the daily brief card and share it as text through the phone's share sheet, to WhatsApp, email, or anywhere the phone can send text. The share is manual. The brief is not sent out on its own.
Q: When is a promised payment marked missed?
A: A promise is marked missed only after the promised date has passed and no receipt has landed in Tally for that party, with allowance for sync lag. It is proven missed, not marked the minute the date ticks over. A newer promise in the follow-up log supersedes the older one, and entries are append-only.
Q: Can I set a different reminder cadence for each customer?
A: No. Reminder cadence is a company-wide setting. The presets are Every day, Every 2 days, Every 3 days as the default, and Every 7 days, each with its own before-due nudge and overdue schedule, plus a custom cadence of 1 day before due, on the due date, then every N days from 1 to 90.
Q: Does every WhatsApp reminder include a UPI payment link?
A: No. WhatsApp reminders can carry a UPI payment link once payment collection is active, after KYC. When collection is on, UPI collections run at 0% MDR, with no transaction cap and no monthly fee.
Takkada is a Tally-integrated receivables and auto-reconciliation app for Indian distributors, with 0% MDR UPI collection and WhatsApp dispatch. Book a free demo.