Delinquency Event Eligibility Evaluation and Trigger Date Calculation

After executing the C1-ACDLQ batch, you need to execute the C1-DPEVL batch. The C1-DPEVL batch is used to monitor or check whether there is any delinquency process in the status (for example, Initiated) which is specified in the Delinquency Process Initiated Status attribute of the delinquency process preference. Note that this batch 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 Setting the DELINPROC Feature Configuration.

If there is a delinquency process in the Initiated status, the system checks whether its delinquency event trigger mode is set to Automatic or Manual or Automatic in the respective delinquency process type. If its delinquency event trigger mode is set to Manual in the respective delinquency process type, the batch does not consider the delinquency process for the delinquency event eligibility evaluation and trigger date calculation. However, if its delinquency event trigger mode is set to Automatic or Manual or Automatic in the respective delinquency process type, the system checks whether the trigger dates exist for the delinquency events. If the trigger dates exist for the delinquency events of a delinquency process, the batch does not consider the delinquency process for the delinquency event eligibility evaluation and trigger date calculation. However, if the trigger dates does not exist for the delinquency events of a delinquency process, the batch continues with the delinquency event eligibility evaluation for each delinquency event in the delinquency process.

While evaluating whether the delinquency event is eligible to be included in the delinquency process, the system checks whether the rule type is specified corresponding to the delinquency event type in the respective delinquency process type. If the rule type is specified corresponding to the delinquency event type, the system checks whether the delinquency entity type of the delinquency process is set to Account and the delinquency category is set to Individual. If so, the system derives the individual memberships which are billed to the delinquent account using an algorithm which is attached to the Memberships Derivation system event of the respective delinquency process type.

Once the individual memberships are derived for the account, the system derives the health plan for which the individual membership is availed. Once the health plan is derived for each individual membership, the system derives the rules created using the rule type (which is specified to corresponding to the delinquency event type) from the rules engine which are effective on the batch business date. The effective rules are executed in the order of their priority. If at least one individual membership satisfies the rule, the delinquency event is retained in the delinquency process. However, if none of the individual memberships satisfy the rule, the delinquency event is removed from the delinquency process.

Once the delinquency event eligibility evaluation is done for each delinquency event, the system does the following:

  • Derives the wait days or wait month and the day of the month from the delinquency process type or using an algorithm attached to the Wait Days Derivation system event depending on the wait period source which is specified in the delinquency process type

  • Calculates the trigger date for the delinquency event based on the trigger date calculation mode, usage basis, and wait period defined in the delinquency process type

  • Sets the delinquency due date of the delinquency process to the latest bill due date

If the Consider Work Days option is selected in the respective delinquency process type, the system derives the work calendar of the division to which the account belongs. The system then checks whether the calculated trigger date falls on the working (i.e. business) day. If the calculated trigger date does not fall on the working (i.e. business) day, the system will accordingly add days to the calculated trigger date to ensure that it falls on the next working day.

If the calculated trigger date of a delinquency event is later than or equal to the batch business date, the status of the delinquency event is changed from Pending Evaluation to Pending. But, if the calculated trigger date of a delinquency event is earlier than the batch business date and if the Skip Past Event option is selected corresponding to the respective delinquency event type, the system sets the status of the delinquency event to Skipped. However, if the calculated trigger date of a delinquency event is earlier than the batch business date and if the Skip Past Event option is not selected corresponding to the respective delinquency event type, the system checks whether the Move Past Dated Event to Future option is selected corresponding to the respective delinquency event type.

Note: You can select the Move Past Dated Event to Future option only when the wait period is set to Monthly Cyclic in the respective delinquency process type.

If the Move Past Dated Event to Future option is selected corresponding to the respective delinquency event type, the system moves the trigger date by adding one month until the trigger date is later than or equal to the batch business date. But, if the Move Past Dated Event to Future option is not selected corresponding to the respective delinquency event type, the system makes no changes to the trigger date even if it is past dated. Finally, the system sets the status of the delinquency event to Pending.

Note:

If the trigger date of an event is moved to a future date, the trigger date of the subsequent events in the delinquency process is also moved accordingly. This is because the system is designed to trigger only one event at a time in a month.

Usually, this batch changes the status of the delinquency event from Pending Evaluation to Pending. But, if the wait period in the respective delinquency process type is set to Monthly Cyclic and if the Move Past Dated Event to Future option is selected corresponding to the respective delinquency event type, the C1-ADJTGDT algorithm attached to the Post-Processing system event of the C1-DPEVL batch moves the past dated trigger date to a future date and changes the status of the delinquency event to Pending.

If the Preview Required option is not selected corresponding to the delinquency event type in the respective delinquency process type, the system sets the preview status of the delinquency event to Not Required. However, if the Preview Required option is selected corresponding to the delinquency event type in the respective delinquency process type, the system does the following:

  • Derives the preview days specified corresponding to the delinquency event type in the delinquency process type

  • Calculates the preview date (i.e. Trigger Date – Preview Days) for the delinquency event

  • Sets the preview status of the delinquency event to Pending

The C1-DPEVL batch is a multi-threaded batch. The multi-threading is based on delinquency event ID and chunks for multi-threading are created based on numerical distribution of delinquency event ID. For more information about the batch, see Oracle Revenue Management and Billing Batch Guide.