Release documentation - Life - Enhancements and requests

Problem:

Account Balance Pairing - 'Always keep Expected Payment Balance after pairing' option Switched OFF doesn't work as expected

Solution:

When the system parameter 'Always keep Expected Payment Balance after pairing' is not selected:

The Expected Payment Balance information will only be kept in the database if the payment currency is the same as the Expected Payment Currency. If the Payment Currency is different from the Expected Payment Currency, the system will inform the user that the Expected Payment Balance will be removed after pairing.

The above is applicable when the pairing is done automatically via the Generate Payment Request option or manually

When the balances are fully settled, the confirmation message will read 'Expected Payment(s) will be removed after pairing. Do you want to continue?

Only when the balances are not fully settled, irrespective of the system parameter the existing message AC00014 that refers to partially settled balances will appear

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Own Bank Account Currency must match Bank Currency not working properly

Solution:
When the system parameter 'Own Bank Account Currency must match the Bank Currency' is ON, the system shall make sure that the correct Bank Account is defaulted, i.e. when only one exists for the given Bank Currency, and if more than one Bank Accounts exist for the given Bank Currency then the user must select one. The only available Bank Accounts to select among shall be those with the same currency as the given Bank Account on the remittance.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Per latest confirmation from CHR: when manage worksheet of service contract, it works more similar with OCC. i.e. when booking the details, if selected EC which flag 'is positive on Assured Business' is checked, its amount should be automatically set as negative -,  if selected EC which flag 'is positive on outward business' is checked, its amount should be automatically set as positive +. While now SICS set sign as opposite with expected. 

Solution:

For the level of business Service Contract - all entry code properties that have been defined for an OCC Business should be applicable

Eg: When the entry code is defined as 'Positive on Assumed business' then when the entry code is used to make a booking on a Service Contract, the amount should be booked as a negative amount
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
retrieveObject returns walkback in SICS Life when AXIS

Solution:

When retrieving any object in the Life environment do not read any P&C conditions.
The object should be retrieved without any abend

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Unplaced Risk are not Updating correctly when the RPO is run

Solution:
When the sum to be retroceded exceeds the available capacity then the amount that exceeds the available capacity should be listed against the respective cession as an unplaced amount when the RPO is run

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Decrease transaction outside latest renewal transaction should not got premium returned

Solution:
Any transaction created beyond the latest effective period should not have any reversal ACIs of any other transaction created. If the transaction is created within an existing effective period then the prorata difference should be calculated for all the ACIs within that period

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when RPO is run without OCCs linked to the PP

Solution:

When the PP has no OCCs attached or OCCS that are not realised or OCCs that are not fully placed 100%, the RPO should fail with the error message No proportional treaties defined/ attached/ fully realised and the system should not abend

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Getting incorrect Calculation in Retrocession when one policy benefit term is over

Solution:
Always consider the accumulated sum at risk as on the date of the RPO during retroprocessing.

When the cession benefit that has been picked up by the RPO has a benefit expiry date less than the RPO effective date, then the sum at risk on this cession should not be included in the accumulation.

Any utilized retention and capacity that is applicable for this cession should be 'released' and be made available for the life, benefit for further retroprocessing

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Cession loader cannot save policy number of cession

Solution:

The policy number, cedent cession number, proposal number and any value that is mapped to the Group Info tab should be updated on the cession that is created as per the mapped value.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when copying the RPO

Solution:

The RPO should be copied without abend. All details on the RPO except the effective date should be copied from the source
This is applicable to RPO with the 'Multiple PP' flag selected and when it is not selected

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Loading commission should not be positive and basic premium should be negative number

Solution:
When the flag on the entry code properties is 'Is Positive on Assumed Business' and there is no specific flag selected for Outward Business, then the entry code should be booked with a negative sign on the Outward accounting

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Underwriting cession not referenced and created through the loader

Solution:

When there is an underwriting cession with a final decision that is referenced through the cession loader
based on the proposal number/ policy number/ cedent cession number and the same insurable object identifier and this underwriting cession has the same details as the record that is referenced then the underwriting cession should be converted into an actual cession
The record that references this UW cession should not create a new cession

When the record that is loaded references an underwriting cession then do not validate for duplicate benefit covered/ insurance product with the message LCH018 on the referenced cession. The underwriting cession should be converted into an actual cession.

If the loader does not reference an underwriting cession and the referenced cession is an actual cession with the same insurance product and benefit covered, then the record should be rejected with LCH018 as per existing functonality

Any loading that is created on the underwriting cession should be copied to the actual cession as per the final underwriting decision

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Error message related to premium term > benefit term incorrectly thrown for short term policies

Solution:

When the short term flag is on:
It will be possible to enter the benefit term and the premium paying term in only days and not years

When the premium term is not explicitly entered, default the benefit term values to the premium term

When the expiry age or expiry date is given, then the BT should be calculated in days and the respective fields updated (similar to what happens when the flag is not selected)

If the flag is not selected - and there is a value > 365 in the benefit term days or policy term days fields then give the message SICS00007 'Please enter the benefit term in years if the number of days is greater than 365'

Irrespective of the Short Term flag : Give the error message 'Premium Term is greater than benefit term' only when the values in the premium term field are greater than the benefit term

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Unable to make the Cession status Active when Cession is created with Transaction code- OLD Business -Online (Manual Cession)

Solution:

Enable the edit button and allow manually adding ACIs on Old Business transactions. No automatic calculation of SAR, ACIs should not be done based on the business conditions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

RPO failed for the Renewal transaction when the OCC Insured Period is outside the cession transaction period

Solution:

Continue to process renewals on the retrocession cession even if the transaction effective period of the cession benefit is outside the insured period of the OCC if the OCC has been terminated or cancelled with the Existing business option 'Runs off'

Continue to validate the retrocession transactions against the insured period (or amendment effective period of the insured period) within which the reinsurance start date of the retrocession cession falls.

Any retrocession cession that is linked to the Insured Period of an OCC where the termination option is 'Existing Business Runs off' should not be picked up by any other OCC for retro processing

When the OCC is NOT terminated or the existing business option is NOT runs off then any retrocessions linked to the insured period of the OCC should not be processed beyond the insured period end date of the OCC

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when runnng the RPO

Solution:

The RPO should validate the cessions against the insured period of the OCC/ OCCs of the PP and process the retrocession cessions and should not abend

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

RPO Issues - Retro Sum at Risk is incorrect, The policy where limit is exceeded is showing Negative value in SAR Net Sum Retained

Solution:

When the calculated retro sum at risk exceeds the autocover limit defined on the OCC then create the retrocession cession with the available autocover amount and list the remaining amount in the list of unplaced amounts in the RPO
The retention on the inward cession should never be calculated as a negative value

RETEST:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
New Cession is getting created when we add a New Benefit with a different benefit reinsurance start date through Loader

Solution:
When the system parameter 'Benefit Reinsurance Start Date' is in use:
When the reinsurance start date and policy number of the cession benefit is referenced to an existing cession, then the benefit that is being created through the batch upload should be created on the same cession with the same reinsurance start date, renewal point (defaulted) but the cession benefit transaction should start with the benefit start date as mapped to the field 'Benefit Reinsurance Start Date'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Commission is not calculated correctly based on the Policy Year

Solution:

When the ceded flag is on:

Use the value in the field Policy Year to calculate the commission
When the policy year = 1 - Use the rates for Initial Commission OR rate defined with the year 1 for Other Deductions
When policy year !=1 - Use the rates defined for the corresponding year in the Renewal Commission or Other Deductions
When the created commission is not Initial commission then always use the entry code for subsequent year commission

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when running RPO when AB classifications do not match the OCC
Solution:

When the classifications of the AB included in the RPO and the PP do not match then reject any cessions that have been picked up by the RPO and cannot be retroceded through the OCC with the existing messages 'Missing Matching OCC- Covered Benefits are Invalid' 'Insurance Product is invalid' or 'Missing Matching OCC- No additional classifications found' depending on which is the mismatched classification

The system should not abend

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Negative amount is not updated to the Claim when created through the loader

Solution:

The ACIs on a claim with the Ceded Paid status should be updated as loaded. The loaded amount should be updated as per the entry code properties (negative or positive)

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when running RPO for the Joint life cessions

Solution:

The RPO should not abend when picking up joint life cessions. The accumulation should be done based on the primary life defined on the joint life cession and the sum to be retroceded should be calculated based on the accumulated SAR on that life

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when calculate ACI on the Standalone Individual Retrocession

Solution:
When the Joint Life Age is defined as Equivalent Single Life age and Determined by Cedant- the value from the Joint Life age should be taken for calculation
If the table has other parameter that is not life specific (such as gender, occupation class etc) then that parameter should also be considered while calculating the ACI
If all the paramters are available, then calculate the ACI using the relevant rates
If the cession benefit does not have one or more of the required values from the table then on a manual cession give the message
No row found for table <table name> for values <parameter for which the value is missing>
If this is created through the cession loader or RPO, just answer yes to the message and do not calculate the ACI on the cession/ retrocession. It should just be created without ACI

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
ACIs for ceded cessions are calculated with renewal entry codes for first year transactions

Solution:

