Central Matching Service User Guide

Central Matching Service User Guide
Central Matching Service
User Guide
Version: 1.13
Date:
27 April 2015
Table of Contents
Table of Contents .............................................................................................. 2
1.
1.1.
About This Document ............................................................................ 6
Scope ....................................................................................................... 6
1.2.
Chapter Overview ..................................................................................... 6
1.3.
Glossary of Terms .................................................................................... 6
2.
2.1.
Introduction ............................................................................................ 7
CMS Overview ......................................................................................... 7
2.2.
Electronic Confirmation Matching ............................................................. 8
2.2.1.
Physicals ........................................................................................... 8
2.2.2.
Financials .......................................................................................... 8
2.3.
CMS eCM Process ................................................................................... 9
2.4.
CMS eRR Process ................................................................................. 10
2.5.
CMS eXRP Process ............................................................................... 11
2.5.1.
Clearing in eXRP ............................................................................. 11
2.5.2.
Current Scope of eXRP ................................................................... 12
2.5.3.
The UMTF Process ......................................................................... 12
3.
3.1.
Using the CMS ...................................................................................... 13
Accessing the CMS interface.................................................................. 13
3.2.
The First Login ....................................................................................... 13
3.3.
The Welcome Page ................................................................................ 14
3.4.
User Roles ............................................................................................. 15
4.
4.1.
The eCM Menu ...................................................................................... 15
Trader Dashboard .................................................................................. 17
4.2.
Broker Dashboard .................................................................................. 17
4.3.
Results Detail ......................................................................................... 18
4.4.
eCM Deal Finder .................................................................................... 20
4.4.1.
Filters .............................................................................................. 20
4.4.2.
Auto-Populated Filters ..................................................................... 21
4.4.3.
My Filters......................................................................................... 22
4.5.
Interactive Icons within the eCM Tab ...................................................... 23
4.5.1.
Document Page............................................................................... 23
4.5.2.
Audit Trail ........................................................................................ 23
4.5.3.
Notes............................................................................................... 26
4.5.4.
Exporting Documents ...................................................................... 27
4.5.5.
Near Matching ................................................................................. 29
4.5.6.
Hide Indicator (MO Only) ................................................................. 31
Central Matching Service User Guide v1.13
Page 2 of 95
4.5.7.
Manual Terminate (MO Only) .......................................................... 33
5.
5.1.
eCM lite Menu ....................................................................................... 35
Enter Trade ............................................................................................ 35
5.2.
Amending a Trade .................................................................................. 37
5.3.
Cancelling a Trade ................................................................................. 38
5.4.
eCM lite Dashboard ................................................................................ 39
5.5.
eCM lite Deal Finder ............................................................................... 39
5.6.
Auto-Populated Filters ............................................................................ 41
5.7.
My Filters................................................................................................ 41
5.8.
Interactive Icons within the eCM lite Tab ................................................ 42
5.8.1.
Document Page............................................................................... 42
5.8.2.
Audit Trail ........................................................................................ 43
5.8.3.
Notes............................................................................................... 44
5.9.
Exporting Documents ............................................................................. 46
5.10.
Near Matching .................................................................................... 47
5.11.
Hide Indicator (MO Only) .................................................................... 49
5.12.
Manual Terminate (MO Only) .............................................................. 51
6.
6.1.
eCM Settings......................................................................................... 52
eCM 4.0 Process .................................................................................... 52
6.2.
Box Result Messages ............................................................................. 54
6.3.
Broker Restrictions (MO Only) ................................................................ 54
6.4.
Column Order ......................................................................................... 55
6.5.
Holiday Calendar .................................................................................... 56
6.6.
Products (MO Only) ................................................................................ 57
7.
7.1.
The eRR Menu ...................................................................................... 61
eRR GUI................................................................................................. 61
7.2.
eRR Dashboard...................................................................................... 61
7.3.
eRR Deal Finder..................................................................................... 62
7.3.1.
Filters .............................................................................................. 63
7.3.2.
Interactive Icons within the eRR Tab ............................................... 63
7.3.3.
eRR Deal Finder Export .................................................................. 65
7.4.
Standing Instructions .............................................................................. 66
7.4.1.
Add or Edit Instruction ..................................................................... 67
7.5.
eRR Reconciliation ................................................................................. 69
7.6.
Retry Queue ........................................................................................... 72
8.
8.1.
The eXRP Menu .................................................................................... 72
eXRP Dashboard ................................................................................... 73
8.1.1.
Filters and Refresh .......................................................................... 73
Central Matching Service User Guide v1.13
Page 3 of 95
8.1.2.
Columns: Update Time .................................................................... 74
8.1.3.
Rows: Clearing State ....................................................................... 74
8.2.
eXRP Deal Finder .................................................................................. 75
8.2.1.
Searching for Reference Numbers .................................................. 76
8.2.2.
Searching by General Properties ..................................................... 76
8.3.
eXRP Deal List ....................................................................................... 76
8.3.1.
Information in the List ...................................................................... 77
8.3.2.
Interactive Icons for Manual Actions / Document Details ................. 78
8.3.3.
Document Detail Views ................................................................... 78
8.3.4.
Exporting and Adapting a List of Transactions ................................. 79
9.
9.1.
Preferences ........................................................................................... 80
Account .................................................................................................. 80
9.2.
Change Password .................................................................................. 81
9.3.
Mail Alerts .............................................................................................. 82
9.3.1.
Global Mail Alert Settings (UA Only) ................................................ 82
9.3.2.
eCM Mail Alert Settings (MO Only) .................................................. 82
9.3.3.
eXRP Mail Alert Settings ................................................................. 83
9.3.4.
Alerts for Broker (UMTF) Organisations........................................... 83
9.3.5.
Alerts for CRA Organisations........................................................... 84
10.
Administration ...................................................................................... 84
10.1.
Organisations...................................................................................... 84
10.1.1.
Amend an Existing Organisation .................................................. 85
10.1.2.
Creating a New Organisation ....................................................... 86
10.2.
User Accounts .................................................................................... 86
10.2.1.
Add User Account ........................................................................ 87
10.3.
User Permissions ................................................................................ 88
10.4.
Assign User Roles .............................................................................. 89
11.
Help ....................................................................................................... 91
11.1.
Contacts ............................................................................................. 91
11.2.
Support ............................................................................................... 92
12.
Further Documentation and Downloads ............................................. 93
12.1.
EFET Website..................................................................................... 93
12.2.
ENTSOe Website................................................................................ 93
12.3.
Support Team Help Desk Tool ............................................................ 93
13.
Appendix 1 – Offline reports ................................................................ 93
13.1.
Billing Details Report........................................................................... 93
13.2.
Matched Product Matrix ...................................................................... 94
13.3.
Billing Report Statistics ....................................................................... 94
Central Matching Service User Guide v1.13
Page 4 of 95
Central Matching Service User Guide v1.13
Page 5 of 95
1. About This Document
1.1. Scope
This document is intended for users of the EFETnet Central Matching Service (CMS).
Outlined in the following chapters is a step by step guide on how to operate the CMS;
electronic confirmation matching (eCM and eCM lite), electronic regulatory reporting (eRR)
and electronic exchange-related processing (eXRP). Also included is an overview of the
concepts behind the system, the processes involved, and how to access support for issues
encountered when using the CMS.
1.2. Chapter Overview
Outline of the following chapters:
Introduction: provides an overview of the CMS and its services
Using the CMS: introduces fundamental user interface concepts
The eCM Menu: details user interface features for eCM
eCM Settings: provides information on changeable settings
The eRR Menu: details user interface features for eRR
The eXRP Menu: details user interface features for eXRP
Preferences: describes user-specific customisation features
Administration: describes the interface for the User Administrator (UA) role
Help: details the ways to contact the CMS Service Team
Further Documentation and Downloads: provides a detailed list of links to other useful
resources
1.3. Glossary of Terms
Term
ACK
BCN
BFI
BMN
BR
BRS
CA
CAN
CMS
CMTF
CNF
CP
CRA
CRQ
CRP
Description
Acknowledgement
Broker Confirmation
Broker Fee Information
Broker Match Notification
Broker
Box Result
Clearing Agent (= clearing house)
Cancellation
Central Matching Service
Cleared Multilateral Trading Facility
Trade Confirmation
Counterparty
Clearing Registration Agent
Clearing Request document
Clearing Response document
Central Matching Service User Guide v1.13
Page 6 of 95
eCM
ebXML
eXRP
EFET
EIC
ETRM
EU
FHA
MO
MSU
MSA
MSR
OP
OTC
P2P
REJ
TUR
UA
USI
UMTF
XBN
XML
electronic Confirmation Matching
electronic Business (eb), using eXtensible Markup Language (XML)
electronic eXchange Related Processes
European Federation of Energy Traders
Energy Identification Code
Electronic Trading and Risk Management
European Union
Functional Hub Admin (Service Team administrator role)
Master Operator
Match Suggestion
Match Suggestion Acceptance
Match Suggestion Rejection
Operator
Over the Counter
Peer-to-peer
Rejection
Tear-Up Request
User Administrator
Unique Swap Identifier
Uncleared Multilateral Trading Facility
eXRP Broker confirmation document, clearing submission format for brokers
eXtensible Markup Language
2. Introduction
2.1. CMS Overview
EFETnet Central Matching Services (CMS) is a central platform offering straight through
processing to energy trading companies.
The EFETnet CMS provides a single interface to all EFETnet products and services, acting
as a common gateway to market participants (traders). EFETnet offers a secure, reliable
infrastructure with a dedicated Service Team to monitor performance and manage and
resolve issues.
The CMS currently delivers the following EFET processes: eCM, eCM lite, eXRP and eRR.
It is a software component developed by Ponton Consulting GmbH, which is fully extendable
to enable the package to include further developments and updates. CMS uses the ebXML
Message Service, via Ponton X/P, for secure and reliable communication between clients
and the service.
The CMS is located at the URL:
Production: https://www.cms.efetnet.org
UAT https://www.cms-test.efetnet.org/login
Central Matching Service User Guide v1.13
Page 7 of 95
The service is only accessible for registered CMS users from approved access points. To
register as a CMS user please contact a User Administrator (UA) or the CMS Service Team.
2.2. Electronic Confirmation Matching
Electronic Confirmation Matching (eCM and eCM lite) is a process in which trade
confirmations are exchanged and matched electronically between trading partners and/or
brokers. This is standardised to eradicate errors and manage risk when matching contracts.
The EFET eCM Standards v4.2 describes the process of eCM:
A trade is carried out between traders or through the help of a broker. Once the transaction
has been executed, each respective information system is updated with the trade data.
Each information system then transmits a confirmation document through the eCM process
which conducts the matching in order to reconcile any differences between the independent
records of the trade data. Any exceptions resulting from the matching process are manually
resolved
Version 4.0 of the eCM Standards centralised confirmation matching is included, and is
backwardly compatible with versions 3.3 and 3.2.
The CMS performs electronic confirmation matching (eCM) for over the counter (OTC)
confirmations as defined in the eCM 4.0 standard which supports:
2.2.1. Physicals
1. Physical instruments
a. "FOR": physical forward that settles against a fixed price
b. "OPT": option on a physical forward
c. "PHYS_INX": physical forward that settles against an index
d. "OPT_PHYS_INX": option on a physical forward that settles against an index
2. Physical Commodities
a. Gas, Power, Coal
b. Emission allowances (EUAPhase_1, EUAPhase_2, EUAPhase_3, CER)
2.2.2. Financials
1. Financial instrument types:
a. "FXD_SWP": fixed/float swap
b. "FLT_SWP": float/float swap
c. "OPT_FXD_SWP": fixed/float swaption
d. "OPT_FLT_SWP": float/float swaption
e. "OPT_FIN_INX": option on an index
2. Commodities for financials:
a. Agricultural products (Canola, Cocoa, Coffee, Corn, Cotton, Livestock, Milk, Oats,
Orange Juice, Rubber, Soya beans, Sugar, Sunflower Seeds, Wheat, Wool)
b. Energy products (Benzene, Coal, Diesel Fuel, Electricity, Fuel Oil, Gas Oil,
Gasoline, Heating Oil, Jet Fuel, Methanol, Naphtha, Nat Gas, Nat Gas Liquids,
Oil, Ultra Low Sulphur Diesel)
c. Emissions (EUA, CER)
d. Time Charter
Central Matching Service User Guide v1.13
Page 8 of 95
e. Freight (Wet Freight, Dry Freight)
f. Metals (Aluminium, Copper, Gold, Lead, Nickel, Palladium, Platinum, Silver,
Steel, Tin, Zinc)
All EFET Standards are freely available from the EFET website http://www.efet.org in the
"Standardisation" tab.
2.3. CMS eCM Process
The eCM process provides traders and brokers with the following matching capabilities:



