Dunning Configuration

The dunning configuration defines how the system handles overdue payments: how many attempts, the interval between them, and the behavior after exhaustion.

Configuration Fields

Field	Default	Range	Description
Maximum attempts	3	1-10	Total attempts allowed
Interval between attempts (days)	[2, 5, 7]	-	Days to wait between each attempt
Grace period (days)	3	1-90	Days before suspension
Automatic retry	Yes	-	Whether attempts are triggered automatically
Suspend after attempts	Yes	-	Whether the account is suspended after exhausting attempts
Payment methods for retry	pix, bank_slip, card	-	Which methods to use for retry attempts

Configuration Hierarchy

1. Organization configuration: Each organization can customize its rules
2. Global default configuration: Used when the organization has no custom config
3. System defaults: Hardcoded values as final fallback

Timeline Example

With the default configuration (attempts: [2, 5, 7], grace period: 3 days):

Day 0: Invoice becomes due
Day 2: 1st retry attempt
Day 5: 2nd retry attempt (if 1st failed)
Day 7: 3rd retry attempt (if 2nd failed)
Day 10: Grace period ends → account suspended

Dunning Stages

The delinquent account progresses through the following stages:

Stage	Days overdue	Description
initial	1-7 days	Recent delinquency
reminder	8-15 days	Reminders sent
warning	16-30 days	Imminent suspension warning
final	30+ days	Last chance before action
suspended	After grace period	Account suspended

Management

Pause Dunning

Use "Stop Dunning" to temporarily suspend communications while keeping the invoice as past-due.

Cancel Attempts

Cancels all pending attempts for a specific invoice and clears the next retry date.

Manual Retry

The operator can trigger a manual retry at any time, regardless of the automatic schedule.