Release documentation - Life - Enhancements and requests

Problem:
Joins and Object definitions in the Life Universe missing some functionality that needs to be adjusted.

Solution:
Need to update the joins and object definitions for Life Universe for the coming release.

Problem:
User Defined Fields in SICS does not match what we have in Life Main Universe.

Solution:
In Life main universe side we need to add the Userdefined string fields as showing in SICS side.

Problem:
In Life Universe we do not have possibility to inherit the values to ORP level of Business.

Solution:
1. Need to adjust V_UDD_BUSINESS views that are present in PC to fit into LIFE Universe.

2. Need to adjust to all the User Defined Field objects to come from this new views to make it possible to inherit the values to ORP level same as PC Universe.

Problem:
It was observed that the SICS APIs discloses technical details like backend server & database information and WEB-INF/conf path through HTTP error response.

Solution:
Introduce a new configuration parameter (init-parameter) in web.xml, named 'UseGenericSoapFaults'.

When this parameter option is enabled SICS Server will suppress technical information in SOAP response messages. This technical information could originate from for example:

• Invalid xml syntax causing AxisException
• invalid SQL causing SQLException
• Invocation of the unused REST endpoint in the Axis WS engine

Example of configuration -  Enable the new function (default value is false):

Excerpt from web.xml:

<init-param>
            <description>Flag for suppressing technical details in error messages in SOAPFaults (for increased security).</description>
            <param-name>UseGenericSoapFaults</param-name>
            <param-value>true</param-value>
</init-param>

 
Note:
Only technical error messages are suppressed.

Regular validation and conformation messages, triggered by functional behavior in SICS are NOT getting suppressed by this setting.

Problem:
Cession ID move from BENEFIT_GROUP to instead come from LF_CESSION.

Solution:
Get the cession id from the LF_CESSION on the BO report. Each cession whether it has one or more benefits will have only one cession id.

Problem:
New reference data child relationships not created during reference data update

Solution:
New reference data child relationships should be created during reference data update

Problem:
The transaction name on cession benefit is displaying as None when the effective date of subsequent transaction falls on 28th feb of leap year.

Solution:
Only for Leap Year and ONLY if the transaction is Renewal Transactions:

When the renewal point date is 28th February and the value that is mapped to the renewal transaction effective date is 28th February ignore the mapped value and always update the transaction effective date as 29th February.

For any other transaction use the date as mapped.
For any other dates use the date as mapped.

Problem: 
Duplicate column names shown in SQL Utility when the querying of the meta-data is done without specifying schema name.

Solution:
Return the schema that we are logged in to, if the creator is missing. 

Problem:
PM condition of business having multiple rate table and Accounting Admin condition not created through MTK

Solution:
Copy the Multiple Rate Tables and all the tables that are part of the Multiple Rate block when the PM condition is created through MTK if the tables have already been created

When the A condition is migrated through the Life MTK migrate all the fields including the Payment Due date to the target business condition from the source

Problem:
Issue in benefit_group table for retrocession placement cession.

Solution:
The following fields proposalNumber, memberStatus, memberId, certificateNumber, gsipFromDate and gsipToDate.
Should be copied to the placements from the retrocession cession and be available in the database columns for reports.

Problem:
In the SICS Desktop Application, the login password is stored in memory in cleartext even after logout.

Impact
Attackers or malicious insiders with access to the memory dump or physical access to victim machine would be able to retrieve sensitive information including cleartext passwords.
Besides obtaining unauthorized access to the application in the name of any user, this can be leveraged to carry out password stuffing attacks to compromise other accounts of the same user, in case the password is reused.

Likelihood
Sensitive information stored in memory in cleartext can only be accessed by an attacker who gained access to the victim machine or local access to the machine at the same time when the user is using the application which makes it. Hence it requires relatively high efforts to perform the attack in relation to the access obtained.

Solution:

• Store the login password encrypted in memory after login.
• Flush the encrypted login password from memory after logout.

Problem:
System is not validating when inactivating the person linked to business partners.

Solution:
 When a person is inactivated and the person is linked to any other partner as a contact person then throw a warning message 'The person is a contact person for one or more partners' .

 Problem:
