# L_2020289EN.01033501.xml

| 3.9.2020 | EN | Official Journal of the European Union | L 289/335 |
| --- | --- | --- | --- |

3.9.2020

EN

Official Journal of the European Union

L 289/335

---

COMMISSION DELEGATED REGULATION (EU) 2020/1229

of 29 November 2019

supplementing Regulation (EU) 2017/2402 of the European Parliament and of the Council with regard to regulatory technical standards on securitisation repository operational standards for data collection, aggregation, comparison, access and verification of completeness and consistency

(Text with EEA relevance)

THE EUROPEAN COMMISSION,

Having regard to the Treaty on the Functioning of the European Union,

Having regard to Regulation (EU) 2017/2402 of the European Parliament and of the Council of 12 December 2017 laying down a general framework for securitisation and creating a specific framework for simple, transparent and standardised securitisation, and amending Directives 2009/65/EC, 2009/138/EC and 2011/61/EU and Regulations (EC) No 1060/2009 and (EU) No 648/2012 (1), and in particular point (a) of Article 10(7) and points (b), (c) and (d) of Article 17(2) thereof,

Whereas:

| (1) | The entities referred to in Article 17(1) of Regulation (EU) 2017/2402 should be able to fulfil their respective responsibilities, mandates and obligations. The information provided to those entities by securitisation repositories should therefore be of high quality and should lend itself to an aggregation and comparison across different securitisation repositories in a timely, comprehensive and structured manner. Securitisation repositories should therefore assess whether that information is complete and consistent before making it available to those entities and should provide those entities with an end-of-day report and overall data completeness score. |
| --- | --- |

(1)

The entities referred to in Article 17(1) of Regulation (EU) 2017/2402 should be able to fulfil their respective responsibilities, mandates and obligations. The information provided to those entities by securitisation repositories should therefore be of high quality and should lend itself to an aggregation and comparison across different securitisation repositories in a timely, comprehensive and structured manner. Securitisation repositories should therefore assess whether that information is complete and consistent before making it available to those entities and should provide those entities with an end-of-day report and overall data completeness score.

| (2) | The procedures to verify whether the information reported to securitisation repositories by originators, sponsors or SSPEs is complete and consistent should take into account the variety of securitisation types, features and practices. It is therefore appropriate to provide for verification procedures that include the comparison of the information reported with respect to similar securitisations, such as securitisations sharing the same or related originator, underlying exposure type, structural feature or geography. |
| --- | --- |

(2)

The procedures to verify whether the information reported to securitisation repositories by originators, sponsors or SSPEs is complete and consistent should take into account the variety of securitisation types, features and practices. It is therefore appropriate to provide for verification procedures that include the comparison of the information reported with respect to similar securitisations, such as securitisations sharing the same or related originator, underlying exposure type, structural feature or geography.

| (3) | To ensure the quality of the information reported, verification procedures should also apply to the completeness and consistency of the documentation supporting that information. Given, however, the relative difficulty in verifying completeness and consistency of that documentation, securitisation repositories should request reporting entities to confirm in writing that the underlying securitisation documentation made available by them is complete and consistent. Material updates to documentation already reported should be considered a new securitisation document requiring a written confirmation request. |
| --- | --- |

(3)

To ensure the quality of the information reported, verification procedures should also apply to the completeness and consistency of the documentation supporting that information. Given, however, the relative difficulty in verifying completeness and consistency of that documentation, securitisation repositories should request reporting entities to confirm in writing that the underlying securitisation documentation made available by them is complete and consistent. Material updates to documentation already reported should be considered a new securitisation document requiring a written confirmation request.

| (4) | To enable the entities referred to in Article 17(1) of Regulation (EU) 2017/2402 to fulfil their respective responsibilities, mandates and obligations, the details of securitisations to which those entities must have direct and immediate access should be comparable across securitisation repositories in a harmonised and consistent manner. Those details should therefore be provided in Extensible Markup Language (XML) format because that format is widely used in the financial industry. |
| --- | --- |

(4)

To enable the entities referred to in Article 17(1) of Regulation (EU) 2017/2402 to fulfil their respective responsibilities, mandates and obligations, the details of securitisations to which those entities must have direct and immediate access should be comparable across securitisation repositories in a harmonised and consistent manner. Those details should therefore be provided in Extensible Markup Language (XML) format because that format is widely used in the financial industry.

| (5) | Confidentiality of any type of data exchanged between securitisation repositories and the entities referred to in Article 17(1) of Regulation (EU) 2017/2402 should be ensured. Such exchanges should therefore be carried out through a secure machine-to-machine connection by using data encryption protocols. To ensure minimum common standards, an SSH File Transfer Protocol should be used. |
| --- | --- |

(5)

Confidentiality of any type of data exchanged between securitisation repositories and the entities referred to in Article 17(1) of Regulation (EU) 2017/2402 should be ensured. Such exchanges should therefore be carried out through a secure machine-to-machine connection by using data encryption protocols. To ensure minimum common standards, an SSH File Transfer Protocol should be used.

| (6) | Data concerning the latest securitisation underlying exposures, investor reports, inside information and significant event information, as well as indicators of the quality and timeliness of those data, are essential for ongoing monitoring of securitisation investment positions and potential investments, as well as financial stability and systemic risk. The entities referred to in Article 17(1) of Regulation (EU) 2017/2402 should therefore have access to those data on an ad hoc or predefined periodic basis proportionate to their needs for receiving it. |
| --- | --- |

