What's new
Accounting General #
SE-19544 - Avoid 'over settlement', i.e. Unsettled Amount get opposite sign compared to its Balance Amount when Pairing - Aon #
Aim of function
To display a validation error message - 'Over Settlement of Balances not Allowed' - whenever any of the balances (Driving Balance or Follower Balances) involved in the balance pairing process have an unsettled balance with a sign opposite to its original balance. This is to ensure that neither the Driving Balance nor the Follower Balances get over-settled.
Business value for customers
This will enable clients to prevent the over-settlement of balances as it is not possible to over-settle balances in the General ledger.
System Parameters Affected
A new System parameter - 'Prevent Over Settlement of Balances While Pairing' under Accounting> Balance Pairing
Existing functionality affected
- Manual Balance Pairing
- Balance pairing through createBalancePairing web service
Changed documentation
SE-18216 - Cannot create a subsection or inactive section, or delete the current section - China Re #
Aim of function
When the user from a business Section is trying to either create a sub-Section, inactivate or delete this Section and there exists bookings on this section that have not been reversed, then the system should not allow this. In addition, if the section of business link a claim, a sub-section can be created only if the status of the claim is inactive or close. A sub-section cannot be created if the state of the claim is open.
Business value for customers
Booking must be done on the lowest section level on a business and this section must be an active section.
System Parameters Affected
Do not allow create Technical Worksheet for non-leaf sections
Do not Allow Inactive Section When Bookings on this Section is not zero
Create claim only on lowest leaf section level
Existing functionality affected
- Add Child Section
- Create Child Sections
- Inactive section
Changed documentation
SE-19018 - TW-TW Mass Pairing Part 2 - SOMPO JAPAN INSURANCE INC. #
Aim of function
When running the Mass Pairing of Technical/Claim Balances order implemented by enhancement case 'TW-TW Mass Pairing' released in SICS 23.1, the below functionality is now added;
- The available Booking Year and Period currently is extracted from <default settings> of base company specific settings and not taken from specific base company settings for the given Base Company.
- If only one Base Company is given on the order, then only one Booking Year and Period shall be available and taken from this BCs default booking terms for Balance Pairing.
- If multiple Base Companies are given on the order, then the available Booking Year and Periods shall be the union of default booking terms for Balance Pairing from all the given Base Companies and the user have to select one of them.
- If there are no default booking periods defined for Balance Pairing for the given Base Company on the order, then the drop down for the Booking Year and Period is empty.
When running the order, the system will only extract balances matching the Booking Year and Period on the order, i.e., existing functionality. - Note! If the Booking Terms for the given base company have been changed after the order has been created, so that the Booking Year and Period field becomes blank and not visible on the order, then the validation of missing Booking Year and Period must appear if the user tries to run the order. This means, the user must edit the order and select a valid Booking Year and Period before the order ran.
- Text string in parameter was initially not position free. For example, if in system parameter 'Reversal' is mentioned and in worksheet title 'Reversal of TW1234' or 'This is Reversal' is mentioned, then driving balance will not be extracted, as text string is not matching exactly. The string is now position free as per the requirement given, so that the balances on both of the above worksheets are extracted. Additionally, it is made none case sensitive, i.e., if the text string in the system parameter is 'Reversal', then worksheet with title 'Reversal', 'REVERSAL' and 'reversal' shall be extracted.
- If Business partner is not given in order and we have balances to pair from different Business IDs with different partners, then pairing is not done when we run the order. If balances of 2 different Businesses have same Business Partner, then pairing can be done. The pairing now take place even if multiple business partners are provided in the order.
- If Closed Date is not defined in order, then the system is not doing any pairing. When a new order is created, the Closed Date is defaulted to today's date and this will work fine. If the date is changed to an earlier date this will also work fine. But if the date is removed then the system now acts as if the current date is given in the Closed Date field.
- Functionality to view multiple business partner field in new mass pairing order, which was implemented for Mass Pairing in the enhancement 'Manual BP Entry in Business Partners in Mass Pairing' (SICS 23.1), was missing in the new order. This is now implemented for the Mass Pairing of Technical/Claim Balances order.
- In the Mass Pairing of Technical/Claim Balances Order window, a new tick box with the label 'Exclude Inactivated Business Partners' is added. It is placed below the Business Partner(s) field. If this new tick box is selected (this is the default value) when the order runs, the system will check each partner on the balances before the matching takes place and if a partner (either on the driving or the included balance) in the pairing is not Active (the Active box is not selected in the partner's properties), then this partner is ignored and the pairing cannot take place. If the box is unticked on the order, the system will also do pairing between balances even if the partner involved is inactivated.
- The update of pairing information in Notes on the Driving Balance in the pairing will be updated AFTER the existing text, i.e. at the end of the Notes page for this balance.
Business value for customers
When reversal of technical or claim balances have been done by users without access right to perform balance pairing, the system will leave the two balances Unsettled. Then the user with access right to perform balance pairing will be able to run this new mass pairing order so that all reversed source and target balances becomes automatically paired and settled.
System Parameters Affected
Driving Balance String for Mass Pairing of Technical Balance
Existing functionality affected.
Balance Pairing of Source and Reversal Worksheet.
Changed documentation
SE-19014 - Automatically book target tax amount when trigger amount is detected on claim worksheet originating from CM message- Part 2 - Swiss Re Zurich #
Aim of function
With Acord Standard 2016, claim related tax amounts are presented on the TA Claim Signing message then the referring CM message that creates the claim worksheet which presents the tax trigger amount should also automatically generate the target tax amount on the claim worksheet.
Business value for customers
Achieve automatic message processing for claim movements with tax amounts. After implementing this change there is no discarding of messages and no manual bookings necessary in case of claim related tax amount situation.
System Parameters Affected
Removed the following fields from Government tax rule table.
• 'Message Function excluded'
• 'Exclude All'
• 'Applicable for Technical WS'
• 'Applicable for Claims WS'
Existing functionality affected
The fields 'Applicable for Technical WS' and 'Applicable for Claims WS' are automatically updated to active from backend for all the Government tax rules.
Changed documentation
Business #
SE-18215 - Require current date to be later than insured period from at registration complete - China Re #
Aim of function
To ensure that a definite contract is ready to be processed, the system offers the possibility to indicate that the registration is complete. Sometimes there are regulatory requirements stating that a contract cannot commence before the contract's start date has reached today's date. When setting the registration to complete, the system should therefore ensure that today's date is equal to or greater than the insured period from date.
Business value for customers
Meets regulatory requirements.
No contract is complete before the start of the contract period
System Parameters Affected
Require Complete Registration
Prevent Completion Before Period Start
Existing functionality affected
Maintain Registration Complete on existing business
Create Business
Update Business
Change Business Life Cycle Status
Renew Business Manually
Maintain Business in Programs
Maintain System Parameters
Set Registration Complete by Web Service
Changed documentation
Claim, NP Recovery, Cede #
SE-18338 - CEDE Light Policies - User Interface Clean Up - DXC #
Aim of function
Our goal is to enhance functionality by implementing Policy Light User Interface adjustments. These adjustments involve removing group boxes, improving field alignments, and enhancing the navigation bar. By doing so, we aim to create a more streamlined and user-friendly interface for our customers.
Business value for customers
1. Eliminating group boxes can make forms look cleaner and more streamlined, this can make forms easier to scan and understand, which can lead to fewer errors and a better user experience.
2. Improving field alignments can make forms look more professional and polished. This can create a more positive impression on customers, which can lead to increased trust and loyalty.
3. Improving navigation bars can make it easier for customers to find what they are looking for. This can lead to shorter customer journeys and improved customer satisfaction.
System Parameters Affected
n/a
Existing functionality affected
n/a
Changed documentation
SE-19083 - Enhance Recovery Calculation - View Source Claim bookings - DXC #
Aim of function
Improve Source Claim Bookings View – showing accumulated inward source bookings included for the current OCC Claim Booking As-of-Date
The list is accumulated per Inward Business, Claim, Currency and Accounting Classification (picture1)
and is based on NONPROP_REC_DETAIL table.
It also shows the distribution at OCC Claim at accumulated level (picture2).
The information is available for Non-Prop Treaty OCC, Non-Prop Fac OCC and US Quota Share
Business value for customer
New improved view available directly from OCC Claim list – showing inward source claims at an accumulated level
System Parameters Affected
None
Existing functionality affected
Recovery Calculation for Protection Program
Recovery Calculation for single OCC
Recovery Calculation for US Quota Share
Changed documentation
/sicsdocs/user_guide/pc/non_prop_retro_ceded_accounting/source_claim_bookings/
eMessaging #
SE-15725 - Remove EDI Component - DXC #
Aim of function
The EDI component of SICS will no longer supported in 23.2 and higher. The EDI component will continue to be supported in older versions for as long as they are contractually supported. The functionality is still present for viewing historical data. It will not be supported in DXC Assure Reinsurance.
Business value for customers
N/A
System Parameters Affected
N/A
Existing functionality affected
N/A
Changed documentation
/sicsdocs/user_guide/pc/edi/edi_and_sics/
SE-18250 - TA eMessage Due Date instead of the Instalment Due Date - Renaissance Re #
Aim of function
Introduce a new Modify rule which takes the Technical Account (TA) eMessage Due Date instead of the Instalment Due Date. When linking a Technical Account (TA) eMessage to an instalment and with this rule active, the Due Date of the TA eMessage should be used, instead of the P/L Instalment Due Date. If TA eMessage does not contain any Due Date, the P/L Due date will be used.
The new rule prevents the Due date in the Technical Account (TA) message to be replaced by Instalment due date from DXC SICS, on the Technical Worksheet (TWS). As-is, this creates a mismatch between the Financial Account (FA) due date and the Technical Worksheet (TWS), also the Balance doesn't settle on the Business Ledger (BL).
Business value for customers
The new rule prevents mismatch between the Financial Account (FA) due date and the Technical Worksheet (TWS). Also, the balance the Business Ledger (BL) will be correct using this new rule.
System Parameters Affected
N/A
Existing functionality affected
Process eMessaging messages
Changed documentation
SE-18594 - Keep Own Incurred parameter for B2B/eMessaging - Renaissance Re #
Aim of function
For B2B/eMessaging , the parameter 'Keep Own Incurred' is to be considered the same way as it is for manually created FGU Advisory entries.
Business value for customers
Achieve the functionality of a parameter through eMessaging.
System Parameters Affected
N/A
Existing functionality affected
Processing of eMessages (B2B)
Changed documentation
SE-18942 - FA Message - FAI Rejected Outward L4 Ack Message does not have Error Indicator - Renaissance Re #
Aim of function
Introduce the ability to reject the Settlement messages with an error indicator.
Business value for customers
When rejecting the Financial Account Items individually or simultaneously, the system will send an 'Acknowledgement' with an error indicator.
When rejecting the Settlement message, the system will send an 'Acknowledgement' with an error indicator.
Applicable for both B2B and London Market messages.
System Parameters Affected
N/A
Existing functionality affected
Processing eMessages.
Changed documentation
/sicsdocs/user_guide/pc/emessaging/highlights/#discard–reject–restore
SE-19198 - Automatic Claims Creation: set State Location based on CM message - Renaissance Re #
Aim of function
Set 'State Location' on a claim, during the automatic claim creation.
Business value for customers
When creating the automatic claim (using any of the available options) from the eMessage, the system will generate the respective 'State Location' in the 'Locations' field of a claim, only if the mapped sub entity on the message is under the 'Risk Territory' of the contract.
• If the mapping is not defined or the message does not contain any sub entity 'Location', then it will work as it was working previously.
• If the mapped sub entity on the message is not under the 'Risk Territory' of a contract, then it will work as it was working previously.
Applicable for both B2B messages, and London Market messages.
System Parameters Affected
N/A
Existing functionality affected
Processing eMessages.
Changed documentation
/sicsdocs/user_guide/pc/emessaging/information_on_claim/#locations
SE-19200 - Automatic Claims Creation: set Line of Business based on CM message - Renaissance Re #
Aim of function
System to update the respective Class of Business on the claim during the automatic claim creation.
Business value for customers
When creating the automatic claim (using any of the available options) from the eMessage, the system will generate the respective class of business on the claim, only if the mapped class of business on the message is matched with the class of business on the contract.
• If the mapping is not defined or the message does not contain any class of business, then it will work as it was working previously.
• If the mapped class of business on the message is not matched with the class of business on the contract, then it will work as it was working previously.
Applicable for both B2B messages, and London Market messages.
System Parameters Affected
N/A
Existing functionality affected
Processing of eMessages.
Changed documentation
/sicsdocs/user_guide/pc/emessaging/information_on_claim/#classification
SE-19205 - Validate Claim Headline Loss When No Unique Match - Renaissance Re #
Aim of function
Set the flag 'Allow change Applies to First Message for Claim' to true on rule ValidateClaimHeadlineLossWhenNoUniqueMatch.
Business value for customers
The customer can select/unselect the flag 'Only applies to first message for claim' on rule properties of the ruleset. The system defaults the flag 'Allow change Applies to First Message for Claim' to true on the rule 'ValidateClaimHeadlineLossWhenNoUniqueMatch' and by this flag system administrator is able to select the flag 'Only applies to first message for the claim' on rule properties of the rule set.
System Parameters Affected
N/A
Existing functionality affected
Processing of eMessages.
Changed documentation
SE-19547 - New Modify rule that will eliminate ClaimReferenceRule requirement for DOL - Renaissance Re #
Aim of function
To introduce a new modifier rule ModifyClaimReferenceIgnoreDateOfLoss that will eliminate a ClaimReferenceRule requirement for Date of Loss (DOL).
Business value for customers
When the new rule ModifyClaimReferenceIgnoreDateOfLoss is on, the system will not consider the need for matching Date of Loss (DOL), and it attaches a claim only if any claim references on the message match with the references on a claim. If the rule is not in force, then it will work as previously.
Applicable for both B2B and London market messages.
System Parameters Affected
N/A
Existing functionality affected
Processing of eMessages.
Changed documentation
SE-19550 - Lloyds RiskCodeValidationRule - allow for it to apply to first message on claim only - Renaissance Re #
Aim of function
To set the flag 'Allow change Applies to First Message for Claim' to true on rule LloydsRiskCodeValidationRule.
Business value for customers
The customer can select/unselect the flag 'Only applies to first message for claim' on rule properties of the ruleset. The system defaults the flag 'Allow change Applies to First Message for Claim' to true on the rule LloydsRiskCodeValidationRule and by this flag system administrator can be able to select the flag 'Only applies to first message for the claim' on rule properties of the rule set.
System Parameters Affected
N/A
Existing functionality affected
Processing of eMessages.
Changed documentation
SE-19634 - Lloyds TA RIP - previous message - Renaissance Re #
Aim of function
Introducing a new matching rule 'Contains' in reference data table 01217, which can be used by PreviousMessageMappingRule.
Business value for customers
Introducing the new matching rule enables to select the matching rule 'Contains' in the previous message mapping.
When it is selected for any of the XML components, using the PreviousMessageMappingRule, the system will check if the previous message xml component value is contained in the current message or not. If it is, then the system will make an automatic reference of business/claim on the Lloyds TA RIP Message.
System Parameters Affected
N/A
Existing functionality affected
Processing eMessages
Changed documentation
Life #
SE-18343 - Block creation of retrocession cessions if premium calculations fail when running the RPO - DXC #
Aim of function
The aim of the function is to be able to prevent the retrocessions from being created by the RPO if the ACIs are not calculated on the retrocessions
Business value for customers
When the premium ACIs (and other ACIs that are dependent on the premium) are not created, the retrocession cession continues to be created without any ACIs.
It is also not possible to easily identify such retrocessions and ACIs cannot be added manually after the retrocession has been created.
If a retrocession cession is created without any ACIs it will result in discrepancies in the accounting process.
Now, it is possible to prevent creation of a retrocession cession when there are no ACIs created
System Parameters Affected
None
Existing functionality affected
A flag 'Create Retrocessions even if ACIs are not created' is now available on the RPO
This is selected by default
Where the OCC has premium rate lookup tables that have been defined such that the premium is to be calculated based on parameters available on the inward cession (eg: Smoker Status, Occupation Class, Occupation Code etc), then when the necessary value is not available on the inward cession, it will mean that the value will not be copied to the retrocession and therefore result in the Premium ACIs not being created.
When the above mentioned flag is selected and the inward cession does not have the necessary parameters for the retrocession ACIs to be created, then the cession will be listed in the failed assignments and the retros will not be created
Note: The current implementation is limited to only validating reference data values in the premium rate Lookup Tables on the OCC against the values available on the inward cessions. Any other calculations (such as missing Age values, missing inward cession ACIs for As Original or Retro Share of Original) will not be supported and the retrocession cessions will continue to be created without ACIs
Changed documentation
SE-18895 - Retention Corridor for Capped Quota Share - DXC #
Aim of function
The aim of this enhancement is to introduce a Retention Corridor to the Capped Quota Share retrocessions
Business value for customers
When a retention corridor is defined for a Capped Quota Share business, then when the sum to be retained is within the defined retention corridor, but exceeds the defined capped retention amount, the amount will be retained
System Parameters Affected
None
Existing functionality affected
Only when the system parameter 'Sum at Risk Reinsured Sequentially in excess of retention' is selected.
A new tab 'Retention Corridor' is available on a Capped Quota Share OCC
Only Monetary Amount will be considered, any value defined as a percentage will be informational.
When the sum to be retained as calculated by the RPO falls above the defined capped retention, but this is within the retention corridor that has been defined on the condition, then instead of the amount being Unplaced, this amount will be considered as retained.
Note: This retention corridor is applicable only to the first transaction that is retroceded and will not be considered when the subsequent transactions have changes in the SAR. Also, the retention corridor will not be accumulated and will be applied on only one cession benefit that has been processed sequentially.
Changed documentation
SE-19169 - Handling of Proportional Claims without Cessions - DXC #
Aim of function
The aim of the function is to be able to create proportional claims without a link to a cession benefit
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
This claim can be created without the link to a cession
The claim loader now has an output pattern that is specific to a Standalone Proportional Claim where there will be no referencing to an inward cession
Note: The current implementation is limited to creating an inward proportional claim only. No retrocession claims or claim recovery is possible
Changed documentation
SE-19359 - Extended Term Transaction Handling for any change in expiry date - DXC #
Aim of function
The aim of the function is to use the current 'Extended Term' transaction to also reduce the term on a cession benefit, thereby creating the necessary reversals of account costing items where applicable
Business value for customers
When the term of a cession is reduced, then the existing transactions that had already been created with the account costing items should be reversed and adjusted as per the new benefit expiry date. This functionality will allow the user to create the necessary reversals and adjustments
System Parameters Affected
None
Existing functionality affected
The 'Extended Term' Amendment transaction on a cession benefit will now be applicable to reduce the term also
When the policy expiry date is to be updated as a backdated transaction then the effective date of the Extended Term Transaction will be equal to the new Benefit Expiry Date. All ACIs will be reversed and refunded based on the definition on the AC condition
Changed documentation
SE-19591 - Reinstatement Handling with changes to Cession details - DXC #
Aim of function
The aim of this enhancement is to allow flexible reinstatement options where the benefit that has been terminated can be reinstated with terms and conditions that are different from the original cession benefit
Business value for customers
Through this new type of reinstatement, the customer will be able to reinstate the terminated benefits from a specific date, up to a specific date and also, update the cession benefit with additional loadings or changes to the insured's occupation etc in the reinstatement transaction
System Parameters Affected
None
Existing functionality affected
A new type of Reinstatement transaction 'Reinstatement with Updates' is now available
When this transaction is created on a terminated cession the following functions are possible
1. The reinstatement may be created for specific effective periods only
2. It will be possible to update the details on the cession benefit such as SAR, loadings, occupation class etc on this transaction
3. When this reinstated transaction is picked up by the RPO the corresponding retrocession transactions will be processed based on the available retention and capacity as on the date of running the RPO, using the updated values on the reinstatement transaction
Changed documentation
SE-19545 - When the system parameter is selected the user will not be allowed to change the insured period start date or underwriting year - Qianhai Re #
Aim of function
The aim of the function is to prevent update in Underwriting year on a definite business
Business value for customers
The business value for customers is that it will now not be possible to update the insured period start date and therefore change the underwriting year on the business
System Parameters Affected
New system parameter 'Prevent update of Insured Period Start date or Underwriting Year on a Definite Business' is now available under Business -> Insured Period
Existing functionality affected
When the above-mentioned system parameter is selected, then the user will not be able to change the insured period start date or underwriting year on a definite business.
Changed documentation
Other #
SE-19184 - Generate SOAP API Documentation - DXC #
Aim of function
Generate and publish SOAP API Documentation on SICS Docs. The generated documentation in this release will provide basic information on the available APIs and some simple statistics, such as count of webservices per entry point, total, etc.
The new solution will eventually replace the hand written Word documents with 'doc-as-code' that generates full documentation from the API specifications.
Business value for customers
Provide easily accessible, up to date generated documentation for SOAP webservices for SICS API Server.
System Parameters Affected
None
Existing functionality affected
None
Changed documentation
SE-19930 - SICS UI/UX Improvements Life - DXC #
Aim of function
Improve UX of SICS Life Screens in Business and Cession areas.
The Term & IO Information Tab of Joint Life Cession & Retrocession is improved by proper alignment of all the fields and Creation of new tab named as Individual Specific life data.
The Standalone Individual Retrocession creation screen is improved by proper alignment of All fields.
The Business Highlights Tab is improved by removing the General Group box under the General Tab.
The Additional Scope (AS) condition of Business is improved by removing the Original Conditions Group box on the Original Condition Tab.
Business value for customers
Improved Look & feel of SICS Life application.
System Parameters Affected
N/A
Existing functionality affected
N/A
Changed documentation
This report was generated Thu Jun 22 09:13:47 UTC 2023.