C1-THRSHDAMT

This algorithm is invoked when the membership is in the Pending Effectuation status and the status reason is Awaiting Binder Payment, as per the binder payment preference configuration done in the Field Mapping screen. It monitors or checks the memberships from whom the binder payment is yet to be received.

This algorithm's behavior is shown as follows:

Scenario System Behavior
If the BINDER_​PAY_​APPL_​SW field (also known as the Binder Payment Applicability flag) from the CI_​MEMBERSHIP table is set to Y The algorithm retrieves the BINDER_​LIABILITY_​AMT from the CI_​MEMBERSHIP table.
If the Consider Binder Liability Amount Flag is set to Y, and the Binder Liability Amount is blank or the Binder Liability Amount is less than zero The algorithm generates an error, Binder Liability Amount can’t be blank or less than zero if the Consider Liability Amount is Y.
If the BINDER_​LIABILITY_​AMT field from the CI_​MEMBERSHIP table is not blank and greater than zero The algorithm calculates the threshold amount using the following formula,
CI_MEMBERSHIP.THRESHOLD_AMT = CI_MEMBERSHIP.BINDER_LIABILITY_AMT * (CI_MEMBERSHIP.BINDER_PAY_THRES %)

For example, Let's assume that the binder liability amount is $100 and binder payment threshold percentage is 90%. The algorithm uses the above formula to derive the threshold amount which is $100 * 90% = 90. The calculated threshold amount is added in the CI_​MEMBERSHIP.THRESHOLD_​AMT field for the membership which is in Pending Effectuation status where the status reason is Awaiting Binder Payment.

Note: The threshold amount is updated whenever the binder liability amount or binder threshold percentage value changes for the membership which is in the Pending Effectuation status.