Problem:
RPO creates incorrect Retro Sum in linked Retro scenario when the equivalent values are applied to calculate the limits

Solution:

When the retros are processed through the RPO and the cession currency is defined as part of the equivalent values of the OCC limit :
Calculate the sum to be retroceded in the equivalent values of the OCC limit currency
Apply the QS percentage and limits or Surplus limits to the sum to be retroceded based on the reinsurance product of the OCC
Process the retrocession cession with the retroceded sum at risk and retention in the cession currency

The RPO should follow the same functionality as the manual retrocession

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Cession Renewal Order not properly working for specific reinsurance start dates on the cession

Solution:
The Cession Renewal Order should renew all cessions that are due for renewal in the month specified in the Cession Renewal Order

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Smoker Status is not updated for joint life IO's through cession loader

Solution:

The Smoker Status should be updated as per the mapping in the Joint Life Block to the individual lives within the joint life cession similar to how the occupation class and code are updated

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Some structures are not connected to anywhere in the universe in SLife Main SICS 20.4.

Solution:

This structure of tables must be connected to the required tables.

Declination Reason:

Problem:
Incorrect retrocessions created by RPO when the cession benefits are to be protected by a QS and then Surplus

Solution:
RPO should process the retrocessions sequentially when the system parameter 'Sum at Risk- Standalone Retrocessions Only is NOT selected'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Claim Liability and Accounted Liability fields updated incorrectly when the claim is created through the loader

Solution:

When a claim is loaded with the status that is Valid, Preliminary or Outstanding
Ignore any mapped values to
Claim Liability
Accounted Liability
ACIs

On the created claim the Accounted Liability field will be picked up from the Claim Liability field
The Claim Liability field will get the value as mapped/ defaulted from the Notified Reinsurer's Liability
The following fields should be updated on the claim as mapped

Benefit Sum Insured
Benefit Sum Reinsured
Notified Reinsurer's Liability
Notified FGU Liability

When a claim is loaded with the status of Paid or In Payment or Special Paid or Update Claim Reserve
Ignore any mapped values to the following fields:

Benefit Sum Insured
Benefit Sum Reinsured
Accounted Liability
Any ACI

The following fields should be updated on the claim as mapped or if not mapped, the default values should remain
Notified FGU Liability
Notified Reinsurer's Liability
Claim Liability
Interest
Taxation
Claim Reserve

Accounted Liability will be defaulted from the value in the field Claim Liability
Where Interest and Taxation are mapped and updated on the claim the Accounted Liability with the values from Claim Liability and Interest and Taxation and Claim Reserve as applicable

The ACIs will be calculated based on the values mapped and updated to the fields
Claim Liability
Interest
Taxation
Any Expenses

Whatever fields are allowed to be updated manually should be updated accordingly when the claim is created through the loader

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Basic Premium calculation (based on the Premium Rate) is Incorrect on the linked Retro

Solution:

When the OCC Premium is Risk Premium and defined to use the premium rate/ amount from cession benefit:
Use the premium rate or amount that has been copied from the inward cession benefit to calculate the retrocession premiums as per the same rules that apply to the inward cession
Any extra premiums or deductions that have been defined to use the basic premium should be calculated as per the basic premium that has been calculated using the rate/ amount from cession benefit

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Claim Event Date outside the Cession Benefit Expiry Date is not validated

Solution:
Claim Event Date should always be within the cession benefit period
When a claim is created in any status with a claim event date beyond the benefit expiry period the system should throw a validation error 'Claim Event Date greater than Benefit Expiry date'

For all claims except with the status Preliminary the claim event date should always fall within an active transaction effective period as per existing functionality

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Getting error while export the lookup table

Solution:
It should be possible to export the Lookup Table from any already created imported or user defined Lookup Table.
This should be applicable to Life and P&C tables
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Warning message related to multiple premium rate tables appears incorrectly

Solution:
Do not check for multiple premium rate tables when they are not in use
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Personal details are not copied over from cession to claim on individual life claim

Solution:

For both Single and Joint Life cessions:
All details from the Personal Details of the Underwriting Cession benefit should be copied to the Actual Cession benefit for each life
All details from the Underwriting Cession benefit and the actual Cession benefit should be copied to the claim
It should be possible to enter personal details on the claim

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Incorrect transaction age when calculating the prorata premium when the transaction effective date falls within an effective period

Solution:

When calculating the prorata adjustment use the transaction age of

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Extra Mortality type is not working through Loader when it is used twice for same IO
Solution:

When there is more than one loading type mapped and uploaded through the loader, each loading should be created as individually on the cession
When the extra premium and ACIs are calculated for these loadings the consolidated ACI amounts should be calculated against the respective entry code

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Verification- SICSR-20645 RPGO calculation result is wrong

Solution:
When the RPGO is run always process each RPO sequentially in the order in which they are created by the RPGO
On the inward cession the RPO should only update the retrocession details and not the placement details

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect calculation of ACIs for 'Ceded in Error' and 'Cancelled from Inception'

Solution:
For facultative standalone retrocessions:
Similar to the behaviour on inward cessions:
Do not reverse any already reversed ACIs that have been created due to a termination transaction.
When reversal is to be done on an already reinstated transaction, apply the reversal to only the reinstated transaction and not to the linked termination transaction of the reinstatement

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Duplicate fields in Cession Output Pattern

Solution:

Remove the duplicate output pattern field PREM_RATE

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Cession Loader - Calculated Commission wrong with JL- Unable to select Initial Commission Timing when the deduction table is attached

Solution:

When the calculation frequency on the PM condition is not Yearly or Single the Initial Commission Timing field on the Basic Commission and Extra Commission field should always be editable
This should be editable when the commission rate is defined as a rate or a rate table

When the PM condition

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Cession Loader - Refund of Commission not working
Solution:

When the Unearned Premium is defined as returnable on the AC condition of the business section- all ACIs including commissions should be refunded as per the Unearned Premium Definition on the AC condition when a termination transaction is created on the cession benefit
This should be consistent for termination transactions created through the cession loader similar to how it is calculated on a manual cession

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Unable to create a claim for a life that is part of a joint life cession through the cession loader

Solution:

The claim loader should reference to the individual life that as mapped create the claim on that life as part of the joint life cession benefit

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Getting this SQL error on trying to load cessions through cession loader.

Error states :-
*_An error occurred running SQL: Referencing Cession Joint Life
com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'T1'._*

Solution:

It should be possible to load cessions with more than one IO on the same cession benefit and create a joint life cession

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Initial Commission timing is disabled for table of rates in deductions.

Solution:

When the calculation frequency on the PM condition is not Yearly or Single the Initial Commission Timing field on the Basic Commission and Extra Commission field should always be editable
This should be editable when the commission rate is defined as a rate or a rate table

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends while loading ACIs (our share) with null value.

Solution:
When the flag 'Cession amounts in our share' is selected on the Share condition of the business section
When the ACI is null or 0 as mapped, the ACI should be created on the cession benefit with a value of 0 and the cession benefit should be set to a status of active

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Amount field is picked for the Age instead of Age loading field through Loader

Solution:

Introduce one more field in the cession output pattern labelled 'Loading Age' to accept an integer
When the Loading Duration Option is 'From an Age' or 'Upto an Age' this field will be mandatory
When mapped, this should popular the field 'Age' when the Loading is created and the loading amount or percent or permille should be calculated From or To the mapped age value
The LOADING_AMOUNT field should always be mapped only the the Loading Amount and be applicable only when the Loading Factor is Flat Extra

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Renewal Point field is wrongly updated when cession is created through loader

Solution:
When a date value is mapped to the existing Renewal Point field, the loader should ignore the year and use the date and month from the mapped value to populate the Date and Month field on the cession's renewal point.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Loading factors with six decimals rounded off after full refresh

Solution:

Permille loadings should be accepted with up to six decimal places both on manual cessions and cessions created through the loader
The ACIs should be calculated using the permille values as entered
The loading values should not be rounded off after a refresh
The same loading values as entered should be applied to all the transactions as per the defined duration upto which the loading factor applies

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Initial Commission not calculated as per the Initial Commission Timing Defined

Solution:

When the cession renewal frequency is not Yearly- the initial commission for the first policy year should be calculated on the cession benefit as per the selection on the 'Initial Commission Timing' field in the Basic and Extra Premium Commission fields

If you select All in Period One then calculate the total Deductions that apply for Year 1and allocate them to the first risk period (i.e. the first month on monthly premium cession benefits).

• If you select Divided Over All Periods in First Year then calculate the Initial Annual Deduction and then divide the figure by the premium frequency to arrive at the deduction for each period. (i.e. if the premium frequency is monthly, the first 12 months).

• The option Divided Over All Periods in Each Subsequent Years then calculate the Initial Annual Deduction and then divide the figure by the premium frequency to arrive at the deduction for each period in the subsequent years- This will use the entry code as mapped for Initial Commission on Basic Premium in the subsequent policy years. (i.e. if the premium frequency is monthly, after first 12 months).

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends on trying to load cessions with subsequent transactions gives NullPointerException

Solution:

The subsequent transactions on the cession benefits should be created without abend. Any error should be part of the rejected records with the respective error message

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Subequent Year Commission for Extra Premiums not calculated as per the rates defined on the condition

Solution:

All subsequent year extra commissions should be calculated on the respective extra premiums based on the definition of the commission under the 'Renewal' Commission on the Extra Premium Tabs,
If the commission for the extra premium is defined as 'Same as Basic' then it should follow the rate option from the basic commission tab

The commissions should be calculated for each type of extra premium as defined and created with the entry code as per the calculation model

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Commission is wrongly calculated for the first year of the basic premium when Initial commission timing is All in period One

Solution:
When the Initial commission timing is defined as 'All in Period One' :
Calculate the total Deductions that apply for Year 1and allocate them to the first risk period (i.e. the first month on monthly premium cession benefits, the first quarter on quarterly premiums etc).
No further deductions should be calculated for the remaining periods within the first year

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends when creating a cession through loader with start date falls in the month of February

Solution:

Any date field for the month of February should be supported without abend depending on the type of year- whether leap year or not. When an invalid date for the month of February is entered or loaded, the system should not abend- it should reject the transaction with the error message 'Invalid Date'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

RPO creates incorrect retros when the cession benefit has more than one benefit covered

Solution:
When the RPO is run, only one retrocession cession should be created for the benefit
The retrocession cession benefit should also have all the benefits covered as per the inward cession

Where the PP does to cover all the benefits on the inward cession the RPO should fail this cession with the message 'invalid classifications'
The RPO should follow the same logic as per the manual retrocession process

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Booked ACI are linked to wrong Section / AC

Solution:

1. When the cession order or the retrocession cession order is run the ACIs should be booked on the section on the assumed business or OCC to which the cession benefit is linked

2. When there is more than one Accounting classification on the section, the AC marked as default should be defaulted to the booking

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 calculate cessions when the treaty has multiple layers. For example when a policy is to be reinsured through a Quota Share layer and then a Surplus or through more than one Surplus layer.

System Parameters Affected

None

Existing functionality affected

Reinsurance Program:
A new level of business 'Reinsurance Program' is now available. Multiple proportional assumed businesses can be linked and structured within a Reinsurance Program

Manual Cessions
It is now possible to create a manual cession linked to a Reinsurance Program also.

When a cession benefit is created and linked to a Reinsurnace Program, the Total Sum Reinsured will be validated against the Autocover Limit of the first layer of the Reinsurance Program

When the Gross Sum Reinsured exceeds the Autocover Limit, the remaining sum to be reinsured can be reinsured through the other assumed businesses defined as subsequent layers of the Reinsurance Program

Cession Loader

It is now possible to add a Reinsurance Program as a Business on the Cession Batch. The batch will be processed by applying the same input file and the mapping for all the businesses within the reinsurance program

Aim of function

To include several new fields on Cessions, Claims and Business Partners that were introduced over the past few releases to be supported through MTK

System Parameters Affected

None

Existing functionality affected

MTK for Cessions, Claims and Business Partners

Aim of function

Added Underwriters Estimates Supporting Figures Import Facility in SICS Life.

1. New Reference table Underwriters Estimates Imported Value Data Types (Code 1174)

2. New Import facility in System Administration Utility/Inbound Interfaces

3. New calculation variables in Underwriters Estimates Calculation Rules to retrieve the imported values

The calculation variables will retrieve the imported value for the referenced Data Type

System Parameters Affected

N/A

Existing functionality affected

Underwriters Estimates/Projections Estimate

Aim of function

To allow an automated process for Multi GAAP, we have added a new Accounting Order to automatically create and calculate Projections in Underwriters Estimates.

With this Order you can:
1. Create and calculate initial Projections in main currency on businesses with no existing Projections
2. Add and calculate additional Projections on businesses with already existing Projections
3. Recalculate existing Projections with a specific As At Date

When Projection Basis is 'Yearly' the Last Projection Year can be specified on the Order.

System Parameters Affected

N/A

Existing functionality affected

Calculate Projections

Aim of function

Sometimes the inforce files have only a transaction effective date or only a rule/ transaction code to identify whether the cession transaction is to be considered as a New Business, Renewal or Other transaction. The aim of this enhancement is to be able to identify the type of transaction code to be defaulted based on the transaction effective date and the renewal frequency OR to default the transaction effective date based on the transaction code.

System Parameters Affected

None

Existing functionality affected

Cession loader

When the input file has only a transaction effective date and no transaction code:
If the cession benefit does not already exist, a new business transaction is created with the reinsurance start date and transaction effective date as per the mapped values
If the cession benefit already exists and the transaction effective date as mapped = next renewal date as per the renewal frequency, a renewal transaction is created
If the cession benefit already exists and the transaction effective date as mapped != the next renewal date, then an Other transaction is created.

When the input file has a transaction code but no transaction effective date:
When the cession benefit already exists and the input file has a transaction code= Renewal, then the transaction is created as a renewal transaction and the transaction effective date is defaulted as per the next renewal date

For any other transaction code, the transaction effective date will be defaulted as per the online functionality when the specific transaction code is selected.

Aim of function
Added calculation variables to retrieve booked amounts in Underwriters Estimates. Functionality has previously been available in P&C only.

A new Entry Code Group Category is available:

4 new variables in Underwriters Estimates calculation rules. When used in a calculation rule, an Entry Code Group within Entry Code Group Category 'Underwriters Estimates' must be referenced.

When calculated in Underwriters Estimates, bookings within the referenced entry code group are retrieved. For bookings in a different currency than the estimate currency, the booking details are converted to estimate currency using different exchange rules retrieved on the Projection Year equal to the Accounting Year on the booking details.

for the 4 variables (see system administration guide for details).
Note that when Projection Basis is Yearly, the booked amounts are System parameters affected
New calculation variables in Underwriters Estimates calculation rules

Existing functionality affected
Configure Underwriters Estimates calculation rules

Aim of function

To address certain gaps in loading cession transactions with the transaction code 'Old Business' through the cession loader

System Parameters Affected

None

Existing functionality affected

Loading of cession transactions with transaction code 'Old Business'

Aim of function

In a scenario where one cession/ policy has several benefits covered which are being retroceded/ reinsured to different retrocessionaires/ reinsurers, it is expected that the entire policy/ cession is considered as one entity for sequencing.

System Parameters Affected

New System Parameter 'Include Policy Number in Sequencing' is now available.
This will be available for selection ONLY when the system parameter 'Method of Retrocession is reinsured sequentially in excess of Maximum Retention' is selected

Existing functionality affected

1. When the above mentioned system parameter is selected, on the Protection Program a new flag 'Allow more than one PP' is available for selection. This will allow the user to add more than one PP to the same RPO

2. When the RPO is run :

All the cessions that have been picked up by the RPO and have no prior retrocessions are sequenced as per the following order:

i. Reinsurance Start Date

ii. Policy Number- sorted numerically and then alphabetically

iii. Base Benefits within the sequenced policy numbers

iv. Rider Benefits within the sequenced policy numbers

Each cession will then be retroceded in sequence through the PPs within the RPO, where all the benefits on the same cession i.e all benefits that have the same policy number are fully retroceded before the next set of cessions with the same policy number are retroceded.

Note: RPOs that have more than one PP will not be included in a Retrocession Processing Group Order

Aim of function

Allocation of 'Original Accounting Year' and 'Original Accounting Period' based on policy anniversary- remaining functionality

System Parameters Affected

None

Existing functionality affected

Original Accounting Year and Period on the Cession Benefit and on the Cession Worksheets