Hold Delinquency

Oracle Revenue Management and Billing enables you to hold the delinquency process for a person or an account through a hold request. If the delinquency process is kept on hold for an account, the system does not allow you to continue the delinquency process (if any) created for the account. Similarly, if the delinquency process is kept on hold for a person, the system does not allow you to continue the delinquency process (if any) created for the person and its accounts.

While adding the delinquency process in a hold request, you need to specify the date range for which you want to hold the delinquency process for the persons or accounts. The system enables you to hold the delinquency process while creating a hold request from the user interface or through the upload request feature. If you want to create a hold request to hold the delinquency process for a person or an account through the upload request feature, you need to specify the following details in the CSV file:

• Whether you want to hold the delinquency process for the person or account (the valid values are Y or N)

• Hold delinquency start date (required if the hold delinquency is set to Y)

• Hold delinquency end date

You can also create, update, or release a hold request through an inbound web service. For more information, see Hold Request Creation, Modification, Release, and View Through Inbound Web Service.

Delinquency Hold Activation

On activating a hold request for an account, the system sets the postpone credit review until date corresponding to the accounts whose date range falls within the delinquency process date range of the hold request. The postpone credit review until date is set to the hold entity end date or delinquency process end date whichever is earlier. If the postpone credit review until date stamped on the delinquent account is later than the system date, the system will then hold the delinquency process, if any, initiated for the account. Note that if the start date of the hold request, hold entity, or hold process is earlier than the system date, the system sets the respective start date to the system date.

Let us understand how the postpone credit review until date is derived for an account that is kept on hold through a hold request.

In the scenario 1, the postpone credit review until date for the Account 1 is set to 15-Jan-2025 and the postpone credit review until date for the Account 2 is set to 20-Jan-2025. This is because the entity end date is earlier than the delinquency process end date. However, in the scenario 2, the postpone credit review until date for the Account 1 is set to 20-Jan-2025. This is because the delinquency process end date is earlier than the entity end date.

In the scenario 3, three hold requests are created with different hold reasons to keep the Account 3 on hold for different duration. In this case, the postpone credit review until date of the Account 3 is updated every time a new hold request is created for the same account. On 1st Jan, the postpone credit review until date of the Account 3 is set to 15-Jan-2025 and then on 5th Jan, the postpone credit review until date of the Account 3 is updated to 20-Jan-2025, and finally, on 10th Jan, the postpone credit review until date of the Account 3 is updated to 25-Jan-2025.

In the scenario 4, the postpone credit review until date for the Account 1 and Account 2 is set to 30-Jan-2025. This is because the system sets the postpone credit review until date to the delinquency process end date when the entity end date is not specified in the hold request. In the scenario 5, the postpone credit review until date for the Account 1 and Account 2 is set to 31-Jan-2025. This is because the system sets the postpone credit review until date to hold request end date when both the entity end date and delinquency process end date are not specified in the hold request. In the scenario 6, the postpone credit review until date for the Account 1 and Account 2 is set to 15-Jan-2025 and 20-Jan-2025, respectively.

In all the above scenarios, the start date of the hold request, hold process, and hold entity is same. Therefore, the postpone credit review until date is derived for the entities either immediately or in the deferred mode (when the C1-HLDRQ batch is executed). However, if the start date of the delinquency process or hold entity is later than the hold request start date, the postpone credit review until date is derived for the respective entity in the deferred mode (when the C1-HLMON batch is executed on or after delinquency process or hold entity start date). For example,

In the scenario 1, the postpone credit review until date for the Account 1 is derived on 01-Jan-2025 (in the online mode), or on or after 01-Jan-2025 (in the deferred mode). However, the postpone credit review until date for the Account 2 is derived on or after 05-Jan-2025 (in the deferred mode). Similarly, in the scenario 2, the postpone credit review until date for the Account 1 is derived on or after 15-Mar-2025 (in the deferred mode) and not on 01-Mar-2025.

On activating a hold request for a person, the system sets postpone credit review until date to the entity end date or process end date whichever is earlier for the respective person and its immediate accounts (where the person is the main customer). If the postpone credit review until date does not exist for the person or if the postpone credit review until date already exists for the person but is earlier than the system date, then the postpone credit review until date is set to the entity end date or process end date whichever is earlier. However, if the postpone credit review until date already exists for the person but is later than the derived hold end date (i.e., entity end date or process end date whichever is earlier), then the postpone credit review until date of the person is not updated.

If the postpone credit review until date does not exist for the person’s immediate account or if the postpone credit review until date already exists for the person’s immediate account but is earlier than the derived hold end date, then the postpone credit review until date is set to the derived hold end date. However, if the postpone credit review until date already exists for the person’s immediate account but is later than the derived hold end date, then the postpone credit review until date of the account is not updated.

If the Hierarchy option is selected for the person, the system sets the postpone credit review until date for the person, its immediate accounts, its child persons, and for the child persons’ accounts. Note that the system considers only the child persons and not the grandchild persons from the person’s hierarchy and then derives the accounts where the child person is the main customer. If the postpone credit review until date does not exist for the person’s child person or if the postpone credit review until date already exists for the person’s child person but is earlier than the derived hold end date, then the postpone credit review until date is set to the derived hold end date. However, if the postpone credit review until date already exists for the person’s child person but is later than the derived hold end date, then the postpone credit review until date of the child person is not updated.

Similarly, if the postpone credit review until date does not exist for the child person’s account or if the postpone credit review until date already exists for the child person’s account but is earlier than the derived hold end date, then the postpone credit review until date is set to the derived hold end date. However, if the postpone credit review until date already exists for the child person’s account but is later than the derived hold end date, then the postpone credit review until date of the child person’s account is not updated.

If the postpone credit review until date stamped on the delinquent person or account is later than the system date, the system will then hold the delinquency process, if any, initiated for the person or account. Note that if the start date of the hold request, hold entity, or hold process is earlier than the system date, the system sets the respective start date to the system date.

If the Delinquency process is added in the hold request, the system derives the entity level of the hold request. If the entity level is set to Account, the system checks whether any individual or group membership is billed to the account. If an individual membership is billed to the account, the system determines whether the number of entities in the hold request exceeds the defer processing count (specified in the respective hold request type). If the number of entities in the hold request is less than or equal to the defer processing count, the system sets the status of the hold request to Active. In addition, it immediately sets the postpone credit review until date for the respective account. However, if the number of entities in the hold request is greater than the defer processing count, the system sets the status of the hold request to Deferred Processing. The system then sets the postpone credit review until date for the respective accounts in the deferred mode when the C1-HLDRQ batch is executed.

However, if a group membership is billed to the account, the system does not use the defer processing count. It sets the status of the hold request to Active. It then sets the postpone credit review until date for the respective accounts in the deferred mode when the C1-HLMON batch is executed. Similarly, if the entity level is set to Person, the system does not use the defer processing count. It sets the status of the hold request to Active. It then sets the postpone credit review until date for the respective persons and its accounts in the deferred mode when the C1-HLMON batch is executed.

Delinquency Hold Release

On releasing a hold request for an account, the system sets the postpone credit review until date to the system date for the respective account. Let us understand how the postpone credit review until date is updated for an account when the hold is manually or automatically released.

In the scenario 1, the postpone credit review until date for the Account 1 and Account 2 is set to the system date when the hold request is manually released on 10-Jan-2025. In the scenario 2, the postpone credit review until date for the Account 1 is set to the batch business date (i.e., 20-Jan-2025) when the hold request is automatically released through the C1-HLMON batch on 20-Jan-2025.

In the scenario 3, the postpone credit review until date for the Account 3 is not set to the system date when the hold request 2 and 3 are manually released on 10-Jan-2025 and 20-Jan-2025, respectively. The postpone credit review until date for the Account 3 is set to the system date when the hold request 4 is manually released on 21-Jan-2025. This is because no more hold requests exist for the Account 3 in the system.

On releasing a hold request for a person, the system sets the postpone credit review until date to the system date for the respective person and its immediate accounts (where the person is the main customer). If the Hierarchy option is selected for the person, the system sets the postpone credit review until date for the person, its immediate accounts, its child persons, and for the child persons’ accounts. Note that the system considers only the child persons and not the grandchild persons from the person’s hierarchy and then derives the accounts where the child person is the main customer. The way in which the postpone credit review until date is updated for the person, its immediate accounts, its child persons, and its child persons’ accounts is same as that of an individual account whose hold is released either manually or automatically.

The system does not consider the defer processing count while releasing a hold request where the delinquency process is kept on hold for an account or a person. The system sets the postpone credit review until date in the deferred mode when the C1-HLMON batch is executed.