How an owner decides which overdue customer to call personally
An illustrative account of only the accounts where the relationship, not the reminder, is the issue.
This story shows a practical response to only the accounts where the relationship, not the reminder, is the issue.
Who this is
This composite follows the owner in a industrial supplies trading business of about 20 people. Their work crosses several desks, with handwritten registers and messages used alongside digital records. The role is answerable for the state of the daily collections and promise register and for passing exceptions to the owner or sales manager. Calls most often come from people who need a yes, no or reliable date before they can continue.
The task here is how an owner decides which overdue customer to call personally. The responsibility is limited: this person can check and record facts within their role, then seek approval when money, safety, customer promises or rules require it.
The moment
The daily collections and promise register is open, but nobody can identify the next owner. The issue now being examined is only the accounts where the relationship, not the reminder, is the issue. The owner has to decide what can move now and what must wait. The information comes from Tally customer ledger, invoice copies, credit notes and receipt confirmations. A quick answer is tempting, especially when the next team is already standing nearby, but an unverified status can become a commitment.
The first action is to put the current source on the desk or screen. It may be a job card, a supplier message or a bank entry. The owner compares the source with the last approved record. A difference is recorded openly. The role then asks who can verify it, rather than inventing a missing value.
This particular moment turns on three small decisions: rank relationship-sensitive overdue accounts, confirm undisputed amount, and pick a factual personal call. Their order matters. A later approval does not repair a wrong quantity or an unsafe condition discovered after work has started.
What they check, in order
- Confirm the case. Rank relationship-sensitive overdue accounts. Look at Tally customer ledger, invoice copies, credit notes and receipt confirmations. Write the reference next to the question instead of keeping it only in chat.
- Check the original evidence. Verify invoice due date, undisputed amount, customer contact, promised date and receipt. If two records disagree, keep both and record what needs reconciliation.
- Look for downstream effects. Confirm undisputed amount. Tell the affected team which job, payment, batch or person is waiting. Avoid giving a firm time without evidence.
- Apply the authority boundary. The owner or sales manager reviews exceptions involving an altered commitment or a decision outside the normal limit. A verbal approval should be documented.
- Keep the next action visible. Pick a factual personal call. Show the person, deadline and the record that will prove the task is done.
- Verify closure. Find invoice reference and dated customer reply. If it is missing, keep the item open and make it the first check at the next review.
The checks are intentionally small. They should fit into the person's existing shift instead of creating another report. More detail is useful only when someone will read it and act on it.
What they wish they knew earlier
They would prefer to have invoice due date, undisputed amount, customer contact, promised date and receipt before the request becomes urgent. A short update from the previous team can prevent repeated calls. The hard part is deciding whether the update is current and authorised.
The owner or sales manager should receive exceptions with evidence, rather than a stack of routine entries. Separate disputed balances from undisputed ones. Do not threaten a customer over an unreconciled ledger.
The one sheet that helps
A small daily collections and promise register brings the question, the evidence and the next person together. The rows below are examples only. They are neither a real company's records nor measured results.
| Reference | Amount (example) | What needs checking | Owner | Next review |
|---|---|---|---|---|
| S106-01 | ₹42,000 | Rank relationship-sensitive overdue accounts | owner | Next morning |
| S106-02 | ₹8,600 | confirm undisputed amount | owner or sales manager | Before payment |
Update the sheet when something changes, even if that change is a revised promise or a failed check. Do not erase the original instruction. For a reusable version, open Receivables ageing sheet.
If you do this job
- Tomorrow, select one real case that matches Escalating overdue accounts. Keep the original source visible while you make the check.
- Record who owns the next move. If the evidence is missing, mark the case open and state the exact document or physical check needed.
- Before hand-over, tell the next role which part is confirmed and which part still needs a decision. Use Afraid to remind big customers to investigate any repeated gap.
Read next
- Afraid to remind big customers
- Escalating overdue accounts
- Receivables ageing sheet