Commission Implementing Regulation (EU) 2025/1339 of 10 July 2025 laying down implementing technical standards for the application of Regulation (EU) 2023/2859 of the European Parliament and of the Council with regard to certain tasks of the collection bodies

Technical automated validations

Article 1

1.   Where a specific machine-readable format is required by any of the acts referred to in Article 1(1), point (a), of Regulation (EU) 2023/2859, collection bodies shall verify that the information submitted to them pursuant to that act is compliant with the machine-readable format specified in those acts. 2.   Where no specific machine-readable format is required by any of the acts referred to in Article 1(1), point (a), of Regulation (EU) 2023/2859, collection bodies shall verify that the information submitted to them: (a) is submitted in one of the formats referred to in Article 7(1) or in other data extractable format required by any binding Union legislative act; (b) contains text that can be extracted by a machine. 3.   Collection bodies shall verify that: (a) the data submitted is complete and compliant with the metadata specification set in the Annex to this Regulation; (b) the metadata is consistent with any other metadata provided otherwise by the same entity; (c) where provided by the submitting entity, the metadata indicating the legal entity identifier of the submitting entity complies with the specifications laid down in Article 2 of Implementing Regulation (EU) 2025/1338 at the moment of submitting the information to the ESAP; and (d) where provided by the submitting entity, the metadata indicating the legal entity identifier of the entity to which information relates complies with the specifications laid down in Article 2 of Implementing Regulation (EU) 2025/1338 at the date or period to which the information relates. 4.   Where a qualified electronic seal is required in accordance with Article 5(9) of Regulation (EU) 2023/2859, collection bodies shall: (a) perform the validations set out in Article 32(1) of Regulation (EU) No 910/2014; and (b) verify that the qualified electronic seal accompanying the information submitted to them complies with Article 2 of this Regulation. 5.   Collection bodies shall reject information that does not comply with any one of the requirements set out in paragraphs 1 to 4. 6.   Collection bodies shall undertake their best efforts to provide the submitting entities with detailed information on the results of the automated validations referred to in paragraphs 1 to 4 within 60 minutes after they have received the information. 7.   In duly justified exceptional circumstances, including major accidents and errors, deliberate attacks and natural events, collection bodies may provide the results of the automated validations beyond the time limit set out in paragraph 6. In that case, collection bodies shall undertake their best efforts to provide the results of the automated validations to the submitting entities within 60 minutes after the resolution of the relevant exceptional circumstance.

Characteristics of the qualified electronic seal

Article 2

1.   Where Member State require a qualified electronic seal, that seal accompanying the information shall comply with the list of technical specifications set out in the Annex to Implementing Decision (EU) 2015/1506 and shall be at conformance level LT or higher. 2.   Where the submitting entity is identified with a legal entity identifier compliant with ISO 17442, the qualified electronic seal shall be based on the qualified certificate in which the submitting entity is identified with that legal entity identifier.

Open standard licence

Article 3

The use and re-use of the information made available to the ESAP by the collection bodies shall be subject to the conditions of the Creative Commons public domain dedication (CC0) or any equivalent open licence allowing for unrestricted use and re-use of data. That is without prejudice to information covered by copyright and other related rights, the use and re-use of which shall be governed by the conditions of the Creative Commons Licence BY-NC-ND or any equivalent open license.

Characteristics of the data collection API

Article 4

The application programming interface (API) for the collection of ESAP data from collection bodies shall: (a) allow collection bodies to make available the information, the accompanying metadata for that information and, where required, the qualified electronic seal to the ESAP and receive feedback on the data exchanged; (b) support the formats for the information specified in Article 7; (c) support the formats for the metadata specified in Article 5; (d) rely on secure internet protocols, including SFTP or HTTPS to exchange data via the transfer of files; (e) allow the European Securities and Markets Authority (ESMA) to implement access control procedures; and (f) incorporate any changes or update requested by ESMA to ensure compliance with points (a) to (e).

Characteristics of metadata

Article 5

1.   When providing the ESAP with information referred to in Article 1(1), point (a), of Regulation (EU) 2023/2859, collection bodies shall make available to the ESAP the relevant accompanying metadata in accordance with the table of the Annex to this Regulation. 2.   Collection bodies shall provide the metadata in a common format in accordance with the ISO 20022 methodology. Where the information is prepared in a machine-readable format pursuant to any of the Union legislative acts referred to in Article 1(1), point (a), of Regulation (EU) 2023/2859, collection bodies shall ensure that the metadata for that information is provided either in accordance with the ISO 20022 methodology or in the same format as the information.

