EDI (Electronic Data Interchange)

9.11. EDI (Electronic Data Interchange)

Note! The EDI component of SICS will no longer supported in 23.2 and higher. #

The EDI component of SICS will no longer supported in 23.2 and higher. The EDI component will continue to be functional in older versions for as long as they are contractually supported.

The functionality is still present for viewing historical data. It will not be supported in DXC Assure Reinsurance.

The Reinsurance industry relies increasingly on EDI to transmit data and update information.

P&C support EDI functionality. The EDI settings can be viewed and edited in the EDI tab’s of the System Parameters Maintenance.

Defaults #

The Default tab lets you select how you want the EDI messages to be processed.

Select System Administration from the SICS Workstation desktop.
Select the System Parameter Maintenance.
Select the EDI tab.
Select the Default tab.

JV Business Logic settings #

Field	Description
*Use SICS Sub Class of Business for processing and generating messages*	Selected: The Mapping of JV (Joint Venture) messages are defined at Sub Class of Business level. See the JV Mappings tab and select Sub Class of Business. The table for Mapping JV Sub Class of Business with SICS Sub Class of Business is defined in this tab. Selecting this Parameter also makes the Class of Business option on the JV Mappings tab irrelevant, i.e. no mappings are allowed at this level. Cleared: The Mapping of JV messages are defined at Class of Business level. See the JV Mappings tab and select Class of Business. The table for Mapping JV Class of Business with SICS Class of Business is defined in this tab. Leaving this parameter cleared also makes the Sub Class of Business option on the JV Mappings tab irrelevant, i.e. no mappings are allowed at this level. Relevant when: Use this parameter to define at which level the JV mappings are done, i.e. at Class of Business level or Sub Class of Business Level. Applicable for: P&C
*Show JV References in Worksheet Windows*	Selected: JV (Joint Venture) message related columns are enabled and shown in the Technical Worksheet Closing window. The Columns are labelled REBORD Reference and RETACC Reference. This parameter applies for RETACC and REBORD Unique Message Reference. Cleared: The REBORD Reference and RETACC Reference columns are not available in the Technical Worksheet Closing window. Relevant when: Select the parameter when you want to be able to see the REBORD- and RETACC reference columns in the Technical Worksheet Closing window. Applicable for: P&C
*Show JV Segment Information*	Selected: The Joint Venture (JV) Segment Information (segment name and -number) is shown in the beginning of each line in the message preview. Cleared: The JV Segment name and - number are not shown in the beginning of each line in the message preview. Relevant when: Select the parameter when you want the segment name and -number to be displayed in the massage preview. Applicable for: P&C
*Stop automatic processing of RETACC with claims related bookings*	* for Non-Prop Treaty * for Proportional Treaty * for Non-Prop Facultative * for Proportional Facultative Selected: You can select one or more of the above types of business. When processing JV RETACC messages with claim related bookings for the selected types of business, the system files an Error note in the message problem tab and assigns the Error status to the message. The user has the option of whether to continue and process the message via swap-to-worksheet or not. The functionality does not apply if the referenced business is flagged as an ‘EDI General Cover’. Cleared: The messages for the respective types of business are processed and technical worksheets are automatically closed when the associated booking mapping is marked “Automatic Booking”. Relevant when: You select the parameter when you want to ensure that no technical bookings of claim entries are made before consideration of manual claims bookings via the From Ground Up feature. Thus when the system processes such messages, the system will stop the processing and raise an error. Applicable for: P&C
*Check Already Booked Instalments and Adjustments*	Selected: The functionality applies for JV RETACC messages referenced to Assumed Non-Proportional Treaty Business.

Minimum and Deposit Premium:

The incoming RETACC message containing Minimum Deposit Premium (MDP) is checked against the Limit and Premium conditions of the referenced business.

When MDP instalments are recorded on the business and the entries due date, premium and net premium match, the system checks if the MDP is already booked on the business.

If the MDP is already booked (i.e. the “Autom. Booked” flag = Yes), the booked balance is updated with the “Unique RETACC Message Reference” from the message. The message status is also changed to Processed.

If the MDP is not already booked, the premium is booked on a Technical Worksheet and the “Autom. Booked” flag is set to Yes.

When there is no record of MDP instalments on the business or one of the entries due date, premium or net premium, does not match, the system stops processing the message. It files an Error note in the message problem tab and assigns the Error status to the message.

XL premium Adjustment:

The incoming RETACC message containing Premium Adjustment is checked against the Limit and Premium conditions of the referenced business.

When the referenced business has Premium Adjustment recorded, the system checks if the respective adjustment is already booked.

If the Premium Adjustment is not already booked (i.e. the “Autom. Booked” flag = No), the premium is booked on a technical worksheet. The Limit and Premium Condition is updated with Adjusted SUPI information from the message and the “Autom. Booked” flag is set to Yes.

When there is no recorded premium adjustment in the Limit and Premium Conditions or the Premium Adjustment is already booked, the system stops processing the message. It files an Error note in the message problem tab and assigns the Error status to the message.

Cleared: When processing incoming JV RETACC messages including Minimum Deposit Premium (MDP), the MDP is booked without checking if the premium is already booked. The GNPI information from the message is booked on the Technical Worksheet, but the premium condition is not updated with this information.

