Problem:
Brokerage Payment Task and VAT calculation

Solution:
When the system automatically calculates VAT on a technical worksheet and the worksheet contains Brokerage, then the system must find the VAT % on the country for the Broker on the actual insured period. If the country for the Broker do not have a VAT % defined, then use the VAT % for the Cedent. If there are more than one Broker defined on the insured period, then use the Broker with the Brokerage Payment task, else use any of the Brokers on the insured period.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Calculated Adjusted Premium is wrong if there is amendment.

Solution:
The view of the Adjustment Premium, both on the conditions and on the Accounting window, must show the TOTAL picture for the whole IP, and taking the different effective periods into account so that the Our Share amounts are displayed with the same amount independent from which effective period it is opened.
The two Our Share n% columns must change the header to display only Our Share (not showing the percentage since this may vary for the different amendments).
The calculation of the amounts in the Our Share of Adjusted Premium and Our Share of Adjustment Premium must use the Share from the Share conditions, but it must calculate this based on how many days these different shares have effect.
Example:
If you have an Adjusted Premium of 200 000 and the share has changed from 10% to 30% mid period from e.g. 1st July 2019 (IP is 1st Jan 2019 - 31st Dec 2019), then Our Share must be calculated like (200000*10%*181/365) + (200000*30%*184/365) = 9 917,81 + 30 246,58 = 40 164,39.
The same should be the case for the Our Share of the Adjustment Premium.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When Business has already Invalid AC exist on the business with 0% share and we try to Importing ESPID table with SPLIT % shares, System distributes equally divided shares to invalid AC's.

Solution:
When Business has already Invalid AC exist on the business without split % and when we generates ACs according to the attached ESPID table with SPLIT % shares, we must make sure the system creates valid ACs and distributes the AC split percentages among these only, i.e. ignore the existing invalid ACs.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Plausibility Check 'Change in Loss Incurred' - Ignore zero movement' not working as expected'

Solution:
When executing the PBR Change in Loss Incurred and the system is executing the logic of ignoring zero movement (new in SE-1797), we must make sure this ignore facility is performed per aggregation level on the worksheet. This ignore zero movement facility works fine if the zero booking is the only aggregation level on the worksheet, but not when it is combined with other aggregation levels and these are not zero.
The logic also works fine if there ALL aggregation levels on the worksheet are zero, e.g. if a detail with one Accounting Classification is zero and another detail with another Accounting Classification, then the PBR is not triggered.

Workaround:

Root Cause:
Wrong implementation of SE-1797 in version 4.9.5

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Hard stop error on loss deposit retain based on the loss reserves

Solution:
When the system validates the Premium or Loss Deposit Retained on a worksheet, we must make sure the system aggregates also the previous booked retained and released deposits within the same aggregation level. The computed value in message AC0770 must reflect this aggregated value.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Default Booking Year and Period per RU is not working on business with multiple Insured Periods

Solution:
On a technical worksheet on a business with multiple Insured Periods, when the user add the first row, the system will not default the Insured Period, but still sets the Booking Year/Period from the Default setting for the Base Company on the last Insured Period. In this process, the system must also check if there is a special setting for the RU on the last IP. If a special RU settings exists for this BC, then the system must set the Default value from this setting.
If the user change the IP on an existing row, and the existing Booking Year/Period on this row is open for the BC/RU combination then this Booking Year/Period is kept, else the system resets the Booking Year/Period from the Default for this BC/RU setting.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The given Original Base Company in the Spreadsheet does not create separate balances with this Base Company when uploaded to Technical Worksheet

Solution:
When the function Import Technical Worksheet from Spreadsheet is started from the Find Accounting Worksheet window, and the selected spreadsheet contains details for an OCC with Original Base Company set, then these details must be treated in the same way on the Technical Worksheet as when the user manually select the option Link OCC Base Company. This means that the given Original Base Company shall trigger its own balance containing all details with the same Original Base Company linked.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Unable to commute because of unreleased non-liquid deposits when there are none on the As Booking ledger

Solution:
When the user is in the process of Commute the ORP on an Insured Period, the system is currently checking if there are any unreleased deposits, liquid and non-liquid. The system should check the As Booking ledger of this ORP only, and not check the As Account ledger. If there are no unreleased deposits, liquid or non-liquid, on the As Booking ledger for the actual Insured Period, then no error message BS0663 should be presented. Only if there are unreleased deposits on the As Booking ledger for the actual Insured Period that the error message BS0663 should be presented.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Removed BP still affects search result when find accounting worksheet

Solution:
When a business partner name/identifier is entered in a partner field on the Find Accounting Worksheet window, e.g. Payment Partner, Responsible Partner or Base Company, and the system also automatically gets and lists all merged partner in the field, it must be possible to delete these automatically added partners from the field so that only the manually given business partner is used to retrieve balances when Find Now is selected.
 
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
While generating accounting classification manually, System considers only the generic classification types on the AC generate criteria window and not the specific values defined under BC specific settings for a certain Type of Business

Solution:
When Accounting Classification is either Added or Generated on a Business, e.g. Proportional Treaty, with a Base Company in combination with Type of Business, e.g. also Proportional Treaty, has Special Settings for the Classification Rules 2, then we must make sure the system is able to read this special settings for the combination of Base Company and Type of Business, and both create and validate Accounting Classifications on this business accordingly.
If there is not special Classification Rules 2 for the combination of the Base Company and Type of Business, then the system must do as today, use the Base Company settings in combination with Type of Business <None>.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Reinstatement is not calculated on Main section if one child section does not have any.

Solution:
When calculating reinstatement, the system must consider whether it can be calculated on the current section - and not check other sections of the business.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Brokerage Payment Task not working when booking on multiple Insured Periods

