Different EMIR Reporting Methods

1. Trade Level / Trade Lifecycle Reporting

Trade Lifecycle means reporting one Trade ID per order with no concept/reporting of a position. All subsequent Valuation and Collateral updates take place at the trade level. This system is most commonly used for reporting under MT4 as well as physical products such as FX Forwards.

So, what does trade lifecycle look like?

Example
On 01/01/2020, I open a CFD trade, buying 1 contract of FTSE 100 Cash Index at a price of 6000.
In the EMIR report this is reported with:

• Action = ‘N’ (for New)
• Level = ‘T’ (for Trade)

Any subsequent modifications/valuations/collateral updates are made at the trade level.

On 02/01/2020, I modify the Maturity Date with my counterparty.  Therefore, I would submit an Action of ‘M’ = ‘Modify’ and the updated Maturity Date.

On 03/01/2020, I terminate the contract early (not at the maturity date).  Therefore, I would submit a report with Action of ‘C’ = ‘Early Termination’ and the updated Maturity Date.

2. Position Level / Position Lifecycle Reporting

Position Level/Lifecycle reporting means you report all individual transactions as compressed into a position, reporting the additional end of day Open Positions at Position level.

This system works well where Partial Closes are used as you can report all single executions individually at trade level as well as report any modifications/updates at Position level.

So, what does the Position Lifecycle reporting method look like?

Example
On 01/01/2020, I open a CFD trade, buying 10 contracts of FTSE 100 Cash Index at a price of 6000.

In the EMIR report this is reported with:

• Action = ‘P’ ( for Position Component)
• Level = ‘T’ (for Trade).

Therefore we need to create two reports for 01/01/2020:

1. The compressed trade
2. The open/new position

1.  This compressed trade contains a Termination Date, as upon compression the trade is terminated.

2.  At the end of the day, my position of 10 contracts in FTSE 100 is still open so I report a New Position with an EOD Valuation. The UTI has been updated to be the Position UTI.

On 02/01/2020, I partially close my position by selling 4 contracts of FTSE 100 Cash Index at a price of 6500.

Therefore we need to create two reports for 02/01/2020:

1. The new compressed trade
2. The revised Position

1.  I will report this trade as a new compressed trade.

2.  At the end of the day, I have a position of 6 contracts long in the FTSE 100. As the number of contracts have changed in my Position from yesterday, I need to send a Modification to my position.  Therefore, I include the number of contracts I have left open as the Quantity and update the Notional Value.

All Valuations made are at the Position level.

3. Position Level / Position Lifecycle Reporting with aggregation

Position Lifecycle with aggregation means that TRAction will aggregate your EOD open positions by Counterparty and Instrument (similar to Position level reporting).

So, what does Position Lifecycle with aggregation look like?

Example
On 01/01/2020, I open two CFD trades, one buying 10 contracts of FTSE 100 Cash Index at a price of 6000, another buying 20 contracts of FTSE 100 Cash Index at a price of 6500.
I report both as compressed trades.

Both positions remain open at the end of the day, so I aggregate my two positions and use the Volume Weighted Average Price (VWAP) in the price field.

Any subsequent Valuations and collateral updates are made are at the Position level.

How does ESMA identify the different reporting methods?

Reporting at trade level is identified by using the field and value, Level = ‘T’ in the reports

Reporting at Position level is identified by using the field and value, Level = ‘P’ in the reports

What do I need to consider before selecting or changing methods?

Clients must also be aware that under EMIR there is a Pairing & Matching obligation which requires you to agree on a method of reporting consistent with your counterparty.  Please refer to our Pairing & Matching article for more information on this.

Are there advantages in moving to Position level reporting?

• Position level reporting is more likely to coincide with how your liquidity providers report
• It is easier to reconcile between raw data files and the submitted reports
• May result in reduced costs due to less valuation and collateral
• Increase efficiency at various stages of reporting due to reduced file sizes
• Simpler to account for and report different lifecycle events

If you have any questions or would like to report under a particular method please let us know.