v4.8 Change to Rules

v4.8 Change to Rules

v4.8 Changes to rules #

The following rules have been changed and will require action on the part of users to maintain existing (or comparable) functionality.

PreviousMessageMappingRule has replaced PreviousMessageReferenceRule. The old rule is still available and both are optional to allow switch-over.

Example Mapping Sets and XPATH:

NAME FRK_MSG_TYPE IS_NOT_SPECIFIC ORDER_N DESCRIPTION FRK_MATCHING_RULE
TA Receiver Ref CP RCSR ACORD_TECHACC N 110 TA Contract Period Start End EXT_MATCH_POP
TA Receiver Ref CP RCSR ACORD_TECHACC N 110 TA Sender Contract Section Reference EXACT_MATCH
TA Receiver Ref CP RCSR ACORD_TECHACC N 110 Receiver Contract Reference EXT_MATCH_POP
TA Receiver Ref CP RCSR ACORD_TECHACC N 110 TA Receiver Contract Section Reference EXT_MATCH_POP
TA Receiver Ref CP HLR ACORD_TECHACC N 112 TA HighLevelReference EXT_MATCH_POP
TA Receiver Ref CP HLR ACORD_TECHACC N 112 TA Contract Period Start End EXT_MATCH_POP
TA Receiver Ref CP HLR ACORD_TECHACC N 112 Receiver Contract Reference EXT_MATCH_POP
TA Receiver Ref Risk Code ACORD_TECHACC N 114 TA Lloyds Risk Code EXT_MATCH_POP
TA Receiver Ref Risk Code ACORD_TECHACC N 114 TA Contract Period Start End EXT_MATCH_POP
TA Receiver Ref Risk Code ACORD_TECHACC N 114 Receiver Contract Reference EXT_MATCH_POP
TA Receiver Ref CP SCSR ACORD_TECHACC N 120 TA Sender Contract Section Reference EXT_MATCH_POP
TA Receiver Ref CP SCSR ACORD_TECHACC N 120 TA Contract Period Start End EXT_MATCH_POP
TA Receiver Ref CP SCSR ACORD_TECHACC N 120 Receiver Contract Reference EXT_MATCH_POP
TA Receiver Ref CP ACORD_TECHACC Y 130 Receiver Contract Reference EXT_MATCH_POP
TA Receiver Ref CP ACORD_TECHACC Y 130 TA Contract Period Start End EXT_MATCH_POP
TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Receiver Contract Section Reference EXT_MATCH_POP
TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Sender ID EXT_MATCH_POP
TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Contract Period Start End EXT_MATCH_POP
TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Sender Contract Section Reference EXACT_MATCH
TA Sender Ref CP HLR ACORD_TECHACC N 142 TA HighLevelReference EXT_MATCH_POP
TA Sender Ref CP HLR ACORD_TECHACC N 142 TA Contract Period Start End EXT_MATCH_POP
TA Sender Ref CP HLR ACORD_TECHACC N 142 TA Sender ID EXT_MATCH_POP
TA Sender Ref CP Risk Code ACORD_TECHACC N 144 TA Lloyds Risk Code EXT_MATCH_POP
TA Sender Ref CP Risk Code ACORD_TECHACC N 144 TA Sender ID EXT_MATCH_POP
TA Sender Ref CP Risk Code ACORD_TECHACC N 144 TA Contract Period Start End EXT_MATCH_POP
TA Sender Ref CP SCSR ACORD_TECHACC N 150 TA Sender ID EXT_MATCH_POP
TA Sender Ref CP SCSR ACORD_TECHACC N 150 TA Contract Period Start End EXT_MATCH_POP
TA Sender Ref CP SCSR ACORD_TECHACC N 150 TA Sender Contract Section Reference EXT_MATCH_POP
TA Sender Ref CP ACORD_TECHACC Y 160 TA Contract Period Start End EXT_MATCH_POP
TA Sender Ref CP ACORD_TECHACC Y 160 TA Sender ID EXT_MATCH_POP
Placing Receiver Ref CP RCSR ACORD_PLA N 500 Placing Section Level Sender Contract Section Reference EXT_MATCH_POP
Placing Receiver Ref CP RCSR ACORD_PLA N 500 Placing Section Level Receiver Contract Section Reference EXT_MATCH_POP
Placing Receiver Ref CP RCSR ACORD_PLA N 500 Receiver Contract Reference EXT_MATCH_POP
Placing Receiver Ref CP RCSR ACORD_PLA N 500 Placing Contract Period EXT_MATCH_POP
   
Receiver Contract Reference `jv-ins-re:Contract[jv-ins-re:InsurerReference[translate(., ‘PA_’,‘pa ‘) != ‘please advise’]]/jv-ins-re:InsurerReference
TA Sender Contract Section Reference `jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:CedentContractSectionReference[//jv-ins-re:TechAccount[attribute::Sender=‘cedent’]]
TA Receiver Contract Section Reference `jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:InsurerContractSectionReference[translate(., ‘PA_’,‘pa ‘) != ‘please advise’]
TA Sender ID `jv-ins-re:Cedent/jv-ins-re:Party/jv-ins-re:Id/attribute::Agency[//jv-ins-re:TechAccount[attribute::Sender=‘cedent’]]
TA Underwriting Year jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:UnderwritingYear
TA Contract Period Start End `jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:ContractPeriod/jv-ins-re:StartDateTime
TA Sender Contract Reference `jv-ins-re:Contract/jv-ins-re:CedentReference[//jv-ins-re:TechAccount[attribute::Sender=‘cedent’]]
TA Lloyds Risk Code jv-ins-re:Extension//*[local-name()='RiskCode']
TA HighLevelReference jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:HighLevelReference
Placing Section Level HLR //jv-ins-re:ContractSection[attribute::ContractReportingLevel='section_level']/jv-ins-re:HighLevelReference
Placing Section Level Sender Contract Section Reference `//jv-ins-re:ContractSection[attribute::ContractReportingLevel=‘section_level’ and //jv-ins-re:Placing[attribute::Sender=‘cedent’]]/jv-ins-re:CedentContractSectionReference
Placing Section Level Receiver Contract Section Reference `//jv-ins-re:ContractSection[attribute::ContractReportingLevel=‘section_level’]/jv-ins-re:InsurerContractSectionReference

Section References for ACORD 2016-10 #

Jv-Ins-Reinsurance Version 2016-10 TechAccount Referencing.

The presumption of referencing is that a first message would either link to an Insured Period via provided references or be manually located and linked. Subsequent messages should then reference automatically.

A ceded (Sender) contract may be mapped to multiple contracts and / or sections. The sender contract reference may be added to the section references on one or more contracts which may be on a parent section. This will be used to look up the Insured Period (presuming only one would identically match), otherwise manually linked on the first message.

eMessaging_Contract_ref.png

eMessaging_Contract_ref_msg.png

More Reference types can be added manually via Reference Data table 01212, if required.

A specific section would be located via the contract section references via Section Mappings or manually linked.

eMessaging_Section_Ref.png

eMessaging_Section_ref_msg.png

Validation can be performed that references match the section / section hierarchy to ensure that sender and receiver references are present and correct.

A second message (given receiver section reference was previously not present) would then reference to an Insured Period via Receiver Contract Reference and Section via Receiver Contract (Section) Reference.

eMessaging_ Receiver_Reference.png

Subsequent messages should match and reference via the PreviousMessageMapping rule although validation on contract section references can still be performed.

eMessaging_Previous_Ref.png

The Previous Message Mapping for a TA would be on Contract Dates, Receiver Contract Reference Populated and Receiver Contract (Section) Populated.

Example XPaths for Message Fields #

References extracted ignoring TBA etc. having no digit.

Receiver Contract Reference

jv-ins-re:Contract[jv-ins-re:InsurerReference[translate(., ‘[^0-9]’, ‘[^0-9]’) != translate(., ‘[^0-9]’, ‘’)]]/jv-ins-re:InsurerReference | jv-ins-re:Contract[jv-ins-re:ReinsurerReference[translate(., ‘[^0-9]’, ‘[^0-9]’) != translate(., ‘[^0-9]’, ‘’)]]/jv-ins-re:ReinsurerReference

TA Receiver Contract Section Reference

jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:ContractMarket/jv-ins-re:InsurerContractReference[translate(., ‘[^0-9]’, ‘[^0-9]’) != translate(., ‘[^0-9]’, ‘’)] | jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:ContractMarket/jv-ins-re:ReinsurerContractReference[translate(., ‘[^0-9]’, ‘[^0-9]’) != translate(., ‘[^0-9]’, ‘’)]

TA Contract Period Start End

jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:ContractPeriod/jv-ins-re:StartDateTime | // jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:ContractPeriod/jv-ins-re:StartDate | //jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:ContractPeriod/jv-ins-re:EndDateTime | //jv-ins-re:Subaccount/jv-ins-re:ContractSection/jv-ins-re:ContractPeriod/jv-ins-re:EndDate