Overview
Use dunning policies, dunning cases, communication requests, scheduled retry state, escalation status, and canonical dunning events.
Problem
Overdue balances need repeatable follow-up and escalation instead of ad hoc reminders.
Solution
Represent collections as policy-driven dunning cases and advance them through the manifest-owned dunning worker.
How it works
Create or associate the dunning case with its billing context, apply the configured dunning policy, let the scheduled worker evaluate due actions, advance stages or recovery state, and retain communication requests and finance events.
Who is this for
Collections Manager
Finance Operations
Expected outcomes
- Consistent overdue-account follow-up
- Durable recovery, escalation, and communication state
Key metrics
Security impact
- Dunning policies/cases, balance context, retry dates, stage, communication requests, recovery/escalation state, and finance events · PII: yes where billing, customer, payment, bank, invoice, or external reference data identifies a person or organization
Compliance
- Workspace permissions, trusted execution, resource authorization, Core secrets, finance audit, and app-scoped grants.
Availability & next steps
Team
Business
Enterprise