On Webservices, the UpdateLfDeduction condition, is not updating the Flat and Extra Commission tabs of deduction condition.

 Solution:
The Flat and Extra Commission tabs of the Deduction condition should be included in the UpdateLfDeduction webservice.

 Problem:
System is updating the Proportional General Limit Condition of Business without checking the mandatory validations when updated through API.

Solution:
When user update the Proportional General Limit as 'PL' or Per Life, user has to provide a Retention Priority Basis, which is not given on the SOAP, so system should stop by a Validation Message as SYN0012 - The value of Limit Basis Definition -Per Life  requires that Proportional Limit Retention Priority Basis is specified.'

If no specific value is given then the PL condition should be created with the default setting of Benefits, First Death then equal proportions.

Problem:
Similar to the update/ edit functionality online

When the currency is replaced on the Limits condition through the s 'updateProportionalLimitsConditionForLife' API then the equivalent values should be updated and any value that is part of the soap should be considered for this. When there are valid equivalent values the L condition should be updated with the new currency.

When the currency is added, i.e it is updated in addition to an existing currency then the equivalent values should not be required and the currency and the limit amounts as input through the soap should be accepted and updated on the L condition.

Solution:
Similar to the update/ edit functionality online

When the currency is replaced on the Limits condition through the s 'updateProportionalLimitsConditionForLife' API then the equivalent values should be updated and any value that is part of the soap should be considered for this. When there are valid equivalent values the L condition should be updated with the new currency.

When the currency is added, i.e it is updated in addition to an existing currency then the equivalent values should not be required and the currency and the limit amounts as input through the soap should be accepted and updated on the L condition.

Problem:
Incorrect calculation of Premium, commission and extra premium for a migrated policy where the 1st transaction is old business. Issue-1.

Solution:
When the flag 'Old Business transactions as New Business' is selected on the PM condition of the OCC and the New Business transaction on the retrocession has 0 as the ACI.

1. Perform a calculation on the premium and related ACIs for the new business transaction using the rates/ rate tables/ amounts on the OCC
2. Use this calculated amount to calculate the pro rata ACIs for the lapse or Other transaction that falls within the New Business transaction period.

Problem:
Incorrect calculation of Premium, commission and extra premium for a migrated policy where the 1st transaction is old business. Issue-2

Solution:
When there is an Other transaction that does not impact any parameter that will recalculate the premium (such as SAR, any parameter that is part of the LUT linked to the PM condition) no premium ACI should be calculated for that Other transaction. No other ACI that is dependent on the premium ACI should also be calculated.

When any of the parameters that impact the premium calculation are updated on the OTHER transaction then the adjustment premium for the transaction should be calculated on prorata basis for the transaction period and the other ACIs that use the premium as the basis should be calculated as adjustments using the already calculated adjusted premiums.

Problem:
Other transaction processed in a period which is not active

Solution:

Reword the message 'LCH153 : Renewal points exists which have been missed on this cession benefit. Processing this transaction may result in incorrect ACIs being automatically calculated. Do you want to continue?'

Throw this message when a transaction is processed with an effective date outside the current active period as per existing functionality.

Only when the ceded flag is selected : Answer the message ; LCH153 'Renewal points exists which have been missed on this cession benefit. Processing this transaction may result in incorrect ACIs being automatically calculated. Do you want to continue?' as No when the transaction that is being processed is NOT a Renewal transaction

When the ceded flag is not selected : Existing functionality to remain, all transactions should be processed by this message being answered as Yes when processed through the loader. Any ACI that is mapped to the cession manually on original basis should be updated on the cession.

Problem:
All fields on Retro/Placements claims are not displaying when claims are created on cessions created on AB which are linked to STP/QSR.

Solution:
Only when the system parameter 'Sum at risk standalone retrocession only is selected' 
 When the cession has been retroceded through a QSR or STP then the retroclaims should also be automatically created when the inward claim is created. When this is automatically created without the RCPO then copy all the fields and tabs from the inward claim to the retroclaims and the placement claims.

Problem:
System is not allowing to attach notifer in remittance worksheet when the flag is selected- send an email to interested user.

It should be possible to attach a notifier to a remittance when the remittance worksheet is opened in View mode.

