Please respond to:
LME Clear Relationship Management
Lmeclearing@lme.com
This document is published by LME Clear Limited. To the best of the publisher’s knowledge and belief, statements made are correct at the time of going to press. All
such statements and all opinions expressed herein are published for the general information of readers but are not to be taken as recommendations for any course of
action. The publisher accepts no liability for the accuracy of any statement or representation.
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
1
Contents
1
Introduction
3
2
LME Clear reporting examples
4
2.1
Counterparty Data
5
2.2
Common Data
10
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
2
1
Introduction
nd
On 22 September 2014, LME Clear went live, becoming the central counterparty to all LME
Exchange contracts and providing segregation for all LME Client contracts.
nd
From 22 September 2014 LME Clear began meeting its reporting obligation to report all its
transactions and exposure data to a Trade Repository (TR).
ESMA have now directed all Trade Repositories to reject certain EMIR fields that have not been
populated with an applicable entry. These changes have been titled ‘ESMA Data Validation 1’ and
impact the ‘Required’/’Conditional’/’Optional’ nature of the data fields reported to TRs.
This document has been produced to provide clarity as to how LME Clear will be reporting trades and
st
positions following the introduction of ESMA Data Validation on 1 December 2014. Examples for an
LME Forward and LME Option have been provided which specifies how LMEwire will report each
ESMA Common and Counterparty Data field for LME Clear (as CCP) following the introduction of
‘ESMA Data Validation 1’.
The objectives of the document are:
 Provide a point of reference for LME Clear reporting of LME ETD trades and positions;
 Facilitate improvements in the TR matching of reported LME ETD trades.