Relevant when: You select this parameter when you want to book MDP for non-proportional business as soon as possible and to ensure that all related information is available in the premium conditions. MDP instalments are booked from the Limit and Premium Conditions before receiving a RETACC message containing the MDP. When processing the message containing the already booked instalments, the system sets the message to Processed.

Applicable for: P&C

Facultative Processing Payment Lag

The parameter applies for RETACC messages involving non-periodic accounts and referenced to facultative business. Non-periodic account implies that “DTM07(240) - Reinsurance Accounting Period” is not specified in the message header. The referenced business can be a “facultative folder treaty” flagged as an EDI general cover or a single facultative treaty.

Selected: When processing a non-periodic RETACC message for facultative business, the system sets the due date on technical worksheet equal to the message date [DTM07(137)] plus the defined payment lag period. The period can be expressed in Day(s), Month(s) or Year(s).

Cleared: For non-periodic RETACC messages the due date on technical worksheet is set equal to the message date.

Relevant when: You want to adjust the due date on technical worksheet with a defined payment lag.

Applicable for: P&C

Default Settings #

Field	Description
Default Path for Generated Messages:	The path to the file directory where the generated messages are stored. Values: File reference Functional Impact: Path to file directory. The user preferences settings can override the global value for the individual user. Mandatory: Yes Applicable for: P&C
*Mandatory Note Update on Discard/Restore Message*	Selected: When the Discard/Restore menu option is used from the View Messages window, you are prompted to enter a reason. The text is visible in the note attached to the message. The Parameter applies for JV messages. Cleared: It is optional to enter a reason why the message is discarded or restored. Relevant when: Select the parameter when you want to ensure that a reason is always attached to the message when the message is discarded or restored. Applicable for: P&C
Note Update on Mark as Examined Message	Selected : When the Mark as Examined menu option is used from the View Messages window, you are prompted to enter a Reason Note. Additionally you may enter a Reason Code and a Responsible Unit. Both the text and the Reason Code/Responsible Unit are visible in the note attached to the message. None of the above information is mandatory to enter. Cleared: The window to enter notes will not appear automatically when the Mark as Examined menu option is selected. Relevant when: You select this parameter when you want to make it easier for the users to make necessary comments when messages are marked as examined. Applicable for: P&C, Life
*Rename Batch by appending Batch Name and Batch Number:*	Selected: The batch is renamed in the archive when importing batches to the system, i.e. the Batch Type and Batch Number is added to the original batch name. Cleared: The original batch name is filed in the archive. Relevant when: Select this parameter when you want to add more information to the original batch name, e.g. to make each batch easier to identify in the archive. Applicable for: P&C

Validation Rules #

The Validation Rules tab shows all the EDI validation rules in SICS. The Validation Rules are hard coded into the SICS system. The rules are made available within each bureau by Message Type and Message Sub Type (excepting Joint Venture).

Set Validation Rule #

Select System Administration from the SICS Workstation desktop.
Select the System Parameter Maintenance
Select the EDI tab
Select the Validation Rules tab
Select a validation rule for the applicable bureau.
Select edit from the pop-up menu if you want to access the different editing options.

You are allowed to modify some of the validation rule fields. Dependent on the rule type you can turn the rules on or off, set tolerance upper- and lower limits, and switch the error type between error and warning. For certain LIMNET rules that allow validation to section level you may turn validate to section on or off.

Field Description - Validation Rules #

Applicable for: P&C

Field	Description
*Message Type:*	Describes the type of message the validation rule applies for. Values (listed per Bureau): Joint Venture: <None>, REBORD, RECLAM, REDIAL, RESETT, RETACC ILU: <None>, CLASS, Settlement, Signing LIRMA: <None>, CLASS, Settlement, Signing Lloyds: <None>, CLASS, Settlement, Signing VNAB: <None>, Signing Mandatory: No, when a message type is defined as <None> the rule applies to all relevant message types at that level
*Message Sub Type:*	For each Message Type, Message Sub Types are defined to further describe the type of message the validation rule applies for. Values: A text field defined in the system, e.g. Claim Response, Premium Broker Error, For declaration only signing, etc. Mandatory: No, when a message sub type is defined as <None> the rule applies to all relevant message sub types at that level
*Description:*	A short description of the validation rule. Values: Free text
*Is On:*	Indicates if the validation rule is activated or deactivated. Values: Yes/No Functional Impact: The validation is only performed if this indicator is activated, i.e. value is yes.
*Lower Limit:*	If the validation rule has a tolerance associated, this value indicates the lowest tolerance limit. Values: Numeric value without sign Functional Impact: When a field on the message is compared against a field in SICS and the fields are not identical, a tolerance test is done between the fields. If the difference is less than the lower tolerance limit, an error/warning message is set. Example: If your value is 100 and you want values from 98 to be accepted, you enter 2 in the lower limit field. Mandatory: No
*Upper Limit:*	If the validation rule has a tolerance associated, this value indicates the upper tolerance limit. Values: Numeric value without sign Functional Impact: When a field on the message is compared against a field in SICS and the fields are not identical, a tolerance test is done between the fields. If the difference is greater than the upper tolerance limit, an error/warning message is set. Example: If your value is 100 and you want values to 105 to be accepted, you enter 5 in the upper limit field. Mandatory: No
*Tolerance:*	Indicates the types of value the lower/upper limits are defined by. Values: Date, Percentage and Value Mandatory: Yes
*Rule Type:*	Indicates during which processing steps the validation rule is used. Values: Applying Rule, Field Rule, Pairing Rule, Pre Applying Rule and Referencing Rule Derived From: The Reference Data Type ‘00226 EDI Rule Type’ Example: Pre Applying and Applying are internal rules, e.g. used when validating a newly created claim or when closing a worksheet. Mandatory: Yes
*Can Permanent Override:*	Indicates if the rule can be permanently overriden or not. Values: Yes or No Functional Impact: Determines if the rule can be permanently overridden when applied to subsequent messages on the same Insured Period or Claim. When No, the rule may not be permanently overridden. Mandatory: No
*Error Type:*	Indicates what kind of error to generate. Values: Warning, Error Mandatory: Yes
*Section Level:*	Indicates whether the rule allows validation to section level. Applies for Certain LIMNET rules. Values: Yes, No Functional Impact: When this indicator is activated, i.e. the value is yes, the system validates to the message referenced section. When the value is no, the validation is done to the main section. Mandatory: No