Solution:
It should be possible to attach a notifier to a remittance even when the remittance is in Edit mode and the notifier has to be sent to users via email. When the email is not configured, throw the relevant error message and attach the notifier.

Problem:
System throws a wrong validation message when cession loaded without benefit expiry date.

Solution:
When the calculation schedule period on the NC condition- Cession tolerance and data calculation tab- Data Calculaton is defined as 'To Benefit Expiry Date' OR when the calculation schedule period on the system parameters is defined as 'To Benefit Expiry Date' and the NC condition- Cession tolerance and data calculation tab- Data Calculation has the flag 'Use System Parameter Schedule' selected.

When the cession is processed in a batch and there is no benefit expiry date on the created cessions then fail the cession with the message 'Calculation Schedule period is defined as To Expiry Date in System Parameters. You must enter an Expiry Date.
 
The same message should be thrown when the cession is set to active manually or being processed as active through the loader.

Problem:
System throws a warning message when creating a new business.

Solution:
Do not throw the warning message BS00206 anytime during the new business creation process both in the first screen and at the time of saving the business that is created.
This should not be thrown for any type of business (Prop, Non Prop) and irrespective of the nature of business selected.

Problem:
Net sum retained and ceded percentage are calculating incorrectly for increase transaction when STP/QSR is attached on PP condition of AB.

Solution:
For a QSR or STP the ceded percentage should always remain the same throughout the life cycle of the cession and retrocession i.e the ceded percentage defined as the QS percentage on the STP or QSR on the Proportional Protection assignment on the AB.

Problem:
Protection Program (PT) condition is not getting linked to subsequent insured period of OCC.

Solution:
When a closed ended OCC is linked to an open ended PP, all renewal insured periods of the OCC should continue to be linked to the same PP. The link from the OCC to the PP and vice versa should be established and the cessions that were retroceded through the PP should continue to be retroceded through the same PP and OCC.

Problem:
Values for region of residence field are not sorted in alphabetical order.

Solution:
Sort the Locations in the Region of Residence drop down in alphabetical order. This is applicable to cessions, retrocessions, claims, retroclaims and all other dropdowns where region of residence is selected.

Problem:
On Facultative retrocession the Gross sum retroceded is updating when Retro SAR is increased by option adjust SAR to Existing Facultative retrocession.

Solution:
The Gross Sum Retroceded should never be recalculated or updated. It should always be copied from the previous transaction. Only the Retro SAR should be recalculated based on the change in the SAR which will be used to calculate the Retro SAR on the Fac Retrocessions.

When the retrocession is pure fac i.e there are no retros created through the RPO, then when the faculatative cession is attached do not validate the sum to be retroceded as part of the current facultative retrocession against the existing gross sum retroceded. Any increased remaining unplaced amount should be placed to the same fac retro or to any new fac retrocession

Problem:
System abends when creating a Standalone Individual Retrocession if the Reinsurance Premium method is blank on child sections of OCC.

Solution:
Do not allow child sections to be generated on the OCC if the reinsurance premium method is not entered.
Throw the existing validation message 'Reinsurance premium method is required'.

When the PP runs and it references to an OCC section without a reinsurance premium method it should not abend - the RPO should fail with an error message 'Reinsurance premium method is required'.

Problem:
Incorrect SAR for retrocession is updating in a cession after the refreshing the system.

Solution:
When the SAR rule is applied and the ield SA for retrocessio n is updated with the calculated value then this value should remain as per the calculated value based on the rule for each transaction. All values in the remaining fields such as GSR, SAR should emain as it was entered/ mapped at the time of creating the cession. Refresh of the system should not update any value.

Problem:
System generates a Walkback file on executing the SOAP for UpdateProportionalLimitCondition when 'Percent' element is not defined for Quota Share limit.

Solution:
 On executing the SOAP file for update proportional limit condition without a percent element then the system should not abend, and if the percent element is not defined, The SOAP should executed successfully & it should be considered as 0 similar to online functionality.

Problem:
Field Calculation Schedule Period is not available for selection in Business NC condition.

Solution:
In the NC condition when the data calculation is defined as Calculation Schedule ' Number of Years' the field 'Number of years' should be made available and force the user to input a value in it before saving.

