Info
🔗 Back to Summary. 🇫🇷 French Version: 2022R1858_FR.1. Back to Summary of LVL1. Open the PDF. Direct link to EUR-LEX.
Retour au sommaire ⬅️ | ➡️ Article 2 – Procedure for updates of Legal Entity Identifiers
Article 1 - Verification of derivatives by trade repositories
1.
A trade repository shall verify all of the following in a received derivative report:
(a)
the identity of the report submitting entity as referred to in field 2 of Table 1 and field 2 of Table 3 of the Annex to Commission Implementing Regulation (EU) 2022/1860
;
(b)
that the XML template used to report a derivative complies with the ISO 20022 methodology in accordance with Article 1 of Implementing Regulation (EU) 2022/1860;
(c)
that the report submitting entity, if different from the entity responsible for reporting as referred to in field 3 of Table 1 and field 3 in Table 3 of the Annex to Implementing Regulation (EU) 2022/1860, is duly authorised to report on behalf of counterparty 1 or the entity responsible for reporting, if different from counterparty 1, as referred to in field 4 of Table 1 and field 4 in Table 3 of the Annex to Implementing Regulation (EU) 2022/1860;
(d)
that the same derivative has not been submitted previously;
(e)
that a derivative report with action type ‘Modification’, ‘Margin Update’, ‘Valuation’, ‘Correction’, ‘Error‘ or ‘Terminate’ relates to a previously submitted derivative;
(f)
that a derivative report with action type ‘Modification’ does not relate to a derivative that has been reported as cancelled with action type ‘Error’ which has not been subsequently reported with action type ‘Revive’;
(g)
that a derivative report does not include the action type ‘New’ in respect of a derivative that has previously been reported;
(h)
that a derivative report does not include the action type ‘Position component’ in respect of a derivative that has previously been reported;
(i)
that a derivative report does not purport to modify the details of fields ‘Counterparty 1’ or ‘Counterparty 2’ to a previously reported derivative;
(j)
that a derivative report does not purport to modify an existing derivative by specifying an effective date later than the reported maturity date of the derivative;
(k)
that a derivative reported with action type ‘Revive’ relates to a previously submitted derivative report with action type ‘Error’ or ‘Terminate’ or to a derivative that has matured;
(l)
the correctness and completeness of the derivative report.
2.
A trade repository shall reject a derivative report that does not comply with one of the requirements set out in paragraph 1 and assign to it one of the rejection categories set out in Table 1 of the Annex.
3.
A trade repository shall provide the report submitting entities with detailed information on the results of the data verification referred to in paragraph 1 within sixty minutes after it has received a derivative report. A trade repository shall provide those results in an XML format and a template in accordance with the ISO 20022 methodology. The results shall specify reasons for the rejection of a derivative report in accordance with Table 1 of the Annex.