(6)

Data concerning the latest securitisation underlying exposures, investor reports, inside information and significant event information, as well as indicators of the quality and timeliness of those data, are essential for ongoing monitoring of securitisation investment positions and potential investments, as well as financial stability and systemic risk. The entities referred to in Article 17(1) of Regulation (EU) 2017/2402 should therefore have access to those data on an ad hoc or predefined periodic basis proportionate to their needs for receiving it.

| (7) | Securitisations are complex and heterogeneous and the users accessing information from securitisation repositories are diverse. It is therefore essential that the direct and immediate access to specific datasets and information is facilitated. That access should include access in a machine-readable format where the information relates to data and to all current and historical information on a securitisation stored within a repository. For that purpose, a framework should be created for ad hoc requests that can be combined to obtain specific information. The deadlines by which securitisation repositories should provide data to the entities referred to in Article 17(1) of Regulation (EU) 2017/2402 should be harmonised to facilitate efficient data processing by those entities and securitisation repositories. At the same time, it should be ensured that data are obtained within deadlines that enable the effective fulfilment of the requesting entities’ responsibilities. |
| --- | --- |

(7)

Securitisations are complex and heterogeneous and the users accessing information from securitisation repositories are diverse. It is therefore essential that the direct and immediate access to specific datasets and information is facilitated. That access should include access in a machine-readable format where the information relates to data and to all current and historical information on a securitisation stored within a repository. For that purpose, a framework should be created for ad hoc requests that can be combined to obtain specific information. The deadlines by which securitisation repositories should provide data to the entities referred to in Article 17(1) of Regulation (EU) 2017/2402 should be harmonised to facilitate efficient data processing by those entities and securitisation repositories. At the same time, it should be ensured that data are obtained within deadlines that enable the effective fulfilment of the requesting entities’ responsibilities.

| (8) | The entities referred to in Article 17(1) of Regulation (EU) 2017/2402 rely on the data maintained by securitisation repositories, including for comparing current securitisations with past securitisations. Therefore, it is appropriate to specify that repositories should maintain records of a securitisation for 10 years following the termination of the securitisation, pursuant to Article 10(2) of Regulation (EU) 2017/2402 and Article 80(3) of Regulation (EU) No 648/2012 of the European Parliament and of the Council (2). |
| --- | --- |

(8)

The entities referred to in Article 17(1) of Regulation (EU) 2017/2402 rely on the data maintained by securitisation repositories, including for comparing current securitisations with past securitisations. Therefore, it is appropriate to specify that repositories should maintain records of a securitisation for 10 years following the termination of the securitisation, pursuant to Article 10(2) of Regulation (EU) 2017/2402 and Article 80(3) of Regulation (EU) No 648/2012 of the European Parliament and of the Council (2).

| (9) | The provisions in this Regulation are closely linked, since they deal with standards and procedures relating to the collection and processing of information held by securitisations repositories and access to that information. It is therefore appropriate to include those provisions in a single Regulation. |
| --- | --- |

(9)

The provisions in this Regulation are closely linked, since they deal with standards and procedures relating to the collection and processing of information held by securitisations repositories and access to that information. It is therefore appropriate to include those provisions in a single Regulation.

| (10) | This Regulation is based on the draft regulatory technical standards submitted to the Commission by the European Securities and Markets Authority (ESMA). |
| --- | --- |

(10)

This Regulation is based on the draft regulatory technical standards submitted to the Commission by the European Securities and Markets Authority (ESMA).

| (11) | ESMA has conducted an open public consultation on the draft regulatory technical standards on which this Regulation is based, analysed the potential related costs and benefits and requested the opinion of the Securities and Markets Stakeholder Group established in accordance with Article 37 of Regulation (EU) No 1095/2010 of the European Parliament and of the Council (3), |
| --- | --- |

(11)

ESMA has conducted an open public consultation on the draft regulatory technical standards on which this Regulation is based, analysed the potential related costs and benefits and requested the opinion of the Securities and Markets Stakeholder Group established in accordance with Article 37 of Regulation (EU) No 1095/2010 of the European Parliament and of the Council (3),

HAS ADOPTED THIS REGULATION:

Article 1

Definitions

For the purposes of this Regulation, the following definitions shall apply:

| (a) | ‘reporting entity’ means the entity designated in accordance with Article 7(2) of Regulation (EU) 2017/2402; |
| --- | --- |

(a)

‘reporting entity’ means the entity designated in accordance with Article 7(2) of Regulation (EU) 2017/2402;

| (b) | ‘data cut-off date’ means the reference date of the information reported in accordance with Commission Delegated Regulation (EU) 2020/1224 (4). |
| --- | --- |

(b)

‘data cut-off date’ means the reference date of the information reported in accordance with Commission Delegated Regulation (EU) 2020/1224 (4).

4

Article 2

End-of-day report

1.   Securitisation repositories shall produce, on a daily basis, a single aggregate end-of-day report for all securitisations reported to them, excluding any reported securitisation that has been rejected in accordance with Article 4(6). That report shall be based on the most recent reported information, shall exclude any reported securitisation that has been rejected in accordance with Article 4(6) and shall include at least the following information:

| (a) | the unique identifier assigned in accordance with Article XI of Delegated Regulation (EU) 2020/1224; |
| --- | --- |