LIMNET Mappings #

Select System Administration from the SICS Workstation desktop.
Select the System Parameter Maintenance
Select the EDI tab
Select the LIMNET Mappings tab

The EDI LIMNET specific settings are defined in the LIMNET Mappings tab. These settings are called mappings because they link EDI LIMNET information to SICS information.

The mappings are Cause of Loss, LIMNET Entry Code, ILU Cancellation and Treaty Statement.

Cause of Loss Mappings #

Select Cause of Loss from the list of mappings in the LIMNET Mappings tab. The defined mappings are displayed in a table.
You can create new mapping, edit existing mappings or remove mappings by selecting an item from the table and select the applicable option from the menu.

The table is a transitional table that links the Claim Sub Category code on the EDI LIMNET message to the SICS Cause of Loss. If an EDI message has a CLASS Claim Sub Category that is not defined in the table, or the referenced claim has a different cause of loss, the system will raise an error.

Field Description - Cause of Loss Mappings #

Applicable for: P&C

Field	Description
*CLASS Claim Sub Category:*	The EDI LIMNET cause of loss information Values: CLASS Claim Sub Category values defined for each Claim Sub Category code on the EDI message, e.g. PL = Public Liability. Derived from: The Reference Data Type table 00551 EDI Claim Sub Category. Mandatory: No
*Cause of Loss:*	Different Cause of Loss values defined in SICS Values: Cause of Loss values such as Explosion, Pollution and Robbery. Derived from: The Reference Data Type table 00523 Cause of Loss Mandatory: No

LIMNET Entry Codes Mappings #

Select LIMNET Entry Code from the list of mappings in the LIMNET Mappings tab. The defined mappings are displayed in a table.
You can create new mapping, edit existing mappings or remove mappings by selecting an item from the table and select the applicable option from the menu.

When LIMNET EDI messages arrive, certain codes determine how the bookings should be made. EDI LIMNET Entry Types need to be linked to SICS Entry Codes, which can be accomplished in the LIMNET Entry Code mapping window. Here you can also determine processing options, such as preventing a value from being changed on the worksheet. The Entry Code table holds details of which entry codes to use when creating worksheet items. You can change the entry code and the indicators.

Field Description - LIMNET Entry Code Mappings #

Applicable for: P&C

Field	Description
*Message Type:*	The LIMNET Message Type the Entry Code mapping applies for. Values: CLASS, Settlement and Signing Mandatory: Yes
*Message Sub Type:*	For each Message Type, Message Sub Types are defined for further description of the type of message the mapping applies for. Values: Message Sub Type values are determined by the defined Message Type, e.g. Class Claim Signing, Premium Signing Mandatory: No, if <none> is selected all Message Sub Types for the selected Message Type apply.
Entry Type:	A user-defined description of the Entry Type Code. Values: Free text to define the Entry Type Derived from: The Reference data Type table 00195 EDI Entry Type Mandatory: Yes
*Entry Type Code:*	A market defined code that is included in the message. Values: A code determined by the selected Entry Type Derived from: Entry Type field Mandatory: Yes
*Entry Code:*	The SICS user defined Entry Codes. Values: User defined codes, e.g. 10 Premium, 20 Commission Mandatory: Yes
*Early Documentation Indicator:*	If the EDI message has the attribute Early Documentation Indicator set as Yes, the system will generate the entry code having this indicator. Values: Yes/No
*To be Rejected Indicator:*	If the EDI message generates an entry code with this indicator, the system raises an error and the user must confirm the entry code in worksheet. Values: Yes/No
*Premium Reserve Release Indicator:*	If the EDI message of sub type Premium Signing generates an entry code with this indicator, the system checks if the premium reserve release amount on the message matches the original reserve transaction. Values: Yes/No
*Reinstatement Indicator:*	If the EDI message of sub type Premium Signing generates an entry code with this indicator, the system ignores the default Accounting Classification spilt when booking to an Insured Period where the EDI Accounting Classification processing option is “Process According to Accounting Classification Split”. For reinstatements, it is likely that the premium belongs 100% to one accounting classification, and therefore the standard split does not apply. Should only be set on reinstatement entry types. Values: Yes/No
*Validate to EPI Indicator:*	If the EDI message of sub type Premium Signing generates an entry code with this indicator, the system compares the premium on the message with the premium on the referenced business. Values: Yes/No
*Test Gross equals Net Indicator:*	If the EDI message of sub type Premium Signing generates an entry code with this indicator, the system checks that the gross amount equals the net amount on the message. Values: Yes/No
*Include in Hash Total Test:*	The system calculates a control total for each balance on the worksheet. Only items having this field defined, as ‘Yes’ are included in the test. Values: Yes/No Default: Yes
*Protect Amount:*	When an EDI worksheet is created, this field indicates if the amount linked to the applicable Entry Code should be protected in the worksheet. Values: Yes/No Default: Yes
*Protect Entry Code:*	When an EDI worksheet is created, this field indicates if the Entry Code should be protected in the worksheet. Values: Yes/No Default: No

