What's new

What's new

Accounting General #

SE-7459 - SBG Upload Function - Asia Capital Reinsurance #

 Aim of function

The aim of this change is to be more precise when searching for balances in the function Automatic Search for SBG from the BP Ledger. Therefore a new option to the existing 'Import Record File...' is established named 'Import Excel/Delimited Record File...'
The new option uploads an electronic file with a title supports TXT, CSV, XLS, and XLSX files with titles. The column names must strictly follow the names given in the Template.

Create SBG from Automatic matching by use of the new file structure:
If the Currency column is the same as 'SBG Currency' column, the value in the Settlement Amount column in the electronic file will be ignored when the SBG is created (the Unsettled Amount of the matched balance is used). The Settlement Balance Group will use the SBG Currency as the Currency and it will sum up the Unsettled Part Amounts from the rows with the same Currency and the Settlement Amount from the rows with different Currency. If NO Settlement Amount given on a row with different Currency, Then the system will calculate the Settlement Amount by use of current exchange rate (existing functionality).

System Parameters Affected

N/A

Existing functionality affected

  1. Automatic Search for Settlement Balance Group uploads files
  2. Create Settlement Balance Group from Automatically Matched Balances

 

 

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/accounting/bp_ledger/#automatic-search-for-settlement-balance-group


SE-3295 - Support update of Retro Pairing Table in scheduler - DXC #

Aim of function
Added periodic function 'Update Retro Pairing Table' as a job step in scheduler

AddJobStep.png

JobTemplate.png

System Parameters Affected
None 
Existing functionality affected
Update Retro Pairing Table
Create and run scheduled jobs

Changed documentation


SE-6492 - Support Original Acc Yr and Period in Online Statistics & MG Accounting on Open Ended contracts - DXC #

Aim of function

  1. When the Original Accounting Year and Period flag is selected on an Assumed Business or OCC and where bookings are made with values in the OYRP fields, it should be possible to view the Online Statistics for both actual and estimates based on the Original Accounting Year and Period as one of the criteria
  2. When the Projection Basis = Yearly AND the Original Accounting Year and Period flag is selected on the business, the Accruals will be calculated as the estimates for each year in the Period Estimates, less the accounted amounts for each corresponding Original Accounting Year.

System Parameters Affected

None

Existing functionality affected

Business Online Statistics:

  • A new selection criteria option 'Original Accounting' is available on the Business Online Statistics. 
  • When selected (or set as default as per the user preferences) the online statistics for both actuals and estimates are displayed based on the Original Accounting Year and Period of the bookings made on the business/ businesses included in the statistics view
  • If the business included in the statistics view does not have the Original Accounting Year and Period flag selected or bookings that have been made do not contain values in the respective fields, then the statistics will not be displayed for those bookings

image-2021-09-17-15-05-41-607.png

Multi GAAP Accounting Order and Multi GAAP Retrocession Order:

  • Normally when Projection Basis = Yearly, the Multi GAAP Accounting and Retrocession Orders calculate Accruals as the Period Estimate amounts for each year, less the accounted amounts for the corresponding Accounting Year. However, when the Original Accounting Year and Period flag is selected on the business (Insured Period tab), Accruals will be calculated as the Period Estimate amounts for each year, less the accounted amounts for the corresponding Original Accounting Year. In addition, Original Accounting Year and Original Accounting Period are populated on the Accrual details. They are set equal to the Accounting Year and Accounting Period.

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/getting_started/set_user_prefs/#criteria

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/analyse_business/online_statistics/#maintain-criteria-for-view-of-online-statistics


SE-6406 - New dedicated Web Service e.g. 'updateWorksheetDetailInformation' - Swiss Re Zurich #

Aim of function

To be able to update details, e.g. Accuracy Validation or Government Tax information, on an Open (any pending statuses) technical or claim worksheet through a new web service. The details to be updated are identified by their object id.
The name of the new web service is updateWorksheetDetails and is found in SicsWsCommonAccountingEntryPoint

System Parameters Affected

N/A

Existing functionality affected

Update existing pending Technical Worksheet
Update existing pending Claim Worksheets
Web Services within SicsWsCommonAccountingEntryPoint

Changed documentation


SE-6854 - Gov Tax - If the Trigger EC amount is 0.00, exit the rule (no error must be triggered), else move on - Swiss Re Zurich #

Aim of function

When book a Trigger Entry Code on a worksheet with the amount of zero, no validation of this detail shall take place even if it is hit by a Government Tax rules. Both on Claim and Technical Worksheet, and in eMessaging (Tech Account/Claim Movement).

 System Parameters Affected

N/A

Existing functionality affected

Government Tax Validation

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/accounting/claim_acc/#government-tax-validation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/accounting/manual_bookings_on_ws/#government-tax-validation


SE-7016 - Gov. Tax Table - Line of Business (UC-SE-2663-2937) - Swiss Re Zurich #

Aim of function

When Class of Business (Line of Business) is defined in the Government Tax Rule then this rule should compare it with the Class of Business in the Accounting Classification of the current booking row on the worksheet (not the section level as being currently). This will make the Government Tax Rule more precise for the actual booking row since the Accounting Classification for the booking row can only contain one Class of Business, while the business section may contain more than one Class of Business.

System Parameters Affected

Government Tax Table

Existing functionality affected

