DEL145 ECF2 Reports: Cross-Market
Incomplete Transactions (ECF004)
Functional Specification
Report Specification
Version: 1.1
Issue Date: 15-Feb-2010
Copyright Information
© Xchanging 2010
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in
any form or by any means, electronic, mechanical photocopying, recording, or otherwise, without the prior
permission of Xchanging.
Xchanging Confidential – do not copy or forward on. The document and the information it contains is
restricted and the circulation list is controlled by the author who should be identified in the document.
Note only signed hard copies and electronic masters of documents will be controlled. Any other copy may not be
current.
Trademark Information
Company, product, or brand names mentioned in this document, may be the trademarks of their owners.
Approved Distribution List
Name
Title
Gary Bass
ECF User Group Chairman
Pat Talbot
IUA
Steve Flood
Lloyd’s
Steve Spicer
Millers
Itay Wein
ECF2 Project Manager, Xchanging
Stuart Pembery
ECF2 Programme Manager
Functional Specification
DEL145 ECF 2 Reports: Workflow Report (ECF004) Functional Specification
Version 1.0, Final
Contents
1
Introduction ...................................................................................................................... 3
2
Functional Requirements ................................................................................................ 4
3
Functional Design ............................................................................................................ 5
4
5
3.1
Report Descriptions .................................................................................................. 6
3.2
Report Designs ......................................................................................................... 7
3.3
Data Descriptions ..................................................................................................... 7
Document Control .......................................................................................................... 12
4.1
Document Information ............................................................................................ 12
4.2
Issue List ................................................................................................................. 12
APPENDICES .................................................................................................................. 13
5.1
EL4.1 Incomplete Transactions for Company Carriers (DL6201) ......................... 15
5.2
EL4.2 Incomplete Transactions for Lloyd’s Carriers and XCS (DL6202) .............. 16
5.3
EL4.3 - Incomplete Transactions for Brokers on Lloyd’s Claims (DL5112) ............ 18
5.4
EL4.4 Incomplete Transactions for Brokers on Company Claims (DL5113) ......... 19
5.5
EL4.5 Incomplete Transactions (DL7528) - Management..................................... 21
5.6
Transaction Status Codes ...................................................................................... 22
5.7
Claim Response Codes .......................................................................................... 23
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 2 of 29
ECF2 Reporting – ECF004
Report Specification
Version 0.99, Draft
1
Introduction
This report specification is the detail pertaining to the report ECF004 which forms part of the
CLASS Workflow reporting suite. For details of this, please see the ECF2 Reporting – CLASS
Workflow Reporting Functional Specification (CLASSWorkflow.doc).
It is a Claims Data Warehouse version of the reports currently produced from the mainframe
called “ECF004” and at this stage will duplicates – where possible - those reports.
The intended user base of the report(s) is all carrier and broker users of Lloyd’s CLASS, and
those at market association level needing statistics on throughputs. It does not cover
commercial arrangements or specific support/service levels which will be defined in a
separate Services Definition for ECF2 Reporting.
For full details of the data elements mentioned in this specification, please consult the
separate Data Definitions document (CDWDataDefinitions.xls) and the Claims Data
Warehouse Design (CDWDesign.doc).
The purpose of this document is to define the product offered by Xchanging to provide both
Lloyd’s and company market participants with details of incomplete ECF transactions. The
information to be provided will enable brokers and carriers to review such transactions and, in
particular, monitor ‘slow-moving claims’. Detailed transaction information will be provided in
order to enable the parties involved to identify these transactions and take the appropriate
form of action.
The reports and services described in this document will be supplied to Lloyd’s managing
agents, companies, brokers and Xchanging Claims Services. For a full list of reports to be
produced and the recipients of each please see section 3.1. The reports will provide details of
all incomplete ECF transactions. (“Incomplete” claims for Lloyd’s are transactions that have a
systems status other than ‘40’. “Incomplete” ILU and LIRMA Claims are transactions that have
not yet been fully authorised (signed).)
However, the reports will only include details of transactions that are of relevance to the report
recipients (i.e. where the party identified is an agreement party (lead, second agreement party
or XCS)). The transactions will be sequenced according to the length of time since the last
activity took place. High-level transaction totals will be provided to the market associations.
These reports, when coupled with the data provided within reports ECF001 / ECF002
(completed transactions), will provide brokers and claim agreement parties with details of all
ECF transactions that they are involved in.
The reports will be produced on a weekly basis.
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 3 of 29
ECF2 Reporting – ECF004
Report Specification
Version 0.99, Draft
2
Functional Requirements
There is a requirement to provide Lloyd’s market participants with information on the
outstanding action required on claim transactions by carriers using ECF. The information to
be provided will enable Lloyd’s, LIIBA and the Market Reform Office (MRO) to measure and
monitor the level of ECF outstanding activity within the Market and will enable individual
brokers and managing agents to manage their implementation and use of the system.
The reports and services described in this document are to be supplied to Lloyd’s, LIIBA, the
Market Reform Office, Lloyd’s Managing Agents and Lloyd’s brokers.
The following are transactions which will be considered for inclusion or exclusion in ECF004.
Whether they are included or not will depend on the trigger rules, defined in section 3.1.

All incomplete Lloyd’s, ILU and LIRMA claim transactions that are processed via ECF

Both new claims and new transactions on existing claims

Both loss advices and settlement requests. This includes initial advices, subsequent
advices, initial settlements and subsequent settlements.

Claim transactions ‘in transition ’

ILU and LIRMA claims that have been ‘purged’ (broker reports only)
The following are transactions which will not be considered for inclusion/exclusion:

Claims that have been completed (fully authorised by all agreement parties)

Claims that have not been processed via ECF

Transactions that have been raised by brokers and subsequently deleted or cancelled
by them.

ILU claim objection signings and ILU CPA claims.

LIRMA claim transactions that have been cancelled by the LIRMA Leader.
Non-functional requirements are:
1. Security of access is determined from CLASS security by claim transaction
transactions (via SECURITY BROKER CODE on the transaction, and COY CODE on
the market, respectively).
2. Reporting is via the Business Objects on-line reporting system (InfoView) and subject
to a report production from request time of 10 minutes for reports of 20,000 rows.
3. Reports can be produced as Excel spreadsheets (as Excel 2003 .xls, and if rows
exceed 65,536 then the data will continue on a second or subsequent tab), or csv files
or pdf. Reports can be scheduled to go into the user’s Business Objects “Inbox”.
Out-of-Scope are:
1. Separate “data extract” capabilities which may be offered by Xchanging (TBA).
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 4 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
3
Functional Design
The following diagram and table show the separate detailed weekly reports which will be delivered. The reports will provide the following:

Details of Lloyd’s, ILU and LIRMA ECF transactions that are incomplete - both claims advice and settlement requests.

Outstanding claim amount and paid to-date figures will be provided in detailed transaction reports. All figures quoted will be in sterling. In
the case of claims that are to be settled in more than one currency, a single combined amount will be provided for the transaction in
convertible sterling according to a reporting conversion rate.

The report will show the current status of each transaction along with the date on which the transaction was last updated. The number of
working days since the last action took place on the transaction on CLASS will be shown. This will enable recipients of the reports to
obtain details of transactions that have been inactive for a set number of days – i.e. report recipients will be able to set their own
parameters to review ‘slow-moving’ claims, should they wish to do so.

The reports will only provide details of transactions that are of relevance to the parties – i.e. where either the broker or the carrier may
need to take some form of action in order to progress or complete the transaction or its status may be of interest to them.

The report will sequence the transactions according to the amount of time since the last activity took place on the transaction – i.e. the
transaction which has been ‘inactive’ for the longest period of time will appear as the first item on the report. The ‘age’ will be measured
from the date of the last recorded activity (last updated timestamp) on the transaction in question.
© Xchanging 2010 – Confidential
Market
Carrier
Broker
Log on
Log on
Log on
Report List
Report List
Report List
Select
Period
Select
Period
Select
Period
Select
Period
Select
Period
E4.4 Incomplete
Statistics
E1.2a Company
Carrier
Incompletes
E4.2 Lloyd’s
Carrier and XCS
Incompletes
E4.3 Company
carrier
Incompletes
E4.4 Lloyd’s
carrier
incompletes
DL7528
DL6201
DL6202
DL5113
DL5112
Document uncontrolled once printed
Page 5 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
3.1
Report Descriptions
ID
Report
Description
Purpose
Usage
Parameters
Frequency
E4.1
Incomplete
Transactions for
Company Carriers
(DL6201)
Incomplete Transactions for Company
(ILU/LIRMA) Carriers
Provides Company carriers with
action list of claim transactions to
adjust
Available to all
company carriers
As-at close of
business on a
given day
10 minutes on-line
E4.2
Incomplete
Transactions for
Lloyd’s Carriers and
XCS (DL6202)
Incomplete Transactions for Lloyd’s Carriers
and XCS
Provides Lloyd’s carriers with action
list of claim transactions to adjust
Available to all
Lloyd’s carriers
Variant for XCS
where LCO1 appears
as syndicate but
excludes XCS1
As-at close of
business on a
given day
10 minutes on-line
E4.3
Incomplete
Transactions for
Brokers on Lloyd’s
Claims (DL5112)
Incomplete Transactions for Lloyd’s Brokers
Provides brokers with action list of
Lloyd’s claim transactions to adjust
Available to all
brokers
As-at close of
business on a
given day
10 minutes on-line
E4.4
Incomplete
Transactions for
Brokers on Company
Claims (DL5113)
Incomplete Transactions for Company
(ILU/LIRMA) Brokers
Provides brokers with action list of
Company market claim transactions
to adjust
Available to all
brokers
As-at close of
business on a
given day
10 minutes on-line
E4.5
Incomplete
Transactions
(DL7528) Management
Incomplete Transactions Summary
Provides market management with
statistics on outstanding work
Provided to
management weekly
Weekly
10 minutes on-line
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 6 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
3.2
Report Designs
3.2.1
Data Descriptions
Transaction Information Report Data Fields
Field Name
Format
6201
6202
5112
5113
Definition
Carrier Code
Lloyd’s = Alpha/Numeric
(4)
LIRMA = Alpha/Numeric
(5)
ILU = Numeric (6)
Y
Y
Y
Y
The syndicate number or company code number of the carrier. (The syndicate number
will still be shown in cases where XCS are acting in a delegated lead role.)
Carrier Name
Alpha (20)
Y
Y
Y
Y
The (abbreviated) name of the carrier.
Carrier Reference
Alpha/Numeric (15)
Y
Y
Y
Y
The underwriting stamp reference that the syndicate or company allocated to the
contract / contract section
Claims Adjuster Name
Alpha (30)
Y
Y
Y
Y
The name of the claims adjuster involved in the current transaction (when known).
Carrier Role
Alpha (1)
Y
Y
Y
Y
An indicator that identifies whether the carrier is acting as the Leader or a claims
agreement party on the contract. The codes are as follows:
L = Bureau Lead
F = Second Lead (Lloyd’s claims)
A = Agreement Party (ILU and LIRMA claims)
Transaction Status
Alpha (30)
Y
Y
Y
Y
The status of the transaction at the end of the reporting period (i.e. when the data is
extracted). (See Appendix 5.7 for codes.)
Transaction Status Code
Numeric (2)
Y
Y
Y
Y
The current systems status code of the transaction – note this is the latest transaction
status so will not relate to the as-at date of the report (See Appendix 5.6 for codes.)
Carrier’s Response Code
Alpha (3)
Y
Y
Y
Y
A code that indicates how the carrier has responded to the transaction. The values that
will be displayed are as follows:
Lloyd’s – ‘AUT’ (Action/Agree), ‘QUE’ (Queried) or ‘‘NAK’ (no response has yet
been applied)
ILU – ‘PEND’ or ‘ACCEPT’
LIRMA – ‘INF’, ‘FIL’, ‘ACC’, ‘DIS’’, ‘CAA’, ‘YES’ or ‘NO’
Further details of carrier response codes can be found in Appendix 5.7.
Leader’s Response Code
Alpha (3)
Y
Action Required by
Carrier?
Alpha (1)
Y
© Xchanging 2010 – Confidential
Y
Y
Y
A code that indicates how the Bureau Leader has responded to the transaction. The
values that will be displayed are shown above.
Y
Y
This field will indicate whether the carrier needs to take any form of action on the
transaction. (Y/N)
Document uncontrolled once printed
Page 7 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
Field Name
Format
6201
6202
5112
5113
Definition
Days Since Last Action
Numeric (3)
Y
Y
Y
Y
The number of calendar days since the last action took place to the as at date for the
transaction on CLASS.
Created Date
YYYYMMDD
Y
Y
Y
Y
The day upon which the broker created the transaction on ECF/CLASS – i.e. the date
when the transaction was first added to the Market Repository / CLASS. (If the broker
has either updated or deleted and replaced the transaction then the date shown will be
the date when the original transaction was created.)
Last Updated Date
YYYYMMDD
Y
Y
Y
Y
The date when the last activity took place on the transaction.
Advice / Settlement
Indicator
Alpha (1)
Y
Y
Y
Y
An indicator that identifies whether the transaction is for advice purposes only or whether
it is a claim settlement request.
A = Advice
S = Settlement
100% Outstanding Claim
Amount (in GBP)
9(13).99
Y
Y
Y
Y
The (100%) outstanding claim amount figure expressed in sterling. A single combined
amount will be provided in convertible sterling for transactions that are to be settled in
more than one currency. (The current rates of exchange held on Xchanging’s on-line
currency tables system will be used for these purposes.)
100% Amount Paid This
Time (in GBP)
9(13).99
Y
Y
Y
Y
The (100%) claim amount that is being settled on this transaction expressed in sterling.
A single combined amount will be provided in convertible sterling for transactions that
are to be settled in more than one currency. (The current rates of exchange held on
Xchanging’s on-line currency tables system will be used for these purposes.)
Slip Leader Name
Alpha (20)
Y
Y
Y
Y
The name of the Overall Slip Leader. (This field may sometimes be blank.)
Slip Leader Code
Lloyd’s = Numeric (4)
LIRMA = Alpha/Numeric
(5)
ILU = Numeric (6)
Y
Y
Y
Y
The syndicate number / underwriting stamp code of the overall Slip Leader. (This field
may sometimes be blank.)
Bureau Leader Name
Alpha (20)
Y
Y
Y
Y
The name of the Bureau Leader.
Bureau Leader Code
As above.
Y
Y
Y
Y
The syndicate number / underwriting stamp code of the Bureau Leader on the claim.
Other Agreement Party
Name
Alpha (20)
Y
Y
Y
Y
The name of any other claim agreement party on the transaction concerned. If there is
more than one party then ‘VARIOUS’ will be shown in this field.
Other Agreement Party
Code
Numeric (4)
Y
Y
Y
Y
The syndicate number or underwriting stamp code of any other claim agreement party on
the transaction concerned. If there is more than one party then ‘VARIOUS’ will be shown
in this field.
Broker Code
Alpha/Numeric (4)
Y
Y
Y
Y
The broker code number under which the ECF transaction is being processed. (The
broker code used within the Transaction Reference will be used for these purposes.)
Broker Name
Alpha (20)
Y
Y
Y
Y
The name of the broker
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 8 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
Field Name
Format
6201
6202
5112
5113
Definition
Broker Contact Name
Alpha (30)
Y
Y
Y
Y
The name of the broker contact who created the transaction on ECF
Transition Indicator
Alpha (1)
Y
Y
Y
Y
An indicator that identifies whether the transaction relates to a claim that is ‘in transition’
from paper to electronic processing.
T = The transaction is a first advice on a claim ‘in transition’
Y = ECF Claim
Unique Market Reference
Alpha/Numeric (17)
Y
Y
Y
Y
The Unique Market Reference allocated to the contract.
Unique Claim Reference
Alpha/Numeric (17)
Y
Y
Y
Y
The Unique Claim Reference allocate to the claim
Transaction Reference
Alpha/Numeric (17)
Y
Y
Y
Y
The Transaction Reference for the item
Sequence Number
Numeric (2)
Y
Y
Y
Y
The sequence number allocated to the transaction
COR of Previous
Transaction
Alpha/Numeric (12)
Y
The Claims Office Reference that Xchanging allocated to the previous claim movement /
settlement request. To be supplied for Lloyd’s transactions only. (‘VARIOUS’ will be
shown in this field when there are multiple CORs.)
Original Premium Signing
Number
Lloyd’s = Numeric (11)
LIRMA = Numeric (13)
ILU = Alpha/Numeric (15)
Y
Y
Y
Y
The bureau signing reference that was allocated to the original premium entry for the
contract. (Only the first signing reference will be shown where the claim is being settled
in multiple currencies.)
Insured / Reinsured Name
Alpha (50)
Y
Y
Y
Y
The name of the Insured/Reinsured party
Loss Name
Alpha (20)
Y
Y
Y
Y
The details completed by the broker in the Loss Name field.
Date of Loss
YYYYMMDD
Y
Y
Y
Y
The loss date entered by the broker. (This field may sometimes be blank.)
Risk Code
Alpha/Numeric (2)
Y
The risk code applicable to the claim transaction. Further information is provided within
the Service Proposal ECF002. (This field will be blank if the transaction is an unclosed
advice.)
Class of Business Code
Alpha/Numeric (2)
Risk Description/
Alpha (30)
Class of Business
Description
Alpha (30)
Y
Claim Reference 1
Alpha/Numeric (15)
Y
Y
Y
Y
Narrative entered by the carrier to identify or filter claim transactions within their own
offices (Lloyd’s and LIRMA carriers only)
Claim Reference 2
Alpha/Numeric (15)
Y
Y
Y
Y
Narrative entered by the carrier to identify or filter claim transactions within their own
offices (Lloyd’s and LIRMA carriers only)
© Xchanging 2010 – Confidential
Y
Y
Y
Y
Y
The business category code applicable to the claim transaction. Further information is
provided within the Service Proposals ECF001 (This field will be blank if the transaction
is an unclosed advice. The field will also be blank until a response has been made.)
Y
Y
The risk code description (see above)
The class of business description (see above)
Document uncontrolled once printed
Page 9 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
Field Name
Format
Year of Account
YYYY
OS Qual - Outstanding
Qualifier (Closed/TBA flag)
Alpha (1)
6201
6202
5112
Y
Y
Y
Y
5113
Definition
Y
The Year of Account for the transaction - i.e. the year in which the contract incepted.
(This field will only be populated on Lloyd’s transactions.)
Y
Outstanding Qualifier Code. The broker may select a qualifier to more fully define the
outstanding position of the claim. If present, the qualifier shows whether a recovery is
expected (R), claim notified awaiting report (M), circumstance of loss notified (L),
awaiting advice from cedant (A), precautionary (P), subrogation (S), erroneous entry not
to be reopened (X). Value may be a space. In addition Codes N,T & C can be reported
for this field. The ‘N’ will no longer be shown in the file. T stands for TBA and C stands
for closed.
Note, the outstanding qualifier is held at currency level so if a transaction has multiple
currencies on it, the transaction (and indeed claim) needs to be reported as closed only if
all the currency qualifiers on the transaction are set to closed (X or C – to be chacked)
Seg - Segmentation
Alpha (1)
Y
Y
Y
Y
Segmentation Indicator set by the leader identifying the type of claim for processing (e.g.
Complex) for old Lloyd’s Claim Scheme and the CTP Triage Flag for the type of claim
under CTP (values to be defined). Values could be Complex, Standard , Not Specified or
blank for the 2006 Lloyd’s scheme, and CTP Standard, CTP mid Tranch and CTP
Complex for the 2010 Lloyd’s scheme
Previous transaction
incomplete suspend Ind
Alpha (1)
Y
Y
Y
Y
This is the “NAK BLACK” problem whereby a transaction cannot be completed because
a previous transaction is incomplete; for example, in cases for Lloyd’s it is possible for
the Lead to authorise the transaction but XCS are unable to act on the transaction –
hence XCS show an “NAK” response but in the ECF application, it is black rather than
blue and is inactionable. Lloyd’s only.
Header Information Fields
Field Name
Format
Definition
Report Number
Alpha/Numeric (6)
The ‘DL’ number allocated to the report.
Report Name & Period
Alpha/Numeric (50)
The report name and the period covered by the report
Extract Date
DD/MM/YYYY
Date of run (to identify when the extract program was run).
Report Date and Time
DD/MM/YYYY + HH:MM
The time and date when the report is actually produced.
Transaction Summary Report (DL7528)
Field Name
Format
Definition
Job Name
Alpha/Numeric (7)
Used for report distribution purposes
Market Sector
Alpha (40)
Specifies whether Company or Lloyd's Transactions
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 10 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
Field Name
Format
Definition
0 to 5 DAYS
Numeric (5)
The total number of incomplete transactions where action took place up to 5 days ago.
6 to 30 DAYS
Numeric (5)
The total number of incomplete transactions where action took place between 6 and 30 days ago.
31 to 90 DAYS
Numeric (5)
The total number of incomplete transactions where action took place between 31 and 90 days ago.
Over 90 DAYS
Numeric (5)
The total number of incomplete transactions where action took over 90 days ago.
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 11 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
4
Document Control
4.1
Document Information
Prepared by:
Peter Taylor
Project Manager:
Itay Wein
Programme Manager:
Stuart Pembery
Version
4.2
Date
Author
Description
Prior
23-Jan-09
John Semple
Published version (29 January 2009 v2.0 of Report )
0.96
12 Jan 10
Peter Taylor
Version for initial Implementation Team review
0.97
15 Jan 10
Peter Taylor
Further version for initial Implementation Team review
0.99
31 Jan 10
Peter Taylor
Version following initial user review
1.0
8 Feb 10
Peter Taylor
Version following second user review
Issue List
Issue
Owner
Priority
Comments
Status
Consistency of new “Swimlane” system with
the various status-controlled assignments of
ownership in the existing ECF004
Peter Taylor
1
This is part of a bigger issue which is the consistency of reporting
“ownership of action” between ECF2 Awaiting Action list (governed by
Claim Workflow Triggers), the existing CLASS Awaiting Action List, the
ECF001/2/4 reports, and the FPD reporting of claim transactions.
Open
Assess use of the RIPS indicators and
determine if this can be used in assisting
reporting
Charles Lee
2
Not sure as to use in each of the different markets
Open
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 12 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
5
APPENDICES
Note: The UCR, UMR, TR fields will show on all reports on the left hand side of the report. The below examples are for illustration.
The example transactions used in the sample reports are:
BROKER
SLIP LEADER
BUREAU LEADER
AGREEMENT PARTIES
TRANSACTION STATUS
Report 1 - Lloyd’s Transaction Examples for Markel International
Lloyd's Example 1
WILLIS
Markel Intl. (3000)
Markel Intl. (3000)
Catlin (2020)
Partially Authorised (by Markel)
Lloyd's Example 2
AON
Chaucer (4000)
Chaucer (4000)
Markel Intl. (3000)
Lloyd's Example 3
MARSH
QBE (D1806)
Markel Intl. (3000)
Hiscox (1165)
Queried (by Markel)
Lloyd's Example 4
WILLIS
Global Aerospace (401204)
Markel Intl.(3000)
Catlin (2020)
Awaiting Action (by Leader)
Lloyd's Example 5
AON
Catlin (2020)
Catlin (2020)
Markel Intl. (3000)
Partially Authorised (by Chaucer)
Authorised but Incomplete
Report 2 - Lloyd’s Transaction Examples for Willis
Lloyd's Example 1
WILLIS
Markel Intl. (3000)
Markel Intl. (3000)
Catlin (2020)
Lloyd's Example 2
WILLIS
Chaucer (4000)
Chaucer (4000)
Markel Intl. (3000)
Partially Authorised (by Markel)
Lloyd's Example 3
WILLIS
QBE (D1806)
Markel Intl. (3000)
Hiscox (1165)
Queried (by Markel)
Lloyd's Example 4
WILLIS
Global Aerospace (401204)
Markel Intl.(3000)
Catlin (2020)
Awaiting Action (by Leader)
Lloyd's Example 5
WILLIS
Catlin (2020)
Catlin (2020)
Markel Intl. (3000)
Partially Authorised (by Chaucer)
Authorised but Incomplete
Report 3 - Company Transaction Examples for Swiss Re
ILU Example 1
ILU Example 2
WILLIS
Catlin (Synd. 2020)
Swiss Re (377201)
AIG (400501)
Queried (by Swiss Re)
AON
GAUM (401204)
GAUM (401204)
Swiss Re (377201)
Partially Authorised (by GAUM )
LIRMA Example 1
MARSH
Hiscox (Synd. 1165)
QBE (D1806)
Swiss Re (E6200)
Partially Authorised (by QBE)
LIRMA Example 1
MARSH
(As above)
(As above)
Axis (A9208)
(As above)
LIRMA Example 1
MARSH
(As above)
(As above)
Zurich (Z4904)
(As above)
LIRMA Example 2
AON
Swiss Re (E6200)
Swiss Re (E6200)
Axis (A9208)
In Error
Catlin (Synd. 2020)
Swiss Re (377201)
AIG (400501)
Queried (by Swiss Re)
Report 4 - Company Transaction Examples for Aon
ILU Example 1
AON
ILU Example 2
AON
GAUM (401204)
GAUM (401204)
Swiss Re (377201)
Partially Authorised (by GAUM )
LIRMA Example 1
AON
Hiscox (Synd. 1165)
QBE (D1806)
Swiss Re (E6200)
Partially Authorised (by QBE)
LIRMA Example 1
AON
(As above)
(As above)
Axis (A9208)
(As above)
LIRMA Example 1
AON
(As above)
(As above)
Zurich (Z4904)
(As above)
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 13 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
LIRMA Example 2
AON
© Xchanging 2010 – Confidential
Swiss Re (E6200)
Swiss Re (E6200)
Axis (A9208)
Document uncontrolled once printed
In Error
Page 14 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
5.1
EL4.1 Incomplete Transactions for Company Carriers (DL6201)
This report will be sent to all companies. This illustration shows data that would be sent to Swiss Re (company codes 37701 and E6200)
WEEKLY INCOMPLETE TR FOR COMPANIES
20080601
2
20080602 13:09
E4.1 (DL6201)
CARRIER
CODE
CARRIER
NAME
CARRIER
REFERENCE
CLAIMS
ADJUSTER NAME
CARRIER
ROLE
TRANSACTION
STATUS
TRANSACTION
STATUS CODE
CARRIER
RESPONSE CODE
LEADERSRESPON
SE CODE
ACTION REQUIRED
BY CARRIER?
DAYS SINCE
LAST ACTION
ILU Example1
377201
SWISS RE
ZURICH
REF0001
JAMES
L
PENDED
12
PEND
PEND
N
12
ILU Example 2
377201
SWISS RE
ZURICH
REF0002
--
A
PARTIALLY
AUTHORISED
15
--
ACCEPT
Y
6
LIRMA Example 1
E6200
SWISS RE
ITALY
REF0004
--
A
CIRCULATED
20
--
YES
Y
4
LIRMA Example 2
E6200
SWISS RE
ITALY
REF0033
--
L
IN ERROR
01
--
--
N
3
CREATED
DATE
LAST
UPDATED
DATE
ADVICE /
SETTLMNTI
NDICATOR
100% OUTSTDG.
CLAIM AMOUNT
(IN GBP)
100% AMOUNT
PAID THIS
TIME (IN GBP)
SLIP LEADER
NAME
SLIP
LEADER
CODE
BUREAU
LEADER NAME
BUREAU
LEADER
CODE
OTHER
AGREEMENT
PARTY NAME
OTHER
AGREEMENT
PARTY CODE
BROKER
CODE
BROKER
NAME
BROKER
CONTACT
NAME
TRANSITION
INDICATOR
20080112
20080513
S
50,000
20,000
CATLIN
2020
SWISS RE
ZURICH
377201
AIG
400501
0576
WILLIS
STEVE
Y
20080128
20080521
S
200,000
130,000
GLOBAL
AEROSPACE
401204
GLOBAL
AEROSPACE
401204
--
--
0823
AON
BARRY
Y
20080405
20080523
S
350,000
210,000
HISCOX
1165
QBE
D1806
VARIOUS
VARIOUS
0509
MARSH
TREVOR
Y
20080527
--
A
1,200,000
500,000
SWISS RE
ITALY
E6200
SWISS RE ITALY
E6200
AXIS
A9208
0823
AON
BARRY
T
UNIQUE
MARKET
REFERENCE
UNIQUE
CLAIM
REFERENCE
TRANSACTION
REFERENCE
SEQUENC
E NUMBER
ORIGINAL PREMIUM
SIGNING NUMBER
INSURED /
REINSURED
NAME
LOSS NAME
DATE OF
LOSS
CLASS OF
BUSINESS
CODE
CLASS OF BUSINESS
DESCRIPTION
CLAIM
REF 1
CLAIM REF 2
B0576001122
B05760007
B05761011
01
PMC07 114466
23/05/07
ABC SHIPPING
FLORIDA STORM
LOSSES
20071201
MC
MARINE CARGO
--
--
B0823008899
B08239998
B08231077
02
PMA07 112233
03/04/07
XYZ AIRLINES
MEXICO CRASH
20071214
AH
AVIATION HULL
--
--
B0509007711
B05095556
B05091865
01
07100988888
US ATTORNEYS
INC
CHICAGO BANK
CLAIM
20080105
NM
NON-MARINE DIRECT
INS.
D&O
CLAIMS
AREA 90
B0823007766
B08236677
B08233211
01
07050766666
NEW YORK
CRUISES
OCEAN CRUISER
GROUNDING
20080114
MH
MARINE HULL
MARINE
CLAIMS
CRUISERS
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 15 of 29
OS
QUAL
SEG
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
5.2
EL4.2 Incomplete Transactions for Lloyd’s Carriers and XCS (DL6202)
This report will be sent to all Lloyd’s carriers and XCS. This illustration shows data that would be sent to Markel International (syndicate 3000):
HDR
WEEKLY INCOMPLETE TR DETAILS FOR LLOYD’S CARRIERS
DL6202
CARRIE
R CODE
CARRIER
NAME
CARRIER
REFERENCE
CLAIMS
ADJUSTER
NAME
Lloyd's Example 1
3000
MARKEL INTL
REF0001
REGAN
Lloyd's Example 2
3000
MARKEL INTL
REF0002
Lloyd's Example 3
3000
MARKEL INTL
REF0004
Lloyd's Example 4
3000
MARKEL INTL
REF0005
Lloyd's Example 5
3000
MARKEL INTL
REF0009
20080601
20080602 13:09
CARRIER
ROLE
TRANSACTION STATUS
TRANS
STATUS
CODE
L
PARTIALLY AUTHORISED
F
PARTIALLY AUTHORISED
L
L
F
AUTHORISED
REGAN
DAVID
CARRIER
RESPONSE
CODE
ACTION
REQUIRED BY
CARRIER?
DAYS SINCE
LAST
ACTION
CREATED
DATE
LAST UPDATED
DATE
14
AUT
N
12
20080112
20080513
14
NAK
Y
6
20080128
20080521
QUERIED
10
QUE
N
4
20080405
20080523
AWAITING ACTION
10
NAK
Y
2
20080316
20080528
32
AUT
N
2
20080323
20080528
ADVICE/
SETTNT
IND
100% OUTSTDG.
CLAIM AMOUNT
(IN GBP)
100% AMOUNT
PAID THIS
TIME (IN GBP)
SLIP LEADER
NAME
SLIP
LEADER
CODE
BUREAU
LEADER NAME
BUREAU
LEADER
CODE
OTHER
AGREEMENT
PARTY NAME
OTHER
AGREEMENT
PARTY
CODE
BROKER
CODE
BROKER
NAME
BROKER
CONTACT
NAME
TRANSITION
INDICATOR
UNIQUE
MARKET
REFERENCE
UNIQUE
CLAIM
REFERENCE
S
50,000
20,000
MARKEL INTL
3000
MARKEL INTL
3000
CATLIN
2020
0576
WILLIS
STEVE
Y
B0576001122
B05760007
S
200,000
130,000
CHAUCER
4000
CHAUCER
4000
MARKEL INTL
3000
0823
AON
BARRY
Y
B0823008899
B08239998
S
350,000
210,000
QBE
D1806
MARKEL INTL
3000
HISCOX
1165
0509
MARSH
TREVOR
Y
B0509007711
B05095556
A
1,200,000
500,000
GLOBAL
AEROSPACE
401204
MARKEL INTL
3000
CATLIN
2020
0576
WILLIS
STEVE
T
B0576003344
B05763244
S
45,000
25,000
CATLIN
2020
CATLIN
2020
MARKEL INTL
3000
0823
AON
BARRY
Y
B0823007676
B08239907
TRANSACTION
REFERENCE
SEQUENCE
NUMBER
COR OF
PREVIOUS
TRANSACTION
ORIGINAL
PREMIUM
SIGNING NUMBER
INSURED /
REINSURED
NAME
LOSS NAME
DATE OF LOSS
RISK
CODE
RISK
DESCRIPTION
CLAIM
REFERENCE 1
CLAIM
REFERENCE 2
YEAR OF
ACCOUNT
B05761011
01
M0712666662
99999 22/12/06
ABC
SHIPPING
FLORIDA STORM
LOSSES
20071201
V
CARGO ALL
RISKS
MARINE CLAIMS
AAA TEAM
2006
B08231077
02
A288888201207
88888 08/09/07
XYZ
AIRLINES
MEXICO CRASH
20071214
H2
AIRLINE HULL
AVN. CLAIMS
SECTION 2A
2007
B05091865
01
N20333210208
77777 03/01/08
US
ATTORNEYS
INC
CHICAGO BANK CLAIM
20080105
DO
D&O LIABILITY
D&O CLAIMS
AREA 90
2008
B05761534
02
M0801555552
66666 17/10/07
NEW YORK
CRUISES
OCEAN CRUISER
GROUNDING
20080114
T
VESSELS
MARINE CLAIMS
CRUISERS
2007
B08231104
01
N20444040308
22222 12/01/08
UK INS.
COMPANY
SPRING FLOODS
20080117
XU
NM PROPERTY
XOL
REINS. CLAIMS
XOL TEAM
2008
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 16 of 29
OS
QUAL
SEG
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 17 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
EL4.3 - Incomplete Transactions for Brokers on Lloyd’s Claims (DL5112)
5.3
This report will be sent to all brokers on Lloyd’s claims. This illustration shows data that would be sent to Willis (broker code 0576).
HDR
WEEKLY INCOMPLETE TRS FOR BROKERS – LLOYD’S
DL5112
BROKER
CODE
BROKER
NAME
BROKER CONTACT
NAME
TRANSACTION
STATUS
TRANSACTION
STATUS CODE
ACTION REQUIRED
BY BROKER?
DAYS SINCE LAST
ACTION
CREATED DATE
LAST UPDATED
DATE
0576
WILLIS
STEVE
PARTIALLY AUTHORISED
14
N
12
20080112
20080513
Lloyd's Example 1
20080601
20080602 13:09
Lloyd's Example 2
0576
WILLIS
ROB
PARTIALLY AUTHORISED
14
N
6
20080128
20080521
Lloyd's Example 3
0576
WILLIS
ROB
QUERIED
10
Y
4
20080405
20080523
Lloyd's Example 4
0576
WILLIS
STEVE
AWAITING ACTION
10
N
2
20080316
20080528
ROB
AUTHORISED
32
N
2
20080323
20080528
Lloyd's Example 5
0576
WILLIS
Queried
By/Next Action
E ACTION
CARRIER
CODE
CARRIER
ROLE
CARRIER
REFERENCE
ADVICE /
SETTLEME
NT
INDICATOR
100% OUTSTDG.
CLAIM AMOUNT
(IN GBP)
100% AMOUNT
PAID THIS TIME
(IN GBP)
SLIP LEADER
NAME
SLIP LEADER
CODE
BUREAU
LEADER NAME
BUREAU
LEADER
CODE
OTHER
AGREEMENT
PARTY NAME
OTHER
AGREEMENT
PARTY CODE
TRANSITION
INDICATOR
CATLIN
2020
F
REF0001
S
50,000
20,000
MARKEL INTL
3000
MARKEL INTL
3000
--
--
Y
MARKEL INTL
3000
F
REF0002
S
200,000
130,000
CHAUCER
4000
CHAUCER
4000
--
--
Y
MARKEL INTL
3000
L
REF0004
S
350,000
210,000
QBE
D1806
MARKEL INTL
3000
HISCOX
1165
Y
MARKEL INTL
3000
L
REF0005
A
1,200,000
500,000
GLOBAL
AEROSPACE
401204
MARKEL INTL
3000
CATLIN
2020
T
XCS
LCO1
F
REF0009
S
45,000
25,000
CATLIN
2020
CATLIN
2020
MARKEL INTL
3000
Y
UNIQUE MARKET
REFERENCE
UNIQUE CLAIM
REFERENCE
TRANSACTION
REFERENCE
SEQUENCE
NUMBER
ORIGINAL PREMIUM
SIGNING NUMBER
INSURED /
REINSURED NAME
LOSS NAME
DATE OF LOSS
RISK
CODE
RISK DESCRIPTION
YEAR OF
ACCOUNT
B0576001122
B05760007
B05761011
01
99999 22/12/06
ABC SHIPPING
FLORIDA STORM LOSSES
20071201
V
CARGO ALL RISKS
2006
B0576008899
B05769998
B05761077
02
88888 08/09/07
XYZ AIRLINES
MEXICO CRASH
20071214
H2
AIRLINE HULL
2007
77777 03/01/08
US ATTORNEYS
INC
CHICAGO BANK CLAIM
20080105
DO
D&O LIABILITY
2008
66666 17/10/07
NEW YORK
CRUISES
OCEAN CRUISER
GROUNDING
20080114
T
VESSELS
2007
22222 12/01/08
UK INSURANCE
COMPANY
SPRING FLOODS
20080217
XU
NM PROPERTY XOL
2008
B0576007711
B0576003344
B0576007676
B05765556
B05763244
B05769907
© Xchanging 2010 – Confidential
B05761865
B05761534
B05761104
01
02
01
Document uncontrolled once printed
Page 18 of 29
OS
QUAL
SEG
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
5.4
EL4.4 Incomplete Transactions for Brokers on Company Claims (DL5113)
This report will be sent to all brokers on company claims. This illustration shows data that would be sent to Aon (broker code 0823):
HDR
WEEKLY INCOMPLETE TRS FOR BROKERS - COMPANIES
DL5113
20080601
2
20080602 13:09
BROKER
CODE
BROKER
NAME
BROKER
CONTACT NAME
TRANSACTION STATUS
TRANSACTION
STATUS CODE
ACTION REQUIRED
BY BROKER?
DAYS SINCE
LAST ACTION
CREATED
DATE
LAST UPDATED
DATE
Queried By/Next
Action
CARRIER
CODE
ILU Example 1
0823
AON
BARRY
QUERIED
12
Y
12
20080112
20080513
SWISS RE
377201
ILU Example 2
0823
AON
BARRY
PARTIALLY AUTHORISED
15
N
6
20080128
20080521
SWISS RE
377201
LIRMA Example 1
0823
AON
MIKE
CIRCULATED
20
Y
4
20080405
20080523
SWISS RE
E6200
LIRMA Example 1
0823
AON
MIKE
CIRCULATED
20
Y
4
20080405
20080523
AXIS
A9208
LIRMA Example 1
0823
AON
MIKE
CIRCULATED
20
N
4
20080405
20080523
ZURICH
Z4904
LIRMA Example 2
0823
AON
BARRY
IN ERROR
01
Y
3
20080528
--
--
--
CARRIER
ROLE
CARRIER
REFERENCE
CARRIER
RESPONSE
CODE
CLAIMS
ADJUSTER'S
NAME
ADVICE
/ SETT
IND
100% OUTSTDG.
CLAIM AMOUNT
(IN GBP)
100% AMOUNT
PAID THIS TIME
(IN GBP)
SLIP LEADER NAME
L
REF001
PEND
DAVID
S
50,000
20,000
CATLIN
A
REF0002
S
200,000
130,000
GLOBAL AEROSPACE
SLIP
LEADER
CODE
BUREAU LEADER
NAME
BUREAU
LEADER
CODE
OTHER
AGREEMENT
PARTY NAME
OTHER
AGREEMENT
PARTY CODE
TRANSITION
INDICATOR
2020
SWISS RE ZURICH
401204
GLOBAL AEROSPACE
377201
AIG
400501
Y
401204
SWISS RE
377201
Y
A
REF0004
INF
GEOFF
S
350,000
210,000
HISCOX
1165
QBE
D1806
VARIOUS
VARIOUS
Y
A
REF9977
INF
PAT
S
350,000
210,000
HISCOX
1165
QBE
D1806
VARIOUS
VARIOUS
Y
A
REF5588
CAA
WILL
S
350,000
210,000
HISCOX
1165
QBE
D1806
VARIOUS
VARIOUS
Y
--
--
--
--
A
1,200,000
500,000
SWISS RE ITALY
E6200
SWISS RE ITALY
E6200
AXIS
A9208
T
UNIQUE
MARKET
REFERENCE
UNIQUE CLAIM
REFERENCE
TRANSACTION
REFERENCE
SEQUENCE
NUMBER
ORIGINAL
PREMIUM SIGNING
NUMBER
INSURED /
REINSURED NAME
LOSS NAME
DATE OF LOSS
CLASS OF
BUSINESS
CODE
CLASS OF BUSINESS DESCRIPTION
B0823001122
B08230007
B08231011
01
PMC07 114466
23/05/07
ABC SHIPPING
FLORIDA STORM
LOSSES
20071201
MC
MARINE CARGO
B0823008899
B08239998
B08231077
02
PMA07 112233
03/04/07
XYZ AIRLINES
MEXICO CRASH
20071214
AH
AVIATION HULL
B0823007711
B08235556
B08231865
01
07100988888
US ATTORNEYS
INC
CHICAGO BANK
CLAIM
20080105
NM
NON-MARINE DIRECT INS.
B0823007711
B08235556
B08231865
01
07100988888
US ATTORNEYS
INC
CHICAGO BANK
CLAIM
20080105
NM
NON-MARINE DIRECT INS.
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 19 of 29
OS
QUAL
SEG
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
B0823007711
B08235556
B08231865
01
07100988888
US ATTORNEYS
INC
CHICAGO BANK
CLAIM
20080105
NM
NON-MARINE DIRECT INS.
B0823003344
B08233244
B08231534
01
07260899988
NEW YORK
CRUISES
OCEAN CRUISER
GROUNDING
20080114
MH
MARINE HULL
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 20 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
5.5
EL4.5 Incomplete Transactions (DL7528) - Management
This report will be sent to Lloyd’s, the LMBC and the MRO.
DL7528
INCOMPLETE TRANSACTION TOTALS –
WEEK ENDING 30/05/08
20080601
20080602 13:09
MARKET SECTOR
0 to 5 DAYS
6 to 30 DAYS
31 to 90 DAYS
OVER 90 DAYS
LLOYD’S
560
230
54
19
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 21 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
5.6
Transaction Status Codes
The status codes that are allocated to ECF Claim transactions or are displayed within ECF/CLASS are detailed below.
Claim Origin
Transaction Status
Transaction Status Code
Lloyd’s
Fully Authorised
30, 31, 32, 33 or 36
Part Authorised (this may indicate that a query has been raised by an agreement party)
14 or 15
Awaiting Action / Queried (by the Lloyd’s Leader)
10
Awaiting Market Check
09
Rejected – Market Check
05
Awaiting Action
10
Awaiting Reinstatement
20
Circulated
20
Purged
08
Awaiting Action
10
Awaiting Reinstatement
24 or 25
Fully Authorised
30
Part Authorised
15
Pended
12
Purged
08
In Error
01, 02, 03 and 04.
Completed
40
LIRMA
ILU
All
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 22 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
5.7
Claim Response Codes
Details of how carriers can respond to transactions within ECF/CLASS are provided below for information.
Claim Origin
Response Status
Lloyd’s
Seen/Action (claim advices)
S/A
Query/Return (claim advices)
QUE
Agree to Pay (settlement requests)
PAY
Authorised (settlement requests)
AUT
No response has yet been made to the transaction
NAK
Claim Advice Accepted (claim advices)
CAA
Carrier requires further information (claim advices & settlement requests)
INF
File or further documentation requested (claim advices & settlement requests)
FIL
Carrier in Dispute regarding the claim (loss claim advices only)
DIS
Claim Settlement Agreed (settlement requests)
YES
Carrier is disputing the claim (settlement requests)
NO
Carrier agreed claim but has an accounting issue with the client (settlement requests)
ACC
YES responses set to CES if carrier sets Immediate Partial Collection to ‘C'
CES
LIRMA
ILU
Response
Status Code
To indicate that the transaction is agreed
ACCEPT
To indicate that they are querying the transaction
5.8
PEND
Generic Rules
The tables below indicates circumstances under which a transaction might appear on the report and the rule about the setting of the “action
required” indicator. However it is important to note that the report is not based on transaction’s status, but rather on their logged time. The table is
left in the document as a guideline and as a comparison to previous live versions of the report only.
Incomplete Transactions Report DL6201 - sent to Company Carriers
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 23 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
Type of transaction being reported
in DL6201
Trigger causing
transaction to appear
in report DL6201
Role of the party receiving
report DL6201
Transaction
Included for
this party?
Partially Authorised ILU transaction
Transaction status is 15
Lead
Yes
N/A
Additional Agreement party
Yes
Additional Agreement party has not yet made AUT response.
Lead
Yes
Any previous transaction is fully authorised and on the current
transaction the ILU lead has NAK* response or LIRMA lead has not
circulated.
Additional Agreement party
No
N/A
Lead
Yes
Any previous transaction is fully authorised and on the current
transaction the LIRMA lead has not made a YES or CAA response
Additional Agreement party
Yes
Any previous transaction is fully authorised and on the current
transaction an agreement party has not made YES or CAA response
Lead
Yes
N/A
Additional Agreement party
No
N/A
Lead
Yes
N/A
Additional Agreement party
No
N/A
Lead
Yes
N/A
Additional Agreement party
No
N/A
Lead
No
N/A
Additional Agreement party
No
N/A
Lead
No
N/A
Additional Agreement party
No
N/A
Awaiting Action (by the Leader)
Circulated by the LIRMA lead (LIRMA
claims only)
Pended (ILU only)
Transaction status is 10
Transaction status is 20
Transaction status is 12
Awaiting Reinstatement Premium
Processing (ILU)
Transaction status is 24
Awaiting Reinstatement Premium
Processing on the previous
transaction (ILU)
Transaction status is 25
In Error
Transaction status is 01,
02, 03 or 04
Purged
Transaction status is 08
Trigger causing party to be set 'action required by carrier' to 'Y'
*NAK response - party has not entered a response of S/A or PAY or QUE
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 24 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
Incomplete Transactions Report DL6202 - sent to Lloyd's Carriers and XCS
The table defines circumstances under which a transaction appears on the report and the rule about the setting of the “action required” indicator.
Type of transaction being reported in
DL6202
Trigger causing
transaction to appear
in report DL6202
Role of the party
receiving report DL6202
Transaction
Included for
this party?
Lloyd's fully Authorised but Incomplete
transactions - these are old style 'coupled'
claims.
Transaction status is
31, 32, or 33
Lead
Yes
N/A
Additional Agreement party
No
N/A
XCS
No
N/A
Lead
Yes
N/A
Additional Agreement party
Yes
Additional Agreement party has NAK response*
XCS
Yes
Any previous transaction is fully authorised, on the current
transaction all other Lloyd's agreement parties have responded
S/A or pay and the transaction is not an "unclosed advice"
Transaction status is 10
Lead
Yes
Lead has NAK response. Unless i) there is a previous
transaction where they haven't responded or have responded
QUE** or ii) if the transaction is an 'unclosed advice'.
Transaction status is 10
& leader has responded
QUE
Additional Agreement party
Yes
Additional Agreement party has NAK response. Unless i) there
is a previous transaction where they are required to respond
but have not responded or have responded QUE** or ii) if the
transaction is an 'unclosed advice'.
Transaction status is 10
& leader has responded
QUE
XCS
Yes
Lead or Additional Agreement party has made QUE responses
and LCO1 has a NAK response. Unless i) there is a previous
transaction where XCS hasn't responded or has responded
'QUE' or ii) if the transaction is an 'unclosed advice'.
Partially Authorised Lloyd's transactions
Awaiting Action (by the Leader)
Transaction status is 14
or 15
Trigger causing party to be set 'action required by carrier'
to 'Y'
*NAK response - party has not entered a response of S/A or PAY or QUE
**NAK BLACK - a transaction is created where one or more preceding transaction has at least one agreement party who has not responded S/A or PAY
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 25 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
Incomplete Transactions Report DL5112 - sent to Brokers on Lloyd's claims
The table defines circumstances under which a transaction appears on the report and the rule about the setting of the “action required” indicator.
Type of transaction being reported in DL5112
Trigger causing
transaction to appear in
report DL5112
Role of the party
receiving report DL5112
Transaction Included
for this party?
Lloyd's fully Authorised but Incomplete
transactions - these are old style 'coupled'
claims.
Transaction status is 31,
32 or 33
Broker
Yes
N/A
Partially Authorised Lloyd's transactions
Transaction status is 14
Broker
Yes
Additional Agreement party or XCS have made a
QUE response or the transaction is an unclosed
advice.
Partially Authorised Lloyd's transactions
Transaction status is 15
Broker
Yes
Additional Agreement party has made a QUE
response or the transaction is an unclosed
advice.
Awaiting Action (by the Leader)
Transaction status is 10
Broker
Yes
Lead, Additional Agreement party, or XCS have
made a QUE response or the transaction is an
unclosed advice.
In Error
Transaction status is 01,
02, 03 or 04
Broker
Yes
All set to 'Y'
Market Check Rejected
Transaction status is 05
Broker
Yes
All set to 'Y'
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Trigger causing party to be set 'action
required by broker' to 'Y'
Page 26 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
Incomplete Transactions Report DL5113 - sent to Brokers on Company claims
The table defines circumstances under which a transaction appears on the report and the rule about the setting of the “action required” indicator.
Type of transaction being reported in
DL5113
Trigger causing
transaction to appear
in report DL5113
Role of the party
receiving report
DL5113
Transaction Included
for this party?
Partially Authorised ILU transaction
Transaction status is 15
Broker
Yes
N/A
Awaiting Action (by the Leader)
Transaction status is 10
Broker
Yes
Lead has responded INF, FIL, ACC, DIS, NO (LIRMA)
or PEN (ILU).
Circulated by the LIRMA lead
Transaction status is 20
Broker
Yes
Lead or Additional Agreement party has responded
INF, FIL, ACC, DIS or NO.
Pended (ILU only)
Transaction status is 12
Broker
Yes
All set to 'Y'
Awaiting Reinstatement Premium Processing
(ILU)
Transaction status is 24
Broker
Yes
N/A
Awaiting Reinstatement Premium Processing
on the previous transaction (ILU)
Transaction status is 25
Broker
Yes
N/A
In Error
Transaction status is 01,
02, 03 or 04
Broker
Yes
All set to 'Y'
Purged
Transaction status is 8
Broker
Yes
All set to 'Y'
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Trigger causing party to be set 'action required by
broker' to 'Y'
Page 27 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
Incomplete Transactions Report DL7528 - sent to Lloyd’s Management, LIIBA and MRO
The market associations will receive a weekly report that provides details of the current number of incomplete ECF transactions. The report will
show totals of Lloyd’s claim transactions, banded according to the number of days that the transaction has been ‘inactive’. This report will be
sent to Lloyd’s, the LMBC and the MRO.
Type of transaction being reported in DL7528
Trigger causing
transaction to appear in
report DL7528
Role of the party
receiving report DL7528
Transaction seen by
this party?
Trigger causing party to be set 'action
required' to 'Y'
Lloyd's fully Authorised but Incomplete
transactions - these are old style 'coupled'
claims.
Transaction status is 31,
32 or 33
Management
Yes
N/A
Partially Authorised Lloyd's transactions
Transaction status is 14
Management
Yes
N/A
Partially Authorised Lloyd's transactions
Transaction status is 15
Management
Yes
N/A
Awaiting Market Check
Transaction status is 09
Management
Yes
N/A
Awaiting Action (by the Leader)
Transaction status is 10
Management
Yes
N/A
In Error
Transaction status is 01,
02, 03 or 04
Management
Yes
N/A
Market Check Rejected
Transaction status is 05
Management
Yes
N/A
Report DL7528 shows total numbers of transactions that have a TRANS-STATUS of less than '40' - it does not have an 'Action Required' field
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 28 of 29
ECF2 Reporting - ECF004
Report Specification
Version 0.99, Draft
© Xchanging 2010 – Confidential
Document uncontrolled once printed
Page 29 of 29