ILU Cancellation Mappings #

Select ILU Cancellation from the list of mappings in the LIMNET Mappings tab. The defined mappings are displayed in a table.

When archiving LIMNET EDI signing messages from ILU, cancellation messages are encountered. These messages can represent cancellations of various application types that correspond to different message subtypes in SICS. The message subtype will be set based on the entry type of the cancellation.

Field Description - ILU Cancellation #

Applicable for: P&C

Field	Description
*Entry Type:*	Type of cancellation message. Values: Text to define the Entry Type, e.g. Cancellation of Claim Paid, Cancellation of PM Entry, Cancellation of Treaty Statement Mandatory: Yes
*Message Sub Type:*	The SICS message types that correspond to the different Entry Types. Values: Values defined for the Message Type ‘Signing’, e.g. CLASS Claim Signing, Premium Signing, Treaty Statement Signing (Refer to the reference data type 00181 EDI Message Sub Type.) Mandatory: Yes

Treaty Statement Mappings #

An incoming identifier on a LIMNET EDI Treaty Statement message is converted into a type description. A treaty statement is a type description on which entry codes can then be defined.

To view the Treaty Statement list:

Select Treaty Statement from the list of mappings in the LIMNET Mappings tab. The defined mappings are displayed in a table.
You can create new mapping, edit existing mappings or remove mappings by selecting an item from the table and select the applicable option from the menu.

The Treaty Statement Item table holds details of the individual items on incoming treaty statement signings, and whether each item should be booked to the ledger.

Field Description - Treaty Statement mappings: #

Applicable for: P&C

Field	Description
*Bureau:*	The EDI Bureau each treaty statement item applies for. Values: ILU, LIRMA Mandatory: Yes
*Identifier:*	The identifier on an incoming LIMNET EDI Treaty Statement message. Values: A numeric code Mandatory: Yes
*Type code:*	A market defined code that is included in the message. Values: A code determined by the selected Type Description. Derived from: Entry Type field Mandatory: Yes
*Type Description:*	A user-defined description of the Entry Type Code. Values: Free text to define the Entry Type Derived from: The Reference data Type table 00195 EDI Entry Type Mandatory: Yes
*Is to be booked:*	Indicates whether the individual items on the incoming treaty statement signings are to be booked to the ledger. Values: Yes/ No

JV Mappings #

Select System Administration from SICS Workstation desktop
Select the System Parameter Maintenance
Select the EDI tab
Select the JV Mappings tab

This tab presents all EI JV specific settings. The settings are called mappings because they link EDI JV information to SICS information.

The mappings are JV Supra Entity, Class of Business, Subclass of Business, JV Entry Code and JV Type of Participation.

JV Supra Entity Mappings #

The JV Supra Entity values defined by JV are mapped together with Areas defined in SICS.

Select JV Supra Entity from the list of mappings in the JV Mappings tab. The defined Mappings are displayed in a table.
You can edit the existing items by selecting an item and then select Edit from the menu.

The Mapping items displayed are already defined in Locations, which is part of the Reference Items. You are allowed to maintain the mapping from the System Parameters. Your changes will also be updated in the Reference Items.

Field Description - JV Supra Entity Mappings #

Applicable for: P&C

Field	Description
*Type:*	Area Group Category. Values: User defined, alphanumeric, minimum 1 digit, e.g. Geographical, Political Derived from: The Reference Data Type table 00020 Area Group Category Mandatory: No
*Name:*	The name of the Areas defined in the Locations, which is part of the Reference Items. Values: User defined, alphanumeric, minimum 1 digit, e.g. Worldwide, Scandinavia Mandatory: Yes
*JV Supra Entity:*	Identifies the geographical scopes to which the entry pertains or (for facultative accounts) the location of the risk. Values represent the identification of the country or the supra-entity. Values: Defined in the JV Segment Guide, e.g. Scandinavia, Europe, America Derived from: The Reference Data Type table 00591EDI JV Supra Entity Mandatory: No
*Code:*	A short name or code to identify the Area Name Values: User defined, alphanumeric, minimum 1 digit, e.g. WW, SCA Mandatory: Yes

Class of Business Mappings #

