eMessaging

9.19. eMessaging

This section describes the system parameters used by the eMessaging module to import and process ACORD RLC xml messages. Before using the eMessaging module, it is necessary to have the database configured correctly, and the eMessaging unlock key entered in the module unlock key window. See SICS eMessaging Setup within the Technical Documentation for full instructions.

The eMessaging System Parameters are accessed from the System parameter maintenance option within the System Administration menu.

There are seven tabs:

Processing options - controls for the import and processing of messages are managed here
Mappings - there are a number of mapping tables needed to match ACORD values to SICS values that are managed in this tab
Rules - at the heart of eMessaging are the rules that control the referencing, validation and processing of a message. The rules and their management are controlled in this tab
Default settings - manages defaults used by eMessaging.
ACORD Codes - controls the codesets supplied by ACORD and used in
eMessaging
Usage Table - manages various usages, for example allowed values in a particular element.
Message Function Identification - manages certain message processing types, for example how to identify if a message should be referenced to an instalment.

These are described more fully in the following sections.

Processing Options #

Import #

Rename Message File on Import #

Selected: The date and time are appended to the filename of each message after it is imported and before it is moved to he archive folder. This ensures each message has a unique name in the archive folder.

Cleared: The message is moved without changing the file name.

Relevant when: If you are using the job scheduler, and the incoming messages do not have unique filenames. If this option is not checked, and a message with the same name already exists in the archive folder, the recently imported message will not be moved from the inbox path to the archive path. This may cause the same message to be imported many times. Note: the Universal Unique Identifier (Uuid) validation rule will prevent multiple instances of a message from being processed.

If your incoming messages have unique file names before they are loaded into SICS (as is frequently the case: typically the file name will include the Uuid) there is no need to rename them on import.

Process on load #

Enabled only when system parameter Validate on load is not selected

Selected: Messages will begin the processing cycle automatically once they are loaded.

Cleared: The user must use the Find message window to initiate processing manually.

Relevant when: Normally we recommend that messages should be processed automatically, but during initial system setup and testing it may be useful to manage progress manually to see what is happening.

Validate on load #

Enabled only when system parameter Process on load is not selected

Selected: Messages will be validated automatically once they are loaded.

Cleared: The user must use the Find message window to initiate the message validation manually, unless the above parameter Process on load is selected.

Relevant when: You want to validate the messages automatically, but do not want the messages to be fully processed.

Business Logic #

Show References in Worksheet Window #

Selected: message related columns are enabled and shown in the Technical Worksheet Closing window. The Columns are labeled REBORD Reference and RETACC Reference. In eMessaging, the Uuid is held in the RETACC Reference. The LM Reference column is also shown.

Cleared: The REBORD Reference and RETACC Reference columns are not available in the Technical Worksheet Closing window. The LM Reference column is also hidden.

Relevant when: Select the parameter when you want to be able to see message reference columns in the Technical Worksheet Closing window.

Applicable for: P&C

Processing Payment Lag #

Selected: When processing a periodic treaty message where no matching account is found in the Administration Conditions, the due date on the technical worksheet is set equal to the Accounting Period To Date in the message + the defined Payment Lag. The period can be expressed in Day(s), Month(s) or Year(s). The Payment Lag defined here will only be used if no Payment Lag is defined on the Business’ Insured Period.

Cleared: For above bookings the due date on technical worksheet is set equal to the Accounting Period To Date on the message, unless a Payment Lag is defined on the Business’ Insured Period.

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

Applicable for: P&C

Facultative Processing Payment Lag #

Selected: When processing a facultative message with no accounting start and end dates then the system will set the due date on the technical worksheet to the MESSAGE DATE plus the defined payment lag period. The period can be expressed in Day(s), Month(s) or Year(s). Note: For the first premium booking on an Insured Period the Warranty Date, if present will be used to set due date.

Cleared: For above bookings the the due date on technical worksheet is not adjusted.

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

Applicable for: P&C

Lloyds Instlmt Due Date: #

Specify the Xpath which is used in “ModifyInstalmentDueDate” Rule for Lloyds TA eMessages. For example: “/jv-ins-re:Extension//*[local-name()=‘PremiumPayableByDate’]”

LIRMA Instlmt Due Date: #

Specify the Xpath which is used in “ModifyInstalmentDueDate” Rule for LIRMA TA eMessages. For example: “/jv-ins-re:Extension//*[local-name()=‘ActualPaymentDate’]”

Claims Due Date Additional Days #

Selected: When processing a B2B claim movement message where the modify rule ModifyClaimDueDateBookingRule is in force, the system will set the due date on the claims worksheet plus an additional number of days. The number of days is added to either Message As of Date or Message Creation Date, depending on your selection in the Claims Due Date Basis drop-down. The number of days can be specified per insured period. but in the absence of eMessaging info on an insured period, this system-wide value will be used instead.

The period can be expressed in Day(s), Month(s) or Year(s).

Values: Claims Due Date Basis: Message As of Date, Message Creation Date

Cleared: For above bookings the the due date on the claim worksheet is not adjusted.

Relevant when: You want to adjust the due date on a claims worksheet with a payment lag. B2B claim movements do not include a due-date, and neither creation date nor as-of-date correctly reflect the actual due date.

Applicable for: P&C

Outstanding Claim Processing Option #

The parameter applies for message that include an Outstanding loss item, as defined in the usage table. The processing depends on the selected outstanding claim processing option.

Values: Reverse Latest Loss Reserve or Reverse Accumulated Loss Reserve

Mandatory: Yes

Reverse Latest Loss Reserve: If the message contains an Outstanding Loss item then 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.

Reverse Accumulated Loss Reserve: If the message contains an Outstanding Loss item, 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 when processing messages that include an Outstanding Loss item.

Values: Per Section and AC (defaulted value) and Per AC

Mandatory: Yes, when the Reverse Accumulated Loss Reserve option is selected.

Relevant when: The Outstanding Claim Processing option ‘Reverse Accumulated

Loss Reserve’ is selected.

Show Lloyds Attributes in Worksheet Windows #

Selected: Lloyds related fields are shown on the worksheets. This applies for ‘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.

Default Remittance Type #

To generate the default payment type in the remittance for B2B messages, the user can select the default remittance type from the drop-down option. The selected value will be generated as the remittance payment type for B2B messages. When the rule LondonMarketServiceProvider is in force for the London market service providers, the system parameter will not affect the payment type of the Lloyds and LIRMA message.

Mandatory: Yes

Relevant when: To default the remittance payment type for B2B messages.

Applicable for: P&C

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

Relevant when: You are a Lloyds syndicate, and you need to validate Lloyds Risk code.

Where is the Lloyds Reporting Class Found in Business #

The selected Additional Classification states where the Lloyds Reporting Class is stored on the business. This is used in the rule RejectOnMessageFunctionAndReportingClass, which is intended to prevent certain messages from processing automatically based on message function and reporting class. A typical example is where a new claim must be linked to a headline loss, but only for certain reporting classes.

Values: Additional Classifications derived from Reference Data.

Mandatory: No

Relevant when: Processing Lloyds messages that must not be processed automatically

Where is the Validation Trigger for Approval Required Found #

The Check and Set Approval required rules used when processing B2B claims related messages check if the claim classification is in the usage ‘Check Approval required’. However, the specific claim classification table to be tested is defined here.

If the log functionality for Claim Category Limit is in use, the changes made on the claim for the defined claim classification table are displayed together with the claim category limit in the Claim Category Log

Values: List of Claim classification tables derived from Reference Data

Mandatory: Yes

Relevant when: Claim related messages require approval before they can be processed

Pair all Balances Created by eMessaging #

eMessaging will not normally pair newly created balances, unless this option is ticked.

Selected: eMessaging will attempt to pair each new balance it creates

Cleared: eMessaging will not attempt to pair newly created technical balances

Relevant when: For London Market messages, newly created balances should always try to pair

Which Receiver Reference Edit Routine #

Users have different approaches to embedding extra information in the Receivers Contract Reference in the message. This element is expected to carry the SICS business identifier, but may also include additional data such as underwriting year or section code. The format can normally be defined in Base Company Specific parameters/eMessaging, using a regular expression (select ‘Generic’ here), but there are specific rules for Swiss Re (select ‘Swiss Re’ here) that test multiple formats.

Values: Generic, Swiss Re

Mandatory: Yes

Relevant when: The message Receiver Contract Reference contains more than a simple copy of the SICS business identifier.

Total Deductions Entry Code #

The selected Entry Code will be used for the (total) single deduction added to the worksheet when processing a Lloyds TechAccount message.

Mandatory: No, but required when the (total) single deduction amount is to be booked on the Worksheet.

Relevant when: You should select an Entry Code in this field when the eMessage containing ‘TotalDiscoundPercentage’ in the extension and the message includes the net premium. The calculation of the single (total) deduction amount is based on the total deduction percentage. Also the autobooking rule must be selected for the Insured Period to have the deduction amount booked.

Query Acknowledgement Not Allowed #

The eMessaging view message menu includes an option to send a query acknowledgement back to the sender. Query acknowledgements can also be created when a message is discarded.

Selected: The ‘Send Query’option is disabled, as well as the ‘Save With Acknowledgement’ option when having discarded a message.

Cleared: The system provides an option to select ‘Send query’ from the message menu. From the discard window the ‘Save With Acknowledgement’ option is enabled after having filled in a text to append.

When processing a message that is related to other messages, all the related messages will be reprocessed together with a single click.

Selected: Messages related to this message will be reprocessed after this message is processed.

Cleared: Only the current message is processed

Relevant when: Automation of the processing of related message is required

Automatically Reprocess messages upon Registration complete #

When Registration Complete flag is selected on a business, i.e. registration marked complete, all the messages linked to that Insured Period shall be reprocessed.

Selected: Messages related to this Insured Period will be reprocessed after it’s Regristration Complete flag gets selected.

Cleared: Automatic reprocess of messages will not take place when registration is marked complete.

Relevant when: Automation of the processing of related messages is required.

When discarding a message, any messages related to the message are also discarded with a single click

Selected: Messages related to this message will be discarded after this message is discarded.

Cleared: Only the current message is discarded

Relevant when: Automation of the discard of related message is required. This option should be used with caution, as you may find messages you did not want to be discarded have been removed by mistake.

Apply Enhanced Error History for resolved errors #

An additional tab on the message view window shows resolved problems, and attempts to show how they were resolved. There is however an overhead for providing this additional information, so it is optional.

Selected: The resolved problem tab is shown, and a list of resolved problems is compiled for each message

Cleared: The resolved problem tab is not shown, and no list of resolved problems is compiled for each message

Relevant when: The list of resolved problems can be useful when tracking the progress of a message, and can help establish common faults that occur within the message contents.

Transfer Lloyds Proportional Claim Bookings to Ledger #

As Lloyds send claim movement messages for proportional treaties, it is important that we do not book the same item twice (once from the claim movement, and again from the treaty statement Tech Account message).

Selected: Claim movement adjustments on proportional treaties for Lloyds syndicates are booked to the business ledger.

Cleared: Claim movement adjustments on proportional treaties for Lloyds syndicates are not booked to the business ledger.

Relevant when: You are Lloyds syndicate receiving claim movement messages.

Mappings #

ACORD messages and SICS both use codes to identify particular objects. Some, like currency and country codes, are identical, but frequently the codes are incompatible. To resolve this incompatibility, mappings are required from one codeset to the other.

There are several mappings than can be created:

Class of business
Entry code
Type of participation
Area Code
Lloyds Outward Entry codes
Cause of Loss
Consequence of Loss
Claims Basis
Tax Application Entry Codes
Location Subentity
Deductible Basis
Deducible Type
Coverage Basis
Coverage Type
Classification Mapping
Entry codes outbound messages
Section Mapping
Previous Message Mapping
Duplicate Message Mapping
EMessage Extension

To view the mappings of a particular type, highlight the mapping type in the mapping column. The columns to the right will vary according to which mapping is displayed.

To edit or delete a mapping, highlight a line in the right hand frame, and select an option from the pop up menu (right click to view it). A new item can be added in a similar way, though for ’new’ it is not necessary to select an item first.

Edit and new options will open a new window dedicated to the mapping in question.

A selection of mapping options are now described further. Generally, if a mapping is not described here, it is a straightforward matching of one ACORD code to one SICS code.

Class of Business #

ACORD Class of Business: A value form ACORD RLC GeneralCodes, code set A34, Class of Business

Class of Business: A value from SICS reference data table 0003, Class of Business

Is used for sending: Generally mappings are made from ACORD to SICS. When ‘Is used for Sending’ is checked, the mapping can be used from SICS to ACORD. Such mappings are used when creating messages. It means that several ACORD values can map to one SICS code when mapping from ACORD to SICS, but each SICS value can only map to one ACORD value when mapping in reverse.

Entry Code #

Entry code is the most significant mapping set used by eMessaging. Not only does it manage what entry code is used by SICS, but it also controls how the entry code is used. As such, this mapping has many more attributes than the others.

Message Type: Select one of the ACORD message types. This allows the same ACORD code to map in different ways on different message types.

ACORD code set: ACORD have account codes in seven code subsets in their AmountCode table. For TechAccount messages, only three of these are used for mappings. Again, this allows the same ACORD code to map to different SICS entry codes, according to the codeset from which is selected.

ACORD accounting code: Each account code in the message must link to a value selected here.

ACORD amount status: If the account entry in the message has an AmtStatus attribute it must also match the value selected here. The most common value is ‘informational’. Account entries that update liquid balance do not include an AmtStatus attribute, and <none> should be selected in this case.

Message Function: This only applies for special messages that have an identified message function and have an ACORD entry that is mapped to a SICS Entry Code that has Sub-Category Premium. The default value is ‘None’ which indicates no alteration to normal functionality. This allows the user to set an entry mapping as the preferred premium mapping for a specific message function. Only the first matching mapping will be selected so at most one mapping should have a particular message function set. In the case of a message that is identified by for example the transaction type in the Message Function Identification but has a non-preferred premium entry e.g. generic ‘premium’ then it is possible to map the premium entry to the preferred entry. This could be to use a preferred SICS Entry Code for the booking such as a Reinstatement Premium entry code rather than a generic premium, to use a specific parameter on the entry mapping e.g. To be rejected indicator which would otherwise not be used or to include / exclude the entry in validation rules where the is a difference in functionality based on the ACORD entry.

To be rejected indicator: If this mapping is detected on the message, and this indicator is checked, an error will be set on the message to prevent it from processing automatically.

To be booked indicator: If this mapping is detected on the message, and this indicator is not checked, the account item that made the link will not be included on the worksheet. If the indicator is checked, the item will be included on the worksheet. Note: if the indicator is not checked, and the entry is part of the Balance amount, the control balance rule will set an error, as the worksheet total will not match the balance total.

Included in hash total test: If this mapping is detected on the message, and this indicator is checked, the entry amount will be included in the hash total test on the worksheet. The hash total test is means of controlling non-liquid amounts, the sum of which must remain constant within hash total.

TechAccount direct indicator: When this indicator is selected the Entry Code is used for booking IndividualClaimAmtItems in TechAccounts in cases where the message Sender has the flag ‘No Claim Movement Messages’ selected.

Protect entry code indicator: If the user swaps to worksheet, and this mapping is used to populate an entry code on the worksheet, and this indicator is checked, the entry code on the worksheet will be protected, and cannot be changed.

Protect amount indicator: If the user swaps to worksheet, and this mapping is used to populate an entry code on the worksheet, and this indicator is checked, the amount for the entry code on the worksheet will be protected, and cannot be changed.

Switch sign: If there is a sign mismatch between an ACORD interpretation of a code and a SICS Entry Code then the user may alter the sign of an amount on the worksheet for a specific SICS Entry Code. This may be required if e.g. the ‘Is Positive on Assumed Business’ flag is set to the opposite value or a single SICS entry code is mapped to an ACORD entry pair such as Adjustment Premium - due by/to sender. The Entry Code mapping table view has columns to aid the user in this respect. These are ‘SICS normally positive’ from the mapped SICS Entry Code and ‘Credit or debit’ which is the eMessaging interpretation of an amount on a SICS Worksheet after the SICS Entry Code flag has been applied and, if set, a subsequent switch sign.

Tax Application Entry Code #

This mapping links Tax Application elements in the message to an entry code used to book Tax amounts associated with the Application. Some the attributes in this mapping replicate similar attributes in the standard entry code mapping table.

Mapping Reference No: Unique identifier given by the system

Tax Application Type: Select one of the ACORD Tax application types. Tax applications are either added to gross premium or are deducted from gross premium. This item is mandatory.

Tax Class: Select the ACORD code for the general type of the tax applied - typical values are ‘Premium Tax’or ‘Parafiscal Tax’. This item is mandatory.

Tax Type: Tax type indicates the specific nature of the tax being applied. Select from the ACORD codeset, or choose ’none’. None is provided as some senders are unable to supply a coded tax type.

Tax Location: Taxes such as Insurance Premium Tax are levied country by country (and even state by state), so the message may carry the Location of the Tax Authority. Choose from an area (supranetity), country or state (subentity). None may also be chosen.

Tax Type Description: Senders may include a Tax Type description in the message. In cases where no Tax Type coding is supplied, the Tax Type Description is used instead to find a mapping. The text in the mapping must match the text in the message exactly - there is no provision for wild cards or Regular expressions, though the match is not case sensitive. Some senders, especially in the London Market, can be relied upon to use the same description over and over without alteration.

Message function: By specifying a message function in the mapping it is possible to allocate different entry codes for the same tax item based on the reason for the message - instalments can have a different entry code from adjustments if desired. If there is no mapping matching the message function of the message, a matching mapping without message function will be used instead

SICS entry code: Choose the SICS entry code to be used to book any Tax Application matching this mapping. It is not mandatory to enter a code here, but if there is no code, the entry code cannot be protected, and it must be manually added to the worksheet on ‘swap-to worksheet’.

To be rejected: If this mapping is detected on the message, and this indicator is checked, an error will be set on the message to prevent it from processing automatically.

Note: if the indicator is not checked, and the entry is part of the Balance amount, the control balance rule will set an error, as the worksheet total will not match the balance total.

Switch sign: If there is a sign mismatch between an ACORD interpretation of a code and a SICS Entry Code then the user may alter the sign of an amount on the worksheet for a specific SICS Entry Code. This may be required if e.g. the ‘Is Positive on Assumed Business’ flag is set to the opposite value. The Tax Application Entry Code mapping table view has columns to aid the user in this respect. These are ‘SICS normally positive’ from the mapped SICS Entry Code and ‘Credit or debit’ which is the eMessaging interpretation of an amount on a SICS Worksheet after the SICS Entry Code flag has been applied and, if set, a subsequent switch sign.

IPT related: Indicates that a Tax Application in a TechAccount message linked to this mapping is IPT related, and thus the rule TaxApplicaitionValidationRule will be applied if it is in force. TaxApplicationValidationRule is only relevant for businesses with IPT.

Type of Participation #

ACORD Type of participation: A value from ACORD RLC GeneralCodes, code set A31, Type of participation. Appears in the message as <CoverType>.

Type of participation: A value from SICS reference data table 0022, Type of Participation.

Area Code #

ACORD Supra Entity: A value from ACORD RLC GeneralCodes, code set A38, SupraEntity. Appears in the message as <Location><Supraentity>.

Area: A value from Locations/Area in SICS.

Entry Codes Outbound Message #

Entry Codes Outbound Message is used to find what entry code to be used in when creating outbound message from SICS.

Message Type: Select one of the ACORD message types. This allows the same

SICS entry code to map in different ways on different message types.

ACORD Code Set: ACORD have account codes in various code subsets in their AmountCode table. For TechAccount messages, only three of these are used for mappings. Again, this allows the same SICS entry code to map to different ACORD codes, according to the code set from which is selected.

ACORD Accounting Code: Select an ACORD accounting code to be linked to a SICS entry code. The selected ACORD accounting code will be shown in the outbound message.

ACORD Amount Status: Account entries that update liquid balance do not include an amount status attribute, and <none> should be selected in this case. The value ‘Informational’ should be selected when liquid balance should not be updated (e.g. for Reserve entry codes).

SICS Entry Code: Select a SICS Entry Code. Each SICS entry code booked with a SICS detail amount must have a link to an ACORD accounting code.

Accounting Transaction Type: Select an accounting transaction type to indicate at a high level the nature of the transaction to be included in the outbound message.

To be Include In Outbound Message: When ‘To be Include In Outbound Message’ is checked, the mappings are used when creating messages from SICS. If this indicator is not checked, the system will set an error and the message can not be created due to missing mapping.

Location SubEntity #

The codeset used by ACORD for parts of a country does not match the codeset used by SICS for States or Cities. This mapping provides the necessary links between the two. This is typically used to indicate the state or county within a country.

ACORD Location SubEntity: A value from ACORD RLC GeneralCodes, code set A53, SubEntity. Appears in the message as <Location><Subentity>.

Location: A value from Locations/State in SICS.

Use For Sending: Generally mappings are made from ACORD to SICS. When ‘Use for Sending’ is checked, the mapping can be used from SICS to ACORD. Such mappings are used when creating messages. It means that several ACORD values can map to one SICS code when mapping from ACORD to SICS, but each SICS value can only map to one ACORD value when mapping in reverse.

Classification Mapping #

Making links between a message and a SICS Account Classification can be achieved in several ways. For example. where a message has already linked to a section with only one Account Classification, this will be used by default. But where there is a choice of Account Classifications, one method of making the link is to match one or more message fields (XML component) with the corresponding SICS attributes.

As these links need to be flexible, a mapping table for Classification mappings is provided. When processing a message, the Account Classification referencing rule will be begin with the mapping with the lowest order, and will work through successive orders until either a single account classification is found (when the link is made), or there are no more orders (when an error is set).

Each mapping order must include at least one mapping pair. Where a mapping order includes multiple pairs, each pair is tested in turn. If the first pair makes a single match, the link is made and remaining pairs are disregarded. If the first pair makes no match, the remaining pairs are disregarded, and the next mapping order is tested. If the first pair matches multiple classifications, the second pair is tested. Subsequent pairs are tested until a single match is found (when the link is made) or there are no more pairs (when testing of this mapping order is ended, and we move to the next mapping order).

Typical mapping pairs might include Risk Code, High Level Reference or Class of business. Much will depend on what the sender is able to supply - London Market messages have a very limited scope for providing Account Classification identifiers.

Mapping Set Name: The name of the mapping set. Chosen by the user to reflect the nature of this mapping order set.

Order: The order determines the sequence in which mapping sets are used by the Account Classification referencing rules. Must be unique.

Mapping Pair table: The table shows the mapping pairs that exist for the mapping set. On selecting a pair, a new Field Mapping Pair window is opened.

XML Component: A message field (see Message Field definitions below).

SICS Attribute: A SICS attribute. These are provided from a Reference data table

Mapping Option: Where the XML Component contains an ACORD code, but the SICS Attribute uses a SICS code, the mapping table linking ACORD code to SICS code should be specified. Eg ACORD JVClass of Business maps to SICS Class of Business using the Class of Business mapping.

Section Mapping #

Making links between a message and a SICS section can be achieved in several ways. For example. where a message is linked to an insured Period which only has main section, this will be used by default. But where there is a choice of sections, and the processing option is to find a specific one, one method of making the link is to match one or more message field (XML component) with the corresponding SICS attributes.

As these links need to be flexible, a mapping table for section mappings is provided. When processing a message, the sSection referencing rule will be begin with the mapping with the lowest order, and will work through successive orders until either a single section is found (when the link is made), or there are no more orders (when an error is set).

Each mapping order must include at least one mapping pair. Where a mapping order includes multiple pairs, each pair is tested in turn. If the first pair makes a single match, the link is made and remaining pairs are disregarded. If the first pair makes no match, the remaining pairs are disregarded, and the next mapping order is tested. If the first pair matches multiple sections, the second pair is tested. Subsequent pairs are tested until a single match is found (when the link is made) or there are no more pairs (when testing of this mapping order is ended, and we move to the next mapping order).

Mapping Set Name: The name of the mapping set. Chosen by the user to reflect the nature of this mapping order set.

Order: The order determines the sequence in which mapping sets are used by the section referencing rule. Must be unique.

Mapping Pair table: The table shows the mapping pairs that exist for the mapping set. On selecting a pair, a new Field Mapping Pair window is opened.

XML Component: A message field (see Message Field definitions below).

SICS Attribute: A SICS attribute. These are provided from a Reference data table

Previous Message Mapping #

A ‘Previous Message Mapping’ table is available on System Parameter. User can choose the elements they want to determine what is ‘previous’. The group of elements chosen will be form a mapping set. The mapping set values are message elements. ‘PreviousMessageMappingRule’ rule will find a matching previous message based on the previous message mapping set rules defined in the System Parameter maintenance.

The previous message mapping table allows the user to specify which message elements must match before a message is considered to be previous - these might include Receivers Contract reference, Underwriting year, Contract period From date, High level reference and broker.

Alongside each item is a matching rule that indicates how the current message value must match the value.

For ’exact match’ the current message and previous values must match exactly.

For ’exact match populated’, system will only match if the value returned is not empty (unlike exact match which will match empty against empty).

For ‘contains’ the previous message value must be contained in the current message.

For ‘greater than’, the current message must have a value greater than the previous message.

For ‘greater or equal’, the current message value can be equal or greater than the previous message.

For ‘incremental match’, the current message must have a value exactly one more than the previous.

For ’less than’, the current message must have value less than the previous message.

For ’less than or equal’, the current message can have value equal to or less than the previous message.

If the current message does not include an element specified in the mapping set, it is deemed match this element on previous messages. If the current message includes an element in mapping set, the previous message must match the value.

Message Type: User will first select the message type for which the mapping set has been created.

Mapping Set Name: User can give any name to the set for easy reference.

Order: Both name and order must be unique for the message type. If they are not unique, an error is issued.

Applies to: The user is allowed to add message function(s) from the list, to which the mapping set applies. Once selected the system will either apply only sets which have a match on Message Function for the current Message or if none then only apply sets that have no selections.

Excludes: The user is allowed to add message function(s) from a list of message functions. Once selected system will ignore Sets that have a message function intersect with the current message and any potential previous messages.

Like: The user is allowed to add message function(s) from a list of message functions. Once selected, system will only consider those previous messages that have the same intersect of message functions as the current message (which can be no intersect).

XML Component: A message field (see Message Field definitions below).

Matching Rule: The set can require a particular field to have Exact match, Incremental match, Greater than Less than Exact match populated to make a link between the previous and the current message.

Duplicate Message Mapping #

Because there is a risk that the same message will be loaded and processed multiple times in eMessaging, and while both ACORD and eMessaging have some provision to prevent this, it is not exhaustive, this new rule is useful in identifying possible duplicates.

A ‘Duplicate Message Mapping’ table is available on System Parameter. User can choose the elements they want to determine what is ‘duplicate’. The group of elements chosen will be form a mapping set. The mapping set values are message elements. ‘DuplicateMessageMappingRule’ rule will find a matching duplicate message based on the duplicate message mapping set rules defined in the System Parameter maintenance.

The duplicate message mapping table allows the user to specify which message elements must match before a message is considered to be duplicate - these might include Receivers Contract reference, Underwriting year, Contract period From date, High level reference and broker.