(a)

the unique identifier assigned in accordance with Article XI of Delegated Regulation (EU) 2020/1224;

| (b) | the ISIN codes of the tranches, bonds or subordinated loans of the securitisation, where available; |
| --- | --- |

(b)

the ISIN codes of the tranches, bonds or subordinated loans of the securitisation, where available;

| (c) | the sum of current principal balances of all tranches, bonds or subordinated loans of the securitisation, in EUR, using the exchange rates published on the website of the European Central Bank for the previous working day; |
| --- | --- |

(c)

the sum of current principal balances of all tranches, bonds or subordinated loans of the securitisation, in EUR, using the exchange rates published on the website of the European Central Bank for the previous working day;

| (d) | the securitisation name; |
| --- | --- |

(d)

the securitisation name;

| (e) | whether the securitisation is an ABCP or non-ABCP securitisation; |
| --- | --- |

(e)

whether the securitisation is an ABCP or non-ABCP securitisation;

| (f) | whether the securitisation structure type is type ‘M’ for a Master Trust as reported in field SESS9 of Annex XIV to Delegated Regulation (EU) 2020/1224 or type ‘S’ for all other securitisations; |
| --- | --- |

(f)

whether the securitisation structure type is type ‘M’ for a Master Trust as reported in field SESS9 of Annex XIV to Delegated Regulation (EU) 2020/1224 or type ‘S’ for all other securitisations;

| (g) | whether the securitisation risk transfer method is ‘T’ for a true sale as reported in field IVSS11 of Annex XII to Delegated Regulation (EU) 2020/1224 or ‘S’ for a synthetic securitisation as reported in field SESV11 of Annex XIV to that Regulation, or ‘ABCP’ for ABCP securitisations; |
| --- | --- |

(g)

whether the securitisation risk transfer method is ‘T’ for a true sale as reported in field IVSS11 of Annex XII to Delegated Regulation (EU) 2020/1224 or ‘S’ for a synthetic securitisation as reported in field SESV11 of Annex XIV to that Regulation, or ‘ABCP’ for ABCP securitisations;

| (h) | the name and legal entity identifiers (‘LEI’) of the originator, sponsor and SSPE; |
| --- | --- |

(h)

the name and legal entity identifiers (‘LEI’) of the originator, sponsor and SSPE;

| (i) | the most recent interest payment date in ISO 8601 date format; |
| --- | --- |

(i)

the most recent interest payment date in ISO 8601 date format;

| (j) | the timestamp, in ISO 8601 date and time (UCT) format, to the nearest second, of the most recent data submission received by the securitisation repository, or, where there are multiple data submissions referenced against the same data cut-off date, the timestamps, in ISO 8601 date and time (UCT) format, of the earliest and most recent data submissions having the same data cut-off date; |
| --- | --- |

(j)

the timestamp, in ISO 8601 date and time (UCT) format, to the nearest second, of the most recent data submission received by the securitisation repository, or, where there are multiple data submissions referenced against the same data cut-off date, the timestamps, in ISO 8601 date and time (UCT) format, of the earliest and most recent data submissions having the same data cut-off date;

| (k) | the data cut-off date, in ISO 8601 date format, of the most recent data submission received by the securitisation repository; |
| --- | --- |

(k)

the data cut-off date, in ISO 8601 date format, of the most recent data submission received by the securitisation repository;

| (l) | the number of data submissions received by the securitisation repository that are referenced against the same data cut-off date set out in point (k); |
| --- | --- |

(l)

the number of data submissions received by the securitisation repository that are referenced against the same data cut-off date set out in point (k);

| (m) | the data completeness score referred to in Article 3 of the most recent data submission received by the securitisation repository; |
| --- | --- |

(m)

the data completeness score referred to in Article 3 of the most recent data submission received by the securitisation repository;

| (n) | for non-ABCP securitisations, the country of establishment of the originator or original lender; |
| --- | --- |

(n)

for non-ABCP securitisations, the country of establishment of the originator or original lender;

| (o) | for ABCP securitisations, the country of establishment of the sponsor; |
| --- | --- |

(o)

for ABCP securitisations, the country of establishment of the sponsor;

| (p) | the country where the majority of the underlying exposures is located, in terms of underlying exposure current principal balance; |
| --- | --- |

(p)

the country where the majority of the underlying exposures is located, in terms of underlying exposure current principal balance;

| (q) | the most prevalent type of the underlying exposures in the securitisation, in terms of current principal balance. |
| --- | --- |

(q)

the most prevalent type of the underlying exposures in the securitisation, in terms of current principal balance.

| (r) | For the purposes of point (n), where the securitisation underlying exposures are a combination of exposures from multiple originators or original lenders, the country of establishment of the originator or original lender shall be the country of the originator or original lender that has the largest amount of exposures in terms of current principal balance in the securitisation. |
| --- | --- |

(r)

For the purposes of point (n), where the securitisation underlying exposures are a combination of exposures from multiple originators or original lenders, the country of establishment of the originator or original lender shall be the country of the originator or original lender that has the largest amount of exposures in terms of current principal balance in the securitisation.

2.   Securitisation repositories shall make the end-of-day report available in XML format.

3.   Timestamps referred to in this Article shall not diverge by more than one second from the UTC issued and maintained by one of the timing centres listed in the latest Bureau International des Poids et Mesures (BIPM) Annual Report on Time Activities.

