Use case · Collection & Dunning
Stage 1 — Overdue Notice
First reminder sent after payment due date is missed.
CollectionDunning SchedulerNotification GW
SystemPrimary actor
Collection & DunningCategory
3Modules involved
At a glance
TriggerPayment due date missed
OutcomeMost customers pay after a gentle reminder
Main flow
The usual path from start to finish.
- 1
Identify overdue accounts - 2
Assign collection scenario - 3
- 4
- 5
Wait for payment or next stage
Exceptions & alternate flows
Payment arrivesStop dunning
Systems & modules involved
CollectionDunning SchedulerNotification GW
Business rules
- Scenario by customer risk and value
- Pause for disputes and promises to pay
- Protect vulnerable customers
KPIs to watch
- Days sales outstanding
- Recovery rate per stage
- Bad-debt ratio
Standards & references
TMF678Customer Bill Management
This page describes generic industry practice and public standards. It is not based on, and does not describe, any particular vendor's product or operator's systems.