Account Level Delinquency Process Creation

A new batch named C1-ACDLQ is introduced in this release. It is used to create a delinquency process for an account when its overdue bills do not meet the tolerance limit. This batch considers the accounts which meet the following conditions:

Collection method of the collection class to which the account belongs is set to Self-Control Delinquency
Next credit review date is either not calculated for the account or is earlier than or equal to the batch business date
Postpone credit review until date is either not defined for the account or is earlier than or equal to the batch business date
The date derived using the last credit review date + minimum credit review frequency (defined in the delinquency control) is either blank or is earlier than or equal to the batch business date

Note: The next credit review date of an account is stored in the CI_ADM_RVW_SCH table and the postpone credit review until date of an account is stored in the CI_ACCT table.

Once the list of accounts are derived, the system executes the delinquency monitor rule algorithm which is attached to the delinquency control of the respective account's collection class. If the system is not able to derive the delinquency monitor rule algorithm for an account, an appropriate error message is shown in the batch run tree. If the system is able to derive the delinquency monitor rule algorithm for an account and if the new delinquency process is successfully created for an account or if an existing delinquency process is updated for an account, this batch sets the last credit review date of the account in the CI_ACCT table to the processing date.

For more information on how the C1-DLNQMNRL algorithm (attached to the delinquency control) derives the overdue bills, see Delinquency Control.

This batch is a multi-threaded batch. The multi-threading is based on account ID and chunks for multi-threading are created based on numerical distribution of account ID. This batch contains the following parameters:

Parameter Name	Mandatory (Yes or No)	Description
Division	Yes (Conditional)	Used when you want to monitor the delinquency of the accounts which belong to a particular division. Note: This parameter is required when you specify a customer class while executing this batch.
Customer Class	No	Used when you want to monitor the delinquency of the accounts which belong to a particular customer class.
Chunk Size	Yes	Used to specify the number of accounts you want to process in each work unit. Note: By default, the value is set to 5.
Thread Pool Name	No	Used to specify the thread pool on which you want to execute the batch.

If a new delinquency process is successfully created for an account, the status of the delinquency process is set to the value (for example, Initiated) specified in the Delinquency Process Initiated Status attribute of the delinquency process preference. Note that the system considers the preference which is specified in the Delinquency Process Field Mapping option type of the DELINPROC feature configuration. For more information about the feature configuration, see DELINPROC Feature Configuration.

The system then invokes the C1-DPEVTCR algorithm which is attached to the Initiated status. The C1-DPEVTCR algorithm creates a delinquency event of each delinquency event type that is added in the delinquency process type using which the delinquency process is created. If the delinquency event trigger mode is set to Manual in the delinquency process type, the status of the delinquency event is set to Pending. However, if the delinquency event trigger mode is set to Automatic or Manual or Automatic in the delinquency process type, the status of the delinquency event is set to Pending Evaluation.

Once the delinquency events are created for the delinquency process, this algorithm does the following:

Sets the delinquency due date of the delinquency process to the latest bill due date
Derives the grace period from the delinquency process type or using an algorithm attached to the Grace Period Derivation system event depending on the grace period source which is specified in the delinquency process type

Sets the grace start date in the following manner:

Trigger Date Calculation Mode	Usage Basis	Grace Start Date Basis	Grace Start Date is set to…
Latest Bill Due Date with Grace Period	-	-	Latest Bill Due Date
Usage Basis	Delinquency Process Creation Date	-	Delinquency Process Creation Date
Usage Basis	Grace Start Date	Latest Bill Due Date	Latest Bill Due Date
Usage Basis	Grace Start Date	X Days after Latest Bill Due Date	Latest Bill Due Date + Add Days To Due Date
Usage Basis	Grace Start Date	Delinquency Process Creation Date	Delinquency Process Creation Date
Usage Basis	Latest Bill Date	-	Latest Bill Date
Usage Basis	Latest Bill Due Date	-	Latest Bill Due Date

Calculates the grace end date in the following manner:

Trigger Date Calculation Mode	Usage Basis	Grace Start Date Basis	Grace Start Date	Grace Start Date is set to…
Latest Bill Due Date with Grace Period	-	-	Latest Bill Due Date	Grace Start Date + Grace Period + Drag Days (if any, defined at the respective level (i.e. account or person)
Usage Basis	Delinquency Process Creation Date	-	Delinquency Process Creation Date	Grace Start Date + Grace Period
Usage Basis	Grace Start Date	Latest Bill Due Date	Latest Bill Due Date	Grace Start Date + Grace Period
Usage Basis	Grace Start Date	X Days after Latest Bill Due Date	Latest Bill Due Date + Add Days To Due Date	Grace Start Date + Grace Period
Usage Basis	Grace Start Date	Delinquency Process Creation Date	Delinquency Process Creation Date	Grace Start Date + Grace Period
Usage Basis	Latest Bill Date	-	Latest Bill Date	Grace Start Date + Grace Period
Usage Basis	Latest Bill Due Date	-	Latest Bill Due Date	Grace Start Date + Grace Period

Note: This algorithm does not calculate the trigger date and preview date for the events when delinquency event trigger mode is set to Manual in the delinquency process type. However, the system calculates the trigger date and preview date for the events when delinquency event trigger mode is set to Automatic or Manual or Automatic in the delinquency process type while executing the C1-DPEVL batch.

Once a delinquency process is created for an account, you can perform the following actions on the delinquency process from the user interface:

Add additional information in the form of comments or characteristics
Manually hold a delinquency process and edit the hold details (if required)
Manually release a hold on the delinquency process
Manually cancel a delinquency process
Edit the trigger date of the delinquency events in the delinquency process
Trigger or skip the delinquency events in the delinquency process
Request to reinstate the delinquency process (only applicable for the fully insured group business)
Approve, reject, or withdraw an approval record of the delinquency process

For more information about the manual actions, seeDelinquency Process Maintenance. The system also enables you to do the following:

Automatically hold a delinquency process when the certain conditions are met
Automatically release a hold on the delinquency process when the certain conditions are met
Automatically cancel a delinquency process when the certain conditions are met
Automatically resume a cancelled delinquency process when the certain conditions are met
Automatically reinstate a delinquency process when the certain conditions are met (only applicable for the fully insured group business)

To enable the automatic process for the above actions, you need to accordingly configure the delinquency process type. The system also enables you to optionally configure the approval process for various manual actions that you can perform on the delinquency event or delinquency process. For more information, see Delinquency Process Approval.

A delinquency event and process goes through various statuses in its lifecycle. The delinquency process status also accordingly changes when the policies or individual memberships billed to the account are terminated or reinstated.