Time limits for collection bodies

Article 6

1.   Without prejudice to other legal obligations stemming from Union legislative acts, collection bodies shall provide to the ESAP the information, the metadata for that information and, where required, the qualified electronic seal as soon as possible, and no later than 60 minutes after the information has been submitted to the collection body for the purpose of making it accessible on the ESAP and the submission of the information has passed the technical automated validations referred to in Article 1. 2.   In duly justified exceptional circumstances, including major accidents and errors, deliberate attacks and natural events, collection bodies may provide the relevant information beyond the time limits set out in paragraph 1. In that case, collection bodies shall inform ESMA as soon as possible during their working hours and undertake their best efforts to provide the information within 60 minutes after the resolution of the relevant exceptional circumstance.

Indicative list and characteristics of acceptable data formats

Article 7

1.   HTML, PDF and txt formats shall be deemed to constitute data extractable formats, where those formats allow extraction of text by a machine and are human-readable. 2.   XML, XBRL, XBRL-csv, XBRL-xml and inline XBRL formats shall be deemed to constitute machine-readable formats, where those formats are structured so that software applications can easily identify, recognise and extract specific data, including individual statements of fact, and their internal structure contained therein.

Entry into force and application

Article 8

This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union . It shall apply from 10 July 2026.

ANNEXSupplementary provisions

ANNEX Table Metadata Number Field Format 1. Name(s) of the entity that submitted the information Free text field up to 500 alphanumeric characters 2. Name(s) of the natural or legal person to which the information relates Free text field up to 500 alphanumeric characters 3. Legal entity identifier of the entity that submitted the information ISO 17442 Legal Entity Identifier (LEI) 20 alphanumeric character code 4. Legal entity identifier of the legal person to which the information relates ISO 17442 Legal Entity Identifier (LEI) 20 alphanumeric character code 5. Type of information submitted by the entity Taxonomy in accordance with the common list of types of information as set out in Table 1 of Annex to Implementing Regulation (EU) 2025/1338 6. Size of the entity by category that submitted the information Taxonomy in accordance with the common list of categories of entities by size as set out in Table 2 of Annex to Implementing Regulation (EU) 2025/1338 7. Size of the legal person to which the information relates Taxonomy in accordance with the common list of categories of entities by size as set out in Table 2 of Annex to Implementing Regulation (EU) 2025/1338 8. Country of registered office of the legal person to which the information relates ISO 3166 – 2-character country code 9. Industry sector(s) of the economic activities of the natural or legal person to which the information relates Taxonomy in accordance with the common list of industry sectors as set out in Table 3 of Annex to Implementing Regulation (EU) 2025/1338 10. Personal data flag ‘true’ – the information submitted contains personal data ‘false’ – information submitted does not contain personal data 11. Voluntary or mandatory nature of the information submitted ‘true’ – voluntary ‘false’ – mandatory 12. Date and time when the data was submitted by the entity to the collection body ISO 8601 date in the Coordinated Universal Time (UTC) time format YYYY-MM-DDThh:mm:ssZ 13. Date or beginning of the period to which the information relates ISO 8601 date in the Coordinated Universal Time (UTC) format YYYY-MM-DD 14. Date or end of the period to which the information relates ISO 8601 date in the Coordinated Universal Time (UTC) format YYYY-MM-DD 15. Collection body responsible for the collection of the information Name of the collection body designated for the collection of the data as published on ESMA’s website pursuant to Article 4 of Regulation (EU) 2023/2859 16. Home Member State, where applicable ISO 3166 – 2-character country code 17. Host Member State, where applicable ISO 3166 – 2-character country code 18. Instrument or product identifier, where applicable ISIN or up to 52 alphanumeric characters 19. Unique data record identifier Free text up to 140 alphanumeric characters 20. Data file reference Free text up to 500 alphanumeric characters 21. Qualified electronic seal file reference, where applicable Free text up to 500 alphanumeric characters 22. Type of submission NEWT = New (to be used for new information) MODI = Modify (to be used for modifications in light of newly available information) EROR = Error (to be used in case of errors leading to removal of the entire record) CORR = Correction (to be used when information previously reported is found to be incorrect and should be corrected) 23. Version of the dataset (data and metadata) Integer number 24. Legal framework Taxonomy in accordance with list of Union legislative acts referred to in Article 1(1) point (a), of Regulation (EU) 2023/2859 25. Historical information flag ‘true’ – Yes ‘false’ – No 26. Language in which the information was submitted ISO 639-1 – 2-character language code