Debt Notification Delinquency Process

There might be scenarios wherein the group or individual customers fail to pay premium for their policy plan or health plan coverage, respectively. In such cases, you may want to send reminder notifications to the group or individual customers to pay their premium immediately without any delay. Oracle Revenue Management and Billing enables you to send one or more To Do notifications at regular intervals to:

  • The person (i.e. parent customer or bill group) when the delinquency process is created for a person

  • The main customer of the account when the delinquency process is created for an account

To create a delinquency process to send To Do notifications, you need to design the delinquency process type (using which you want to create the delinquency process) in the following manner:

The following table lists how you can design the delinquency process type (using which you want to create the delinquency process) to send To Do notifications.
Delinquency Process Type Delinquency Event Type System Event Algorithm Algorithm Purpose
DP1 Send First Reminder Notification Event Activation C1-DLQCRTODO1 Creates a To Do using the given To Do type
Send Second Reminder Notification Event Activation C1-DLQCRTODO2 Creates a To Do using the given To Do type
Send Third Reminder Notification Event Activation C1-DLQCRTODO3 Creates a To Do using the given To Do type

Note that the C1-DLQCRTODO algorithm is shipped with the product. However, you can create different algorithms (for example, C1-DLQCRTODO1, C1-DLQCRTODO2, and C1-DLQCRTODO3) using the C1-DLQCRTODO algorithm type when you want to send different reminder notifications at regular intervals to the person or the main customer of the account. For more information about the C1-DLQCRTODO algorithm, see Delinquency Event Type.

Note: If you want to send the same reminder notification (i.e. the same message) multiple times at different intervals, you can use the C1-DLQCRTODO algorithm in all the delinquency event types. However, if you want to send different reminder notifications (i.e. the different message) at different intervals, you can create different algorithms (for example, C1-DLQCRTODO1, C1-DLQCRTODO2, and C1-DLQCRTODO3 as shown above) and attach it to the delinquency event type in the sequence in which you want to send the reminders.

Once a delinquency process is created for a person or an account to send To Do notifications, 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. Once the first event in the delinquency process is triggered, the status of the delinquency process is changed to the value (for example, Delinquency In Progress) specified in the Delinquency Process InProgress Status attribute of the delinquency process preference. Once a To Do is created for the person or the main customer of the account, the status of the delinquency event is changed to Completed. Once all the delinquency events are triggered successfully, the status of the delinquency process is changed to the value (for example, Completed) specified in the Delinquency Process Completed Status attribute of the delinquency process preference.

The system may receive a payment or an adjustment against the overdue bill for which a delinquency process is created to send To Do notifications. In such case, the system behaves in the following manner depending on the status of the delinquency process:

  • If a payment or an adjustment is made when a delinquency process is in the Initiated, Delinquency In Progress, On Hold status, the status of the delinquency process is changed to the value (for example, Canceled) specified in the Delinquency Process Canceled Status attribute of the delinquency process preference. For more information on how the delinquency process is automatically canceled, seeCanceling a Delinquency Process.

  • If a payment or an adjustment is made when a delinquency process is in the Pending Termination status, the status of the delinquency process is changed to the value (for example, Canceled) specified in the Delinquency Process Canceled Status attribute of the delinquency process preference. For more information on how the delinquency process is automatically canceled, seeCanceling a Delinquency Process. This scenario is valid only for the fully insured individual business. This scenario is addressed only when such delinquency processes are automatically canceled through the C1-DPMON batch.

  • If a payment or an adjustment is made when a delinquency process is in the Completed status, no action takes place on the debt notification delinquency process.

However, if the payment or adjustment is canceled due to any reason, the system executes the C1-CDPPAYCAN or C1-DPADJCAN algorithm attached to the customer class or adjustment type, respectively, to resume the delinquency process. For more information on how the delinquency process is automatically resumed, see Resuming a Delinquency Process.

Note:

If a payment or an adjustment is canceled when a debt notification delinquency process is in the Completed status, no action takes place on the debt notification delinquency process.

The system considers the delinquency process 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