Solution:
When booking on multiple Insured Periods on a Business with the Payment Task assigned to the Broker, we must make sure that ALL balances created for the Brokerage, the Broker must be assigned as the Payment partner on these balances. This must be the case if booking only on one of the IPs and when booking on multiple IPs.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Can't trigger retrocession calculation order for OCC auto booking

Solution:
When a worksheet is closed on an Assumed Business and this is protected by one or more proportional treaty OCCs, and if any of these OCCs have the flag 'Automatic Booking for OCC ORP' selected, the system must automatically create and run a Retrocession Calculation order for this/these OCCs, independent if the first OCC in the list has this flag selected or not. Each OCC in the Proportional Protection window must be considered separate if Retrocession Calculation order should be created automatically or not.
 
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Unable to close Technical Worksheet - SICS is abending - when linking to a HL with a date outside the IP

Solution:
When booking on a technical worksheet and linking a Headline loss to the detail, and the Date of Loss (both from and to date) is outside the Insured Period of the Business, then the message AC0249 must be presented, both when the Claim Basis is defined as <None> (working fine) and when it is not defined at all (currently this is when it abends).

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Trying to remove the linked remittance from the Account Balance Group but the function is disabled if the group contains a Partially Settled balance

Solution:
When a balance group, Settlement Balance Group or Account Balance Group, contains of balance(s) that are Partially Settled and it has a link to a Remittance, we must make sure it is possible to select the option Remove Link To Remittance. Today this option is disabled if the balance group contains a Partially Settled balance, so we need to have this option enabled and if selected, we must make sure the remittance is correctly delinked so that the remittance can be used elsewhere.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Walkbacks when closing worksheets containing a mixture of ORPs with and without IGC setup.

Solution:
When booking takes place on a worksheet, either manually created or created from the 'import from spreadsheet'-function, and the worksheet contains prop treaty Retrocessionaire Participations, some with a link to an IGC IAB and some without such a link, then we must make sure the system handle each business separated when worksheet is closed. This means that when it comes to the process of checking of linked IGC IAB, and if automatic booking shall take place on this or not, it must handle each individual ORP on the worksheet separate to prevent the abend.

Workaround:
When booking on prop treaty ORPs, make sure the worksheet do not contains a mixture of businesses with and without link to IGC IAB

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Showing value for 'new amount' which EC corresponding flag unticked  when 'View Balance details'

Solution:
When the View Balances Details is opened from the Worksheet Closing window, and the user select the option As Of Date in the bottom left corner, the system will add the column Previous Amount and New Amount. In that process the system must check all entry codes on the list of details, and for each of the entry codes with the As Of Date tick box selected on the Entry Code properties, the system shall display the Previous Amount and the New Amount. This is additional to the logic of today where the Previous Amount is shown only based on the fact that there is a Previous Amount stored for the detail in the database.
 
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
1. Automatic reinstatement calculation abends when worksheet contains expense reserve (reserve expense, client ibnr lae, and/or acr lae) and deductions are to be calculated on reserves.
2. Deductions on reserves not always calculated.
3. Reinstatement details for Client ibnr and ACR included in claim balance, and not in reinstatement balance

Solution:
1. Ensure that deductions are calculated correctly when defined, and also when expense reserves are included in worksheet. The deduction basis is the entry codes defined in entry code group defined for that calculation.
2. Ensure that when separate balance is created for reinstatement, all related entry codes are included in this - also reinstatement premium reserve and deduction entry codes

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Retrocession of Claim Amount distributed with incorrect share

Solution:
When details are booked automatically on non prop treaty ORP coming from OCC the system must check the sum of the details on the ORPs if they match the respective detail on the OCC multiplied with the Total Placement percentage. If it don't match, then the system will make an adjustment to the last ORP so that the sum match the detail on the OCC multiplied with the Total Placement percentage. In case any of the ORPs have the Automatic Booking flag NOT selected, this adjustment to the last ORP shall not take place. The adjustment on the last ORP can only take place if ALL ORPs on the placement list have the Automatic Booking flag selected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect Accounting Period is assigned to the Retrocessionaire Participation (ORP) when running the Retrocession Calculation Order and the system parameter Accounting/Retrocession/ 'Book Future Due Items on RP' is active.

Solution:
When running the Retrocession Calculation Order and the system parameter Accounting/Retrocession/ 'Book Future Due Items on RP' is active, system must compare the Due Date of the OCC 'as Original' booking detail (i.e. the source detail) against the 'Acct as of'' date of the ordered Retrocession Calculation Order. If Due Dates of the source bookings <= date in the field 'Acct as of' of the ordered account, the bookings must be allocated the AccYearPeriod from the ordered account. If Due Date of the bookings > date in the field 'Acct as of' date of the ordered account, the date in the field 'Acct as of ' of the next account number must be checked. If Due Date <= this date, assing corresponding AccYearPeriod to the bookings, else continue to check the next one.
This check must be performed for the Outward Cedent's Contract. And the AcctYearPeriod assigned to the OCC 'as Booking' detail must also be assigned to the ORP detail. (The check of the Due Date must not be considered in this step i.e. when assigning AccYearPeriod to ORP details)

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Client review technical worksheet without changing anything in 'worksheet closing' screen and click on button 'worksheet', SICS updated 'last updated by' value

Solution:
On the Worksheet Closing Window, both Technical and Claim worksheet, when the user click the Worksheet button or the OK button WITHOUT updating any information on the Worksheet Closing Window, then we must make sure the system does not update the Last Updated By/Date on the worksheet table (AC_WORKSHEET).

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Original Premium/Loss Reserves are getting opposite sign for FC1 on ORP when Retrocession Calculation order is executed for last Quarter

Solution:
Preconditions:
Both System Parameters Functional Currency is in use and Use FC Rate From Source Business is active.
When running the Retrocession Calculation Order on the LAST account for the Accounting Year, for an OCC with Portfolio Conditions defined with Calculation Method Pct Of Reserve (either on Premium or Loss portfolio), so that the existing reserves are reversed, we must make sure the Functional Currency Amount on the reversal detail has the same sign as its Original Amount.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected
The wrong sign can be updated by a script

