What's new
Accounting General #
SE-22677 - Create Remittance Worksheet via upload function - part 2 - Achmea Reinsurance Co #
Aim of function
A spreadsheet can be used to describe all the required (mandatory and optional) remittance fields in a specific format. Some fields are required, while others are optional; however, in some situations, optional fields must also be provided based on system parameter in SICS. The system creates the relevant remittances in SICS, including the necessary validations, so that the remittance balances are stored in the database as if they were manually made, i.e., using the same validation and the current system parameter settings for remittance balances.
New option is added in the Find Accounting Worksheet window - 'Import Remittance Worksheet from Spreadsheet'
Business value for customers
Instead of creating remittance balances one by one in SICS it is more efficient to prepare this in a spreadsheet file and upload several remittance balances in a bulk process.
System Parameters Affected
None
Existing functionality affected
Create Remittances
Changed documentation
/sicsdocs/user_guide/pc/accounting/find_ws/#import-remittance-balances
SE-23017 - Multi-GAAP Calculation Editor Improvements - Part 2 - DXC #
Aim of function
Improve the usability of the Multi-GAAP calculation editor in system parameters.
We introduced a searchable hierarchy of calculation functions and operators to make it easy to find the value you need faster when editing a calculation.
Business value for customers
Customers can now have a modified user interface with all available items in a searchable tree to insert into calculation rule.
System Parameters Affected
Multi GAAP --> Calculation rule
Existing functionality affected
There is no impact to functionality. This will only improve the usability of calculation editor in Multi GAAP & underwriter estimates system parameter window.
Changed documentation
SE-18941 - Update of Level of Business Indicator/Direction when Remittance is Final - Renaissance Re #
Aim of function
User should be able to update The Level of Business Indicator/Direction even when Remittance is Final. Allowed by a new system parameter.
Business value for clients
When incoming remittances are fetched from the GL into SICS automatically, this functionality can be used to determine the Direction, i.e., Inward or Outward, on Remittance Worksheets which are set to Final. The direction may be required by the General Ledger system to record the remittance correctly.
System Parameters Affected
A new System parameter named 'Update of Level of Business Indicator on Final Remittances Allowed' under Accounting, Remittance -> Remittance Validation page. This is enabled only when the existing parameter 'Indicator for Level Of Business On Remittance Worksheet Required' is selected.
A new System parameter named 'Update of Final Remittances Allowed through Web Services' under Accounting, Remittance -> Remittance Validation page.
Existing functionality affected
The Level of Business Indicator field in the More Details tab of the Remittance Worksheet will be able to be updated even when the Remittance Worksheet status is Final when the new parameter 'Update of Level of Business Indicator on Final Remittances Allowed' is ON.
When a new Remittance Worksheet is created from scratch, the Level of Business Indicator is mandatory to give. But for the new functionality, when a Remittance with status Final is edited, the Level of Business may be updated, but it is not mandatory to be set if it is blank/none.
For the APIs, a new system parameter 'Update of Final Remittances Allowed through Web Services' will be created to allow updating the Remittances which are in Final Status. When this parameter is selected then updateRemittanceBalance API will be changed so that the Level of Business Indicator field can be updated from webserver as well.
Changed documentation
/sicsdocs/user_guide/pc/accounting/remittance_booking/#enter-details-in-the-remittance-worksheet
SE-22506 - Simplex Workstream Financial Handling – New Parameter to prepopulate Due Date/Value Date with Remittance Creation - Swiss Re Zurich #
Aim of function
A new feature to set the Due Date/Value Date on Paid Remittances equal the Remittance Creation Date + a number of days given in a new system parameter.
Business value for clients
Higher accuracy on Payment Date for Cash & Cost Ops Team & Bank payment info.
Less 'urgent' payments created in error by using the incorrect Due Date.
Automation of Approval/Authorization possible.
System Parameters Affected
New System parameter 'Prepopulate Due Date/Value Date for Remittance Creation' under Accounting>>Remittance.
Existing functionality affected
Creation of Paid Remittance.
Changed documentation
/sicsdocs/user_guide/pc/accounting/remittance_booking/#enter-details-in-the-remittance-worksheet
Business #
SE-22419 - Configure manual assignment of business identifier - Swiss Re Zurich #
Aim of function
Some companies use SICS Server to record new contracts. Some of these contracts exist in other systems and therefore already have an identifier. To keep the same Business Identifier in all systems, they give the same identifier also when recording these contract by SICS Server.
To avoid that the end user also enters identifiers manually for the contracts they create, it should be possible to set up the system to allow manual Business Identifiers only when the contract is created by Web Service API.
Business values for Customer
Simplifies tracing contracts present in different systems.
Contracts have identifiers according to company guidelines.
System Parameters Affected
Manual Business Identifier only allowed when created by Web Service
Assign Manual Business ID with Auto Option
Existing functionality affected
Create new business
Copy to new business
Place Business
Create business by Web Sevices
Create Business with Sections by Web Service
Copy Business by Web Services
Place Business by Web Services
Changed documentation
Claims #
SE-21793 - Allow list of countries/areas in Claim Program - Swiss Re Zurich #
Aim of function
Allow Claim Programs to cover a list of countries/areas, instead of a single value.
The default value will be the list of locations as defined on selected business. Businesses can be added if they cover the location of the Claim Program (ie the CP location must be equal to or a subset of the locations of the added business.)
Business value for customer
Reduce the number of required Claim Programs, when only the location differs.
System Parameters affected
None
Existing Functionality affected
Claim Program administration
Claim Program APIs
Changed documentation
/sicsdocs/user_guide/pc/claims/edit_claim_program/#edit-claim-program-period-andor-classifications
eMessaging #
SE-22249 - Acord ADEPT Integration - Outbound messages - DXC #
Aim of function
Support of outbound messages via the already supported integration with ADEPT (ACORD Data Exchange Platform & Translator). The new integration plugin builds upon the sophisticated SICS eMessaging foundation to provide a next-generation market capability to increase the timeliness, accuracy, and security of business data exchange.
Business value for customers
Enabling rapid data exchange, translation, and transformation via ADEPT, the ACORD Data Exchange Platform & Translator.
System Parameters Affected
Configuration of a new eMessaging ADEPT gateway plugin.
Existing functionality affected
eMessaging
Changed documentation
SE-21170 - No Headline Loss was selected - Incorrect warning - Renaissance Re #
Aim of function
To extend the functionality of mandatory headline loss for MCOB/RU via eMessaging.
Business value for customers
System parameters:
Either one or both of the following parameters are defined:
- From base-company specific settings, claim Headline loss assignment – Mandatory headline loss link for MCOB flag with MCOB.
- Headline Loss link mandatory for reporting units.
along with other parameter 'Link to a Headline Loss is Mandatory When Closing Claim Worksheet'.
Based on the above parameters selection, the system applies the functionalities of the parameters for all the Claim Movement messages.
System Parameters Affected
- From base-company specific settings, claim Headline loss assignment – Mandatory headline loss link for MCOB flag with MCOB.
- Headline Loss link mandatory for reporting units.
- Link to a Headline Loss is Mandatory When Closing Claim Worksheet.
Existing functionality affected
Claim creation from eMessaging.
eMessage processing.
Claim status.
Changed documentation
SE-23022 - Additional eMessaging rule to keep overall incurred on Non-FGU claims - Part2 - Renaissance Re #
Aim of function
In SICS there's the possibility to activate the 'Keep own incurred' functionality on FGU claims. The customer would like an eMessaging rule which does the same, but on claims which are 'non-FGU' (FGU tick not set).
The aim would be when processing an eMessage against such a claim and with this rule activated, eMessaging to keep the overall incurred value, meaning if there are ACRs (Additional Case Reserve) booked to process a change in ACRs based, the eMessage movements to keep the overall incurred stable on the claim.
With this, its ensured that ACRs are updated as we progress on the claim and no dedicated process needs to keep in place to adjust them manually either during processing (swap to worksheet) or after processing (report and manual booking).
This enhancement should not only focus on ACR but also incorporate Client IBNR (Incurred But Not Reported). Or in other words, this should consider, ACR Indemnity and ACR LAE (Loss Adjustment Expense) as well as Client IBNR Indemnity and Client IBNR LAE entry codes.
Business value for clients
eMessage based control on overall incurred on non-FGU claims.
System Parameters Affected
N/A
Existing functionality affected
eMessage processing
Changed documentation
SE-19058 - Advised Date logic changes for eMessaging in Claim Section Update Information - Swiss Re Zurich #
Aim of function
A Claim will now be created using the message' creation date as Advised date, when a claim is created through eMessaging (process or swap to).
Business value for clients
Ensuring that a correct advised date is captured on claims, and improving further automation.
System Parameters Affected
N/A
Existing functionality affected
eMessage processing
Claim creation from eMessaging
Changed documentation
SE-22594 - New eMessaging Modifier Rule to prevent certain areas (for example LPC) from automatically populating the Remittance Due Date/Value Date and maintain the current logic - Swiss Re Zurich #
Aim of function
Wrap the setting of due date based on pre-population /calculation within an eMessaging Modifier Rule so it will always set the due date from an eMessage when the rule is active (ostensibly for Service Provider messages).
Note! Service Provider eMessaging bookings rely on Due Date set from messages and thus must not be altered. The new calculated value will not be used in this case, whereas for B2B which relies on linked messages the new functionality to change due date can still be applied.
Business value for clients
- Higher accuracy on Payment Date for Cash & Cost Ops Team & Bank payment info
- Less 'urgent' payments created in error by using the incorrect Due Date
- Automation of Approval/Authorization possible
System Parameters Affected
N/A
Existing functionality affected
eMessage processing
Changed documentation
SE-22272 - Due date to be considered from message only - Triglav #
Aim of function
A new eMessaging rule ModifyTechAccountDueDate to consider the eMessage due date when booking TechAccounts.
When the rule is in force:
- For all the TechAccount messages, the system only considers the due date of the message (i.e., balance amount item due date) irrespective of the Accounting period, Admin Condition, Adjustment Due date…etc.
- If there is no due date on the message, then it work as it works now.
When the rule is not in force:
- Then it work as it works now.
Regardless of this new rule, for the Instalment messages the control of the due date depends upon the existing rule 'ModifyInstalmentDueDate'.
Business value for clients
With the new rule in force, user can able to book all the TechAccounts as per the eMessage due date (i.e., balance amount item due date) Applicable for TA messages.
System Parameters Affected
N/A
Existing functionality affected
eMessage processing
Changed documentation
Life #
SE-21379 - Facultative Automatic Dev/ multiple Fac policies to be placed to the same Fac OCC - DXC #
Aim of function
The aim of the function is to be able to place the increased SAR to the same OCC on which the previous facultative amount was placed.
Business value for customers
When there is an increase in the SAR and there is an existing facultative retrocession linked to the cession, it will be possible to retrocede the increased SAR to the same retro partner on the same facultative agreement.
System Parameters Affected
None
Existing functionality affected
When there is an increase in the SAR in a subsequent transaction and there is an existing Facultative Retrocession linked to the cession a new option 'Adjust SAR to Existing Facultative Retrocession' is available.
When this is selected the user will be allowed to add the increased SAR that is now unplaced and available for retrocession to the existing Facultative Retrocession as long as the ACIs are already not included.
The increased SAR that is unplaced can be allocated to the same Fac OCC as long as there is capacity available on the OCC.
Changed documentation
SE-23050 - Handle Accumulation of Retrocession Cessions - View and API - DXC #
Aim of function
The aim of this function is to be able to view the accumulation on the insurable object for the retrocessions and also retrieve the accumulation for the retrocessions through an API.
Business value for customers
This will enable the customers to have a snapshot of the accumulated retrocessions at any given date similar to the inward cessions. It will also allow the customers to retrieve the accumulated retro sum at risk through APIs which may be used during underwriting.
System Parameters Affected
None
Existing functionality affected
1. Insurable Object- Accumulation Control now has an a tab 'Standalone Retrocessions'
This tab will display the Accumulated figures from the retrocession cessions
2. It is possible to retrieve the accumulation of a standalone retrocession through the RetrieveCessionsAndAccumulatedSARofIO webservice
Soap Message :
Response:
Changed documentation
SE-23051 - SAR Calculation Rule - Part 2 - DXC #
Aim of function
To be able to use more values from the cession in the SAR calculation rules including values in the 'Original policy' tab.
To be able to use the original policy frequency in a Lookup Table.
Business value for customers
The Sum at Risk that will be considered for retrocession/ reinsurance can be calculated using the SAR calculation rules by applying additional parameters from the original policy when the RPO is run.
System Parameters Affected
Additional variables for the SAR calculation rules
Existing functionality affected
1. Escalation Indexation and Original Policy tab is now available for input for all cessions where the ceded flag is selected.
2. The values in this tab can be used in defining the SAR calculation rules and are available as variables
3. Original Policy Renewal Frequency is now a system-defined Lookup Table Allowable column and can be defined within any LUT. This will refer to the field 'Policy Renewal Frequency' in the Escalation Indexation and Original Policy tab of the cession or retrocession.
Changed documentation
SE-23055 - Update provisional and active cessions that do not have retrocessions through the loader - DXC #
Aim of function
The aim of the function is to be able to update values on existing cessions through a batch process where the cessions have not yet been retroceded or included in accounting.
Business value for customers
It will now be possible to make corrections on already loaded batches or to update the classifications such as underwriting flag (additional classifications) and other details on a cession after the decision is made.
It will also be possible to load cessions in a provisional status and update them once confirmed or approved.
System Parameters Affected
None
Existing functionality affected
A new flag is available on the cession batch loader in the Create New Batch option.
When this flag is selected and the imported records reference to an existing new business cession benefit transaction that is not yet retroceded or not included in accounting yet, then the details on the cession benefit will be updated as per the input file.
When the cession is in provisional status, and the input file contains ACIs then the referenced cession benefit will be set to active with the ACIs being created.
Changed documentation
SE-23402 - Attach to matching OCC within the PP based on the cession classifications - DXC #
Aim of function
Attach to matching OCC within the PP based on the cession classifications.
Business value for customers
For scenarios where the treaty covers a set of products and there is more than one Fac agreement with different reinsurers that cover a subset of the products on the treaty or, when the Facultative agreement pertains to a pure fac and the cession that is processed needs to be reinsured only through the Fac layer on the PP it will be possible for the cession to be reinsured through the respective layer within the same PP
System Parameters Affected
None
Existing functionality affected
When a Protection Program has more than one OCC and each OCC has different classifications or additional classifications, then the cession benefit will be retroceded to the OCC that has the matching classifications within the same PP.
Changed documentation
SE-24229 - Implement functions available only in HA version to head version - DXC #
Aim of function
The aim of this function is to move some functions that were implemented directly in the HA version SSP to head.
Business value for customers
New features as described in the Existing functionality affected section will be available.
System Parameters Affected
None
Existing functionality affected
1. Specific sections of the treaty can be updated using webservices.
2. It is possible to create amendments through webservices.
Changed documentation
MG & Reserve Orders #
SE-22986 - Batch Job Scheduling Usability Enhancements - DXC #
Aim of function
To implement support for creation of actual job for the Group Orders. Group orders (as mentioned below) will also be supported to Activate Scheduled job from the workstation (from the Group order window itself) for all child orders.
-Account Group Order (Retrocession Account Order Group)
-Calculation Group Order (Retrocession Calculation Order Group)
-Recovery Calculation Group Order
Business value for customers
Once Schedule job is created with request status, The Job, however, will not be run before its activation through Accounting Orders Monitor. With this enhancement, users can Activate Schedule job from the workstation (from the Group order window itself) for all child orders.
System Parameters Affected
None
Existing functionality affected
Accounting Orders (Scheduled Job activation)
Retrocession Calculation Order Group
Create Scheduled Jobs for Orders
Activate Scheduled Jobs
The above are same for other two group orders (Retrocession Account Group Order & Recovery calculation Group Order)
Changed documentation
Other #
SE-3373 - Logging of all DB upgrade functions in event log - DXC #
Aim of function
When upgrading the DB and updating security, the event log will now be updated with evidence of the steps executed.
Business value for customers
Audit evidence during the upgrade process.
System Parameters Affected
None
Existing functionality affected
Update Security
Changed documentation
SE-19054 - SICS UI/UX Improvements - Business Group Handling - DXC #
Aim of function
Improve the usability of managing the assignment of business to Master Treaty Groups , Merger Groups, Bifurcation Groups and Business Groups.
Business value for customers
Improved UX and usability.
System Parameters Affected
N/A
Existing functionality affected
Assign Business to Business Group from Business
View Business Group Members from Business
Create Business Group from Business
Changed documentation
SE-22292 - Support for Microsoft SQL Server 2022 - DXC #
Aim of function
We now support Microsoft SQL Server 2022 as a DBMS platform version.
System Parameters Affected
None
Existing functionality affected
None
Changed documentation
SE-22928 - Remove support for Microsoft Windows Server 2012 - DXC #
Aim of function
Microsoft Windows Server 2012 R2 reached End of Life status on Oct 10, 2023
DXC no longer supports Windows Server 2012 as a platform for SICS.
https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2012-r2
System Parameters Affected
None
Existing functionality affected
None
Changed documentation
SE-22984 - Implement New Security use case for URL links in Help Menu - DXC #
Aim of function
Implement New Security use case for URL links in Help Menu. The use name is 'System Parameter Help Menu Link'. This use case protects editing of URLs in System parameter.
Business value for customers
Protected modifying the Help menu URLs in system parameters.
System Parameters Affected
N/A
Existing functionality affected
User can't edit Help menu URLs from System parameter if above use is not assigned to user.
Changed documentation
SE-24389 - Remove support for PostgreSQL 11 - DXC #
Aim of function
Postgres dropped support for version 11 from 9 November 2023.
DXC will no longer support PostgreSQL 11 from 23.4.
We support PostgreSQL 12+
https://www.postgresql.org/support/versioning/
System Parameters Affected
None
Existing functionality affected
None
Changed documentation
#
SE-23026 - UI/UX Improvements - P&C - DXC #
Aim of function
Split the System Parameter page Remittance under Accounting, into two sub pages to give more space for these parameters and to have them grouped in a better way; one to show the settings of the Properties for the Remittances and one for the settings of the Validation of the Remittances.
Business value for customers
Makes it easier to find the wanted system parameter.
System Parameters Affected
Existing functionality affected
N/A
Changed documentation
This report was generated Thu Dec 14 15:46:13 UTC 2023.