Please insert at least 3 characters

FAQs on transaction reporting – Question II.3.1.17

REMIT Implementing Act Article 5(1)(b) and Annex, table 1 data field 31 (Unique transaction ID), table 2 data field no 11 (contract ID).

We understand that market participants need to agree on their method of generating a Contract ID – this can include using the UTI algorithm provided by ACER. However, what should a MP do if its counterparty provides the ID after T+1 or T+30 or indeed not at all and they have not agreed to use the ACER algorithm? This is particularly of concern as the use of the ACER algorithm is not mandatory.

Under REMIT, phase 2 transactions need to be provided either under table 1 (for contracts that specify and outright price and volume) or under table 2.

In submitting a table 1 or 2 report the UTI field must be completed. However, it is possible a counterparty, who is not using the ACER algorithm, may not provide their UTI to us to enable us to report in the necessary timescales.

We are engaging with our CPs to ensure this does not occur but it is always a risk.

Our preferred approach is to:

1) Submit a temporary UTI, calculated based on the ACER algorithm.

2) Once we have received the UTI from the CP an ‘error’ report will be submitted to remove the previous report and a ‘new’ transaction report with the correct UTI will be submitted.

As an alternative to 2) we are also happy to simply submit a modify report if that is preferable to ACER.  Can ACER please confirm this is acceptable?


Answer:

Market participants should submit a temporary UTI, then once they have received the UTI from their counterparty, a ‘Modify’ report will be submitted to modify the previous report recalling the old UTI. In the schema there is a field called “AdditionalUtiInfo” field where the old UTI should be reported in the modified report. e.g.

Using Schema Table 1_Version 2

1st report Using Schema Table 1_Version 1

<uniqueTransactionIdentifier>UTI123</uniqueTransactionIdentifier>

<actionType>N</actionType>

2st report Using Schema Table 1_Version 1

<uniqueTransactionIdentifier>UTI456</uniqueTransactionIdentifier>

<previousUniqueTransactionIdentifier> UTI123 </previousUniqueTransactionIdentifier>

<actionType>M</actionType>

Using Schema Table 1_Version 1

1st report Using Schema Table 1_Version 1

<uniqueTransactionIdentifier>UTI123</uniqueTransactionIdentifier>

<actionType>N</actionType>

2st report Using Schema Table 1_Version 1

<uniqueTransactionIdentifier>UTI456</uniqueTransactionIdentifier>

< additionalUtiInfo> UTI123 </ additionalUtiInfo>

<actionType>M</actionType>

Last update: 26/09/2016   RSS_Icon Subscribe to this Page’s RSS