Problem:

TM process with Service Contract abends

Solution:

Support for Service Contract added

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when we Import Technical Worksheet from Column Spreadsheet

Solution:

It should be possible to create a mapping during the import process of a column spreadsheet. The mapping once created during this process should be available for selection whenever a column spreadsheet is imported

Declination Reason:

Workaround:

Root Cause:

Problem:  ACI Original Accounting Year and Period objects .

Solution:  Need to add those objects and joins in both S Life and O Life Universes.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: Bookings and their related cession bookings

Solution:* Adding alias table, creating joins between them and adding the objects under cession details in the latest version as mentioned in the excel sheet attached.*

Problem:

ACI - Rename of objects

Solution:

Booking Year and period objects renamed

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

On any cession benefit that is active the adjustment reversals should be allowed from the latest active transaction number

The lapse and reinstatement transactions should be ignored when checking for the latest active transaction number since they should not be allowed for adjustment reversals

Solution:

On any cession benefit that is active the adjustment reversals should be allowed from the latest active transaction number

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

SQL related error messages when running the RCO

Solution:

In the RCO or Cession Order: When the From and To Date is entered only the cessions/ retrocessions/ claims/ retroclaims having the Released ACI As of Date that falls within (including) the From and To Date should be picked up

When the To date only is entered then all ACIs that have the status Released that fall within the To Date( included) should be picked up and booked on the cession worksheet

No SQL related error should be thrown when running the RCO or cession order

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When Projection Basis = Yearly, the accounting year on estimate bookings created by the Multi GAAP Accounting and Multi GAAP Retrocession Orders are not correct when the business does not start from January 1st.  For instance, If you have quarterly estimates and the Insured start date is July 1st 2021, the estimates for the first 4 periods are booked with the following Accounting Year and periods::
2021, 1st of 4
2021, 2nd of 4
2022, 3rd of 4
2022, 4th of 4
The last two periods should have Accounting Year 2021

Solution:

Correct the Accounting Year setting for Estimate bookings when Projection Basis = Yearly
No changes to be implemented for Accrual bookings.

Workaround:

Root Cause:

 Extent of Impact:

Impact on Existing Data

None

Recovery Method for Existing Data Affected

N/A

Problem:

SLIFE - Original Accounting Year

Solution:

Added to the SLIFE universe

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Transaction age copied from primary life transaction age on joint life tab

Solution:

Do not populate the transaction age on the Joint Life tab from anywhere. This field is currently informational and needs to be blank

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
MTK- The values in deductible and payment ratio fields are not populated on migrated inward cession and manual standalone individual retrocession

Solution:

Include Deductible and Payment Ratio in the MTK for Inward cessions, retrocessions and placement cessions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
MTK- The Ceded Percentage field on the cession, retrocession, placement cession and Claims is not migrated through MTK.

Solution:

Include Ceded Percentage in the MTK for Inward cessions, retrocessions, placement cessions and Claims.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
MTK- The values in Unplaced Amount and Retroceded Date on Retrocession Information Tab are not populated on migrated inward cession

Solution:

The Deductible and Payment Ratio in the MTK for Inward cessions, retrocessions and placement cessions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Few fields on dates tab of joint life cession are not migrated through MTK

Solution:

All values on the Dates tab in a joint life and individual single life cession benefit transaction should be supported through MTK

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
RCPO run not calculating ACI's in placements for non - ceded claims

Solution:
For non-Ceded claims : When the inward claim has a status of Paid, In Payment, Update Claim Reserve or Special Paid the RCPO should pick up the claim if the payment due date of the inward claim falls within the period end date of the RCPO and process the retroclaims using the ceded factor of the effective period of the cession benefit transaction within which the claim event date falls in

All ACIs should be calculated on the retro claim and placements using the respective ceded percentage or retrocessionarire percentage

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Value changed on Benefit sun retroceded is not updating on notified reinsurer liability field on non ceded standalone individual retrocession claims

Solution:
When the value in the benefit sum retroceded is manually changed the value should reflect in the notified reinsurers liability and the claim liability

When the value in the notified reinsurers liability is changed it should reflect in the claim liability field

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

MTK- Not able to migrate Claim, as System is Rejecting the file.

Solution:

MTK Loader should support all claims- Inward, Standalone Retrocession claims and the placement claims

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Defaulted ACI's are not calculating on Standalone Individual retrocession claims when we add additional ACI's