This tab is relevant when the parameter ‘Use SICS Sub Class of Business for processing and generating messages’ located in the Default tab is cleared.

Select Class of Business from the list of mappings in the JV Mappings tab. The defined Mappings are displayed in a table.
You can create a new item, edit the existing items or remove items by selecting an item and then select the applicable option from the menu.

The mapping of JV messages is defined at Class of Business level and the table shows the mapping of JV Class of Business with SICS Class of Business.

Note! When the Class of business mappings are available, the Subclass of Business mappings are not.

Field Description - Class of Business Mappings #

Applicable for: P&C

Field	Description
*JV Class of Business:*	The Class of Business reported in the message. Values: Values defined in the JV Segment Guide, e.g. Fire - Hotel, Marine Ocean Cargo Derived from: The Reference Data Type table 00251 EDI JV Class Of Business Mandatory: Yes
*JV Class of Business Code:*	The code that applies for the selected JV Class of Business. Values: Numeric codes, e.g. 234, 307 Derived from: The Reference Data Type table 00251 EDI JV Class Of Business Mandatory: Yes
*Class of Business:*	The SICS Class of Business values to be linked with the corresponding JV Class of Business. Values: Values defined in the Reference Data Type table 00003 Class of Business, e.g. Fire Insurance, Marine Cargo Mandatory: Yes
*Class of Business Code:*	The code that applies for the defined Class of Business. Values: Abbreviation to describe the Class of Business, e.g. FI, MA Derived from: The Reference Data Type table 00003 Class of Business Mandatory: Yes
*Is used for sending:*	Indicates whether the mapping item is used for sending in addition to receiving messages. Values: Yes/No

Subclass of Business Mappings #

This tab is relevant when the parameter ‘Use SICS Sub Class of Business for processing and generating messages’ located in the Default tab is selected.

Select Subclass of Business from the list of mappings in the JV Mappings tab. The defined Mappings are displayed in a table.
You can create a new item, edit the existing items or remove items by selecting an item and then select the applicable option from the menu.

The mapping of JV messages is defined at Sub Class of Business level and the table shows the mapping of JV Class of Business with SICS Sub Class of Business.

Note! When the Subclass of business mappings is available, the Class of Business mappings are not.

Field Description - Subclass of Business Mappings #

Applicable for: P&C

Field	Description
*JV Class of Business:*	The Class of Business reported in the message. Values: Values defined in the JV Segment Guide, e.g. Fire - Hotel, Marine Ocean Cargo Derived from: The Reference Data Type table 00251 EDI JV Class Of Business Mandatory: Yes
*JV Class of Business Code:*	The code that applies for the selected JV Class of Business. Values: Numeric codes, e.g. 234, 307 Derived from: The Reference Data Type table 00251 EDI JV Class Of Business Mandatory: Yes
*Sub Class of Business:*	The SICS Sub Class of Business values to be linked with the corresponding JV Class of Business. Values: Values defined in the Reference Data Type table 00050 Sub Class of Business, e.g. Fire Industrial Mandatory: Yes
*Sub Class of Business Code:*	The code that applies for the selected Sub Class of Business. Values: Abbreviation to describe the Class of Business, e.g. FIREIND Mandatory: Yes
*Is used for sending:*	Indicates whether the mapping item is used for sending in addition to receiving messages. Values: Yes/No

JV Entry Code Mappings #

When a JV EDI Message is imported, certain codes determine how the bookings should be made. JV Entry Codes are linked to SICS Entry Codes.

Select JV Entry Code from the list of mappings in the JV Mappings tab. The defined Mappings are displayed in a table.
You can create a new item, edit the existing items or remove items by selecting an item and then select the applicable option from the menu.

The Entry Code table holds details of which entry codes to use when creating worksheet items.

Field Description - JV Entry Code Mappings #

Applicable for: P&C

Field	Description
*JV Entry Code:*	Joint Venture booking codes. Values: A Number and a text, e.g. 150-Value Added Tax, 18-Brokerage Mandatory: Yes
*JV Status:*	JV Entry Code Status. Values: <None>, Informational, Non Advised, Not Available, Provisional, Requested Mandatory: No
*Entry Code:*	SICS user defined Entry Codes. Values: 10 Premium, 20 Commission, etc Mandatory: No
*Is used for Sending:*	Indicates which JV Entry Codes to use when creating JV messages. Values: Yes/No
*Display Order:*	Indicates which order the Entry Code shall be shown in the Bordereau window of a JV messages. Functional Impact: Entries coming form EDI JV message will be shown as part of the Bordereau window. You can set the order how the Entry Codes should appear in the window. The lowest number you enter will be shown first in the Bordereau. Values: Numeric values 1- 999

JV Type of Participation Mappings #

When a JV EDI Message is imported, JV Type of Participation values are linked to SICS Type of Participation values.

Select JV Type of Participation from the list of mappings in the JV Mappings tab. The defined Mappings are displayed in a table.
You can create a new item, edit the existing items or remove items by selecting an item and then select the applicable option from the menu.

Field Description - JV Type of Participation Mappings #

Applicable for: P&C

