In this article, you will learn about the validation feature for the dunning configuration. This enhancement ensures consistent and robust dunning rules, preventing scenarios that could negatively impact your turnover.
Topics covered:
- Why we introduced validation for dunning configuration
- Validation of rules for direct debit
- Specific validations for dunning levels
- Additional validations for dunning level 0
Fast lane
- Open the dunning configuration settings.
- Ensure one entry type is valid: either “dunning run” or “immediate”.
- Check that all chargeback reasons are covered by rules (exceptions apply for certain rule types).
- Validate that the range of dunning levels (0 to endless) is covered without overlaps or unreachable rules.
- For collection stop rules, verify proper target dunning levels and transitions.
- Review additional requirements for dunning level 0:
- Ensure every level has a rule targeting it.
- Cover the range of failed payments (1 to endless) without conflicting rules.
Why we introduced validation for dunning configuration
The dunning process is a critical part of managing overdue payments. However, due to its complexity, misconfigurations could previously occur, leading to:
- Members being stuck in the same dunning level.
- Missed transitions to debt collection.
- Financial losses due to inefficient dunning workflows.
To address these challenges, we introduced validations to ensure that all dunning configurations are consistent and comprehensive.
Validation of rules for direct debit
Our new validation system supports the configuration of dunning rules for direct debit payments. It ensures that at least one of the following entry types is valid:
- Dunning run
- Immediate
With this update, the system automatically checks configurations for inconsistencies at each dunning level, helping you create robust and effective rules.
Specific validations for dunning levels
To provide clarity and reduce errors, our validation feature now performs the following checks on all dunning levels:
-
Complete coverage of chargeback reasons
The system ensures that all chargeback reasons are addressed by rules.
Exception: A rule of type “delay of payment” can cover the dunning level but applies only to “dunning run” and not to “immediate.” -
Full range of dunning levels covered (0 to endless)
Validations ensure all dunning levels from 0 to “endless” are included, without overlap or unreachable rules.
Example:
- A rule with “greater or equal 0” should not precede another with “greater or equal 1” if their parameters are identical. This ensures all rules remain reachable. -
Collection stop rules
When a rule sets a collection stop but does not target the “debt collection” level, the target dunning level must include a rule with “delay of payment.” This ensures that members can continue progressing through the dunning levels.
Additional validations for dunning level 0
For the initial dunning level, our validations include additional checks to ensure accuracy:
-
Rules targeting every level
Any dunning level in the active configuration without a “delay of payment” rule must include another rule targeting it. -
Coverage of failed payment range (1 to endless)
The system checks that all rules account for the range of failed payments from 1 to “endless,” avoiding overlaps or unreachable conditions.
Example: A rule with “greater or equal 0” should not come before another with “greater or equal 1” if conditions are identical.
Note: We do a validation here that points to misleading configurations to make sure, that your dunning processes are working as expected. But we do not block or avoid the usage of misconfigured rules.
These new validations ensure that your dunning configuration operates seamlessly and prevents members from getting stuck or bypassing important transitions. With these updates, your dunning processes are now more efficient and reliable.