Problem:
System is not updating the Cession Tolerance and Data Calculation tab on the NC Condition of business through Webservices.

Solution:
If no value is specifically given on the NC conditions for the Cession Tolerance tab (but other tabs have values) then always create the condition with the value defaulted to 'Use System Parameter Tolerance' and 'Use System Parameter Data Calculation' flags selected.

If the flag is selected and any other values are provided for the tolerance elements or schedule, then these should be ignored and the condition should be created with the system parameter flags selected.

If the System parameter flags are deselected in the soap and no values are mentioned in the soap then create the condition without any tolerance limit - all flagged as No.

If the Use System Parameter Schedule is deslected then save the condition with Original defaulted in the data calculation.

If any value is provided for the Cession Tolerance after the System Parameter flags are deselected then the values as per the soap should be updated on the condition.

Problem:
System Pop up a Unable to edit cell error when Medical reports are added with future date on Underwriting cession.

Solution:
When a future date is entered for a medical report then the system should throw an error message 'Date is a future date' and force the user to change the date.

Any date before or equal to the current date should be allowed without any error.

Problem:
Getting ABEND while running RPO when on the PP underlying limit and prop limit is not define 

Solution:
Do not check for or validate the limit values on the PP PT condition when processing the RPO
If the layers that are added or added and realised from outline on the PT, XL or SL condition are empty give a confirmation message 'One or more limits have not been defined on the protection assignments of the PP. Do you want to continue without defining the limits?'

Problem:
Add ACI button is disabled for Ceded Outstanding status of claim

Solution:
It should be possible to add ACIs manually on the claim with the status Ceded Outstanding
On right click in the ACI window the option Add ACI should be enabled
When any ACI is manually added these ACIs should be saved

If there are no ACIs added then the value from the claim liability field, interest, taxation if applicable should be automatically updated on the ACI tab similar to a claim with status Ceded Paid.

Problem:
Incorrect accounting year period for description of account - Regular claim reserve account.

Solution:
The accoutning year and period of the bookings created while running the retrocession cession order or cession order for Regular Account or Regular Claim Reserve Account should always use the From and To dates of the order.
Even if there are any open periods before or after the last accounting period the bookings created through the order should always have the same AYRP as the one defined on the order.

Problem:
Removing the Loading factors from the reinstatement with updates transaction for calculation frequency YEARLY and load a BATCH the transaction is created on the cession with Loading factors.

Solution:
When a Reinstatement with updates transaction is loaded and in this transaction there are updates on the loadings, either added or removed or with the values changed, then the loading changes should apply only to the reinstated transaction, and the ACIs should be calculated on pro rata basis for this specific reinstatement with update transaction only.

Any transactions prior to this should not be impacted. All transactions created after this should continue with the updated values unless specifically modified.

Problem:
System is not showing Group Information Tab on the Renewal Amendment window of Manual Standalone Retrocession.

Solution:
Similar to an inward cession the Group Information Tab should be available on the Renewal Amendment of the standalone retrocession.

Problem:
Incorrect validation SYN0002 while creating Referral limits condition when we have single currency on Business.

Solution:
The order in which the error messages appear when the RL condition single monetary amounts is not specified should be updated as below.
When the claim authority limits or the underwriting limits are defined as a single monetary amount and the amount and currency is not entered manually or through the webservices the error message triggered should be 'Missing mandatory currency'. When the currency is entered and then if the business has more than one currency defined then prompt the user to enter the equivalent values with the error message SYN0002 The equivalent value is required but has not been specified'.
If the business does not have multiple currencies then the field should be saved with the entered amount and selected currency .

Problem:
System is not allowing to create a cession batch with Reinsurance Program.

Solution:
It should be possible to add a Reinsurance Program in a cession batch and process the batch to create cessions on one or more of the assumed business linked to the Reinsurance Program.

When the reinsurance program is added to the batch the latest insured period of the reinsurance program should be added. The latest insured period of the businesses within the reinsurance program should be listed in list of ABs.

Validate the mandatory conditions on each AB within the PP. Even if one AB within the PP fails the mandatory conditions the batch should not be created.

If a specific insured period of the RP is selected then the insured periods of the ABs that are included in that insured period of the RP should be validated and included in the batch.

Problem:
When the loading factor is less than 1%, ACI's got calculated but the loading rate is not updated on the loading factor tab in the cession. 

Solution:
When the type of loading is Extra Mortality/ Morbidity and the Mord Rate value is mapped this value should be updated on the Total Mortality Percentage field in the cession in the loading container.

Here when the value is  less than or equal to 100 the existing error message as per manual functionality LCH277 'The Amount field is smaller than its minimum allowable value (101). The Loading will not be created. Do you want to continue? should be triggered, answered as Yes and the mapped value should be ignored and no loading should be created. Not extra premium should be calculated.
 
When the Mord Rate mapped is greater than 100 this value should be updated as the Total Mortality Percentage and the Extra Mortality Percentage should be calculated as 100- Mord Rate and updated on the cession benefit transaction.
 
The extra premium should be calculated for the extra mortality percentage.

Problem:
System Abends when more than 6 STRING type field is defined on the User Defined Layout for the Business UD condition.

Solution:
The system should not abend if on a business opening the user defined pages and user defined fields have been setup with more than 6 fields for User Defined Field Type: String (free text).   

Instead, allow 20 user defined string fields per business layout. It should be allowed to be create this when defining the business UDF layout. If more UDFs are have been  set up, the system should prevent this at the time of setting up the UDF layout.

This should be applicable to Life and P&C.

This is applicable to

• Bank
• Business - All Layouts
• Person
• Cession
• Benefit
• Insurable Object
• Claim

Problem:
System Abends on clicking the Task Management Button on the Remittance Worksheet window.

Solution:
The Task management button should open the Task Management Processes window when clicked and list any tasks linked to where Remittance Worksheet is defined as part of the start action.

Problem:
Joint Life Data transaction age is not correctly displayed on the renewal transaction.

Solution:

Add a new field Joint Life Transaction Age in the Joint Life tab (tab where Joint Life age is available)

Default the value from the Joint Life age tab to this field

When the joint life age basis is determined by cedent then calculate the Joint Life transaction age as Joint Life age + 1 for each completed policy year ( 4 quarterly, 12 monthly, 2 HLY, 1 yearly)

If the joint life age is overridden then copy this value to the Joint life transaction age and use this value to calculate the premiums as per existing functionality

Problem:
Joint Life Age is not displayed on the facultative retrocession.

Solution:
When he Joint life age calculation basis is , Joint premium method is' Equivalent single life and Joint age Table type as determined by cedent' on the Fac OCC then copy the joint life age from the inward cession transaction to the fac retrocession.

Problem:
System is showing the wrong Effective Period, when a manual Renewal Transc. created on the Standalone Retrocession.

Solution:
When a manual transaction is done on a  retrocession cession that is linked to an inward cession then only allow a transaction to be created within the existing effective periods. When this type of a transaction is created then the effective period end date should be defaulted to the end date of the effective period within which this transaction falls. Any transaction where the effective period start date is later than the last effective period end date of the cession should not be allowed.

On a manual standalone retrocession that is not linked to an inward cession all transactions should be allowed as per exisiting functionality.

Problem:
Getting an error 971 while running the retrocession cession order for regular claims account with FAC OCC.

Solution:
Do not check for the type of claim status when creating the worksheets and bookings while running the retrocession cession order or cession order.

When the description of account is Regular Claim Reserve include any entry codes that are part the Reserve EC category in any of the transaction picked up by the order

When the description of account is Cash Claim then include any entry coeds that are defined as Cash Claim.

When the description of account is Regular Account then include all entry codes from the transactions picked up that do not fall under Reserve or Cash Claim.

The transactions that the order picks up should be as per existing functionality- all transactions that have the as of date that fall within the From and To date of the order.

Note: All this works as intended for the Non Ceded claim statuses (Paid, In Payment, Update Claim Reserve, Special Paid).

The system should not abend and there should be no Non Proportional business referenced in this process.

Problem:
Getting an AC0870 information message while running the retrocession cession order for regular account with OCC

Solution:
When the reporting unit is not mandatory for the AC as per the system parameter settings for the base company then the cession order, retrocession cession order and any other accounting orders/ manual accounting should not require the reporting unit to be selected for the bookings created.

The message AC0870 should be removed. It is not relevant and not needed in any scenario.

Problem:
System is showing Negative net sum retained and ceded percentage more than 100 on retroceding, when cession is created with currency other than Main currency of business.

Solution:
Whenever the RPO is run always calculate the used retention, available retention, used capacity and available capacity in the currency of the cession benefit that is picked up using the exchange rate as on the date of transaction effective date (equivalent values are defined can currently only use daily rates).

Using these values calculated in the currency of the cession then process the cession through the OCC/ OCCs.

Problem:
The ACI status indicator for manual ACIs is updated as Suspended on ceded outstanding  status of claim.

Solution:
The status of the Ceded Outstanding ACIs should be Released on the inward and recovery claims created through the RCPO.

Problem:
The Interest and Taxation amounts are getting copied from previous transaction when we create a new status on claim.

Solution:
When a new Ceded Paid or Ceded Outstanding transaction is created do not copy the interest and taxation fields from the previous transaction

Problem:
System is not calculating the Premium as per the Calculation Rule Defined on the PM condition for Inward Cession.

Solution:

If there is an IF-THEN-ELSE defined in any calculation rule for Prop Premium then it will always be mandatory that all the IF and ELSE rules have a cession variable referenced for the rate table to be applied to

Otherwise there should be no cession variable for the IF and ELSE rules

The calculated rate should use the Rate basis refined on the table and apply this rate to the referenced cession variable

Here calculated rate from the table and applied to the value on the Cession Variable field defined. The rate should be as defined on the table as percent/ permille/ fixed amount.

If there is no cession variable defined on any one of the IF ELSE rules then the result will be incorrect.

Problem:
Retro claims are not created when claims are created through loader on STP business.

Solution:
Retroclaims should be automatically created and linked to the retrocessions as soon as the inward claim is created. The Retro claim date should be updated with the same date as the inward claim payment date and it should not be picked up by the RCPO.

When the retrocessions have been processed through a QSR or STP protection then the RCPO or RPO will not be relevant for processing the retrocessions or retro claims. They should be automatically created as soon as a inward cession or claim is created.

Problem:
System abends While defining SR and PM condition's on AB's that are attached to Reinsurance Program.

Solution:
When any  AB (Prop or Non Prop) is realised from an outline created from the RP then it should be possible to define all the conditions on the AB without an abend similar to an AB created through the wizard.

Do not validate the PM calculation basis or the SR condition calculation basis within the IABs within the RP.

Do not check for a linked protection program on an assumed business at any point since it is not possible or required to have a PP linked to an assumed business

There should be no reference to any protection program-OCC related logic in the RP-IAB linking process.

The solution of SE-16525 should not be applicable to IAB-Reinsurance Program irrespective of any system parameter setting.

Problem:
FAC retrocession is created on the claims with SAR amount and ACI's got calculated when the unplaced amount is 0 on the cession.

Solution:
When the RCPO is run pick up all the claims that have a payment due date that fall within the period end date of the RCPO as per existing functionality.

On each claim use the claim event date to reference the linked retrocession cessions:

Create the recovery claims on only the retrocession cessions where the cedent percentage is >0.

Use the ceded percentage on each of those linked retrocession cessions to calculate the claim ACIs.

Problem:
Accounting Classification are not saving on AC condition of OCC.

Solution:
Accounting Classifications that are created on the OCC and copied to the placements should remain on the placements including the intermediary placements even after refresh.

If the ACS are generated directly on the placements they should be saved and not vanish on refresh.

Problem:
System is throwing a validation when we edit the fixed ceded percentage flag on one of the OCCs that is linked to PP.

Solution:
Change this error message BR0179 to a warning message and allow the user to update the PL condition on the OCCs linked to the PP.

Problem:
The values in Ceded percentage, Net sum retained and total sum retroceded fields are calculating incorrectly on reinstatement with update transaction when fixed ceded percentage flag is selected on OCC.

Solution:
When the flag 'Fixed ceded percentage throughout the retrocession cession' is selected the ceded percentage that has been calculated on the transactions before the lapse should be applied for the reinstatement with update transaction. If there is any change in the SAR that is calculated then the reinstatement with update transaction should use the same percentage to calculate the net sum retained and retro SAR.

In a reinstatement with update transaction allow entering a new value for SAR for Retrocession. If this value is != SAR of the Reinstatement transaction then apply the fixed ceded percentage to the SAR for Retrocession field to calculate the Net Sum Retained and RSAR.

Any premium that needs to be calculated on the reinstatement with update transaction should use the revised Retro SAR.

Problem:
When OCC has a calculation rule on Quota Share business, system is calculating wrong retention and retroceding amount on cession on running RPO.

Solution:
When the SAR calculation rule is part of the OCC and the SAR for Retrocession is recalculated then apply the Quota Share limits to  this SAR for Retrocession value to calculate the Retention and Retro SAR.
 
Apply the QS percentage to the SAR for Retrocession to calculate the retention and the Retro SAR.

This should be applicable to all transactions where the RPO will recalculate the SAR for Retrocession value:

Always use the value in the SAR for Retrocession field and apply the same logic as the Sum at Risk field when there is no calculation rule.

Problem:
System is not updating the value of Cedent Retention on the Retrocession from inward cession on running the RPO.

Solution:
Copy the value from the Cedent's Retention field from the inward cession to the cedent retention field of the retroclaim when the RPO creates the retrocession.

Problem:

Other tab is not available on Standalone Retrocession edit tab while creating Reinstatement with updates transaction.

Solution:
Similar to inward cessions the Reinstatement with updates transaction should have all the tabs available to make any changes to the cession benefit details and the loadings. The same tabs available for an Other transaction should be available for a Reinstatement with updates on a Standalone Retrocession Cession.

Problem:
Incorrect SAR Calculation when Fixed Ceded Percentage flag is selected and a SAR calculation rule is defined.

Solution:
When the flag Fixed Cede Percentage is selected and the SAR Calculation rule has calculated a value in the SAR for Retrocession field after the RPO is run always use the value in the SAR for Retrocession field to calculate the Retro SAR for the retro transactions.

Always apply the ceded percentage from the first transaction to the SAR for Retrocession to calculate the net sum retained and the retro SAR for subsequent transactions.

The logic should be the same as when the SAR calc rule is not applicable, but instead of using the field Sum at Risk on the inward cession use the field SAR for Retrocession.

Problem: 
Ceded Claim Reserve is calculating incorrectly on ceded paid status of claim.

Solution:
When the Ceded Paid transaction is created after a Ceded Outstanding transaction then on the Ceded Paid transaction the following should happen.

1. Deduct the current ceded paid loss amount from the claim reserve amount of the immediate previous ceded outstanding transaction.
2. Create a claim reserve ACI with this new amount with the claim reserve entry code.
3. Create the loss paid ACI with the loss paid loss amount.

Problem:
RPO bug for multiple PP mode.

Solution:
When there is more than one PP that matches the cession benefit's classification, but only the OCCs within one of the PPs match the classification of the cession benefit, then if the cession fails being retroceded through the first PP (due to mismatch of OCC classifications) then it has to then be processed through the next PP with the same classifications and if the OCCs within that PP match, then the cession should be retroceded through that PP. 

Aim of function
For current messages:

• To raise an error message related to AAD whenever there is an AAD applied on the contract.

Business value for customers
For current messages:

• When AAD is applied to Claim FGU advisories, SICS to raise an error message “Claim is on a contract with AAD, which might impact the loss and expense amounts” by “FGUClaimAmountsValidationRule” whenever there is a mismatch of amounts due to AAD.

System Parameters Affected
None

Existing functionality affected
Processing of eMessages.

Aim of function
Review all validation/information/confirmation messages and make sure to avoid SICS term in Assure Re version.

Business value for customers
Better UI for the Standalone Retrocessions Main and Agreement tab.

System Parameters Affected
N/A

Existing functionality affected
N/A

Aim of function
The aim of the function is to be able to add more than one Protection Program to the Retrocession Claim Processing Order to process the recovery of all claims retroceded through the Protection Programs.

Business value for customers
All claim recoveries can be done through a single run of the Retrocession Claim Processing order.
 
System Parameters Affected
None

Existing functionality affected
A new flag ' Multiple PP' is available on the Retrocession Claim Processing Order. Selecting this will allow the user to include several Protection Programs within the same RCPO for processing.

Aim of function
New Security use cases for Individual Insurable Object handling.
New Security use cases for Cession Worksheet administration.

Business value for customers
It will be possible to delink the Individual Insurable Object handling use case from the Group Insurable Object use case enabling the customer to entirely hide the Group Insurable Object handling from the desktop when not relevant.
New Security Use Cases and user access will now be available to control the Cession Worksheets created through the Cession and Retrocession Cession Order.

System Parameters Affected
None

Existing functionality affected
New Update User Access is available in the Individual Insurable Object Administration.
New Use Case for Cession Worksheet handling.

Note:
The new Use Case for Cession Worksheet handling is unassigned to all users by default and hence the system administrator will need to assign this use case to all relevant users when upgrading to the version where this use case is available.

Aim of function
The aim of this function is to extend the Life Business webservices to support more functions.

Business value for customers
More Life business conditions are now supported through APIs.
 
System Parameters Affected
None

Existing functionality affected
The following functions are now available through Webservices for Life business:

1. Link OCCs to PPs through Webservices
2. Link Assumed Business to Reinsurance Program through Webservices
3. Add placements on OCCs through Webservices
4. Administration Condition on the business can be created through Webservices
5. The flag 'Default Accounting Classification from the Linked Inward Cession' can be set through Webservices

Aim of function
Various new fields on the cession benefit which will be included in the SAR and premium calculation rules and also be used to process the retrocessions when the RPO is run.

A new Rate Amount option for Premium Calculation where a Premium Calculation Rule can be specified.

Additional fields on the Other Information tab.

Business value for customers
The Premium calculation and SAR calculation rules will now be able to use parameters from the Retrocession Cession level along with the parameters from the Cession level which include new fields for Accumulated values.

Ten Other Information fields will be available for SAR and Premium Calculation rules.

It will also be possible to define a Premium Calculation Rule on the PM condition which will reference to various fields on the cession and retrocession cession benefits for premium calculation.
 
System Parameters Affected
New system parameter 'Show accumulated amounts on the cession benefit'.

New Variables for Retrocession in the SAR and Premium Calculation Rules

Existing functionality affected

1. When the system parameter 'Show accumulated amounts on the cession benefit'

The following new fields will be available on the cession benefit

1. Accumulated Retention
2. Accumulated Sum Assured
3. Accumulated Gross Sum Reinsured
4. Accumulated Sum at Risk

The above values will be defaulted on the cession benefit as an absolute value without considering any exchange rates
The values will be defaulted from the cession benefit in the sequence of the effective period start date and the sequence of creation. Only the absolute value will be updated and no currency exchange rates will be applied. No recalculation of these values will be done after the RPO is processed.

2. All fields on the retrocession cession benefit are now available for selection as variables when defining the SAR calculation and the premium calculation rules.

3. On the PM condition a Rate / Amount option 'Use Premium Calculation Rule' is available. Selecting this option will calculate the premiums using the calculation rule defined in the system parameters where one or more Lookup Tables can be referenced along with other fields on the cession benefit.

4. 34 Other Information fields are now available on the Cession Benefit transaction. These are informational fields. Other Info 1 to Other Info 10 are now available as Cession and Retrocession variables that can be used in SAR and PM calculation rules.
 

Aim of function
The aim of the function is to be able to handle recovery of declined claims where the reinsurance premiums are refunded.

Business value for customers
For products where there are specific rules for recovery of premiums in case of declined claims there are now different options to support various calculation rules.

System Parameters Affected
None

Existing functionality affected
For claims on cessions where the Ceded flag is selected, there is now a new status 'Declined' that is allowed. On a Declined claim the following options are available and selection of each option will result in the claim recovery being calculated based on the reinsurance premium paid.

Declined- no refund : The recovery claims will be created with the status Declined, but no ACIs will be created for recovery
Declined- recovery of all reinsurance premiums paid : This will create the recovery based on Net premiums (Premiums+ Extra premiums – all types of Commissions) that have “Included” status on linked retrocession.
Declined- recovery of only reins premiums paid after the date of claim event on non pro rata basis with recovery of only reinsurance premiums paid after the next anniversary date following the claim event date.