Notification on Receiving Advance Deposit

Oracle Revenue Management and Billing enables you to send notification via a customer contact when the advance deposit payment is received fully for a customer at the parent customer or policy level. To enable this feature, you need to attach an algorithm created using the C1-NOTADREC algorithm type to the Payment Freeze system event of the parent customer's customer class.

This algorithm checks whether the payment is made on a contract which is created using a contract type specified in the Advance Deposit Contract Type attribute of the delinquency process preference. If the payment is not made on a contract of the advance deposit contract type, no action takes place while freezing the payment. However, if the payment is made on a contract of the advance deposit contract type, this algorithm checks whether the advance deposit contract is linked to any policy. If so, the system derives the advance deposit amount specified on the policy and then checks whether the sum of payments received on the advance deposit contract is greater than or equal to the advance deposit amount specified on the policy. If so, the system creates a customer contact using the given customer contact type for the given customer contact class. In addition, the system stamps the policy ID as a characteristic on the customer contact using the characteristic type which is specified in the Policy Characteristic Type for Customer Contact option type of the DELINPROC feature configuration. However, if the sum of payments received on the advance deposit contract is less than the advance deposit amount, no action takes place while freezing the payment.

If the advance deposit contract is not linked to any policy, the system derives the account for which the advance deposit contract is created. The system then derives the person who is associated with the account using the relationship type which is specified in the Advance Deposit Account Relationship Type attribute of the delinquency process preference. Once the person is derived, the system derives the advance deposit amount specified at the parent customer level. The system then checks whether the sum of payments received on the advance deposit contract is greater than or equal to the advance deposit amount specified at the parent customer level. If so, the system creates a customer contact using the given customer contact type for the given customer contact class. However, if the sum of payments received on the advance deposit contract is less than the advance deposit amount, no action takes place while freezing the payment.

This algorithm also derives the preferred contact method for the customer contact. While deriving the preferred contact method, this algorithm first fetches the main customer's bill route type on the advance deposit account and then fetches the bill routing method of the bill route type. Once the bill routing method is derived, the system considers the preference which is specified in the Routing Method - Contact Method Mapping option type of the DELINPROC feature configuration. For more information about the feature configuration, see Setting the DELINPROC Feature Configuration.

It then checks whether any preferred contact method is mapped to the bill routing method in the preference. If the preferred contact method is mapped to the bill routing method in the preference, the system stamps it on the customer contact. However, if the preferred contact method is not mapped to the bill routing method in the preference, the system considers the default contact method as the preferred contact method and stamps it on the customer contact.

This algorithm contains the following parameters:

• Customer Contact Type - Used to indicate the customer contact type using which you want to create the customer contact. Here, you must specify a customer contact type with the appropriate letter template depending on the type of letter you want to send to the customer.

• Customer Contact Class - Used to indicate the customer contact class to which the customer contact type belongs.

• Default Contact Method - Used to indicate the contact method that you want to use when the preferred contact method cannot be derived for the routing method from the preference.

All these parameters are mandatory.