Problem:
The Open Worksheet Mass Update function is used to close worksheets uploaded through excel or API without calculating Amout
When you import technical worksheet from spreadsheet with multiple businesses/currencies, and use the New Amount column, then the details on the business/currency not inspected by the user becomes zero, i.e. the Amount value is not calculated.

Solution:
When using the function Import Technical Worksheet from Column Spreadsheet and it contains mappings to the New Amount column on the worksheet, then the system must calculate correct Previous Amount so that the Amount column is calculated correctly (New Amount less Previous Amount = Amount). A fix has been implemented in version 22.1 according to SICSR-23207, but it must also work in case there are two rows in the spreadsheet on same aggregation level, so that also the second worksheet created on this aggregation level calculates the Previous Amount after the 1st worksheet is closed.

Problem:
SICS 22.4 UAT - Abend on select 'Find in Retroceded' from assumed Business Ledger

Solution:
When the column Retroceded in the Details container on the Business Ledger on outward business, e.g. a prop treaty OCC, is added and saved for this user in the Column View, it shall correctly be shown in the container for prop treaty OCC and other businesses where this is relevant. But we must make sure the system is not abending and that means it must also be shown it Business Ledgers where it is not relevant, e.g. on an Assumed Business.

Workaround:
The Retroceded column is irrelevant on an Assumed Business, so the user should just avoid use the option Find in Retroceded in this column.

Problem:

Upload the worksheet using ''Import Technical Worksheet from Column Spreadsheet 'function. After the worksheet is uploaded, the system creates a balance for each entrycode

Solution:

When Import Technical Worksheet from Column is executed and it contains of different details, when the worksheets are created with several details, make sure the system groups the details correctly in necessary balances, as if the user has inspected the worksheet manually.

For the wrong reasons, need to add verification rules when using ''Import Technical Worksheet from Column Spreadsheet 'function to upload worksheet. The AccYR of the worksheet is greater than or equal to underwriting year.

Problem:

Table V_CD is not linked to any other table in structure.

Solution:

Table V_CD should be connected to CD(CESSION_DETAIL) table with proper join conditions.

Problem:

 Below objects are not working when running a check against a SQL Server database:

1. Accounting Period From Quarter

2. Primary life

3. First Death

Solution:

The SQL it should be 

• Accounting Period From Quarter
  @Aggregate_aware(V_BOAC_LF_FACT.PERIOD_QUARTER,V_BALANCE_TIMELINE.PERIOD_QUARTER)
  This view also needs to be (almost) the same between Cede, PC and Life
• Primary life
  LF_IOPrimLife.CURRENTNAME_FULLN
• First Death
  LF_IOFirstDeath.CURRENTNAME_FULLN

Problem:

Use Cases for Business Conditions Underwriters Estimate Period Estimate Life and Business Conditions Underwriters Estimate Projection Estimate Life missing description

Solution:

The Use Cases for the following that are missing a description to be updated with the text describing the function that they control

Depending on the Use Case type selected Create, Update or Delete the description should be updated as below

Business Conditions Underwriters Estimate Period Estimate Life : Controls Access to Creating./ Updating/ Deleting of Business Conditions Underwriters Estimate Period Estimate Life

Business Conditions Underwriters Estimate Projection Estimate Life : Controls Access to Creating/ Updating/ Deleting of Business Conditions Underwriters Estimate Projection Estimate Life

Problem:

System abends when creating Technical Worksheet when there are no single accounts in the insured period.

Solution:

Default the Accounting Year and Period as None when the user changes the insured period or creates a booking on an insured period where the single accounts have not been defined. The system should not abend.

Problem:

The Multi GAAP Recalculation of ES in the SICS Life business of QianHai Re is very slow

Solution:

After 'Period Estimation Calculation on Prop Outward Contracts' is selected, a new value related to the Period estimate item is generated when Recalculation order is executed. Therefore, the solution is that IAB skips this processing logic, and only OCC and ORP are affected by this parameter, which can improve the efficiency of Recalculation order execution.

Problem:
Performance issue in cession loader batch

Solution:

Update the queries to improve the performance