Article 3

Scoring of completeness of data

4.   Securitisation repositories shall calculate a data completeness score for each data submission by using the scoring matrix set out in Table 1 of the Annex and the following inputs:

Image 1

Image 2

Where:

Image 3
  denotes the total number of fields in a data submission containing the respective ‘No Data Option’ values that are reported in accordance with Article 9(3) of Delegated Regulation (EU) 2020/1224.

N denotes the total number of fields in the data submission where any ‘No Data Option’ values (ND1 to ND4) are permitted to be reported in accordance with Article 9(3) of Delegated Regulation (EU) 2020/1224.

For the purposes of calculating the data completeness score, fields completed using the format of ‘ND4-YYYY-MM-DD’ shall be understood as ‘ND4’.

Article 4

Verification of completeness and consistency of information

1.   Securitisation repositories shall verify the completeness and consistency of information reported to them by verifying the following:

| (a) | the name of the reporting entity, as reported in field IVSS4 of Annex XII or in field IVAS3 of Annex XIII to Delegated Regulation (EU) 2020/1224; |
| --- | --- |

(a)

the name of the reporting entity, as reported in field IVSS4 of Annex XII or in field IVAS3 of Annex XIII to Delegated Regulation (EU) 2020/1224;

| (b) | whether the submission item code as reported in Table 3 of Annex I to Delegated Regulation (EU) 2020/1224 is correct. |
| --- | --- |

(b)

whether the submission item code as reported in Table 3 of Annex I to Delegated Regulation (EU) 2020/1224 is correct.

2.   With regard to the information referred to in points (a), (e), (f) and (g) of Article 7(1) of Regulation (EU) 2017/2402, Securitisation repositories shall also verify the completeness and consistency of information by:

| (a) | verifying whether the information reported complies with the structure and format of the templates set out in Annex II to XV of Commission Implementing Regulation (EU) 2020/1225 (5); |
| --- | --- |

(a)

verifying whether the information reported complies with the structure and format of the templates set out in Annex II to XV of Commission Implementing Regulation (EU) 2020/1225 (5);

| (b) | comparing the information reported:






  (i) | across different fields for the same data cut-off date and the same underlying exposure, investor report, inside information or significant event information item; |
| --- | --- | --- |

(b)

comparing the information reported:

(i)

across different fields for the same data cut-off date and the same underlying exposure, investor report, inside information or significant event information item;

| (ii) | across different underlying exposures, investor report, inside information or significant event information items for the same field and the same data cut-off date; |
| --- | --- |

(ii)

across different underlying exposures, investor report, inside information or significant event information items for the same field and the same data cut-off date;

| (iii) | across the same underlying exposure, investor report, inside information or significant event information items for the same field and different data cut-off dates; |
| --- | --- |

(iii)

across the same underlying exposure, investor report, inside information or significant event information items for the same field and different data cut-off dates;

| (iv) | across similar securitisations; |
| --- | --- |

(iv)

across similar securitisations;

| (c) | verifying whether the data cut-off date of the information reported and the timestamp of the submission comply with Article 10 of Delegated Regulation (EU) 2020/1224; |
| --- | --- |

(c)

verifying whether the data cut-off date of the information reported and the timestamp of the submission comply with Article 10 of Delegated Regulation (EU) 2020/1224;

| (d) | verifying that the ‘No Data Options’ set out in Article 9(3) of Delegated Regulation (EU) 2020/1224, are only used where permitted and do not prevent the data submission from being sufficiently representative of the underlying exposures in the securitisation. |
| --- | --- |

(d)

verifying that the ‘No Data Options’ set out in Article 9(3) of Delegated Regulation (EU) 2020/1224, are only used where permitted and do not prevent the data submission from being sufficiently representative of the underlying exposures in the securitisation.

For ABCP securitisations, references in this paragraph to underlying exposures shall be construed as references to underlying exposure types.

3.   Securitisation repositories shall verify the completeness and consistency of the documentation made available to them under point (b) of Article 7(1) of Regulation (EU) 2017/2402 by requesting from reporting entities a written confirmation of the following:

| (a) | that all items referred to in Table 3 of Annex I to Delegated Regulation (EU) 2020/1224 and required to be made available pursuant to point (b) of Article 7(1) of Regulation (EU) 2017/2402 have been provided to the securitisation repository; |
| --- | --- |

(a)

that all items referred to in Table 3 of Annex I to Delegated Regulation (EU) 2020/1224 and required to be made available pursuant to point (b) of Article 7(1) of Regulation (EU) 2017/2402 have been provided to the securitisation repository;

| (b) | that the documentation is consistent with the actual arrangements and features of the securitisation. |
| --- | --- |

(b)

that the documentation is consistent with the actual arrangements and features of the securitisation.

4.   The written confirmation referred to in paragraph 3 shall be requested within the following timeframes:

| (a) | within five working days of the first issuance of securities under the securitisation or, for ABCP securitisations, within five working days of the first issuance of securities under the ABCP programme; |
| --- | --- |

(a)

within five working days of the first issuance of securities under the securitisation or, for ABCP securitisations, within five working days of the first issuance of securities under the ABCP programme;

| (b) | every 12 months from the dates of the requests referred to in point (a); |
| --- | --- |

(b)

every 12 months from the dates of the requests referred to in point (a);