The information in this document also takes account of the ESMA Q&A, ESMA/2014/1300 published
th
on 24 October 2014.
The information contained in this document is subject to change in accordance with further
ESMA clarification, subsequent discussions and views of the industry participants and
evolving trading standards and practices.
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
3
2
LME Clear reporting examples
The below examples are for two LME Exchange trades booked between Clearing Members ABC
Limited and XYZ Limited.
LME Clear is the reporting entity for its trades and positions with ABC, reporting for itself only.
All entities, LMEC and ABC, are incorporated in Europe and ABC is an Investment firm in accordance
with Directive 2004/39/EC
Trade Parameters
LME Forward
LME Traded Option
Buyer
LMEC
ABC
Seller
ABC
LMEC
Metal
CAD
AHE
Option Call/Put
-
Call
Option Strike Price
-
EUR2,000.00
Lots
10
20
Price/Premium rate
USD8,000.00
EUR100.50
Prompt Date
16Oct14
Dec14
Matched/Novated Date
22Sep14
22Sep14
MatchRefNo – LMEsmart Tag 5935
2014092200014751
2014092200012771
Slip ID – LMEsmart Tag 5442
10014772
10000971
ABC_H_1
ABC_H_1
Booking Account at LMEC
ABC House account
In the Counterparty and Common tables below, LMEwire details what it will report for both trades and
positions based on its interpretation of ESMA requirements.
Where the Counterparty data section is the same for both the forward and the option it is shown in
green; where it is different it is shown in red or blue as per the specific trades detailed above.
Throughout all references to LEIs should be taken to be references to pre-LEIs.
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
4
2.1
No.
Counterparty Data
Field
Details to be reported
ESMA Format
LMEC Value for Trades
LMEC Value for Positions
1
Reporting
timestamp
Date and time of reporting to the trade
repository.
ISO 8601 date format / UTC time format.
YYYY-MM-DDTHH:MM:SSZ
YYYY-MM-DDTHH:MM:SSZ
2
Counterparty ID
Unique code identifying the reporting
counterparty. In case of an individual, a client
code shall be used.
Legal Entity Identifier (LEI) (20 alphanumerical
digits), interim entity identifier (20 alphanumerical
digits), BIC (11 alphanumerical digits) or a client
code (50 alphanumerical digits).
LMEC LEI
LMEC LEI
213800L8AQD59D3JRW81
213800L8AQD59D3JRW81
LEI for ABC
LEI for ABC
LME Clear Limited
LME Clear Limited
56 Leadenhall Street
London EC3A 2DX
UK
56 Leadenhall Street
London EC3A 2DX
UK
3
4
5
ID of the other
counterparty
Unique code identifying the other counterparty
of the contract. This field shall be filled from the
perspective of the reporting counterparty. In
case of an individual, a client code shall be
used.
Legal Entity Identifier (LEI) (20 alphanumerical
digits), interim entity identifier (20 alphanumerical
digits), BIC (11 alphanumerical digits) or a client
code (50 alphanumerical digits).
Name of the
counterparty
Corporate name of the reporting counterparty.
This field can be left blank in case the
counterparty ID already contains this
information.
100 alphanumerical digits or blank in case of
coverage by Legal Entity Identifier (LEI).
Domicile of the
counterparty
Information on the registered office, consisting
of full address, city and country of the reporting
counterparty. This field can be left blank in
case the counterparty ID already contains this
information.
500 alphanumerical digits or blank in case of
coverage by Legal Entity Identifier (LEI).
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
5
No.
6
Field
Details to be reported
Corporate sector
of the
counterparty
Nature of the reporting counterparty's company
activities (bank, insurance company, etc.). This
field can be left blank in case the counterparty
ID already contains this information.
[FOA note:
Corporate sector is not part of the Pre-LEI, so
this field must be populated if Pre-LEI is used]
7
8
9
ESMA Format
Taxonomy:
A=Assurance undertaking authorised in
accordance with Directive 2002/83/EC;
C=Credit institution authorised in accordance
with Directive 2006/48/EC;
F=Investment firm in accordance with Directive
2004/39/EC;
I=Insurance undertaking authorised in
accordance with Directive 73/239/EEC;
L=Alternative investment fund managed by
AIFMs authorised or registered in accordance
with Directive 2011/61/EU;
R=Reinsurance undertaking authorised in
accordance with Directive 2005/68/EC;
U=UCITS and its management company,
authorised in accordance with Directive
2009/65/EC;
or blank in case of coverage by Legal Entity
Identifier (LEI) or in case of non-financial
counterparties.
LMEC Value for Trades
LMEC Value for Positions
[Blank]
[Blank]
[LMEC is reporting [Blank] as
the Taxonomy does not cater
for a CCP]
[LMEC is reporting [Blank] as
the Taxonomy does not cater
for a CCP]
Financial or nonfinancial nature
of the
counterparty
Indicate if the reporting counterparty is a
financial or non-financial counterparty in
accordance with Article 2(8,9)of Regulation
(EU) No 648/2012.
F=Financial Counterparty, N=Non-Financial
Counterparty.
[Blank]
[Blank]
[LMEC is reporting as “ESMACCP”]
[LMEC is reporting as “ESMACCP”]
Broker ID
In case a broker acts as intermediary for the
reporting counterparty without becoming a
counterparty, the reporting counterparty shall
identify this broker by a unique code. In case of
an individual, a client code shall be used.
Legal Entity Identifier (LEI) (20 alphanumerical
digits), interim entity identifier (20 alphanumerical
digits), BIC (11 alphanumerical digits) or a client
code (50 alphanumerical digits).
[Blank]
[Blank]
In case the reporting counterparty has
delegated the submission of the report to a
third party or to the other counterparty, this
entity has to be identified in this field by a
unique code. Otherwise this field shall be left
blank. In case of an individual, a client code
shall be used, as assigned by the legal entity
used by the individual counterparty to execute
the trade.
Legal Entity Identifier (LEI) (20 alphanumerical
digits), interim entity identifier (20 alphanumerical
digits), BIC (11 alphanumerical digits) or a client
code (50 alphanumerical digits).
Reporting entity
ID
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
6
[No Broker used on these
trades]
LMEC LEI
LMEC LEI
213800L8AQD59D3JRW81
213800L8AQD59D3JRW81
No.
10
11
12
13
14
Field
Details to be reported
ESMA Format
Clearing member
ID
In case the reporting counterparty is not a
clearing member, its clearing member shall be
identified in this field by a unique code. In case
of an individual, a client code, as assigned by
the CCP, shall be used.
Beneficiary ID
Trading capacity
Counterparty
side
Contract with
non-EEA
counterparty
LMEC Value for Trades
LMEC Value for Positions
Legal Entity Identifier (LEI) (20 alphanumerical
digits), interim entity identifier (20 alphanumerical
digits), BIC (11 alphanumerical digits) or a client
code (50 alphanumerical digits).
[Blank]
[Blank]
The party subject to the rights and obligations
arising from the contract. Where the
transaction is executed via a structure, such as
a trust or fund, representing a number of
beneficiaries, the beneficiary should be
identified as that structure. If the beneficiary of
the contract is not a counterparty to this
contract, the reporting counterparty has to
identify this beneficiary by a unique code or, in
case of individuals, by a client code as
assigned by the legal entity used by the
individual.
Legal Entity Identifier (LEI) (20 alphanumerical
digits), interim entity identifier (20 alphanumerical
digits), BIC (11 alphanumerical digits) or a client
code (50 alphanumerical digits).
LMEC LEI
LMEC LEI
213800L8AQD59D3JRW81
213800L8AQD59D3JRW81
Identifies whether the reporting counterparty
has concluded the contract as principal on own
account (on own behalf or behalf of a client) or
as agent for the account of and on behalf of a
client.
P=Principal, A=Agent.
P
P
Identifies whether the contract was a buy or a
sell. In the case of an interest rate derivative
contract, the buy side will represent the payer
of leg 1 and the sell side will be the payer of leg
2.
B=Buyer, S=Seller.
B
B
S
S
Indicates whether the other counterparty is
domiciled outside the EEA.
Y=Yes, N=No.
[Y/N - As per Member
Reference Data]
[Y/N - As per Member
Reference Data]
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
7
No.
15
16
17
18
19
Field
Details to be reported
Directly linked to
commercial
activity or
treasury
financing
Information on whether the contract is
objectively measurable as directly linked to the
reporting counterparty's commercial or treasury
financing activity, as referred to in Art. 10(3) of
Regulation (EU) No 648/2012. This field shall
be left blank in case the reporting counterparty
is a financial counterparty, as referred to in Art.
2 (8) Regulation (EU) No 648/2012.
Y=Yes, N=No.
Clearing
threshold
Information on whether the reporting
counterparty is above the clearing threshold as
referred to in Art. 10(3) of Regulation (EU) No
648/2012. This field shall be left blank in case
the reporting counterparty is a financial
counterparty, as referred to in Art. 2 (8)
Regulation (EU) No 648/2012.
Y=Above, N=Below.
Mark to market valuation of the contract, or
mark to model valuation where applicable
under Article 11(2) of Regulation (EC) No
648/2012.
Up to 20 numerical digits in the format
xxxx,yyyyy.
Mark to market
value of contract
Currency of mark
to market value
of the contract
Valuation date
ESMA Format
LMEC Value for Trades
LMEC Value for Positions
[Blank]
[Blank]
[LMEC reporting [Blank] as not
an NFC]
[LMEC reporting [Blank] as not
an NFC]
[Blank]
[Blank]
[LMEC reporting [Blank] as not
an NFC]
[LMEC reporting [Blank] as not
an NFC]
[Blank]
DCVM - Variation Margin
[Industry stance is that for ETD
MTM applies to Positions only]
NLV - Variation Margin
USD
The currency used for the mark to market
valuation of the contract, or mark to model
valuation where applicable under Article 11(2)
of Regulation (EC) No 648/2012.
ISO 4217 Currency Code, 3 alphabetical digits.
[Blank]
[LMEC will always report MTM in USD/base
currency rather than the native currency of the
traded instrument]
[Industry stance is that for ETD
MTM applies to Positions only]
Date of the last mark to market or mark to
model valuation.
ISO 8601 date format.
[Blank]
LME Clear EMIR Reporting following ESMA Data
Validation 1
[Industry stance is that for ETD
MTM applies to Positions only]
Version 0.1
8
EUR
YYYY-MM-DD
No.
20
21
22
Field
Valuation time
Valuation type
Collateralisation
Details to be reported
24
25
26
LMEC Value for Trades
LMEC Value for Positions
[Blank]
23:59:00 UTC
Time of the last mark to market or mark to
model valuation.
UTC time format.
Indicate whether valuation was performed mark
to market or mark to model.
M=mark to market / O=mark to model.
Whether collateralisation was performed.
U=uncollateralised, PC= partially collateralised,
OC=one way collateralised or FC- fully
collateralised.
[Blank]
U
[Industry stance is that for ETD
Collateral applies to Positions
only]
[ESMA Q&A TR 33 23Jun14
applies]
[Blank]
[Blank]
[Industry stance is that entity lodging collateral
reports, LMEC is not lodging any collateral with
Members]
23
ESMA Format
[Industry stance is that for ETD
MTM applies to Positions only]
[Blank]
M
[Industry stance is that for ETD
MTM applies to Positions only]
Collateral
portfolio
Whether the collateralisation was performed on
a portfolio basis. Portfolio means the collateral
calculated on the basis of net positions
resulting from a set of contracts, rather than
per trade.
Y=Yes, N=No.
Collateral
portfolio code
If collateral is reported on a portfolio basis, the
portfolio should be identified by a unique code
determined by the reporting counterparty.
Up to 10 numerical digits.
Value of the
collateral
Value of the collateral posted by the reporting
counterparty to the other counterparty. Where
collateral is posted on a portfolio basis, this
field should include the value of all collateral
posted for the portfolio.
Currency of the
collateral value
Specify the value of the collateral for field 25.
[Industry stance is that for ETD
Collateral applies to Positions
only]
[Blank]
LMCABC_H_1
[Industry stance is that for ETD
Collateral applies to Positions
only]
[LME mnemonic + LMEC
Account ID from RTC]
Specify the value the total amount of collateral
posted; up to 20 numerical digits in the format
xxxx,yyyyy.
[Blank]
[Blank]
Specify the currency of field 25; ISO 4217
Currency Code, 3 alphabetical digits.
[Blank]
[Industry stance is that for ETD
Collateral applies to Positions
only]
[Industry stance is that for ETD
Collateral applies to Positions
only]
[Only to be reported after 12Feb14 + 180 days]
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
9
[Blank]
2.2
No.
Common Data
Field
Taxonomy used
Details to be reported
The contract shall be identified by using a
product identifier.
Refer UTI & UPI Paper.
U=Product Identifier [endorsed in Europe]
I=ISIN/AII + CFI
E=Interim taxonomy
I
I
I
I
For taxonomy = U: Product Identifier (UPI),
to be defined For taxonomy = I: ISIN or AII,
12 digits alphanumerical code For taxonomy
= E: Derivative class: CO=Commodity
CR=Credit CU=Currency EQ=Equity
IR=Interest Rate OT= Other
Refer to ‘LME Clear UTI &
UPI’ Paper.
Refer to ‘LME Clear UTI & UPI’
Paper.
XLMECADF20141016
XLMECADF20141016
XLMEAHEOC201412032000
XLMEAHEOC201412032000
For taxonomy = U: Blank For taxonomy = I:
CFI, 6 characters alphabetical code For
taxonomy = E: Derivative type: CD=
Contracts for difference FR= Forward rate
agreements FU= Futures FW=Forwards
OP=Option SW=Swap OT= Other
Refer to ‘LME Clear UTI &
UPI’ Paper.
Refer to ‘LME Clear UTI & UPI’
Paper.
FCEPSX
FCEPSX
OCAFPS
OCAFPS
The underlying shall be identified by
using a unique identifier for this
underlying. In case of baskets or indices,
an indication for this basket or index shall
be used where a unique identifier does
not exist.
ISIN (12 alphanumerical digits); LEI (20
alphanumerical digits); Interim entity
identifier (20 alphanumerical digits); UPI (to
be defined); B= Basket; I=Index.
[As per ESMA Q&A TR28]
[As per ESMA Q&A TR28]
[Blank]
[Blank]
[Currently LMEC is reporting
[Blank] as DTCC does not
support “NA”]
[Currently LMEC is reporting
[Blank] as DTCC does not
support “NA”]
The currency of the notional amount. In
the case of an interest rate derivative
contract, this will be the notional currency
of leg 1.
ISO 4217 Currency Code, 3 alphabetical
digits.
USD/EUR/GBP/JPY
USD/EUR/GBP/JPY
USD
USD
EUR
EUR
The currency of the notional amount. In
the case of an interest rate derivative
contract, this will be the notional currency
ISO 4217 Currency Code, 3 alphabetical
digits.
Leave Blank for Commodities
Leave Blank for Commodities
[Blank]
[Blank]
The contract shall be identified by using a
product identifier.
The contract shall be identified by using a
product identifier.
3
Underlying
4
Notional
currency 1
5
6
Notional
currency 2
LMEwire Value for Positions
Refer UTI & UPI Paper.
2
Product id 2
LMEwire Value for Trades
Identify the taxonomy used:
1
Product id 1
ESMA Format
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
10
No.
Field
Details to be reported
ESMA Format
LMEwire Value for Trades
LMEwire Value for Positions
of leg 2.
7
Deliverable
currency
Trade id
8
Transaction
reference
number
9
The currency to be delivered.
A Unique Trade ID agreed at the
European level, which is provided by the
reporting counterparty. If there is no
unique trade ID in place, a unique code
should be generated and agreed with the
other counterparty.
A unique identification number for the
transaction provided by the reporting
entity or a third party reporting on its
behalf.
ISO 4217 Currency Code, 3 alphabetical
digits.
Up to 52 alphanumerical digits.
An alphanumeric field up to 40 characters
USD/EUR/GBP/JPY
USD/EUR/GBP/JPY
USD
USD
EUR
EUR
Refer to ‘LME Clear - UTI &
UPI Paper’ – UTI for Trade
Refer to ‘LME Clear - UTI &
UPI Paper’ – UTI for Position
E01LMEC000201409220001
475110014772
E01LMEC000LMCABC_H_1C
AD161014
E01LMEC000201409220001
277110000971
E01LMEC000LMCABC_H_1A
HE031214C2000
[As per FIA guidance
currently no way to report
TRN correctly. Reported as
“NA” – not available]
Blank for Positions
[Blank]
N/A
Venue of
execution
10
Compression
The venue of execution shall be identified
by a unique code for this venue. In case
of a contract concluded OTC, it has to be
identified whether the respective
instrument is admitted to trading but
traded OTC or not admitted to trading
and traded OTC.
ISO 10383 Market Identifier Code (MIC), 4
digits alphabetical.
Refer to ‘LME Clear - UTI &
UPI Paper’
Refer to ‘LME Clear - UTI &
UPI Paper’
Where relevant, XOFF for listed derivatives
that are traded off-exchange or XXXX for
OTC derivatives.
XLME
XLME
Identify whether the contract results from
a compression exercise.
Y = if the contract results from compression;
N= if the contract does not result from
compression.
Refer ESMA Q&A 20Dec13
TR 17
Refer ESMA Q&A 20Dec13
TR 17
N
Y
Up to 20 numerical digits in the format
xxxx,yyyyy.
Trade Price
Position Price
11
12
Price/rate
The price per derivative excluding,
where applicable, commission and
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
11
No.
Field
Details to be reported
ESMA Format
LMEwire Value for Trades
accrued interest.
Price notation
13
The manner in which the price is
expressed.
E.g. ISO 4217 Currency Code, 3
alphabetical digits, percentage.
LMEwire Value for Positions
8000.00000
[Blank]
100.50000
[Blank]
USD/EUR/GBP/JPY
USD/EUR/GBP/JPY
USD
[Blank]
EUR
Notional amount
Original value of the contract.
Up to 20 numerical digits in the format
xxxx,yyyyy.
14
[Quantity x Price multiplier x
Price for Futures, Strike Price
for Options]
[Quantity x Price Multiplier X
(Closing Price for Futures,
Strike Price for Options)]
2000000.00000
(10 x 25 x CCP Closing
Price)
1000000.00000
1000000.00000
Price multiplier
15
Quantity
16
Up-front payment
The number of units of the financial
instrument which are contained in a
trading lot; for example, the number of
derivatives represented by one contract.
Up to 10 numerical digits.
Number of contracts included in the
report, where more than one derivative
contract is reported.
Up to 10 numerical digits.
Amount of any up-front payment the
reporting counterparty made or received.
17
Delivery type
18
Indicates whether the contract is settled
physically or in cash.
Lot Size
Lot Size
25
25
25
25
Number of Lots
Number of Lots
10
10
20
20
Up to 10 numerical digits in the format
xxxx,yyyyy for payments made by the
reporting counterparty and in the format
xxxx,yyyyy for payments received by the
reporting counterparty.
Premium value for LME
Options & TAPOs
Blank for Positions
C=Cash, P=Physical, O=Optional for
counterparty.
As per product definition
As per product definition
P
P
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
[Blank]
[Blank as N/A for Forward]
50250.00000
12
No.
Field
Execution
timestamp
Details to be reported
As defined in Article 1(2).
ESMA Format
LMEwire Value for Trades
ISO 8601 date format / UTC time format.
19
LMEwire Value for Positions
P
P
[ESMA Q&A 19Dec13
requires use of Trade Date &
Trade Time from LMEsmart]
Blank for Positions
[Blank]
YYYY-MM-DDTHH:MM:SSZ
Effective date
20
Maturity date
21
Termination date
22
23
Date of
settlement
Master
agreement type
24
25
Master
agreement
version
Date when obligations under the contract
come into effect.
ISO 8601 date format.
Original date of expiry of the reported
contract. An early termination shall not be
reported in this field.
ISO 8601 date format.
Termination date of the reported contract.
If not different from maturity date, this
field shall be left blank.
ISO 8601 date format.
Date of settlement of the underlying. If
more than one, further fields may be
used (e.g. 23A, 23B, 23C, etc.).
ISO 8601 date format.
[Trade date reported]
[Date of position reported]
2014-09-22
YYYY-MM-DD
As per product definition
As per product definition
2014-10-16
2014-10-16
2014-12-03
2014-12-03
ISDA specific term N/A to
ETD
ISDA specific term N/A to ETD
[Blank]
[Blank]
As per product definition
As per product definition
2014-10-16
2014-10-16
2014-12-03
2014-12-03
Reference to the name of the relevant
master agreement, if used for the
reported contract (e.g. ISDA Master
Agreement; Master Power Purchase and
Sale Agreement; International ForEx
Master Agreement; European Master
Agreement or any local Master
Agreements).
Free Text, field of up to 50 characters,
identifying the name of the Master
Agreement used, if any.
Not applicable to ETD
reporting
Not applicable to ETD
reporting
[Blank]
[Blank]
Reference to the year of the master
agreement version used for the reported
trade, if applicable (e.g. 1992, 2002,
etc.).
Year, xxxx.
Not applicable to ETD
reporting
Not applicable to ETD
reporting
[Blank]
[Blank]
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
13
No.
Field
Confirmation
timestamp
26
27
Confirmation
means
Clearing
obligation
28
Details to be reported
ESMA Format
LMEwire Value for Trades
Date and time of the confirmation, as
defined under Commission Delegated
Regulation (EU) No 149/2013 ( 1 )
indicating time zone in which the
confirmation has taken place.
ISO 8601 date format, UTC time format.
Whether the contract was electronically
confirmed, non-electronically confirmed
or remains unconfirmed.
Y=Non-electronically confirmed, N=Nonconfirmed, E=Electronically confirmed.
Indicates, whether the reported contract
is subject to the clearing obligation under
Regulation (EU) No 648/2012.
Y=Yes, N=No.
LMEwire Value for Positions
[Clearing date and time
reported]
Not applicable to ETD position
reporting
YYYY-MM-DDTHH:MM:SSZ
[Blank]
[Clearing type of Electronic
reported]
Not applicable to ETD position
reporting
E
[Blank]
[Reported as “ESMA-CCP” to
indicate Not Applicable to
LMEC as CCP]
Not applicable to ETD position
reporting
[Blank]
[Blank]
Cleared
Indicates, whether clearing has taken
place.
Y=Yes, N=No.
Y
Y
Clearing
timestamp
Time and date when clearing took place.
ISO 8601 date format, UTC time format.
Cleared time and date
provided by CCP
23:59 to signify EOD and EOD
date
YYYY-MM-DDTHH:MM:SSZ
YYYY-MM-DDT23:59:00Z
29
30
CCP
31
Intragroup
32
33
Fixed rate leg 1
(tolerance tba)
In case of a contract that has been
cleared, the unique code for the CCP that
has cleared the contract.
Legal Entity Identifier (LEI) (20
alphanumerical digits) or, if not available,
interim entity identifier (20 alphanumerical
digits) or, if not available, BIC (11
alphanumerical digits).
LMEC LEI
LMEC LEI
213800L8AQD59D3JRW81
213800L8AQD59D3JRW81
Indicates whether the contract was
entered into as an intragroup transaction,
defined in Article 3 of Regulation (EU) No
648/2012.
Y=Yes, N=No.
As Applicable to
Counterparties
As Applicable to
Counterparties
N
N
An indication of the fixed rate leg 1 used,
if applicable.
Numerical digits in the format xxxx,yyyyy.
Not applicable to LME
reporting
Not applicable to LME
reporting
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
14
No.
Field
Fixed rate leg 2
(tolerance tba)
Details to be reported
An indication of the fixed rate leg 2 used,
if applicable.
ESMA Format
LMEwire Value for Trades
Numerical digits in the format xxxx,yyyyy.
34
Fixed rate day
count
35
36
37
38
39
40
Fixed leg
payment
frequency
Floating leg
payment
frequency
Floating leg reset
frequency
Floating rate of
leg 1
Floating rate of
leg 2
LMEwire Value for Positions
[Blank]
[Blank]
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
The actual number of days in the relevant
fixed rate payer calculation period, if
applicable.
Actual/365, 30B/360 or Other.
Frequency of payments for the
fixed rate leg, if applicable.
An integer multiplier of a time period
describing how often the
counterparties exchange payments,
e.g. 10D, 3M, 5Y.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
An integer multiplier of a time period
describing how often the
counterparties exchange payments,
e.g. 10D, 3M, 5Y.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
An integer multiplier of a time period
describing how often the
counterparties exchange payments,
e.g. 10D, 3M, 5Y.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
An indication of the interest rates used
which are reset at predetermined
intervals by reference to a market
reference rate, if applicable.
The name of the floating rate index, e.g. 3M
Euribor.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
An indication of the interest rates used
which are reset at predetermined
intervals by reference to a market
reference rate, if applicable.
The name of the floating rate index, e.g. 3M
Euribor.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
Frequency of payments for the
floating rate leg, if applicable.
Frequency of floating rate leg
resets, if applicable.
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
15
No.
Field
Currency 2
41
Exchange rate 1
42
43
44
Forward
exchange rate
Exchange rate
basis
Commodity Base
Details to be reported
The cross currency, if different from the
currency of delivery.
Commodity
Details
LMEwire Value for Trades
Not applicable to LME
reporting
[Blank]
[Blank]
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
E.g. EUR/USD or USD/EUR. 2 X ISO 4217
Currency Code, 3 alphabetical digits
separated by a slash.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
Indicates the type of commodity
underlying the contract.
AG=Agricultural
EN=Energy
FR=Freights
ME=Metals
IN= Index
EV= Environmental
EX= Exotic
[As per ESMA Q&A TR28]
[As per ESMA Q&A TR28]
ME
ME
Details of the particular commodity
beyond field 45.
Metals:
[As per ESMA Q&A TR28]
[As per ESMA Q&A TR28]
"PR" = Precious
NP
NP
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
The contractual rate of exchange of the
currencies.
Forward exchange rate on value date.
Quote base for exchange rate.
ISO 4217 Currency Code, 3 alphabetical
digits.
LMEwire Value for Positions
Not applicable to LME
reporting
45
46
ESMA Format
Up to 10 numerical digits in the format
xxxx,yyyyy.
Up to 10 numerical digits in the format
xxxx,yyyyy.
"NP" = Non-precious
47
48
Delivery Point or
zone (energy)
Interconnection
point (energy)
Delivery point(s) of market area(s).
Identification of the border(s) or border
point(s) of a transportation contract.
EIC code, 16 character alphanumeric code.
Free text, field of up to 50 characters.
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
16
No.
49
50
51
52
53
54
55
56
Field
Details to be reported
ESMA Format
Repeatable section of fields 50-54 to
identify the product delivery profile which
correspond to the delivery periods of a
day.
Repeatable section of fields 50-54 to identify
the product delivery profile; BL=Base Load
PL=Peak Load OP=Off-Peak BH= Block
Hours OT=Other
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
Delivery start
date time
(energy)
Start date and time of delivery.
ISO 8601 date format.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
Delivery end
date time
(energy)
End date and time of delivery.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
Contract
Capacity
(energy)
Quantity per delivery time interval.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
Quantity Unit
(energy)
Daily or hourly quantity in MWh or kWh/d
which corresponds to the underlying
commodity.
10 numerical digits in the format xxxx,yyyyy.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
If applicable, price per time interval
quantities
10 numerical digits in the format xxxx,yyyyy.
Not applicable to LME
reporting
Not applicable to LME
reporting
[Blank]
[Blank]
As per product definition
As per product definition
[Blank]
[Blank]
C
C
As per product definition
As per product definition
[Blank]
[Blank]
A
A
Load Type
(energy)
Price/time
interval
quantities
(energy)
Option type
Option style
Indicates whether the contract is a call or
a put.
Indicates whether the option may be
exercised only at a fixed date (European,
and Asian style), a series of pre-specified
dates (Bermudan) or at any time during
the life of the contract (American style).
LMEwire Value for Trades
ISO 8601 date format.
Free text, field of up to 50 characters.
P=Put, C=Call.
A=American, B=Bermudan, E=European,
S=Asian.
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
17
LMEwire Value for Positions
No.
Field
Details to be reported
ESMA Format
LMEwire Value for Trades
The strike price of the option.
57
58
59
Up to 10 Numerical digits in the format
xxxx,yyyyy.
Strike price
Action type
Whether the report contains: — a
derivative contract or post-trade event for
the first time, in which case it will be
identified as ‘new’; — a modification of
details of a previously reported derivative
contract, in which case it will be identified
as ‘modify’; — a cancellation of a wrongly
submitted report, in which case, it will be
identified as ‘error’; — a termination of an
existing contract, in which case it will be
identified as ‘cancel’; — a compression of
the reported contract, in which case it will
be identified as ‘compression’; — an
update of a contract valuation, in which
case it will be identified as ‘valuation
update’; — any other amendment to the
report, in which case it will be identified
as ‘other’.
Where field 58 is reported as ‘other’ the
details of such amendment should be
specified here.
details of action
type
LMEwire Value for Positions
As per product definition
As per product definition
[Blank]
[Blank]
2000.00000
2000.00000
[Lifecycle events
[EOD Position with MTM
included]
Compression = Z]
Valuation update
N=New
Z
M=Modify
Lifecycle events - Option
Exercise & Assignment and
Position Transfer Only = Other
E=Error
C=Cancel
Other
Z=Compression
V=Valuation update
O=Other
Lifecycle events – Option
Exercise & Assignment Only
Free text, field of up to 50 characters.
LME Clear EMIR Reporting following ESMA Data
Validation 1
Version 0.1
[Blank as N/A for Forward /
Option Trade Reporting]
18
Lifecycle events – Option
Exercise & Assignment and
Position Transfer Only
[Blank]