Dunning management relates to the process for managing the complications of payment declines, and when a collection attempt fails, the options available to help you collect this debt.
Fusebill provides you with the ability to set up dunning rules, which control the actions taken upon a credit card collection failure. The options available to help you collect include:
- Automated retry attempts on failures
- Automated communications
- Automated changes to a customer’s status.
Automated Retry Attempt on Failures
If a collection fails, we will automatically retry to collect after a period of time. Our default collection attempts are Day 1, Day 3 and Day 5.
Retry attempts can be customized on a per-account basis and can be configured to try more frequently and for longer periods.
Automated Communications – Email Notifications
When a collection attempt fails, there are specific Email Notifications that can be configured to be sent to your customers. These email notifications are trigger-based and are sent based on the trigger condition being met. For example, the Failed Payment Notification, if configured, would be sent upon a collection attempt failing. The email notification would be sent to the primary email address for that customer. Optionally, you can configure all email notifications to send a copy internally to one or many email addresses.
Automated Changes to a Customer’s Status
The two main actions that control automated changes to a customer’s status are:
- Accounting Status* changes to Poor Standing
- Accounting statuses include Good, Poor Standing and Collections
- Poor Standing is caused by an invoice moving into an Overdue status
- Failed credit card attempts automatically move a customer into Poor Standing as their invoice is now in an Overdue status.
- Poor Standing is caused by an invoice moving into an Overdue status
- Accounting statuses include Good, Poor Standing and Collections
- Grace Period is met
- Grace Period is a default Account setting that determines the number of days a customer remains in an Activestate when they have overdue invoices and are in Poor Standing. Once the default number of days are reached, the customer is automatically moved into a Suspended state.
Dunning Process
As mentioned above, every customer in Fusebill has two levels of status that relate to the health of their account. Service status relates to the state of their account and accounting status which informs you if the customer has any overdue invoices or failed credit card payments. Both the service status and accounting status are displayed on the main customer grid, providing you easy insight into customer statuses. An added piece of data included in the grid is the Days Until Suspension, which reflects the Grace Period (number of days before the customer will be automatically moved to a Suspended state).
The example below outlines the different actions a customer may experience when you are unable to collect payment and their invoice is moved to an Overdue status. This will include attempts and notifications if configured.
Note: The example below is based on the Grace Period being set to 5 days and Collection Attempts on Day 1,3 and 5.
Trigger |
Service Status |
Accounting Status (Days Until Suspension) |
Possible options based on Dunning Management configuration |
||
Retry Collection |
Status Change |
Email Notification |
|||
Customer in Good standing |
Active |
Good |
|
|
|
Collection Fails and Invoice is now Overdue - Day 0 |
Active |
PoorStanding (5) |
|
x |
x |
Retry – Day 1 |
Active |
PoorStanding (4) |
x |
|
x |
Retry– Day 3 |
Active |
PoorStanding (2) |
x |
|
x |
Retry– Day 5 |
Suspended |
PoorStanding |
x |
x |
x |
Configuring your Dunning Management rules is normally handled during implementation but you are able to make changes as needed to your configuration.
To view or edit your dunning configuration, navigate to Settings > Collections > Dunning Management.
Other documents that will provide additional insight into Dunning Management include Status Messages and Email Messages.
Comments
0 comments
Please sign in to leave a comment.