Counterparty Confirmation Matching: the bilateral matching of electronic confirmation
documents (CNFs) between two trading counterparties.
Broker Confirmation Matching: the independent bilateral matching of trader and broker
confirmations and optionally Broker Fee Information (BFI) documents between one
broker and trader.
Trilateral Confirmation Matching: the cross matching between a trader's confirmation
(CNF) and optionally Broker Fee Information (BFI) document(s) with the counterparty's
Confirmation (CNF) and the broker's confirmation document (BCN).
In eCM, both trading parties submit a CNF to the CMS from their ETRM (Energy Trading and
Risk Management) system. If a broker is involved in the trade, a BFI will also be sent with
the CNF. Successfully submitted documents are assigned to a 'Pending' state and become
subject to the matching dialogue. Documents submitted to CMS that fail validation are
rejected and returned with an error message to the X/P Messenger. If a broker is involved in
a trade, they will submit a BCN to CMS, which is a combination of trade details and agreed
broker fees.
In eCM lite, both trading parties enter a trade confirmation directly into the CMS GUI.
Successfully entered trade confirmations are assigned to a 'Pending' state and become
subject to the matching dialogue. Confirmations which are entered incorrectly are subject to
an on screen error message. eCM lite confirmation matching is only between traders and
does not include brokers.
CMS is an implementation of the 'multi-tenancy' approach described in the eCM v4.2 eCM
Standards, simplifying the matching dialogue.
Figure 1 Document Process
Central Matching Service User Guide v1.13
Page 9 of 95
2.4. CMS eRR Process
electronic Regulatory Reporting (eRR) is the EFETnet implementation of the EFET eRR
Standard. eRR is a reporting format and method which is independent of the reporting
regime and destination of the data.
eRR simplifies the regulatory process for reporting entities by utilising a single data format
independent of the destination of the report. The use of a single data format also enables
users to change Trade Repositories depending on their business strategy, with no changes
required to the process or the interface.
As of February 2014, eRR supported Commodities reporting under ODRF and Dodd-Frank
in the US, and Commodities, Foreign Exchange and Interest Rates under EMIR in Europe.
It will soon be extended to facilitate REMIT reporting in line with ACER’s implementation
plans.
Figure 2 eRR Process
eRR Standard
The purpose of the eRR Standard is to facilitate automation of an electronic regulatory
reporting process in response to the introduction of EMIR and REMIT reporting regulations
in European commodity markets and related asset classes. The eRR Standard defines the
process and message choreography for notifying regulatory databases of a new trade, and
any further life cycle events.
http://www.efet.org
CpML
The CpML Data Standard is used to define eRR process documents, enabling organisations
to use a single CpML message to report any eligible transaction under EMIR and/or REMIT.
The CpML standard describes the message content and structure for documents submitted
to eRR.
http://www.efet.org
CNF
For eRR, the payload document within the CpML reporting message is a CNF (Trade
Confirmation) document. The content and structure of the CNF is defined in the EFET eCM
Central Matching Service User Guide v1.13
Page 10 of 95
Standards, identifying key fields and informational fields required to describe the commercial
details of an individual trade.
EFET eCM Standard:
http://www.efet.org/Cms_Data/Contents/EFET/Media/Documents/Public%20%20Standardisation/EFET%20ECM_v_4.0.1_final.doc
CpML submissions to eRR will be subject to validation against the eRR Standard, and the
payload data (in the CNF) will be subject to validation against the eCM Standards.
To join eRR, an organisation should contact the EFETnet Service Team with their request.
New joiners will be asked for various data on joining, such as business and connection
details for the Organisation wishing to report under EMIR and/or REMIT via eRR in CMS.
A new joiner should also list all entities which they wish to report for, including third party
entities which they wish to report on behalf of. The EFET eRR Standard enable agent based
reporting by defining roles for market participants. This is further detailed in the CMS eRR
Agent Reporting paper.
2.5. CMS eXRP Process
eXRP streamlines, standardises and automates the flow of trade and trade related data
between traders, brokers, exchanges, clearing houses and clearing banks. It also enables
an organisation to monitor the clearing process through the eXRP GUI, supported by
automated email alerts informing all concerned parties of key events during the clearing
process.
2.5.1. Clearing in eXRP
Traders and (non-clearing) brokers are the initiators of clearing transactions and the
receivers of clearing results. They submit standardised documents to the CMS and receive
standardised feedback documents with the results.
Clearing Agents (CAs) / clearing houses are the receivers of clearing requests, facilitated
by Clearing Registration Agents (CRAs) interacting with CMS by means of document
exchange.
As indicated in the diagram below, a CRA can support multiple CAs, and reversely, a CA
can have multiple CRAs. Also, some CAs may not use other legal entities as registration
agents, in which case the CRA and CA are the same organisation.
Central Matching Service User Guide v1.13
Page 11 of 95
Figure 3 eXRP Process
2.5.2. Current Scope of eXRP
eXRP recognises 3 classes of clearable trades:
 UMTF (uncleared multilateral trading facility): this applies to trades executed through
non-clearing brokers with clearing requests issued by eXRP based on broker
submissions.
 CMTF (cleared multilateral trading facility): this applies to trades executed on an
exchange platform and cleared via that platform (outside of eXRP). In this instance
eXRP acts as a status reporting service from the exchange platform, notifying
participants about the clearing results.
 Bilateral: This is for non-brokered trades, with registration being initiated by trader
submission.
The current eXRP release supports UMTF trades. CMTF and Bilateral trade submissions are
subject to on-going specification work and will be included in a future release.
2.5.3. The UMTF Process
The UMTF process standardises clearing for brokered deals as follows:
1. A Broker submits a trade after execution (XBN = eXRP broker confirmation)
2. CMS eXRP routes a standard clearing request (CRQ) to the CRA
3. The CRA validates the agreements/limits and opens a clearing transaction in the CA's
clearing system. The outcome is reported back as a clearing response (CRP)
4. eXRP notifies the broker of the clearing outcome with a Box Result (BRS). The broker
can then amend / resubmit in the case of a refusal.
Central Matching Service User Guide v1.13
Page 12 of 95
Figure 4 UTMF Process
3. Using the CMS
3.1. Accessing the CMS interface
The CMS is accessible through a web browser at: https://www.cms.efetnet.org
Enter the user name and password provided by the User Administrator (UA) for the
organisation. The CMS URL will need to be accessed from an approved IP range for the
organisation.
3.2. The First Login
After using the one-time password from the UA, a permanent password will need to be set
by the user. The user will also be directed to this page if their current password has expired
or has been reset by the UA.
Central Matching Service User Guide v1.13
Page 13 of 95
Figure 5 First Login
3.3. The Welcome Page
After successful login to CMS, users will see the Welcome Page, as below:
Figure 6 CMS Welcome Screen
The basic screen layout of the CMS user consists of:
 The title bar at the top:
o CMS (UAT) / CMS (Live) system indication
o User name
o Organisation selector (for organisation group with multiple legal entities, including
the corresponding EIC code)
o Logout button
 The navigation bar on the left
The Welcome Screen shows:
 Welcome message including the user's full name
 Date when the user's password will expire, and direction to change it
 Date and time of the user's last log-in
 Version number of CMS software
Central Matching Service User Guide v1.13
Page 14 of 95

