Account Debt Monitor
The Account Debt Monitor (ADM) creates a collection process when an account violates your collection criteria. The collection process has one or more collection event(s). The number and type of events is defined on the collection process's template.
This process has an optional input parameter for CIS Division. It can be used if you implementation requires processing of data by CIS Division. You will need to create a copy of this process’s batch control for each CIS Division.
Monitoring account debt is usually done based on a schedule triggered by system events such as a bill or canceled payment. If too much time has gone by since the last debt review, the account can be selected for debt monitoring as well. ADM has an optional input parameter Include Minimum Days Review. When set, accounts that have gone too long since their last review are selected along with those scheduled to be reviewed. The minimum days between review is defined on the customer class
A separate background process (ADM2) only selects accounts based on the minimum days. This process can be used when the option to include minimum days on ADM has not been set.
ADM2 does not have an option to be run by CIS Division.
In the above diagram, the account debt monitor creates a collection process (with 3 events) on 1-Dec-99. Notice that the events all exist in the Pending state. The events will exist in this state until their trigger date is on or before the current date.
Refer to How Does The Account Debt Monitor Work for more information.