Problem:
POSTGRE Walkback for Data Export function (Remittance)

Solution:
When running the Execute Selected Functions for a remittance with the Rem Class 2 and/or Rem Class 3 given, then the system must also be able to get those values and add them to the export file.
The system must get these values from the fields FRK_REM_CL2 and FRK_REM_CL2 in table AC_REM_ADD_CL and these are found by following the AC_LEDGER_BALANCE.FK_REM_ADD_CL from the actual remittance balance.

Problem:

System is showing wrong Unsettled Amount in Balance Pairing, when the Group Pairing Identifier is not defined on the system parameter.

Solution:

When the system parameter 'Balance Pairing Group in Use' is selected a group pairing identifier becomes mandatory for all types of balance pairings
So when the user attempts to perform a balance pairing and clicks on OK the error message 'No valid group pairing identifier is defined' should be thrown as per existing functionality. Nothing further should be validated here after this. On clicking OK to the error message and then again clicking OK for the balance pairing, the same error message should pop up.
No further calculation of the unsettled/ outstanding amounts should be done during this process. The error message should continue to be thrown forcing the user to cancel the operation and add an identifier

For Reference: This works fine when the operation is 'Create Balance Pairing Group'

Problem:

On individual claim with Payment type as Income benefit Per frequency ACI's are not updated after editing and updating decision liability tab values.

Solution:

Irrespective of the Sum Reinsured Type all values from the Decision Liability tab on the claim- Claim Liability, Interest, Taxation, Claim Reserve  should be used to calculate the ACIs.

Problem:

Batch saved with incorrect Agreement insured period.

Solution:

Save the cession or claim batch with the insured period of the agreement that had been selected

Process all cessions or claims referencing to the selected insured period only

Validate all mandatory conditions such as Admin condition, Accounting Classifications, Partial Processing flag etc while saving the batch based on the selected insured period.

Problem:

System not able to find Remittance WK created through migration & abends when trying to find a migrated remittance worksheet.

Solution:

When importing a remittance worksheet through MTK never check for a business identifier.

If the business partner identifier is null, then similar to a technical worksheet reject the file with the message 'Business partner identifier not available'.

Problem:

For any transaction of a Policy which has no retrocession and full amount under 'Unplaced Share', the option 'create facultative' is not enabled

Solution:

The option to add OCC for facultative retrocession should be enabled in the below scenario also:

Where there is a value in the field Unplaced Amount AND the value in the field Total Sum Retroceded and SAR Net Sum Retained is 0
Do not check for the Retrocessions attached or the Retroceded Date in the above scenario.

Problem:

Number of lives is not visible on Renewals on the FAC retrocession and placements.

Solution:

On all Facultative retrocession transactions copy the value from the field number of lives  from the corresponding inward cession transaction.

Problem:

Incorrect validation when we take reinsurance start date earlier than policy start date.

Solution:

Batch should get updated with error as per the online error message 'Commencement date of policy is invalid, and Should be before or equal to the commencement date of reinsurance.' Validation error should not contain anything related to joint life.

Problem:

System abends while running RCPO for Non ceded claims with expenses.

Solution:

The RCPO should pick up the claim expenses and process them on the created standalone claim in the ceded percentage.

If the claim has already been picked up once and the retroceded date is sett, then any new expenses should be ignored and the system should not abend.

Problem:

Paid Loss and Outstanding Reserve ACI amount on Retro Claim needs to be rounded off to the nearest Integer (similar to how retro SAR is calculated).

Solution:

All claim ACI amounts that are calculated/ copied from any of the values in the claim decision liability or expenses tab should reflect the same decimals as available in the respective fields.

When the Claim Liability, Reserves, Expenses, Taxation or Interest values are calculated and this calculated value is then created as the retro claim ACI then the ACI should be rounded off using the same rule as the calculated values in the respective fields.

When the ACIs are specifically mapped with a value or entered on the claim, then the value as mapped or entered with the decimals if any should be considered and the retro claim ACIs should be calculated using the ACIs.

Problem:

System abends on Registering Termination on a Business in Combined Database.

Solution:

