Hold Request

Oracle Revenue Management and Billing allows you to hold the amount for Person, Account or Bills. Hold is a way to prevent certain types of activities from taking place for a customer over a given period of time. The activities that need to be on Hold vary according to the reason for hold, such as due to a climate disaster the collection activity remains on Hold until disaster period is over.

Hold Request is a object which contains list of processes to be kept on hold for certain entities such as account, person, and bill for certain period of time The hold period is defined as the duration between Hold Request Start Date and End Date. Each Hold Request contains an entity and processes on hold. There could exists multiple hold requests for an entity for different hold reasons and processes.

Following are the hold request entities:

  • Person: If the person is on hold then all entities linked to that person where the person is financially responsible, such as accounts and its bills will be on hold.

  • Account: If the account is on hold then all the bills of that account will be on hold.

  • Bill: A bill will be on complete or partial hold.

In Hold Request, following mentioned processes can be on hold:

  • Auto Pay - If the auto payment process is on hold then, then auto pay for the bills of the account added in hold request will be on hold till the request is released. However, you can do the manual payments. On activation of the hold request, Defer Auto Pay Date field (in Account screen) is populated with some future date. If billing process is on hold then auto payment process would also go on hold.

  • Bill Generation - If the bill generation process is on hold then, then new bills will not be created for the account added in hold request till request is released. On activation of the hold request, Bill After date field (in Account screen) is populated with either hold request end date or some future date until that date billing is kept on hold. Whenever hold request is released for billing process then Bill After date field will be populated as system date.

    Note: During the tenure of a hold request if customer does not require pending bills to be used for bill generation, bill in pending for accounts under hold are identified during activation of hold request which can be deleted by execution of the C1-DELBI batch . For more information about the batch, refer to Oracle Revenue Management and Billing Batch Guide

  • Overdue - If the overdue process is on hold then bills associated with accounts in the hold request will be on hold for overdue process. It means existing overdue will be cancelled. New overdue process will get created once hold request is released. On activation of the hold request, Postpone Credit Review field (in Account screen) is populated with either hold request end date or some future date. When hold request is released, Postpone Credit Review field would be set as system date. If the overdue process is on hold then request for policy termination due to non payment will be on hold.

  • Funding - A list of bills identified for a full bill amount or a partial bill amount will be kept on hold for a funding process.

    Note:

    For Funding process, Person, Bill, and Account entities can be put on hold. However, for processes like Auto pay, Bill Generation, and Overdue, only Account entity can be put on hold.

    Processes and Entities start dates and end dates are expected to be with in the limit of Hold Request Start Date and End Date.

You need to specify the hold request type while creating a hold request. Hold request type helps the system to determine:

  • Whether to allow the partial hold for bill or not

  • Whether hold request must be approved by the approver before keeping entities and processes on hold

It is possible for a given entity, such as a person or account, to be affected by hold request with differing periods or at differing levels. For example, if there is a hold request added for a person manually and another hold request is there due to some other reason for an account belongs to the person who is already on hold. The system assumes that both hold requests are in effect for the account and that the period of accounts starts from the start of the earlier hold request record (for the account) until the later of the two release dates.

During the hold request process, a hold request goes through various statuses in its lifecycle. For more information about the hold request statuses, see Hold Request (Without Approval) Status Transition and Hold Request (With Approval) Status Transition

Note that the lifecycle of a hold request is driven by the business object using which the hold request is created. A hold request business object named C1-HoldRequest is shipped with the product. The hold request feature explained in this document is articulated based on the lifecycle and logic defined in the C1-HoldRequest business object. In addition, you can configure the search feature by setting Fkref feature configuration for each entity, such as person, account and bill.

For more information on how to setup the hold request processes, see Prerequisites.

Related Topics

For more information on... See...
Hold Request Type screen Hold Request Type
Hold Request screen Hold Request (Used for Searching)
Hold Request screen Hold Request (Used for Viewing)

Parent Topic: Oracle Revenue Management and Billing Generic Business Processes