Problem:

SICS abend - when in the technical worksheet by clicking on the calendar icon for registration date and select future date and tab out

Solution:

 The selected value on the calendar icon should be accepted. Any validation of the selected date should be done after the date has been accepted in the field. The system should not abend

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem

Unable to view LUT from multiple table in view mode

Solution

On right click, you should see the menu similar to what you see when you right click on the table in edit mode. Only the option View should be avaialable and selecting this should open the respective table

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

On the SAR calculation Rule to include Benefit Covered and Insurance Product in the Variable >> Classification

Solution:

In the system parameters Add Benefit Covered and Insurance Product as selectable variables under the calculation rules under Variable- Classification for all Life calculation rules

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Basic premium is not calculating when “Multi Prem Rate or Value” option is selected on PM condition of business and one table is attached

Solution:

When the option Multi Premium Rate table is selected and only one LUT is attached then give a validation error message 'Please attach more than one table when Multi Premium Rate table is selected'

When there is more than one rate table attached and the Calculation Rule is 'None' then give the validation error message 'Calculation Rule is mandatory when Multi Premium Rate table is selected'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Extraction of Life Claims transactions.

Solution:

Alias table and joins added-

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Due to incorrect date format in the reject file row count is displaying incorrectly when loading a rejected CSV file

Solution:

The reject file that is created from the upload and processing of a csv file should have the same date and other formats of all the columns and fields 

The reject file should be uploaded as it is to process the rejected records without having to make changes to the file or mapping

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, csv file or text file

++

 
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

1. RCPO is not calculating Interest and taxation fields on Placements claims.

2. Expenses are not calculating on the expenses tab of placements claim when we have multiple retrocessionaire in OCC - Non ceded claims.

Solution:

Similar to all other ACIs, Expenses and Expense ACIs should be calculated on all the retro placements in the retrocessionaire placement percentage when the RCPO is run or when the expenses are updated on the retrocession 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Cessions are not creating as Informational even the reinsurance start date is defined as future date 

Solution:

Do not allow new business transactions or old business transactions on cessions with a future date. Throw an error message <Reinsurance start date cannot be a future date>

Informational renewals for future dates should still be allowed as per the current functionality with the ACIs set to Suspended

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Transaction number field is not available on create window of manual Standalone Individual Retrocession and Facultative Standalone Retrocession

Solution:

When the system parameter 'Allow Transaction number of cession and claim' is selected the transaction number field should be available while creating a manual standalone retrocession and facultative standalone retrocession cession.

The functionality should be similar to that of an inward cession

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

RCPO Run is creating only one retro claim, even the inward cession is having multiple retrocessions,

Solution:

When the RCPO picks up a claim that is linked to a cession benefit that has more than one retrocession linked to it, the outward claims that are created should also have the same number of retroclaims created on the inward claim

The ceded % of each retrocession cession should be applied to all the accounting items on each of the respective retro claims

On each retro claim, the placement claims should be created based on the retrocessionaire placement percentage

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Details are not copied correctly in Individual Retrocessions when we perform Other transaction on Inward cession

Solution:

 Any updates made to the inward cession transaction should be copied to the retros created during the RPO run

If there are any calculations/ validations that are applicable to the retrocession processing due to the changed values they will need to be done on that respective retrocession transaction

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

UDF Fields are not overwriting on Cession Level, when a new Benefit is created, with a different UDF data on the same Cession. 

Solution:

When a new cession benefit is created on the same cession with different values in the UDF for cession level, then the previous UDF values on the cession level should be overwritten with the UDF values from the latest cession benefit that is uploaded

No changes should be made to an existing cession benefit level UDF based on the cession or cession benefit level updates on another cession benefit that is loaded on the same cession

Declination Reason:

Workaround:

Root Cause:

Problem:

Liability amount getting decreased based on the Ceded Percentage when Claim Status is updated from Ceded Outstanding to Ceded Paid

Solution:

When the RCPO is run, use the calculation variable (Inward SAR/ Retro SAR) without rounding it off while calculating the ceded percentage to be applied to the claim figures (claim liability, interest, taxation, expenses and any other ACIs)