All options under Business Default Values including Wizard Layout options should not be applicable to Life. They are P&C options. This should not impact the windows that open in Life. Selections in this option should not be applicable in Life and should not cause any abend in the Life wizards.

Problem:

Duplicate joint life IO's are getting created even after merging the individual IO's with different identifier types

Solution:

When an individual IO is merged and the individual IOs that were being merged were part of different joint life insurable object then the joint life IO should also be merged and all the joint life cessions should be linked to the same individual and joint life IO

Problem:

Incorrect ACI calculation on Retrocession cession for Other deductions

Solution:
When the ceded flag is selected:

Always calculate ALL basic premium ACIs on annualised basis and divide it by the calculation frequency

Calculate Extra mortality premiums on the basis of the calculated basic premiums

Calculate Flat Extra on annual basis and divide by calculation frequency

Calculate per mill extras on annual basis and divide by calculation frequency

Calculate all commissions based on reinsurance premium using the calculated premium as above

Calculate the Other Deductions based on the gross premium , net premium , basic gross, extra gross, basic net, extra net using the above calculated values

The factor for dividing the annualised premium should be applied only once when calculating ANY ACI

When the ceded flag is selected- DO NOT apply the calculation frequency as a factor to calculate the premiums- the premium for each renewal period is as defined and all related ACIs will also be calculated based on this premium

Problem:

The flag 'Create Retrocessions even if ACIs are not calculated' is visible on RPO irrespective of system parameter selection
 

Solution:

The flag ''Create Retrocessions even if ACI's are not calculated' should be visible only when the system parameter ''Method of retrocession is reinsured sequentially in excess of maximum retention' is selected.

Problem:

SICS abends when user try to open 'View or Edit Mapping' option on a cession batch which has it's status updated as 'Referenced with Error' or 'Updated with Error'

Solution:

View or edit of the child batch that has been created due to any errors should be allowed without an abend.

The user should be able to update the mapping, reload the batch and process it again without abend.

Problem:
Add Benefit to existing Underwriting Individual Cession leads to abend

Solution:
System should allow adding Benefit to existing Underwriting Individual Cession without an abend

Problem:

The flag 'Create retrocessions when ACIs are not created' is not available in the webservices to create the RPO.

Solution:

The option to select or deselect the flag should be available in the create RPO webservice

The default option should be selected

This should be applicable only in an environmet where the system parameter 'sum at risk reinsured sequentially in excess of maximum retention' is selected. 

In an env where this system parameter is not selected selection or deselection of the flag should have no impact and the RPO should run and create the retros.

Problem:

Classifications of PP are not displaying on RPO when PM conditions are not defined on OCC

Solution:

When any one of the OCCs linked to the PP that is being attached does not have the PM condition and therefore it is not able to validate the calculation frequency, then throw the same error message as implemented in SE-19615 modified as below 'One or more OCCs linked to the PP has a calculation frequency that is not As Original or the PM condition has not been defined'

The same error message should be applicable to all scenarios as per SE-19615.

Problem:

Batch is getting referenced with error when trying to create a cession in SQLSERVER_2019 Database
 
Solution:

On the SQL servers also, when the claim is loaded and there is more than one cession benefit on the cession with the same details (where there is one active benefit and one or more duplicate inactive benefits), it should be possible to reference to the cession benefit based on the claim event date and attach the claim to the cession benefit where the claim event date is valid.

Problem:

Technical worksheet is not available in a business ledger when running retrocession calculation order

Solution:

All As Booking and As Account bookings on the OCC and ORP in closed and open status in any currency should be displayed on the respective business ledgers

Problem:

The released retention is not being utilized by another cession with same benefit of same life when the fixed ceded percentage is selected on OCC.

Solution:

When the flag 'Fixed ceded percentage throughout the life cycle of the retrocession cession' is selected on P/L condition and the SAR of a cession reduces thereby reducing the retention that is used by the cession, then this retention should be 'released' and made available for other cessions that are processed through this PP.

Problem:

Getting abend while attaching PP on cession in the 'linked environment'.

Solution:

'Reinstatement with Updates' should be available for selection on a cession benefit only when the system parameter 'Retrocession Basis is Reinsured Sequentially in Excess of Retention'.

In any other environment this should never be allowed, and any referencing to this functionality should be bypassed.

Problem:

The ceded percentage on retro claims is not calculating correctly when the cession is retroceded by multiple facultative OCCs/ PP having multiple OCCs + Fac OCC.

Solution:

When there is one retrocession or more than one retrocession linked to the cession benefit:

When the inward claim is created default the ceded percentage from the cession benefit transaction to the claim. This can be overridden on the claim.

When the ceded percentage on the claim is not overridden i.e defaulted from the cession benefit then when the RCPO is run :

If the total ceded percentage on all the linked retrocession cessions on the cession benefit linked to the claim = the the ceded percentage on the inward claim, then use the retrocession share (Retro SAR/ SAR) to calculate the retro claim ACIs and all the values on each of the retro claims

Update the retrocession claims with the same ceded percentage that is available on the respective retrocession cessions.

When the ceded percentage is overridden- this currently seems to still be incorrect. We will need to handle this as a separate case since the same scenarios with one or more retros is possible. So as per this case, the existing logic can remain when the ceded percentage on the claim != the sum of the ceded percentage of the retrocession cessions.

Problem:

Individual IO details are not updated on Facultative Retrocessions when we create Joint life cession

Solution:

Copy all IO details- Joint Life IO and the individuals within the joint life IO- from the inward cession to the facultative retrocession

When any of the limits, premiums or other ACIs are dependent on these parameters (occ class, preferred life classification etc) then they should be considered on the fac retro also
 

Problem:

Claim liability is not recalculating While changing Liability type.

Solution:

When the claim liability type has been switched on a claim that is being created or edited or when edited while changing the status of the claim, then throw a warning message 'Claim Liability type has been changed and the claim liability amount may be recalculated. Please check claim liability before saving'.

Problem:

Facultative retro created on incorrect transaction period

Solution:

The manual facultative retrocession should only be created and linked to the effective period from which the facultative OCC was linked. The unplaced amount for that effective period should be considered and the remaining unplaced amount should be updated using the unplaced amount corresponding to that effective period only.

Even if there was an unplaced amount in the earlier effective periods that were not facultatively placed this amount should remain unaffected by fac retros created and linked to later effective periods of the cession.

Problem:

System is abending when trying to closed the rejected child batch

Solution:

When a child batch is created from a main batch that is linked to a closed insured period then the child batch should also be linked to the same insured period as the main batch

The system should not abend when trying the reprocess the rejected batch.

Problem:

The Sum Re/Insured Type is not updating when a Business is created through SICS Webservices.

Solution:

The Sum Reinsured Type should be an element in the Create Business SOAP.

This will require the value in the Reference Date 823.

If the value is TERM then the frequency element should be made available for selection as a mandatory field value.

This should be similar to online functionality.

Problem:

Retro calculation Order abends before closing the worksheet

Solution:

Intra Group Contract is not relevant for Life. So both  in a combined database or standalone Life Database when the Retrocession Calculation Order is run on a business that has an intermediary placement any check for IGC should be bypassed.

It should be possible to close the worksheet directly when the RCO is closed or it should be possible to close the worksheet from the list of open worksheets in the RCO.

Problem:

Incorrect retention calculated when we create two cessions on same life and define retention corridor in L condition.

Solution:

When the retention corridor is applied it should be applied and the SAR is retained, this should be considered as part of the used retention. When there is another cession created for the same life, same benefit then the retention should be considered as used by the first cession.

The above logic works as expected for a retention when there is no retention corridor applied.

Problem:

System abends on Web Services, when the 'Total Retention' or 'Our retention' element is not defined on the UpdatedLfProportionalLimitCondition Operation.
 
Solution:

We should be able update the L condition even of only one value is given in these 4 fields - the behaviour will be similar to online functionality in this case where all 4 fields are updated using the 1 value entered. If only Cedents Retention is entered also, the value will be calculated as 0 and still the condition will be saved without abend.