Important information regarding CMS
The CMS navigation bar includes (depending on the user's organisation and user role):
 eCM – Dashboard, Deal Finder, settings for eCM users
 eRR – Dashboard, Deal Finder, Standing Instructions, Reconciliation
 eXRP – Dashboard, Deal Finder for eXRP users
 Preferences – the user's account/password settings, the user's mail alert subscriptions
 Administration – organisation and user account maintenance for user administrators of
the user's organisation
 Help – help desk contact addresses, service announcements, user contact directory,
release notes
3.4. User Roles
Users are categorised according to permission levels within the system. As a result, certain
screens will be accessible depending on the role(s) to which the user has been assigned:
 OP – (standard) Operator
Operators are allowed to access trade data in CMS
 MO – Master Operator
Master Operators have all Operator rights and, in addition, access to privileged functions
such as:
o (eCM) tools to change eCM process settings for their organisation
o (eRR) tools to add Standing Instructions for their organisation
o (eXRP) the ability to decide which users receive which email alerts from the
CMS
o (eXRP / brokers only) to option to manually declare failed clearing transactions
"ABORTED" and thus mark them as non-actionable
 UA – User Administrator
User administrators maintain access rights for users within their Organisation Group, for
example, they can add/disable users, reset passwords, amend user details and
configure an individual’s user roles.
4. The eCM Menu
The eCM menu allows a user to navigate to eCM-related trade data and configuration
functions. These are:
 Dashboard – access the confirmation status matrix → see eCM Settings
 Deal Finder – search for confirmations using specific confirmation details, such as Trade
ID, Trade Date, Counterparty, Commodity etc. → see eCM Deal Finder
 Settings – view and change eCM-related to organisation settings → see eCM Settings
The eCM Dashboard displays confirmations in progress, with issues, and completed. These
can be viewed by:
 Trade Date – date the trade was agreed
 Submission Date – date the trade confirmation was submitted to CMS
Central Matching Service User Guide v1.13
Page 15 of 95
Figure 7 Dashboard View
Users can refine the displayed trade confirmations further by using the following filters:
 Counterparty (EIC code of trader organisation)
 Broker (Broker code of broker organisation)
 Transaction Type (FOR, FXD_SWP etc.)
 Commodity (Gas, Power etc.)
 Market (country code)
 Hidden (exclude / include / show only hidden confirmations)
Details on how to operate the filters can be found in the section ‘Deal Finder’. Confirmations
are viewed and categorised by age:
 Today – confirmations agreed today or submitted today
 Before Today – confirmations with a trade date older than 1 day or submitted more than
1 day ago
 1 – confirmations agreed or submitted 1 day ago only
 2 – confirmations agreed or submitted 2 days ago only
 3 – confirmations agreed or submitted 3 days ago only
 4-7 – confirmations agreed or submitted 4-7 days ago only
 8-30 – confirmations agreed or submitted 8-30 days ago only
 31+ – confirmations agreed or submitted more than 31 days ago
"Time Out processing was removed in Standards V4.0, in favour of implementation specific
reports highlighting 'aged' documents that have not progressed to a resolved state."
Confirmations are expected to match within 3 business days. If confirmations do not match
within 3 business days, further investigation may be necessary in order to ascertain why,
and whether further action is required (e.g. discrepancy over trade data or the counterparty
hasn't uploaded their side of the confirmation).
The eCM Dashboard section of the CMS
displays three sections: In Progress, Issue
and Complete.
Sub-categories within these sections may
differ depending on whether the organisation
is a trader or a broker.
Central Matching Service User Guide v1.13
Figure 8 Dashboard Sections
Page 16 of 95
4.1. Trader Dashboard
1. In Progress –Deals which have been well processed, but have not matched yet. All
confirmations within this section are in state "Pending" with the counterparty and can
match, be amended, or be cancelled. 'In progress' deals are split into four categories:
a. Pending (CP) – confirmations submitted by the user's organisation which are
awaiting the matching CNF
b. Alleged (CP) – confirmations alleged to the user's organisation by a counterparty
awaiting a matching CNF.
c. Pending (BR) – confirmations the user's organisation has submitted which are
awaiting a matching BCN.
d. Alleged (BR) – broker confirmations which have been alleged to the user's
organisation, awaiting a matching trade document (CNF and/or BFI).
2. Issue – Confirmations in the ’Issue’ tab cannot match in the CMS without corrective
action. These issues are split into four categories:
a. Error – confirmations which were in the matching process with a peer-to-peer
counterparty but have experienced issues (e.g. match suggestion received for a
timed out confirmation).
b. Failed – confirmations which were sent to the CMS but do not comply with the
EFET eCM Standards (e.g. Missing “DeliveryPointArea”).
c. Receiving – A transitory state for the sending/receiving of CNF/BCN Documents.
d. Matching – A transitory state for the sending/receiving of MSU/MSA Documents.
Business Note
'Receiving' and 'Matching' should be transitory states, and it is expected that
confirmations should leave this state within 4 business hours. If any confirmations are in
a transitory state for an excess of 4 business hours then it is likely there is an issue
processing the CNF.
3. Complete – Deals which have Matched or have been Cancelled. These are split into five
categories
a. Matched – The confirmation has Matched completely with the counterparty
(bilateral)
b. Matched (BR) – The confirmation has matched completely with the Broker
c. Preliminary Matched (BR) – The confirmation is Pending with the counterparty,
and has matched with the broker. The confirmation will remain in a ‘Preliminary
Matched’ state until the counterparty match completes.
d. Cancelled – The confirmation has been Cancelled.
e. Terminated - The confirmation has been terminated and is not eligible for
matching. By submitting an amendment, with a higher version number, an
organisation can return the trade confirmation to a 'Pending' state, from which it is
eligible to match.
4.2. Broker Dashboard
The Broker Dashboard, available to users of a broker organisation, contains three tabs.
These are:
1. In Progress – Shows all ‘Pending’ confirmations which are yet to match in CMS. These
are split into two categories:
Central Matching Service User Guide v1.13
Page 17 of 95
a. Pending – confirmations a broker organisation has submitted which are waiting
to match with the trader organisation’s CNF and optional broker fee information
(BFI).
b. Alleged – confirmations alleged to a broker organisation by a trader organisation.
2. Issue – Shows all confirmations which are unable to match in CMS and require
corrective action. These are split into four categories:
a. Error – confirmations in the matching process which experienced issues (e.g.
Match suggestion received for a timed out confirmation).
b. Failed – confirmations which were sent to CMS that do not comply with the EFET
eCM Standards (e.g. Missing "DeliveryPointArea").
c. Receiving – A transitory state for the sending/receiving of CNF/BCN Documents.
d. Matching – A transitory state for the sending/receiving of MSU/MSA Documents.
Business Note
'Receiving' and 'Matching' should be transitory states, and it is expected that
confirmations should leave this state within 4 business hours. If any confirmations are in
a transitory state for in excess of 4 business hours then it is likely there is an issue
processing the BCN with an acknowledgement not being sent or received correctly.
3. Complete – Deals which have Matched or been Cancelled. These are split into four
categories:
a. Matched – The confirmation has Matched in CMS eCM and is a final state.
b. Preliminary Matched (BR) – The confirmation is Pending with the counterparty,
and has matched with the broker. The confirmation will remain in a ‘Preliminary
Matched’ state until the counterparty match completes
c. Cancelled – The confirmation has been Cancelled.
d. Terminated – The confirmation has been Terminated, and is not eligible for
matching. By submitting an amendment, with a higher version number, an
organisation can return the trade to a ‘Pending’ state, from which it will be eligible
to match.
4.3. Results Detail
To view results in greater detail, select the desired category in the Dashboard e.g. 'In
Progress' – 'Total Pending (CP)' to display the details of all pending confirmations.
Central Matching Service User Guide v1.13
Page 18 of 95
Figure 9 Results View
This detailed trade display replicates the filters available in the Dashboard (eCM Menu
section). Additionally, the user is able to choose how many entries are displayed (up to 100
per page), and to export confirmation data to excel (more information in section Exporting
Documents ).
Other interactive icons in the dashboard include:
 Column Headings – Selecting the column label (e.g. Counterparty) will sort the column
result set, ascending or descending.
 Document Page – Displays the confirmation document in HTML format. (See section
Document Page).
 Audit Trail – Displays the flow of technical information to and from the CMS for a
confirmation document, e.g. the receipt of an amendment (See section Audit Trail).
 Notes – Allows an organisation to post and view messages on a confirmation document.
Other CMS organisations party to the trade will also be able to see any notes added.
(See section Notes).
 Export – Allows an organisation to export confirmations into an excel document (See
section Exporting Documents).
 Counterparty Near Match Icon – Allows an organisation to view any counterparty near
matches (See section Near Matching).
 Broker Near Match Icon – Allows an organisation to view any broker near matches
(See section Near Matching).
 Hide – Allows Master Operators to mark unfinished (PENDING/ERROR/FAILED)
confirmations as "hidden" and suppress their display in the GUI (See section Hide
Indicator).
These are described in detail in section Interactive Icons
Central Matching Service User Guide v1.13
Page 19 of 95
4.4. eCM Deal Finder
The Deal Finder allows a user to search for specific confirmations within an organisation.
Figure 10 Deal Finder
4.4.1. Filters
The Deal Finder offers the same filters as the Dashboard, as well as additional filters
including:











Our Trade ID –Trade ID for an organisation (up to 50 ID’s can be entered; these can be
copied and pasted from another source).
Their Trade ID –Trade ID for the counterparty or broker involved in the trade (up to 50
ID’s can be entered; may be copied and pasted from another source).
Document ID / USI / UTI – Document ID, USI or UTI relating to any confirmation from
either counterparty involved in the trade (up to 50 ID’s can be entered; these can be
copied and pasted from another source).
Trade Confirmations Not Found - Our Trade ID, Their Trade ID or Document/UTI/USI
IDs not found during a search in the eCM Deal Finder will be shown in a warning
message. Multiple IDs not found, a warning sign is displayed and can be expanded to
show the list of IDs.A single ID not found, will be displayed by the warning symbol. If
multiple IDs are not found then a user can expand the details by selecting ‘Show’.
Price – Specific price of the trade can be searched for.
Sender – Us or Them – confirmations sent by the user’s organisation, or by the
counterparty/broker.
Hidden – Choose whether to view Hidden confirmations (default is exclude)
Trade Date Range – Select the range of trade dates (Trade Date refers to the date the
trade was booked).
Submission Date Range – Select the range of submission dates (Submission Date
refers to the date the confirmation was submitted to CMS).
Delivery Start – Select the date when the delivery begins.
Delivery End – Select the date when the delivery ends.
Central Matching Service User Guide v1.13
Page 20 of 95
The date filters can be used to select
particular dates by selecting the green
calendar icon. The supported date format is
“DD/MM/YYYY” (DD=Day/two digits,
MM=Month/two digits,
YYYY=Year/four digits), for example
12/09/2011 for 12 September 2011. The date
filter is only available in this view.
A date picker control is provided to facilitate
the input of the date.
This control resembles a calendar and will
insert the appropriate date into the date fields
for the day selected in the date picker. To
open the date picker, click the calendar icon
to the right of the filter.
Figure 11 Date Picker
There is also the option to select a date
range on the blue calendar icon (shown
right).
The same date format is supported as with
the previous calendar icon, however the user
is offered preselected date ranges, and
search options.
Figure 12 Date Range Selector
Business Note
If no Submission Date is selected the Submission Date range automatically populates to
show the last 20 days.
4.4.2. Auto-Populated Filters
Filter options will only contain information relevant to the user’s organisation. For example, if
an organisation does not confirm Power trades, then Power will not be available in the
Commodity filter drop down list. The list is generated at the time of log in for each user,
based on all submissions made in the previous 90 days. It is also possible to select multiple
fields within each filter by using the check boxes in the drop down box. Filters that
automatically populate include:
Central Matching Service User Guide v1.13
Page 21 of 95





Counterparty – Filter by Counterparty EIC Code.
Broker – Filter by Broker Code.
Transaction Type – Filter by Transaction Type (e.g. FOR, OPT etc.)
Commodity – Filter by Commodity Type (e.g. Power, Gas etc.)
Market – Filter by geographical location of the market an organisation is trading in (e.g.
FR for France)
4.4.3. My Filters
A user can save searches using the “My Filters” button. This is available on all Dashboard
and Deal Finder screens. To save a search, first select the fields to filter. For example if a
user wishes to view confirmations for ‘11XTST-CHARLIE-1’, they would select only this
counterparty in the Counterparty drop down list and click ‘OK’. To save this filter, click ‘My
Filters’ > ‘Save Current’. If a filter already exists, the ‘Save’ functionality will be unavailable.
Figure 13 Saving a Filter
This opens up a new window, where a name for the filter must be entered which can extend
to 31 characters; e.g. ‘TST Charlie’. By selecting ‘Save As’ the filter will be saved. To replace
an existing filter, there is the ability to select a filter in the drop down, then click ‘Replace’. To
set a search as the default search in the Deal Finder, tick the ‘Use as default’ check box.
Once a filter is saved it will appear in the ‘My Filters’ drop down list. Date Range, Price and
Sender are not included within the saved filter.
Figure 14 Naming a Filter
To delete a filter, the user should select ‘Manage Filters’ in the ‘My Filters’ drop down. This
presents a screen which allows the user to select and delete saved filters.
Central Matching Service User Guide v1.13
Page 22 of 95
Figure 15 Managing Saved Filters
4.5. Interactive Icons within the eCM Tab
4.5.1. Document Page
Figure 16 Document Page Icon
To display a specific confirmation document, click the document icon. The confirmation
document opens in a separate window.
Figure 17 Document Page
4.5.2. Audit Trail
Central Matching Service User Guide v1.13
Page 23 of 95
Figure 18 Audit Trail Icon
To view technical information for a specific confirmation, select the 'audit trail' icon (shown
above). There is a unique Audit Trail for every confirmation in the CMS. This Audit Trail
details the messages exchanged during submission, processing and the matching process.
The example audit trail below shows the submission of a CNF and BFI to CMS. The
chronology commences at the foot of the page.
Figure 19 Audit Trail
The initial view can be expanded by checking either one or both of the two boxes at the top
left hand side of the screen; "Show processing details" and "Show messaging details".
Selecting "Show processing details" adds extra information to the original audit trail
summary. This allows the user to view processing messages from the client's back end
systems and which also detail message IDs communicated by the X/P Messenger.
Figure 20 Audit Trail Processing Details
Selecting “Show messaging details” adds messaging details to the original list. This details
communication from the X/P Messenger, including message IDs which can be identified in
the organisations X/P Messenger.
Central Matching Service User Guide v1.13
Page 24 of 95
Figure 21 Audit Trail Messaging Details
Selecting both “Show processing details” and “Show messaging details” will merge all details
into the one audit trail view
Figure 22 Audit Trail Complete View
The audit trail is colour coded according to whether each communication step is ‘well
processed’:



Lime Green – Processed correctly (e.g. Message Accepted)
Red – Information relating to a failure or error (e.g. Message failed to send)
Yellow – Warning information (e.g. Internal Acknowledgement Created)
Business Note
If errors are seen in the audit trail which are followed by green sections (confirming
correct processing) then it can be presumed that the error has been resolved. This may
occur in a situation where a confirmation failed at version 1 and then matched at version
Central Matching Service User Guide v1.13
Page 25 of 95
2 after an amendment had been sent.
Figure 23 Audit Trail Colour Coding
4.5.3. Notes
To add notes in the confirmation view, a user can choose to add a single note to an
individual confirmation or to update multiple selected confirmations with a single note input.
Individual Notes
Figure 24 Notes Icon
To add a note to a specific confirmation for
the counterparty to read, click the note icon
(shown left). The number of notes is indicated
on the button. Coloured dots indicate the
writer of the latest note.
Adding Notes to Multiple Confirmations
Select the tick box next to the notes symbol
for all confirmations applicable
Figure 25 Multiple Note Selection
Select the 'Add Note' button selected above
the trade data
Figure 26 Add Notes
Central Matching Service User Guide v1.13
Page 26 of 95
Figure 27 blue dot
Figure 28 yellow dot
blue: a note posted by someone within the
user’s organisation.
yellow: counterparty note posted by
someone within the counterparty/broker
organisation
red: a note posted by a CMS administrator
Figure 29 red dot
When the icon is selected, the “view confirmation notes” screen will be visible (See below).
This allows the user to communicate with other organisations on specific confirmations. All
previous notes are shown beneath the text box.
Figure 30 Notes View
Hovering over the notes button in the confirmations row, will display the last note posted, as
shown below.
Figure 31 Notes Tooltip
4.5.4. Exporting Documents
To export a list of all confirmations in the Dashboard, or returned through a deal finder
search, click the “Export” icon which appears on the top right of the results list.
On clicking this icon, a pop up screen appears asking the user to select how they wish to
view the exported file.
Central Matching Service User Guide v1.13
Page 27 of 95
Figure 32 Exporting to Excel
By selecting 'OK' a Microsoft Excel spreadsheet will be created using the exported data. The
columns shown in the spreadsheet will match the columns chosen in the CMS. In order to
export specific data columns; these must first be selected in the CMS 'Settings' - 'Column
Order' (see section Column Order). When exporting from the Deal Finder, all filters will be
detailed in "Parameters" within the Excel spreadsheet.
Central Matching Service User Guide v1.13
Page 28 of 95
Figure 33 Excel View of Export
The export will include:
 Organisation – The EIC Code of the organisation that carried out the export
 Generated on – The time the export was generated
 Generate by – The person who generated the export
 Records – The number of records shown in the export list
 System – Which system the export was created from (Live or UAT)
4.5.5. Near Matching
Figure 34 Near Matching Icons
The CMS will search for matching documents, and near matches will be shown in the near
match finder when a match is not achieved.
To view the near matches for a confirmation, click on the "near match" icon in the results list.
Users should be aware that:


The "near match" icon is not included in every entry on the results list.
The "C" indicates counterparty near match and "B" indicates a Broker near match.
Clicking on the "Near Match" icon opens a new browser window which displays all the near
matches for the selected confirmation, that is: all CNF/BCN documents in state "Pending"
where the sender/receiver parties are reversed (compared to the selected document).
Furthermore, when the selected confirmation is a power deal, only power CNFs are offered
as near matches and vice versa. If there are no near-matches then there will not be any
confirmations listed for comparison.
Central Matching Service User Guide v1.13
Page 29 of 95
Figure 35 Counterparty Near Match
Use the filter functions in the Near Match window to order the selection by a specific criteria.
The list can be filtered according to the number of matching key values in the document. The
box at the top of the window will allow a user to hide any documents that have more
discrepancies than they wish to view. Please note: The "Delta" column indicates which
confirmations have the fewest discrepancies (e.g. Delta 1 indicates there is 1 difference
between the 2 confirmation documents).The "Find Equal" check boxes at the top of the field
columns can be used to filter the near matches according to a given field, allowing a user to
see documents where the selected field matches. For example, if the "Find Equal" box in the
"Trade Date" column is selected, the list will only show documents with a matching "Trade
Date".
Selecting the compare comparisons icon
(Shown left) for a chosen confirmation will
open a new window displaying both
confirmation side by side (see below), with
discrepancies highlighted in red. In the
example below, the confirmation is
Figure 36 Compare Comparisons Icon
mismatched the Commodity Reference
Pricing Date.
Central Matching Service User Guide v1.13
Page 30 of 95
Figure 37 Compare Comparison View
Once the corresponding near match has been found, an amended version of the CNF can
be generated. In accordance with the EFET standard, the amended confirmation must use
the same Document ID as the original document, but the version number must be
incremented.
4.5.6. Hide Indicator (MO Only)
The Hide Indicator provides an MO with the ability to hide confirmations and suppress their
display in the eCM Dashboard and Deal Finder. 'Hidden' state applies to an individual trade
confirmation and is only hidden from view to users within the organisation (feature works
independently for each organisation entitled to view the deal). Hide only affects filtering in
the eCM Dashboard and eCM Deal Finder and does not affect any other eCM GUI or
process feature. Hiding a trade confirmation does not impact the matching process, and
therefore if a hidden trade confirmation is identified in the matching process, the confirmation
is unhidden and moves to ‘Matched’ state.
The Hide function is only available for trade confirmations in states 'Pending (CP)', 'Pending
(BR)', 'Alleged (CP)', 'Alleged (BR)' buckets, Preliminary Matched (BR),'Failed', and 'Error'.
An MO can add the “Hide Indicator” and “Hide Reason” to their eCM Dashboard view, by
navigating to Settings > Column Order.
To hide a trade confirmation an MO must select the empty tick box in the 'Hidden' column for
the applicable confirmation. This selection prompts a dialogue box to open, where the user
should enter a 'Hide Reason', then confirm by clicking the 'Hide' button. The reason text
must be 1-50 characters in length.. The Trade ID is also shown in the 'Hide Confirmation'
box.
Central Matching Service User Guide v1.13
Page 31 of 95
Figure 38 Hiding a confirmation
Once hidden, the confirmation will disappear from view on the Dashboard or Deal Finder, as
the default filter is to 'Exclude' hidden confirmations. To view hidden confirmations the user
must select the 'Include' or 'Hidden Only' filter options.
Business Note
Hidden trade confirmations are exportable providing they are visible to the user on the
Dashboard or Deal Finder screen (e.g. by selected view 'Include'). Once exported the
columns will render as 'Yes' for Hidden confirmations and 'No' for Unhidden
confirmations. The Hide reason can also be displayed in the export, if the column is
added to the users display in CMS.
Figure 39 Viewing a Hidden Confirmation
The ‘Hide Reason’ will be made visible in the eCM Dashboard if the user chooses to include
the column in the eCM Dashboard.
Central Matching Service User Guide v1.13
Page 32 of 95
Figure 40 Hide Reason
To 'unhide' a trade confirmation, the user must 'Include' hidden confirmations or view 'Hidden
Only' confirmations in their search. An MO can then select the tick box in the 'Hidden'
column for the applicable confirmation. This opens a dialogue box showing the trade ID of
the confirmation informing the user that the confirmation's display will no longer be
suppressed. The user must confirm by selecting 'Unhide'.
Figure 41 Unhide a Confirmation
4.5.7. Manual Terminate (MO Only)
Both Manual and Auto Terminate are available to CMS users. For details of Auto Terminate
see eCM Settings.
Figure 42 Manual Termination Icon
The Manual Terminate functionality applies to all CNF documents on CMS which are in the
state "Preliminary Matched" with the broker and/or in the state "Pending" with the
counterparty. Deals can only be terminated if they are not alleged to your organisation. The
counterparty would need to terminate these.
Summary of Bilateral States that can be terminated;
Central Matching Service User Guide v1.13
Page 33 of 95
Trade State
Pending
Matched
Terminated
Cancelled
Manually Terminate Deal?
Yes
Not Available
Not Available
Not Available
Resulting Trade State
Terminated
Summary of Trilateral States that can be terminated;
Trade State
Broker State
Manually
Resulting Trade
Terminate Deal? State
Pending
Pending
Yes
Terminated
Pending
Preliminary
Yes
Terminated
Matched
Matched
Matched
Not Available
Terminated
Terminated
Not Available
Cancelled
Cancelled
Not Available
Resulting
Broker State
Terminated
Terminated
This functionality only applies to Traders and CNF files. Brokers are unable to Terminate a
Broker Confirmation document.
Activation of the "Manual Terminate" button will set the "Pending" counterparty side of the
trade to state "Terminated". The broker leg will then move to state "Terminated".
The user must enter a reason for termination.
Figure 43 Manual Terminate
Confirmations which have been manually terminated can be viewed in the Dashboard
'Complete' tab, in the 'Terminated' row, and can also be searched for in the 'Deal Finder'.
Terminated confirmations will be in state 'TERMINATED', and optional 'BoxResults' can be
returned to the owner Organisation reporting the termination. An Organisation is able to opt
in to receive 'BoxResults' at Organisation (EIC code) level in Settings → eCM v4.0 Process
tab.
The termination reason is also available to view on the dashboard deal list. The user can
add the ‘Reason for Match Termination’ to their column settings by navigating to Settings >
Column Order.
Central Matching Service User Guide v1.13
Page 34 of 95
Figure 44 Reason for Match Termination
Trade confirmations in state 'Terminated' are not eligible for matching in CMS, however, they
can be amended to return the confirmation to 'Pending', from which the matching process
will begin.
In the case of a trilateral confirmation matching dialogue where the trader leg has 'Matched'
and the broker leg remains in 'Pending', the 'Pending' broker leg can be 'Manually
Terminated'. The 'Terminated' broker leg cannot be amended and is no longer eligible to
Match. Trader leg 'Matched' and Broker leg 'Terminated' is the final state for this trade.
Manually terminated trades cannot be cancelled. Organisations will need to amend the
confirmation to ‘Pending’ from which a cancellation can be made.
5. eCM lite Menu
5.1. Enter Trade
The ‘Enter Trade’ screen allows a user with Master Operator rights to submit a new trade
confirmation to CMS eCM lite, and to amend an existing trade confirmation.
Select ‘Enter Trade’ from the eCM menu options and using the drop down select the product
to be submitted to eCM. The screen will auto-populate with the required trade data fields.
To complete the trade submission a user must complete the online form and press
“Confirm”. The confirmation is then saved in the CMS and is viewable in the eCM
Dashboard and eCM Deal Finder.
To enter a trade confirmation, follow the steps below:
Select eCM > Enter Trade and using the drop down select the applicable product for
matching. Click confirm.
Central Matching Service User Guide v1.13
Page 35 of 95
Figure 45 eCM > Enter Trade - Select Product
Populate the generated fields.
Figure 46 eCM > Enter Trade Details
Figure 47 eCM > Populated Trade
Click ‘confirm’.
Confirmation Submitted notification will appear on the screen.
Central Matching Service User Guide v1.13
Page 36 of 95
Figure 48 eCM > Enter Trade - Confirmation
Any errors on the form will be flagged and the confirmation will not save. Update the fields
which are incorrect (a red information icon will appear next to incorrect fields) and click
confirm. If the changes are accepted the 'Confirmation Submitted Successfully' message
will appear on screen.
Figure 49 eCM > Enter Trade - Confirmation Error
5.2. Amending a Trade
To amend a trade confirmation, a user can select a button within the populated results of
either the Deal Finder or Dashboard Buckets. The user can search for the appropriate trade
and select the “Amend” button from the search results. The user must have the column
Button “eCM lite Controls’ selected within the column settings to view these options.
Figure 50 eCM > Deal Finder > Search Results
Central Matching Service User Guide v1.13
Page 37 of 95
If the "Amend" button is selected then the user will be taken to the ‘Enter Trade’ screen prepopulated with the trade details.
Figure 51 eCM > Deal Finder > Selecting A Trade to Amend
Once the amendments have been completed, the user can press the “Amend” button to
reconfirm the details.
Figure 52 eCM > Deal Finder > Select Amend to Confirm Changes
5.3. Cancelling a Trade
If the “Cancel” button is selected then a warning message is generated. The user can then
select whether to confirm the cancellation by selecting “Yes – Cancel” or by rejecting the
cancellation by selecting “No – Abort”
Figure 53 eCM > Deal Finder > Cancelling a Trade
Central Matching Service User Guide v1.13
Page 38 of 95
Figure 54 eCM > Cancelling a Trade Confirmation
5.4. eCM lite Dashboard
In Progress –Deals which have been well processed, but have not matched yet. All
confirmations within this section are in the state "Pending" with the counterparty and can
match, be amended, or be cancelled. 'In progress' deals are split into four categories, only
two are applicable for eCM lite:
 Pending (CP) – confirmations submitted by the user's organisation which are awaiting
the matching CNF
 Alleged (CP) – confirmations alleged to the user's organisation by a counterparty
awaiting a matching CNF.
Issue – Confirmations in the ’Issue’ tab cannot match in the CMS without corrective action.
These issues are split into four categories:
 Error – confirmations which were in the matching process with a peer-to-peer
counterparty but have experienced issues (e.g. match suggestion received for a timed
out confirmation).
 Failed – confirmations which were sent to the CMS but do not comply with the EFET
eCM Standards (e.g. Missing “DeliveryPointArea”).
 Receiving – A transitory state for the sending/receiving of CNF Documents.
 Matching – A transitory state for the sending/receiving of MSU/MSA Documents.
Complete – Deals which have Matched or have been Cancelled. These are split into five
categories, only three are applicable to eCM lite:
 Matched – The confirmation has Matched completely with the counterparty (bilateral)
 Cancelled – The confirmation has been Cancelled.
 Terminated - The confirmation has been terminated and is not eligible for matching. By
submitting an amendment, with a higher version number, an organisation can return the
trade confirmation to a 'Pending' state, from which it is eligible to match.
5.5. eCM lite Deal Finder
The Deal Finder allows a user to search for specific confirmations within an organisation.
Central Matching Service User Guide v1.13
Page 39 of 95
Figure 55 eCM > Deal Finder
The Deal Finder offers the same filters as the Dashboard, as well as additional filters
including:
 Our Trade ID –Trade ID for an organisation (up to 50 ID’s can be entered; these can be
copied and pasted from another source).
 Their Trade ID –Trade ID for the counterparty involved in the trade (up to 50 ID’s can be
entered; may be copied and pasted from another source).
 Document ID – Document ID relating to any confirmation from either counterparty
involved in the trade (up to 50 ID’s can be entered; these can be copied and pasted from
another source).
 Trade Confirmations Not Found - Our Trade ID, Their Trade ID or Document/UTI/USI
IDs not found during a search in the eCM Deal Finder will be shown in a warning
message. Multiple IDs not found, a warning sign is displayed and can be expanded to
show the list of IDs. A single ID not found, will be displayed by the warning symbol. If
multiple IDs are not found then a user can expand the details by selecting ‘Show’.
 Price – Specific price of the trade can be searched for.
 Sender – Us or Them – confirmations sent by the user’s organisation, or by the
counterparty/broker.
 Hidden – Choose whether to view Hidden confirmations (default is exclude)
 Trade Date Range – Select the range of trade dates (Trade Date refers to the date the
trade was booked).
 Submission Date Range – Select the range of submission dates (Submission Date
refers to the date the confirmation was submitted to CMS).
 Delivery Start – Select the date when the delivery begins.
 Delivery End – Select the date when the delivery ends.
The date filters can be used to select
particular dates by selecting the green
calendar icon. The supported date format is
“DD/MM/YYYY” (DD=Day/two digits,
MM=Month/two digits, YYYY=Year/four
digits), for example 12/09/2011 for 12
September 2011. The date filter is only
available in this view.
A date picker control is provided to facilitate
the input of the date.
This control resembles a calendar and will
insert the appropriate date into the date fields
for the day selected in the date picker. To
open the date picker, click the calendar icon
to the right of the filter.
Central Matching Service User Guide v1.13
Figure 56 eCM - Filters Date Picker
Page 40 of 95
There is also the option to select a date
range on the blue calendar icon (shown
right).
The same date format is supported as with
the previous calendar icon,
however the user is offered preselected date
ranges, and search options.
Figure 57 eCM - Date Range Selector
Business Note
If no Submission Date is selected the Submission Date range automatically populates to
show the last 20 days.
5.6. Auto-Populated Filters
Filter options will only contain information relevant to the user’s organisation. For example, if
an organisation does not confirm Power trades, then Power will not be available in the
Commodity filter drop down list. The list is generated at the time of log in for each user,
based on all submissions made in the previous 90 days. It is also possible to select multiple
fields within each filter by using the check boxes in the drop down box. Filters that
automatically populate include:




Counterparty – Filter by Counterparty EIC Code.
Transaction Type – Filter by Transaction Type (e.g. FOR, OPT etc.)
Commodity – Filter by Commodity Type (e.g. Power, Gas etc.)
Market – Filter by geographical location of the market an organisation is trading in (e.g.
FR for France)
5.7. My Filters
A user can save searches using the “My Filters” button. This is available on all Dashboard
and Deal Finder screens. To save a search, first select the fields to filter. For example if a
user wishes to view confirmations for ‘11XTST-CHARLIE-1’, they would select only this
counterparty in the Counterparty drop down list and click ‘OK’. To save this filter, click ‘My
Filters’ > ‘Save Current’. If a filter already exists, the ‘Save’ functionality will be unavailable.
Central Matching Service User Guide v1.13
Page 41 of 95
Figure 58 eCM > My Filters
This opens up a new window, where a name for the filter must be entered which can extend
to 31 characters; e.g. ‘TST Charlie’. By selecting ‘Save As’ the filter will be saved. To replace
an existing filter, there is the ability to select a filter in the drop down, then click ‘Replace’. To
set a search as the default search in the Deal Finder, tick the ‘Use as default’ check box.
Once a filter is saved it will appear in the ‘My Filters’ drop down list. Date Range, Price and
Sender are not included within the saved filter.
Figure 59 eCM - Saving My Filters
To delete a filter, the user should select ‘Manage Filters’ in the ‘My Filters’ drop down. This
presents a screen which allows the user to select and delete saved filters.
5.8. Interactive Icons within the eCM lite Tab
5.8.1. Document Page
Figure 60 eCM - Document Icon
To display a specific confirmation document, click the document icon. The confirmation
document opens in a separate window.
Central Matching Service User Guide v1.13
Page 42 of 95
Figure 61 eCM - Document Example
5.8.2. Audit Trail
Figure 62 eCM - Audit Trail Icon
To view technical information for a specific confirmation, select the 'audit trail' icon (shown
above). There is a unique Audit Trail for every confirmation in the CMS. This Audit Trail
details the messages exchanged during submission, processing and the matching process.
The chronology commences at the foot of the page.
Figure 63 eCM - Audit Trail
The initial view can be expanded by checking either one or both of the two boxes at the top
left hand side of the screen; "Show processing details" and "Show messaging details".
Central Matching Service User Guide v1.13
Page 43 of 95
Selecting "Show processing details" adds extra information to the original audit trail
summary. This allows the user to view processing messages from the CMS. The “Show
messaging details” is not applicable to eCM lite organisations.
Figure 64 eCM - Audit Trial with Processing Details
The audit trail is colour coded according to whether each communication step is ‘well
processed’:
Lime Green – Processed correctly (e.g. Message Accepted)
Red – Information relating to a failure or error (e.g. Message failed to send)
Yellow – Warning information (e.g. Internal Acknowledgement Created)
Business Note
If errors are seen in the audit trail which are followed by green sections (confirming
correct processing) then it can be presumed that the error has been resolved. This may
occur in a situation where a confirmation failed at version 1 and then matched at version
2 after an amendment had been sent.
5.8.3. Notes
To add notes in the confirmation view, a user can choose to add a single note to an
individual confirmation or to update multiple selected confirmations with a single note input.
Individual Notes
To add a note to a specific confirmation for
the counterparty to read, click the note icon
(shown left). The number of notes is indicated
on the button.
Coloured dots indicate the writer of the latest
note.
Central Matching Service User Guide v1.13
Page 44 of 95
Adding Notes to Multiple Confirmations
Select the tick box next to the notes symbol
for all confirmations applicable
Select the 'Add Note' button selected above
the trade data
blue: a note posted by someone within the
user’s organisation
yellow: counterparty note posted by
someone within the counterparty/broker
organisation
red: a note posted by a CMS administrator
When the icon is selected, the “view confirmation notes” screen will be visible (see below).
This allows the user to communicate with other organisations on specific confirmations. All
previous notes are shown beneath the text box.
Figure 65 eCM - Entering Notes
Central Matching Service User Guide v1.13
Page 45 of 95
Hovering over the notes button in the confirmations row, will display the last note posted, as
shown below.
Figure 66 eCM - View Notes within Results
5.9. Exporting Documents
To export a list of all confirmations in the Dashboard, or returned through a deal finder
search, click the “Export” icon which appears on the top right of the results list.
On clicking this icon, a pop up screen appears asking the user to select how they wish to
view the exported file.
Figure 67 eCM > Export
By selecting 'OK' a Microsoft Excel spreadsheet will be created using the exported data. The
columns shown in the spreadsheet will match the columns chosen in the CMS. In order to
export specific data columns; these must first be selected in the CMS 'Settings' - 'Column
Order' (see section Column Order). When exporting from the Deal Finder, all filters will be
detailed in "Parameters" within the Excel spreadsheet.
Central Matching Service User Guide v1.13
Page 46 of 95
Figure 68 ecm > View of Export
The export will include:
Organisation – The EIC Code of the organisation that carried out the export
Generated on – The time the export was generated
Generate by – The person who generated the export
Records – The number of records shown in the export list
System – Which system the export was created from (Live or UAT)
5.10.
Near Matching
The CMS will search for matching documents, and near matches will be shown in the near
match finder when a match is not achieved.
To view the near matches for a confirmation, click on the "near match" icon in the results list.
Figure 69 eCM > Counterparty Near Match Icon
Users should be aware that:
 The "near match" icon is not included in every entry on the results list.
 Clicking on the "Near Match" icon opens a new browser window which displays all the
near matches for the selected confirmation, that is: all CNF documents in state "Pending"
where the sender/receiver parties are reversed (compared to the selected document).
 When the selected confirmation is a power deal, only power CNFs are offered as near
matches and vice versa. If there are no near-matches then there will not be any
confirmations listed for comparison.
Central Matching Service User Guide v1.13
Page 47 of 95
Figure 70 eCM > Counterparty Near Match Candidates
Use the filter functions in the Near Match window to order the selection by a specific criteria.
The list can be filtered according to the number of matching key values in the document. The
box at the top of the window will allow a user to hide any documents that have more
discrepancies than they wish to view. Please note: The "Delta" column indicates which
confirmations have the fewest discrepancies (e.g. Delta 1 indicates there is 1 difference
between the 2 confirmation documents).The "Find Equal" check boxes at the top of the field
columns can be used to filter the near matches according to a given field, allowing a user to
see documents where the selected field matches. For example, if the "Find Equal" box in the
"Trade Date" column is selected, the list will only show documents with a matching "Trade
Date".
Selecting the compare comparisons icon
(Shown left) for a chosen confirmation will
open a new window displaying both
confirmations side by side (see below), with
discrepancies highlighted in red. In the
example below, the confirmation is
Figure 71 eCM > Compare Icon
mismatched the Commodity Reference
Pricing Date.
Figure 72 eCM > Comparison View
Once the corresponding near match has been found, an amended version of the CNF can
be generated.
Central Matching Service User Guide v1.13
Page 48 of 95
5.11.
Hide Indicator (MO Only)
The Hide Indicator provides an MO with the ability to hide confirmations and suppress their
display in the eCM Dashboard and Deal Finder. 'Hidden' state applies to an individual trade
confirmation and is only hidden from view to users within the organisation (feature works
independently for each organisation entitled to view the deal).
Hide only affects filtering in the eCM Dashboard and eCM Deal Finder and does not affect
any other eCM GUI or process feature. Hiding a trade confirmation does not impact the
matching process, and therefore if a hidden trade confirmation is identified in the matching
process, the confirmation is unhidden and moves to ‘Matched’ state.
The Hide function is only available for trade confirmations in states 'Pending (CP)', 'Alleged
(CP)', 'Failed' and 'Error'.
An MO can add the “Hide Indicator” and “Hide Reason” to their eCM Dashboard view, by
navigating to Settings > Column Order.
To hide a trade confirmation an MO must select the empty tick box in the 'Hidden' column for
the applicable confirmation. This selection prompts a dialogue box to open, where the user
should enter a 'Hide Reason', then confirm by clicking the 'Hide' button. The reason text
must be 1-50 characters in length. The Trade ID is also shown in the 'Hide Confirmation'
box.
Figure 73 eCM > Hide Confirmation
Once hidden, the confirmation will disappear from view on the Dashboard or Deal Finder, as
the default filter is to 'Exclude' hidden confirmations. To view hidden confirmations the user
must select the 'Include' or 'Hidden Only' filter options.
Business Note
Hidden trade confirmations are exportable providing they are visible to the user on the
Dashboard or Deal Finder screen (e.g. by selected view 'Include'). Once exported the
columns will render as 'Yes' for Hidden confirmations and 'No' for Unhidden
confirmations. The Hide reason can also be displayed in the export, if the column is
added to the users display in CMS.
Central Matching Service User Guide v1.13
Page 49 of 95
Figure 74 eCM > Searching for Hidden Confirmations
The ‘Hide Reason’ will be made visible in the eCM Dashboard if the user chooses to include
the column in the eCM Dashboard.
Figure 75 eCM - View of Hide Reason
To 'unhide' a trade confirmation, the user must 'Include' hidden confirmations or view 'Hidden
Only' confirmations in their search. An MO can then select the tick box in the 'Hidden'
column for the applicable confirmation. This opens a dialogue box showing the trade ID of
the confirmation informing the user that the confirmation's display will no longer be
suppressed. The user must confirm by selecting 'Unhide'.
Figure 76 eCM - Unhide a Confirmation
Central Matching Service User Guide v1.13
Page 50 of 95
5.12.
Manual Terminate (MO Only)
Both Manual and Auto Terminate are available to CMS users. For details of Auto Terminate
see eCM Settings.
Figure 77 eCM - Manual Termination Icon
The Manual Terminate functionality applies to all CNF documents on CMS which are in the
state "Pending" with the counterparty. Deals can only be terminated if they are not alleged
to your organisation. The counterparty would need to terminate these.
Summary of Bilateral States that can be terminated:
Trade State
Pending
Matched
Terminated
Cancelled
Manually Terminate Deal?
Yes
Not Available
Not Available
Not Available
Resulting Trade State
Terminated
The user must enter a reason for termination.
Figure 78 eCM - Entering a Terminate Reason
Confirmations which have been manually terminated can be viewed in the Dashboard
'Complete' tab, in the 'Terminated' row, and can also be searched for in the 'Deal Finder'.
Terminated confirmations will be in state 'TERMINATED'.
The termination reason is also available to view on the dashboard deal list. The user can
add the ‘Reason for Match Termination’ to their column settings by navigating to Settings >
Column Order.
Central Matching Service User Guide v1.13
Page 51 of 95
Figure 79 eCM - Dashboard - Terminate Reason Display
Trade confirmations in state 'Terminated' are not eligible for matching in CMS, however, they
can be amended to return the confirmation to 'Pending', from which the matching process
will begin.
Manually terminated trades cannot be cancelled. Organisations will need to amend the
confirmation to ‘Pending’ from which a cancellation can be made.
6. eCM Settings
6.1. eCM 4.0 Process
This screen displays the capabilities of all CMS organisations. A green tick indicates that the
organisation has enabled the setting, and a red cross indicates that the organisation has
disabled the setting. By default these settings are disabled.
Figure 80 eCM 4.0 Process View
Central Matching Service User Guide v1.13
Page 52 of 95
There are 11 columns within 'Settings':
1. Organisation Group – A logical grouping of organisations. Provides for consolidated
transaction billing across organisations belonging to the same legal entity. The
Organisation Group is created by the CMS Service Team and will have at least one
Organisation (e.g. one Organisation Group of ALPHA, may include two Organisations:
ALPHA ONE and ALPHA TWO)
2. EIC Code – (Energy Identification Code) – Within the community of trading organisations
a unique code is required to identify a party, which is known as an EIC Code. This code
is also used by the EFETbox for processing. These can be found on the EFET Static
Data website (http://www.efet.org/staticdata/group.aspx?g=All).
3. Display Name – This is the name assigned to an Organisation in CMS. This may be
different to the legal name, and may be different to the Organisation Group name if the
Organisation Group has multiple Organisations.
4. Amend Cancelled* – Cancelled confirmations can be amended to return them to a
'Pending' state. If the document was in the state 'Pending' before it was Cancelled, then
the submission of an amendment by the owner organisation will return the confirmation
to a ‘Pending’ state. However, if the confirmation was Cancelled from a ‘Matched’ state,
then both sides should send amendments to bring the deal out of cancelled, re initiating
the matching process.
5. Amend Matches* – Documents in a 'Matched' state can be amended in CMS, when
using version 4.0 of the eCM process. However, the new versions of a currently
matching pair of documents can only be matched with one another, as stated in 4.4
Business Document Processing 'Suggested Match' Processing (EFET Standards v.4.0,
Chapter 4, p.48). This allows owner organisations of confirmations in a matching pair to
use the existing matching dialogue to mutually amend the content of the matched
documents, and thus reconcile changes made to the terms of the separately held
confirmation records (See EFET standards v4.0, Chapter 4, p.25). Both counterparties
will need this functionality enabled in CMS for the amendment to be successful. If one
counterparty has this function disabled then an amendment from either side will be
rejected. Confirmations will remain matched on the dashboard until the amended
confirmation is successfully matched with the counterparty.
6. Tear Up Matches* – The eCM v4.0 process introduces the ability to 'Tear Up' a Matched
pair of confirmations. If an underlying deal is made void, or a fundamental change is
required that cannot be achieved through amending the matched documents, such as
changing a counterparty, then the change to the Trader and/or Broker backend systems
can be reconciled using Tear-Up processing (See EFET standards v4.0, Chapter 4,
p.24). Both counterparties will need this functionality enabled in order to Tear Up a
matched trade. The request can only be sent by a trading organisation; not a broker.
7. Match Broker Fee* – In CMS, a trading organisation can optionally elect to match
brokerage fees with a broker through the eCM v4.0 process. If this is turned off, then the
trading organisation is not required to submit a BFI for matching in CMS, (See EFET
standards v4.0, Chapter 4, p.19).
8. Auto-Terminate – Confirmations that are 'Pending' and older than 31 days since the last
submission date can be automatically "Terminated" in CMS. The 'Auto Terminate'
process runs between 20:00 – 08:00 UK Time each night. 'Terminated' confirmations are
not eligible for matching unless an amendment, with a higher version number, is
submitted by the owner organisation.
9. Box Results for Terminate* – Organisations are able to choose whether to receive box
results to their back end systems for Terminated confirmations. If an organisation elects
to receive box results for Terminated trades, the back end systems will need to be
configured to handle these messages.
10. Box Results Contains USI* - CMS Organisations are able to choose whether or not to
receive a USI in the Matched BRS result returned from eCM after a Match has occurred.
If an organisation elects to receive the USI, the organisation’s backend system will then
need to be configured to consume the USI issued. Alternatively, the USI can be ignored.
Central Matching Service User Guide v1.13
Page 53 of 95
11. Box Results Contains UTI* - CMS Organisations are able to choose whether or not to
receive a UTI in the Matched BRS result returned from eCM after a Match has occurred.
If an organisation elects to receive the UTI, the organisation’s backend system will then
need to be configured to consume the UTI issued. Alternatively, the UTI can be ignored
*Functionality is unavailable to eCM lite Organisations
A user with MO rights is able to change CMS settings to enable or disable Amend
Cancelled, Amend Matches, Tear-Ups, Match Broker Fee, Auto-Terminate, Auto-Terminate
box results, Box Results for Terminate, Box Results Contains USI and Box Results Contains
UTI.
The MO can only change the settings for an organisation for which they have been assigned
MO rights. They are not able to change settings for other organisations within their
organisation group if they did not have MO rights for the organisation(s). For more
information on user rights, please refer to section User Roles.
6.2. Box Result Messages
eCM Settings > eCM 4.0 Process: Enabling UTI in BRS messages
CMS Organisations are able to choose whether or not to receive a UTI in the Matched BRS
result returned from eCM after a Match has occurred. If an organisation elects to receive the
UTI, the organisation’s backend system will then need to be configured to consume the UTI
issued. Alternatively, the UTI can be ignored.
To opt in to receive the UTI in each Matched BRS, a user with MO rights should enable in
the ‘BoxResult contains UTI’ in 'Settings' for the relevant organisation, ensuring a green tick
is shown. To opt out, the user should click the indicator to show a red cross.
6.3. Broker Restrictions (MO Only)
An organisation can upload an XML broker restriction file in the 'Broker Restrictions' tab.
This file allows an organisation to choose which brokers to match confirmations with in CMS.
An example Broker Restriction files is available on request from the CMS Service Team. To
upload a file, click on the ‘Browse File’ button and select the broker restrictions file to be
uploaded.
Figure 81 Broker Restriction View
Central Matching Service User Guide v1.13
Page 54 of 95
Once the file is selected, the file name will appear in the text box and Upload button will be
highlighted. Uploading the file will apply the desired broker restrictions in CMS.
Figure 82 Uploading a Broker Restriction
Business Note
In order to help to reduce dashboard noise, CMS counterparties are able to restrict
unwanted broker confirmations from appearing in their dashboard by uploading a broker
restriction file.
Brokers who allege broker confirmations to trading organisations with a broker restriction in
place will receive the following BoxResult and the broker confirmation will be rejected from
CMS.
Figure 83 BRS Broker Restriction
Business Note
Broker matching is not supported by eCM lite and is implicitly disabled for all eCM lite
users. If a broker confirmation is alleged to an eCM lite counterparty, the confirmation will
be rejected by CMS and the broker will receive a BoxResult message notifying them of
the rejection.
6.4. Column Order
Within the eCM Settings tab, a user is able to change the columns displayed within the
Dashboard and Deal Finder, as well as the order in which each column appears.
Central Matching Service User Guide v1.13
Page 55 of 95
Figure 84 Column Order Tab
To add additional columns, a user should select the desired column field from the 'Hidden
Columns' section; and drag the field to the 'Selected Columns' section to the left. When the
new column field is hovering in the correct order, the user can 'drop' it into place. It is also
possible to reorder column fields displayed by moving the field up or down the list (the top of
the list is the first information displayed in the dashboard). Select "Save changes" to
implement the new column order. Column orders are saved for individual users and do not
affect the whole organisation.
Figure 85 Changing Personal Column Settings
6.5. Holiday Calendar
The holiday calendar details non business days such as public holidays across the Europe.
It also provides time out information on P2P confirmations and calculates based on today's
date -3 days for a trade confirmation or -10 days for broker confirmations. For example, if
today is 24th July 2014, the confirmations can only be sent to a P2P trader if the trade date
is no earlier than 18th July (24 less 3 working days = 18). If the trade date is earlier and still
pending, then an amendment needs to be sent as the trade would have timed out in the P2P
system.
Central Matching Service User Guide v1.13
Page 56 of 95
Figure 86 Holiday Calendar
6.6. Products (MO Only)
The Products function allows a Master Operator (MO) to define and centrally control which
confirmations are accepted by an organisation in CMS. The objective is to ensure only those
trades which an organisation wishes to electronically match, are accepted by CMS, thereby
reducing dashboard noise. The Products function is found in the eCM → Settings →
Products tab.
The ‘Matched by’ column displays the number of organisations in CMS that currently match
the product.
The ‘We match’ column shows whether the user’s organisation has opted to confirm each
product in CMS. A prohibition sign indicates that the Organisation will not match that
product. A green circle with a tick in it indicates that the Organisation is willing to match that
product.
eCM lite organisations can only enable/disable gas and power forwards for eCM Matching in
CMS. These are displayed in the Products table as FOR Gas or FOR Power, followed by the
Market.
Central Matching Service User Guide v1.13
Page 57 of 95
Figure 87 Products View
To allow the matching of a new product in CMS, a user should click the prohibition sign for
the desired product in the ‘We Match’ column.
Figure 88 'We match' View
This will bring up a dialogue box asking the user to confirm that the product should be
enabled.
Figure 89 Activate Box
Clicking the ‘Yes – Activate’ button will confirm the selection and return the user to the
Products screen. The product will now show a ticked green circle next to it and the number
in the ‘Matched by’ column will have increased by one.
Central Matching Service User Guide v1.13
Page 58 of 95
Figure 90 Revised 'We match' View
To block an already enabled product, simply reverse the process. Clicking on a green circle
will bring up a dialogue box asking the user to confirm that they wish the product to be
blocked for eCM in CMS.
Figure 91 Block Product Box
Clicking the ‘Yes – Block’ box will return the user to the Products screen. The product will
now show a red circle in the ‘We match’ column and the ‘Matched by’ column will have
decreased by one.
Figure 92 'We match' View for Blocked Product
When a confirmation is submitted to CMS for a product which is blocked by an organisation,
the following can be expected:
 The confirmation will be rejected - this applies to both traders and brokers.
 A particular case exists for a trilateral match. If one trader has a product blocked for
eCM in CMS, and the second trader and broker have the product enabled, then a broker
only match should be sent to match with the broker. There is no need to send a
document to the counterparty as they are not matching this product combination
 When a combination of Trade Type, Commodity & Product is sent to the CMS which is
not in the Gatekeeper list, it will be blocked.
o Rejection example message is: "eCM Gatekeeper: confirmation blocked. Reason:
contains unknown product "FXD_SWP Canola". Remedy: (1) verify you are using
Central Matching Service User Guide v1.13
Page 59 of 95

the correct product code (2) ask EFETnet support to add it to the product
definitions, then enable it under "eCM > Settings > Products".
An audit trail entry is written when the gatekeeper narrows a trilateral match to
“counterparty only” (because the broker does not support the product)
A user can choose to extract the Products data by clicking on the ‘Download for all eCM
Parties’ button at the top of the Products page
Figure 93 Download Button
The exported data is extracted as a spread sheet in Microsoft Excel format. This export
displays which products have been enabled for eCM in CMS by user CMS Organisation.
Enabled products are indicated by a green highlighted, X.
Figure 94 Exported Products for all CMS Parties - File Example
To start matching a product not currently listed in the Products tab, please contact the CMS
Service Team to request it be added.
Central Matching Service User Guide v1.13
Page 60 of 95
7. The eRR Menu
7.1. eRR GUI
Users can access the eRR GUI via the EFETnet CMS. Only organisations connected to
eRR for reporting will be able to view the eRR menu tab in the CMS GUI.
The eRR menu allows a user to navigate to eRR-related trade data and configuration
functions. These are:




Dashboard – access the submission status
Deal Finder – search for submissions using specific details, Document ID or UTI
Reconciliation – provides access to daily reconciliation reports comparing trade
portfolios between the trading organisation and its counterparties using data reported
through eRR.
Standing Instructions - view Standing Instructions set for each organisations
Figure 95 eRR Menu
7.2. eRR Dashboard
The eRR Dashboard displays in progress, with issues, and completed. These can be viewed
by:


Trade Date – date the trade was agreed
Submission Date – date the trade confirmation was submitted to CMS
Figure 96 eRR Dashboard
Users can refine the displayed trade submissions further by using the following filters:
Central Matching Service User Guide v1.13
Page 61 of 95



Trade Repository (i.e. Regis-TR, UnaVista etc.)
Asset Class (Asset Class of submission i.e. Commodity, Foreign Exchange etc. )
OTD vs. ETD
Confirmations are viewed and categorised by age:
 Today (0-4h): transaction updated today, less than 4 hours ago
 Today (earlier): transaction updated today, more than 4 hours ago
 Yesterday: transaction last updated on the previous calendar day
 2 days ago: transaction last updated 2 calendar days ago
 3-6 days ago: transaction last updated 3-6 calendar days ago
 7+ days ago: transaction last updated 7+ calendar days ago
1. In Progress – trade reports submitted to eRR, currently in processing and yet to be
reported at the TR
a. Pending – The document was sent to the repository and is now waiting for a
response or it is waiting to be sent to the repository because a former version is
still waiting for a response.
b. Alleged – a counterparty submitted a trade not yet submitted by your
organisation
c. Retry – .deals which have failed validation (during the mapping or enrichment
process) and have been moved to the manual intervention queue for rejection by
the Service Team
2. Issue –
a. Rejected eRR – any submission that has an error within the submitted XML file
and rejected by the eRR system
b. Rejected TR - any submission that has been rejected directly by the TR
c. Communication Problem - TR – any submission which is unable to be sent to
the TR due a communications issue
d. Processing eRR - any submission which is currently being processed by the TR
3. Completed –
a. Reported to TR – successfully reported submissions to the TR
b. Not Reportable - any submission which has been processed by eRR but does
not require reporting under EMIR
7.3. eRR Deal Finder
The Deal Finder allows a User to search for a specific trade report submitted by their
organisation.
A user can search by entering the full Document ID or UTI into the search bar. Selecting
‘Search’ will populate the search window with the search result. If no document(s) are found,
the window will be empty.
Central Matching Service User Guide v1.13
Page 62 of 95
Figure 97 eRR Deal Finder
It is not possible to perform a search with only ‘part’ of the Document ID or UTI.
7.3.1. Filters
Users can search for specific trade reports in the eRR Deal Finder by using either an
Document ID, UTI, Internal Trade ID’ and/or by identifying the ‘Document Type’.
Figure 98 eRR Filters
7.3.2. Interactive Icons within the eRR Tab
Document
To display a specific confirmation document, click the document icon. The latest CpML
document opens in a separate window.
Central Matching Service User Guide v1.13
Page 63 of 95
Figure 99 eRR Document Icon
Central Matching Service User Guide v1.13
Page 64 of 95
Audit Trail
To view technical information for a specific report, select the 'audit trail' icon (shown above).
There is a unique Audit Trail for every submission in the CMS. This Audit Trail details the
messages exchanged during submission, processing and the matching process.
The chronology commences at the foot of the page.
The initial view can be expanded by the box at the top left hand side of the screen; "Show
messaging details".
The audit trail is colour coded according to whether each communication step is ‘well
processed’:
 Lime Green – Processed correctly (e.g. Message Accepted)
 Red – Information relating to a failure or error (e.g. Message failed to send)
 Yellow – Warning information (e.g. Internal Acknowledgement Created)
The audit trail also contains hyperlinks to the documents that have been submitted and
processed through eRR. These include the CpML submissions, Enriched documents and
Box Results received.
Figure 100 eRR Audit Trail
If errors are seen in the audit trail which are followed by green sections (confirming correct
processing) then it can be presumed that the error has been resolved. This may occur in a
situation where the CMS still in progress/waiting for status change of a report.
7.3.3. eRR Deal Finder Export
To export a list of all confirmations in the Dashboard, or returned through a deal finder
search, click the “Export” icon which appears on the top right of the results list. On clicking
this icon, a pop up screen appears asking the user to select how they wish to view the
exported file.
Central Matching Service User Guide v1.13
Page 65 of 95
Figure 101 eRR Deal Finder Export
7.4. Standing Instructions
To simplify the reporting process for users, eRR provides the ability to default a number of
reporting fields. These default values are described as Standing Instructions and are
typically fields which change rarely, if ever.
Submissions made to eRR with no value provided for the Standing Instruction fields will be
enriched with the respective data provided through the Standing Instructions. Each
Organisation within an Organisation Group reporting via eRR must complete its own
Standing Instructions
Central Matching Service User Guide v1.13
Page 66 of 95
Figure 102 eRR Standing Instructions
7.4.1. Add or Edit Instruction
An MO can edit the data in the Standing Instructions by editing the existing data in the GUI.
Clicking ‘Update’ with update the Standing Instructions, effective immediately.
Central Matching Service User Guide v1.13
Page 67 of 95
Figure 103 Adding/Editing Standing Instructions
A user is able to change the Standing Instructions for any organisation for which they are
assigned MO rights. Fields are populated/updated using one of three methods - free text,
drop down or toggle options – depending on the data required.
Some fields are mandatory, and others are conditional; affected by the instruction given in a
previous field. The Standing Instruction fields are described in Section 2 Business
Processing, Table 1 of the eRR Standards.
Users are able to view external organisations (outside of their organisation group) that they
report on behalf of. Changes to these organisations can only be made by FHAs.
Central Matching Service User Guide v1.13
Page 68 of 95
Figure 104 External eRR Parties
In order to edit standing instructions for external parties the screen eRR > Standing
Instructions has an additional field “External Party”.
Figure 105 Amending Standing Instructions for an external organisation
Business Note
The default Trade Repository cannot be changed in the Standing Instructions screen. To
change the default Trade Repository for an organisation, please contact the EFETnet
Service Team.
7.5. eRR Reconciliation
This is an automated report which compares trade portfolios between counterparties based
on their EMIR trade reporting. The report is executed each weekday (Monday-Friday) and
includes the following:
Central Matching Service User Guide v1.13
Page 69 of 95



EMIR only submissions sent in through the CMS eRR module and reported to an EMIR
TR (trade repository).
All legal entities within ‘your’ organisation group registered for eRR EMIR reporting.
All OTC trades (commodity, FX, interest rates) and excludes ETD trades (exchange
traded derivatives) which are exempt from EMIR portfolio reconciliation requirements.
The reconciliation report presents the outcome of the reconciliation run as an Excel file with
8 worksheets:








Info
MTM
Matched
Partial Match
Mismatched
Pending
Alleged
Error
Matching takes place in two steps:
 find pairs: for trade details reported by one counterparty find the corresponding data
sent by the other counterparty; a pair is established when both sides have used the
same UTI (unique trade identifier) and counterparty identifiers (LEIs)
 match pairs: for each established pair commercial details are compared field by field;
the relevant fields are defined in the EFET ePR standard (electronic portfolio
reconciliation)
Functions
 Download: allows a user to download reconciliation results in Excel format
 Rerun (available to Master Operators only): instructs the CMS to redo a given
reconciliation. The new report version will include corrections received since the last run.
 A Master Operator can upload trades (optionally with Valuations) of non-eRR
counterparties. By uploading a CSV file and pressing 'Rerun' the data will be included in
the reconciliation run.
Meaning of the Data Columns
Dates
 As of: reconciliation cut-off date, i.e. reconciliation reflects trades executed on/before this
date and outstanding on this date
 Executed: date and time at which the reconciliation was performed
Trade counts
 Match: the trades which matched perfectly with counterparty data
 Partial: trades which matched perfectly with the exception of product IDs (in case the
reporting sides chose different product taxonomies)
 Mismatch: your trades for which discrepancies were detected
 Pending: the trades for which no counterparty details were found (with matching UTI and
LEIs)
 Alleged: counterparty trades for which no corresponding submission from the user's
organisation was found
 Error: trades which had to be excluded from reconciliation because of (a) duplicated
UTIs or (b) incomplete data fields
Central Matching Service User Guide v1.13
Page 70 of 95
‘Click for Help’ on this screen for details located above the report screen (Figure 1 eRR >
Reconciliation - Excel Report Button). Select the ellipsis […] to expand the screen.
Figure 106 eRR Click For Help
eRR > Reconciliation
Select the appropriate date and download the excel file
Figure 107 eRR Reconciliation - Excel Report Button
Figure 108 eRR Reconciliation Report - Matched Positions
MTM Reconciliation & CSV Valuation UploadEMIR valuation data is included in
reconciliations, the nightly report features a separate MTM discrepancy overview. Additional
trade and valuation data can be uploaded as alleged positions supplementing the existing
EMIR reporting data; thus reconciliations can be extended to counterparties who do not
participate in eRR EMIR reporting. Once the file has been uploaded the user can rerun the
report to include the valuation data.
Central Matching Service User Guide v1.13
Page 71 of 95
Figure 109 CSV Data Upload & Rerun
7.6. Retry Queue
All eRR submissions which are validated by eRR, but fail during the mapping or enrichment
process, are added to the Retry Queue.
If the error lies in the CpML submission document or the organisation’s eRR set up, a
BoxResult message will be returned to the sender organisation with an error message.
For example:
UTI Enrichment Error:
- No namespace found. Please contact the EFETnet support.
[AgentOrSender=123456ABCDEFG123HI789, procId=18739]
If the error is the result of incorrect mapping or enrichment, the EFETnet Service Team will
seek to resolve the issue. Reasons for these submission failures may include:
 LEI to EIC code mapping
 Exchange product codes
The EFETnet Service Team will actively monitor this queue for process errors, and once
resolved, the trade report will be resubmitted to eRR for validation.
The Retry Queue is only visible to FHA users (EFETnet Service Team).
8. The eXRP Menu
For Organisations participating in eXRP, the eXRP menu will be accessible to Operators
(OPs) and Master Operators (MOs).
The tracking screens for clearing transactions include:
 Dashboard – the main tracking screen for clearing transactions → see section eXRP
Dashboard
 Deal Finder – a search screen enabling users to find a specific transaction → see
section eXRP Deal Finder
Users can access a configurable and exportable trade details list from both screens. This
list also contains error messages → see section eXRP Deal Finder
Additionally, ‘Mail Alerts’ are issued by eXRP for tracking the clearing process, informing
users of exceptions in real-time → see section Mail Alerts
Screens and functions differ slightly depending on the role of the user's organisation in the
eXRP process:
Central Matching Service User Guide v1.13
Page 72 of 95



Brokers submit trades for clearing to eXRP on behalf of the trade counterparties.
CRAs (Clearing Registration Agents) receive and process clearing requests from
eXRP and forward them to the clearing system of the CA (Clearing Agent, a.k.a. clearing
house).
Traders can monitor trades submitted by brokers on their behalf. Traders are the
buy/sell counterparties to clearable trades.
8.1. eXRP Dashboard
The eXRP dashboard is the main tracking screen for clearing transactions.
Figure 110 eXRP Dashboard
The eXRP Dashboard shows all clearing transactions for the user's organisation which have
been processed in the past 31 calendar days. Clicking on a number in the Dashboard matrix
will bring up the corresponding trades in the eXRP trade detail list view → see section eXRP
Deal List.
CMS deletes eXRP transaction information for each trade 35 days after it has been
received and only retains audit information about processing the transaction.
8.1.1. Filters and Refresh
The 'Refresh' button updates the dashboard matrix.
Subsets of clearing transactions can be displayed by using the filter function, giving users
the option to save their filters using the 'My Filter' function. For more information about how
to operate and save filters, please refer to the eCM sections: Auto-Populated Filters and My
Filters.
Within the eXRP Dashboard:
 Broker users can filter by CRA Party, Trader Party, and product code
 CRA users can filter by Broker Party, Trader Party, and product code
 Trader users can filter by CRA Party, Broker Party, Counterparty and product code
Central Matching Service User Guide v1.13
Page 73 of 95
8.1.2. Columns: Update Time
The columns signify when the last activity (i.e. state change) took place for the transaction.
The criterion is the 'last update' timestamp available for each transaction. The 'time buckets'
are:






Today (0-1h): transaction updated today, less than an hour ago
Today (1-3h): transaction updated today, 1-3 hours ago
Today (earlier): transaction updated today, more than 3 hours ago
Yesterday: transaction last updated on the previous calendar day
2-31 days go: transaction last updated 2-31 calendar days ago
Total: sum of previous columns
8.1.3. Rows: Clearing State
The matrix below defines the clearing states listed in order of their occurrence in the
process. States in black are transitory or desired final states, while states in red signify
actionable errors.
Mail Alerts
Users of broker and CRA organisations can opt to receive instant email alerts whenever a
transaction reaches a critical state. Find the details in section Mail Alerts.
State
Rejected EXRP
Pending EXRP
Pending CRA
Error
Meaning
The CMS has rejected an
invalid broker document
(XBN). Examples: mandatory
information missing,
amendment not allowed,
refers to unknown clearing
party.
Temporary state: the CMS
has accepted the broker
submission and is trying to
issue a clearing request
(CRQ) to the clearing
registration agent (CRA).
Action
Broker to investigate error
reason (found in deal list or
mail alert) and amend the
submission.
Typically no action. State
usually lasts for 1-3 seconds.
Should trades remain in this
state for 1 hour or more, a
communication problem
exists between the CMS and
the CRA. In this case contact
the support team.
The CRA has received the
Typically no action. State
clearing request. CMS is
usually lasts for a few
waiting for the CRA to accept seconds but can last longer if
or reject the submission.
the CRA has a (semi-)manual
Hint: CRA users can
verification process in place.
subscribe mail alerts for
Broker to inform a CRA
transactions reaching this
contact in case processing
state.
appears to take too long.
The CRA has rejected the
Broker to investigate error
clearing request. No
reason (found in deal list or
transaction has been opened mail alert) and (1) amend the
in the clearing system. This is submission or (2) use the
Central Matching Service User Guide v1.13
Page 74 of 95
State
Pending CA
Meaning
typically due to invalid product
or party references, sending
outside business hours,
missing agreements.
The CRA has verified the
clearing request and has
started a clearing transaction.
Action
"abort" function to give up on
clearing the deal.
Cleared
Refused
Deal has been cleared.
The clearing system has
refused clearing.
Typically no action. Wait for
clearing system to return with
the clearing outcome
("Cleared" or "Refused").
Duration of this phase varies
depending on the underlying
clearing process. Broker to
inform CRA in case
processing appears to take
too long.
No action.
CRA user to verify whether
the automatic clearing refusal
1.
a. was justified, in
this case return an
"Aborted"
response to the
CMS or
b. can be overridden,
in this case return
a "Cleared"
response to the
CMS
Aborted
Clearing either aborted by
broker (see state "Error") or
CRA (see state "Refused").
Typically no action. Broker
can retry clearing by sending
an amendment.
8.2. eXRP Deal Finder
The eXRP Deal Finder can be used to search for a specific deal. Enter the search criteria
and press the appropriate search button to return the results list described in the next
section eXRP Deal List.
Figure 111 eXRP Deal Finder
Central Matching Service User Guide v1.13
Page 75 of 95
8.2.1. Searching for Reference Numbers
The ID fields on the left hand side allow a user to search for between 1-50 reference
numbers
Copy and Paste from Spreadsheets
You can copy and paste a list of reference numbers directly from your spreadsheet
application into the appropriate search box to search for multiple deals at the same time.
The following reference numbers can be searched for:
 Trade Ref / Deal ID: finds transactions which contain the given IDs in either the ‘Deal ID’
or the broker-assigned ‘Trade Reference ID’ field.
 Clearing ID: finds transactions by the CRA-assigned ‘Clearing ID’ (which are transmitted
in clearing responses sent by the CRA).
 Document ID: finds transactions by the ‘Document ID’ of the broker submission (XBN
document) or clearing request (CRQ document).
8.2.2. Searching by General Properties
The right hand side of the Deal Finder is for searching for transactions that fulfil the selected
criteria. In addition to the filters available in the eXRP dashboard, it is possible to define:
 The Clearing House (identified by EIC code)
 the eXRP state
 the exact Unit Price
 the Trade Date range
 the Submission Date range
Use the Search button in the lower right corner to start a search. Use the ‘Reset’ button to
clear the search criteria. Find more information on filters in the eCM-related sections:
 operating filters and date pickers → Filters
 saving queries → My Filters
8.3. eXRP Deal List
The deal list displays details for clearing transactions selected in the Dashboard or searched
for in the Deal Finder. The deal list displays:
 the status and error information for transactions
 icons to view clearing documents (broker submission, clearing request)
From the deal list it is possible to:
 trigger manual actions on transactions (given the appropriate user permissions)
 export transactions to Excel, from both the Dashboard and Deal Finder
 configure columns included within the display and to rearrange their order
Central Matching Service User Guide v1.13
Page 76 of 95
Figure 112 eXRP Deal List
8.3.1. Information in the List
The following information is available for each trade in the detail list:
Field
Clearing ID
CRQ Document ID
CRQ Document Version
Error Type
Error Details
Last update
State
Submission Date
Submission Timestamp
Description
clearing transaction reference returned from
clearing system
document reference for the clearing request
issued by the CMS (empty if not issued)
version number of clearing request
(increased when amending)
error category (empty if no error was
reported)
error code and description (empty if no error
was reported)
date and time at which the last update (state
change) occurred
clearing state
day on which the broker first submitted the
transaction
day and time at which broker first submitted
the transaction
Table 1 Progress Information (set by the CMS)
Field
Anonymous
Automatic Execution (Buyer/Seller)
Buyer EIC
CRA Product Code
Clearing Account ID (Buyer/Seller)
Central Matching Service User Guide v1.13
Description
“yes” for anonymous trades / “no” otherwise
"yes" = screen trade, "no" = voice trade
buyer party (identified by EIC code)
product identifier as required by the CRA
buy/sell side clearing account (only
applicable to some CRA parties)
Page 77 of 95
Field
Clearing House EIC
Contact (Buyer/Seller)
CRA EIC
Deal ID
Delivery Start
Delivery End
Lots
Manually Confirmed (Buyer/Seller)
Seller EIC
UMTF Contact
UMTF Document ID
UMTF Document Version
UMTF EIC
UMTF Trade Reference ID
UMTF Trade Timestamp
Unit Price
Description
clearing house at which CRA clears (as EIC
code)
full name of executing trader
clearing registration agent to whom the
request is routed (as EIC code)
globally unique trade identifier
day of product delivery (start date)
day of product delivery (end date)
number of lots (contracts) traded
whether buy/sell side verified and affirmed
the deal prior to clearing registration
(yes=affirmed, no=not affirmed / unknown)
seller party (identified by EIC code)
full name of executing broker (voice deals) or
responsible contact (screen deals)
document reference of the broker submission
document version of the broker submission
(increased when amending)
broker party (identified by EIC code) =
submitter
trade identifier as assigned by the broker
(UMTF)
trade execution time registered by broker
(UMTF)
price per lot
Table 2 Broker-Provided Transaction Details
8.3.2. Interactive Icons for Manual Actions / Document Details
In addition to the columns described in the previous section, the detail list contains the
interactive icons as shown below:
Figure 113 Buttons for Manual Actions
8.3.3. Document Detail Views
Interactive Icons will take the user to the latest version of:
 the broker submission (XBN)
 the clearing request (CRQ) issued to the CRA
Both documents are available in a screen-friendly form (HTML format) or in machinereadable form (XML format).
Central Matching Service User Guide v1.13
Page 78 of 95
Abort Transaction in State 'Error' (MO of broker organisation only)
Figure 114 Abort Transaction in State Error
For all transactions in state ‘Error’, an MO of a broker Organisation will have the option to set
the state to ‘Aborted’ (thus marking it as non-actionable). The user should select the ‘Abort’
button, followed by ‘Yes – Abort’. The transaction is then promoted to state ABORTED.
Figure 115 Abort Clearing
8.3.4. Exporting and Adapting a List of Transactions
The icons at the top right of the results list enable a user to export and customize a list of
transactions:
Figure 116 Export and Customise Icons
Central Matching Service User Guide v1.13
Page 79 of 95
Figure 117 Customising column settings



Export: transports an on-screen list of transactions to an Excel spreadsheet
Customize: allows a user to adjust their ‘Personal Column Settings’. Follow the onscreen instructions to add/remove columns and to change their order. Press ‘Save
Changes’ to confirm the selection and ‘Back to Deal List’ to return to the previous screen.
Show ‘X’ entries: allows the user to choose the number of transactions displayed on a
page. The user can enter a number between 1 and 100, pressing ‘Enter’ to confirm their
selection.
9. Preferences
9.1. Account
In the 'Account' section a user can view their personal details, edit their job title,
phone/mobile number and update methods of contact. Only a user with UA rights can edit a
User Name, First/Second Name and Email Address. For more information on how to do this
as a UA please refer to section ‘User Accounts’. This information is also visible in the
contacts section (See section Contacts).
Central Matching Service User Guide v1.13
Page 80 of 95
Figure 118 Personal Account Data
9.2. Change Password
This tab allows a user to change the password for their account and informs the user when
the password was last changed. Passwords will only be accepted if they meet the
requirements of the password policy – see screenshot below. Passwords must be changed
every 90 days for security reasons (an automatic prompt will appear).
User Accounts are automatically locked by the system if it has not registered any login
attempts for 40 days.
Figure 119 Change your password
Central Matching Service User Guide v1.13
Page 81 of 95
9.3. Mail Alerts
9.3.1. Global Mail Alert Settings (UA Only)
Users can opt in to receive mail alerts, sent from CMS when the state of another user’s
account changes. In the Mail Alert Settings screen the UA can view:
 User Name – Name of the user as it appears on CMS (also their log in name).
 Real Name – Real name of the user.
 User State – Displaying one of three states; Active, Inactive and Locked. These can be
changed by the UA within the Administration section (See section User Accounts).
 User State Changes – This shows whether the selected user will receive email alerts
relating to state changes for other users within their Organisation e.g. when a user
account has been locked.
Figure 120 Mail Alert Settings
9.3.2. eCM Mail Alert Settings (MO Only)



User Name – Name of the user as it appears on CMS (also their log in name).
Real Name – Real name of the user.
User State –Displaying one of three states; Active, Inactive and Locked. These can be
changed by the UA within the administration section (See section User Accounts).
Figure 121 eCM Alert Settings
Central Matching Service User Guide v1.13
Page 82 of 95
9.3.3. eXRP Mail Alert Settings







User Name – Name of the user as it appears on CMS (also their log in name).
Real Name – Real name of the user.
User State – Displaying one of three states; Active, Inactive and Locked. These can be
changed by the UA within the administration section
XBN Rejected – This indicates whether the selected user will receive email alerts when
an XBN fails validation and was rejected by the CMS.
CRQ Rejected – This indicates whether the selected user will receive email alerts when
a clearing request is rejected by the registration agent
Clearing Refused – This indicates whether the selected user will receive email alerts
when the clearing system refused clearing the trade
Aborted by CRA – This indicates whether the selected user will receive email alerts
when the registration agent verifies the clearing refusal and declares the refusal final
Figure 122 eXRP Mail Alert Settings
9.3.4. Alerts for Broker (UMTF) Organisations
Intended Receiver*
System support
This suggests an
implementation or
configuration problem in the
broker system.
Business users, to escalate to
the system support if not due
to agreement / master data
settings.
Event
XBN Rejected
What happened?
A broker submission (XBN)
failed validation and was
rejected by the CMS.
CRQ Rejected
A clearing request was
rejected by the registration
agent. Causes include:
unsupported product code,
missing agreement setup at
CRA, out of business hours.
The clearing system refused Business users
clearing the trade.
The registration agent verified Business users
the clearing refusal and
declared the refusal final. At
this point the brokers can give
up or submit an amendment.
Clearing Refused
Aborted by CRA
Central Matching Service User Guide v1.13
Page 83 of 95
9.3.5. Alerts for CRA Organisations
Event
Pending CRA
CRQ Rejected
Pending CA
Clearing Refused
CRP inconsistent
What happened?
Intended Receiver*
A clearing request has arrived Optionally sent to business
for pre-validation
users if eXRP clearing
request validation is not fully
automated in your system.
The clearing request failed
Optionally sent to business
pre-validation in the user’s
users to escalate to the
system. Causes include:
system support if not
broker used unsupported
explicable.
product codes; an agreement
is not set up; out of business
hours.
A clearing request has been Optionally sent to business
pre-validated, clearing
users if clearing approval is
decision outstanding
not fully automated in your
(cleared/refused)
system.
The clearing system refused Business users
clearing the trade. Decision
needed as to whether clearing
can be overridden (clear
manually) or not (abort).
The clearing response sent
System support/EFETnet
back from the user’s system support -a serious integration
to the CMS is invalid. eXRP problem with the CMS exists
could not understand the
response
*
Hints on when to use the alert. For more information on how to deal with errors see
section eXRP Dashboard
10. Administration
10.1.
Organisations
An Organisation Group is a logical grouping of Organisations referring to the same legal
entity. Within this Organisation Group there may be a number of subordinate Organisations
(e.g. one Organisation Group ‘ALPHA’, may include Organisations ‘ALPHA ONE’ and
‘ALPHA TWO’).
An Organisation is the entity which matches confirmations and/or submits to for eRR,
associated with a single EIC code.
The section 'Organisations' under the Administration tab displays a list of all Organisations
within an Organisation Group, allowing a user to view:
 Organisation Group – This is the name of the organisation. It can encompass more
than one subordinate organisation. This contains information display name, EIC code,
eCM Role, eXRP Role, Legal Name and if the entity is active
Central Matching Service User Guide v1.13
Page 84 of 95





Display Name – This is the name of the Organisation displayed in CMS. It usually bears
resemblance to the legal name for identification purposes
EIC Code – The Energy Identification Code assigned to an Organisation for eCM
Partner ID – This is the internal system ID for the Organisation. This usually includes the
EIC code preceded by "BE-" (for CMS Live)
Legal Name – This is the legal name of the Organisation, as registered with ENTSOe ,
to which the EIC code has been assigned
Active – This shows the status of the Organisation. An Organisation cannot be deleted
from CMS, however it can be deactivated by an FHA user
Figure 123 Organisation View
10.1.1.
Amend an Existing Organisation
By navigating to CMS > Administration > Organisations, a user with the User Administrator
role is presented with a view of all Organisations within their Organisation Group. A UA can
edit the Business and Technical Contacts for an organisation, which are visible to all other
CMS users in CMS > Help > Contacts.
Figure 124 Amending an Organisation
Central Matching Service User Guide v1.13
Page 85 of 95
10.1.2.
Creating a New Organisation
To add a new Organisation, contact the CMS Service Team who will provide the appropriate
form to complete (Details in section Support). Please note that in order to add a new
Organisation, authorisation must be obtained from the Primary or Secondary Contact at
Organisation Group level.
10.2.
User Accounts
This section displays all user accounts within an Organisation. The following are displayed:
 Organisation Group – This is the name of the organisation. It can encompass more
than one subordinate organisation.
 User Name – The name assigned to the user for accessing the CMS.
 Real Name – This is the user's full name.
 User State –This is the state of the user’s account. There are 3 options:
o Active – This user account is active and receives alerts
o Locked – This user has a locked account and cannot access the CMS until it is
unlocked by a UA (e.g. if a user has failed to enter their password correctly 3
times their account will be locked or a login 40+ days after the previous login).
But will still receive alerts.
o Inactive – The user’s account has been deactivated by the UA (e.g. if the user
has left the company)
Business Note
3 wrong consecutive password entries or a login 40+ days after the previous login
are two different events that lead to the locking of an account.
At login the following happens:

Password has not been changed for 90+ days the user is redirected to a forced
password change

Password has been reset by FHA / UA and is only temporary, the user is redirected
redirect to a forced password change.
Central Matching Service User Guide v1.13
Page 86 of 95
Figure 125 User Accounts
This screen allows a UA to unlock and reset passwords. A reason must be given for
changing a password or unlocking an account, and this function is monitored by FHAs for
security reasons. The user will only use the new password on their first login in to CMS.
Once entered, the user is prompted to enter a new password of their choice, which must
adhere to the 'Password Policy Requirements', as stated on the password unlock screen.
10.2.1.
Add User Account
A UA can create a new user account for a new user within their Organisation Group. The
fields marked with an asterisk are mandatory fields (e.g. valid email address).
Central Matching Service User Guide v1.13
Page 87 of 95
Figure 126 Adding a New User
A UA has authority to edit details in another user’s account, which cannot be changed by the
user themselves. A UA can edit:
 User Name
 First Name/Second Name
 Email Address
Figure 127 Editing a Current User
10.3.
User Permissions
Users are categorised according to permission levels within the system. As a result, certain
screens will be accessible depending on the role(s) to which the user has been assigned:
 OP – (standard) Operator
Central Matching Service User Guide v1.13
Page 88 of 95
o


Operators are allowed to access trade data in CMS for eCM. They have no
access to the eRR menu.
Master Operators have all Operator rights and, in addition, access to privileged functions
such as:
o (eCM) tools to change eCM process settings for their organisation
o (eRR) the ability to add/edit Standing Instructions
o (eXRP) the ability to decide which users receive which email alerts from the CMS
o (eXRP / brokers only) to option to manually declare failed clearing transactions
"ABORTED" and thus mark them as non-actionable
UA – User Administrator
o User administrators maintain access rights for users within their Organisation
Group, for example, they can add/disable users, reset passwords, amend user
details and configure an individual’s user roles.
10.4.
Assign User Roles
CMS users are categorised by 'User Role'. This role determines what a user is able to view
and access within the CMS. Display screens may appear differently depending on the role to
which the user has been assigned. → See section User Roles
A UA can assign roles to a user by selecting the desired role, turning the icon from light blue
to dark blue (e.g. if ‘Alpha User’ is an MO then the box should be highlighted dark blue). A
user may be assigned to more than one role, and may have different roles for different
Organisations, within the same Organisation Group (e.g. Alpha User may be a MO of
ALPHA ONE and an OP of ALPHA TWO).
Business Note
A user account which has been created but not assigned either a MO or OP user role will
allow the user to log in to CMS, but will not have access to any organisational information
(i.e. dashboard, deal finder etc.)
Summary of User Roles Against Function
Function
Account
Management
add/edit
MO
OP
Central Matching Service User Guide v1.13
UA
FHA*
Menu Section
√
Administration >
Page 89 of 95
Function
organisations
configure
organisation
contacts
add/edit user
accounts
change user
account
activation
reset user
passwords
edit user
privileges
receive user
account alerts
eCM
Configuration
matched
products (view)
matched
products (edit)
broker match
restrictions (view)
broker match
restrictions (edit)
advanced
process settings
(view)
advanced
process settings
(edit)
personalize
confirm list
manage eCM
mail alerts
eCM
Confirmation
Process
search trades
(Dashboard)
search trades
(Deal Finder)
eCM lite: enter
trade
eCM lite: amend
trade
MO
eCM lite: cancel
trade
√
display
confirmation
√
√
OP
√
UA
FHA*
√
(√)
√
(√)
√
(√)
√
(√)
√
(√)
√
(√)
(√)
√
(√)
√
(√)
√
√
√
(√)
√
√
Menu Section
Organisations
Administration >
Organisations
Administration >
Users
Administration >
Users
Administration >
Users
Administration >
Assign User Roles
Preferences > Mail
Alerts > Global
eCM > Settings >
Products
eCM > Settings >
Products
eCM > Settings >
Broker Restrictions
eCM > Settings >
Broker Restrictions
eCM > Settings >
eCM 4.0 Process
eCM > Settings >
eCM 4.0 Process
√
(√)
eCM > Settings >
Column Order
Preferences > Mail
Alerts > eCM
√
√
(√)
eCM > Dashboard
√
√
(√)
eCM > Deal Finder
√
√
eCM > Enter Trade
√
confirmation list,
column: Button
"eCM lite Controls"
confirmation list,
column: Button
"eCM lite Controls"
confirmation list,
column: Button
"Document"
√
Central Matching Service User Guide v1.13
(√)
Page 90 of 95
Function
display audit trail
MO
√
OP
√
UA
FHA*
(√)
find counterparty
near matches
√
√
(√)
find broker near
matches
√
√
(√)
annotate trades
√
√
(√)
hide trades
√
terminate trade
√
export
confirmations
√
√
(√)
Menu Section
confirmation list,
column: Button
"Audit Trail"
confirmation list,
column: Button
"Counterparty Near
Match"
confirmation list,
column: Button
"Broker Near Match"
confirmation list,
column: Button
"Notes"
confirmation list,
column: Hide
Indicator
confirmation list,
column: Button
"Terminate Deal"
confirmation list,
button "Export"
*FHA role is only applicable to the Service Team
11. Help
11.1.
Contacts
The "Contacts" screen displays contact details for all primary and secondary users within all
organisations on the CMS. The columns show:
 Organisation group
 Display Name
 Legal Name
 EIC Code
 eCM Role – The Organisation's role in the eCM process (none, trader, broker)
 eXRP Role – The Organisation's role in the eXRP process (none, trader, broker, CRA =
clearing registration agent)
 Primary Contact – initial person to contact for the organisation
 Secondary Contact – person to contact if primary contact is not available
Central Matching Service User Guide v1.13
Page 91 of 95
Figure 128 Organisation Contact List
11.2.
Support
For support, please contact the CMS Service Team on the details below:
Help Desk
Monday to Friday from 08:00 to 18:00 (UK Time)
Email → [email protected]
Phone +44 (0) 1372 860720 (Standard support hours)
Phone +44 (0) 7920 797 123 (Out of hours support – for P1 issues only)
Details are also listed on the CMS page Help > Support.
Figure 129 Support Page
Central Matching Service User Guide v1.13
Page 92 of 95
12. Further Documentation and
Downloads
12.1.
EFET Website
Further information can be found at the European Federation of Energy Trader's website: →
www.efet.org including detailed information on the eCM standard v4.0 under the tab
"standardisation". Hub Codes and Delivery Point Areas can be found in the in the EFET
Static Data Tables.
12.2.
ENTSOe Website
This website provides you with a list of all legal names and EIC codes for all registered
organisations within Europe:
ENTSOe
It is possible that some EIC codes are not published on ENTSOe website for the following
reasons:

There is one Central Issuing Office (ENTSOe) and (almost) each country a Local
Issuing Office (LIO)

If a counterparty will only act in national market, then its EIC shall not be published on
ENTSOe. This code shall only be published on the website of the national LIO. E.g.
German company will only act on German market, then this code will only be
published on the websites of BDEW (German LIO).
12.3.
Support Team Help Desk Tool
You will need to be a registered user to access the Helpdesk tool. An individual can register
by following the instructions on the Helpdesk homepage:
http://hosted.unipresssoftware.com/cgi-bin/WebObjects/HostedHelpdesk.woa/wa?id=91
Individuals can use the Helpdesk tool to log issues with the CMS Support Team. Helpdesk
'tickets' are raised for each new issue. Frequently Asked Questions are also available on
the Helpdesk, providing answers to the most common issues reported to the CMS Support
Team.
13. Appendix 1 – Offline reports
At the start of each month the CMS Service Team issues a series of reports to each
Organisation Group.
13.1.
Billing Details Report
The Billing Details Report is a break-down of all confirmations matched by an Organisation
during the previous calendar month, including details of each individual match.
Central Matching Service User Guide v1.13
Page 93 of 95
The Billing Details Report contains the following information:
Org Group – The Organisation Group name
Org EIC Code – The EIC code of the Organisation within the Organisation Group which is
party to the match
Match Timestamp – The date and time of the match
Match Type –The type of match of each trade which can be one of the following three
options:
ECM_BR_ONLY_MATCH – A bilateral match between a CMS trader and a CMS broker
only.
ECM_CP_MATCH – A bilateral match between a CMS trader and another trader (CMS or
P2P).
ECM_BR_TRI_MATCH – A trilateral broker match, where there also exists a trader match
(an existing ECM_CP_MATCH).
Partner EIC Code – Either the CMS or P2P column will be populated with the counterparty
EIC or Broker Code.
Trade ID – The trade ID as specified by the Organisation Group (i.e. 'Your' EIC Code).
13.2.
Matched Product Matrix
The Matched Product Matrix identifies which products have been matched on the CMS since
go live (September 2011), by all organisations currently electronically matching trades. The
matrix is sent out on a monthly basis with the Billing Details Report.
The matrix contains three tabs:
“MATRIX”: a list of all organisations currently electronically matching trades. Each
organisation has been plotted against the ‘Transaction Type’, ‘Commodity’ and ‘Market’
which they match with CMS counterparties.
“NEW_PROD”: a list of only products newly added to the portfolio of confirmed products for
an individual organisation, within the last month.
“MKT_KEY”: a list of all the country codes in the “Market” and the corresponding country.
The Matched Product Matrix can be used to identify new products to confirm with other
counterparties.
13.3.
Billing Report Statistics
The Billing Report Statistics contain the matching volumes and other metrics for each
individual Organisational Group. The report is firstly sent with blind rankings for all
organisations, followed by an email confirming the individual organisation’s own rank. The
statistics include:
Confirmation Volumes
The table shows confirmation match volumes on the CMS for the previous calendar month
by ‘Organisation Group’, for traders and for brokers. Each table is sorted by Total Matches
in descending order.
Time to Match – All Matches - Traders
The table shows the time to match as a percentage of the total matches for the previous
calendar month by ‘Organisation Group’ for all matches performed on the CMS. A match
delay of 0 means a confirmation was matched on the trade date T, a match delay of 1
means the confirmation was matched on T+1, etc. The column <=2 days shows the
percentage of confirmations which matched within 2 days of T (i.e. the sum of the 0, 1 & 2
columns). The table is sorted by Match Delay <=2 in descending order.
Central Matching Service User Guide v1.13
Page 94 of 95
Time to Match – Counterparty Matches - Traders
The table shows the time to match as a percentage of the total matches for the previous
calendar month by Organisation Group for all counterparty matches performed on the CMS.
Time to Match – Broker Only Matches - Traders
The table shows the time to match as a percentage of the total matches for the previous
calendar month by Organisation Group for all broker only matches performed on the CMS.
Note that not all traders match with brokers, hence there are fewer lines in this table.
Time to Match – Trilateral Broker Matches - Traders
The table shows the time to match as a percentage of the total matches for the previous
calendar month by Organisation Group for all broker leg matches as part of a trilateral match
performed on the CMS. Note that not all traders match with brokers, hence there are fewer
lines in this table.
Time to Match – All Matches - Brokers
The table shows the time to match as a percentage of the total matches for the previous
calendar month by Organisation Group for all matches performed on the CMS. A match
delay of 0 means a confirmation was matched on the trade date T, a match delay of 1
means the confirmation was matched on T+1, etc. The column <=2 days shows the
percentage of confirmations which matched within 2 days of T (i.e. the sum of the 0, 1 & 2
columns). The table is sorted by Match delay <=2 in descending order.
Time to Submit – All Matches - Traders
The table shows the time taken to submit a confirmation against the trade date as a
percentage of the total matches for the previous calendar month by trader for all matches
performed on the CMS. A submission delay of 0 means a confirmation was submitted on the
trade date T, a submission delay of 1 means the confirmation was submitted on T+1, etc.
The table is sorted by Submission Delay 0 in descending order.
Time to Submit – All Matches - Brokers
The table shows the time taken to submit a confirmation against the trade date as a
percentage of the total matches for the previous calendar month by broker for all matches
performed on the CMS. A submission delay of 0 means a confirmation was submitted on the
trade date T, a submission delay of 1 means the confirmation was submitted on T+1, etc.
The table is sorted by Submission Delay 0 in descending order.
Central Matching Service User Guide v1.13
Page 95 of 95
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement