What's new
Accounting General #
SE-12358 - Paid Remittance to be possible only from 'Generate Payment Request' and 'Reverse' Received Remittance - Africa Re #
Aim of the function:
The aim is to ensure that there are no paid remittance with classification Cash Payment left unsettled in the system. To achieve this objective, an error message will appear if a new Paid remittance with Rem Class 1 equal Cash Payment is created and left Unsettled. Further more, if a remittance is generated from an existing Technical or Claim balance it will be set to Cash Payment and immediately/automatically paired and set to Settled.
Reversal of a Received remittance will also generate a Paid remittance with Cash Payment and these two remittances will be paired and set to Settled automatically.
System Parameter/Reference Data Affected:
New system parameter 'Independent creation of Cash Paid remittance not allowed' under Accounting, Balance Pairing
New system defined value in Reference table 415 (Rem Class 1) named 'Cash Payment'
Also existing parameters affects this functionality:
'Mandatory - Rem Class 1' under Accounting, Remittance
'Automatic Balance Pairing when change of Remittance Status' under Accounting, Balance Pairing.
Existing functionality Affected:
Manually creation of Paid Remittance balances, in any status, and leave them Unsettled
Reverse Received Remittance balances and create reversal Paid Remittances
Generate Remittance balances from payable individual balances or balance groups
Changed documentation
SE-12359 - Remittance Balance involved in Pairing Process to be always fully Settled - Africa Re #
Aim of the function:
The aim is to ensure that during the Pairing process, any remittance balance(s) involved should never be left as Partially settled and in such a case, the pairing process must be stopped by the system.
System Parameter Affected:
New system parameter: Suppress creation of Partially settled remittance balance
Existing functionality Affected:
Currently there is no system parameter/functionality to stop the User from creating a 'Partially Settled' Remittance Balance during the pairing process. However, there are certain scenarios based on a specific system set-up where the system provides an alternative to the User to decide whether to leave the Technical or the Remittance balance as partially settled; and the User can select the option to leave the Remittance Balance as partially settled
Changed documentation
SE-12504 - Always use Remittances as the driving Balances - With Exceptions - DXC #
Aim of function
Client wants to give exception of mixing technical and remittance balances as included balances in the balance pairing when they are not both in Pending status. So we introduce new system parameter 'Exclude Definite Pairings from the above restriction' to control. If checked, be able to replace an Unallocated Remittance Balance with a regular Remittance Balance in a Balance Pairing when there exists other Technical/Claim Balances in this pairing that are Definite, or vice versa.
System Parameters Affected
Balance Pairing Group in use
When Pairing, always use Remittances as the driving Balance
Exclude Definite Pairings from the above restriction
Existing functionality affected
Replace Selected URB in Pairing
Changed documentation
SE-6029 - Update accounting classification names and split % through the SICS webservices - Swiss Re Zurich #
Aim of function-
To be able to update the Accounting Classification name and/or Accounting Classification Split % through a Web Service both for SICS P&C and SICS Life. It can be used for updating the Accounting Classification name and Accounting Classification Split % for one or multiple Accounting Classifications.
All the validations and interactive messages applicable to this functionality for Workstation are applicable to this new Web Service also.
The name of the new web service is updateAccountingClassifications and is found in SicsWsBusinessEntryPoint.
System Parameters Affected-
No System Parameter is affected.
Existing functionality affected-
Update Accounting Classification Name.
Update Accounting Classification Split %.
Web Services within SicsWsBusinessEntryPoint.
Changed documentation
SE-10603 - Improved Government Tax warning messages to support both online and APIs - Swiss Re Zurich #
Aim of function
When creating worksheets through createWorksheet or createClaimWorksheet web services, a new interactive warning message is needed so that the user can reply Yes on this message, while the web service is stopped by Government Tax validation error. In the above two web services the various GT error messages that appear online should be replaced by the new warning message so that the worksheets can be created in open status.
System Parameters Affected
No System Parameter is affected.
Existing functionality affected
System now creates a new interactive warning message in the web services createWorksheet and createClaimWorksheet instead of error message. When replied Yes on the new warning message, the worksheet can be created in Open status even if a Government Tax validation error would have stopped this worksheet from being applied to the database in an online process. At the same time, the reason for the validation error is also logged for this detail in the DB to allow identification of the failed detail record(s) later. In the above two web services, the new warning message replaces the Government Tax error messages that are triggered online. When these worksheets later are closed the system will trigger the online Government Tax validations and the user must take actions accordingly (existing functionality).
Changed documentation
BO #
SE-10812 - Generate or Execute multiple BOAC & Support scripts in the System Administration Desktop - DXC #
Aim of function
You can now generate or execute one or multiple BOAC Scripts in a single click in the from System Administration Desktop (SICS Admin –> Database Setup -> Manage Tables -> BO Reporting Tab).
User can also Create or Execute one or Multiple support scripts in single click in the System Administration Desktop.
BOAC Scripts :
Support Script :
System Parameters Affected
Not Applicable
Existing functionality affected
1. Creation of BOAC Scripts from SICS admin & Execution of BOAC scripts on Database from SICS Admin
2. Creation of Support Scripts from SICS admin & Execution of Support Script on Database from SICS Admin
Changed documentation
Business #
SE-10406 - Capture Treaty Type of Cover by Web Service - Allianz AG #
Aim of Function
An excess of loss treaty may have special covers like Clash Cover and Cost Cover. For these, SICS has separate validations, e.g. regular covers cannot overlap, clash covers cannot overlap, clash cover can overlap with regular cover and vice versa.
Earlier, if using web services to capture Treaty Type of Cover, it could be captured only when creating treaty outlines on a reinsurance program. Now, it is possible to capture Treaty Type of Cover also when creating a new assumed non-proportional treaty or updating an existing one by using web services.
The new element <treatyTypeOfCover> has been added to the <insuredPeriod> part of relevant Web Services.
System Parameters Affected
None
Existing Functionality Affected
Create Business by Web Service
Update Insured Period by Web Service
Changed documentation
SE-9311 - Business Conditions visibility depending on Security - DXC #
Aim of function
To reduce clutter in the user experience of SICS, the security facility now hides the condition buttons if they have no content (empty) and the user do not have an Update or Create right for these conditions.
When the user has no Update or Create right for certain conditions, their buttons are not be visible anywhere if they do not have any content. For example:
-Toolbar
-Structure Overview
-Cedent's Program Contract Overview
Condition buttons are visible and accessible if they have contents (condition buttons are yellow).
System parameters affected
None
Existing functionality affected
Maintain Share Conditions
Maintain Premium and Limit Main Conditions
Maintain Deduction Conditions
Maintain Reinstatement Conditions
Maintain Claim Conditions
Maintain Rebate Conditions
Maintain Deductibles Conditions
Maintain Profit Commission Conditions
Maintain Cancellation Conditions
Maintain Index Clause Conditions
Maintain Clauses Conditions
Maintain Reserve Conditions
Maintain Deposit Conditions
Maintain Portfolio Conditions
Maintain Calculation Rules Condition
Maintain Performance Management Data Return Condition
Maintain Additional Scope
Maintain Administration Life
Maintain Agreement Clause Life
Maintain Cancellation Provisions Life
Maintain Claim Life
Maintain Deposit of Reserves Life
Maintain Experience Adjustment Life
Maintain Limit Life
Maintain Non-Contract Administration Life
Maintain Portfolio Transfer Life
Maintain Premium Life
Maintain Profit Commission Life
Maintain Sum at Risk Life
Manage Security
Maintain Section Overview
Maintain Cedent's Program Contract Overview
Changed documentation
SE-11453 - Improve Business - DXC #
Aim of function
Display lists in SICS have an initial setting called the Factory Settings. The lists can however be customized by an organization and even by individual users, depending on security permissions.
When a user is allowed to save column settings (User Preferences / Misc. Preferences: 'Allow Saving of Container Changes (Column Changes)' is selected), additional options are available in the standard pop-up menu of the display lists. These options were earlier missing from the display lists of Protection Program and Reinsurance Program treaty parts: Prop., XL, AX and SL. These have now been made available.
System Parameters Affected
None
Existing functionality affected
Organise Display Lists
View Protection Program Outlines
View Reinsurance Program Outlines
Changed documentation
SE-12185 - Improve Wizard Support for all Party Details - DXC #
Aim of function
Earlier, the create new business partner wizard allowed for some details to be set up to appear as additional pages. All items listed under the Details tab of an existing business partner were available, however, out of these, only 2 pages could appear simultaneously. Now, this has been improved to allow all pages to be included in the wizard simultaneously. In addition, the User Defined Page can also be included here.
These improvements apply to Business Partner, Bank, Third Party and Person.
System Parameters Affected
None
Existing functionality affected
Create Business Partner
Create Bank
Create Person
Create Third Party
Maintain User Defined Pages
Maintain Reference Data
Changed documentation
SE-5996 - Upload Retrocessionaire Participation, also upload Written Share - Unive Verzekeringen #
Aim of Function
In SICS, the current Outward Cedent's Contract placing process allows loading of retrocessionaires from external excel files. Earlier, only Signed Share could be uploaded. This enhancement makes it possible to upload both Signed Share and Written Share values.
In addition, it is now possible to upload files to update share values (signed share and written share) on existing retrocessionaires.
System Parameters Affected
Business / P&C Miscellaneous/ Default Status of Upload of Placements
Existing functionality affected
Create New Business
Place Business
Maintain Share Condition
Change Life Cycle Status
Changed documentation
Claim, NP Recovery, Cede #
SE-9630 - Make Headline Loss link mandatory for Main Class of Business - Renaissance Re #
Aim of function:
Make Headline Loss link mandatory for Main Class of Business/Base Company combination
System Parameters affected:
New Base Company Specific Setting parameter enabling activation, and listing of Main Classes of Business
Existing functionality affected:
Create New Claim
Link Claim to Headline Loss
Create Worksheet
Change Claim Status
Changed documentation
SE-12099 - LinkClaimWorksheetToEMessage API - Renaissance Re #
Aim of function
New API which allows user to create a link between a single claim worksheet and one or more eMessages.
System Parameters Affected
None
Existing functionality affected
Changed documentation
SE-12100 - Prevent closing of worksheet when claim is not linked to HL - Renaissance Re #
Aim of function
When either reporting unit or combination of Base Company and Main Class of Business indicates that link to Headline Loss is mandatory, user cannot close a claim worksheet unless this link is defined.
System Parameters Affected
New parameter 'Link to a Headline Loss is Mandatory when Closing Claim Worksheet'
Existing functionality affected
Close Claim Worksheet
Changed documentation
eMessaging #
SE-11780 - Outbound eMessaging Improvements - DXC #
Aim of function
Made various improvements on the creation of outbound messages in eMessaging
- Made it possible to specify an ACORD Schema version for a specific recipient. This is done in eMessaging Information on the business partner. If a partner has a specific ACORD Schema selected then this is used to generate message for that recipient, otherwise if non is set then the Global ACORD Schema is used.
- Added Support for a commission calculation account, including supporting document for calculation description.
- On Outbound messages, made it possible to switch the sign of the amount in the case that the Entry Code and ACORD code normally positive flags do not correspond
- On Claim Movement messages, made it possible to include FGU Advisory info when FGU Indicator is activated,
- On Claim Movement messages, added previous amounts when applicable, so that messages with booked adjustments can be validated against the previous movements.
- On Claim Movement messages, when a message has a booking of a Multiple Account Group Item for current payment, all other items in the group are also included. Same when a message has a booking of a Multiple Account Group for Outstanding Loss, all other items in the group are also included.
- On Claim Movement messages and TechAccount Claim Signings: When a message has a booking of an item having a current and previous item for loss / loss expense, the total loss incurred / loss expense incurred is also included in the message
System parameters affected
N/A
Existing functionality affected
Create outbound TechAccount and Claim Movement messages
Changed documentation
SE-8641 - Non FGU Claim Movements to use message creation date as As of Date - Renaissance Re #
Aim of function
New rule applicable for claim movement messages which do not have the FGU Indicator activated. When rule is included the messsage creation date will be used as the as of date in the worksheet, instead of the message' as of date.
The rule should be implemented on message layer
System Parameters affected:
None
Existing functionality affected
Process Claim Movement message
Swap to Claim Worksheet
Changed documentation
SE-11068 - Scheduler - Status from Unprocessed to validated - Renaissance Re #
Aim of function
The aim is to make it possible to automatically validate messages after they have been imported, without fully processing the messages.
Two changes:
1. Added a new system parameter 'Validate on load' in eMessaging -> Processing Options
When selected, messages are automatically validated once they are loaded.
2. Added a new Job Step Type 'eMessaging Import and Validate' in Scheduler.
When used, messages are automatically validated after they have been imported.
System parameters affected
eMessaging Processing Options parameter 'Process on load'
Existing functionality affected
Import eMessaging messages from the workstation
Import eMessaging messages from Scheduler
Changed documentation
SE-11954 - Defaulting the entry code in the FGU tab for subsequent advisories - Renaissance Re #
Aim of function
When FGU Advisory is created by an eMessage the system should default the entry codes using mapping table for the message amtItems for the initial message, but for subsequent messages entry codes should be defaulted using mapping table for message amtItems, and default the entry codes defined on latest advisory for non-message FGU amounts (Client IBNR, Client IBNR LAE, ACR, ACR LAE
System Parameters Affected
None
Existing functionality affected
Validate and process subsequent ClaimMovement message using FGU booking rule
Changed documentation
Life #
SE-11715 - Short Term Policies with Benefit Term as one day - DXC #
Aim of function
The aim of the enhancement is to be able to create cession benefits with a benefit term of one day.
System Parameters Affected
None
Existing functionality affected
When the Short Term flag is selected on the cession benefit, it is now possible to create cessions with the benefit term of one day.
Changed documentation
SE-11889 - Retro Premium to be calculated based on inward premium with SAR= 0 - DXC #
Aim of function
The aim of this enhancement is to be able to process retrocessions on inward cessions where the sum at risk = 0 and use the ceded percentage to only retrocede premiums
System Parameters Affected
None
Existing functionality affected
Only on cessions where the Ceded flag is selected:
It will be possible to create cession benefits with the Sum at Risk entered as 0 and add premium and other ACIs manually
When the Retrocession Processing Order processes the cession benefits and the outward business is a quota share contract, then the ACIs from the inward cession benefit will be retroceded using the quota share percentage and the retrocession cession will be created with the retro sum at risk = 0
A new field Ceded Percentage will be available on the inward cession to pass the ceded percentage that needs to be used while processing the retrocessions and this value will be used when the outward business is not a quota share
Changed documentation
SE-12117 - New column for Deductible on the cession benefit - DXC #
Aim of function
The aim of this function is to be able to capture the value for 'Deductible' and 'Payment Ratio' on the cession benefit
System Parameters Affected
None
Existing functionality affected
A new field 'Deductible' and 'Payment Ratio' are now available on the cession benefit transactions
The fields are also available as output pattern fields on the cession output pattern
Changed documentation
SE-11513 - Handling of Loading and other details on the Joint Life level for Joint Life cessions - Misr Insurance Company #
Aim of function
The aim of the enhancement:
a) To be able to define parameters such as 'preferred life classification' that would be applicable to the joint life insurable object and use these parameters for validations of limits and any other calculation that are dependent on the joint life insurable object
b) To be able to define loadings applicable to the joint life insurable object
c) To calculate the accumulation based on the sum at risk of the primary life on the joint life cession
System Parameters Affected
None
Existing functionality affected
New tab for joint life insurable object:
- A new tab 'Joint Life Data' is available on a joint life cession benefit
- All fields in this tab are open for input/ selection and are independent of the values from the individual insurable objects that are part of the joint life cession
- When no values are specifically entered in this tab, all values from the individual insurable object which is flagged as the primary life will be copied to this tab
Please note that as per the current implementation, the Age fields on the Joint Life Data tab are informational and will not be used for any calculations or validations
Loading for Joint Life Insurable Object:
In addition to the loadings that can be imposed on individual insurable objects, it is now possible to add loadings that will be applicable for the joint life insurable object
Please note that any Age Loading will not be applicable to a joint life insurable object
Cession Loader- New Output Pattern Fields
- IS_JL_LOADING_ : This output pattern field will be applicable for the respective loadings that are applicable to the joint life loadings
Note: For a joint life cession benefit the Life for Loading should always be mapped
- New output data fields for the Joint Life Data are now part of the Cession Output Pattern.
- When specifically mapped to a value, the values will be updated on the respective fields in the Joint Life Data tab. When not mapped, all fields, where available, from the Primary Life data will be copied to the Joint Life Data tab
Changed documentation
SE-11515 - Additional Claim Statuses for Ceded Claims - Misr Insurance Company #
Aim of function
The aim of this function is to allow the following additional statuses on Ceded Claims
- Ceded Outstanding
- Transaction Reversal
System Parameters Affected
None
Existing functionality affected
The following statuses will now be allowed on a Ceded Claim
- Ceded Outstanding: The ACIs will be calculated from the claim liability field or the mapped ACI amount using the Claim Reserve entry code for this status
- Ceded Outstanding to Ceded Paid : When the status of the Ceded Outstanding claim is changed to Ceded Paid the claim reserve ACIs will be reversed and converted into an actual loss entry code for the Ceded Paid status
- Transaction Reversal: This status will automatically reverse the last active claim status and reverse all ACIs and also automatically create a reversal transaction on the outward claims if any. Once the last active status transaction on the claim is reversed then the next Transaction Reversal status will cancel the claim and the claim status will be set to Cancelled
Changed documentation
SE-11594 - Claim ACI should be picked from Claim Liability amount - Misr Insurance Company #
Aim of function
The aim of this enhancement is to be able to default all values including the Claim Liability Amount from the Decision Liability Tab of the Ceded claims and use the entry codes from the Calculation Model and Claims Entry Code Maintenance to calculate the ACIs when no ACI is specifically mapped
System Parameters Affected
None
Existing functionality affected
When no claim ACIs are entered or mapped, the value from the Claim Liability field will be calculated as the claim ACI using the respective default entry code
In addition to the defaulted ACI, it will also be possible to manually add other ACIs
Changed documentation
SE-11797 - RPO- Sequential Retrocessions- Handling of Retention and Unplaced Amounts when the sum at risk is entirely retained or unplaced - Misr Insurance Company #
Aim of function
The aim of the enhancement is to be able to handle cession benefits that are entirely retained and entirely unplaced when the retroprocessing is done and to be able to view the unplaced amounts on the cession benefit
System Parameters Affected
None
Existing functionality affected
- A new field 'Unplaced amount' is available on the Retrocession Tab of the cession benefit
- The list of Unplaced amounts after the RPO run will now list fully unplaced cessions also
- Once a cession is listed as Unplaced, it will not be listed in subsequent runs of the RPO with the same Protection Program.
Changed documentation
SE-11877 - Use Reinsurance start date during retrocession processing on a closed ended business - Misr Insurance Company #
Aim of function
The aim of this enhancement is to use the cession reinsurance start date to process all retrocessions and validate the terms and conditions on the business when there are benefits on the cession that have different benefit start dates
System Parameters Affected
New system parameter 'Use Reinsurance Start Date for Retroprocessing'
Existing functionality affected
When the system parameter is selected:
When there is a cession that has more than one cession benefit which has a benefit reinsurance start date later than the cession reinsurance start date, then on running the RPO all benefits will be retroceded based on the cession reinsurance start date.
This will mean that even if the OCC has been terminated and the cession benefit start date is beyond the OCC termination date, the benefit will continue to be retroceded based on the cession reinsurance start date (if it falls within the active insured period of the OCC)
All the terms and conditions that the cession benefits will reference to will also be the terms and conditions linked to the insured period/ amendment effective period on the OCCC within with the cession reinsurance start date falls in
When the system parameter is not selected:
Each benefit will be retroceded based on the benefit reinsurance start date of the cession benefit. If the cession benefit start date falls outside the active insured period of the OCC then it will not be retroceded even if there are other cession benefits on the same cession that have been retroceded through the same OCC
Changed documentation
Other #
SE-11844 - Complete Unicode support on SQL Server - DXC #
Aim of function
Fully support unicode mode on SQL Server on all text columns. In prior releases, some columns were not correctly created as NVARCHAR columns when unicode mode was enabled.
System Parameters Affected
In the sics-databasesource.xml file
<unicodeMode>true</unicodeMode>
Existing functionality affected
Create tables
Changed documentation
SE-11820 - Desktop Environment Announcements - Swiss Re Zurich #
Aim of function
Provide a means of issuing system level announcements to a specific SICS environment that will be shown on login and desktop refresh.
The announcement is edited in System Parameters and includes a from/to dates:
When the user logs into a SICS Environment or refreshes the desktop, the announcement will be shown if the from/to dates indicate it is active.
An API is provided for programmatically setting/unsetting the announcement.
System Parameters Affected
New system parameter section and settings:
Desktop Administration/Banner Announcement
Existing functionality affected
Login/Refresh
Changed documentation
SE-12180 - Issue loading excel files including PIVOT tables into ADH - Swiss Re Zurich #
Aim of function
Enable the import of Excel files (workbooks) where one or more sheets contain cells with a formula that refers to another, pivot table sheet, using the PIVOT function. SICS uses a 3rd party library, POI, to read Excel data. This library does not support the PIVOT function. The solution is to utilize the pre-calculated value of the cell formula. This value was stored during the last save of the Excel workbook, and was made available in a recent upgrade of POI. There should be no need to re-calculate the formula during import to ADH.
System Parameters Affected
None.
Existing functionality affected
ADH import of Excel spreadsheets as XML data.
Changed documentation
This report was generated Thu Jun 23 07:19:45 UTC 2022.