C1-RULEAPPRC

This algorithm considers financial transactions (FTs) where the financial transaction type is set to Bill Segment (BS), Bill Cancellation (BX), Adjustment (AD), and Adjustment Cancellation (AX). It checks whether there are rule based auto pay instructions for the account which are effective on the bill's due date. Note that the system considers rule based auto pay instructions where the auto pay usage is set to Debit or Credit and Debit for the debit FT amount and rule based auto pay instructions where the auto pay usage is set to Credit or Credit and Debit for the credit FT amount. If there are multiple rule based auto pay instructions effective on the bill's due date, the system will sort and consider the rule based auto pay instructions based on the priority. In addition, if there are two rule based auto pay instructions for the same date range – one with the auto pay usage set to Debit and another with the auto pay usage set to Credit and Debit, the system considers the rule based auto pay instruction with the highest priority. Similarly, if there are two rule based auto pay instructions for the same date range – one with the auto pay usage set to Credit and another with the auto pay usage set to Credit and Debit, the system considers the rule based auto pay instruction with the highest priority.

If the rule based auto pay instruction with the highest priority does not have any rules, the auto pay ID is simply stamped against the financial transaction in the C1_FT_EXT table. If the rule based auto pay instruction with the highest priority has rules, then the rule criteria derivation algorithm on the respective rule type is executed to derive the required output, which is in turn sent to the auto pay rules engine for evaluation. If the financial transaction satisfies the rules defined in the auto pay instruction, the auto pay ID is stamped against the financial transaction in the C1_FT_EXT table. However, if the financial transaction does not satisfy the rules defined in the auto pay instruction, the system considers the rule based auto pay instruction with the next priority and then derives the parameters which are to be used by the auto pay rules engine for evaluation. If the financial transaction does not satisfy any rule based auto pay instruction which is effective on the bill's due date, the system checks whether there is an effective default auto pay instruction for the account. If there is an effective default auto pay instruction for the account, the auto pay ID is stamped against the financial transaction in the C1_FT_EXT table. However, if there is no effective default auto pay instruction for the account, the auto pay ID is not stamped against the financial transaction in the C1_FT_EXT table.

Once the auto pay ID is stamped against the financial transaction, the system checks whether the Autopay Creation Option field in the installation options is set to Freeze Payment on Notification. If so, it checks whether the C1-APAY-CROP algorithm is attached to the Override Auto Pay Creation Option system event of the customer class. If the algorithm is attached and returns the value as Y, the automatic payment or adjustment for automatic refund is created and a record with zero value is created in the CI_BILL_ACH table. However, if the algorithm is not attached or returns the value as N, a record with the calculated automatic payment or automatic refund amount is created in the CI_BILL_ACH table.

Before creating the automatic payment or adjustment for automatic refund, or before creating a record in the CI_BILL_ACH table, the system checks whether the Generate Auto Pay option is selected in the respective auto pay source's tender type. If the Generate Auto Pay option is selected and the CI_BILL_ACH record is in credit, the algorithm attached to the Automatic Adjustment Creation system event in the installation options is executed. If the Generate Auto Pay option is selected and the CI_BILL_ACH record is in debit, the algorithm attached to the Automatic Payment Creation system event in the installation options is executed.

However, if the Generate Auto Pay option is not selected in the respective auto pay source's tender type, an error occurs, and the algorithm is aborted. This algorithm is invoked during:

Online billing when the Bill Segment Freeze Option field in the installation options is set to Freeze At Bill Completion (Note that, in this case, the algorithm only considers the financial transactions of the post-processing bill segments.)
Online billing when the Bill Segment Freeze Option field in the installation options is set to Freeze At Will

Note: Note that this algorithm is invoked only when it is attached to the Rule Based Auto Pay Processing system event of the required customer class.