Field	Description
*JV Type of participation:*	Type of Participation values defined by JV. Values: Quota Share, Surplus, Excess of Loss etc. Mandatory: Yes
*JV Type of Participation Code:*	Type of Participation code values defined by JV and linked to a JV Type of Participation value. Values: Numeric codes, e.g. 001, 004, 012 Derived from: JV Type of Participation Mandatory: Yes
*Type of Participation:*	Type of Participation (Reinsurance Product) values defined in SICS. Values: Quota Share, Surplus, Excess Of Loss etc. Derived from: Reference Data Type table 00022 Type Of Participation Mandatory: Yes
*Type of Participation Code:*	Type of Participation code values defined in SICS and linked to a SICS Type of Participation value. Values: Abbreviation to describe the Type of Participation, e.g. QA, SURPLUS, XL Derived from: Reference Data Type table 00022 Type Of Participation Mandatory: Yes
*Is used for sending:*	Indicates which JV Type of Participation values to use when creating JV messages. Values: Yes/No

Notifications #

Select System Administration from SICS Workstation desktop.
Select the System Parameter Maintenance
Select the EDI tab
Select the Notifications tab

This tab presents settings for notification as batches are imported and processed. It lets the System Administrator select which users can subscribe to those notifications. There are mainly three sources from which the system fetches the users to be notified:

The “EDI Notification Subscribers” list on this tab. (See Modify Notification Subscriber below for more information.)
The “Responsible Persons” defined on the “Classifications” tab on businesses. (See Add/Edit Responsible Persons in the Handle Business Life Span chapter in the User’s Guide.)
The “Responsible Persons” defined on business partners. (See Assign Internal Responsibilities per Partner in the Handle Partners chapter in the User’s Guide.)

Events #

Field	Description
*Notify on Unsuccessful Import of Batches*	Selected: The users listed as ‘EDI Notification Subscribers’ for corresponding message type (LIMNET or JV) are notified upon unsuccessful import of batches into the system. Cleared: Users are not notified upon unsuccessful import of batches. Relevant when: Select the parameter when you want unsuccessful import of batches to be notified. Applicable for: P&C
*Notify on Successful Import of Batches*	Selected: The users listed as ‘EDI Notification Subscribers’ for corresponding message type (LIMNET or JV) are notified upon successful import of batches into the system Cleared: Users are not notified upon successful import of batches. Relevant when: Select the parameter when you want successful import of batches to be notified. Applicable for: P&C
*Notify on Unsuccessful Process of Messages*	Selected: Users are notified when messages have been unsuccessfully processed. The users to notify are: For EDI LIMNET messages the EDI LIMNET responsible person on the referenced business is notified. If there are no business referenced or no EDI LIMNET responsible person on the business, the users listed as ‘EDI Notification Subscribers’ with EDI LIMNET Handler Role will be notified. For EDI JV Booking Messages (RETACC and REBORD) the business linked to the booking mappings on the message are examined. If any of the businesses have assigned one or more ‘EDI JV Handler’, this/these user(s) are notified. If none is found, the ‘EDI JV Handler’ assigned the referenced receiving business partner is notified. If none is found, the ‘EDI JV Handler’ assigned the referenced sender business partner is notified. If none is found, the users listed as ‘EDI Notification Subscribers’ with EDI JV Handler role will be notified. For EDI JV messages not being booking messages, the users listed as ‘EDI Notification Subscribers’ with EDI JV Handler role will be notified. Cleared: Users are not notified when messages have been unsuccessfully processed. Relevant when: You should select the parameter when you want to notify users about unsuccessfully processed messages. Applicable for: P&C
*Notify on Successful Process of Messages*	Selected: Users are notified when messages have been successfully processed. (For information about the users to notify see Notify on Unsuccessful Process of Messages.) Cleared: Users are not notified when messages have been successfully processed. Relevant when: You should select the parameter when you want to notify users about successfully processed messages. Applicable for: P&C
*Notify on Unsuccessful Generation of Messages*	Selected: Users are notified when messages have been unsuccessfully generated. (For information about the users to notify see Notify on Unsuccessful Process of Messages.) Cleared: Users are not notified when messages have been unsuccessfully generated. Relevant when: Select the parameter when you want to notify users about unsuccessfully generated messages. Applicable for: P&C
*Notify on Successful Generation of Messages*	Selected: Users are notified when messages have been successfully generated. (For information about the users to notify see Notify on Unsuccessful Process of Messages.) Cleared: Users are not notified when messages have been successfully generated. Relevant when: Select the parameter when you want to notify users about successfully generated messages. Applicable for: P&C

Modes #

Field	Description
*Notify in Unattended Mode*	Selected: Notifications are done also when using the Scheduler to automatically import and process messages. Cleared: Notifications are not done when using the Scheduler to automatically import and process messages. Relevant when: Select the parameter if you want notifications to be done when using the Scheduler to automatically import and process messages. Applicable for: P&C
*Notify in Attended Mode*	Selected: Notifications are done when using the EDI system in manual mode. Cleared: Notifications are not done when using the EDI system in manual mode. Relevant when: Select the parameter when you want the notifications to be done when using the EDI system in manual mode. Applicable for: P&C

Modify Notification Subscribers #

You can select which users can subscribe to notifications.