| (c) | within five working days of a new document being made available pursuant to point (b) of Article 7(1) of Regulation (EU) 2017/2402. |
| --- | --- |

(c)

within five working days of a new document being made available pursuant to point (b) of Article 7(1) of Regulation (EU) 2017/2402.

A securitisation repository that has not received a written confirmation within 14 days of the date of any request referred to in the first subparagraph shall request the reporting entity to provide it with the written confirmation within 14 days.

5.   Securitisation repositories shall verify whether the STS notification referred to in point (d) of Article 7(1) of Regulation (EU) 2017/2402, which has been made available to that securitisation repository complies with the structure and format of the templates set out in the Annexes to Commission Implementing Regulation (EU) 2020/1227 (6).

6.   A securitisation repository shall reject a submission of information that is incomplete or inconsistent pursuant to paragraphs 1, 2, and 5, except for sub-points (iii) and (iv) of point (b) of paragraph 2. The securitisation repository shall assign submissions rejected pursuant to this paragraph to one of the rejection categories set out in Table 2 of the Annex.

7.   The securitisation repository shall notify the entities referred to in Article 17(1) of Regulation (EU) 2017/2402 without undue delay of the following:

| (a) | that the submitted information is incomplete or inconsistent pursuant to sub-points (iii) and (iv) of point (b) of paragraph 2; |
| --- | --- |

(a)

that the submitted information is incomplete or inconsistent pursuant to sub-points (iii) and (iv) of point (b) of paragraph 2;

| (b) | that the securitisation repository has not received the written confirmation referred to in paragraph 3. |
| --- | --- |

(b)

that the securitisation repository has not received the written confirmation referred to in paragraph 3.

8.   Within one hour of the receipt of the information referred to in Article 7 of Regulation (EU) 2017/2402, securitisation repositories shall provide reporting entities with detailed feedback on the results of the verifications performed under paragraphs 1, 2, 3 and 5, including any rejection category assigned pursuant to paragraph 6. That feedback shall also include at least the following::

| (a) | the unique identifier of the securitisation assigned in accordance with Article 11 of Delegated Regulation (EU) 2020/1224; |
| --- | --- |

(a)

the unique identifier of the securitisation assigned in accordance with Article 11 of Delegated Regulation (EU) 2020/1224;

| (b) | the item code(s) referred to in Table 3 of Annex I to Delegated Regulation (EU) 2020/1224; |
| --- | --- |

(b)

the item code(s) referred to in Table 3 of Annex I to Delegated Regulation (EU) 2020/1224;

| (c) | the submission timestamp, in ISO 8601 date and time (UCT) format, to the nearest second, of the information reported. |
| --- | --- |

(c)

the submission timestamp, in ISO 8601 date and time (UCT) format, to the nearest second, of the information reported.

9.   By 19.00.00 UTC each Monday, securitisation repositories shall produce a report on all information rejected by it since 19.00.00 UTC on the previous Monday. That report shall include at least the following items:

| (a) | the unique identifier of the securitisation assigned in accordance with Article 11 Delegated Regulation (EU) 2020/1224; |
| --- | --- |

(a)

the unique identifier of the securitisation assigned in accordance with Article 11 Delegated Regulation (EU) 2020/1224;

| (b) | the securitisation name; |
| --- | --- |

(b)

the securitisation name;

| (c) | the ISIN codes of the tranches or bonds or subordinated loans of the securitisation, where available; |
| --- | --- |

(c)

the ISIN codes of the tranches or bonds or subordinated loans of the securitisation, where available;

| (d) | the name and LEI of the originator, sponsor and SSPE; |
| --- | --- |

(d)

the name and LEI of the originator, sponsor and SSPE;

| (e) | the timestamp, in ISO 8601 date and time (UCT) format, to the nearest second, of the submitted information; |
| --- | --- |

(e)

the timestamp, in ISO 8601 date and time (UCT) format, to the nearest second, of the submitted information;

| (f) | the submission item code referred to in Table 3 of Annex I to Delegated Regulation (EU) 2020/1224; |
| --- | --- |

(f)

the submission item code referred to in Table 3 of Annex I to Delegated Regulation (EU) 2020/1224;

| (g) | the rejection category referred to in Table 2 of the Annex to this Regulation and the specific circumstances for assigning that rejection category; |
| --- | --- |

(g)

the rejection category referred to in Table 2 of the Annex to this Regulation and the specific circumstances for assigning that rejection category;

| (h) | any explanation(s) provided by the reporting entity before 17.00.00 UTC on the Monday of the report publication date as to why the reported information is incomplete or inconsistent, or as to why the written confirmation referred to in paragraph 3 has not been provided. |
| --- | --- |

(h)

any explanation(s) provided by the reporting entity before 17.00.00 UTC on the Monday of the report publication date as to why the reported information is incomplete or inconsistent, or as to why the written confirmation referred to in paragraph 3 has not been provided.

Article 5

Details of information to which access is to be granted

The details of information referred to in point (c) of Article 17(2) of Regulation (EU) 2017/2402 are the following:

| (a) | all information received by the securitisation repository from reporting entities in accordance with Regulation (EU) 2017/2402; |
| --- | --- |

(a)

all information received by the securitisation repository from reporting entities in accordance with Regulation (EU) 2017/2402;

| (b) | the end-of-day report referred to in Article 2, the data completeness score referred to in Article 3 and any information resulting from the verifications carried out pursuant to Article 4 of this Regulation; |
| --- | --- |

(b)

the end-of-day report referred to in Article 2, the data completeness score referred to in Article 3 and any information resulting from the verifications carried out pursuant to Article 4 of this Regulation;

| (c) | all formulae and calculation and aggregation methods used to produce the information referred to in points (a) and (b). |
| --- | --- |

(c)

all formulae and calculation and aggregation methods used to produce the information referred to in points (a) and (b).

Article 6

Terms and conditions for access to details of information

1.   Access to the information referred to in Article 5 shall be granted upon request. The request for access shall include the following information:

| (a) | the name of the requesting entity; |
| --- | --- |

(a)

the name of the requesting entity;

| (b) | the contact person at the requesting entity; |
| --- | --- |

(b)

the contact person at the requesting entity;

| (c) | the type of requesting entity as referred to in Article 17(1) of Regulation (EU) 2017/2402 that requests access; |
| --- | --- |

(c)

the type of requesting entity as referred to in Article 17(1) of Regulation (EU) 2017/2402 that requests access;

| (d) | the names of the persons at the requesting entity who will have access to the requested information; |
| --- | --- |

(d)

the names of the persons at the requesting entity who will have access to the requested information;

| (e) | credentials for secure SSH File Transfer Protocol connection as required by Article 7(2); |
| --- | --- |

(e)

credentials for secure SSH File Transfer Protocol connection as required by Article 7(2);

| (f) | whether the request is an ad hoc or predefined periodic request; |
| --- | --- |

(f)

whether the request is an ad hoc or predefined periodic request;

| (g) | the identification of the information requested based on any combination of the criteria in paragraph 4; |
| --- | --- |

(g)

the identification of the information requested based on any combination of the criteria in paragraph 4;

| (h) | any other technical information relevant to the requesting entity’s access. |
| --- | --- |

(h)

any other technical information relevant to the requesting entity’s access.

2.   For the purposes of paragraph 1, securitisation repositories shall:

| (a) | designate a person or persons responsible for liaising with the entities referred to in Article 17(1) of Regulation (EU) 2017/2402; |
| --- | --- |

(a)

designate a person or persons responsible for liaising with the entities referred to in Article 17(1) of Regulation (EU) 2017/2402;

| (b) | publish on their website the terms and conditions for accessing the information and the instructions for submitting a request for accessing that information; |
| --- | --- |

(b)

publish on their website the terms and conditions for accessing the information and the instructions for submitting a request for accessing that information;

| (c) | provide access only to the information specified in the request for access; |
| --- | --- |

(c)

provide access only to the information specified in the request for access;

| (d) | as soon as possible but no later than 30 days following a request to set up access to that information, establish the technical arrangements necessary to enable the entities referred to in Article 17(1) of Regulation (EU) 2017/2402 to submit requests to access that information. |
| --- | --- |

(d)

as soon as possible but no later than 30 days following a request to set up access to that information, establish the technical arrangements necessary to enable the entities referred to in Article 17(1) of Regulation (EU) 2017/2402 to submit requests to access that information.

3.   Access to the information referred to in Article 5 shall be granted within the following timeframes:

| (a) | no later than 19.00.00 UTC of the day to which the report relates for an ad hoc or predefined periodic request for an end-of-day report as referred to in Article 2; |
| --- | --- |

(a)

no later than 19.00.00 UTC of the day to which the report relates for an ad hoc or predefined periodic request for an end-of-day report as referred to in Article 2;

| (b) | no later than 12.00.00 UTC on the first day following the day of receipt of the request for access where the information concerns a securitisation that has either not yet been priced or has not yet matured or has matured less than one year before the date on which the request was submitted; |
| --- | --- |

(b)

no later than 12.00.00 UTC on the first day following the day of receipt of the request for access where the information concerns a securitisation that has either not yet been priced or has not yet matured or has matured less than one year before the date on which the request was submitted;

| (c) | no later than three working days following the day of receipt of the request for access where the information concerns a securitisation that has matured more than one year before the date on which the request was submitted; |
| --- | --- |

(c)

no later than three working days following the day of receipt of the request for access where the information concerns a securitisation that has matured more than one year before the date on which the request was submitted;

| (d) | no later than three working days following the day of receipt of the request for access where the information concerns several securitisations falling under both points (b) and (c). |
| --- | --- |

(d)

no later than three working days following the day of receipt of the request for access where the information concerns several securitisations falling under both points (b) and (c).

4.   Securitisation repositories shall grant the entities referred to in Article 17(1) of Regulation (EU) 2017/2402 access to the information referred to in Article 5, based on any combination of the following criteria:

| (a) | securitisation type: non-ABCP or ABCP; |
| --- | --- |

(a)

securitisation type: non-ABCP or ABCP;

| (b) | securitisation structure type: either ‘M’ for Master Trust as reported in field SESS9 of Annex XIV to Delegated Regulation (EU) 2020/1224 or ‘S’ for all other securitisations; |
| --- | --- |

(b)

securitisation structure type: either ‘M’ for Master Trust as reported in field SESS9 of Annex XIV to Delegated Regulation (EU) 2020/1224 or ‘S’ for all other securitisations;

