Page tree
Skip to end of metadata
Go to start of metadata

This topic provides an overview of CME’s European Trade Repository (ETR) operating under the brand CME Global Repository Services delivering a derivatives trade reporting service for compliance with the European Markets Infrastructure Regulation (EMIR). It covers registration for access, data submission (formats and specifications), an overview of the User Website, recovery of data via reports (Collateral, Transaction and Valuation) and customization functionality. CME ETR will leverage existing CME Group connectivity, functionality and processes in order to accept, store and report trade data, where applicable and in adherence to regulatory frameworks.

Revision History

Date

Version

Description

February 1, 20151.0Initial publication
June 24, 20192.0

Replaced PDF with wiki.

Prerequisites

This document assumes that the user has basic trade repository flow knowledge. For more information, please refer to the relevant European derivatives regulations, or contact our team:

Access to the CME ETR

Registering for ETR Test Environment Access

In order to assist clients with their preparation for the EMIR reporting requirements, CME ETR has created a Test Environment. Access to the Test Environment can be granted prior to execution of the CME ETR User Agreement by the completion of an informational form located at cmegroup.com/ETR. Production Environment access may only be granted to Users and Service Providers with completed registrations and Legal Agreements. A full ETR User registration also includes access to Test Environment. Service Providers do not have a Test Environment only option, and must sign the full Service Provider Agreement (which includes test environment access)

Steps for CME ETR Test Environment access include:

  1. Complete the ETR User Agreement or Test Environment form (single form to gain access to any of CME’s Global Trade Repositories) at www.cmegroup.com/ETR. Fill out the registration form electronically (do not print and complete).
  2. Upon completing the registration; use the forms’ submit button and your system’s default email program will prepare an email to the ETR Registration If you prefer a different email program to send in the form, you may copy the email attachment and email address into that preferred program.
  3. Once the form has been received, CME will process the Upon completion, CME ETR will send an email to the administrator contact confirming the registration and provide information on how to get started. NOTE: The URL (ETRuinr.cmegroup.com) for the test environment is different to the production environment.

For assistance during or following the registration process; please contact CME Global Repository Client Services at repositorysupport@cmegroup.com.

Registering for ETR Production Environment Access 

Production Environment access is only granted to fully registered Users and Authorized Service Providers. The following steps outline the registration process required to submit and to access derivative data to CME ETR for EMIR reporting compliance.

  1. Obtain a Legal Entity Identifier (LEI)
    1. A LEI is strictly required at the time of full A LEI is required for each separate legal entity for who data will be submitted or retrieved for from the CME ETR. Users may acquire a LEI through one of the authorized LEI issuers listed at http://www.leiroc.org. A LEI obtained previously for a legal entity to satisfy other business purposes (including trade reporting in a different global jurisdiction) may be used in the CME ETR registration so long as the issuer is recognized on the LEI ROC website.

      CME Central Counterparty (CCP) LEI’s provided for reference:

Chicago Mercantile Exchange Inc. (US Clearing House)

CME LEI: SNZ2OJLFK8MNNCLQOF39 
CME UTI Namespace: 1010000023

2. Execute the CME Repository Services User Agreement (User Agreement or Service Provider Agreement)

User Agreement – Entered into by a party to a derivatives transaction; the Agreement enables the Registered User to (1) submit (2) analyse/filter (3) extract and (4) authorize their counterparty or service provider (not a party to the transaction) to view its derivative data stored in CME ETR. In order to execute the CME ETR User Agreement:

  • Download the agreement from the CME ETR website www.cmegroup.com/ETR. Complete the user agreement and click the send button to electronically submit the agreement (via the SUBMIT button at the form end) to the CME ETR Registration team.
  • The User Agreement will be received and processed by the CME ETR Registration. A notification of receipt of the submission is provided and a subsequent notification is sent when the registration has been completed. In the registration complete email, instructions are provided on how to contact the CME registration team to receive the login information over the phone (for security reasons). A required form as part of CME ETR Firms are required to specify at least one Verification Officer upon registration. The Verification Officer will act as the account administrator, approving any new requests or access modifications, etc. In addition to a Verification Officer regular Users can also be requested. Verification Officers have a choice of admin roles or view only roles. Admin roles allow users to upload, amend and view while a View Only role allows for read only access to the ETR.

Service Provider Agreement – Applies to entities which are not party to the trade and are providing services to facilitate the trade report in some capacity on behalf of one or both of the obligated counterparties to the reportable derivatives trade. Parties interested in a Service Provider registration should contact CME ETR at repository@cmegroup.com.

3. Validation of Reporting Party LEI

CME ETR validates all LEI fields where the Party Type is specified as LEI against an open source GLEIF centralized database, www.gleif.org
Records with values in the LEI field that fail validation (where the LEI value is not listed on the GLEIF centralized database) will be rejected by the CME ETR and will require parties to take action for resolution. ESMA requires all TRs to perform this validation as the industry moves towards improving data quality. Please contact the CME ETR support team with any follow up questions.

4. UI Access

Please visit https://etrui.cmegroup.com once access to the TR has been granted.

Additional User Access Requests

Once registered, accounts may authorize additional users to access the data (i.e. internal staff, fund administrators, other intra-group entities, etc. Please follow the instructions on the additional user access request form located at cmegroup.com/ETR.

Regulatory Authority Access

A Regulatory Authority wishing to gain access to CME ETR is required to contact CME ETR’s Regulatory Support at <GRS_Regulatory_Support@cmegroup.com>

Once the Regulatory Authority’s identity and level of access are confirmed by the CME Compliance Officer, the Regulatory Authority will be contacted to provide details on the persons who require access and their role per the Access levels below. Each person will receive a separate welcome email from CME ETR Registration which includes instructions on how they may obtain a username and password.

Access Levels

CME ETR Administrator:

  • Rights to create, modify and remove user accounts
  • Rights to view data for all accounts
  • Rights to upload data for all accounts
  • Rights to run all reports and download the results for all accounts

CME ETR Full Access:

  • Rights to view data for accounts
  • Rights to upload data for accounts
  • Rights to run all reports and download the results for accounts

CME ETR View Only Access:

  • Rights to view data for accounts

Trade Submissions to CME ETR

Reports may be submitted to CME ETR via the following methods:

Format

Transport

CSV File

Website upload

CSV File

HTTPS web services

CSV File

sFTP

 

What data is required to be submitted to CME ETR?

Please see the CME technical specification located at https://www.cmegroup.com/trading/global-repository-services/technical-documentation.html#etr.  The ESMA data field validation demonstrates all the applicable data fields to be submitted and the appropriate format. This table additionally states any validations applied to the data submitted in order to verify the accuracy of data submitted.

Unique Transaction Identifier (UTI)

A unique trade id also referred to as the UTI (Unique Transaction Identifier), is an identifier agreed by the counterparties to the trade, and provided by the reporting counterparty while reporting to a European Trade Repository. ESMA has stipulated the length of the field can be up to 52 characters. All reportable transactions will be assigned a transaction identifier and will conform to the UTI structure defined below.

The UTI is comprised of two fields.

  1. The namespace of the assigner or the Prefix
  2. The transaction identifier

For all (OTC and ETD) trades cleared by CME, the DCO will use the CFTC assigned namespace for the DCO. Trades cleared by CME Clearing Europe (CCE) will use the CCE MIC code with a prefix and suffix. The namespace will have a maximum length of 10 characters. The maximum length of the transaction identifier assigned by CCE or CME will be 32 characters.

  • Namespace/Prefix for Trades cleared at CME – 1010000023
  • Namespace/Prefix for Trades cleared at CCE – 000CMEC000

CCE and CME will assign a cleared UTI for all trades cleared by the respective clearing org. The cleared UTI will be used to meet any CCP reporting obligation under EMIR.

Differing clearing models between the US and European jurisdictions alter the number of UTI’s required to be generated.  Trades cleared by CCE will use the principal structure and the trades cleared by CME will assume an agency structure.

For principal model the clearing member acts as principal, the end-user will face the clearing member, and the clearing member will face the clearing house (here, there are two identical ‘back-to-back’ transactions among the three parties). All trades cleared by CCE will be reported under the principal clearing model. Under the principal model, the cleared UTI will correspond to the trade between the clearing member and CCE. In addition, a second UTI will be generated by CCE. This UTI corresponds to the trade between the clearing member and the client.

For agency the clearing member acts as an agent, the end user will face the clearing house directly. All trades cleared by CME will be reported under the agency clearing model. Under the agency model, the cleared UTI will correspond to the trade between the client and the CME. So no additional UTI will be assigned under the agency model.

For detailed trade scenario diagrams and assigning UTI for various clearing models please reference CME ETR website http://www.cmegroup.com/market-data/files/cce-and-cme-uti-assignment.pdf.


Unique Product Identifier (UPI)

In order to aid European clients in their EMIR Trade reporting requirements, CME ETR has published the attached table matrix. This table and subsequent schematic are in reference to the reporting of fields 1 to 4 and 21, 55 and 57 of the EMIR Regulator Technical Standards (RTS) Common Data Tables, pursuant to the reporting of product identification. In order to find the relevant Classification of Financial Instruments (CFI) code, please find these on the CME Group Product reference files located on the CME group Public FTP site: ftp.cmegroup.com/fprf. This is organised by clearing org, then by product exchange, then by date.

Another source for product codes and slate, CME website: http://www.cmegroup.com/trading/products/

For detailed usage of a UPI or its equivalent, refer to the CME technical specification located here.


Life
Cycle Events

High Level description of reporting the various Life Cycle events of a trade are below. Conceptually this process applies to all forms of submission.

  • New: To enter a new trade use the Action tag populated with value as “New” and Event tag as “New Trade” with other economics of the trade populated.
  • Modify: To modify or change any economics of the trade the Action tag needs to be populated with value “Amend” and Event tag as “Amendment” with all the details of the trade and the changed economic values.
  • Error: In case of error in entering the trade, it can be moved to a remove/invalid status by populating the Action tag as “Remove/Invalid” and the Event tag as “Cancellation” with the other details of the trade entered as is.
  • Cancel: In order to cancel an entered trade, the Action tag needs to be populated as “Terminate” and Event tag to be populated as “Cancellation” with other details of the trade entered as is.
  • Compression: To show compression of trades, enter the Action tag as “Terminate” and Event tag as “Full Netting/Partial Netting” for the UTIs that need to be compressed. All the other details of the trades have to be specified as in the “New trade” entry. In case of partial netting an additional trade entry is required to reflect the remnant trade. This will be entered with the Action tag as “New” and the Event tag as “Partial Netting” and the economics of the remnant trade.
  • Valuation : To enter valuation on a trade, the Action tag needs to be populated as “Valuation” and Event tag as “Valuation”.

Transport Overview

Web User Interface

Users or service providers may use the CME ETR secure web User Interface (UI) to upload CSV formatted files. On-screen confirmations are provided on acceptance or identify required corrective actions. Full documentation on this option (including the asset class specific CSV templates and samples) are available online.

Web Services

CME ETR allows programmatic submissions, cancellations, and amendments via secure https web services. This web service submission facilitates connection to the CME ETR via the internet, removing the need for any other type of connectivity infrastructure (such as MQ). CSV formatted data may be passed via this transport method. Full technical details are available below:

Authentication TokenRefer to Generate Authentication Token
Data Capture Generate

Contact repositorysupport@cmegroup.com

Importing Certificate in Local Java KeystoreRefer to Importing Certificate in Local Java Store
Submitting CSV Message FileRefer to CSV Specs here.


URLs

UAT/NR:

https://etrwsnr.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/FX
https://etrwsnr.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/CMDTY
https://etrwsnr.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/IRS
https://etrwsnr.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/CDS
https://etrwsnr.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/COLL
https://etrwsnr.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/EQUITY

PROD:

https://etrws.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/FX
https://etrws.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/CMDTY
https://etrws.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/IRS
https://etrws.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/CDS
https://etrws.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/COLL
https://etrws.cmegroup.com/cgrs-ws/dataCaptureService/submitCSV/EQUITY

SFTP

About SFTP                                                                                     

Secure File Transfer Protocol (SFTP), is a method of transferring data between to end points using strong encryption and authentication.  We utilize this to allow confidential and easy transfer of files between our clients and our CME Repositories. 

Getting Access to SFTP

New Client

For any client who wishes to use CME for their TR needs they will need to complete a User Agreement,  within this agreement they will be presented the below question to which you must select “Secure FTP CSV” (to note you can select as many methods as you like or specify none for view only access if someone is reporting on your behalf)

 Fig.1 Taken from ETR User Agreement

 Once all the onboarding is complete Client Services with provide your chosen Verification Officer the folder Username & Password.

Existing Client

Please have your Verification Officer reach out to  repositorysupport@cmegroup.com with your request to have an SFTP folder and then someone will reach back out to your Verification Officer with the folder Username & Password.  Note, if your firm has a pre-existing SFTP folder for other CME business services, another SFTP account will still need to be created specifically for your firms CME Repository submissions.


Technical Set-Up Information

CME supports file transfer through Secure FTP available via Wide Area Network connection as well as via the Internet. Please have your IT Staff facilitate the below connectivity and provide access through your firewall for our IPs as required.

SFTP via CME WAN connectivity

This requires firms to have direct access to the CME network via circuit.

Production IP: 167.204.41.33 (port 22)

Disaster Recovery: Same as Production IP address above.
CME will whitelist IP addresses connecting via this method. A gateway range will have been provided to a contact within your firm when direct circuit access to CME was established.
In the event of a DR situation, the failover will not require firms to switch access or manage additional entries to their firewall.

SFTP via Internet

Web based without a direct connection to CME.

 When using SFTP, SSH encrypted software is required for the connection.
CME does not require firms to enter the internet based SFTP IP address into their firewall to access the site. CME only require users to utilize an sftp tool and a valid CME provided SFTP account and password.

Environment

IP

DNS

Port

Production

164.74.122.33

sftpng.cmegroup.com

22

Disaster Recovery

204.10.15.24

sftpng.cmegroup.com

22

UAT (testing)

164.74.123.120

sftpcert.cmegroup.com

22

CME Public Key Installation

CME allows the use of public/private key authentication. (SSH Public Key File format RFC4716).  Firms who require the use of public keys are responsible for the installation themselves.

Please note:  Public key may not be required as it is dependant of the connection method you use

CME uses SSH Public Key File Format (RFC4716)

The location of your public key should be installed to: 
“YOUR_CME_SFTPNG_HOMEDIR”/.ssh/”USERNAME”

Example, where username is “USERNAME”:
sftp> ls .ssh
.ssh/USERNAME

If you already have an RFC4716 Public Key file yet installed at CME
Here’s the steps, you’ll need to update the Public Key named “USERNAME” at CME:

1. Sftp to the site
2. Run the command, sftp> get .ssh/”USERNAME” where “USERNAME” is your login name.
3. Append new key(s) to the Public key file.
4. Put the key file up, sftp> put .ssh/”USERNAME” where “USERNAME” is your login name.

If you don’t have an RFC4716 Public Key file yet installed at CME
Here are the steps, you’ll need to have the Public Key file named “USERNAME” which contains the keys in the local directory on your source host in order for these steps to work:

1. ssh-keygen –t rsa –b 2048 –f id_rsa –N ‘’ && ssh-keygen –e –f id_rsa > USERNAME
2. sftp to the site
3. Put the key file up, sftp> put .ssh/”USERNAME” where “USERNAME” is your login name.
    NIST expects that a 2048 key size will be secure until 2030
    (http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf). You can opt for 4096, but it is not required.
    More about RFC 4716 https://tools.ietf.org/html/rfc4716

CME SFTP Directory and Path Structure

Regardless how firms connect to their CME sftp account, there are 3 default directories that each firm is provided when their sftp account is added. Each folder is utilized for a specific purpose as outlined below including the directory path, note that 123 represents the firm’s sftp account ID:

cme/ftp/123/Incoming (with upper case I)
cme/ftp/123/Outgoing (with upper case O)
cme/ftp/123/PUB (all upper case)

When a user logs into their sftp account, the default maps to the user account root directory where the above 3 folders securely accessed by the account. Firms then can navigate between the folders and sub-folders based on their data upload or download requests.

Incoming: Used for confidential data files submitted by firms to CME. Firms will upload the required files to the Incoming directory as required by CME.
Outgoing: Used for confidential files that CME makes available for firms. Firms will be able to download files when they are ready to be retrieved.
PUB: Used for shared files that CME makes available for firms into specific sub-directories. Firms will be able to download files when they are ready to be retrieved from the sub-directories.

Submitting Files to SFTP

The folder will have two sections: Incoming and Outgoing. Files must be dropped for upload into the incoming section, and reports can be pulled from the outgoing section. There will be a response file in the outgoing file which is prefixed with ‘res_’ to the data file.  There is an acknowledgment for each file; if the data is successful the response file will simply contain ‘success’.  If there are errors the response file will be larger and will contain ‘error’ and give a detailed message explaining the failure.  Duplicate submitted records are rejected with an appropriate error message and for every 1 file submitted into incoming there will be 2 files in outgoing (the original file submitted and the results file).  Files dropped in the incoming folder to upload in the TR should be asset class specific.

  • All submitted files must be in .csv format.
  • All response files will be in .txt format.
File Naming Convention for CSV files

Each file submission must begin with the asset class prefix as shown below, then any free text is allowed to follow to help clients identify their submission activity more effectively.  E.g. trade, position, amendments, date etc.

<<AssetClass>>_<<Free Text>>.csv

Examples:

IRS_CLC01_NEWTRD_20190331183400.csv (for Interest Rates)
FX_CLC01_NEWTRD_20190331183400.csv (for FX)
CDS_CLC01_NEWTRD_20190331183400.csv (for Credit)
CMDT_CLC01_NEWTRD_20190331183400.csv (for Commodity)
EQUITY_CLC01_NEWTRD_20190331183400.csv (for Equity)
COLL_CLC01_NEWTRD_20190331183400.csv (for Collateral)

Data Access and Reports (Generic and Custom)

Additional Resources

See also: cmegroup.com/ETR

Generate Authentication Token

1. Login to https://ETRui.cmegroup.com with your CME Group Login ID and password
2. Navigate to Submit>Generate Token menu as shown in screen shot below:


3. Enter your username and password and click “Generate Token”. It should give you your authentication code for using web service in Token text field. You will have to use valid username and password which is authorized by CME Repository Support Group during Registration. (Make sure you have already changed the temporary password provided during registration. You can use https://ETRuinr.cmegroup.com/ETRui/ to change your temporary password. It will prompt you to change the password when you login first time)


4. You are ready to use this token for your web service client code to submit CSV messages to CME ETR. This token will be used as a value for http header name “Authorization” (Please refer to DataCaptureWSClient.java code ). 

Importing Certificate in Local Java Keystore


1. Open https://ETRws.cmegroup.com/datacapture-ws/ETR/submitCSV/CMDTY URL in IE.
2. Click on Lock image and click on View Certificate. You will see following dialog box

3. Open Certificate Path Tab and select VeriSign as shown in image below.

4. Select Details tab and click “Copy to File” and Click Next 


5. Select first format option of “DER encoded binary X.509 (.CER) on “Certificate Export Wizard” dialog and click Next as shown in below screen shot 

6. Specify file name and local path to store the certificate on your local machine (e.g C:/ETRwsnr.cer)
7. Click Next and Finish. It will save the certificate locally on your machine in C:/etrwsnr.cer file which we will import to your local java keystore. 
8. Open DOS command window
9. Type following command at DOS prompt to create and import the certificate in local keystore.

keytool -import -trustcacerts -alias root -file c:/etrwsnr.cer -keystore c:/ETRwsnr.jks
Hit Enter Key

10. It will prompt you for password for your keystore. Enter any password which you will be passing later to your Web Service client along with path to the keystore you will be creating (e.g password “trwsnrclient”). Hit enter key. Retype same password and hit enter key again. 
11. Type “yes” for Trust this certificate? [no]. Hit enter key. You should see last line as “Certificate was added to keystore” as shown in following screen shot. 

FAQs

1. Do I get a username for each person who wants to access to sFTP folder?

No, only one username is provided for the entire folder. This can be disseminated by the Verification Officer at their discretion

2. My Verification Officer has left the company, how do we assign a new one?

Please reach out to repositorysupport@cmegroup.com so that they can provide you the most up to date documentation to allow a new Verification Officer to be assigned in the absence of a previously appointed Verification Officer/

 3. How do I log into UAT/Testing environment?

You will use the same Username and password, but you will need to use the following Host:
sftpcert.cmegroup.com

 4. Why has our submitted file not moved from our firms ‘Incoming’ folder? 

Files and the resulting records in our SFTP directories will be processed in First in, First out (FIFO) order. The time of submission will determine file order written to the CME server. It is not uncommon for files to remain unprocessed for several hours during busy periods when there are lengthier file queues but if you have any concerns about how long your file has been unprocessed, please contact: repositorysupport@cmegroup.com

Contact Information

ETR Business Team - repository@cmegroup.com

ETR Support Team - repositorysupport@cmegroup.com
Chicago +1 312 580 5352
London +44 (0) 203 379 3180
Singapore +65 6593 5592

ETR Hours of Operation - CME ETR service is available to client’s twenty four hours a day starting Sunday 1100 hrs and ending Saturday 0600 hrs (GMT). Please note this does not allow for British Summer Time changes.

CME ETR website address - http://cmegroup.com/etr

CME ETR New Release (Test) website address - https://etruinr.cmegroup.com/etrui/

  • No labels