Dunning

The Dunning microservice provides a way to set up tiered dunning plans to assist with collection of accounts receivable. For example, a dunning plan may include a friendly payment reminder email one day prior to due date, formal payment request email 15 days after the due date, and a change of billing account status to Suspended 30 days after the due date. Plans are applied at the billing account level, allowing companies to provide configurable dunning plans on a customer-by-customer basis if desired.

Dunning operates through a scheduled job evaluation of dunning-enabled billing accounts for past due (delinquent) payments. If these billing accounts fall within the threshold of their assigned dunning plan, the Gotransverse Action Framework will initiate an HTTP action on the billing account or an email notification based on the plan configuration. Dunning plans are configured with escalating tiers of action so that you can ensure the actions taken after delinquent payment are customized based on the particular client, lateness of the payment, or amount unpaid.

Refer to Action Framework for more information about this notification management system.

Dunning tiers are assigned priority levels to ensure that the correct action is taken based on the billing account criteria. A dunning plan may contain a tier structure similar to the following:

Dunning Plan Tier Structure
Priority Dunning Tier Days Overdue on Payment Description
0 No Dunning (Default) 1 For customers with dunning status of No Dunning, no dunning actions will be taken. Level 0 tiers cannot be edited and should be applied on billing accounts that you do not want to include in dunning.
1 Friendly reminder 10 First reminder notification sent to the customer as the oldest open invoice is past the invoice due date.
2 Important notice 30 Second reminder notification sent to the customer as the oldest open invoice is past the invoice due date.
3 Avoid suspension 40 Third and final reminder notification sent to the customer as the oldest open invoice is past the invoice due date.
4 Suspension 45 Suspension notification has been sent to the customer.
5 Collection agency 60 Notification sent to the customer that all open invoices will be transferred a Collection Agency.
6 Write off 90 Invoices of a Billing account have been written off because payments cannot be collected.

The Gotransverse Payment Plan feature can work in conjunction with existing dunning capability to help streamline the collections process. When invoice amounts for a billing account move to higher dunning tiers, causing the billing account and services to be suspended or money owed to be written off, you may lose money and customers. Reaching out to the customer and working together to formulate a Payment Plan instead increases the possibility of collecting money owed and retaining customers. Invoices moved into a Payment Plan are no longer evaluated by dunning while in the plan.

Complete the following tasks to set up dunning in Gotransverse applications:

Ensure that the Dunning Gateway processor (Dunning Essentials) is configured in the Setup application. Please contact Gotransverse Support for help with your integration of a Dunning Gateway.

  1. Define an HTTP operation and an Email Operation. Refer to Action Framework Integration with Dunning.

  2. Create Dunning Plan.

  3. Create Dunning Plan Tiers.

  4. Assign Billing Account to Dunning Plan.

  5. Create Notifications and Actions for Dunning.

  6. Create System Job for Dunning.

Also refer to the Datasheet: Collections & Dunning external link for additional information about collections and dunning.