When the ceded flag is selected AND policy year = 1

Automatic calculation of all ACIs should use the first year related entry codes

When the ceded flag is selected AND policy year !=1

Automatic calculation of all ACIs should use the entry codes for subsequent year and the calculation of deductions should use the rate as per the policy year value

When the ceded flag is not selected: The policy year should not impact the entry codes or calculations. The first year transactions should always use the First year entry codes

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

username :- lf_mtk_man_test
password :- lf_mtk_man_test
Database:- postgreSQL_DXCDARCOP002
Personal DB

Abend in Postgre Sql DB in the following scenarios:
1. while creating claims - while attaching a cession in create claim window.
2. while creating individual/ group cessions. - on clicking finish button

Problem:

Commissions for extra premiums have an incorrect sign

Solution:

The ACIs that are created should always follow the rules for the sign as defined on the entry code properties of the respective entry code
When the properties have been defined as 'Positive on Assumed Business' and the flag ' Positive on Outward Business' is not selected then the entry code should be created with a positive sign on an assumed business and a negative sign on the OCC

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Adjustment Reversals should have the retroceded date automatically generated

Solution:

For any automatic reversal transaction copy the Retroceded date from the retroceded date of the source transaction
Only transactions that are created through the RPO should have the Retroceded date from the RPO that created the transaction

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Retrocession ACIs are calculated beyond the Premium Paying Term defined
Solution:

When there is a premium paying term on the retrocession cession no premium ACI or any ACI that is dependent on the premium should be calculated beyond the premium paying term. The renewals and other transactions should be allowed and should continue until the benefit term ends if there is any specific benefit term defined on the cession benefit

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Accumulation calculating wrongly when the same benefit is added to Cession after an earlier cession benefit with the same benefit covered was inactivated

Solution:

Only accumulate active cession benefits as on the date of RPO while calculating the retention and capacity

Whenever there is an inactive cession benefit, then the retention used for that should be 'released' and made available for utilising on other cession benefits having the same benefit covered on the same life

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function

The aim of the enhancement is to be able to extend the term of group cessions that have no member data available without creating any retrocession premiums for the Extended Term Transaction

System Parameters Affected

None

Existing functionality affected

Only when the flag 'Group Cessions without member list' is selected:
When an Extended Term transaction is created, then the corresponding Extended Term transaction will be created on the Retrocession Cession, but no premiums or other ACIs will be automatically calculated for this transaction

When the flag is not selected, depending on the Sum at Risk Retroceded, the corresponding retrocession premiums and other ACIs will be calculated on the Retrocession Cession's Extended Term transaction

Aim of function

The aim of the function is to be able to create claims that have a claim event date that are earlier than the reinsurance start date of the cession

System Parameters Affected

None

Existing functionality affected

Only when the Ceded Flag is selected:

A flag 'Historical Ceded Claim' is available on the inward claim
When this flag is selected it will be possible to create a claim with an event date that falls prior to the reinsurance start date

A new field 'Ceded Factor' is available on the claim
When a value is entered on this field, then the claim recovery will be done as per the percentage entered in this field
If no value is entered in this field, then the claim will be recovered based on the ceded percentage of the last transaction of the cession benefit

Aim of function

The aim of this enhancement is to be able to use the value in the field Retro Sum at Risk on the OCC to define calculation rules

System Parameters Affected

 
A new variable for Retrocession with the value Retro Sum at Risk is now available under the various calculation rules

Selecting this variable in any of the rules will reference to the value in the field 'Retro Sum at Risk' on the Retrocession Cession

Existing functionality affected

Aim of function

The aim of this enhancement is to be able to create informational cessions linked to a non-proportional business

System Parameters Affected

None

Existing functionality affected

Cession handling: It is now possible to add informational cessions linked to a non-proportional assumed business. No automatic calculations or validations will be done on such cessions.

Accumulation Control: An additional filter on the accumulation control is now available where the user will be able to filter cessions based on the Type of Business

Aim of function

The aim of this enhancement was to not calculate any unearned premium irrespective of the option selected if there is a claim with an event date that falls within a lapsed effective period on the cession benefit

System Parameters Affected

None

Existing functionality affected

When the option 'Unearned Premium Exc Claim' is selected on the Unearned Premium Return type option in the AC condition of the business, then when a lapse or termination transaction is created on the cession/ retrocession and there is a claim in the same effective period as the termination transaction, then no unearned premium will be calculated as return

Aim of function

The aim of the enhancement is to be able to include Benefit Covered information in the response of web service executeBusinessSearch

System Parameters Affected

None

Existing functionality affected

The web service executeBusinessSearch will include Benefit Covered information in the response