Government Tax Validation

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/accounting/manual_bookings_on_ws/#automatic-booking-of-government-taxes

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/accounting/claim_acc/#automatic-booking-of-government-taxes


SE-7018 - Gov.Tax – new column 'Producer Available' on Gov.Tax Table - Swiss Re Zurich #

Aim of function

Add a new column named 'Producer Available' in the Govt Tax Rule Table, above the existing Producer within Tax Country, with the values Yes, No or Not Specified, so that the system will be able to use the correct rule based on the values provided in this field, additional to all the other values in the rule, and only trigger the rule if the value matches the business. E.g. if Yes is selected then the rule will only be triggered for the business only if a Producer exists on the business.

System Parameters Affected

New element in the existing Government Tax Rule table

SE-7018_GovernmentTaxRule_view.PNG

Existing functionality affected
Government Tax Booking and Validation on Technical and Claim worksheet

Changed documentation


SE-7028 - Gov.Tax – Enhanced Logic for Gov. Tax Validation Indicator 'Always Stop if Trigger/Target EC is booked' - Swiss Re Zurich #

Aim of function

Implement a change in logic for Gov. Tax Validation Indicator 'Always Stop if Trigger/Target EC is booked' on the Validation tab on the Insured Period. Some further validation if the worksheet contains a Trigger and Target entry code is needed before a full stop is set.
The indicator can be set with 3 'Full Stop' values, either for Technical Worksheet, Claim Worksheet or both TW and CW.
1.
When a Target EC (Any entry code in any entry code groups within the Entry Code Group Category 'Government Tax Target') is booked in the worksheet, then the message 'Government Taxes to be checked by the user' should apply.
2.
When a Trigger EC is booked in the worksheet for which Government Tax rule(s) exist, then the following logic applies for further validation before a full stop is set.

A) if the Tax Country in the rule (start with the first rule) has the same partner country as the partner on the business with the following partner roles (check the roles in this sequence); Reinsurer, Cedent, Broker, Producer.

B) And if a Government Tax Rule exist that both is Active and has the 'Tax Applicable' parameter selected, check if the EC Group defined for this rule contains the EC in the current booking row.

C) If this is true, present the message 'Government Taxes to be checked by the user'.

D) But if it is false, check the next rule, and if this is the last rule for this partner go to the partner country for the next partner role listed in A. above. When the country for the last partner role has been checked and all replies false to this check, exit this rule without any error triggered

SE-7028_Gov.Tax_AlwaysStopIfTriggerTargetECIsBooked.PNG

System Parameters Affected

N/A

Existing functionality affected
Government Tax Validation on Technical and Claim Worksheets

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/accounting/introduction/#add-accounting-validation-information


SE-8511 - Gov Tax Validation tickbox missing in webservices - Swiss Re Zurich #

Aim of function

As for other information on the business, the aim with this enhancement is to be able to create and update also the Government Tax Validation information on the Insured Period through createBusiness and updateInsuredPeriod web services.

System Parameters Affected

N/A

Existing functionality affected

In the following existing web services in SICS Server (all in SicsWsBusinessEntryPoint) it is now possible to update the Government Tax Validation information:
updateInsuredPeriod
creatBusiness
createBusinessWithSections
renewBusiness
renewBusinessWithSections

Changed documentation


Accounting Orders #

SE-7678 - Accounting Order Improvements - DXC #

Aim of function

Sometimes the company needs to modify/revoke the commutation information on a business. This might be e.g. due to new information or that the business was commuted by mistake. For proportional treaty retrocessionaire participation, the options to 'Modify Commutation'/'Revoke Commutation' is now dependent on a new system parameter being active if the Account entered in the Commute per is already accounted for/booked.

System Parameters Affected

New system parameter Business/Conditions/Miscellaneous 'Allow Revoke Commutation when Account is booked/commuted'

Existing functionality affected

Relevant when option 'Business to be Commuted' has already been entered for a Retrocessionaire Participation on the Partner tab and bookings already exist/no booking exists for the account to be commuted/already commuted. 

Following existing options are affected by the new functionality;

Retrocessionaire's Participation, Partner tab 

  • Modify Commutation 
  • Revoke Commutation

 

Periodic Functions/Business Mass Commutation
Level of Business = Retrocessionaire's Participation 

  • Revoke 

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/business_life_span/terminate_business/#modify-information-for-business-to-be-commuted

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/business_life_span/terminate_business/#revoke-commutation-rules


BO #

SE-7854 - Analytics Improvements - DXC #

Aim of function

Various improvements to the reporting solution.  Solutions implemented as part of the client implementation project reimplemented in the standard solution. This will make the improvement available to all clients plus an easier upgrade for the client with the local solution.

System Parameters Affected

None

Existing functionality affected

Reporting Universes

 

Changed documentation


Business #

Aim of function

Some companies have other applications than SICS that work with complete versions after each amendment. To make the interface to these easier, SICS offers a facility that automatically links all existing conditions to an amendment upon creation of this amendment. Along with this, SICS offers also now a feature for updating the history, where the amendments already existed before activating the facility. This feature is the Mass Update Amendment Links. This mass update has however major impact on all contracts in the system, as all terms and conditions will then be linked to all contract amendments. Thorough analysis and considerations should therefore be taken in advance of taking such action.

MassUpdateAmendmentLink.png

 System Parameters Affected

Automatically Amend Contract Information

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 Classifications
Handle Protection Assignment
Handle Business Amendments

Changed documentation


Aim of function

Most companies need a contract amendment to be linked only to those terms and conditions that changed as part of the amendment. Some companies have however other applications that work with complete versions after each amendment. To make the interface to these easier, SICS offers now a function that automatically links all existing conditions to an amendment upon creation of this amendment.  Activating this function has however major impact on all contracts in the system as all terms and conditions will then be linked to all contract amendments. Thorough analysis and considerations should therefore be taken in advance of taking such action.

Amendable  terms and conditions are divided into 'Auto Amend Groups' and the system can be set up to automatically link existing conditions within these groups to new amendments.

The following Auto Amend Groups are available:

  • Share, Limit and Premium Conditions (Share Condition, Premium and Limit Main Conditions, Deposit Premium Condition, Flat Premium Condition)
  • Other Conditions (Commission Conditions, Brokerage Conditions, Other Deductions, Reinstatement Conditions, Claim Conditions, Rebate Conditions, Deductibles Conditions, Profit Commission Conditions, Cancellation Conditions, Index Clause Conditions, Clauses Conditions, Underlying Business)
  • Business Classifications
  • Administration Conditions
  • User Defined Information
  • Protection Assignment (Proportional and Non-Proportional Protection Assignment)

 

   Amended_condition.png

  System Parameters Affected

Automatically Amend Contract Information

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 Classifications
Handle Protection Assignment
Handle Business Amendments

 

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/business_life_span/business_amendments/#automatically-amend-contract-information


Claim, NP Recovery, Cede #

SE-6753 - Control the pop-up option 'Apply and Create duplicate TWK' - Allianz AG #

Aim of function

In order to control who can create a duplicate Technical worksheet from an open claim worksheet, a new security use case is implemented to control access to create such worksheets.

 

System parameters affected

None

 

Existing functionality affected

Define Security User Roles

Claim Accounting - Create Duplicate Technical Worksheet from Open Claim Worksheet

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/accounting/claim_acc/#apply-and-create-duplicate-technical-worksheet


SE-7249 - Light Policy - Support for Co-insurance managed in PAS - DXC #

Aim of function
Allow SICS Cede to use Policy Light as an administrative business in order to support reinsurance on behalf of the co-insurers when coinsurance is managed by the client.

SE_7965_doc_7249_new.png

SE_7965_doc_7249.png

System parameters affected
N/A

Existing functionality affected
Create Policy Light

  • Manually
  • Cede Interface
  • Web Service

Single Business Auto Protection
Multi Business Auto Protection

Changed documentation


SE-7265 - Prop PA of Policy with underlying top limit (Excess) - DXC #

Aim of function
Automatic Protection Assignment to support Underlying Top Limit on inward policy.

Using Cede to retrocede layered policies may be supported in existing functionality of Automatic Protection Assignment by use of Sequential Risk Unit Group as explained below:
Example:
Protection Program/OCC1: Quota Share 75% - LIM 22.000 (UTL 0)
Protected Policies:
Policy 1 - 20.000
Policy2 - 20.000 (in excess of 20.000)
Let's say I want to allocate 20.000 of Policy 1 and 2.000 of Policy 2 to QS OCC1.
This can be achieved by seeing these policies as one risk and assign them to the same Sequential Risk Unit Group.

Multi Business Auto Protection order will calculate protection in sequence (according to Created Timestamp) and assign as follows:
Policy1 - OCC1 75% (20.000 allocated, remaining capacity 2.000)
Policy2 - OCC1 7,5% (2.000 allocated)
>> As the limit of OCC1 now is exhausted, this leaves 18.000 of Policy2 unprotected (own retention).

Alternative ways of protecting the exceeding limit, e.g.:
a. Facultative protection of Policy2 by assigning 90% to proportional FAC OCC
>> 90% of Policy2 will be allocated to FAC (18.000)
b. Add a 2nd proportional layer to the Protection Program
>> will be assigned to Policy 2 accordingly
c. Add Non-Proportional Protection to the Program, e.g. with Cover Basis 'Net after Proportional Protections'
>> will be assigned with 25% to Policy1 and 92,5% to Policy2 (if no other prop protections than OCC1)
d. Combinations of the above

System parameters affected
N/A

Existing functionality affected
N/A

Changed documentation


SE-7490 - Light Policy - validation against Claim Basis Risks Attaching - DXC #

Aim of function

New validation in Cede Interface for Light Claims when Policy Light is created with Claim Basis Risks Attaching.

  • Original Policy Period must start within Policy Light Insured Period
  • Date of Loss must be within Original Policy Period

Corresponding validations are implemented in web service for Policy Light and Light Claim.

System parameters affected

N/A

Existing functionality affected

Create Light Claim via

  • Cede Interface
  • Web Service

Changed documentation


SE-7634 - Recovery Orders - Auto Test part 3 - DXC #

Aim of function
Created automatic test cases for Recovery Calculation orders for Protection Program and single OCC, covering multiple scenarios.

The tests are run nightly and the results are published in SICS Docs as part of the release.
In addition we capture code coverage statistics to evaluate the percentage of code that is tested as part of the test suite.

This is a part of DXC's mission to achieve provable quality in our software offerings.

System parameters affected
N/A

Existing functionality affected
Recovery Order

Changed documentation


SE-7643 - Cede Auto Test - part 2 - DXC #

Aim of function

Created a test suite of automatic test cases for ceding Policy Light using Scheduled job for Cede Interface, Multi Business Auto Protection, and Preliminary Bookings.

The tests are run nightly and the results are published in SICS Docs as part of the release.
In addition we capture code coverage statistics to evaluate the percentage of code that is tested as part of the test suite.

This is a part of DXC's mission to achieve provable quality in our software offerings.

System Parameters Affected

N/A

Existing functionality affected

N/A

Changed documentation


SE-7057 - Claim Action Date improvements - Renaissance Re #

Aim of function

A claim action date is normally set automatically on all claims, regardless of reserve position. In order to avoid that claims without any reserves have an action date, there should be a validation against the accumulated reserves. The validation should be implemented for all reserve entry codes, and is made per currency, entry code level, and per accounting classification. If the claim has an action date, the action date should be removed if the accumulated reserves are zero. Otherwise the worksheet should result in an update of the action date.

Additionally, a new option is introduced to ensure that action date is always generated if a claim has a sub-disposition, regardless of reserves. 

 

System Parameters Affected

New Base Company Specific Parameter - Claim Specific:  Validate Against Reserves

New Base Company Specific Parameter - Claim Specific: Always Set Action Date for Sub dispositions  other than None 

 

Existing Functionality Affected:

Maintain Claim Sub-disposition

Create Claim Worksheet

Close Claim

Process Claim Movement

 

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/claims/claim_review_update_info/#edit-a-claim-review-and-update-information


SE-6910 - No validation of Claim Limits against Aggregate Limit - Swiss Re Zurich #

Aim of function

When recording claim limits the system validates the new limits against the Aggregate Limit of the business.  A new parameter will remove this validation in the limit recording process, and allow client to maintain all validation as part of the accuracy framework.

 

System Parameters affected:

Do Not Validate Claim Limits against Aggregate Limit

 

Existing Functionality Affected

Create and Edit Claim Limits

 

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/claims/limits_and_shares/#record-new-claim-limit


eMessaging #

SE-6658 - RIP accrual on same CWS as claim and RIP paid - Renaissance Re #

Aim of function:

Add a new rule on message layer to  calculate Reinstatement Reserves, and book these on the same worksheet as claim and reinstatement paid.

The new rule shall be a 'full' reinstatement calculation, but only book the reserve items. 

A new element shall be added to createClaimWK and createFGUClaimWK APIs - to book reinstatement accruals only.

A new option is added to the claim worksheet to create Reinstatement for Reserves only.

 

System Parameters:

New rule available for message layer.

 

Existing functionality affected:

Process ClaimMovement

createClaimWorksheet API

createFGUClaimWK API

Create Claim Worksheet

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/accounting/claim_acc/#automatic-bookings-within-claim-worksheet


SE-6754 - TA Claim Signing Account Message Status - Renaissance Re #

Aim of function:

The automatically reprocess related messages - which is invoked when a message is processed from within emessaging - should also be triggered when a worksheet is closed manually/through API.

 

System parameters affected:

Automatically Reprocess Related Messages must be activated

 

Existing functionality affected:

Close worksheet

CloseWorksheet API

Changed documentation


SE-6821 - Gov. Tax Bookings automatically made by the system must not been considered for the 'Net Premium' - Swiss Re Zurich #

Aim of function
When comparing the BalanceAmtItem in a TechAccount message with the net Instalment or Adjustment premium in the Limit and Premium condition in SICS, any TechAccountAmtItems or TaxAmtItems mapped to a Government Tax Target entry code are now deducted from the BalanceAmtItem before it is compared to the Net Instalment or Adjustment amount.

Government Tax Target entry codes in this respect are defined as entry codes included in an Entry Code Group within Entry Code Group Category 'Government Tax Target'

System Parameters Affected

N/A

Existing functionality affected
The following validation rules are affected:

  • CompareReceivedPremiumToNetInstalmentPremium
  • CompareReceivedPremiiumToNetAdjustmentPremium
  • CompareReceivedPremiumToNetInstalmentPremiumLM
  • CompareReceivedPremiumToNetAdjustmentPremiumLM
  • ValidateNetBookedAmountsOnInstalment

Changed documentation


SE-7021 - New Tab 'Government Tax' on TA Messages - Swiss Re Zurich #

Aim of function
The aim of the function is to show more information on the TechAccount/eMessaging/Government Tax tab and to specify why the validation failed. The Gov. Tax Rule Type gives the following information in the new column Gov. Tax Rule Type depending on various scenarios;

  • Booked Target EC without Gov. Tax Rule
  • Gov. Tax Table Rule
  • Gov. Tax Validation Indicator Rule

 

System Parameters Affected

Two existing Accounting system parameter must be activated/defined;

  • 'Government Tax Framework in use' to activate the new Government Tax functionality.
  • 'Government Tax Table' to define various rules for what to be booked and validated

 

Existing functionality affected

  • eMessaging/TechAccount/Government Tax tab
  • Validation of Government Tax Trigger/Target Entry Codes and amount

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/emessaging/highlights/#government-tax


Life #

SE-7055 - Add Reporting Date to inforce import files - Achmea Reinsurance Co #

Aim of function

To be able to input a Reporting Date on the cession batch while loading the data source and default this date within the input pattern block in the  mapping.

To default the Reporting Date on the cession batch to the created cession benefit transaction

To default the date on which the batch was successfully closed as the 'Created Date' on the cession benefit transactions that were created by the batch

 System Parameters Affected

New system parameter 'Reporting Date mandatory on Cession Batch'

When this parameter is selected the field Reporting Date is mandatory 

image-2021-09-09-12-19-22-225.png

 

Existing functionality affected

On the cession benefit transaction a new tab 'Dates and Sequence Options' is available

The value from the Cession Batch is defaulted to 'Reporting Date' and the date on which the batch was closed to create the cession transaction is defaulted to 'Created Date'

The field Reporting Date is not mandatory on manual cessions irrespective of the system parameter.

image-2021-09-09-12-19-47-970.png

Changed documentation


SE-7363 - Inforce file for multiple contracts - Achmea Reinsurance Co #

Aim of function

The aim of this enhancement is to be able to filter values within the data source that has been uploaded on the cession batch and process only the filtered records against specific contracts.

System Parameters Affected

None

Existing functionality affected

A new button 'Add Filter' is available in the Define Data Source window

image-2021-09-09-17-46-24-308.png

On selecting this button, the user will be able to select values from one or more columns to filter the records

image-2021-09-09-17-43-51-628.png

Once filtered only the filtered records will be available for loading and processing

The same input file can then be loaded against another assumed business  by applying a different filter for the records relevant to that assumed business

 

Changed documentation


SE-6720 - Reinsurance Program to be supported in Find Cessions and Cession Batch - Africa Re #

Aim of function

To be able to navigate from the cession batch to a Reinsurance Program
To be able to find cessions linked to a Reinsurance Program by selecting Reinsurance Program as the level of business in the Find Cessions window

System Parameters Affected

None

Existing functionality affected

Find Cession window:

It is now possible to select a Reinsurance Program under the Agreement and find all cessions linked to all the Assumed Businesses that are part of the Reinsurance Program

screenshot-1.png

Cession Batch :

When a cession batch is created using a Reinsruance Program, it is now possible to click on the Business icon on the batch to navigate to the Reinsurance Program

screenshot-2.png

Changed documentation


SE-4096 - RPO : Insurance products/Benefits, having Base as coverage indicator should be given 'Retrocession Priority' - DXC #

Aim of function

The aim of this enhancement was to use the Coverage Indicator defined on the cession benefit to prioritize cession benefits during the retroprocessing

System Parameters Affected

None

Existing functionality affected

When there is more than one cession benefit on the same life having the same benefit covered and all the cession benefits have the same reinsurance start date, the benefits having the coverage indicator 'Base' will be retained on priority over the 'Rider' when the Retrocession Processing Order is run

When the Coverage Indicator is None or Unknown then there will be no sequencing of the cession benefits within the same reinsurance start date.

Changed documentation


SE-6277 - Estimates and non ACI bookings on AB to flow to the OCC even when the Acct Admin basis is Individual - DXC #

Aim of function

The aim of this function is to allow the flow of estimates and actual bookings that have been made on a technical worksheet from the inward business to an outward business that is attached to the Proportional Protection Assignment as a QSR OCC even when the accounts administration basis on the business is Individual

System Parameters Affected

None

Existing functionality affected

Entry Codes:

Only in SICS Life, a flag is available on the entry code 'Allowed in Retroaccounting when Acct Admin basis is Individual'
screenshot-1.png

When this flag is selected, any actual bookings made on an inward business where the Acct Admin Basis is individual will flow to the linked outward business as As Original bookings, similar to a bulk administered business.
Irrespective of this flag, all estimates will always flow to the outward business

Proportional Protection Assignment on an Assumed Business:

When the Quota Share Retrocession flag is selected, it is now possible to attach an OCC that is part of a Protection Program as a Quota Share Assignment, but only when the flag 'Retro Accounting Only' is selected

screenshot-2.png

When an OCC is linked to the AB with this flag selected, then all estimate bookings made on the inward business and all actual bookings made with entry codes flagged as ''Allowed in Retroaccounting when Acct Admin basis is Individual' will flow from the inward business to the OCC as As Original bookings similar to a Bulk Administered business.

This will not impact the cession ACIs and all cession and claim ACIs will be included in accounting through the We Bill/ They Bill processing as per the definition on the business.

Changed documentation


SE-6730 - Dev-Cession Loader to process Blank Column Headers and Duplicate Column Headers without error - DXC #

Aim of function

When an input file has duplicate column headers or blank column headers, during the Import and Retrieve process, the cession batch loader should not throw exceptions and allow the user to process the file by defaulting values to the duplicate or blank column headers

System Parameters Affected

None

Existing functionality affected

**During the cession loading process:

  • When the input file has duplicate column headers, during the import process the duplicate column headers are updated with the column header name appended with _1
  • When the input file has blank column headers, during the import process the blank column headers are updated with a header BLANK_1, BLANK_2 etc.
  • Any leading and trailing spaces in a column header is ignored

 

Changed documentation


SE-6807 - Include Original Accounting Year and Period in the TW upload template - DXC #

Aim of function

The aim of this enhancement is to be able to upload the Original Accounting Year and Period on a technical worksheet through the Import Worksheet from Spreadsheet or Import Column Worksheet from Spreadsheet option 

 System Parameters Affected

1. The existing system parameter 'Import Technical Worksheet through the rows Generate Worksheet Id' is now renamed as ' 'Allow import of Technical Worksheets as column spreadsheet with a Worksheet Title'

2. In the output patterns for 'Life Technical Worksheet from Spreadsheet' 'P&C Technical Worksheet from Spreadsheet' two new output pattern fields are available and when mapped, the values will be populated on the Technical worksheet created through the mapping

image-2021-09-09-15-05-40-830.png

image-2021-09-09-15-08-01-338.png

Existing functionality affected

From the Worksheet menu, when the user generates a template for the technical worksheet upload either from the 'Import Technical Worksheet from Spreadsheet' or 'Import Technical Worksheet from Column Spreadsheet' option, two new fields Orig Acc Yr and Orig Acc Period are available

The values that are imported from these fields will be updated on the imported technical worksheets when the business has the flag 'Original Accounting Year and Period' selected. 

On business where the flag is not selected, the values in the two fields will be ignored during the technical worksheet upload

image-2021-09-09-14-56-00-859.png

Changed documentation

/https:/github.dxc.com/pages/sics/sicsdocs-hugo-publish/dev/pc/sicsdocs/user_guide/pc/accounting/find_ws/#import-worksheet-details


SE-7221 - Calculation of Premium when Benefit Term in Days- Additional Requirements(Dev-Test) - DXC #

Aim of function

The aim of the function is to be able to define the benefit term and premium paying term in days only and use this value to calculate the premiums when the linked premium rate table is defined in days

System Parameters Affected

None

Existing functionality affected

A new flag 'Short Term' is available on the Group Information Tab

image-2021-09-20-12-45-49-092.png

When this flag is selected, it will be possible to enter the benefit term and the premium paying term in only days and not years

When there is a corresponding premium rate table linked to the business where the rate is defined with benefit term in days as one of the parameters, then the premium on the cession benefit will be calculated using the days value in the benefit term/ premium paying term field

The flag 'Short Term' will not be selected by default and when this is not selected, it will not be possible to define a benefit term of greater than 365 days as per existing functionality

Changed documentation


SE-7387 - Life MTK for Period Estimates - DXC #

Aim of function

The aim of this enhancement is to be able to handle the ES condition and the period estimates through the MTK functionality

System Parameters Affected

None

Existing functionality affected

It is now possible to export and import Period Estimates through the MTK loader

Changed documentation


SE-7569 - Cession Loader Performance Issues - DXC #

Aim of function

The aim of this function was to test and analyse the cession loader performance 

System Parameters Affected

None

Existing functionality affected

None

Changed documentation


SE-7127 - Support adjustment reversal for New business transaction and renewal could be created normally after adjustment reversal for New business transaction - Heng An Standard Life #

Aim of function

The aim of this enhancement is to be able to load a cession with the same policy number as a new business transaction without having to do a reinstatement after a cession has been terminated with a 'Ceded in Error', 'Setup in Error' or 'Cancelled from Inception' transaction

System Parameters Affected

None

Existing functionality affected

When a cession benefit is terminated from inception through a transaction such as 'Ceded in Error', 'Setup in Error' or 'Cancelled from Inception' and there are no more active cession benefits on the same cession, then the policy number on the cession is updated with the termination transaction appended to the policy number.

This way, when the same policy number is loaded and processed again through the cession loader as a 'redo' transaction which is a fresh New Business transaction, the existing cession is not referenced again and a new cession can be loaded without having to reinstate the previously terminated cession.

The terminated cession will not be part of any accumulation calculations when the RPO is run

Changed documentation


SE-7128 - Never return unearned premium for Maturity transaction - Heng An Standard Life #

Aim of function

The aim of this function is to never calculate unearned premium on a cession or retrocession cession benefit when the termination is due to a maturity transaction

System Parameters Affected

None

Existing functionality affected

On the Agreement Clauses condition on the business a new option 'Unearned Prms Ret.Exc. Maturity is available

When this is selected, the unearned premiums will be calculated and returned based on the Pro Rata Return Type selected for all termination transactions except when the termination transaction on the cession benefit is Maturity or Maturity by Marriage

image-2021-09-20-09-52-04-313.png

Changed documentation


SE-7222 - Claim Recovery Calculation Rule for Wavier of Premium Rider Policy (Dev-Test) - Heng An Standard Life #

Aim of function

The aim of this function is to be able to define a percentage on the claim and use this value to calculate the claim recovery, overriding the original ceded percentage on the cession benefit

System Parameters Affected

None

Existing functionality affected

For a claim with a status of 'Ceded Paid' AND the Liability is selected as 'Partial Payment' and a value is defined in the field For Payment % , then when the Retrocession Claim Processing Order is run, the recovery claims will be created by applying the value in the field 'For Payment %' to the inward claim ACIs

The value in the 'Ceded %' on the linked cession benefit will not be considered for calculation of the retro claim ACIs

This is applicable ONLY to claims with the status of Ceded Paid

 

Changed documentation


SE-7385 - Retroprocessing to be sequenced as per 'sequence number' - Heng An Standard Life #

Aim of function

To introduce a new field on the cession benefit transaction labelled 'Sequence Number'

To be able to use this sequence number to sequence and process the cession benefit transaction when the Retrocession Processing Order is run

