Release documentation - Life - Enhancements and requests

Problem:
Import Remittance Worksheet from Spreadsheet function - 'Partner's Bank Account' field length of 20 is not enough.

Solution:
For import remittance worksheet from Spreadsheet, the 'Partner's Bank Account' field length to be increased to 40 as same as 'Bank Account' field.

Problem:
Reserve and Deposit Details Mass Update generate worksheets in both Booking Currency and Account Currency in SICS Life.

Decline Reason
This is not a bug and works as it is.

Problem:
Error message in Assure Preview Mode

Solution:
In Assure Re on opening a business and navigating to the Structure Tab it should be possible to view the created structure if any or any other details on the Structure tab without errors

Problem:
Missing Document for Web Intelligence reports from unv to unx universes using Workflow Assistant - Automation Framework.

Solution:
Need to include this document in GITHUB side so that it can automatically generates with latest versioning to include in delivery folder and SICS SYS Admin guide.

Problem:
Policy year is not getting updated automatically during policy anniversary for monthly cession. Issue persists for both Manual and Loader.

Solution:
 The policy year should be defaulted as 1 for the first transaction on the cession benefit if no value is entered/ mapped
If a specific value is entered or mapped then the mapped/ entered value should be considered as the policy year of the transaction

Calcualtion of Policy Year should be based on the Policy Anniversary
Irrespective of the calculation frequency, the policy anniversary will always be 12 months after the reinsurance start date and every 12 months after that

Policy Year =1+ number of full years completed as of the transaction effective date, from the reinsurance start date.

If a transaction occurs before the next anniversary, it belongs to the current policy year.
If a transaction occurs on or after the next anniversary, it rolls into the next policy year.

Always calcualte the Policy Year for each transaction as per the above rule. If the user overrides it, accept the overriden value. But for the next transaction, again do the automatic calculation as per the policy anniversary logic.

Problem:
 
System is not referencing to the correct Child Section of OCC for a non ceded cession with OldBusiness transaction.

Solution:
 
When there are child sections on the OCC and there are unique child sections then when the cession benefit is being retroceded either manually or through the RPO identify the lowest child section that has the same benefit covered and insurance product and retrocede the cession benefit to that child section
This should be applicable to New business and Old Business transactions
This should be applicable to non-ceded cessions where there is only benefit covered and insurance product on the cession benefit.
If the OCC has more than one child sections on the lowest level that have the same benefit covered and insurance product then link the retroceded cession to any matching section randomly. All subsequent transactions should be processed on the same child section

All calculations and validations should happen based on the terms and conditions defined on the respective child section
 

Problem:
Incorrect ACI on cancel from inception transaction when processed after renewal

Solution:
 Irrespective of the PM condition definition on the business whenever there is a reversal transaction created due to a Ceded in Error, Cancelled from Inception or Setup In Error transaction, ALL the existing ACIs on the cession benefit should be reversed as is without any recalcualtion. For each transaction the corresponding reversal should be created with the ACIs from the source transaction reversed

If there is a reversal ACI calculated on the ceded in error / set up in error/ cancelled from inception transaction (which will be a reversal of the first transaction - New Busienss or Old Business) and there is an ACI value mapped in the input file for this transaction with the SAME entry code as the reversed ACIs then override the automatically calculated reversal ACIs and use only the mapped value

Problem:
Incorrect ACI on 'Lapse Transaction' when processed between NB and Renewal on NB transaction period on a ceded cession with PM condition as 'As original'

Solution:
When the Unearned Premium Return option is selected as Original on the AC condition, irrespective of the premium definition on the PM condition never calculate the pro rata ACIs for a termination transaction

Always accept the mapped value or the value entered manually for the transaction

Problem:
Incorrect ACI's updating on retrocession and placement when multiple other transactions created on a cession in one batch.

Solution:
If the system parameter 'Sum at Risk Standalone Retrocesision only- is NOT selected'

Before processing records of each policy, check if there are any records having same transaction code and transaction date.
if yes then Before processing records, update the transaction number for each of those records with the
next transaction number for that benefit and increment by 1 for all these type of records to differentiate them and
remove this number before committing in DB. If no, then the records will be processed as per the existing functionality.

Functionally, the result should be as below:

The retro ACIs that are being calculated automatically when the inward cession transactions are created should always be created per transaction. When the PM condition on the OCC is set as Original for premium basis then the ceded % should be applied to the inward cession ACIs and this should happen for each transaction separately

When there is more than one placement, the retrocessionaire percentage should be applied to the ACIs calcualted on the retrocession level for each transaction separately and be calculated as the placement level ACIs

