BSS/OSS Academy
πŸ’°
Section 5.8

Dunning & Collections

Payment lifecycle, the dunning escalation ladder, credit management, debt aging, write-offs, and SLM integration for service actions.

The Payment Lifecycle

Once an invoice is generated, the payment lifecycle begins. For most postpaid customers, payment is collected automatically via direct debit or credit card. But a significant percentage of payments fail β€” declined cards, insufficient funds, expired payment methods, disputed charges. Dunning is the systematic process of pursuing overdue payments through escalating actions. Collections is the end-stage process for accounts that dunning cannot recover.

Dunning & Collections
Dunning is the automated process of notifying customers of overdue payments and escalating through defined actions (reminders, payment retries, service restrictions, suspension, and ultimately disconnection). Collections is the downstream process for debt that dunning cannot recover β€” involving debt aging, write-off decisions, and handoff to external collection agencies. Together, they manage the gap between billed revenue and collected revenue.

The Dunning Escalation Ladder

Dunning follows a defined escalation path. Each step increases pressure while giving the customer opportunity to pay. The timing and severity of each step are configurable per customer segment, payment history, and account value.

Typical Dunning Escalation

1
Payment Retry
Payment Gateway

Automatic retry of the failed payment method after 2-3 days. Many failures are transient (temporary insufficient funds, bank processing delay). Retry recovers 30-50% of initial failures with no customer impact.

2
Friendly Reminder
CRM / Notification Engine

SMS or email notification that payment failed, with a link to update payment method or pay manually. Sent 5-7 days after initial failure. Tone is informational, not threatening.

3
Formal Notice
Billing / Dunning Engine

Written notice (email/letter) stating the overdue amount, due date, and consequences of non-payment. Typically sent at 14-21 days overdue. May include a late payment fee.

4
Service Restriction
SOM / Network Policy (PCRF/PCF)

Outbound services restricted (e.g., international calls barred, data throttled) while maintaining inbound connectivity. The customer can still receive calls and access their account to make payment. Triggered at 30-45 days overdue.

5
Suspension
SLM / SOM / Network

Full service suspension β€” the customer cannot use the service but the subscription remains active. The account can be reactivated upon payment. Typically 45-60 days overdue.

6
Disconnection & Collections
SLM / Billing / Collections Agency

Service permanently disconnected, subscription terminated. Outstanding debt moves to collections β€” either internal recovery or handoff to external collection agency. Number may be quarantined. Typically 90+ days overdue.

Credit Management and Write-Offs

Dunning and collections intersect with credit management β€” the function that determines how much credit risk to extend to each customer. Credit limits, deposit requirements, and spending caps are set based on credit scoring at onboarding and adjusted based on payment behaviour. The goal is to minimise bad debt while not over-restricting good customers.

  • Credit scoring β€” At onboarding, customers are scored (via credit bureau data or internal models) to set initial credit limits and deposit requirements. Low-score customers may be offered prepaid only.
  • Dynamic credit adjustment β€” Payment history drives credit limit changes. Consistently on-time customers get higher limits; late payers get reduced limits or tighter dunning timelines.
  • Debt aging β€” Outstanding debt is categorised by age (30, 60, 90, 120+ days). Older debt has a lower probability of recovery. Provisioning for bad debt is based on aging distribution.
  • Write-off β€” Debt deemed unrecoverable is written off β€” removed from accounts receivable and recognised as a loss. Regulatory and accounting rules govern write-off timing and treatment.
Dunning-SLM Integration Is Critical
Service restriction and suspension are dunning actions that require real-time integration with SLM and the network. If the dunning engine triggers suspension but SLM is not updated, the customer loses service but the subscription still shows active β€” billing continues, and the debt grows. Conversely, if the customer pays but the reactivation signal does not reach the network, they remain suspended despite being current. Dunning must be tightly integrated with SLM and service orchestration.
TM Forum Alignment
Dunning and collections map to eTOM 1.1.1.7 (Billing & Collections Management), specifically 1.1.1.7.4 (Manage Collections) and 1.1.1.7.5 (Manage Debt Recovery). TMF676 (Payment Management API) handles payment operations. TMF666 (Account Management API) manages account status changes driven by dunning actions. Credit management aligns with 1.1.1.3 (Customer QoS/SLA Management) for spending limits and 1.1.1.7.3 (Manage Account Balance) for credit exposure.

Key Takeaways

  • Dunning follows a 6-step escalation: retry β†’ reminder β†’ formal notice β†’ restriction β†’ suspension β†’ disconnection
  • Each step requires tighter integration with SLM and network systems β€” service actions must be synchronised with billing status
  • Credit management sets the risk boundary: credit scoring, dynamic limits, and deposit requirements control exposure to bad debt
  • Dunning effectiveness directly impacts cash flow β€” the gap between billed revenue and collected revenue is managed here