Select the Edit button from the EDI Notification tab.
Select Add Notification Subscriber from the menu if you want to apply a user to the list.
Select an existing EDI Notification Subscriber and select Edit Notification Subscriber from the menu when you want to make changes
Or, select an existing EDI Notification Subscriber and select Remove Notification Subscriber when you want to delete.
Define Role and select the Subscribing User of the Role.
Click OK

Field Description - Notification Subscripter #

Applicable for: P&C

Field	Description
*Role:*	Defines which Message Type the subscribed user is notified about Values: ‘EDI JV Handler’, ‘EDI LIMNET Handler’
*Subscribing User:*	The users having one of the above roles defined as Responsible Role in the Security Settings. (Refer to Responsible Roles information in the Security chapter in the System Administrator’s Guide.) Values: Name of users Derived from: The selected role determines which users to be listed Mandatory: Yes, when a role has been defined.

LIMNET Business Logic #

The LIMNET Business Logic tab lets you define how the LIMNET messages are processed.

Define LIMNET Business Logic #

Select System Administration from SICS workstation desktop
Select the System Parameter Maintenance
Select the EDI tab
Select the LIMNET Business Logic tab.

Applicable for: P&C

Field Descriptions - LIMNET Business Logic #

Field	Description
*London Market Module in Use*	Selected: Activates the London Market Module. The related accounting fields are shown. The ‘Multiple open claim worksheet per claim to section link’ errors that may be raised based on the setting of the Claims System Parameters are overridden. Cleared: The London Market Module is not in use. Relevant when: Select the Parameter when the London Market module is to be activated.
*Use Multiple Unique Claim Reference*	Selected: When referencing a CLASS message to a claim, the system tries to find the claim via the Unique Claim Reference (UCR). It searches only those claims that are linked to the referenced business. Cleared: When referencing a CLASS message to a claim, the system attempts to find the claim via UCR only. If a match is found, the system links the message to the claim, and the business for that claim. Relevant when: The parameter only applies for LIMNET CLASS messages. Select the parameter if you want the system to search for claims on the referenced business only.
*Allow to Close Claims*	Selected: When processing a LIMNET CLASS message, the system automatically closes a claim for which Outstanding Amount is zero for all currencies and Outstanding Amount Qualifier is C, N or B for all currencies. Cleared: The system does not close the claim automatically. Relevant when: Y ou want the system to automatically close claims when outstanding loss reserves are zero.
*Are “File Request” and “Information Required” Positive member Responses?*	Selected: When processing a LIMNET CLASS message, the system handles the member responses ‘File Request’ and ‘Information Required’ as positive responses and provides an automatic processing of such messages. Cleared: When processing a LIMNET CLASS message, the system handles the member responses ‘File Request’ and ‘Information Required’ as neutral responses. The messages are processed with the worksheet left open, awaiting a positive response. Relevant when: You want CLASS messages with ‘File Request’ and ‘Information Required’ member responses to be treated as positive responses and processed automatically.
*Where is the Lloyds Risk Code Found in Business?*	The selected Additional Classification states where the Lloyds Risk Code is stored on business. When processing a Lloyd’s message, the system validates if the Lloyds Risk Code on the message matches the one on the referenced business. Values: Additional Classifications derived from Reference Data Mandatory: Yes
*Update Date of Loss After Claim Creation*	Selected: The system is allowed to update the Date of Loss (DOL) on an existing claim. The system updates DOL From on the referenced claim with the Loss From Date on the message if the message Loss From Date is within the insured period of the referenced business, and the DOL From on the claim is the same as the inception date of the insured period. If the Loss To Date on the message is a valid date within the insured period of the business, and the DOL To on the claim is the same as DOL From, the system updates the claim Date of Loss To with the message Loss To Date. Cleared: The system is not allowed to update the date of loss on an existing claim. Relevant when: The Date of Loss is not always known when a new claim is created. If the CLASS message does not include a valid Date of Loss, the claim is created with Date of Loss From equal to the inception date of the insured period of the referenced business. The correct Date of Loss is received later in a subsequent message. Select the parameter if you want an automatic update of the Date of Loss on existing claims.
*Use Special Booking Year/Period Rules*	When creating claim or technical worksheets through EDI Limnet messages, the system generates the attributes Accounting Year and Period, Accounting Period From and To dates and Booking Year and Period. SICS provides two methods of generating these attributes dependent on the setting of this system parameter. Selected: The special rules are designed to work with booking terms set to quarters. (Refer to System Parameters Type - System Parameters Type - Booking Terms chapter for more information.) See Accounting Year/Period and Booking Year/Period in the Processing EDI LIMNET Messages chapter in P&C User’s Guide for description of the attributes. Cleared: The standard rules aim to use as much data as possible from the message and will revert to the base company default settings where necessary. See Accounting Year/Period and Booking Year/Period in the Processing EDI LIMNET Messages chapter in P&C User’s Guide for description of the attributes. Relevant when: Select this parameter when you want to use the special booking rules when creating claim and technical worksheets through EDI.
*Outstanding Claim Processing Option*	The parameter applies for treaty statement signing messages with item types ‘OSCLM’ or ‘OSCLMADJ’ present, or if the message contains no treaty statement items. The processing depends on the selected outstanding claim processing option. Values: Book Last Ouarter Loss Reserve, Reverse Lastest Loss Reserve and Reverse Accumulated Loss Reserve Mandatory: Yes
*Book Last Quarter Loss Reserve*	(formerly option E): If the current signing is the last quarter statement for the referenced business, and accounting basis is ‘Underwriting’, the system books the current outstanding amount. Otherwise it does not book the outstanding loss amount. If no statement items are present on the message, the system books a zero amount regardless of the Outstanding Loss Qualifier setting.
_Reverse Latest Loss Reserve	(formerly option S): If the message Outstanding Loss Qualifier is ‘N’, the system finds the latest outstanding claim entry on the ledger for the referenced business and books a reversal of the previous outstanding amount. It then books the current outstanding loss reserve. If the message Outstanding Loss Qualifier is ‘X’ or blank and there are no outstanding loss amounts on the message, the system books a zero amount. No reversal is needed.
Reverse Accumulated Loss Reserve:	When processing a treaty statement signing message containing loss reserve information, the system will calculate the current accumulated loss reserve on the business ledger (per the message’s insured period, section, accounting classification, currency and entry code). This reserve is then reversed and replaced by the loss reserve on the current message. The aggregation of current loss reserve can be based on section and accounting classification or on accounting classification alone. The choice of aggregation level is made in the parameter Aggregation. If the message does not contain any loss reserve information, the functionality will not be triggered and no reserve bookings made.
Aggregation:	The parameter determines the aggregation level of current loss reserve upon processing of treaty statement signing messages with item types ‘OSCLM’ or ‘OSCLMADJ’ present. Values: Per Section and AC (defaulted value) and Per AC Mandatory: Yes, when theReverse Accumulated Loss Reserve option is selected. Relevant when: The Outstanding Claim Processing option ‘Reverse Accumulated Loss Reserve’ is selected and the ‘Reference to Sections’ functionality is in use.
*Signings Referencing: Original Signing Reference Must Include Stamp Number*	The primary method of linking a LIMNET EDI signing message to a business insured period is to look for a balance where the London Reference matches the original signing reference in the message. Normally, the London Reference on EDI balances is made up of the Stamp number and the signing reference. But some migrated balances may not include the stamp number (because it is not available in SICS classic). For this reason, SICSnt was built with two searches of London reference - first with the stamp number, and then again without the stamp number. The second search can lead to incorrect linkages being established if the same original signing reference (without stamp number) appears many times in SICSnt.
Selected:	The second search is omitted, and only London References containing a matching stamp number are considered.
Cleared:	The system works as originally designed, and will look for London References without stamp number included
Relevant when:	Referencing LIMNET EDI signing messages to insured periods in SICSnt.
*Use EDI CLASS*	Selected: Limnet CLASS messages can be processed, and Claim Signing messages originating from CLASS will be handled accordingly. Claim worksheets will show the EDI specific fields. The EDI FGU Figures tab on claim is enabled, and incurred FGU information is automatically created upon processing of New Claim and Existing Claim messages. Cleared: Limnet CLASS messages cannot be processed and Claim Signing messages are all treated as ’non CLASS’. The Claims worksheets will not display the EDI-specific fields (such as Our Sequence Number and Broker Sequence Number). The EDI FGU Figures tab on claim is disabled and no creation of EDI FGU information is made. Relevant when: Limnet CLASS messages should be processed
*Show Lloyds Attributes in Worksheet Windows*	Selected: Lloyds related fields are shown on the worksheets. This applies for ‘Movement Reference’, ‘DTI Audit Code’, ‘Fil Code 1’, ‘Fil Code 2’, ‘Fil Market Code’, ‘Risk Code’ and Trust Fund Code’. Cleared: Lloyds related fields are not shown on the worksheets. Relevant when: Select the parameter when you want Lloyds Attributes to be shown in worksheets.
*Use EDI VNAB Number*	Selected: The VNAB number is enabled on the section properties of a business. Cleared: VNAB number is not enabled on sections. Relevant when: All messages in a VNAB batch carry a VNAB number. Select the parameter if you want the system to be able to add the number to the section properties on a business.
*Reference To Section*	Selected: When referencing an EDI LIMNET message to a business in SICS, the system attempts to link the message to a section. The referencing depends on the message type.
*CLASS ‘NEW’ and Premium and Treaty Statement Signings:*	The system identifies the accounting classification (AC) id of the message member reference and searches for the matching EDI identifier on the accounting classifications of the referenced business. When an AC id matches, a link between the message and the account classification and the section that it represents is established. If none of the AC identifiers match, or if no account classification part is included in member reference and the referenced business has EDI identifier on the accounting classifications, the system raises a referencing error on the message.
*CLASS not ‘NEW’:*	The system examines the referenced claim scope of cover relationship and sets the message section to that of the claim relationship. The system searches the previous balances for the claim relationship and selects the one with the highest Our Sequence Number. Provided a balance is found, and then the message accounting classification is set to the classification of the first detail.
*Claim Signing Messages:*	The system references the message to a claim worksheet and sets the message accounting classification to the classification of the first detail. Cleared: The system references messages to main section and the first accounting classification. A validation rule selects businesses where sections exist, allowing the user to reject messages linked to such business and to process them manually to the correct section. Relevant when: Select the parameter when you want the system to reference messages to sections.