Monitoring Advance Deposit of a Parent Customer

A new batch control named C1-ADMON is introduced in this release. It considers all the parent customers where the advance deposit level is set to PG or POLI. For a parent customer where advance deposit level is set to PG, the batch checks whether any customer contact is created using the given customer contact type for the given customer contact class where the respective person ID is stored as a characteristic on the customer contact. The system considers the characteristic type which is specified in the Person ID Characteristic for Inbound Log option type of the C1-ASOBLLNG feature configuration. If a customer contact exists for the parent customer, the batch does not consider the parent customer for further processing.

However, if a customer contact does not exist for the parent customer, the batch derives the advance deposit amount and advance deposit grace days from the parent customer level. It then calculates the grace end date and checks whether the grace end date is earlier than or equal to batch business date. If so, the system derives the advance deposit account relationship type and advance deposit contract type from the delinquency process preference. The system then derives the parent customer's advance deposit account and advance deposit contract using the advance deposit account relationship type and advance deposit contract type, respectively. The batch then checks whether the payments received against the advance deposit contract exceeds the advance deposit amount. If the sum of payments does not exceed the advance deposit amount, the system creates a customer contact using the given customer contact type for the given customer contact class. In addition, the system considers the characteristic type that is specified in the Person ID Characteristic for Inbound Log option type of the C1-ASOBLLNG feature configuration and then stamps the person ID using the respective characteristic type on the customer contact.

However, if the grace end date is later than the batch business date or if the sum of payments exceeds the advance deposit amount, the system does not consider the parent customer for further processing.

Similarly, for a parent customer where advance deposit level is set to POLI, this batch fetches all the policies where the parent customer is the policy holder and where the advance deposit applicability is set to Y. The system considers those polices where the parent customer is associated using the policy person role that is specified in the Parent Customer Policy Person Role option type of the C1-ASOBLLNG feature configuration.

For each such policy, this batch checks whether any customer contact is created using the given customer contact type for the given customer contact class where the respective policy ID is stored as a characteristic on the customer contact. The system considers the characteristic type which is specified in the Policy Characteristic Type for Customer Contact attribute of the delinquency process preference. If a customer contact exists for the policy, the batch does not consider the policy for further processing.

However, if a customer contact does not exist for the policy, the batch derives the advance deposit amount and advance deposit grace days from the policy. It then calculates the grace end date and checks whether the grace end date is earlier than or equal to batch business date. If so, the system derives the advance deposit account linked to the policy and the advance deposit contract using the advance deposit contract type specified in the delinquency process preference. The batch then checks whether the payments received against the advance deposit contract exceeds the advance deposit amount. If the sum of payments does not exceed the advance deposit amount, the system creates a customer contact using the given customer contact type for the given customer contact class. In addition, the system considers the characteristic type that is specified in the Policy Characteristic Type for Customer Contact attribute of the delinquency process preference and then stamps the policy ID using the respective characteristic type on the customer contact.

However, if the grace end date is later than the batch business date or if the sum of payments exceeds the advance deposit amount, the system does not consider the policy for further processing.

This batch also derives the preferred contact method for the customer contact. While deriving the preferred contact method, the batch 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, this batch 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 batch is a multi-threaded batch. The multi-threading is based on person ID and chunks for multi-threading are created based on numerical distribution of person ID. You can specify the following parameters while executing this batch: