Electronic Data Interchange (EDI) information

Providing continuity of heritage messaging during phase one of digital services

EDIs are standardised heritage electronic communication methods, used to exchange information and data in a structured format, streamlining transactions and reducing human intervention.  EDI messages will be supported as part of Velonetic’s cutover to phase one digital services with a target date of October 2024. 

25 March 2024

Velonetic has identified two frequently asked questions on EDIs and continuity after the cutover to phase one Digital Processing Services (DPS).

1.    How will Signing Number and Dates (SNDs) generated by heritage services (mainframe applications under the FERN services contract) persist into the Digital Processing Services (DPS) (cloud applications) when the cutover to phase one DPS starts?

Transactions that have an SND generated by heritage services (mainframe applications) will continue to be available with the same SND during DPS. This applies to both signed and settled transactions and ‘in-flight’ transactions that have an SND and were migrated during the cutover to phase one DPS, or used the DPS reachback functionality.

Lloyd’s corrections currently use the same SND of the original transaction for the contra/corrected transaction with a version number appended to the SND. This process will continue to operate after the cutover to phase one DPS, and will work with transactions that have a mainframe-generated SND. For example: a Lloyd’s correction processed once cutover to phase one DPS happens, that relates to a heritage transaction that had a mainframe-generated SND, will have the same SND as the original with a version 2 appended to the SND.

When cutover to phase one DPS starts, reversals and cancellations will be able to use the same SNDs generated by the heritage services (mainframe applications). 

2.    How will EDI message sequence numbers work when the cutover to phase one DPS starts?

On day 1 of the phase one DPS going live, the first EDI messages generated by DPS (cloud applications) will NOT continue the heritage services sequence number. All EDI messages sequence numbers for all customers will be reset to a ‘higher-than-all-current’ sequence. Velonetic will analyse all current sequence numbers and will pick a higher round number, which will become the new market-wide reset for all EDI sequence numbers. By way of a hypothetical example: if out of our thousands of individual current EDI sequence numbers we find the highest is 6,734, then Velonetic will pick 7,000 as the new reset for all EDIs for all customers). When the first phase one DPS EDI messages are delivered with the new reset base sequence number (7,000 in our hypothetical example), subsequent EDIs will have sequences that increase as per each message standard specification (7,001, 7,002, 7,003… in our hypothetical example). The actual market-wide reset base sequence number will be published one month before the cutover to phase one DPS starts. 

Following the updates provided at the Blueprint Two market event on 26 February, on 13 March 2024 Velonetic published:

Digital Processing Services Connection Guide, Draft v0.1, 23 February 2024

Signing and take down number and date (SND) – proposal, 13 March 2024

Please contact your Blueprint Two engagement partner if you have any queries.

Standardised EDIs

We are taking an iterative approach to the development of the technical specifications for standardised EDI messages so that they match current practice. The specifications are as accurate as we can make them at the time they are released, and while there may be some changes from time to time, we expect these to be minor. 

We encourage vendors and market firms to use the technical specifications available now to make any amendments required to be able to produce or consume EDI messages. Using the technical specifications available now will enable firms to prepare their systems for any testing they wish to conduct in Q2 2024 ahead of cutover to phase one digital services with a target date of October 2024. 

Please contact us if you find any issues or concerns so that we can respond and improve the accuracy of the specifications where needed. We will continue to iterate the technical specifications through internal testing, and this will continue as we go through testing with customers in Q2 2024.

Any update to EDI specifications will be notified as soon as possible. If vendors and/or users are using bespoke EDI messages, the impact of any change will vary depending on how the message has been altered.  We are working on a schedule for the release of bespoke EDI messages and will issue this in the coming weeks.

We strongly encourage you to refer to the Adoption Guide aimed specifically at operations, technology and change managers in market firms, setting out the activities that should be undertaken now to adopt phase one digital services at cutover.

1 March 2024

We have updated the table of technical specifications for EDI standardised messages to include USM V9, and an amended version of WSETT (Appendix 2.2 on page 31 has been removed based on market feedback that this was not needed and had the potential to cause confusion). This completes the suite of technical specifications for standardised EDI messages.

EDI message

Type / description

Participant

Release date

Changes made to the structure of the message

Technical specification (click to download)

ILUCSB V2

ILU

Carrier

Released

No

ILUCSB V2

ILUCSM

ILU

Carrier

Released

No

ILUCSM Companies Signing Message ILU

ILUCSM Companies Signing Message Appendices ILU

ILUCST

ILU

Carrier

Released

No

ILUCST

IPCCSM

ILU

Carrier

Released

No

IPCCSM

IPCCSM Appendicies

WSETT

LIRMA

Carrier

Released

No

WSETT

DSIGN

LIRMA

Carrier

Released

No

DSIGN

DSIGN Appendix

IPCDSM

LIRMA

Carrier

Released

No

IPCDSM

IPCBSM

ILU / LIRMA /LLOYD's

Broker

Released

No

IPCBSM

BSM

ILU / LIRMA /LLOYD's

Broker

Released

No

BSM

RESETT

ILU / LIRMA /LLOYD's

Broker

Released

No

RESETT

MCM

LLOYD'S

Carrier/Broker

Released

No

MCM

SCM

LLOYD'S

Carrier

Released

No

SCM

USM V9

LLOYD'S

Carrier

Released

No

USM V9

Message type

Description

Participant

Release date

Changes made to the structure of the message

Technical specification (click to download)

LIMCLM (response)

Broker Claim Submission

Broker

Released

No

LIMCLM (response)

Broker Implementation Guide

LIMCLM diagram

Broker

Released

No

LIMCLM Diagram

LIMCLMA (Overview)

Broker

Released

No

LIMCLMA (Overview)

LIMCLMB (Technical spec)

Broker

Released

No

LIMCLMB (Technical spec)

LIMCLMC (Completion Instructions) ILU

Broker

Released

No

LIMCLMC (Completion Instructions) ILU

LIMCLMC (Completion Instructions) LIRMA

Broker

Released

No

LIMCLMC (Completion Instructions) LIRMA

LIMCLMD (incl LIMRES)

Broker

Released

No

LIMCLMD (incl LIMRES)

LIMCLME (LIMRES error codes)

Broker

Released

No

LIMCLME (LIMRES error codes)

CLMILB

ILU Broker Claim Notification

Broker

Released

No

CLMILB ILU Broker

CLMLLB

Lloyd's Broker Claim Notification

Broker

Released

No

CLMLLB Lloyds Broker

CLMLRB

LIRMA Broker Claims Notification

Broker

Released

No

CLMLRB LIRMA Broker

CLMLRC

LIRMA Carrier Claim Notification

Carriers

Released

No

CLMLRC LIRMA Carrier

CLMILC

ILU Carrier Claim Notification

Carriers

Released

No

CLMILC ILU Carrier

EDI Message

Participant

Release date

Changes made to the structure of the message

Technical specification (click to download)

Appendix A - Data Glossary

Carriers/Brokers

Released

No

Appendix A - Data Glossary

Appendix B - Code sets

Carriers/Brokers

Released

No

Appendix B - Code sets

Appendix C - Segment Directory

Carriers/Brokers

Released

No

Appendix C - Segment Directory

Appendix D - Edifact level a character set

Carriers/Brokers

Released

No

Appendix D - Edifact level a character set

Appendix E1 - Error codes per data element

Carriers/Brokers

Released

No

Appendix E1 - Error codes per data element

Appendix E2 - Validation rules

Carriers/Brokers

Released

No

Appendix E2 - Validation rules

Appendix F1 - Message terms and definitions

Carriers/Brokers

Released

No

Appendix F1 - Message terms and definitions

Appendix F2 - LIMRIN

Brokers

Released

No

Appendix F2 - LIMRIN

Appendix F3 - LIMRIA

Carriers

Released

No

Appendix F3 - LIMRIA

Appendix F4 - LIMRID

Carriers/Brokers

Released

No

Appendix F4 - LIMRID

Appendix F5 - LLDUWR

Carriers

Released

No

Appendix F5 - LLDUWR

Appendix F6 - LIMRES

Carriers/Brokers

Released

No

Appendix F6 - LIMRES

Appendix F6 - LIMRIS

Carriers/Brokers

Released

No

Appendix F6 - LIMRIS

Appendix F7 - LIMRES

Carriers/Brokers

Released

No

Appendix F7 - LIMRES

Appendix G - Registration

Carriers/Brokers

Released

No

Appendix G - Registration

Appendix H - sla (LORS service summary)

Carriers/Brokers

Released

No

Appendix H - sla (LORS service summary)

LORS batch data information manual

Carriers/Brokers

Released

No

LORS batch data information manual

Supported customised EDIs

On 6 March 2024, Velonetic published 21 supported customised EDIs, also referred to as ‘bespoke EDIs’. While these are only used by a few of Velonetic’s customers, we are publishing them in one place to support our customers’ preparations for cutover, with a target date of October 2024.

If you have any queries, please contact your Blueprint Two engagement partner.
 

ACORD4ALL

On Friday 15 March 2024, Velonetic confirmed that the ACORD4ALL mappings are now available. The ability to receive the mappings will depend on whether a firm is an existing customer of ACORD4ALL and/or has signed a non-disclosure agreement (NDA) with Velonetic. If you are: 

  • An existing customer of ACORD4ALL and have a signed NDA with Velonetic, your Velonetic Customer Relationship Manager (CRM) and/or engagement partner will send the mappings to you direct.

  • An existing customer of ACORD4ALL, but do not have an NDA with Velonetic, please contact your Velonetic CRM and/or engagement partner, or email [email protected].

  • Not a customer of ACORD4ALL, please contact your Velonetic CRM and/or engagement partner to complete the NDA process.