LONDON MARKET STANDARD CLAIMS MESSAGE

IMPLEMENTATION GUIDE
CLASS FOR LLOYDS
MESSAGES TO BROKERS FROM LPC.

This document sets out the rules relating to messages detailing syndicate responses which will be
sent to brokers in respect of Lloyds claims processed on CLASS.

The document has been based on the ILU section of the London Market Standard Claims
Message Implementation Guide, as last amended 28/10/1993, sections 3.1 to 3.5 inclusive. The
remainder of the document remains unaffected by CLASS for Lloyds.

Please note that what follows is a suggestion for the treatment of Lloyds responses. If any of you
foresee problems with what is proposed or would like to suggest improvements then please
contact the author.

I am mindful of the age of the original message specification documentation. If anything below is
at variance with what you know to be the current situation, then you should assume that the
current situation prevails.

The following is a summary of the differences between Lloyds and ILU messages.

1. CLASS for Lloyds uses the following syndicate response codes:

AUT = authorised (same as ILU)
NAK = not acknowledged (same as ILU)
QUE = queried (no ILU equivalent, roughly equivalent to LIRMA FIL response
REJ = rejected (roughly equivalent to ILU PEN response

2. LCO responses.
The proposal is to treat LCO as a participating syndicate, but with a line of zero
per-cent. The company code for LCO will always be LCO1. For the purposes of the
pilot, LCO is always a follower, but it is possible that in the production version LCO will
sometimes stand-in for the lead.

3. Signing Details.
In the absence of any signing details being sent to CLASS from LPSO systems, messages
to brokers will not include details of claims signings.

4. The transaction Validation Response value sent for query responses will be spaces.

5. CLASS for Lloyds allows up to five lines of leader comment narrative (ILU allows up to
three).

6. The simultaneous reinstatement flag will always be N for Lloyds entries on CLASS
since this feature cannot apply given the absence of links between CLASS and LPSO
systems.

LIMCLM Implementation Guide (last amended 28/10/93) Page 1

 LONDON MARKET STANDARD CLAIMS MESSAGE

IMPLEMENTATION GUIDE

7. The following types of entry are not available under CLASS for Lloyds and therefore the
types of message which they generate for ILU will not be sent:
a. Conflict of Interest.
b. Lead Interim Advices.
c. Change of Leader.
d. C.P.A.
e. Salvage Association.
f. Automatic Deletions.
g. Objections.

As I have said above, any queries should be addressed to the author.

John Harrison (L.P.C.) 28th February 2000.

Phone: 01303 854689 (direct line) E-Mail: john.harrison@lpc.uk.com

LIMCLM Implementation Guide (last amended 28/10/93) Page 2

 LONDON MARKET STANDARD CLAIMS MESSAGE

IMPLEMENTATION GUIDE

MESSAGES FROM LPC TO BROKERS FOR LLOYDS CLAIMS

ADVICE OF SYNDICATE RESPONSES

This type of message will be sent to advise the broker

of the actions taken by syndicates in response to a
claim.

CHD Claim Header Details

Processing Indicator values are:

Transaction
Type..............................001/002/003/004
Transaction Type Qualifier........001
Transaction Subtype...............not used
Transaction Validation Response...003/004
or spaces

Transaction Type will be set to the value for the type

of transaction to which the response applies.

Transaction Validation Response will be set to '003'

unless any Insurer Response Codes contained in the RES
segments in the message are set to 'REJ' (Rejected).
Then the Transaction Validation Response will be set
to '004'.

The Number of Outstanding Responses will identify the

number of insurers who have not responded.

FTX Free Text

FTX segments will be sent if the Lead Comments

Indicator in the LDR segment is set to 'Y'.

Up to five FTX segments may be sent, with a Text

Subject Code of '010', to provide the Lloyds leader's
comments regarding the claim.

MKT Insuring Market Details

One MKT segment will be sent for each syndicate that

has been selected to note/agree the claim.

Where L.C.O. are involved in the agreement process,

there will also be an MKT segment for L.C.O. The

LIMCLM Implementation Guide (last amended 28/10/93) Page 3

 LONDON MARKET STANDARD CLAIMS MESSAGE

IMPLEMENTATION GUIDE
Company Code for L.C.O. will always be LCO1. The
L.C.O. share will always be zero.

ADVICE OF SYNDICATE RESPONSES (Continued)

RES Insuring Market Responses

One RES segment will be sent for each syndicate that

has been selected to authorise a settlement request,
immediately following the MKT to which it relates.
(This includes L.C.O.)

The RES segment will identify the company's response as

one of: AUT for Noted/Authorised
REJ for Rejected
NAK for No Acknowledgement
QUE for Queried

LDR Lloyds Leader Response Details

This segment will be sent immediately following the MKT

and RES segments for the Lloyds leader.

The Simultaneous Reinstatement Indicator will always be

set to N because there are no links between CLASS and
Lloyds own systems which allow the simultaneous
reinstatement function to be applied.

LIMCLM Implementation Guide (last amended 28/10/93) Page 4

 LONDON MARKET STANDARD CLAIMS MESSAGE

IMPLEMENTATION GUIDE

UPDATE OF SYNDICATE RESPONSES

This type of message will be sent to update 'NAK'

responses to QUE,'REJ' or 'AUT', QUE responses to
AUT or REJ, or 'REJ' responses to 'AUT'. It will
also reflect any changes which can be made by the
Lloyds leader whilst the authorisation procedure is in
progress, including;

- addition of, or updates to, the Lloyds leader's

comments
- addition of syndicates to the list to authorise
- deletion of syndicates from the list to authorise

The data content of the message will be the same as

described for SYNDICATE RESPONSES in 3.1 above. All
previous data will be repeated.

CHD Claim Header Details

Processing Indicator values are:

Transaction Type ................. 001/002/003/004

Transaction Type Qualifier........ 002
Transaction Subtype............... not used
Transaction Validation Response... 003 / 004
or spaces

RES Insuring Market Responses

The Leading Underwriter can delete a syndicate from the

list of syndicates required to authorise a settlement.
In this case the MKT segment will not include the
relevant syndicate when it comes back to the Broker
(note that a list of all syndicates who have
responded/need to respond will always be returned
within the MKT, with an updated RES segment for each
one to give their current states).

LIMCLM Implementation Guide (last amended 28/10/93) Page 5