| (c) | securitisation risk transfer method: either type ‘Y’ for true sale as reported in field IVSS11 in Annex XII to Delegated Regulation (EU) 2020/1224, ‘Y’ for synthetic as reported in field SESV11 in Annex XIV to that Regulation, or ‘ABCP’ for ABCP securitisations; |
| --- | --- |

(c)

securitisation risk transfer method: either type ‘Y’ for true sale as reported in field IVSS11 in Annex XII to Delegated Regulation (EU) 2020/1224, ‘Y’ for synthetic as reported in field SESV11 in Annex XIV to that Regulation, or ‘ABCP’ for ABCP securitisations;

| (d) | securitisation item code; |
| --- | --- |

(d)

securitisation item code;

| (e) | securitisation underlying exposure type; |
| --- | --- |

(e)

securitisation underlying exposure type;

| (f) | securitisation underlying exposure section; |
| --- | --- |

(f)

securitisation underlying exposure section;

| (g) | securitisation investor report template section; |
| --- | --- |

(g)

securitisation investor report template section;

| (h) | securitisation inside information or significant event information template section; |
| --- | --- |

(h)

securitisation inside information or significant event information template section;

| (i) | identifier:






  (i) | unique identifier; |
| --- | --- | --- |

(i)

identifier:

(i)

unique identifier;

| (ii) | transaction identifier; |
| --- | --- |

(ii)

transaction identifier;

| (iii) | International Securities Identification Number; |
| --- | --- |

(iii)

International Securities Identification Number;

| (iv) | new or original tranche/bond identifier; |
| --- | --- |

(iv)

new or original tranche/bond identifier;

| (v) | new or original underlying exposure identifier; |
| --- | --- |

(v)

new or original underlying exposure identifier;

| (vi) | new or original obligor identifier; |
| --- | --- |

(vi)

new or original obligor identifier;

| (vii) | originator legal entity identifier; |
| --- | --- |

(vii)

originator legal entity identifier;

| (viii) | sponsor legal entity identifier; |
| --- | --- |

(viii)

sponsor legal entity identifier;

| (ix) | SSPE legal entity identifier; |
| --- | --- |

(ix)

SSPE legal entity identifier;

| (x) | original lender legal entity identifier; |
| --- | --- |

(x)

original lender legal entity identifier;

| (xi) | CLO manager legal entity identifier; |
| --- | --- |

(xi)

CLO manager legal entity identifier;

| (j) | geography:






  (i) | geographic region; |
| --- | --- | --- |

(j)

geography:

(i)

geographic region;

| (ii) | governing law; |
| --- | --- |

(ii)

governing law;

| (k) | date and time:






  (i) | submission timestamp; |
| --- | --- | --- |

(k)

date and time:

(i)

submission timestamp;

| (ii) | data cut-off date; |
| --- | --- |

(ii)

data cut-off date;

| (iii) | tranche/bond issue date; |
| --- | --- |

(iii)

tranche/bond issue date;

| (iv) | tranche/bond legal maturity; |
| --- | --- |

(iv)

tranche/bond legal maturity;

| (v) | underlying exposure origination date; |
| --- | --- |

(v)

underlying exposure origination date;

| (vi) | underlying exposure maturity date; |
| --- | --- |

(vi)

underlying exposure maturity date;

| (l) | currency:






  (i) | tranche/bond currency; |
| --- | --- | --- |

(l)

currency:

(i)

tranche/bond currency;

| (ii) | underlying exposure currency denomination. |
| --- | --- |

(ii)

underlying exposure currency denomination.

5.   Securitisation repositories shall make the following information available using XML format:

| (a) | the information referred to in point (a) and points (d) to (g) of Article 7(1) of Regulation (EU) 2017/2402; |
| --- | --- |

(a)

the information referred to in point (a) and points (d) to (g) of Article 7(1) of Regulation (EU) 2017/2402;

| (b) | the information produced by securitisation repositories in accordance with Articles 2 and 4 of this Regulation, with the exception of written confirmations received under Article 4(3). |
| --- | --- |

(b)

the information produced by securitisation repositories in accordance with Articles 2 and 4 of this Regulation, with the exception of written confirmations received under Article 4(3).

Article 7

Standards for data collection and access

1.   Securitisation repositories shall use electronic signature and data encryption protocols to receive data from reporting entities or other securitisation repositories, and to transfer data to the entities referred to in Article 17(1) of Regulation (EU) 2017/2402.

2.   For the purposes of paragraph 1, securitisation repositories shall establish and maintain a secure machine-to-machine interface and make that interface available to the reporting entities and the entities referred to in Article 17(1) of Regulation (EU) 2017/2402. That interface shall make use of the SSH File Transfer Protocol.

3.   Securitisation repositories shall use standardised XML messages to communicate through the interface referred to in paragraph 2 and make the information set out in Article 6(5) of this Regulation available to the entities referred to in Article 17(1) of Regulation (EU) 2017/2402.

Article 8

Recordkeeping

1.   Securitisation repositories shall record the following:

| (a) | verifications pursuant to this Regulation, and any other validation carried out by the securitisation repository; |
| --- | --- |

(a)

verifications pursuant to this Regulation, and any other validation carried out by the securitisation repository;

| (b) | the written confirmations received by the securitisation repository referred to in Article 4(3); |
| --- | --- |

(b)

the written confirmations received by the securitisation repository referred to in Article 4(3);

| (c) | the results provided by the securitisation repository to the reporting entity pursuant to Article 4(6); |
| --- | --- |