Solution:
For standalone individual claims with the ceded flag- it should be possible to add ACIs manually in addition to any ACIs that are defaulted from the values in the decision Liability tab

For claims created on retrocessions without the ceded flag - only the automatically calculated ACIs should be allowed.

The above is similar to the existing functionality for manual inward claims

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Issues while processing the RPO for renewal transaction after reinstatement

Solution:

The RPO should pick up all transactions that are active as on the date of running the RPO
When the RPO is run on a cession benefit that has both a termination and a reinstatement, the full recapture transaction and the reinstatement should be created on the linked retrocession. If there are any subsequent renewals or active transactions after the reinstatement, those transactions should also be picked up by the RPO and the retrocession should continue
For any transaction where the retroceded date is set (except termination and reinstatement) the retrocession transactions should be created

If the retros have been created by another RPO until the full recapture and then have been reinstated any subsequent RPO should pick up the active transactions without the retroceded date and continue to process subsequent transactions on the Retrocession

On the inward cession:

All values including the net sum retained, retro sum at risk unplaced that were available on the termination transaction should be updated on the reinstatement transaction (including ACIs if any)

On the retrocession cession and placement cessions :

All values on the full recapture transaction should be automatically restored once the inward cession is reinstated

For all subsequent transactions the RPO should process the transactions similar to how they are processed without an termination and reinstatement in between transactions
 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Original Accounting Year field not saved in DB for placements

Solution:

The Original Accounting Year field is to be stored in the DB for cessions linked to all levels of business where it is applicable

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

UDF fields are not updating on the Cession Benefit.

Solution:

UDF layout should be visible on clicking the UDF icon on the cession benefit if a layout has been created for the criteria of the cession

Declination Reason:

Workaround:

Root Cause:

Problem:
Claim status and Decision is not updating on Retrocession and placement level for Standalone individual retrocession claim after performing Transaction reversal

Solution:

All values from the source transaction should be copied to the reversed transaction on the retrocession and placement level from the inward claim

When the last active transaction is reversed the status should be cancelled and the decision should be declined or rescinded (similar to manual inward claim)

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Claim loader run with Transaction Reversal records is giving a popup Warning message

Solution:

When any warning or confirmation message is triggered when the transaction is created through the loader the message should be by default answered as yes and the transaction should be created

Transaction reversals should be allowed only when the claim is active and the claim has a status of ceded paid or transaction reversal or ceded outstanding

For any other status if a transaction reversal status is passed the record should fail with the message that transaction reversal is not a valid status

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
MTK- The POLICY YEAR field value  on the facultative standalone retrocession and placement is not migrated through MTK.

Solution:

Populate policy year  in the MTK for facultative standalone retrocession and placement.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Additional Classification on the cession is not copied to the renewal transaction for Facultative Standalone Individual Retrocession

Solution:

When the Ceded flag is selected additional classifications that are part of the new business transaction of the manual standalone retrocession should be copied to the renewal transactions. These should not be editable.
On an Other transaction the additional classifications should be editable and once changed they should be copied to the subsequent renewals after the other transaction.
Existing transactions should not be impacted
The additional classifications for lapse or any termination transaction should be coped from the source from which the termination is initiated and should be restored on any reinstatement
All additional classifications should be copied to the placements o the respective transactions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The values in created date and reporting date fields are not being copied to retrocession and placements level after running RPO
 

Solution:
Copy the values from the created date and reporting date from the inward cessions to the retrocession cessions and placements

If the values are entered manually on a standalone retrocession then the value should be copied to the placement cessions
 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends when running RPO for a cession having currency that is not selected on equivalent values of OCC limits condition
 

Solution:
In any setup- irrespective of the system parameters:
When the cession currency is not available on the OCC Limit condition the RPO or manual retrocession process should not abend. The cession should fail with the error message LCH 125 - No matching classification because currency is invalid'
 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

MTK- The Historical Claim Flag is not migrated through MTK.

Solution:

When a claim with the historical claim flag is migrated through MTK the flag should be selected on the migrated claim

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Region of Residence not displayed on the cession benefit

Solution:

Region of Residence should be displayed on the inward cession benefit (single and joint life) and copied to the retrocession and placements

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Transaction age is not calculating correctly on subsequent transactions of retrocession when ‘As Original’ is defined on age definition field of OCC PM condition

