Please insert at least 3 characters

FAQs on transaction reporting – Question II.2.2.4

How to correctly link a Gas Sleeve Spread executed voice by a broker.

We have the following trades resultant from a voice traded Sleeve Spread between two customers using a Sleeve:

Trade 1: Cust1 Vs Sleeve 1

Trade 2: Sleeve 1 Vs Cust2

Trade 3: Cust2 Vs Sleeve 1

Trade 4: Sleeve 1 Vs Cust1

The question is how to link the legs of the trades.

We suggest that the trades should be linked in the following manner:

We have used the combined logic from the Sleeve trading example and Dirty Spark Spread example.

Trade1 Cust 1 Vs Sleeve1
  Linked ID of  Trade 4   Linked ID of Trade 2
       
Trade 2: Sleeve1 Vs Cust2
  Linked ID of Trade 1   Linked ID of trade 3
       
Trade 3: Cust 2 Vs Sleeve 1
  Linked ID of Trade 2   Linked ID of Trade 4
       
Trade 4: Sleeve 1 Vs Cust 1
  Linked ID of Trade 3   Linked ID of Trade 1

Answer:

When a trade occurs across multiple products due to the nature of the product, e.g. a product which is a spread of two or more products falling under the scope of REMIT, a trade report for each product has to be reported and the different trades are to be linked to each other when they are executed simultaneously on the Organised Market Place /platform. For example, Dirty Spark Spreads for a trade that involves electricity and gas: the two contracts are reported separately, with one leg for the electricity and one leg for the gas trade. The two legs, i.e. gas and electricity trades, need to be linked together through this field.

Same applies to Physical Swaps for a trade that involves two gas or electricity trades: a geographical physical swap involves two trades, e.g. selling gas in a particular delivery point and buying it in another delivery point. Both trades have to be reported separately and linked together through this field if they are traded simultaneously.

The whole chain of trade reports and the Linked Transaction ID fields should look like the example (3.20) in Annex II to the TRUM.

Last update: 08/09/2015   RSS_Icon Subscribe to this Page’s RSS