Problem:
Not recalculate deduction VAT on ORP when cut Fac OCC protection from IAB

Solution:
When booking takes place on an Assumed Business protected by a Fac OCC, which is placed to ORPs, so that the bookings are automatically retroceded to the Fac OCC and to the ORPs, the system also automatically calculates the deductions from the Deduction Conditions on the ORP (or inherited from the Fac OCC), including VAT both on premium and deductions. This is working fine.
When you later remove the Fac OCC from the protection of the Assumed Business, the system shall reverse all the bookings both on the Fac OCC and on the ORPs, and here we must make sure the system also reverse the VAT on deductions, same as it does for the VAT on the premium.
When you later add a Fac OCC on the protection of the Assumed Business, the system shall book existing details on the Assumed Business to the Fac OCC and on the ORPs, both premium and calculation of deduction and here we must make sure the system also calculate and books the VAT on premium and the VAT on deductions.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect solution of SICSR-14203 causes that Automatic Booking is not read when closing worksheet at OCC and it is distributed wrongly to all retrocessionaires.

Solution:
Fix in SICSR-14203 must be rolled back and solved correctly.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Unexpected commission/deduction calculated on reinstatement when deduction is an amount.

Solution:
Deductions recorded as an amount must be ignored in reinstatement premium calculation
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
After run retrocession calculation order to check 'As original' booking's target, SICS showing NULL, only after SICS refresh, 'As Original' booking's target can be shown.

This issue possible happens for manually run order or auto trigger orders.

Solution:

 
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Reinstatement premium calculation on Main Section uses the booked premium on child sections, and does not include premium not yet booked when use deposits in reinstatement calculation is activated

Solution:
Reinstatement premium calculation on Main Section should consider both booked and not yet booked premium on child sections when use deposits in reinstatement calculation is activated.

Workaround:

Root Cause:

Extent of Impact:
Sectioned business with claims on main section, and premium/deposits still to be booked on child sections

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Enhancement SE-929, Use FX Headline for TW Details Linked to HL, Not Working properly

Solution:
1. Code change:
When system parameter 'Use FX Headline for Technical Worksheet Details Linked to Headline' is active and a detail on the Technical worksheet is linked to a Headline Loss (HL) the system will use the exchange rule for Claim if existing, but if no rule for Claim exists, then the system should look for a matching rule for Technical, and if no rule for Technical exists then use existing default exchange rule. Currently the system ignores the rule for Technical and look directly for the default exchange rule.

2. Documentation change:
The description of the system parameter 'Use FX Headline for Technical Worksheet Details Linked to Headline' should be like this:
Selected: When booking on a Technical Worksheet and for a detail linked to a Headline Loss, the system uses the FX rules defined for worksheet type Claim and if the Exchange Rate Category is FC - Daily Rate then the system will use the FX Date of Loss date as defined on the Headline Loss itself, if this is in use, else the HL Date of Loss from date,
If FX Headline is not defined, or there are no special FX rule for Claim, then the regular Technical Worksheet rules are used.
The occurrence year is automatically set to the year of the selected Headline Loss, and the details are excluded from the Occurrence Year Allocation order.

Cleared: The system uses the FX rules defined for Technical Accounts. The Occurrence Year is defaulted if the parameter is activated, and the details are included in the Occurrence Year Allocation order.

Relevant when: You want to book your proportional accounts on technical worksheets only, but apply the FX rules for Claim, and allocate all such details to the year of the Headline.

Workaround:
To get the exchange rate for the functional currency calculation according to the Date of Loss on the linked Headline Loss you must define the Exchange Rule for Claim as Exchange Rate Category Daily Rate

Root Cause:
Missing part in the implementation of SE-929 and wrong description of the system parameter 'Use FX Headline for Technical Worksheet Details Linked to Headline'

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System allows IGC linking to FAC ORP (ORP not linked to OCC) and transfers booking directly done on ORP

Solution:
When manual booking takes place on a Fac ORP linked to an IGC IAB, then the bookings are correctly copied to the IGC IAB. When bookings takes place on the original AB protected by this Fac ORP, then these bookings are correctly retroceded to the Fac ORP, but we must also make sure these bookings are copied to the IGC IAB.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
If you on a Multi Year Contract you have sub periods with different Premium Types, e.g. Flat Rate and Fixed Rate, defining e.g. Flat Premium Condition and then answer 'Yes' on BS0699 'Do you want to copy this condition to all sub periods within this multi year contract, where condition is not defined', details are also copied to Deposit Premium Condition (i.e. Premium Type 'Fixed Rate')

Solution:
When on a Multi Year Contract and you have sub periods with different Premium Types, e.g. Flat Rate and Fixed Rate, upon saving the Premium Condition (Deposit or Flat Premium Condition), the system must check if other sub periods have the same premium type and only copy condition to sub periods with same premium type and with no Premium Condition previously defined

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Web service updateLifeCycleStatus is updating Registration Complete flag fields even if flag is already activated

Solution:
When executing web service updateLifeCycleStatus with tag isRegistrationComplete set to True, implement a new check if the updated Business / Life Cycle Status is already having flag Registration Complete set to active.
If the flag is already activated, the web service must be stopped by new error message ''Registration for this contract is already complete'' and DO NOT update fields 'Complete Updated By' and 'Complete Updated Date'.
In all other cases, the system must work in the same way as before.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When assigning an Outward Cedent's Contracts protection to an assumed business automatically by selecting the Program Program it belongs to, the system does not validate the Account Group of the Assumed Business against the Account Group of this OCC.  

Solution:

When assigning one or more Outward Cedent's Contracts automatically by selecting the Program Program they are part of, the system should validate the Account Group of the Assumed Business against the Account Group of these OCCs.  If it is not matching, the system should stop the user with an error message.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When uploading intermediaries gives intermediary placements with 'Government Tax Accounting' task, while manually to add intermediary, 'Government Tax Accounting' tax isn't selected by default.

Solution:

 When uploading Intermediary and Intermediary Placements via pop-up option 'Upload Intermediaries with Retrocessionaires', the task 'Government Tax Accounting' must not be assigned to the Broker by default.
Just like system correctly works when creating Intermediary and Intermediary Placements via SICS online.

Workaround:
Manually deselect task 'Government Tax Accounting' from Broker on the loaded Intermediary and Intermediary Placements

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Net Premium on Premium and Limit conditions is not calculated correctly in some situations

Solution:
When the Premium and Limit conditions are opened and the system calculates the Total Net Premium, the system reads the Deduction conditions to find the total deduction to subtract from the Total Gross Premium. In this process we must make sure the system also subtract a deduction even if it is not mapped to an entry code.

Workaround:

Root Cause:
Caused by SICSR-7057 in version 4.9.5

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
It is not possible to enter the Cedent's Participation in the Deductibles Conditions.

Solution:

The Loss Corridor field Cedent's Participation should not only show a lead text.  It should also have a belonging input field for a percentage

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When changing the Life Cycle Status of a contract to Offer Accepted, the system gives a validation error message: Definite Life Cycle Status can not be chosen as long as a Business Partner is Provisional.  This is even if the provisional partner is not present at the period for which we are changing the status.  

Solution:

When changing the Life Cycle Status of a Business to Definite, the system should make sure that all definite insured periods have only Business Partners with an Approved status.  If there on any of these periods is a Business Partner in Provisional status, the system must stop the user. This should be the case even if the changes of status is for a later insured period.  If however an insured period has a partner with Provisional status, and this period is in a non-definite life cycle status (e.g. informational), the system should NOT stop the user.  

Workaround:

Root Cause:

Design

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The default 'Share from 100' is wrong for Assumed Intra Group Contracts created from an internal retrocessionaire when this is part of a Fac OCC.   

Solution:

When creating an Assumed Intra Group Contract from a Retrocessionaire Participation in a FAC OCC, the ‘from 100%’ on the Share Conditiona of the assumed business should not be taken from the 'from 100%' of the internal Retrocessionaire.  Instead, the system should take it from the ‘Retroceded of 100%’ on the Internal Retocessionaire Participation.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When the system parameter 'Default only leaf section at protection assignment' is Selected and the the user does not select a leaf section at protection assignment, after save, the system sets the Outward Cedent' Contracts main section to protect the assumed business.

Solution:

When the system parameter 'Default only leaf section at protection assignment' is Selected, and the user has selected Add Outward Cedent's Contract and here have selected and OCC, if the user does NOT select a section before selecting Save, the system should NOT default the OCC's Main section. The system should instead ask the user to select a section. 

 
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Unable to Renew Unplaced Share (USH).

Solution:
Level of Business: Unplaced Share:

It should be possible to renew an Unplaced Share just like it correctly worked in SICS 4.5.2.
This should apply to both Proportional and Non-Proportional Unplaced Share.
Should work in SICS P&C and SICS Cede.

Declination Reason:

Workaround:

Root Cause:
SC-109

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When trying to select only one value of Life Cycle Status on Find Business, the system resets the selection to all values at 'Find Now' selection. The resulting table always shows all found life cycle statues despite user selection.

Solution:

When making a selection in the Life Cycle Status part, e.g. Quoted, and then selecting Find Now, the system should not add back the default values.  Instead, it should keep the selection made and only find businesses corresponding to this selected Life Cycle Status.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When Premium Rate is set to 0,00, the premium is not recalculated, but premium amount is kept as if manually entered

Solution:
When premium is calculated from a Premium Rate (e.g. SUPI * Fixed Rate), the premium rate should always be used if entered - also if the entered rate is 0,00. (If Premium Rate is 0,00, then the calculated EPI (e.g.) is 0,00)

Workaround:
Manually change premium amount(s) to 0,00

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
On Protection Assignment, the blue color indicates at what section level the protection is linked. When renewing a Single Treaty Protection, no section is displayed in blue.

Solution:

When a Single treaty Protection is assigned to an assumed business, the linked section level is displayed in blue. When renewing the Single Treaty Protection, the same section should be displayed in blue also on the new insured period.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Claim Document production does not allow to pull a claim reference for a specific type only.

Solution:
Introduce support to pull claim reference for a specified type only. The types should be those defined in Claim Reference Type table,

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Possible to use entry codes not defined in assigned User Restriction entry code group when entry codes are used on open worksheets.

Solution:
Prevent changes to worksheets containing entry codes not available for user
Prevent copying and reversal of such worksheet to other worksheets
Prevent adding restricted entry codes to worksheets
If entry code restricted for a user is defined as default entry code on a claim worksheet, the worksheet must be created without that entry code.
If entry code is defined as default FGU entry code, the FGU record must be defined without that entry code.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Closing claim worksheet, the system doesn't validate if the classifications of IAB & IGC match when Require Complete Registration is selected and Create Closed Worksheet in Intra Group Contract bookings is NOT selected

Solution:
When closing Claim worksheet for an assumed business where an IGC exists for one of the protecting Fac OCC placements, the system must validate that the same classification is selected for both the assumed inward business as well as the Intra Group. If not the same, bookings cannot be done before it has the same classification is applied. Error message CM0602 must be given.
This must also be the case when Require Complete Registration system parameter is selected and Create Closed Worksheet in Intra Group Contract bookings is NOT selected.

Workaround:
Make sure Assumed business and Intra Group has the same classification. If changing classfication, it must be done both on Inward business, Outward business and Inward IGC business

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Missing validation that date of loss is within insured period when claim condition is not defined or empty

