Configuring your action-ladder thresholds
The dunning ladder's stages and their DPD trigger points are not fixed by Ustawi — they are yours to configure. Action-ladder configuration is where you decide how many days late warrants an SMS versus a call, a field visit, a formal notice, or legal action, and you can set that differently per product and per branch.
What you can configure
- The DPD threshold that triggers each rung — for example, whether an SMS fires at 1 day or 3 days past due.
- Which stages apply — a low-risk product may not need the full ladder, while a riskier one might escalate sooner.
- The scope — thresholds can differ per product and per branch, so a check-off product and an unsecured micro loan need not be chased on the same clock.
Why configure per product or branch
Different products carry different risk and different borrower expectations. A salary-deducted check-off loan behaves differently from an unsecured field loan, and a branch in one region may face different collection realities from another. Configuring thresholds at that granularity means the ladder reflects your actual credit policy rather than a one-size default.
Once configured, the thresholds apply automatically and identically to every loan in scope. Configuration is deliberately a policy setting, not a per-loan lever an officer adjusts case by case — that is what keeps collections consistent and auditable.
After you change a threshold
Changing a threshold changes which action is due for loans currently in arrears under that product or branch. Review the change against your delinquency reporting so you understand how it shifts the volume of SMS, calls, visits and notices your teams will be actioning.