Solution:

When the Age Basis is Original on the OCC the age values from the inward cession transactions should be copied to the respective outward cession transactions and placement transactions

When the values are changed on the inward cession transactions they should be reflected on the linked outward transactions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Additional Classification not copied to LAPSE transaction

Solution:
When the ceded flag is selected on the cession OR when the system parameter Use MCOB as additional classifications is selected :

The additional classifications (or the MCOB) should be available on all transactions including ALL terminations
It should be copied from the previous transaction when the cession is created manually or through the loader

For Ceded Policies only and for OTHER transaction only: It should be possible to edit the Additional Classifications on the Other transaction
Additional classifications should not be editable on any other classification

The classifications on the inward cession benefit should be copied to the retrocessions and placement cessions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Multiple renewal on same file - ACI is updating for only last renewal effective period
 

Solution:

When multiple transactions are uploaded through the same load then the ACIs should be calculated for each transaction (when the ACIS are automatically calculated- not- As Original and Calc resposinbility is Reinsurer) and when the ACIs are mapped (as original) for each transaction, they should be updated on each transaction as mapped
 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Error- Policy year is increasing when we create Lapse Transaction or Other Transaction in same year.

Solution:

When any transaction is within the same policy year i.e one year, 12 months, 4 quarters, 2 half years of the immediate previous transaction the policy year should not be automatically increased

For any cession where the premium calculation frequency is single then the policy year should be the same throughout the life cycle of the cession

The policy year for any termination transaction should be copied from the transaction which was terminated and should never be calculated

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 SICS abends while running RPO when nothing is selected on the smoker status field on the cession based on the lookup table define in the L condition of the business

Solution:

When any parameter from the LUT that is part of the validation for retentions and limits is not available on the cession benefit the cession should fail with the message 'No Retention Specified'. SICS should not abend

This is applicable to individual single life cessions and joint life cessions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Issues in the RPO when OLDBUS is picked up

Solution:

Any accumulation rule that is to be applied when running the RPO for cessions with the OLDBUS transaction should be the same as the accumulation rules for a New Business transaction

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System is taking incorrect life as primary life in cession

Solution:
The Life that has been selected as primary life should be considered as Primary Life throughout the life cycle of the cession benefit

The value from the input file that is mapped to the Is Primary Life in the mapping should be created as the primary life

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

After the last active transaction on the claim is reversed through the transaction reversal status the status of the claim should be changed to Cancelled and the decision should be updated as Declined (similar to cancellation of non ceded claims)

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Other deductions are calculating with negative sign on 'Other' transaction of facultative standalone individual retrocessions

Solution:

 Other Deductions should be calculated on prorata basis for the Other transaction

The Other Deductions should follow the sign as defined in the entry code properties

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Incorrect additional ACI's calculation in placements in standalone individual retrocession claims, if we have two retrocessionaire in occ's placements condition.

Solution:

ALL ACIs whether automatically calculated or manually added should be calculated on the placement claims in the percentage of each retrocessionaire placement

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Loading age not added into individual life age when we performed other transaction

Solution:
Age loadings should be applicable throughout the life cycle of the cession

If an age loading has been added for the new business then this should be applied to the life and the transaction age should be calculated with the loading inclued

This is applicable to manual and loaded inward cessions and faculatative and non-facultative standalone retrocessions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Incorrect adjusted issue age calculated for individual life after performing reinstatement transaction

Solution:

Adjusted Issue Age and Issue Age should always remain the same throughout the life cycle of the cession. No recalculation to be done during  reinstatement transaction- all details from the transaction that is being reinstated should be copied

All transactions after the reinstatement should continue to NOT recalculate the issue age and adjusted issue age

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Solution:

When the benefit reinsurance start date is not the same as the reinsurance start date, the ACIS should be calculated on prorata basis for the transaction

It should be possible to add a duplicate (same IP, BC) benefit to the cession both manually and through the loader if there is no active cession benefit with the same IP. BC

When a renewal is processed through the loader and the cession benefit is referenced, the active cession benefit should only be referenced and hence it should be renewed without any error or confirmation message

ONLY if there is more than one active cession benefit on the cession with the same BC, IP should the confirmation message LCH018 be triggered

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System abends when we calculate ACI's after adding total mortality/morbidity loading factor