(c)

the results provided by the securitisation repository to the reporting entity pursuant to Article 4(6);

| (d) | any explanation provided by the reporting entity as to why the submitted information is incomplete or inconsistent, or as to why there is no written confirmation as referred to in Article 4(7); |
| --- | --- |

(d)

any explanation provided by the reporting entity as to why the submitted information is incomplete or inconsistent, or as to why there is no written confirmation as referred to in Article 4(7);

| (e) | in a reporting log, the details of any corrections or cancellations submitted by the reporting entity; |
| --- | --- |

(e)

in a reporting log, the details of any corrections or cancellations submitted by the reporting entity;

| (f) | any other information produced or submitted pursuant to this Regulation. |
| --- | --- |

(f)

any other information produced or submitted pursuant to this Regulation.

2.   Each record shall be retained for 10 years following the termination of the securitisation to which that record relates.

3.   The reporting log referred to point (d) of paragraph 1 shall include the unique identifier of the securitisation, the item code, the timestamp of the affected submission, the timestamp of the changes and a clear description of the changes to the submitted information, including the previous and new contents of that information.

Article 9

Entry into force

This Regulation shall enter into force on the twentieth day following its publication in the Official Journal of the European Union.

Official Journal of the European Union

This Regulation shall be binding in its entirety and directly applicable in all Member States.

Done at Brussels, 29 November 2019.

For the Commission

The President

Jean-Claude JUNCKER

---

(1)  
  OJ L 347, 28.12.2017, p. 35.

1

(2)  Regulation (EU) No 648/2012 of the European Parliament and of the Council of 4 July 2012 on OTC derivatives, central counterparties and trade repositories (OJ L 201, 27.7.2012, p. 1).

2

(3)  Regulation (EU) No 1095/2010 of the European Parliament and of the Council of 24 November 2010 establishing a European Supervisory Authority (European Securities and Markets Authority), amending Decision No 716/2009/EC and repealing Commission Decision 2009/77/EC (OJ L 331, 15.12.2010, p. 84).

3

(4)  Commission Delegated Regulation (EU) 2020/1224 of 16 October 2019 supplementing Regulation (EU) 2017/2402 of the European Parliament and of the Council with regard to regulatory technical standards specifying the information and the details of a securitisation to be made available by the originator, sponsor and SSPE (See page 1 of this Official Journal).

4

(5)  Commission Implementing Regulation (EU) 2020/1225 of 29 October 2019 laying down implementing technical standards with regard to the format and standardised templates for making available the information and details of a securitisation by the originator, sponsor and SSPE (See page 217 of this Official Journal).

5

(6)  Commission Implementing Regulation (EU) 2020/1227 of 12 November 2019 laying down implementing technical standards with regard to templates for the provision of information in accordance with the STS notification requirements (See page 315 of this Official Journal).

6

---

ANNEX

Data completeness scoring matrix and rejection categories

Table 1

Data completeness scoring matrix

| | | |
| --- | --- | --- |
| | | Input 1: Percentage of fields entered as ‘ND1’ |
| | | Input 1 = 0 % | 0 % < Input 1 ≤ 10 % | 10 % < Input 1 ≤ 30 % | Input 1 > 30 % |
| Input 2: Percentage of fields entered as ‘ND2’, ‘ND3’, or ‘ND4-YYYY-MM-DD’ | Input 2 = 0 % | A1 | B1 | C1 | D1 |
| 0 % < Input 2 ≤ 20 % | A2 | B2 | C2 | D2 |
| 20 % < Input 2 ≤ 40 % | A3 | B3 | C3 | D3 |
| Input 2 > 40 % | A4 | B4 | C4 | D4 |

Input 1: Percentage of fields entered as ‘ND1’

Input 1 = 0 %

0 % < Input 1 ≤ 10 %

10 % < Input 1 ≤ 30 %

Input 1 > 30 %

Input 2: Percentage of fields entered as ‘ND2’, ‘ND3’, or ‘ND4-YYYY-MM-DD’

Input 2 = 0 %

A1

B1

C1

D1

0 % < Input 2 ≤ 20 %

A2

B2

C2

D2

20 % < Input 2 ≤ 40 %

A3

B3

C3

D3

Input 2 > 40 %

A4

B4

C4

D4

Table 2

Rejection categories

| Rejection categories | Reason |
| --- | --- |
| Schema | The submission of information has been rejected because of a non-compliant schema. |
| Permission | The submission of information has been rejected because the reporting entity has not been granted permission to report on behalf of the originator, sponsor or SSPE. |
| Logical | The submission of information has been rejected because the item code does not match the available values in Table 3 of Annex 1 of Delegated Regulation (EU) 2020/1224. |
| Business | The submission of information has been rejected because the data submission does not comply with one or more content validations. |
| Representativeness | The submission of information has been rejected pursuant to Article 4(6). |

Rejection categories

Reason

Schema

The submission of information has been rejected because of a non-compliant schema.

Permission

The submission of information has been rejected because the reporting entity has not been granted permission to report on behalf of the originator, sponsor or SSPE.

Logical

The submission of information has been rejected because the item code does not match the available values in Table 3 of Annex 1 of Delegated Regulation (EU) 2020/1224.

Business

The submission of information has been rejected because the data submission does not comply with one or more content validations.

Representativeness

The submission of information has been rejected pursuant to Article 4(6).

---