1) cedentsRetention is Cedent's Retention Limit
2) ourRetention is Our Reinsurance Limit
3) availableRetention is Available Reinsurance Limit
4) totalRetention is Quota Share Limit

2. It should also be possible to give all 4 values where the final calculation will be done based on the value entered in totalRetention which will update the Quota Share Limit field and then recalculate the rest of the fields based on the cedent's retention percentage

All soap logic should follow the online logic. None of the fields are required, if the value is not entered create the condition with 0 limits but there should be no abend.

Problem:

When same SOAP with exact same data is executed twice on the Webservices, the Limit condition of Quota Share Business is updating twice with different values.

Solution:

When the same update SOAP is executed and there is no change in any of the values for percent, retention, quota share amount, available reinsurance (respective elements) then there should be no recalculation of limits. The same values should be updated on the Limits condition of the Quota Share Business.

Problem:

Ceded percent is not updating on Placements cessions created on manual standalone individual retrocessions.

Solution:

If a ceded percentage field has been entered in the standalone retrocessions then the value should used to update the ceded percentage on the the placements. Calculate the ceded percentage on the placements using the ceded percentage on the OCC and the placement percentage on each of the placements as defined on the OCC.

Problem:
System abends while creating a claim with assessments on manual Standalone individual retrocession

Solution:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Placement claim values are not updating if we edit and update retro claim details.

Solution:

All values on the standalone retro claim should be updated on the placement claims. When an outward claim is edited then the changes made on the outward claim level should reflect on the linked placement claims.

This will be applicable to both ceded and non ceded claims.

If the edit is done on the retrocession claim level wherever it is allowed then the edited values should be copied to the placement claims also.

Problem:

Cession benefit is displayed as always linked to Agreement section but all other details are actually linked to the correct section that it was linked to when created manually

Solution:

When a cession benefit is created manually and is linked to a section of the AB then the created cession benefit should be displayed as linked to that section when viewed on the Agreement tab of the cession benefit.

Problem:

When OCC is linked to AB, the Details of 'Notes' field from the Technical Worksheet of Assumed Buiness is not updating to the OCC Technical Worksheet and Placement TW.
 
Solution:

ONLY IN THE LIFE SYSTEM

When the Acct Admin basis is Bulk

Copy all the Notes from the technical worksheet linked to the inward business to the OCC As Original Worksheet.

Copy the Notes on the OCC As Original Worksheet to the Placement worksheets.

Problem:

Above Notification limit and Above Participation flags are not updating on retro claims and on Placements claims.

Solution:

The Above notification and Above Participation Limit on the OCC should be considered on the retrocession cession level independent of the linked inward cession if any

When the RL condition of the OCC has the Above notification and Above Participation Limit defined then the flags should be available on the retro claim.

When the notified reinsurer's liability on the retroclaim is above the defined values on the OCC then the respective flags should be set (using the same logic as inward claim- Assumed Business RL condition).

When the notified reinsurer's liability is above the notificaion limit then the above notification limit flag should be selected.

If it is above participation limit, then both flags should be selected.

The flags from the Retro claim should be copied to the placement claims.

When the notified reinsurance liability is edited and so the flags are updated on the retro claim level then the placement claims should be updated accordingly.

Problem:

Life Use Cases are missing description.

Solution:

The Use Cases for the following that are missing a description to be updated with the text describing the function that they control

Depending on the Use Case type selected Create, Update or Delete the description should be updated as below

Business Conditions Underwriters Estimate Period Estimate Life : Controls Access to Creating./ Updating/ Deleting  of  Business Conditions Underwriters Estimate Period Estimate Life

Business Conditions Underwriters Estimate Projection Estimate Life : Controls Access to Creating/ Updating/ Deleting of Business Conditions Underwriters Estimate Projection Estimate Life

Problem:
Abend when processing a batch where the input file cannot be found

Solution:

When the referenced file is not accessible then the system or when there is no data that can be processed in the file should not abend. An error message eg 'No output data/ Unable to find the source file for processing' should be thrown when you attempt to process the batch in any status

Problem:

System abends when we click on 'validate and process the input file' option to import sub SOA.

Solution:

Do not validate the accounting year or Insured Period while validating the Sub SOA import.

All validations implemented as per SE-21172 should be applicable only to column spreadsheet upload.

Problem:

Cash claim flag is unavailable on Decision/Liability tab for Sum/Re type as Income per frequency 

Solution:

Cash Claim flag should be available for Income Benefit frequency claims

When this flag is selected the ACIs should be created with the entry code corresponding to the Cash Claim as mapped in the calculation model

Problem:

Mapping boxes - error with numbers. Duplicate numbering and numbering is changed with each new revision

Solution:

Each mapping box that is created through the pallette option should be sequentially incremented and no duplicates should be created

When a mapping is updated as a new revision or the current revision is edited the already created mapping boxes should retain the same numbering.

Problem:

The status indicator of ACI is not updating as released after the cession worksheet is inactivated from the worksheet option

Solution:

When the cession or retrocession worksheet is inactivated either by inactivating it from the order or from the worksheet level using the Inactivate option or through the Right click- Inactivate all open worksheets option, the linked ACIs on the cessions and claims should be set back to released status

Problem:

System Abends on changing the Limits amount to maximum allowed values on a copied Buisness

Solution:

The maximum amount that is allowed in any of the fields in the limit conditions should be accepted. If the value entered (or calculated using Autocver Limit+ Retention/ UTL) exceends that maximum allowable value in any field then the error message should be thrown and the user should be forced to reset the amount

Problem:

System is showing incorrect validation message on creating claim with greater than today's date.

Solution:

When the claim event date is greater than the current date throw the message 'Claim event date cannot be a future date'

Problem:

System is defaulting Sum ReInsured Frq to Yearly and is Grid Out when Sum Reinsured type is As original on Assumed Business

Solution:
When the Sum Reins type = Original and the option on the cession/ claims Income Benefit Per Frequency is selected then it should allow all values Yearly, HLY, QLY, MLY and Weekly

When creating a manual cession or manual standalone claim or through the loader the dropdown should be available for selection and also the option should be accepted as mapped

Problem:
Getting a validation error message when try to add 'assessment' while creating the claim status as Ceased

Solution:

When a claim status is changed to Ceased from any Status only Cease Claim should be available in the Assessment List

It should be defaulted

The cessassition date should be defaulted from the payment date where avaialable

When payment date is not avaialable or cessasition date is removed then the error message 'Cessassition date is required ...' should be thrown

When ceased reason is not given then the existing error message should remain

Problem:
RCPO run is not considering the benefit covered filter

Solution:
When the Benefit Covered filter is applied on the RCPO only the claims as per the selected benefit covered should be processed

Problem:
Critical Issue in GL Transfer

Solution:
Data to be inserted into GL_T_NEW/GL_T_ALL tables when running the Transfer to General Ledger process

Problem:
RPO Abends when processing a Lapse when there is a Fac retrocession

Solution:

When there is a lapse or any termination transaction on a cession where there is a fac retrocession linked the fac retro should be automatically processed as a lapse transaction (or the termination transaction on the inward cession) The Retroceded date should be set on the cession when there is no other retrocession linked. When the RPO is run and there is no other retrocession on this cession transaction should be skipped since there is no treaty retrocession to be processed

Aim of function

The aim of the function is to default an accounting classification when there are multiple matching accounting classifications for retrocession cession

Business value for customers

When there are multiple accounting classifications on the OCC, the retrocession cession order will not automatically close the worksheets. With this enhancement it will be possible to use the inward cession's accounting classifications on the retrocessions

Some customers do not wish to classify their accounting based on the benefit covered, and now it will be possible to generate the ACs without benefit covered or reinsurance product as a parameter

System Parameters Affected

When the flag In AC is marked as No for Benefit Covered and/ or Reinsurance Product these values will not be part of the accounting classifications

Existing functionality affected

A new flag 'Use ACs from linked cessions' is applicable on the AC window of the OCCs and this will be copied to the placements and sections

When this flag is selected and the retrocession cession order is run, the ACs from the linked inward cessions will be used to create the worksheets. 

Where the linked inward cessions are informational or not included in accounting, then the ACs of the OCC will be used

