A practical overdue debt review

Key takeaways

• Segment the list by days overdue and amount while keeping the customer’s previous commitments visible.
• Give every overdue item a concrete next state: contacted, new date agreed, or balance disputed.
• A large, old balance with no recent contact usually needs earlier attention. When the customer has promised a near payment date, time the next contact around that commitment.

pDaftar capabilities

• pDaftar supports tracking customer debts and transaction history.
• pDaftar provides reports and statistics based on recorded business activity.

Workflow inputs

Segment the list by days overdue and amount while keeping the customer’s previous commitments visible.

Include debt date, due date, balance, last contact, and promised payment in the review list. When one customer has several debts, reviewing each separately reduces reminders that quote the wrong amount.

Operating sequence

Give every overdue item a concrete next state: contacted, new date agreed, or balance disputed.

Do not leave a contact outcome only as free text: select a new date, partial-payment plan, or disputed state. The next staff member should continue without guessing what the customer was told.

• Filter overdue records by due date and confirmed outstanding balance.
• Prioritize contact by amount, days overdue, and the previous payment promise.
• Log the outcome, agreement, and next contact date for every account.

Choosing the first account to contact

A large, old balance with no recent contact usually needs earlier attention. When the customer has promised a near payment date, time the next contact around that commitment.

Limitations

• An overdue list does not establish ability to pay. If a dispute, returned item, or recording error appears, correct the basis of the balance before pursuing collection.

Sources

1. pDaftar features — pDaftar
2. pDaftar pricing — pDaftar
3. How long should I keep records? — Internal Revenue Service