Solution:

The ACI should be calculated for any loading that is added to the cession benefit

When the manual standalone retrocession is created (with the PP or facultative) with or without the ceded flag it should not check for inward cession details. 

The behaviour should be similar to any manual inward cession (with or without the ceded flag)

It should be possible to create manual facultative retrocessions wthout the ceded flag irrespective of any system parameter

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Retention is calculating wrongly when we decrease (Renewal) the SAR for OLD Business

Solution:

When the SAR on a transaction has been updated and is different from the SAR on the previous transaction the RPO should recalculate the accumulated SAR for that IO and benefit covered and calculate the new retention and retro sum at risk for the transaction

If the accumulated SAR has been decreased, but there is no change to the utilised retention, then there should be no change in the retention that is calculated but the retro SAR should be updated as per the new SAR

If the accumulated SAR has been decreased to fall below the retention then the entire SAR should be retained and the retro SAR on the cession benefit should be 0 

If the accumulated SAR has been increased, then there will be no change in the retention but the retro sum at risk and unplaced amount if any for the transaction will be updated

The above is applicable for all transactions including transactions where the immediate previous transaction is OLDBUS

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Other deductions not calculated for other transaction in facultative standalone retrocession

Solution:

Any Other Deduction that is defined as a basis if Gross or Net Premium should be calculated on an Other transaction when there is a first year or subsequent year basic or extra premium that is calculated on the Other transaction

The above will be applicable to manual standalone retrocessions and retrocessions that are created through the RPO

Premium on a manual facultative standalone retrocession should never be defined as retro share of original- so the implementation of SE-922 will not be applicable to manual standalone retrocessions

When the premium basis is retro share of original then any ACIs on the inward cession transaction should be retroceded in the ceded percentage

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Incorrect ACI's calculated for LAPSE transaction in facultative standalone retrocession

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Issues with transaction age and commission calculations on Other transactions

Solution:

The transaction age for any transaction should be calculated based on the Age definition basis on the PM condition and the transaction effective date of the transaction

 ACIs for any transaction (Other, Increase, Decrease) that has an effective period that falls within the renewal frequency of the cession benefit should be calculated on pro rata basis

Whenever there is a change in the SAR/ SAR retroceded for the transaction and any premium ACI is dependent on the SAR then the ACI should be calculated for that transaction. All other ACIs that are to be calculated on the basis of the premium ACI should also be calculated for the transaction

Declination Reason

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

ACI’s not calculated when we create ‘OTHER’ Transaction and Deductible Range is part of the LUT

Solution:

When the premiums or commissions are defined using a table that uses Deductible Range then the commissions and premium ACIs should be calculated using the value in the field Deductible for any ACI calculations. When the premiums are calculated on the Other transaction, then any commissions or Other Deductions that are based on gross or net premiums should also be calculated using the rates as defined on the commissions or other deduction tables where deductible range is one of the parameters

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System is allowing to create a cession when we enter premium term and benefit term in days and do not select short term flag

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System Abends when editing the field on the UD window on the Cession Benefit.

Solution:

1. It should be possible to add UDFs on the cession benefit level both manually and through the loader
2. It should be possible to edit the UDFs on the cession benefits manually and overwrite existing UDF fields through the loader when the same cession benefit is referenced
3. The UDFs on the cession benefit level should be reportable
4. The UDFs on the cession benefit level should be supported through MTK

Declination Reason:

Workaround:

Root Cause:

Problem:

RCPO run is Calculating incorrect ACI's in placements when we have multiple retrocessionaire placement

Solution:

All ACIs on the placement claims should be calculated by applying the retrocessionaire placement % to the retroclaim ACIs

This is applicable when the RCPO picks up more than one claim status or when the RCPO picks up each claim status separately

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when adding a new benefit on a cession that has a lapsed benefit

Solution:

It should be possible to add a new cession benefit on a cession that has only one benefit and that benefit is inactive due to a termination.

This new benefit that is created should be created as a new business transaction. The currency of this new benefit should be the same as the other benefits on the cession. 

Declination Reason:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

In personal details tab, cession fields are not visible in retro claim and on placements
Solution:

On a standalone retroclaim and placements in the Personal Details tab all the fields under Cession with all the details from the linked retrocession cession should be available. These should not be editable

Underwriting details should not be available on the retroclaim

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when running the RPO for Lapse transaction on the migrated data

Solution:

 There is no syntax validation for Instance variable #cededPercentage SicsLfAbstractCessionDetailClass.cnuNewCompleteSyntaxDescriptor(). This should be added now in 22.3 release.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Unable to update Cession Benefit level UDFs since the output pattern only updates the Cession level UDFs

Solution:

**It should be possible to update the UDF fields on both the cession and cession benefit level through the cession loader

When values are mapped to the Cession Benefit UDF fields the cession benefit level UDFs should be updated

When values are mapped to the Cession level UDF fields the cession UDFs should be updated.

When values are mapped to both the above fields then the respective values should be updated on the Cession level and Cession Benefit level

Declination Reason:

Workaround:

Root Cause:

Problem:

 Cession Batch is updated with error related to Adjusted Issue age when loading the renewal transaction

Solution:

The issue age and adjusted issue age should be calculated in the new business transaction based on the age calculation basis on the PM condition. If there is an age loading then the loading should be applied to the issue age and this will be the value of the adjusted issue age

On any subsequent transaction the issue age and adjusted issue age should not be recalculated and updated. The value should be copied from the previous transaction (which will be the new business values always)

Only the transaction age should be recalculated and updated with each transaction and the ACIs that are dependent on age should be calculated using the transaction age. 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 ACI's for other deductions are calculating with incorrect sign on increase transaction of retrocessions and placements

Solution:

All other deductions should be calculated with the entry code sign as per the properties defined on the entry code properties

When the entry code is defined as 'Is Positive on Outward Business' (and the flag 'Is positive on assumed business is not selected' then the entry code will always be calculated and updated with a positive sign on the retrocession cession level and the placement level and will always have a negative sign on the cession level.

When the deduction is defined as the basis of premium and the premium is calculated on the cession (either as an increased premium or a decreased premium) then the deduction should be calculated and updated as per the entry code properties irrespective of whether the premium is increased or decreased. 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Claim ACI

Solution:

Corrected

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

ACIs not calculated for Old Business transactions that are retroceded

Solution:

When the cession is migrated as an Old Business and is created as a New Business transaction on the retrocession:

When the Premium basis on the OCC is Risk Premium with the premium basis defined as a fixed amount, percent, permille or LUT then the premium ACIs on the retrocession should be calculated based on the retro SAR and the PM condition

Any deductions that are defined on the D condition should also be calculated

When the premium basis on the OCC is 'Retro Share of Original'- then the ACIs on the retrocession new business transaction that corresponds with the Old business transaction should be calculated and updated by applying the ceded percentage to the inward cession ACIs

When the lapse transaction (or any other termination is created on the retrocession immediately after the new business transaction (from the corresponding old business transaction on the inward cession) then the refund ACIs for the full recapture transaction on the retro should be created as per the definition on the AC condition of the OCC

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Transaction Number is not updating on the claim statuses and ACI's are not calculating/populating for Adjustment reversal transaction

Solution:

When the transaction number is in use (System parameter 'Transaction number on cessions and claims' is selected) the transaction number for each claim transaction should be automatically updated as previous transaction number +1 for each subsequent status. When the number is manually input on each status the input number should be updated as the transaction number

The adjustment reversal transaction should automatically reverse the ACIs of the reversed transaction and an adjustment reversal transaction should be created for each adjustment reversal that is performed

The reversals should be automatically updated on the retro claims and placement claims

Disable the option Cancel Claim for all claims that are created on cessions that have the Ceded flag

It should be possible to create Ceded Paid statuses even after an Adjustment reversal is done on a claim. 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Claim Reserve Amount is showing in Negative Sign for Ceded outstanding in Retrocession Claim

Solution:

Ceded Claim Reserve should be calculated n the retro claim and placement claims with the entry code sign as defined on the entry code properties for the respective entry code

When the entry code properties 'Is Positive on Outward business' is selected, then the entry code should be created on the retro claim and placement claim with the positive sign 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

RPO does not pick up cession benefits that have expired as on date of RPO

Solution:

The RPO should pick up all active cession benefit transactions that do not have the retroceded date set if the transaction effective date is within the RPO effective date**

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: 

Issues with Summary Account on a Sub SOA technical worksheet

Solution: 

Always default the Accounting period From- To based on the Accounting Year/ Period that is selected on the Summary account. This should happen irrespective of whether the Admin condition on the business has single accounts or not

On the list of open worksheets window- the AP from and AP to date should be defaulted from the Accounting Period From- To of the Summary Account when the worksheet status is Manual with Summary

Declination Reason: 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Retention and retrocession not calculated correctly when the limit condition on the business has been defined with a LUT and the IO have cessions created with different parameters that are part of the LUT

Solution:

When the utilised retention  on the life as on the date of the RPO is > or = the available retention as per the Limit condition on the section then consider the entire available retention exhausted and retrocede the entire sum at risk.

When the utilised retention < the available retention, then calculate the retention as MAX (available retention, SAR) and calculate the Sum to be Retroceded as SAR- net sum retained

Declination Reason:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Incorrect ACI's calculation for Increase and decrease transaction on Retrocessions, Facultative standalone Individual retrocession  and on placements

Solution:

For any increase or decrease transaction on a manual standalone retrocession or facultative standalone retrocession or a retrocession created through the RPO:

The premium ACIs should always be calculated on prorata basis for the effective period of the increase or decrease transaction for the updated retro sum at risk as per the transaction

Any other ACI that is calculated on basis of the premium ( such as commission, other deductions, extra premiums etc) should be calculated on the basis of the prorata premiums that are calculated

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Issues with accumulated sum at risk on Joint life cessions

Solution:

The accumulated SAR on the individual life that is part of the joint life cession should be displayed on the accumulation control window of the IO as per the cession as of date. This is similar to the display of the accumulated SAR for single individual cessions

When subsequent transactions on the joint life cession are loaded  the primary life should never be changed. 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Issues with migrating standalone retrocessions

Solution:

All standalone retrocessions that are not of type Facultative Standalone Retrocessions should be migrated using the object %LfStandaloneIndividualRetroBenefitGroup) in both the export and import process using the MTK loader

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS Abends when we attach a table to the Limit condition of a Quota share or Combined Quota Share/Surplus treaty

Solution:

When Table of Rates is selected on a Combined Quota Share and Surplus Limits table it should be possible to select the following tables and attach them to the Quota Share and Surplus tab without abend

1. Quota Share Table
2. Prop Limits Quota Share 100% Table Cover Limits
3. Prop Limits Surplus Autocover Limit Table

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System is abending when running the retrocession calculation order

Solution:

Reserve transfer is not relevant in Life and hence the functionality implemented in SE-12451 with respect to reserve transfer should be made specific to P&C

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Subsequent transactions created with active status when NB transaction is in provisional status

Solution:

It should not be possible to create subsequent transactions on a cession benefit that has a transaction in provisional status.

It is not possible online and hence the batch should fail with an error message ' Attempting a <transaction status> on a cession benefit with a provisional status

 
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Cession Upload - Inconsistent row count

Solution:

The row count displayed on the batch at any stage should only reflect the number of rows with data in it. 

If there is no data in the row then the row should not be included 

This is applicable to all statuses of the batch and also when the row count is displayed when the data is retrieved before the input file is imported and the saved after linking to a mapping. 

Declination Reason:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

MTK-  Not able to migrate the business when Cut-of lover limits is defined in the Propositional Limits condition of an AB and OCC

Solution:

 The Limit Condition with the Cut off Lower Limits defined should be supported through MTK 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

No options are available to select when we click on table menu icon on Basic Multiple Extras tab of Deductions condition

Solution:

User should be allowed to select a Deduction Table when selecting Table of Rates for Basic Multiple Extras

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Premium term is not updating when benefit term is increased on extended term transaction

Solution:

 The premium term should be updated along with the benefit term when the transaction is extended term

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Abend when entering the year in 'event date' on a preliminary claim 

Solution:

The system should not abend

When the event date type is year the input year should be accepted and not abend

If the year is invalid then the error message Event date field is required but not specified should be thrown

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Incorrect claim expenses calculation on retrocessionaire claims -Ceded claims

Solution:

All claim expenses on the retrocessionaire claims should be calculated based on the retro claim ACI * retrocessionaire percentage

Any update/ deletion on the retrocession claim should automatically be updated on the placement claims

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Transaction number is not updating automatically when creating any transaction on manual standalone and facultative standalone retrocessions

Solution:

When the system parameter 'Allow transaction number of cession and claim' is selected

Update the transaction number on the manual standalone retrocessions and claims by incrementing it by one from the previous transaction number

The field should also be editable to allow any transaction number that is not a duplicate

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect exchange rate when the limits are defined as LUT vs Amount

Solution:

When the Limits are defined as Fixed Amounts OR Surplus Limits table or QS Limits table:

Exchange rates for equivalent values should be calculated using the cession reinsurance benefit start date 

Exchange rates should be calculated using the base currency of the business partner

If the exchange rate is defined as anything other than Daily Rate then existing functionality where no exchange rate is applied should remain

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Batch updated with error when trying to add new benefit and there is a duplicate inactive benefit on the same cession

Solution:

When a duplicate benefit is added on the same cession (duplicate = same benefit covered and same insurance product) and the other benefit with the same details is inactive then the new benefit should be created on the cession without an error

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

ACI's are calculating for Outstanding and valid status on non ceded claims

Solution:

When ACIs are mapped for a claim that is of status Outstanding, Valid or Preliminary the mapped ACI should be ignored and it should never be updated on the claim that is created

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Flat extra premium is calculating on retrocessions and placements even the transaction is fully retained

Solution:

No ACI ( including deductions and basic or flat extra premiums that is defined as a fixed amount) I to be calculated when the sum at risk retroceded is set to 0 on the retrocession transactions 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Additional classification defined in the system parameters is not used as MCOB

Solution:

When the system parameter Use Additional Classification as Main Class of Business is selected :

It should be possible to select ANY additional classification as the MCOB

In LIFE_CHR47 - additional classification 10 (000265) is selected

In LIFE_CEDED- additional classification 1(000051) is selected

There is no rule as to which Additional Classification is to be defined as the MCOB.

The dependencies etc are defined on these additional classifications selected as MCOB will determine the selection of the child values like benefit covered, insurance product, branded product etc on the business.

When any functionality related to MCOB is referenced either when creating the business or creating a cession then this additional classification and its dependencies should be used

Declination Reason:
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Batch is partially closed when Policy number and Cedent cession number are not defined

 Solution:

When there is any missing mandatory field in the batch then the record should fail.

The batch should get a status of Closed only if a cession transaction has been successfully created from the records that have been processed as part of the file

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Row count is displaying incorrectly when loaded the cession batch that is partially rejected using CSV file 

Solution:

Row count on the cession batch to always reflect the actual number of rows that have data which is being processed in the respective sheet that is being loaded when the type of input file is an excel file

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of Function
Added a new option for Estimation Frequency in Multi GAAP/General system parameters, labelled Depend On Each Business

When the new option is selected, the Estimation Frequency on each business will be the same as the Account Frequency set in Administration Conditions.
Supported estimation frequencies with this option are Monthly, Quarterly and Half Yearly.
If no Administration condition exists, or there is no Account Frequency defined in the Administration Condition, the Estimation Frequency will be Quarterly.

System Parameters Affected
Multi GAAP General Parameters for Estimation Frequency

Existing functionality affected
Calculate Period Estimates

 Aim of function

Allow to update Last Projection Year in Period Estimates tab through updatePeriodEstimates webservice.
Added new element named <lastProjectionYear> in Entry Point: urn:SicsWsBusinessEntryPoint/updatePeriodEstimatesInput

System Parameters Affected

None

Existing functionality affected

updatePeriodEstimates web service

Aim of function

The aim of this epic is 

• Improved the UX of the Accounting Classifications window.
• Added support for 'view calculation window' to show syntax color highlighting.
• Improved the UX of the Life Cession window , Life Cession wizard, Insurable objects.
• Fixed SOAP Tester alignments for Windows 10 and corrected 'help' tab with correct screenshots.

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function

The aim of the enhancement is to be able to define the basis of Joint Life accumulation.

When the basis is selected as 'Maximum Sum at Risk', then the individual insurable object on the joint life insurable object that has the maximum sum at risk will be considered for the purpose of accumulation

System Parameters Affected

None

Existing functionality affected

On the P/L condition of the Assumed Business and OCC:

A new selection dropdown option for Joint Life Accumulation Basis with the options  'Primary Life' and ' Maximum Sum at Risk' will be available. 

The selection will be informational on an assumed business

Retroprocessing:

When the Joint Life Accumulation Basis is selected as 'Maximum Sum at Risk' on the PL condition, then the individual insurable object with the maximum sum at risk within the joint life insurable object will be considered for determining the accumulated sum at risk to be used while creating the retrocessions

Aim of function

To be able to calculate the Inward Claim Expenses using a rule of Original Expenses Amount (Account Item) *(Sum at Risk/ Sum insured) 

System Parameters Affected

None

Existing functionality affected

Only on Claims created on cessions that have the Ceded flag selected

• A new flag 'Method 1' will be available on the Claim Expenses tab
• When this flag is selected the claim expenses and the claim expenses ACIs will be calculated using the rule Original Expenses Amount (Account Item) *(Sum at Risk/ Sum insured) 
• Claim Expenses will not be calculated as an account costing item. They will be part of the Ceded Paid account costing item
• It will be possible to create a separate claim expense to each Ceded Paid status
• It will be possible to map any entry code to the claim expenses 
• The currency and the payment due date of the claim expense will default from the Decision Liability tab
• When the Retrocession Claim Processing Order is run, the ceded % will be applied to claim expenses from the inward claim to calculate the Retrocession Claim Expenses
  

Aim of function

To be able to add a total of 20 String fields on the UDF for cessions and claims

To be have 10 informational fields on the Group Information tab 

System Parameters Affected

None

Existing functionality affected

User Defined Fields

It is now possible to add 20 String fields on the following User Defined Layouts

Cession 

Cession Benefits

Claims

Cession- > Other Information tab

A total of 10  informational fields in the Other Information Tab are now available

Aim of function

The aim of this function is to be able to use the values  'Deductible' and 'Payment Ratio' in a Premium Calculation Rule 

System Parameters Affected

None

Existing functionality affected

A fields 'Deductible' and 'Payment Ratio' that are available on the cession benefit transactions can be added to a Lookup Table

Aim of function

The aim of the function is to be able to view the accumulated sum at risk on the cession benefit transaction level and have this value updated on each transaction where applicable

System Parameters Affected

None

Existing functionality affected

The following functionality will be applicable only when the System parameter ‘Sequencing based on Original transaction date’ is selected

A new field On the Other Information tab labelled ‘Accumulated Sum at Risk’ is now available

The accumulated Sum at Risk on the life, for the benefit covered on the cession will be recalculated on each transaction based on the Original Transaction Date

The recalculated value will continue to be updated on the field 'Accumulated Sum at Risk' in each transaction with the values as on the Original Transaction Date of the cession benefit transaction

Aim of function

The aim of the function is to enhance the CreateLfCessionBatchRequest webservice such that it will support to pass Mapping document. 

System Parameters Affected

None

Existing functionality affected

As per the existing functionality, mapping reference element is not available to define the mapping name when we generate the new skeleton of cession batch. Therefore the cession batch used to pick the unique mapping that is linked with the input file 

 Aim of function

A new API Interface is to be created which would be using the Column Spreadsheet to Create Technical Worksheets for both SICS Life and SICS P&C.

System Parameters Affected
N/A  

Existing functionality affected

This enhancement is providing the end user to create and close the Technical Worksheets through a API interface in addition to the existing manual upload Technical Worksheet from Column Spreadsheet process. Below are the new tags that were implemented as part of this enhancements,

Create Technical Worksheet with Column Spreadsheet 

• Operation: <ImportTechnicalWorksheetFromSpreadsheetInput>
• Element: <fileName>,<mappingName>

 Aim of function

The aim of the function is to add the Reinsurer Signature Date and Projection Basis while creating a business or updating a business through Webservices

System Parameters Affected

None
  
Existing functionality affected-

•  Reinsurer signature date: Prior to this enhancement Cedent Signature and Reinsurer signature date elements were not available under insured period  element. The reinsurance and cedent signature date elements are now available while creating business through webservices

• Projection basis:   Prior to this enhancement projection basis element is not available in createLfBusiness Skelton. As part of this enhancement Projection basis element  is now available while creating business through webservices where the user can input projection basis as 'Yearly , Ultimate or none'.  

Aim of function

The aim of the function is to include the data on the Joint Life Data tab in reporting

System Parameters Affected

None

Existing functionality affected

None