System Parameters Affected

New System Parameter ' Sequencing Based on Cession Benefit Sequence Number' is available

This will be available for selection only when the system parameter 'Sum at Risk/ Standalone Individual Retrocessions Only' AND 'Method of Retrocession is Reinsured Sequentially in Excess of Maximum Retention' is selected

screenshot-2.png
 

Existing functionality affected

On the Cession Benefit transaction:

A new tab 'Dates and Sequence Options' is available with the field 'Sequence Number'
screenshot-1.png

The field is informational when the system parameter described above is NOT selected,

When the system parameter described above is selected, this field is mandatory.

The value will be copied from the previous transaction and can be overwritten on each transaction if required

When there are several cession benefits for the same life, covering same benefit and the  transactions have the same reinsurance start date/ effective period start date or original transaction date, the value in the field Sequence Number will be used to sequence and prioritise the cession benefit transactions when the Retrocession Processing Order is run. 

Changed documentation


SE-7526 - Reversal of Claims-Dev-Test - Heng An Standard Life #

Aim of function

The aim of this enhancement is to be able to create an Adjustment Reversal transaction on a Ceded Paid Claim and reverse any Retrocession Claim that was recovered

System Parameters Affected

None

Existing functionality affected

When the existing system parameter 'Allow transaction number of cession and claim transactions is selected'

  • It is possible to define a mandatory transaction number on all Ceded Paid claims, the number is defaulted as 1 and can be overridden. This field is optional on non-Ceded Paid claims.
  • A new transaction 'Adjustment Reversal' is available on Ceded Paid claims, both manually and through the loader
  • When an Adjustment Reversal is created on an inward Ceded Paid claim, the adjustment reversal transaction is created for the transaction number specified and all linked outward Ceded Paid claim transactions are also reversed automatically
  • It will be possible to have more than one Ceded Paid transaction on a Ceded claim and when reversed, each Ceded Paid transaction will need to have its corresponding Adjustment Reversal transaction 
  • The reversed transactions will have the same as of date and ACIs as the source transaction, but with the reversed signs and the release indicator will be Released. 

Changed documentation


SE-7553 - Handling of Ceded Paid Claims with no renewals - Heng An Standard Life #

Aim of function

The aim of this function is to be able to process and recover ceded paid claims when the claim event date of the ceded paid claim falls outside the active cession effective period

System Parameters Affected

None

Existing functionality affected

Creation of Ceded Paid Claims

It is now possible to create a claim with the status of 'Ceded Paid' where the claim event date is later than the latest active effective period of the inward cession benefit.

This will not be possible in the following scenarios:

  • When the status of the claim is NOT Ceded Paid
  • When the status of the claim is Ceded Paid, but the Liability Reason is Installment Recovery or Lumpsum Recovery

Retrocession Claim Processing Order

When the Retrocession Claim Processing Order is run and the retrocession claims are created and there is no active effective period on the inward cession for the claim event date and therefore no linked retrocession cession, then the Ceded % from the last active effective period is used to calculate the retro claim ACIs 

Changed documentation


SE-7633 - Start date of return premium is from effective date of termination transaction - Heng An Standard Life #

Aim of function

When a termination transaction is created with the transaction effective period that is later than the effective period end date of the latest cession transaction, the RPO does not pick up the termination transaction to process a Full Recapture. The aim of this function is to be able to process the termination transactions with the transaction dates outside the latest effective period

This epic covered the specification of the functionality to be implemented to support the above mentioned requirement

System Parameters Affected

None

Existing functionality affected

None

Changed documentation


SE-7855 - Dev- Lumpsum Recovery in lieu of Instalments - Heng An Standard Life #

Aim of function

The aim of this enhancement is to be able to process and recover all the installments that are due to be paid on a later date as a lumpsum amount if a death claim is reported on the cession benefit where the payments are currently being paid out and recovered as installments

System Parameters Affected

None

Existing functionality affected

When a Ceded Paid claim is created with the Liability Basis selected as 'Installment Recovery', the outward claim is created with one Ceded Paid status for each installment that will be recovered from the reinsurer. 

When there is a death claim that is reported on the same benefit where installment recovery claims are being processed, one new inward claim transaction with the Liability Basis 'Lumpsum Recovery' will be created on the same Installment Recovery claim 

When this claim transaction is picked up by the RCPO. all the future installments that have the accounted status as Released will be deleted, and the claim ACI amounts of all these deleted installments will be summed up to create one Lumpsum Recovery claim status with the As of Date as per the payment due date of the RCPO that created the claim transaction

 

Changed documentation


SE-6512 - Joint Life Retrocession processing when the cession has both single and joint life cession benefits - Misr Insurance Company #

Aim of function

The aim of this enhancement is for the Retrocession Processing Order to pick up all cession benefits within the cession even when one benefit pertains to a joint life and the other benefit pertains to a single life within the joint life insurable object

 System Parameters Affected

None

Existing functionality affected

When the cession is a joint life cession and the cession benefits within the cession pertain to individual lives, joint lives or/ and both, the Retrocession Processing Order now  processes all the cession benefits and creates the retrocession cessions for each benefit 

Changed documentation


Other #

SE-1819 - MySQL DB Consistency Scripts - DXC #

Aim of function

Provide set of DB consistency scripts for MySQL compatible platforms.

System Parameters Affected

None

