After-Effects (Dunning Stop & Debt Collection)
After-effects are follow-up actions that a workflow performs at a point in the lifecycle of a clarification — for example, lifting a dunning stop when a…
After-Effects are follow-up actions that a workflow performs at a specific point in the life of a clarification, such as lifting a dunning stop when a clarification group closes or handing a document over to collections. They are configured on the workflow.
Configurable After-Effects
Each After-Effect has an action, a stage (when it runs), and options.
Actions
| Action | What it does |
|---|---|
| Set dunning stop | Sets a dunning stop on the clarification's document or on its customer (depending on the option), so that the customer does not receive dunning notices. It can expire after N days or last until the next restart. |
| Remove dunning stop | Lifts a dunning stop on a document or customer. |
| Hand over to collections | Hands documents over to collections: either the current document (if still open) or all open documents of the customer. |
Stage (when it runs)
After-effects can be attached to lifecycle stages, such as after close, after escalation, after response, after start, and the corresponding before variants. In practice, after close is the most important stage (for example, removing the dunning stop or handing over to collections as soon as a clarification group is closed).
Automatic vs. manual
Two switches control when an after-effect takes effect:
Run on automatic actions — the after-effect also runs when the action was performed automatically by the system (not just by a user).
Mandatory on manual actions — the after-effect always runs on manual actions (the processor cannot skip it).
When a user resolves a clarification "with after-effects," they choose which of the configured after-effects run. Automatic closures run the after-close after-effects that are marked for automatic execution.
Built-in dunning stop behavior (separate from the above)
Regardless of any configured after-effects, a clarification affects dunning by default:
Creating a clarification can place a clarification dunning stop on the document (controlled via Triggers dunning stop in the workflow).
A restart sets it again; resolving/closing removes it (if there is no longer an active clarification on the document).
Resolving with a restart date can set a manual dunning stop that expires on the restart date.
Important Settings
| Setting | Meaning |
|---|---|
| Action | Set/remove a dunning stop or hand over to collections |
| Stage | When it runs (after closing, after escalation, …) |
| Dunning stop object | Document or customer |
| Dunning stop expiration | Fixed number of days, or until the next restart |
| Collections handover target | Current document or all open documents |
| Run for automatic / Mandatory for manual | When the after-effect applies |
Troubleshooting
If a dunning stop isn't lifted when a clarification group is closed, check whether a Remove dunning stop after-effect exists for the after closing stage, or whether the built-in behavior applies (it removes the clarification dunning stop only when there is no longer an active clarification on the document). Dunning stops are a shared mechanism — another clarification or a manual stop on the same document can keep it in place.