Do not rank overdue accounts by balance alone. First group them by the next actionable step and deadline, then fill today’s call capacity using owner-set priorities. Keep account totals separate from bill promises and measure original promises against matched receipts.
A large balance may not be today’s first call
A customer who promised payment today, a disputed bill and a customer waiting for a missing copy need different actions. Check the balance and evidence before choosing the call.
| Account | Checked balance | Evidence and deadline | Next actionable step |
|---|---|---|---|
| Example Textiles | ₹80,000 | ₹30,000 promised today | Call to confirm the original promise |
| Sample Garments | ₹1,40,000 | ₹20,000 bill disputed | Resolve the named dispute with documents |
| Demo Stores | ₹45,000 | Due date missing | Check invoice terms before requesting payment |
| Trial Fashions | ₹25,000 | Customer requested a bill copy | Send and confirm receipt |
All names and amounts are fictional. This order is not a universal ranking.
Choose five calls from forty accounts
- Remove rows whose balance or customer identity has not been checked.
- Group the rest by next action: promise due, missing document, dispute, no response or due-date check.
- Within each group, sort by the real deadline or original promise date.
- Apply the owner’s stated priority for today, such as protecting a dispatch decision or following promises due now.
- Fill the available call slots and assign each one. Send document-only tasks to the right queue rather than consuming call capacity by habit.
- Have the owner review conflicts; do not hide policy inside an unexplained score.
Separate account totals from bill promises
An account summary can show the checked total. Each promise should still name the amount, original date and bill allocation where known. If a customer promises ₹30,000 against a ₹80,000 account, preserve the other ₹50,000 separately. Several bills may have different disputes and dates.
For a partial dispute, record the disputed amount and reason without assuming the remainder is accepted. Resolve the evidence before turning the undisputed arithmetic into a payment admission.
Measure promises kept without rewarding reschedules
| Original promise | Receipt matched by cut-off | Revised promise | Outcome |
|---|---|---|---|
| ₹30,000 on 22 Sep | ₹20,000 on 22 Sep | ₹10,000 on 24 Sep | ₹20,000 kept; ₹10,000 rescheduled |
A revised promise is useful planning information. It is not success against the original promise. Keep missing due dates, no-response cases and unresolved disputes visible as separate states.
Use the payment reminder samples after choosing the right recipient and action. This guide selects work; it does not duplicate message templates.
Questions you might ask
How do I choose which overdue customers to call first?
Group checked accounts by actionable next step and deadline, apply the owner’s stated priority, then fill the available call capacity. Avoid an unexplained universal score.
How should I record a promise that covers only part of an account?
Keep the account total separate. Record the promised amount, original date and bill allocation where known, while preserving the remaining balance and disputes.
Does a rescheduled promise count as kept?
No. Match receipts to the original amount and cut-off, then record any revised promise separately.