When the historical claim flag is selected and the value in the ceded percentage field is not equal to the calculated ceded percentage (Inward SAR/ Retro SAR rounded off to 6 decimals), then use the value in the field ceded percentage to calculate the retro claim figures

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Other deductions are calculating incorrectly when the calculation depends on Net Premium

 Solution:

Irrespective of the ceded flag or the sign on the entry code all premium basis that are defined as a type of 'Net Premium' (All Net Premium, Basic Net Premium, Extra Net Premium) should be calculated as the respective premium entry codes minus the respective commission entry codes. The Other Deductions should be calculated on this value by applying the defined percentage or permille rates

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System Abends when creating a valid claim status, when inward business is having SAR Calculation Rule.

Solution:

There should be no Claim Liability on the claim with a Preliminary, Valid or Outstanding status. 

Therefore there should be no comparison between the Claim Liability and SAR for a Preliminary Status

For a Paid status:

Claim Liability should always be defaulted from the Notified Reinsurer's Liability field on the inward cession. If a value is mapped through the loader or overridden then this value will be considered as the Claim Liability

It should never be possible to create a claim without a value in the Claim Liability field

On the Paid status, the SAR calculation rule should be applied for comparison as per the defined rule

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Individual IO Details are getting updating in Renewal transaction on Inward cession when created through the loader

Solution:

The details on the IO Information tab should never be updated during a renewal transaction since it is not possible to update the values when creating the values manually. 

All fields that cannot be updated during a manual renewal transaction should not be updated when the transaction is loaded through the cession loader even if there is an update to those fields

Any mapped values should be ignored and the details from the immediate previous transaction should be copied to the renewal transaction

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The column names on Test values tab are not in same order as the output pattern on Transformation tab of Mapping

Solution:

When the user goes to the Test Values tab on the cession mapping the values in the upper container should always be displayed in the same order as the input file that has been uploaded

This is applicable to both the first upload and the upload of the reject files

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

6 decimals always considered when the system parameter 'Cession SAR in Decimals is selected'

Solution:

When the system parameter 'Cession Sum at Risk in Decimals' is selected then the number of decimals on the cession and retrocession should always be as per the selected value. If it is blank or 0 then the cession SAR should always be rounded off to 0 decimals**

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 MTK- Policy year is not updating correctly for subsequent transactions in migrated facultative standalone retrocession 

Solution:

The policy year field should be migrated through MTK for all types of standalone retrocessions for all effective periods that are migrated

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Transactions allowed without warning when renewal points are skipped resulting in incorrect ACIs

Declination Reason:

When any transaction is created and there are missing renewals in the current effective period or earlier effective periods, always through the message LCH153 Renewal points exists which have been missed on this cession benefit. Do you want to continue?

The message currently appears only when one renewal is missed. It does not appear after that

In the loader, always answer this message as Yes

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Transaction code is displaying as 'None' after creating expiry transaction on manual standalone Retrocession

Solution:

For any expiry transaction or any termination transaction the timestamp of the termination transaction should be taken as the expiry date and the minutes and seconds should be 23.59.59.000000

It should not be possible to create a reinstatement transaction after an Expiry transaction. The existing message 'Effective date greater than the benefit term' should be thrown when you try to reinstate an expired benefit

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System is throwing incorrect validation when values are not defined for mandatory classifications when creating the business

Solution:

When a classification item Benefit Covered, Insurance Product or that has been marked as 'Is Mandatory'= Yes as per the classification rules 2 in the system parameters is not entered in the Classifications screen of the create new business window the error message '<Classification item> is mandatory and has not been specified' should appear instead of the current error message related to incorrect dependencies

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Group Cession with Individual flag should not be editable on subsequent transactions

Solution:

The flag 'Group Cession without Individual Member list should not be editable in subsequent transactions both manually and through the loader. If the flag is updated in the mapping, it should be ignored on any subsequent transactions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Cession Benefit Level UDF window is getting blank when a DATE field is added in the Benefit UDF Layout

Solution:

Do not allow creation of Date fields on the Cession Benefit Layout
If a date field is added then it should be ignored and not displayed on the layout. All other fields that are valid Cession Benefit level UDF fields should be displayed and the layout should not be blank of there is an invalid date field

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

RPO is not running when cession is having Full surrender transaction.

Solution:

A full surrender transaction should be considered similar to any other termination transaction and a Full Recapture should be created on the retrocessions with the ACIs being reversed as per the what has been defined on the AC condition 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Net sum retained is calculated incorrectly on all termination transactions other than Lapse

Solution:

**When the system parameter 'Method of retrocession sequential in excess of retention is selected'.

For ALL termination transactions

Copy the values from the Net Sum Retained, Net Sum Retroceded and Unplaced Amounts fields of the transaction from which the termination transaction has been created to the Retrocession Information tab of the termination transaction

These amounts will be considered 'released' and be made available for the next active transaction for the insurable object, for the benefit

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Output Pattern does not have the field name 'Group Cession without Individual Member list'

Solution:

New cession loader output pattern Eg 'NO_MEMBER_LIST' of type boolean
When flagged yes the flag 'Group without individual member list' on the cession benefit should be flagged as yes
It should not be possible to update this field on subsequent transactions, if flagged for any transaction other than New Business or Old Business it should be ignored

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Output Pattern does not have the field name 'Short Term'

Solution:

Cession output pattern field SHORT_TERM to be available
Type boolean
When flagged Yes the flag Short Term should be flagged yes on the cession transaction
This should not be updated on subsequent transactions on the cession benefit and if mapped, it should be ignored

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Flat or per mile Extra for reason 'Above Free Cover Limit' is not calculating correctly on the Retrocessions and Placements 

Solution:

When the reason for loading is 'Above Free Cover Limit' - for all loadings on the inward, use the ceded percentage to calculate the loading on the outward. No further recalculation of any loading is to be done.
This should happen for both Original and Risk Premium basis

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

AccYr/Period is blank on the 'Summary Account' Tab while doing 'Import Sub SOA file'

Solution:

Always default the accounting year and period on the Summary Accounts tab from the Actual Accounts tab when the Actual Accounts are created first and the summary is generated from the actual accounts

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System is retaining/retroceding wrong amount if Quota Share LUT table is attached on OCC limit condition when the setup is not in the 'standalone' environment

Solution:

Irrespective of the Retrocession basis, when the Quota Share Limits table is attached to the OCC, the values from the LUT should be used to calculate the retention and sum to be retroceded. The Amount field should be considered as the Quota Share amount and the Percentage field should be considered to calculate the retention

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend while creating NB transaction through cession batch when we dont define Transaction code in input file

Solution:

If there is no transaction code defined and the cession does not already exist, it should always be created as a new business transaction and the system should not abend

If the active cession benefit with the same benefit covered and insurance product already exists the new cession that is loaded should fail with the message 'Benefit with the same insurance product already exists...'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When creating RNWL txn SAR for all the NB txns to be accumulated when there are multiple cessions on same IO with same effective date

Solution:

Update the accumulated SAR field sequentially based on the order in which the cession transactions are created when there are multiple cession benefit transactions with the same IO, BC and same original transaction date

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Ceded percentage field is updating with incorrect value on Inward and retro claims when there is more than one retro linked to the cession

Solution:

When the ceded percentage is populated from the cession on the claims (also when the historical claim flag is selected and the ceded percentage on the claim is not mapped) then always use the respective cessions' ceded factor on the ceded percentage field on the claims
Do not populate the value always with only the first cession's ceded factor

On the inward claim in such cases populate the total ceded percentage from the ceded factor of all the inward claims in the field ceded percentage

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The status of claim ACI's on placement level is incorrect.

Solution:

 When all the ACIs are included in the accounting and have been picked up and created as worksheet entries the status of the ACIS should be Included on the retro claim and Placement claim levels

When the claim has entry codes that are defined under the entry code category Cash Claim they should be picked up ONLY when the description of account is 'Cash Claim Account'

When the claim has entry codes that are defined under the entry code category Loss Reserve they should be picked up ONLY when the description of account is 'Claim Reserve'

When the claim has entry codes that are NOT defined under the entry code category Cash Claim or Claim Reserve they should be picked up ONLY when the description of account is 'Regular Account

If there is a claim that has a combination of entry codes, until all the entry codes have been picked up by an RCO and created as bookings on the worksheet the accounting status should be Partially Included

If the RCO has picked up all the ACIs on the claim then the accounting status should be Included

If the RCO has not picked up any ACI on the claim (maybe because there is only cash claim entry codes but the description was regular) then the accounting status of the ACIs should be Released

