Collections
The DPD-driven dunning ladder, promise-to-pay capture, and sync-exception recovery.
How the DPD dunning ladder works
SMS → call → visit → notice → legal, triggered by days-past-due thresholds.
Recording a promise-to-pay (PTP)
Capturing a borrower's commitment and how it affects the dunning cadence.
Configuring your action-ladder thresholds
Customizing DPD trigger points per product or branch.
Understanding sync exceptions
3 unresolved (example)What causes a field-collected payment to flag as a sync exception, and why they're the money-authority alerts in the portal.
Resolving a sync exception
3 unresolved (example)The review-and-clear workflow.
Reading a borrower's collections timeline
The combined view of DPD, contacts made, and PTPs.
Related categories
Loan applications, the approval ladder, disbursement, repayment, restructuring, and write-offs.
Login, worklist, offline cash collection, receipts, EOD reconciliation, and device trust.
PAR30/PAR90 aging, BOT 5-band classification, provisioning, and portfolio disaggregation.
Frequently asked questions
What is DPD?
Days past due — the number of days a repayment is overdue, driving the dunning ladder's next action.
What is the dunning ladder?
An escalating sequence (SMS, call, field visit, formal notice, legal) triggered by DPD thresholds.
Can I customize when each dunning step triggers?
Yes, via action-ladder configuration per product or branch.
What is a sync exception?
A field-collected payment that couldn't reconcile cleanly during offline sync and needs manual review.
Does recording a promise-to-pay pause the dunning ladder?
It can adjust the cadence, but a broken PTP resumes escalation.