Solution:
The system must validate that date of loss is within insured period when claim condition is empty/not defined.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Find Claim Program does not support multiple partners in BP field

Solution:
Find Claim Program should support multiple partners as criteria for one partner type; eg Broker, and retrieve all which has either and matches any other search criteria.
 
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The message text in CM0180 does not reflect changed display name for Type of Risk

Solution:
Change the message so that it refers to Display name, similar to corresponding message appearing on business BS0237

Workaround:
Change message text in System Administration Utility

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
cannot register claims with loss date outside insured period, although within Original Policy Period, on Risks Attaching

Solution:
When claim basis is Risks Attaching, the system must validate that the losses are within Original Policy period, and that the OPP start date is within Insured Perio.

Workaround:

Root Cause:
SICSR-20434

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System requires date of loss to be within insured period, although it is within original policy period with a start date within insured period, when claim basis is not defined

Solution:
When claim basis is not defined and claims trigger is none, and original policy period has a start date which is within insured period, the system should allow loss dates which falls within the original policy period.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The system raises a validation error when date of loss is not within insured period although Claims Made is within the Insured Period.

Solution:
When Claims Trigger Date is within insured period, and claims trigger is Claims Made, the system must allow date of loss which is empty,prior or equal to the Claims Trigger date. There should be no validation against the Insured Period.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
eMessaging Claim Worksheets triggering Claim Action Date Notifers result in Intervening Update error on the User.

Solution:
Remove Notifiers from the User Edit Bubble

Workaround:
Turn off functionality to set the Claim Action Date by adding to
'Base Company Specific Settings - System Parameter Types - Claim Specific - Claim Action Date Not Defaulted For - Dispositions'
while also having the Accounting Update checkbox cleared

Root Cause:
Generation of Notifiers being included in the User object edit bubble.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
eMessaging Claim Movement messages abend on linking to previous CM when there is an intervening TechAccount mesage that matches referencing.

Solution:
Referencing for ClaimMovements should check the type of the message in queries and only return ClaimMovement messages.

Workaround:
Manually link the ClaimMovement to an Adjustment (which links to the ClaimMovement of that adjustment).

Root Cause:
Missing check on type of message in queries and mtaching TA messages with same references as CM.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Lloyds reinstatement TA on Technical Worksheet for per Premium are not grossed up in eMessaging using the rule to Automatically Book Deductions.

Solution:
It should be possible to Gross-Up the Reinstatement Premium booking on a Technical Worksheet as per Premium Sub-Category entry codes as the Reinstatement Brokerage deduction can already be automatically calculated.i.e. for an RIP booking then gross-up the EC based also on Entry Code Sub-Category for Reinstatement Premium.

Workaround:
Do not include the Technical Reinstatement bookings on a Lloyds message in the automatic booking of deductions and continue to book as RIP Net of brokerage or place a stop flag on the eMessaging Entry Code mapping for RIP on Technical to allow user to Swap to Worksheet manually adjust the booking.

Root Cause:
Lloyds EDI messages with RIP on a Technical Worksheet have only ever included the net RIP amount and if automatically booked have only ever been RIP net of Brokerage Deduction.

The Automatic Gross-up Premium and Book Deductions function only performs the Gross-Up part on Entry Codes that have EC Sub-Category of Premium i.e. not applied to EC with ECSC Reinstatement

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

References for ReinsurerReference for contract and claim are identical. This cannot be valid.
Messages contain incorrect values and cannot automatically reference.

Since the release of SICS 20.1.4 For all response messages, they are not being automatically linked to their corresponding claim movement message.

In order to process the response messages I have to manually add the claim worksheet to the response message (which is very time consuming).

Before the new release we did not have this issue.

Some examples are below.

Could you please look into why the response messages are not being linked to the claim movement message and advise how this can be resolved ASAP.

Solution
LIRMA Response messages contain values for broker claim reference and should match the advice on that. Contract Reference should not be required to match.for LIRMA Response.

Workaround:
Manually reference and contact Service Provider regarding invalid references.

Root Cause:
Invalid message references.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Lloyds Syndicate Proportional Treaty Statement (message function) TA with only claim payment item will block on ApplyTechnicalRule - The message has no bookable items

Solution:
ApplyTechnicalRule - The message has no bookable items should only arise in this case if there are no claim balances referenced (single balance manually linked)or matching Bulk Reference balance(es) ). A TA with only claim payments to be updated should pass through and perform the CW update. Only a message that would do nothing at all should be stopped.

Workaround:
Identify the message with Message Function Claim Signing.
A) Identification for Claim payment only Credit cr

If the transaction is lm_treaty_statement_cr and all TA Amt Item types match current_payment_losses_and_expenses_for_contract
then Claim Signing

B) Identification for Claim payment only Debit dr

If the transaction is lm_treaty_statement_dr and all TA Amt Item types match current_payment_losses_and_expenses_for_contract
then Claim Signing

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
TA invoice message cannot find claim while referenced CM message has correct claim auto-attached where there is an Inactive Claim with the same Sender / Cedent Claim Reference.

Solution:
When linking a TA to a Claim via a Sender reference then disregard any Inactive claims that are located using the Sender Claim Reference.

Workaround:
Progrss the CM to at least create a worksheet at which point the TA would link via the CM links.
Remove (claim references from inactive claims.

Root Cause:
Inactive claims considered when searching via Sender Claim Reference and no preceeding method has made a link.

Extent of Impact:
The TA will only link via the CM if the CM has created a worksheet. If that is not the case yet then it will try to link to a claim via other methods and if by Sender Claim Ref. will possibly find and consider inactive claims.

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
1 Incorrect Refresh grid When we update the item's details the grid is not displaying the updated values. Another action is needed to get the grid updated.
2 Find in' does not work Selection container shows only the value of the first row (Message)
3 Sort by Object Items column (Object) is incorreclty sorted
4 Items collapsed After all actions (Sort/Find in...) in grid, the items are collapsed. We would prefer never to collapse items and to see them all as the current screen was working before implementing the grid
5 Column view Column view change does not always work

Solution:
Ensure that the left pannel refreshed after updates, and that the values are sortable and can can be found using selection criteria.
When the items of a tree are filtered or sorted then the tree automatically collapses. This is the same as in e.g. Find Business and will not be changed.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
eMessaging is automatically creating bookings for Profit Commission and Management expenses on an Insured Period that only has PC on child sections, not on Main Section. On-line on a worksheet there is no automatic calculation performed in this case. This is resulting in booking on another Section which has PC booked on an invalid AC which triggers the error message.

Solution:
eMessaging should perform the same checks as the on-line Automatic Calculation and not automatically calculate PC/ME bookings if there is no PC Condition at Main Section level.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System crash processing CM message for FGU Claim booking where bus IP has only written share

Solution:
When booking FGU from eMessaging then the current share on the business should be used as per other cases.
The validity of the share is controlled by other validations and the FGUClaimAmountsValidationRule should just use the current share be it Signed or Written.

Workaround:
Override the FGUClaimAmountsValidationRule

Root Cause:
FGUClaimAmountsValidationRule

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
A message linking to a previous message and setting the Insured Period Reference from that continues to perform the UMR referencing step. This may result in an incorrect IP being referenced if the UMR points to a single / different Insured Period.

Solution:
If the eMessage references to an Insured Period using the Previous Message then it should stop referencing the Insured Period as in all other cases.

Workaround:
Check that the UMR is correct on contracts and do not ignore any relevant warnings / error problems on the eMessage.

Root Cause:

Extent of Impact:
Message linking via a previous message (including sender contract reference) but there being a different insured period with that sender contract reference on the UMR field of the insured period.

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
If a ClaimMovement message has claim_no_amounts indicarot then a Worksheet may still be created via Swap to Worksheet and left open.
If the message is subsequently Processed it goes stright through to Processed without a) Waiting Aprroval if set to do so and/or b) Does not Close the Claim Worksheet.
This results in a Claim Worksheet being left open and upon trying to Close stops with the Message that a linked eMessage is Waiting Apporval (although it is in Processed state)

Solution:
If a Claim Movement Message has claim_no_amounts it should Require Aprroval and go into Waiting Approval status regardless of it making any booking.

Workaround:

Root Cause:

Extent of Impact:
Waisting Apporval functionality in use and
ClaimMovement messages with claim_no_amounts indicator set but actually having amounts and using Swap to Worksheet. to crreate an open worksheet

Impact on Existing Data
Impossible to Close a Claim Worksheet linked to an eMessage that is Waiting Aprroval but in Processed status.

Recovery Method for Existing Data Affected

Problem:
SREF - Country +++

Solution:

Corrected wrong joins.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The object ORP Retroceded Amount (Base ) Dim has some wrong select statement issue in universe, as its not giving any correct value in Webi.  

Solution:

Select statement for *ORP Retroceded Amount (Base) Dim *should be checked and corrected.

Declination Reason

Problem:
SPC - Ref ClmOrAssExp
Solution:

*Correct join
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

SQL Sever GL Universe - Wrong joins for BYRP table

Solution:

Joins corrected

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

SQL Server GL Universe - SJ_REF_COBAcc wrong joins

Solution:

Joins fixed.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: 
Reporting on claim UDF does not return data

Solution: 
Correct the universe

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Object Retroceded (G) Pct showing wrong percentage because of multiple ORP life cycle phases in SPC Main SICS 20.4 and OPC Main SICS 20.4. The present derived table with is calculating wrong values.

Solution:

The present derived table need some changes so that it can count correct number of insured periods. 

Problem: There is a wrong join in SPC Main SICS 20.4.

Solution: The join should be corrected.

UDD_BUSINESS_L1.OBJECT_ID = USER_DEF_COND_L1.FK_USER_DEF.

Declination Reason: 

Problem:
Claim Condition and Reference Data wrong joins

Solution:

Join corrected

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The problem is the function in SICS in which the insured period can be shown as “To Be Advised”.

In order to do the same in the universe have been altered the LOV to be a CHAR instead of a DATE and the format selected for the CHAR* may not always match the date format set up of the server* which means that the LOV when selected will clash with the date format set up on the server which means we get a SQL error message in the report and it will not run.

Solution:

To change the object formatting of four objects: Insured Period Start and Insured Period End and Underwriting Year Start  and Underwriting Year End in Support class.

Declination Reason:

Problem:
Partner Universe - eMessaging Info missing
Solution:

New objects added to Partner Universe

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

It has been noticed there are some transactions that supposed to be shown in the* Balance Outstanding report* have been missing with worksheet.

Also it has been found that the object that causes this transactions missing is “Pairing Historical Dates”. If we remove this dates, these IDs will be shown in the report.

Solution:

Object Pairing Historical Dates must be checked for any join issues.

Declination Reason:

Problem:
Instalment Paid and Paid PCT wrong in SPC
Solution:
Solution from OPC duplicated.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Security Use Case Documentation of Accounting Period for Instalment missing

Solution:
Add the following description for the access right Update, of the Use Case Business Conditions Accounting Period within Installment/adjustment:

Controls access to Edit Accounting Period on the Instalments and Adjustments tab on the Limit and Premium conditions.

This function is available from the Popup Menu on the Instalments and Adjustments tab on the Limit and Premium conditions.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Update of business partner rating by web service, where referred old rating does not exists, returns no error message.

Solution:
The system should give an error message when trying to update a business partner rating and the  referenced rating does not exist.  

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Accounting Miscellaneous Parameter - Original Responsible Partner mandatory is not enabled unless parameter Use FX for Headline for Technical worksheet details linked to Headline has been activated

Solution:
It should be possible to activate the Original Responsible Partner mandatory parameter without setting Use FX for Headline parameter.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS is linking the same claim to 2 different attachment period