This is applicable to all types of entry codes (Regular Account, Cash Claim, Claim Reserve)

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Gross premium and deduction not calculated then also deductions defined on Net premium calculated for Extended term transaction

Solution:

Any deduction that is defined on a premium basis (net, gross) should be calculated only if a premium is calculated for that transaction
If there is no premium calculated, no deduction that is to be calculated using the premiums should be calculated

This is applicable to ALL transactions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System is creating Renewal transaction when we only define transaction effective date in input file and the date is not the next renewal date

Solution:

Whether it is individual transactions or several transactions in the same input file batch:
When there is no transaction code
and the transaction effective date is not a renewal date, then the transaction should be created as an Other transaction
and the transaction effective date is the next renewal date, then the transaction should be created as a Renewal transaction

The above is applicable to both when the Ceded flag is 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:

On retro claim and Placements, Expenses ACI's are deleting when we add new claim status with expenses on Inward claim

Solution:

Any claim expense that was already created on the retroclaim and placement claim should remain and be applicable to that particular status/ effective period. On running the RPO the previous claim expenses should not be deleted

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Incorrect sequencing of Individual Accounts on A condition  when it is an open ended treaty

Solution:

Always create single accounts based on the First Account As of Date and the calculation frequency selected on the Admin Conditions
This is applicable for both open ended insured periods and closed ended insured periods

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Incorrect messages, properties file updated

Solution:

Update the batch with the correct error messages when the batch fails
In the below scenario the message should be 'Cession not found'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

RCPO is not considering first claim status, when we run RCPO to create retro claim for only first claim status

Solution:

 The RCPO should pick up all the claim statuses that have the payment due date that is within and equal to the period end date defined on the RCPO and do not have the retroceded date set. Each claim status should be processed as retroclaims with the corresponding statuses using the ceded percentage of the effective periods of the cession within which the claim event date falls in

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System is allowing to link OCC to PP with different main currency

Solution:

If the OCC main currency or additional currencies are not a subset of the PP's currencies then throw a validation error 'The currency/ies of the selected Business is not a subset of the Program's currencies'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Ceded percentage field is updating with incorrect value on Inward cession benefit for Other than new business transaction 

Solution:

 The Ceded Percentage on the cession benefit transaction should always be updated based on the total ceded factor/ percentage that has been calculated for that transaction after the transaction has been processed through the RPO

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Various issues with loading more than one benefit with a different reinsurance start date

Solution:

 If the benefit reinsurance start date is mapped with a value earlier than the reinsurance start date then the batch should fail the record with the same message as per online functionality. Benefit Reinsurance start date cannot be earlier than <reinsurance start date>
 
The current message related to branded products should not be thrown

When there is an an ACI mapped to the cession benefit then the renewal frequency is mandatory. If a cession is loaded without the renewal frequency and there is an ACI mapped (i.e it is to be created in an active status) then fail the record with the error message Renewal frequency is mandatory but has not been specified

If there is one provisional cession benefit without a renewal frequency and another benefit is loaded with the same benefit reinsurance start date or another benefit reinsurance start date and the renewal frequency is mapped on this cession, then default the renewal frequency from the later cession benefit to the cession level across all effective periods

It should never be possible to have one cession benefit with a renewal frequency and one without

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect validation for Renewal Frequency field and transaction age on Underwriting Cession main window

Solution:

Do not check for Renewal Frequency on the Underwriting cession.
On clicking the Main and SAR buttons the error message related to renewal frequency should not appear
No calculation for transaction age is to be done. Adjusted issue age should be calculated on UW cession based on the DOB of the insured and the age calculation basis on the PM condition and reinsurance start date. Transaction age should be copied from this age
When the cession is converted to an actual cession all calculations and validations as per actual cessions is to be done at the time of setting the cession benefit to active

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect retrocessions when there OCCs linked to the PP have different calculation frequencies in the PM condition

Solution:

When there is more than one OCC on a PP the calculation frequency in the PM and SR conditions should be consistent on all the OCCs

If an OCC is added through the option Create New Treaty from Outline and the OCC that is added has a PM and SR calc frequency that does not match the previous OCCs then throw an error message 'Calculation frequency on SR and PM conditions on all the OCCs linked to the PP should be consistent'

If the OCC is added through the Add Treaty Outline and then realised, then when the PM condition on the OCC is updated the message ' 'Calculation frequency on SR and PM conditions on all the OCCs linked to the PP should be consistent' should be thrown if the SR or PM condition on the agreement section is inconsistent with the other OCCs linked to the same PP

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Transaction number is not defaulting to latest active transaction number when creating adjustment reversal on cessions. 

Solution:

 When an Adjustment Reversal transaction is created the defaulted transaction number should be the transaction number on the immediate previous active transaction

 Reinstatement transactions should always be defaulted to be created based on the immediate previous termination transaction. Adjustment reversals should not be considered as a termination and no reinstatement of adjustment reversals should be possible

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Adjustment reversal transaction is not creating automatically on retrocessions in the linked retro setup

Solution:

 When an adjustment reversal is created on an inward cession transaction the corresponding retro transaction should also get an automatic adjustment reversal transaction

This is applicable to all retrocession basis when the system parameter ' Transaction number on cessions and claims' is selected

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System Abends when Using LUT table with some parameter on limit Condtions and creating cession when the same parameter is missing.

Solution:

When there is a LUT attached to the Limits condition (Surplus Retention, Surplus Autocover, QS Limits) and the cession does not have a value correspodning to the LUT parameters then the system should not abend. The validation error message 'Missing < column name> should appear and the cession should not be created/ updated
This is applicable to both manual cessions and cessions created through the loader

When the parameter is missing and the RPO picks up the cessions then the cession should be part of the failed assignments with the No Retention specified error message

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Batch is getting updated with error while creating claim when Life ID is created with upper case in a cession and lower case in a claim mapping.

Solution:

When the IO is being referenced for any claim transaction or any cession transaction the identifier should not be case sensitive. 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Retroceded Date not updated on Lapse transactions

Solution:

Update the Retroceded Date from the effective date of the RPO on the inward cession transaction for any termination transaction that has been picked up by the RPO even if a full recapture has not been created since the SAR was fully retained

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Entry Code missing validation error message is NOT throwing on 'Import Technical Worksheet From Column Spreadsheet' process

Solution:

If any of the mandatory fields that are required while creating a technical worksheet are not available in one or more rows of the entry code the import should fail in the Validate stage itself and the error message Missing < missing mandatory field> should be thrown and the file should not be processed. 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

First rejected records.csv file got overwritten by the second rejected records file when cession batch run result into 2 sub-batch's creation

Solution:

Create one Reject file for each sub batch created and append the file name with the batch id

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Negative retro sum at risk

Solution:

The sum at risk, net sum retained, gross sum retroceded or any value on the cession and retrocession cession should never be negative

When the SAR is below the retention on subsequent transactions the retro SAR should be updated as 0 and the retrocession cession benefit should continue in an active status

When the SAR is above the retention on any subsequent transaactions the retro SAR should be calculated upto the maximum available capacity and any remaining unplaced amount should be listed as an unplaced amount

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Unlink mapping and Replace mapping options are enabled for closed batch

Solution: 

 Disable the options Unlink mapping and Replace mapping for a batch with a closed or inactivated status

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Cession Benefits without ACI missing in reports.

Solution:

Outer Joins added.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The transaction number remains same on all renewal transactions created through cession renewal order

Solution:

When renewals are created through the cession renewal order or a fac retrocession renewal order and the transaction number is applicable, then each renewal that is created should be created with the transaction number of the previous transaction + 1

When the Calculation Schedule is set on the NC conditions and automatic renewals are created on the cession once the retrocession is done (both actual and informational renewals) each automatic renewal should get the transaction number as previous transaction number + 1

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System is allowing to create claims with event date equals to the cession benefit termination transaction date

Solution:

When the claim event date falls within a cession effective period that is inactive, the validation message The cession benefit is inactive do you want to continue should be answered as No in the loader by default and the record should fail

This is applicable to both ceded and non-ceded claims

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System is allowing to take correspondence date before event date in a claim

Solution:

 
 When the claim is not a Ceded Paid claim the correspondence date should always be later than the claim event date. The message 'The Correspondence Date field is smaller than its minimum allowable value (Event Date)' should be thrown

For a Ceded Paid claim or a Ceded Outstanding claim there should be no validation 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 System abends when creating adjustment reversal transaction on Standalone/ Facultative standalone Individual retrocession

Solution:

 Adjustment Reversals should be possible on manual standalone retrocessions similar to inward cession adjustment reversals when the system parameter 'Allow Transaction number on cessions and claims' is selected. The system should not abend

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Able to create adjustment reversal on an inactive transaction

Solution:

 Adjustment reversals should be allowed only on active transactions.
It should not be possible to create and adjustment reversal transaction on any termination or a reinstatement
 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Additional Retrocession is getting created when we run RPO for termination transactions using PP that has multiple OCC's

Solution:

 When there is a termination transaction picked up by the RPO the existing retrocession transaction that corresponds to the inward cession's termination should be set to inactive with a Full Recapture transaction and the ceded percentage should be set to 0. No additional retro should be created 

This should happen for each retrocession that is linked to the inward cession when there are multiple OCCs retroceding that inward cession transaction

On reinstatement all the linked inactive retrocessions that were created as full recapture should be reinstated

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Issues with subsequent transactions when the OCC has a limits table attached

Solution:

 When the parameter available on an LUT that is required for validating the retention or autocover limit on the OCC is missing the RPO should not abend. The record should be listed in the failed assignments with the message 'No matching value found for <missing parameter>

When the retention or autocover limit is to be validated based on a lookup table then this validation and recalculation of retention and limits should be done for all subsequent transactions (similar to what happens when there is no LUT and the retention and autocover limits are defined as an amount)

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Ceded Percentage is not calculating for Reinstatement Transaction 

Solution:

  Ceded percentage/ ceded factor on the reinstatement transaction should be copied from the transaction that is being reinstated. 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Limits amount on Capped Quota Share Business is recalculating, when we input SAR more than Autocover Limit on the Cession. 

Solution:

The limits on the Capped Quota Share business should never be calculated or recalculated using the retention percentage

The same amounts and percentage values entered on the condition should remain once saved. They should never be updated when the SAR is validated

When the inward cession or manual standalone retrocession is validated use the value in the field Available Reinsurance to validate the gross sum reinsured and throw the message 'The Gross Sum Insured is greater than the Auto cover limit < Available Reinsurance> value when the GSR is greater than the Available Reinsurance

When the RPO is processed and the sum to be retroceded exceeds the Autocover limit then the amount should be listed as unplaced

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Benefit reinsurance start date is not updating in retrocession and placement level

Solution:

 Copy the benefit reinsurance start date from the inward cession to the retrocession cessions and placements

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
 Connection deleted when mappings are updated to a new revision

Solution:

When the mapping is updated to the latest version of the output pattern all existing connections should remain. Any existing connection should continue to point to the object that it was refrencing to  irrespective of any change in the name of the connection

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Start date and Expiry date fields are displaying with incorrect values while attaching PP manually on a cession

Solution:

 The start date and expiry date of the cession that is being retroceded should be displayed during the manual retroprocessing

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System is considering wrong status for ACI outside Effective Period from Retrocession Cession Order

Solution:

Cession and Retrocession Cession Order should ONLY pick up cession and claim (retrocession and retroclaim) ACIs that have As of Date that fall within the From and To dates of the RCO

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 System abends when creating renewal transaction without defining the transaction number through loader

Solution:

When there is no transaction number defined the number should default to 1 for New Business and for any subsequent transactions it should be previous transaction number + 1

The system should not abend

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Reporting date parameter is missing from the Cession Batch creation webservice SOAP request

Solution:

Reporting Date should be added as an element in the create cession batch webservice

When the batch is created and the system parameter ' Use Reporting Date on Cession Batch' is selected this field is mandatory

The webservice should fail with the existing online message 'Reporting Date is mandatory' if not mentioned

When the reporting date is available in the soap and the mapping is generated the input block should contain the field reporting date (as per existing functionality)

When the webservice is executed and an existing mapping is linked, the reporting date link should remain as per the attached mapping

When the system parameter is not mandatory, the webservice should run with or without the reporting date input without an error 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Entry Code for reserves are not picking up correctly in worksheet while running Cession Order for Claim ACI's

Solution:

All entry codes that are defined under the entry code category Reserves should be picked up when the RCO or CO is run with the description of account as 'Regular Claim Reserve' or 'Supplementary Claim Reserve'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

 Net sum retained and total sum retroceded are calculated incorrectly when the reinsurance product is changed on an OCC 

Solution:

When the reinsurance product on a business (AB or OCC) is updated from a copied business or newly created on a fresh business:

 Quota Share treaty only- only the retention and limits that are available on the Quota Share only will be applied while validating the retention and limits for both fixed amount and table

Surplus - only the retention and limits that are available on the Surplus related tabs only will be applied while validating the retention and limits for both fixed amount and table

Capped Quota Share -only the retention and limits that are available on the Capped Quota Share related tabs only will be applied while validating the retention and limits for both fixed amount and table

ONLY if the product is Combined Surplus and QS - first perform all the calculations based on the Quota Share tab, then perform the calculations on the Surplus tab - both fixed amounts and table

 If a business is copied and the product is changed- update the L condition to reflect the tabs relevant to the product on the section

Reset the values on the condition to 0

If there is any other value from the source business still available on the copied business they should be ignored

If a QS business is copied and hte product is changed to combined QS and Surplus- then retain the QS limits from the source business on the L condition

If a Surplus business is copied and the product is changed to combined QS and Surplus- then retain the Surplus limits from the source business on the L condition

If a combined QS business is copied and the product is changed to either surplus or QS then retain the relevant values from the source business in the L condition 

For a Capped Quota Share business -there should be no details pertaining to Quota Share or Surplus available on the L condition once the reinsurance product is changed

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System abends when selecting 'Show All Cessions' flag on IO accumulation window without defining calculation at date

Solution:

The date for Show All Cessions on the accumulation control window should default to the current date when the window is opened

When the date is changed manually the manually changed date, if valid should be used

If the date is deleted then it should default back to the current date. The date field should never be allowed to remain empty

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Getting abend while performing transaction reversal on Ceded Outstanding claim
Solution:

The Payment Due Date for the reversal transaction should be defaulted from the source transaction when a Transaction Reversal is done

It should be editable and if edited, the edited date should be saved

This is applicable to both manual and claims created through the loader

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abend when we run RCPO due to payment due date validation

Solution:

For ceded paid, ceded outstanding claims:

the RCPO should pick up claims that have the payment due date that falls within the period end date on the RCPO

The retro claim should be calculated with the payment due date that is equal to the payment due date on the RCPO

For Paid, In Payment and Special Paid claims 

the RCPO should pick up claims that have the payment due date that falls within the period end date on the RCPO

The retro claim should be calculated with the payment due date that is equal to the payment due date on the RCPO

When the retroclaim is created then all the previous statuses on the valid, paid, in payment claims that are prior to claim status that is picked up should be created on the retro claim

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
RCPO is not creating retro claim, if lapse transaction present on the inward cession.

Solution:

 The retro claim should be created if the claim event date falls within an effective period of the retrocession that is active

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function

The aim of this enhancement is to be able to open Underwriting cessions from the Quick Search and Recents and from Bookmarks

System Parameters Affected

None

Existing functionality affected

It is now possible to 

1. Open Underwriting Cessions from the Recents
2. Open Underwriting Cessions from the Quick Search on the Desktop
3. Open Underwriting Cessions that are linked to Notifiers
4. Open Underwriting Cessions that are added to Bookmarks

Aim of function

The aim of the function is to create a 'Supplementary Transaction' on a cession that is considered as a Group Cession and process and link an actual individual informational cession to the Group Cession 

System Parameters Affected

None

Existing functionality affected

On cessions where the flag 'Group Cession without Individual Member List' is selected:

1. A new transaction of type 'Supplementary Transaction' is available for selection

2. When this transaction is created, an informational individual cession can be linked to the cession that is considered to be the 'group level cession'.

3. This individual informational cession will have the details of the actual member/ insurable object and the premium and other ACIs for this informational cession is updated and claims can be linked to this individual informational cession

4. It is possible to create several Supplementary Transactions to the 'Group Level' cession benefit.

5. When the Retrocession Processing Order is run the following happens:

• The number of members in the group is reduced by 1 for each Supplementary Transaction on the inward cession
• The retrocession premium is is adjusted based on the formula (previous premium * (1/previous number of lives))

Aim of function

The aim of this function is to be able to link facultative standalone retrocessions to an inward cession and run the Retro Claim Processing Order to include the Facultative Standalone Retrocessions also

System Parameters Affected

None

Existing functionality affected

On the inward cession:

It is now possible to attach a Facultative Standalone Retrocession manually from the Retrocessions tab for the entire sum at risk to be retroceded on facultative basis or for the Unplaced Amount that is calculated after the RPO is run

 
On the Cession Benefit- Retrocession Tab a new field 'Fac Total Sum Retroceded' is available

All transactions made on the inward cession will be automatically processed on the linked facultative retrocession

Note:
Changes in the SAR and the recalculation of the retro sum at risk will not be supported on the facultative retrocessions as of now.

This enhancement will not impact manual Facultative Standalone Retrocessions that are not linked to an inward cession.

Retrocession Claim Processing Order

1. A new flag 'Include Facultative Retrocessions : When this flag is selected, all facultative retrocessions that are linked to the inward cession along with the retrocession cessions linked to the PP will be considered during claim recovery
2. Include OCC in the RCPO: It is possible to run the RCPO with the OCC only. When this is run, the RCPO will process the claims that are linked to cessions that have only a facultative standalone retrocession attached to it and process the claim recovery in the retroceded percentage

Aim of function

The aim of the function is to improve the performance of the Retrocession Claim Processing Order by introducing new filters and critera so that only the relevant claims will be picked up during the processing

System Parameters Affected

None

Existing functionality affected

The Retrocession Claim Processing Order has the following options 

1. An Assumed Business can be added to the retro claim processing order so that only the claims linked to this business will be picked up for retro claim processing
2. It is possible to filter the claims based on the Benefit Covered and Insurance Product so that only the claims as per the filtered criteria will be picked up for retroclaim processing
3. Any claim that is linked to a cession benefit transaction that is fully retained will not be picked up by the order for retroclaim processing

Aim of function

The aim of the function is to be able to filter cessions based on parameters like Benefit Covered, Insurance Product of any additional classifications in the RPO so that specific batches of cessions can be processed, thereby improving performance

System Parameters Affected

None

Existing functionality affected

For all the classifications on the RPO it is possible to select specific classifications and process cessions that pertain to only that set of classifications

However, it is recommended that the filters are used with classifications that will not impact the accumulation when the cessions are picked up and processed sequentially. 

Aim of function

The aim of the function is to be able to attach a Capped Quota Share Lookup Table to the Limits condition of  a business where the reinsurance product is Capped Quota Share and use this to process and validate cessions and retrocessions

System Parameters Affected

None

Existing functionality affected

A new type of Lookup Table Capped Quota Share Lookup Table is available

The table has three Rate/Amount Headings for the Quota Share Percentage, Capped Retention Amount and the Overall Limit

On the Business where the Reinsurance Product is Capped Quota Share, on the Limits condition, in addition to the existing type 'Amounts', a new option 'Table of Amounts' is now available

When selected, it will be possible to attach a Capped Quota Share Limits table to the Limits condition

 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 this epic is 

• To Improve the UX of the Life Claims Screens.
• To Improve the UX of the Life Cession Screens.

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function

The aim of this function is to be able to handle transactions with a status of 'Old Business' similar to transactions with a status of 'New Business' during retrocession processing for the purpose of premium calculations

System Parameters Affected

None

Existing functionality affected

On the PM condition of the OCC:

A new flag : Old Business transactions on Risk Premium Basis is available

Processing the Retrocession Processing Order:

When the RPO is run on a cession that is retroceded through an OCC section where the above flag is created, then the premium rate defined on the PM condition will be applied to the New Business retrocession transactions that is created for the corresponding Old Business inward cession transaction

When the flag is not selected, the ceded percentage will be applied to all the ACIs on the Old Business Transaction and this will be considered the ACIs for the corresponding New Business transaction on the retrocession cession

Aim of function:

Introduced new objects in Life Universe both for Claim information and Cession Information:

1) MISR-MLI - ACI Worksheet As At Date

2) MISR-MLI - ACI Booking Year Period Missing Outer Join

System Parameters Affected:

N/A

Existing functionality affected:{}

N/A