This will be applicable for ACIs created when the retrocession is done through SIngle Treaty Protection and Quota Share Retrocession (QSR- from the PP condition defined on the AB) and when the reetrocessions are created without running the RPO when the system parameter Retrocession Basis : Sum at Risk Standalone Retrocessions is NOT selected

The retro ACIs that are being calculated automatically when the inward cession transactions are created should always be created per transaction. When the PM condition on the OCC is set as Original for premium basis then the ceded % should be applied to the inward cession ACIs and this should happen for each transaction separately

When there is more than one placement the retrocessionaire percentage should be applied to the ACIs calcualted on the retrocession level for each transaction separately and be calculated as the placement level ACIs

Problem:
Issue with MultiGAAP Accounting Order while executing with close worksheet option - MultiGAAP Life

Solution:
In the Life Area Multi GAAP module, we will ensure that the MG Accounting order does not abend while running the order on the Close Status worksheet.

Problem:
On a Cession, for Old Business transaction, system is calculating the Issue Age.
 

Solution:
If the transaction is Old Business and a value is mapped to the Issue Age transaction or Adjusted Issue Age then do not recalcualte it absed on the Age definition mentioned in the PM condition. If no Age is mapped, then calculate the age as per the PM condition definition
For any other type of transaction, always calculate the Issue Age, Adjusted Issue Age and Transaction age as per existing functionality
 

Problem:
Incorrect ACI calculation during Other Transaction when PM condition has LUT table defined

Solution:
 Irrespective of the PM condition definition on the business whenever there is a reversal transaction created due to a Ceded in Error, Cancelled from Inception or Setup In Error transaction, ALL the existing ACIs on the cession benefit should be reversed as is without any recalcualtion. For each transaction the corresponding reversal should be created with the ACIs from the source transaction reversed

If there is a reversal ACI calculated on the ceded in error / set up in error/ cancelled from inception transaction (which will be a reversal of the first transaction - New Busienss or Old Business) and there is an ACI value mapped in the input file for this transaction with the SAME entry code as the reversed ACIs then override the automatically calculated reversal ACIs and use only the mapped value

Problem:
Abend when running the RPO

Solution:
Irrespective of whether there is a Premium Calculation Rule defined or not, on any level of business involved in the RPO calculations:

When the PM condition on the placement level is not overridden then the ACIs that are calculated on the retrocession cession level should be retroceded to the placements in the defined percentage

When the PM condition is overridden on the placements, then the premium should be calculated on that particular placement independent of the definition on the OCC level

This will apply to any ACI that is calculated using the premium as a basis - eg deductions or any ACI that is defined as a separate value that is not dependent on the premiums - eg: Other Deduction as a fixed amount

Problem:
The ACI's on the cession are in suspended status when the previous transaction is Suspended

Solution:
For any cession benefit transaction that is created on an actual cession through the loader the ACI status should be set to Released by default irrespective of the status of the earlier ACIs.
This is irrespective of whether the subsequent transactions have new ACIs created or not.
The ACIs will be set to suspended by default only if the created cession is an informational cession

Problem:
Deductions not calculated correctly when premium is Retro Share of Original

Solution:
When the premium basis is Retro Share of Original then the retro premium should be calculated as Inward Premiums (all types of ACIs that are calculated for Basic and Extra Premiums) * ceded percentage. Any deductions or commissions that are to be calcualted based on the premiums should then be calculated using the calculated retro share of original premium

Problem:
Cession and Claim Loader | Amount with negative sign not considered when creating ACI

Solution:
The ACI on the cession benefit transactions AND claim transactions should be created using the following logic when the ACIs are either entered manually or mapped values are created through the loader. This works as expected manually, and the loader should follow the same logic.

If 'Positive on Assumed Business' is selected
The ACI retains the sign of the mapped value.

If 'Positive on Assumed Business' is not selected
The ACI is created with the opposite sign of the mapped value.

Problem:
Unable to create RPO when PP and OCC has multiple Base Companies.

Solution:
 When the PP on the RPO has more than one Base Company, then check if the Base Company of the included AB is a subset of the PP's Base Companies. If it is, then allow the RPO to be saved and process the cessions as per existing functionality

Problem:
Performance issue of running quarterly accounting order - mantis 8862 ( 3rd quarter from 1-7-2024 to 30-9-2024)

Solution:
Optimise the performance of the Retrocession Cession Order and Cession Order.

Problem:
On Webservices, System generates Walkback on adding the Qualifier on adjustment for the PM condition
 

Solution:
When any qualifier value is added to the Extra Premium and Adjustment Tab and this qualifier is part of the lookup table allowable columns the values should be accepted and created on the PM condition through webservices without abend
If the values do not exist then ignore the qualifier, if incorrect values are part of the qualifier then the error message should be thrown - whatever error message is thrown manually

Problem:
In attach additional OCC option the OCC ID field is disable in linked env.

Solution:
When the system paramter 'Sum at Risk Standalone Retrocessions only' is NOT selected:

The option to add additional OCC should be enabled and the user should be allowed to select an OCC that is not linked to a PP and attach it as part of the retrocessions until the entire SAR to be retroceded is fully placed

Problem:
RPO is processing cessions even if placement completed is not set

Solution:
 If the OCC has incomplete placements / placement complete flag nnot set the RPO should not abend. The error message 'LCH080 incomplete placements shpuold be thrown and be listed in the failed assignemnts and the RPO should fail without abend

Problem:
NAT Re - SICS Referencing Delay for Cession File Upload- SQL database

Solution:
Update the query to work for all databases - Oracle, SQL and Postgre SQL

Problem:
The Reserve Amount from the immediate preceding ‘Ceded Outstanding’ transaction is not reversed automatically

Solution:
When the Ceded Outstanding status has an reserve created with an entry code that is mapped to the Ceded Claim Reserve in the Calculation Model, then in the subsequent Ceded Paid statuses the Reserve amount should be reversed to the value equal to the value of the amoutn defined under the entry code Loss on the Ceded Paid statuses if the Loss Entry code is the value mapped in the Calculation Model for the type of claim
This should happen both manually and through the loader irrespective of any other entry code available on the Claim status

Problem:
 The Effective dates on the RPO are not working as expected in Linked Env

Solution:
In the environment where the system parameter 'Sum at Risk- Standalone Retrocessions Only' is not selected, the RPO should accept a From and To effective date. When entered, the cession benefit transaactionss that are picked up by the RPO should have an effective start date that falls within the given dates only (both dates included) Any cession benefit transaction that has an effective start date outside these two values should not be considered.
When no dates are given, the To date should default to the current date
When no From date is given and a To date is given then all cession benefit transactions that have a date upto and including the To date should be picked up
 

Problem: Running RPO encounters memory and performance issues due to large data volume.

Solution: Plan to implement a distributed order processing approach, where order will be divided into smaller chunks and processed in parallel to optimize memory usage and improve overall performance.

Problem:
When open specific RPO and view List of uplaced Risks due to lack of Capacity, for same cession ID  have more than 1 records.

Solution:
The Unplaced Amount listed on the RPO should be the same as the value of the calculated Unplaced Amount in the cession benefit transaction
The Unplaced Amount listed should only list the latest unplaced amount that the RPO has calculated and the cession benefit should be listed only once

Problem:
System allows to select incorrect system parameter selection under Retrocession Basis.

Solution:
When the system parameter REtrocession Basis: Sum at Risk standalon retrocession only is selected then the user should be forced to select one option in the Retrocession/ Reinsurance Basis

The value Sequentially in excess of Retention should be selected by default (currently Proportionally is defaulted) and within this, the option Cession Benefit Sequence Number should be the defaulted selection.

Within this system parameter also, the user should always be forced to select one of the three available sequencing basis, Sequencing based on policy number should be selected by default

If the Retrocession Basis is not selected then the validation error 'REtrocession Basis is Mandatory for Standalone REtrocession approach' should be thrown

When the Method of Retrocession 'Sequentially in excess of...; is selected and the user does not select a Sequencing basis the nthe valiudation error 'At least one Sequencing Method should be selected' should be thrown
 

Problem:
The migration through MTK is resulting in an error.

Solution:
When any object is exported and then imported using MTK in th same format, it should be possible to import that object back into SICS. Here, there will be no validations on the duplication of identifiers. Only validations due to incorrect formats, missing mandatory fields or any functional errors (such as invalid partners, invalid ref data etc) should be thrown.

Problem:
When Loss ACI given manually with negative sign, system displaying Reserve with Positive amount.

Solution:
 The claim reserve ACI that is automatically reversed in the CPaid transaction should always have a sign opposite to that of the Claim Reserve ACI in the Ceded Outstanding transaction AND this should be the opposite sign of the Loss ACI in the Ceded Paid transaction

Problem:
Issue with automatic claim reserve calculation when reserve ACI added manually.

Solution:
 
When Reserve ACI is getting calculated automatically to be reversed (reduced from the available reserve amount) in the CPAID transaction, it should always consider the reserve amount of 'COUT' transaction only.

Any reserve ACI added during CPAID status should not be considered while balancing reserve. If a reserve entry code is added in a CPAID transaction then it should be treated as any other type of entry code

Solution:
 When there are reversal transactions automatically created on the inward cession when there is a backdated termination then all the transactions after the termination date on the retrocession cession should also be reveresed if they already exist on the retrocession cession when the full recapture transaction is created through the RPO

Problem:
Automatic Reversal transactions not created on the retrocession cession and placements when there is a backdated termination on the inward cession that has been retroceded

Problem:
System not allowing to attach OCC on the cessions which has multiple cedents.

Solution:
 Where the OCC has multiple base companies it should be possible to attach this OCC as a manual Facultative retrocession on a cession benefit linked to an AB that has one of the base companies on the OCC as a reinsuerer business partner.
When the Renew Facultative Retrocessions Order is run with one or more of these base companies as part of the criteria, the facultative retrocessions should be picked up by the order and renewed

This is irrespective of the Retrocession Basis system parameter setting

Problem:
 Add currency options is disabled on the Technical Worksheet when business is accessed through Claims

Solution:
 Irrespective of from where the business is accessed from, if the user clicks on the create technical worksheet option from the business level it should be possible to add currency and create the technical worksheet

Problem:
'Transaction Reversal' transaction is not getting Suspended when Original Transaction is Suspended.

Solution:
 If the source transaction has a status of Suspended then the ACI of the Reversal transactions that are created from the Source Transaction should also get the status of Suspended. This is applicable to both cessions and claims

Problem:
The Webservices fails with the Validation error on adding the Qualifier as User defined Fields on adjustment for the PM condition
 

Solution:
System should execute the SOAP and create/update the condition with values defined on SOAP. If any required value are missing from the SOAP system should throw the respective error message.

Aim of Function

The Aim of the Function is to Streamline Standalone Claims to capture more details.

 
Business value for customers

 The Standalone Claims will now have additional fields and functions. It will also be possible to identify worksheets that have been created from the Standalone Claim with a separate identifier series

System Parameters Affected

A new type of Worksheet- Standalone Claim is available for selection for Worksheet Identifier Series

Existing functionality affected

1. The Group Info and Other Info tabs from the Cession and Cession Benefit will now be available on Individual Claims and the tabs will be available for input on Standalone Claims

Group Information Tab

Other Information Tab

For Individual Claims, this is copied from the Cession Benefit and for Standalone Claims this is open for input, both manually and through the loader

2. When the Technical Worksheet is created from a Standalone Claim, the worksheet will be created using the identifier series defined for Standalone Claims

Aim of Function

This feature will allow the user to be able to view the accumulated Claim Liability and other details on a claim for each insurable object.
This feature will allow the user to apply the Domain Restriction that controls creation of ACIs in a Released status based on claims accumulation.

Business value for customers

Customers will now be able to define a domain restriction that prevents including the ACI in accounting based on the accumulated claim liability amount
It will also be possible to view the Claim Accumulation from the Individual Insurable Objects

System Parameters Affected

New Security Domain Restriction is available 'Life Claims Set Release Indicator'

Existing functionality affected

1. On the Individual Insurable Object, the Accumulated Claim Liablity for both Inward and Outward Claims is available, similar to Cession Accumulation

2. A new Domain Restriction is available, and when assigned to a user, the claim ACIs that are created when the Accumulated Claim Liablilty exceeds the Domain Restriction amount will be set to suspended

Aim of Function

The aim of this enhancement is to define domain restrictions for insurable objects for data privacy

Business value for customers

 It will now be possible to restrict certain users from accessing personal information related to the insurable object based on domain restrictions

System Parameters Affected

New Domain Restriction ' Life Insurable Object Identifier Type' is available

Existing functionality affected

When the Domain Restriction is set, then users will only be able to view the Insurable Object and personal details of the Insurable Object on Cessions and Claims if the Identifier type is allowed as per the Domain Restriction. For all other types, the data will be masked

Aim of Function

When the Premium basis is As Original set auto-reversed ACI of all such subsequent periods as ‘Suspended’
 

Business value for customers

Now, instead of recording each reversal transaction separately in accounting, only the total reversed amount that is calculated/ entered on the latest reversal transaction will have an accounting status of Released and be available for inclusion in the accounting process.

System Parameters Affected
None

Existing functionality affected

A new flag is available on the PM condition ' Set Reversed ACIs to Suspended'

This will be available for selection when the Rates/Amount Option on the PM condition is Original

When this flag is selected, any automatically reversed Cession ACI will be set to suspended