Solution:
When loading into Cede Interface, on a Light Claim already existing (the given Claim Id exists in SICS), ignore all the other irrelevant fields in the record, and just load the record's light detail on the existing claim / section linked to the existing claim

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The Multi GAAP Accounting Order creates worksheets on Inactive Contracts

Solution:

Make sure the Order does not create any worksheet on businesses with inactive basic status

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When you have multiple Accounting Classifications on an ORP, with split % on valid accounting classifications adding up to zero, the system does not understand that the AC split is 100%. Occurs when you have invalid Accounting Classifications with different Type of Participation, and these invalid Accounting Classifications also have split percentages

Solution:

When split % on active and valid Accounting Classifications add up to 100%, the system should work as follows:

When running the Multi GAAP Retrocession Order, the estimates/accruals should be split by Accounting Classification

When creating a technical worksheet on a placement, the To Be Split column should default to Yes. 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The DD block does not use the BUSINESS_PRTNR_REL.UPPERCASE_REF rather it uses the BUSINESS_PRTNR_REL.REFERENCE whereas queries should be performed on indexes upper case columns.

Solution:
The DD block should use the BUSINESS_PRTNR_REL.UPPERCASE_REF rather than BUSINESS_PRTNR_REL.REFERENCE

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
IS_OUTWARD flag on AC_LEDGER_BALANCE remains null after creation of worksheet through SOAP service

Solution:
Remove duplicated instance variable and mapping.
The instance variable is now mapped at generic level (available for absract queries) but is still only implemented on applicable balance types as before.

Workaround:

Root Cause:
This is caused by SICSR-16934 implemented in 20.3

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Warning message when BOAC tables are created on SQL Server 2012

Solution:

Change column size in work tables

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When mass renewing placements on an Outward Cedent's Contract by web service 'massRenewal' system returns message 'You are trying to open an edit window but there is already one opened'

Solution:
Mass renewing placement by use of web service 'massRenewal' placements should be renewed to new insured period.
Selecting 'All' - all placements should be renewed
Selecting specific placements, only the ones selected should be renewed

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function

Adding the new column named 'New Amount' in the related to SICS functionality 'Import Technical Worksheet from Spreadsheet'.

The New Amount is an optional column and will activate the replacement value function on the worksheet, i.e. the Replacement Values box is ticked, and the Previous Amount and New Amount columns are displayed. The New Amount given in the spreadsheet will be set in the New Amount column for this detail and the Amount column will be calculated according to existing online functionality.

Normally the Amount is mandatory when the spreadsheet is validated, but if the Amount column is empty for detail in the spreadsheet the system should still accept this detail as long as the New Amount is present, i.e. either Amount or New Amount is mandatory.

Exceptions when a spreadsheet is imported:

If both the Amount and the New Amount is given in the spreadsheet, the system will ignore the New Amount value. If the Entry Code on the actual detail does not allow Replacement Value, the system will not use the New Amount value given in the soap which is also according to online functionality, i.e. the user can give the New Amount in the worksheet but the system will just ignore it.

System Parameters Affected

None

Existing functionality affected

The online functionality of Replacement Value wherein the user needs to update the new amount manually. Now, the user able to update the New amount in the 'Import Technical Worksheet from Spreadsheet' spreadsheet itself and which will automatically activate the replacement value online functionality.

Aim of function

To make it possible to exclude the worksheet origin “Manual” for a specific type of business from being triggered when producing the PBR report through the WEB service for the rule defined for PBR “ Wrong Financial Period” only

System Parameters Affected

Accounting > Plausibility Rules > PBR “Wrong Financial Period” only

Existing functionality affected

Plausibility rule defined for PBR “Wrong Financial Period” only.

Aim of function

When the Assumed Businesses have been imported to the Assumed Business list on a Prop Treaty OCC, the system will perform the generation of preliminary bookings on the OCC when required. If bookings exist on the newly uploaded and linked Assumed Businesses these bookings shall be transferred to the As Original ledger (preliminary bookings) according to the retroceded shares.

System Parameters Affected

System Parameter / Business / Miscellaneous: Import Protected Assumed Business on Treaty OCC

Existing functionality affected

Protect Business

Aim of function

User having review access right but no edit technical worksheet right should be able to review technical worksheet from 'Find Accounting Worksheet' screen, if he double clicks on one open technical worksheet, SICS will open 'Worksheet Closing' screen directly.

System Parameters Affected

NA

Existing functionality affected

Double click on an Open technical worksheet from 'Find: Accounting Worksheet' screen. 

Aim of function

Bifurcation means dividing something in two parts.  In (re)insurance, bifurcation usually refers to situations in which the issues of liability and damages are separated and tried independently.  For these contracts, it is important to clearly see that they are part of the same bifurcation agreement, and therefore to group them together.

SICS offers now a new group type, Bifurcation Group, in which you may group such contracts.  You link the insured period of one of the contracts to an insured period of the other contract.  This feature includes some validations, e.g. that the group contains only businesses of the same level (e.g. only Assumed Businesses or only Outward Cedent’s Contracts).  The system clearly marks the contracts part of this group by showing the Bifurcation Group Name in their business title bar.

System Parameters Affected
None

Existing functionality affected
Maintain Business Groups
Find Business Groups
View Online Statistics
Create Business Group by Web Service
Update Business Group by Web Service

Aim of function

SICS Security Use Case 'Business Administration' offers an overall business authorization possibility for easy setup of most general rights of a user.  For exceptions to the general set up, specific use cases can be set up to restrict, e.g. update of  ‘Business Conditions Shares’, ‘Business Premium and Limit Conditions’ or ‘Business Protection Assignment.   

When not having Update access rights to the use case 'Business Administration', the user earlier was stopped only from creating new conditions.  Now the user is stopped also when editing existing conditions.  This applies to all conditions and other functions shown as 'white buttons' in the navigation bar, e.g. Share Conditions, Proportional Protection Assignment and Underwriter’s Estimates. 

