Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!


Home > Aria Crescendo Documentation > Configuration > Dunning > Dunning Best Practices

Dunning Best Practices

Table of contents
This article applies to:Aria Crescendo


Dunning can be effective for customer retention when done correctly. See the best practices below for setting up and managing dunning.

Best Practices

  • It is recommended that your dunning process be the same duration or shorter than the billing interval of the plan to which the process applies. This allows you the opportunity to collect a payment on a past due amount before a customer's next payment is due.
  • If a customer with an outstanding account balance changes the payment method from net terms to an electronic payment, Aria may not place the account into dunning. You may choose to collect the customer's outstanding balance using the customer's new payment method.

If a customer with an outstanding account balance changes the payment method from an electronic payment method to a net terms payment method, the outstanding balance will be reflected on the customer's next statement.

  • It is recommended that you have consistent dunning processes with matching numbers of steps across all of your plans that are available for selection. This ensures that your dunning processes will work effectively when customers switch plans.

For instance, if a customer is on Plan A and is on dunning Step 3 of Plan A, then switches to Plan B that has only 2 dunning steps, that plan will exit dunning and become suspended.

  • Be sure to consider the effects on customers when you change a dunning process. You may need to make any required actions on accounts manually if they are already in a dunning process that you have changed.

For instance, you may need to manually change an Master Plan Instance's status.

  • If a collection fails when a customer attempts to place an order, the account will not go into dunning. Dunning only applies to recurring charges.
Last modified



This page has no classifications.