This facility enables you to reject selected pay centres from a debit order run that included multiple pay centres.
From the main menu on top, select Transaction Capture. A sub-menu will be displayed on the left.
Select Debit Order Rejections.
The JU2DO Rejections Control List screen will be displayed.
All processed debit order collection runs will be listed. The list can be filtered by scheme code and/or due date.
From the JU2DO Rejections Control List screen, highlight the required transaction, then select Pay Centre Rejection from the sub-menu on the left.
The JU2DS Debit Order Pay Centre Rejection List screen will be displayed.
All pay centre totals will be listed.
Note:
This screen displays only 15 lines. To search for specific pay centres, select SEARCH. The JU2DS Search Criteria screen will be displayed.
To view more details, click DETAIL. The JU2DS Debit Order Pay Centre Rejection Details screen will be displayed.
Click CLOSE to return to the JU2DS Debit Order Pay Centre Rejection List screen.
Select a value from the Rejection Reason drop-down box to indicate the reason for rejection 
.
Select the transactions to be reversed by placing a tick in 
on the required lines. Select Submit Rejection from the sub-menu on the left.
The following confirmation message will be displayed.
Click YES. The selected items will no longer be displayed on the JU2DS Debit Order Pay Centre Rejection List screen.
For each SFEFTPAY Accounting Activity selected and submitted, the system will find all of the Business Transactions created in the selected Debit Order run for that membership and create the equivalent reversal Business Transaction as per current functionality.
In the Debit Order Rejection batch job, an AD HOC Membership Payment Detail record with a Frequency of MONTHLY irrespective of the Frequency of the original record will be created for the rejected payment and the Last Payment Date is not updated on the regular Membership Payment Detail record. This is done so that rejections for non-monthly payments are not only re-collected a year later or three months later, etc. and are recollected in the following debit order run.
When the AD HOC Membership Payment Detail record is created, the system will update the Amendment Reason with the System Value for the UDPV Object SUSPENSION AMENDMENT REASON with a value for Description equal to the value for Description on the System Value for the UDPV Object EFT REJECTION REASON selected on the JU2DR Debit Order Member Transaction List screen.
When determining the number of premiums that have been rejected, the system will count the number of AD HOC Membership Payment Detail records. The value for Description on the PAIDUP NO PREMS Scheme Parameter for the Scheme will be read or, if not found, the PAIDUP NO PREMS Global Parameter will be read.
If the number of premiums is less than the value for the PAIDUP NO PREMS parameter, the system will read the Rejection Reason on the Debit Order Rejection control record for the Member for the payment with a Due Date of the previous month to the Debit Order run month.
If the Rejection Reason is NO MANDATE LOADED, the system will create a My Work Service Request with a Process Name equal to NO BANK MANDATE and an Activity Name equal to NOTIFY POLICYHOLDER and the Scheme Code and Membership Number equal to the Scheme Code and Membership Number for the Membership.
For more information refer to
My Work
Process SR
No Bank Mandate
If the Rejection Reason is not NO MANDATE LOADED, the system will read the PDF Template with a PDF Process of DO REJECTION and a Process Sub-Type equal to the Rejection Reason and create a PDF document.
If a Document Template with a PDF Process of DO REJECTION and a Process Sub-Type equal to the Rejection Reason is not found no letter will be generated.
A Service Request with a Process Name equal to LAPSED POLICIES will be created and an Activity Name equal to NOTIFY POLICYHOLDER. A single Service Request for all of these Memberships will be created and not one for each Membership as when this Service Request is processed it will flow to a Bulk Letters screen.
For more information refer to
My Work
Process SR
Lapsed Policies
Number of unpaid premiums greater than parameter
If the number of premiums is greater than or equal to the value for the PAIDUP NO PREMS parameter, the system will retrieve the transactions in the member’s CONTRIBUTION account and sum the amounts.
No premiums paid
If the result is equal to the value of the reversal amount, i.e. after the reversal the member will not have paid a premium, the system will update the Membership Status for the Member to ENDED with an Effective Date equal to the Last Payment Date and update the value for Policy Decision Status on Member Values to NOT TAKEN UP.
One or more premiums paid
If the result is greater than the value of the reversal amount, i.e. after the reversal the member will have paid previous premiums, the system will update the Membership Status for the Member to ENDED with an Effective Date equal to the Last Payment Date and update the value for Policy Decision Status on Member Values to LAPSED.
The system will read the Rejection Reason on the latest Debit Order Rejection control record for the member. If the Rejection Reason is NO MANDATE LOADED, the system will create a My Work Service Request with a Process Name equal to SECOND NO BANK MANDATE and an Activity Name equal to NOTIFY POLICYHOLDER and the Scheme Code and Membership Number equal to the Scheme Code and Membership Number for the Membership.
For more information refer to
My Work
Process SR
Second No Bank Mandate
Rejection Reason Display
Product > Policyholder Details > Payment Details.
The Rejection Reason will be displayed on the JU4ET Payment Detail Maintain List screen in the Amendment Reason column.
The Rejection Reason will be displayed on the JU4ET Payment Detail Maintain in the Amendment Reason field.
Note:
The Rejection Reason is not recorded on the Business Transaction and therefore it will not be possible for it to be displayed on the Payment History as this is an extract from the Business Transactions.
Lapse Letter Batch Job
Lapse Letters
When the BJU7AB Endowment Batch Job that runs every night to create the lapse letters runs, the system will find all of the Membership records with a Membership Status equal to ENDED and a Policy Decision equal to LAPSED or NOT TAKEN UP and for which there is no Policy Lapse Control record or for which the Status is not C (Completed).
The system will read the value for Percentage on the GRACE PERIOD Scheme Parameter and the start date of the Membership Status of ENDED to check if the policy is within the grace period or not and processes the policy accordingly.
Note:
A Policy Lapse Control record is created so that the same policy is not processed multiple times as the batch job runs every day. It is created with a Status of Completed when it has been processed.
In addition to this and prior to the grace period, the system will check if the policy has been reinstated previously and if so if it has been reinstated for the maximum number of times permitted. This is irrespective of whether or not it is within the grace period.
If there is no Policy Lapse Control record with a Status of C, the system will read the value for Description for the Scheme Parameter with a Parameter Type of MAX REINSTATE.
The system will determine the number of times the policy has been reinstated previously i.e. check the number of times that the Membership Status of PAID UP is immediately followed by a Membership Status of LIVE.
Premium unpaid for less than the grace period
If there is no Policy Lapse Control record with a Status of C and the start date of the Membership Status of PAID UP plus the value for the GRACE PERIOD Scheme Parameter is greater than current date i.e. two or more premiums have been unpaid for less than the grace period within which the policy can be re-instated, the system will create a My Work Service Request with a Process Name equal to LAPSED POLICIES and an Activity Name equal to NOTIFY POLICYHOLDER. The system will read the PDF Template with a Process Type LAPSED NOTICE and create a PDF Document for each membership. A Policy Lapse control record will be created for each Membership with an Effective Date equal to current date and Status of P (Processed).
For more information refer to
My Work
Process SR
Lapsed Policies
Premium unpaid for longer than the grace period
If the Status of the Policy Lapse Control record is P (Processed) and the start date of the Membership Status of PAID UP plus the value for the GRACE PERIOD Scheme Parameter is equal to or less than current date i.e. two or more premiums have been unpaid for longer than the grace period of two months within which the policy can be re-instated, the system will retrieve the Business Transaction (BT) in the Member’s CONTRIBUTION account with an Accounting Activity of SFCONTRIB and with the earliest Due Date.
Policy in force less than 18 months
If the Due Date of the earliest SFCONTRIB BT (date of commencement of the policy) is less than or equal to 18 months prior to the Date of Last Payment, the system will create a My Work Service Request with a Process of WITHDRAWAL and with the membership reference number and an Activity Name equal to INITIATE EXIT.
The Status of the Policy Lapse Control record for the Membership will be updated to C (Completed).
For more information refer to
My Work
Process SR
Exits / Withdrawals
Policy in force longer than 18 months
If it is greater than 18 months then the Membership Status will be set to PAID UP and a My Work Service Request with a Process of PAID UP POLICY and an Activity Name of NOTIFY POLICYHOLDER will be created.
The Status of the Policy Lapse Control record for the Membership will be updated to C (Completed).
For more information refer to
My Work
Process SR
Paid Up Policy