Step-by-step Instructions
Enable eMessaging module #
In order to enable the eMessaging module, the user must enter the module key.
This setting must be entered using the System Administration function in either SICS Workstation or SICS System Administration Utility.
Once the console has started, click on “System Administration” and select “System Parameter Maintenance” function. A new window will appear. Locate and open the “Module Key” tab, enter in Edit mode and provide the value for"EMessaging Module Unlock Key", as shown in the figure below.
Create Rule Data and Factory Rule Sets #
In the SICS System Administration Utility, open the “Database Updating” function and select, in order:
- Update eMessaging Rules
- Update eMessaging Factory Rule Sets
Create eMessaging Party Memberships #
Each party, for being correctly referenced and used in eMessaging, needs to have an eMessaging Membership registered in the database. This allows SICS to map parties from a message to the objects in the database.
For registering a membership for a specific partner, open the “View Business Partner” form, select the “Details” tab and then “eMessaging” property. By clicking on the edit button you will be able to change all eMessaging settings for the partner, including eMessaging memberships.
In order to create an outgoing ACORD Settlement message to be sent to a Business Partner an Outgoing Default and Role must be set.
Define eMessaging Mappings #
As for Business Partners, SICS needs to know how to map several entities from eMessages to SICS objects.
These mappings can be defined in the System Parameter Maintenance function, under the System Administration folder. When the System Parameters form is presented, select the eMessaging tab and then the Mappings sub-tab.
From this form it is possible to create, edit or delete mappings for several kinds of objects.
For detailed description on each mapping, please refer to the System Administration Guide -> Maintain System Parameters -> eMessaging.
If a sender has No Claim Movement Messages then additional Entry Code mappings are required with the flag TechAccount direct
Define ACORD Code Usages #
SICS needs to know whether a specific ACORD code should be accepted or not and how the code must be used in the system.
This information can be entered in the Usage Table tab, under eMessaging System Parameters. The usages are Reference Data 01117 - eMessaging Acord Code Usage Type
A number of usages are mandatory for the processing of messages and additionally for Find (others apply to specific rules and their contents are optional, although to use the rule they would require an entry.) Additionally some usages are used to restrict entry (such as Find Screens) to restrict the items available for selection for example for a particular message type where the ACORD table used is general to a number of messages.
Mandatory Items:
- Informational AmtStatus - Informational
- Balance Type Due By - As above 2 entries
- Balance Type Due To - As Above 2 entries
Restricted List Items:
- Settlement Message Type
- Acknowedgment Transaction Type
A number of the above settings are suggested as being the relevant ACORD codes whereas others are optional based on the requirements of the respective validation rules. Refer to the on-line rule description for further details on each rule.
Validation Rule Items:
| Usage | Description | Version |
|---|---|---|
| Balance Type Due By | Defined here to avoid had-coding the value in SICS. Table values from General Codes BalanceAmtItem. | |
| Balance Type Due To | Defined here to avoid had-coding the value in SICS. Table values from General Codes BalanceAmtItem. | |
| Cash Loss | Used by the rule CashLossValidationRule. The rule only applies if the message contains one or more account entry codes in the Cash Loss usage table. Table values from Amount Codes TechAccountAmtItem, IndividualClaimAmtItem, TaxAmtItem. | |
| Claim Paid Entries | Used by the rule CheckClaimPaidEntriesOnMessage. The rule only applies if the message contains one or more account entry codes in the Claim paid entries usage table. Table values from Amount Codes TechAccountAmtItem, IndividualClaimAmtItem, TaxAmtItem | |
| Gross Net Entry | Used by the rule TestGrossAmountEqualsNetPremiumValidationRule. The rule only applies if the message contains one or more account entry codes in the Gross Net Entry usage table. Table values from Amount Codes TechAccountAmtItem, IndividualClaimAmtItem, TaxAmtItem. | |
| Informational Amt Status | This item is in the usage table because some senders use the StatusCoded value “Informational” (with an uppercase “I”). The standard codeset value rule is that all codes should be in lowercase. However, by adding a code value of “Informational” to the codeset, these messages can be still be processed. See the note in this document for further details. | |
| OCA Entries | Used by the rule CheckOCAEntriesOnMessage. The rule only applies if the message contains one or more account entry codes in the OCA Entries usage table. Table values from Amount Codes TechAccountAmtItem, IndividualClaimAmtItem, TaxAmtItem. | |
| Outstanding loss | Used by the rules TestForOutstandingLossesWithClaimDetailsValidationRule, TestForOutstandingLossToReverseValidationRule and TestForMultipleOutstandingLossesWithCommonOrLaterDateValidationRule. The rules only apply if the message contains one or more account entry codes in the Outstanding loss usage table. Apply Worksheet. The amounts are booked as adjustments. Table values from Amount Codes TechAccountAmtItem, IndividualClaimAmtItem. | |
| Payment means | Used by the rule PaymentMeansValidationRule. The rule only applies if the message does NOT contain a payment means in the payment means usage table. Table values from General Codes PaymentMeansCoded. | |
| Payment Means Settlement | Used by the rule PaymentMeansForSettlementValidationRule. The rule only applies if the message does NOT contain a payment means in the payment means usage table. Table values from General Codes PaymentMeansCoded. | |
| Premium Validation | Used by the rules CompareReceivedPremiumToExpected, CompareReceivedPremiumToNetAdjustmentPremium, CompareReceivedPremiumToNetInstalmentPremium, CompareSumReceivedPremiumToExpected. A rule only applies if the message contains one or more account entry codes in the Premium Validation usage table. Table values from Amount Codes TechAccountAmtItem. | |
| Sub Account Due by | Defined here to avoid had-coding the value in SICS. Used in TestSubAccountBalanceAgainstMessageBalanceValidationRule. Table values from General Codes BalanceAmtItem. | |
| Sub account due to | Defined here to avoid hard-coding the value in SICS. Used in TestSubAccountBalanceAgainstMessageBalanceValidationRule. Table values from General Codes BalanceAmtItem. | |
| Subject Premium income | Used by the apply rule AdjustedSUPIUpdateRule. The rule only applies if the message contains one or more account entry codes in the Subject Premium income usage table. Table values from Amount Codes TechAccountAmtItem, IndividualClaimAmtItem, TaxAmtItem. | |
| Claim Response Negative | Used by the rule CheckForNegativeClaimResponse and others (including create claim). The rule only applies if the message contains one of the codes in the Claim Response usage table. Table values from General Codes A155 (OriginalClaimResponseCode). | |
| Claim Response Positive | Used in Create Claim PreApplyClaimRule. Positive responses are those in this table. Table values from General Codes A155 (OriginalClaimResponseCode). | |
| CM Outstanding loss | Used in Create claim, UpdateClaim to identify entry types in the message that update Outstanding loss on the claim. Table values from Amount Codes ClaimMovementAmtItem. | |
| Accounting Split Message Function | Used by the rule ConfirmAccountingClassificationSplitsMessageFunction for TechAccount messages. Message flows included in this usage table will ignore the ‘applies to first message’ parameter, and still apply the rule. Table values from reference Data 01118, with parent TechAccount. Used by the rule ConfirmAccountingClassificationSplitsMessageFunction for ClaimMovementmessages. Message flows included in this usage table will apply the rule. Flows not in this table will ignore the rule. Table values from reference Data 01118, with parent ClaimMovement. | |
| Outstanding Status codes | Used in the rule CheckForZeroOutstandingClaim. Values in the usage table do not cause a rejection. Table values from General Codes 4405 (StatusCoded). | |
| Message Function To Be Rejected | Used in the rule RejectByMessageFunction and RejectByMessageFunctionValidationRule. Values in the usage table cause a rejection. Table values from SICS Reference Data 1118 (eMessaging Message Function). | |
| Settlement Account Type | Used in the Find: eMessaging eMessages for ACORD Settlement Account Type. ). Allows restriction of items in general table to those applicable. Table values from General Codes A22 (MessageType). | |
| Acknowedgment Transaction Type | Used in the Find: eMessaging eMessages for ACORD Acknowledgment Ack Type. Allows restriction of items in general table to those applicable. Table values from General Codes A22 (MessageType). | |
| Advised Paid | Used in Apply Claim Worksheet. Table values from Amount Codes IndividualClaimAmtItem will be booked as adjustments | Update 4.4.1 |
| Autobooking Exclusions | Used in the rule CheckDeductionsForAutoBookingValidationRule and ModifyDeductionAutoBookingRule. Values in the usage table exclude the message from the rule specific functionality. Table values from SICS Reference Data 1118 (eMessaging Message Function). | 4.3.1 |
| Deduction Entry Type | Used in Create Technical Worksheet and rules CheckDeductionsForAutoBookingValidationRule, ModifyDeductionAutoBookingRule, to identify entry types in the message that are classed as deductions for this functionality. Table values from Amount Codes TechAccountAmtItem. | 4.3.1 |
| Endorsement IP Date | Used in the rule EndorsementInsuredPeriodFromDateValidationRule and EndorsementInsuredPeriodToDateValidationRule. Values in the usage table cause validation using above rules instead of InsuredPeriodFromDateValidationRule, InsuredPeriodToDateValidationRule. Table values from SICS Reference Data 1118 (eMessaging Message Function). | 4.3.1 |
| Premium Entry Type | Used in Create Technical Worksheet and rules CheckDeductionsForAutoBookingValidationRule, ModifyDeductionAutoBookingRule to identify entry types in the message that are classed as premiums for this functionality. Table values from Amount Codes TechAccountAmtItem. | 4.3.1 |
| Skip Test Total Deduction | Used in the rule CheckTotalOfDeductionPercentagesValidationRule. Values in the usage table will cause the above rule not to be executed. Table values from SICS Reference Data 1118 (eMessaging Message Function). | 4.3.1 |
| Reject Message Function & Class: Function | Used in the rule RejectOnMessageFunctionAndReportingClass. Values in the usage table cause a rejection. Table values from SICS Reference Data 1118 (eMessaging Message Function). | 4.3.2 |
| Reject Message Function & Class: Class | Used in the rule RejectOnMessageFunctionAndReportingClass. Values in the usage table cause a rejection. Table values from SICS Reference Data as defined in System Parameter eMessaging -> Processing Options -> Were is the Lloyds Reporting Class Found in Business from SicsRefSOCAdditionalClassification and SicsRefSOCSubAdditionalClassification types. | 4.3.2 |
| Check Approval Required | Used in the rule CheckAndSetApprovalRequired, CheckAndSetApprovalRequiredPreMessageTest, CheckAndSetApprovalRequiredPostMessageTest. Table values from SICS Reference Data as defined in System Parameter eMessaging -> Processing Options -> Were is the Validation Trigger for Approval Required Found from SicsRef classification types. | 4.3.2 |
| Cancel current and original TA message | Used in the rule CheckForTechAccountReversals. Allows restriction of items in general table to those applicable. Table values from General Codes A21 (MessageFunction). | 4.3.2 |
| Cancel current and original CM message | Used in the rule CheckForClaimMovementReversals. Allows restriction of items in general table to those applicable. Table values from General Codes A21 (MessageFunction). | 4.3.2 |
| FGU Incurred | Used in the rule ValidateFGUIncurredAgainstSubPrioThreshold. Table values from Amount Codes ClaimMovementAmtItem. | 4.3.2 |
| FGU Paid, FGU Paid Annuity, FGU Paid Expenses, FGU Paid Interests, FGU Loss Reserves, FGU Annuity Reserves, FGU Expense Reserves, FGU Interest, Reserves | Used in the rule FGUBookingRule and associated Claim Update and Apply Worksheet FGU functionality. Table values from Amount Codes ClaimMovementAmtItem. | 4.3.2 |
| Claim Closed | Used in the rule CheckIfClaimIsClosed. Table values from General Codes A22 (MessageType) | 4.4.1 |
| London Reversal Entries | Used in the Apply Claim Worksheet rule to determine which bookings to consider for reversal when not booking Tech Accounts directly. Table values from General Active SICS Entry Codes. | 4.4.1 |
| Previously Paid | Used in the rule CheckPreviouslyPaidAmountOnSiDXClaim to determine which bookings to consider for the rule. Table values from General Active SICS Entry Codes. | 4.4.1 |
| TA claim payments | Used by the rule CheckBulkBookedAmount and TestSumOfLiquidDetailsAgainstClaimedSubAccountBalanceValidationRule to establish which items in a TechAccount message relate to claim payments. Usage values are from ACORD account codesets ‘IndividualClaimAmtItem’ and ‘TechAccountAmtItem’. | 4.4.2 |
| LORS Acceptance codes | Used when approving/rejecting LloydOutwards messages. The codes in this usage are those from ACORD codeset L09 that indicate acceptance of the message. | 4.4.2 |
| LORS Rejection codes | Used when approving/rejecting LloydOutwards messages. The codes in this usage are those from ACORD codeset L09 that indicate rejection of the message. | 4.4.2 |
| LORS Auto Authorised statuses | Used by the rule AutoApproveLORSMessageCarriesAuthorisation to determine which messages can be accepted automatically. Usage values are from ACORD codeset L11. | 4.4.2 |
| Approval Required Message Function | Used by the rule Set Approval Required By Message Function. Used to identify whether the message function requires approval or not. Available options are values in reference table 0118. | 4.4.2 |
| Loss Date Basis | Used by the rule Check Loss date narrative, to identify which loss date basis should be rejected. Usage values from ACORD codeset 2005 (DateTimePeriodQualifier). | 4.4.2 |
| Set acknowledgement incomplete | Used by the rule UpdateOutboundMessageStatusOnCreation to identify which incoming message types should not create outbound acknowledgement messages with status = complete. Usage values from SICS Reference data table 1106 eMessaging Document Type. | 4.4.2 |
| FGU Incurred Expenses | SICSE-665. Used by ValidateFGUIncurredAgainstSubPrioThreshold. Table values from Amount Codes ClaimMovementAmtItem. | 4.5.1 |
| Validate IPT | SICSE-229. Used by TaxApplicationsValidationRule. Table values fron General Codes A70 (TaxType). | 4.5.1 |
| Premium Date Premium Type | Used by Placing rule CheckPaymentDate. Table values from General Codes A85 (PremiumTypeCode). | 4.5.2 |
| Precautionary Claim | SICSE-1984. Used by RejectPrecautionaryClaim and PreApplyClaimRule to to set initial Claim Disposition. | 4.6 |
| Static Claim | SICSE-1984. Used by PreApplyClaimRule and UpdateClaim for setting Claim Disposition. Table values from General Codes A22 (MessageType). | 4.6 |
| Amount Status Items | SICSE-2050. Used by ApplyClaimWorksheetRule for item types to check if the amount status should be checked for recording. Table values from Amount Codes ClaimMovementAmtItem. Table values from General Codes A22 (MessageType) | 4.6 |
| Amount Statuses to Record | SICSE-2050. Used By ApplyClaimWorksheetRule to record values on balances. Table values from General Codes 4405 (StatusCoded). | 4.6 |
| Omit Account Reference | SICSE-2956. Used by IPAccountReferenceRule to skip the rule. Table values from SICS Reference Data 1118 (eMessaging Message Function). | 4.6 |
| Check Claim Limit Items | SICSE-4135. Used by CheckClaimLimits and Update Claim. | 4.7 |
| Check IP Index Items | SICSE-4135. Used by IPIndexClauseValidationRule. | 4.7 |
| Contract Level | SICSE-1865. Used by ApplySignedSharePlacingRule, SectionReferenceRule. | 4.7 |
| Section Level | SICSE-1865 Used by ApplySignedSharePlacingRule, SectionReferenceRule. | 4.7 |
| Exclude from As of Date Validation | SICSR-8316. Used by CheckAsOfDateValidationRule. | 4.7 |
ACORD Code Set XML File Maintenance #
The ACORD code sets are stored in two XML files:
AmountCodes.xml
GeneralCodes.xml
SICS is delivered with the ACORD RLC Version=“20150727” definitions. The code set XML files can be replaced by the user, if so required.
Replacing code set files in SICS Workstation #
An amount codes xml file must be saved as:
patches\AmountCodes.xml
in the SICS installation runtime folder. A general codes xml file must be saved as:
patches\GeneralCodes.xml
Replacing code set files in the SICS eMessaging server #
An amount codes xml file must be saved as:
WEB-INF/classes/AmountCodes.xml
in the web application war file structure.
A general codes xml file must be saved as:
WEB-INF/classes/GeneralCodes.xml
Viewing the contents of the default code sets delivered with SICS #
The default ACORD code set definitions used by SICS can be found in the file:
lib/acord.framework.war
The contents of a war file may be viewed by an archive application such as WinZip.
ACORD Code Set Database Maintenance #
Alternatively the ACORD code sets can be stored directly in the SICS database. SICS ACORD code sets in the database can be managed from the ACORD Codes tab under eMessaging system parameters.
In order to load ACORD code sets from the database instead of XML files the flag Store ACORD Codes in Database must be selected. To populate or update the ACORD code sets stored in the database with new code set versions released by ACORD, select Load new Codes from XML from the popup menu of the ACORD Code Set container. In the dialog that appears, the path to these files must be entered:
GeneralCodes.xml
AmountCodes.xml
ACORD codes are loaded on demand by SICS eMessaging. In order to view all the ACORD codes that are present in the database, one may select Load all Codes into Memory from the popup in the ACORD Code Set container.
By selecting an ACORD Code Set, the lower container will display all the codes in that code set. The popup menu of the lower container has functionality to manually manage codes. Still, the preferred way to manage code sets is to bulk update all codes by loading from ACORD XML files as described above.
Technical note: There are occurrences where two ACORD codes in the same code set have the same LongCode, but differing JvCode. Such cases are represented by a single ACORD code with a comma separated list of JV codes in the database.
ACORD Codeset - Missing codes used by XIS #
XIS have chosen to use some codes in their versions of the ACORD TechAccount and ClaimMovement messages that do not exist in the ACORD codesets. Whilst strictly this would be a reason to reject the messages as non-compliant with the ACORD standard, it is probably easier to add the missing codes to the codesets before they are used in SICS. The matter has been raised with XIS, and we await their response. In the meantime, the following codes should be added:
| General codes: Message function (table Id A21) | ||
|---|---|---|
| CodeEntry | ||
| LongCode: | lm_serviceprovider_update | |
| JVCode: | n/a | |
| Description: | Service Provider Update |
| Amount codes, ClaimMovementAmtItem | ||
|---|---|---|
| CodeEntry | ||
| LongCode: | lm_value_of_interest | |
| JVCode: | n/a | |
| Description: | Description: Value of Interest | |
| CodeEntry | ||
| LongCode: | professional_advisor_fees_total_paid | |
| JVCode: | n/a | |
| Description: | Professional advisor fees total paid | |
| CodeEntry | ||
| LongCode: | total_losses_plus_expense_paid_for_contract_after_retention | |
| JVCode: | n/a | |
| Description: | Total losses plus expenses paid for contract after retention |
Additional codes may need to be added as more messages are received.
ACORD Acknowledgement generation templates maintenance #
An XSL stylesheet transformation is used to generate ACORD acknowledgement templates. There is a dedicated stylesheet per ACORD version. SICS 4.8 supports generating acknowledgements in the following versions.
2003-1 through 2016-10.
Should there be a requirement to generate acknowledgements in other / newer versions, contact DXC to get new versions of the template. The templates can be upgraded similarly to the code set files, without a need for a new SICS delivery.