Collection Process - Main Information

The Main page contains core collection process information. Open this page using Menu > Credit & Collection > Collection Process > Search.

Fastpath:

The Description of Page section below describes the fields on this page. Refer to How To Perform Common Collection Process Functions for more instructions describing how to use this transaction.

Description of Page

Collection Process is a concatenation of summary information about this collection process. It is composed of the name of the main customer on the account, the collection status, the reason code for the collection status, the collection class control name, and the creation date of the process.

Collection Process ID is the unique system-generated identifier for this collection process.

Account ID is the system-generated account number. The name of the main customer on the account and its customer class are displayed next to the ID number.

Collection Status defines the state of the collection process. The following values may exist:

Active The system creates a collection process in the Active state. A collection process remains in this state until the last event linked to the process is complete OR the customer pays the collection amount on the service agreements linked to the process OR you want to stop the process for whatever reason.

Inactive A collection process becomes Inactive when the last event linked to the process is completed OR the customer pays the collection amount on all service agreements linked to the process OR you want to stop the process for whatever reason. The Reason field tells you how a collection process became inactive.

Fastpath:

To completely understand the significance of a collection process' status, refer to The Lifecycle Of A Collection Process And Its Events.

Reason defines how a collection process became Inactive or why a collection process is Active. The following values may exist:

Canceled by User This reason should be used when a user manually inactivates a collection process (for whatever reason).

Canceled by System This reason is populated by the system when it cancels a collection process. The system automatically cancels a collection process when sufficient credits have been posted to the process' service agreements since the process was started.

Events Pending This reason is populated by the system when a process has pending events.

Completed This reason is populated by the system when it completes the last event linked to the collection process.

Collection Class Control defines the debt class (i.e., the type of debt) associated with the collection process. This is important as it controls which service agreements can be linked to the collection process (every service agreement is associated with a specific debt class). This field is gray when there are service agreements linked to the collection process.

Note:

Multiple collection processes may be linked to an account. It's important to be aware that if an account's service agreements reference multiple debt classes, a collection process must be created for each debt class that you want to collect.

One collection process per debt class. A given debt class for an account may only have one ongoing collection process at any point in time.

Beneath Collection Class Control is displayed a message showing why the system generated the collection process. This information is only displayed for collection processes created by the Account Debt Monitor. If you have plugged in a Collection Process Additional Information algorithm on the Installation record, the results of the algorithm, if any, is displayed on a separate line.

The following line displays the minimum value payment to the collection process debt class that will cause cancellation of the collection process.

Fastpath:

For more information, refer to How Does The Account Debt Monitor Work?.

Collection Process Template defines the collection events in the process. You can override these events on the Events page.

Note:

Changing the template. If you change the template when all events are pending, the system will remove the pending events and replace them with the new template's events.

Fastpath:

For more information, refer to Setting Up Collection Process Templates.

Creation Date/Time defines the start date/time of the collection process. This is important as it affects the trigger dates of the process' collection events. This field becomes protected after the collection process exists on the database. If you need to change the trigger date on the events you can navigate to the Events tab and change the dates manually. Alternatively, you can perform the following "trick":

  • Change the Collection Process Template to something (anything). Doing this causes the Create Date/Time to become unprotected.
  • Specify the date of the first collection event in the newly unprotected Create Date/Time.
  • Change the Collection Process Template back to the desired value. When you change the template, the system removes the events and creates new ones using the Create Date/Time.

The collection process cancellation logic will cancel a collection process when its account's debt no longer exceeds a given amount (you define this threshold amount when you set up the system). Rather than compare an account's total debt to the threshold amount, the cancellation logic compares the account's debt that is older than X days to the threshold amount. X is the date specified in Collection Amount Base Date. You can have the system calculate this date for you by entering the age of the arrears in the field embedded in Calculate Date Using _​_​_​ Days In Arrears.

Fastpath:

For more information, refer to How Are Collection Processes (and their Events) Canceled?

Enter any Comments about the collection process.

The tree at the bottom of the page shows a variety of information about the account and the collection process including:

  • The service agreements linked to the collection process.
  • The events linked to the collection process.
  • The amount of debt currently associated with the account's debt classes.
  • Whether a pay plan exists for the account, or existed at the time the collection process as created.
  • The balance for any service agreements linked to the collection process in Inactive status but that have credit balances contributing to the overall debt class arrears for the account.
  • A summary of other active collection activities (i.e., collection, severance and write-off processes) associated with the account.