Hold Auto Pay

Oracle Revenue Management and Billing enables you to hold the auto pay process for an account through a hold request. If the auto pay process is kept on hold for an account, the system does not allow you to create automatic payments for the debit bills of the account.

While adding the auto pay process in a hold request, you need to specify the date range for which you want to hold the auto pay process for the accounts. The system enables you to hold the auto pay process by 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 auto pay process for an account through the upload request feature, you need to specify the following details in the CSV file:

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

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

• Hold auto pay 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.

Auto Pay Hold Activation

On activating a hold request for an account, the system sets the defer auto pay date corresponding to the accounts whose date range falls within the auto pay process date range of the hold request. The defer auto pay date is set to the hold entity end date or auto pay process end date whichever is earlier. This means that the system will allow to create automatic payments for the accounts only after the respective defer auto pay date. 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 defer auto pay date is derived for an account that is kept on hold through a hold request.

In the scenario 1, the defer auto pay date for the Account 1 is set to 15-Jan-2025 and the defer auto pay date for the Account 2 is set to 20-Jan-2025. This is because the entity end date is earlier than the auto pay process end date. However, in the scenario 2, the defer auto pay date for the Account 1 is set to 20-Jan-2025. This is because the auto pay 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 defer auto pay date of the Account 3 is updated every time a new hold request is created for the same account. On 1st Jan, the defer auto pay date of the Account 3 is set to 15-Jan-2025 and then on 5th Jan, the defer auto pay date of the Account 3 is updated to 20-Jan-2025, and finally, on 10th Jan, the defer auto pay date of the Account 3 is updated to 25-Jan-2025

In the scenario 4, the defer auto pay date for the Account 1 and Account 2 is set to 30-Jan-2025. This is because the system sets the defer auto pay date to the auto pay process end date when the entity end date is not specified in the hold request. In the scenario 5, the defer auto pay date for the Account 1 and Account 2 is set to 31-Jan-2025. This is because the system sets the defer auto pay date to hold request end date when both the entity end date and auto pay process end date are not specified in the hold request. In the scenario 6, the defer auto pay 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 defer auto pay 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 auto pay process or hold entity is later than the hold request start date, the defer auto pay date is derived for the respective entity in the deferred mode (when the C1-HLMON batch is executed on or after the auto pay process or hold entity start date). For example,

In the scenario 1, the defer auto pay 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 defer auto pay date for the Account 2 is derived on or after 05-Jan-2025 (in the deferred mode). Similarly, in the scenario 2, the defer auto pay date for the Account 1 is derived on or after 15-Mar-2025 (in the deferred mode) and not on 01-Mar-2025.

If the number of accounts in the hold request is less than or equal to the defer processing count (specified in the respective hold request type), the system immediately sets the defer auto pay date for the respective accounts. However, if the number of accounts in the hold request is greater than the defer processing count, the system sets the defer auto pay date for the respective accounts in the deferred mode when the C1-HLDRQ batch is executed.

Auto Pay Hold Release

On releasing a hold request for an account, the system sets the defer auto pay date to the system date for the respective account. In addition, the automatic payment details of the debit bills (if any) for the respective account are updated in the CI_​BILL_​ACH table. Let us understand how the defer auto pay date is updated for an account when the hold is manually or automatically released.

In the scenario 1, the defer auto pay 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 defer auto pay 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.

In the scenario 3, the defer auto pay 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 defer auto pay 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.

If the number of accounts in the hold request is less than or equal to the defer processing count (specified in the respective hold request type), the system immediately sets the defer auto pay date to the system date for the respective accounts. However, if the number of accounts in the hold request is greater than the defer processing count, the system sets the defer auto pay date to the system date for the respective accounts in the deferred mode when the C1-HLMON batch is executed.