System Parameters Affected

 None

Existing functionality affected

Maintain Share Condition
Maintain Premium and Limit Conditions
Maintain Deduction Conditions
Maintain Reinstatement Conditions
Maintain Deductibles Conditions
Maintain Profit Commission Conditions
Maintain Claims Conditions
Maintain Administration Conditions
Maintain Deposit Conditions
Maintain Reserve Condition
Maintain Portfolio Conditions
Maintain Internal Premium Reserve Conditions
Maintain Rebate Conditions
Maintain Index Clause
Maintain Clauses
Maintain Cancellation Conditions
Maintain Underlying Business 
Maintain Performance Management Data Return Information
Protect Inward Business by Excess of Loss protection for Common Account of Inward
Protect Outward Business by Excess of Loss protection for Common Account of Outward
Protect Business
Maintain Underwriter's Estimate's 
Edit Business by Update Business Wizard 

Aim of function

In order to better identify correct claim section, new search options for Signed Share From and Signed Share To has been introduced when search option is 'Business Identifier'. The result column also displays limit for the linked section when 'View Details' is selected. 

System Parameters affected:

Existing functionality affected

Find Claims

Aim of function

When linking a technical worksheet detail to an Original Responsible Partner, the available partners should be limited to specific type(s) of partners.

System Parameters affected

 New parameter introduced 'Restrict Original Responsible Partner type' - where none, one or more types may be defined.

 Existing functionality affected

Manual Bookings on Technical Worksheet 

Aim of function

In order to see the 'true' attritional losses a new 'grouping' level for 'Original Responsible Partner' is displayed when Original Responsible Partner is set as mandatory, and either 'Headline' and/or 'Claim' is selected as grouping level (possibly in combination with others).

System Parameters affected

 Original Responsible Partner is mandatory.

Existing functionality affected

 Analyse Business

Aim of function

The claim worksheet is created to reflect a cedent's requests, but may still be under evaluation by reinsurer, and is therefore maintained in an 'open' status. The reinsurer wants to reflect the same booking in their books, but maintained in a technical worksheet. This enhancement introduces an option to create a duplicate technical worksheet, based on the claim worksheet. When this duplicate is created, the claim worksheet is automatically locked for further changes, except for the Booking Year and Period. When the claim worksheet is inactivated or closed, the linked Technical worksheet is reversed.

System Parameters

New Claim Accounting Parameter

Processes

Create Claim Worksheet

Change Status of Claim Worksheet

Aim of function

Make it possible to identify a Business Partner specifically as a London Market eMessage Service Provider. Specific London Market features will only be activated on an eMessage with Service Provider if the Service Provider is identified as being London Market.

System Parameters Affected

eMessaging Business Partner Rule Set - Available Rules for assignment

Existing functionality affected

eMessaging London Market and London Bureau specific processing for Service Provider messages.

Aim of function

New option to import a list of business sections to be included in the Estimation Complete Mass Update. The business list can be imported from a spreadsheet, This must include Business Identifier and Insured Period Start Date. Section name can be included if only some sections on an insured period should be updated.

When the file has been imported, the businesses are shown in the mass update window, instead of the extract criteria.

When the Mass Update is run, only the listed businesses will be updated.

System Parameters Affected

N/A

Existing functionality affected

The periodic function Estimation Complete Mass Update.

Aim of function
The aim of the function is to provide additional information when system issues an error message due to Government Tax deviations. The additional information is given on a new window opened from the worksheet.

System Parameters Affected

• '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

• An error message is issued on the worksheet when e.g. deviations due to Government Tax amount not according to tax percentage defined in the Government Tax table.

Aim of function
The aim of the function is to be able to delete a Government Tax Target Entry Code or Trigger Entry Code directly from the worksheet also when details are linked

System Parameters Affected

• '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

• Deleting a Government Tax Target/Trigger Entry Code from an open worksheet;
  It is not possible to delete a Government Tax Target Entry Code or Trigger Entry Code from worksheet when details are linked. To delete a linked Trigger/Target detail, the user must unlink the details by accessing the Government Tax Linkage Detail screen. After having unlinked the details, the Entry Code may be deleted from the worksheet.

Aim of function

When ADH input data is imported from an Excel spreadsheet, cells that are formatted as Date will be converted to a string representation of the date value. This conversion uses default settings that are not always fitting.

In order to get better control over the conversion, this enhancement will add new settings on the ADH system parameter Options UI:

• 'Excel import date format' (e.g. 'dd.MM.yyyy', defaults to empty)
• 'Locale' (e.g. 'English', defaults to empty)
• 'Apply to date cells with built-in formatting only'=yes/no (defaults to 'yes')

Any date imported from an Excel spreadsheet shall be formatted accordingly.
If 'Excel import date format' is empty/missing, the pre-enhancement default settings mentioned above will be used.

Data imported from .xml files are not affected by this enhancement.

System Parameters Affected

• Automated Document Handling -> Processing Options -> Excel Import -> Date Format
• Automated Document Handling -> Processing Options -> Excel Import -> Locale
• Automated Document Handling -> Processing Options -> Excel Import -> Apply to date cells with built-in formatting only

Existing functionality affected

ADH: Import Document

Aim of function

Made the following changes to the Revised EPI Mass Update:
1. Revised EPI on a section is updated based on booked premium on the same section only. Previously it was considering booked premium on underlying sections also.
2. When Premium & Limit condition has been amended and has multiple effective periods, only the last effective period is updated. Revised EPI on the last effective period is updated based on the booked premium for the entire insured period. Previously the total booked premium was adjusted with number of days in the last effective period compared with number of days in the insured period.

System Parameters Affected

N/A

Existing functionality affected

Run the Revised EPI Mass Update (available in Periodic Functions)