Also, it will be possible to generate accounting classifications without the reinsurance product and the benefit covered based on the classification rules 2 in the system parameters

Aim of function

The aim of this enhancement is to allow the Retention Corridor to the Capped Quota Share retrocessions to be applicable before the Quota Share retrocession is processed. 

On the surplus retrocessions, the retention corridor will apply to subsequent transactions and accumulation will be considered.

Business value for customers

It is now possible to apply the retention corridor before the Quota Share is applied.  When the SAR is within the retention corridor, the entire SAR will be retained and the quota share retrocession calculation will not be done

On the surplus retrocessions, the retention corridor will apply to subsequent transactions and accumulation will be considered.

System Parameters Affected

None

Existing functionality affected

A new flag 'Apply Retention Corridor before the Quota Share' is available on the Retention Corridor window of the Capped Quota Share OCC

When this flag is selected then the retention corridor will first be validated and applied before the QS retrocession

For Surplus the retention corridor for percentage is applied for new business and subsequent transactions

For Surplus when the retention corridor is defined as an amount this will be applied to subsequent transactions.

Aim of function

The aim of the function is to be able to create proportional claims without a link to a cession benefit and perform the recovery of such claims through the RCPO

Business value for customers

It could be possible that for some customers, the claims are handled independently and are interfaced from a separate claims system. To support handling of claims without the need for an already created cession / retrocession for recovery, it will now be possible to create a proportional claim by entering all the necessary details on the claim record itself

System Parameters Affected

None

Existing functionality affected

A new type of claim 'Standalone Proportional Claim' is now available for manual retrocessions and non- ceded statuses such as Valid, Paid, In Payment, Special Paid, Update Claim Reserve

It will be possible to process the recovery claims through the RCPO based on the ceded % that is entered on the claims

Aim of function

Improve UX and UI of SICS Life Screens in Business conditions and cession

The Business >> General tab is improved by proper alignments of all fields . 

The Accounting Info tab of business is improved by removing the fields that are not using in life launcher and proper rearrangement of remaining fields

The share condition of business is improved by proper alignments of all fields in view and edit mode 

The SR condition of business is improved by proper alignment of all fields in view and edit mode

The cancellation provision condition, and age specifications tab of business are improved by proper alignment of all fields

Cancellation Provision:

Age Specifications tab:

The Settlement, Doc and timings tab, Remittances tab and Expenses tab of claim condition of business are improved by proper alignments of fields and flags

The Term and IO information tab of cession is improved by proper alignment of all fields

The Basic premium commission tab of deductions condition of business is improved by rearranging the renewal group box 

The Insured period tab, Partners tab, Classifications tab. Life cycle tab, Amendments tab and statistics tab on business are improved by aligning the fields and group boxes

 

Business value for customers

Improved Look & feel of SICS Life application.

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function

The aim of the function is to refer to the Lookup Table/s in the SAR calculation rule to calculate the sum to be considered for retrocession

Business value for customers

The SAR calculation rule includes SAR reserve tables and Cash Surrender Value table. The Sum to be considered for Retrocession/ Reinsurance can now be calculated using flexible calculation rules and this Sum to be considered for Reinsurance will now be used to process the Retrocessions when the RPO is run

System Parameters Affected

None

Existing functionality affected

A new field 'Sum to be considered for Retrocession' is now available on the inward cession

When the SAR calculation rule is applied, the Sum to be considered for retrocession is calculated and updated on this field.  The limits on the OCC will now use the value on this field to process the retrocession cessions instead of the existing Sum at Risk field

Aim of function

The aim of the function is to be able to query the Accumulation on an insurable object through webservices

Business value for customers

Being able to query the Accumulation through webservices will make it possible for customers to be able to use the API in an interface that allows the users to view the accumulated SAR on a life as on any given date in order to make the underwriting decision before the policy is processed for reinsurance

System Parameters Affected

None

Existing functionality affected

New operation for to Retrieve Cessions and Accumulated Sum at Risk is available for Life webservices

The result of the operation will retrieve all the cessions and the total Sum at Risk as on the given calculation date