Existing functionality affected

SQL Script Manager > Database Consistency Scripts

Changed documentation


SE-6737 - Re-label Favourites as Bookmarks - DXC #

Aim of function

The aim of the function is to re-label Favourites as Bookmarks

System Parameters Affected

N/A

Existing functionality affected

The Favourites menu bar will now appear as 'Bookmarks'.

Changed documentation


SE-6924 - Update Web Service Tester - DXC #

Aim of function
The SICS Web Service testing app had not been updated for some years. It was using a CSC logo, jdk7, and out of date libraries.
It is now updated with the latest libraries & JRE and has updated icons reflecting the new DXC branding.

System Parameters Affected

N/A

Existing functionality affected

N/A

Changed documentation


SE-7361 - SICS UI/UX Improvements - DXC #

Aim of function

The aim of this epic is 

  • Improve the UI alignments of Find functions of SICS Life Workstation and System Parameter screens.
  • Introduce a new Heading widget that is being used in Navigation tool bar and Audit status bar.
  • Change Business & eMessaging Highlights screens such that they are properly visible in different screen display resolutions.

System Parameters Affected

Clean up of System parameter screens such that P&C specific system parameters are not visible in LIFE system.

Existing functionality affected

N/A

Changed documentation


SE-7892 - Wizard Support for Create Party - DXC #

Aim of function

The aim of this change is to allow user to create Party with all required information as configured in Reference data. All the Party Details are now configurable in reference data and these will be appeared as Wizard pages.

Two new Reference Data Types are created. 1) Party Wizard Page (01233) and 2) Party Wizard Type (01234)

  • Reference Data type 'Party Wizard Page' contains the Reference data items corresponding to Party Details.
  • Reference Data type 'Party Wizard Type' contains the Reference data items corresponding to each Party type.(Ex: Business Partner, bank, Third Party, Person).
  • Each 'Party Wizard Type' can be configured to have 'Party Wizard Page' as it's Children Reference data.
    New Screens will appear as below:

Create_new_business_partner.png

Create_new_bank.png

Create_new_person.png

Create_New_Third_Party.png

System Parameters Affected

N/A

Existing functionality affected

The following functions will be opened in wizard
-Create Business Partner
-Create Bank
-Create Person
-Create Third Party

Changed documentation


SE-8452 - ADH - Faster extraction of input data values - DXC #

Aim of function
This applies to XML mappings, in which case the input data is always XML (even if imported from an Excel spreadsheet).

Before this XML data can be used in transformation, the values must be extracted using the xPath expression defined on each Input Pattern group/field. This extraction can be time-consuming, depending on the xPath expression.

There is an opportunity to increase the extraction speed in certain cases, typically when IP fields inside an IP 'row' group refer to table column by using constructs such as 'cell[@columnNumber=number('%../row/cell[contains(value,'Account Currency')]/@columnNumber%')]'.

This JIRA issue is an enhancement which will allow an xPath expression to refer to previously extracted input data.

Typically, one will define a 'helper' IP field above/outside the 'row' group, and extract the required column number there. For example:
'table' IP field = #AccountNo
xPath = row/cell[contains(value,'Account No.')]/@columnNumber
This value will be extracted once per 'table', not for every row.

In the 'row' IP field 'Account No.' we can now refer to the already extracted value for #AccountNo thus:
cell[@columnNumber=number('$../#AccountNo$')]/value
Note the use of $ which signifies that we are referring to a previously extracted value.
The text between the two $ must be the name of the 'helper' field, prefixed by zero, one or more '../' which means navigation to the parent group.

System Parameters Affected
None

Existing Functionality Affected:
ADH

Changed documentation


SE-5267 - ADH new type of Output Pattern and support for handling this type - Swiss Re Zurich #

Aim of function
Implement in SICS ADH a new Output Pattern type 'External', based on the existing 'eMessaging Message' type with the following changes/additions:

  • New setting(s) (URL) for sending generated output as a POST request to a REST or SOAP service
  • New setting(s) (folder name, file prefix) for sending generated output to a disk file (useful for testing)
  • When creating/editing an 'External' OP, one and only one of the above output methods must be selected, else the Output Pattern cannot be saved.

Further enhancements:

  • Allow 'External' OP to be used in XML type mappings (not Tabular ones)
  • Allow 'External' OP to be mixed with other types of OP in XML mappings
  • Support for export and import of 'External' OP
  • During transformation, record any errors that may occur when sending generated output to the target defined by 'External' patterns that are part of the mapping.
  • Augment the DXC internal ADH Test harness with new REST service for 'External' JSON/XML data.

System Parameters Affected
None

Existing functionality affected
ADH

Changed documentation


SE-7698 - ADH - Add a notes option to the properties of each block - Swiss Re Zurich #

Aim of function
Add a notes option to the properties of each ADH transformation block. The original mapper can then add comments to the notes to explain what the block is doing. This should make it easier for anyone coming back to the mapping at a later date to understand what is happening.

System Parameters Affected
None

Existing functionality affected
ADH

Changed documentation


SE-7700 - ADH - Include Business Title into Section Domain Block - Swiss Re Zurich #

Aim of function
Include Business Title as a selectable output from the Section Domain Block.

System Parameters Affected
None

Existing functionality affected
ADH

Changed documentation


This report was generated Wed Sep 22 07:07:47 UTC 2021.