Commission Delegated Regulation (EU) 2025/1155 of 12 June 2025 supplementing Regulation (EU) No 600/2014 of the European Parliament and of the Council with regard to regulatory technical standards specifying the input and output data of consolidated tapes, the synchronisation of business clocks and the revenue redistribution by the consolidated tape provider for shares and ETFs, and repealing Commission Delegated Regulation (EU) 2017/574
Data as of 2026-07-04 · Compiled from an official source version. Later amendments or repeals may not be reflected; the official text prevails. · Read the official text ↗
Definitions
For the purposes of this Regulation, the following definitions shall apply: (a) ‘input data’ means data transmitted by data contributors to the CTP, in accordance with Article 22a(1) of Regulation (EU) No 600/2014; (b) ‘output data’ means data disseminated by the CTP, in accordance with Article 27h(1), point (d), of Regulation (EU) No 600/2014.
Minimum requirements for the quality of transmission protocols
1. For the transmission of input data, data contributors shall offer CTPs at least one transmission protocol that complies with the minimum requirements for the quality of transmission protocols specified in Tables 1 to 4 of Annex I. 2. Upon agreement on the selected transmission protocol for the transmission of input data, CTPs and data contributors shall ensure that the minimum requirements referred to in paragraph 1 are consistently met without interruption.
Real time transmission of data
1. Data contributors shall transmit input data to the data centres of the CTPs as close to real time as technically possible and without artificial delays. 2. Data contributors shall transmit to the CTP for shares and ETFs pre-trade input data as close to real time as is technically possible and in any case no later than 50 milliseconds after the timestamp of the order with a 95 % of confidence interval measured on a daily basis. 3. Data contributors shall transmit to the CTP for shares and ETFs post-trade input data related to transactions executed on a trading venue as close to real time as is technically possible and in any case no later than 50 milliseconds after the timestamp of the transaction with a 95 % of confidence interval measured on a daily basis. 4. Data contributors shall transmit to the CTP for shares and ETFs post-trade input data related to transactions executed outside of a trading venue as close to real time as is technically possible and in any case within 50 milliseconds after the timestamp of the reception of the trade report from the investment firm or DPE with a 95 % of confidence interval measured on a daily basis. 5. Data contributors shall transmit to the CTP for bonds and to the CTP for OTC derivatives post-trade input data related to transactions executed on a trading venue as close to real time as is technically possible and in any case within 500 milliseconds after the timestamp of the execution of the relevant transaction. 6. Data contributors shall transmit to the CTP for bonds and to the CTP for OTC derivatives post-trade input data related to transactions executed outside of a trading venue as close to real time as is technically possible and in any case within 500 milliseconds after the timestamp of the reception of the trade report from the investment firm or DPE.
Data standards and format for the transmission of input data
Data contributors shall transmit to the data centres of CTPs input data in a format that adheres to the ISO 20022 methodology.
Data to be transmitted to the CTP for bonds
1. With regard to core market data for a given bond, data contributors shall transmit to the data centre of the CTP, by reference to each transaction, the details set out in Table 6 of Annex II that are flagged as ‘input’ or ‘both’ in the last column of Table 6. 2. With regard to regulatory data, data contributors shall transmit to the data centre of the CTP, by reference to each financial instrument, the details set out in Table 2 of Annex II that are flagged as ‘both’ in the last column of Table 2. 3. With regard to regulatory data, data contributors shall transmit to the data centre of the CTP, by reference to each trading system, the details set out in Table 3 of Annex II that are flagged as ‘both’ in the last column of Table 3.
Data to be transmitted to the CTP for shares and ETFs
1. With regard to post-trade core market data for a given share or ETF, data contributors shall transmit to the data centre of the CTP all of the following: (a) by reference to each transaction, the details set out in Table 7 of Annex II that are flagged as ‘input’ or ‘both’ in the last column of Table 7; (b) on the first day of each month ( n ), the list of transactions which were executed in the month prior to that ( n -1) in accordance with Article 4(1), point (c), of Regulation (EU) No 600/2014. 2. With regard to pre-trade core market data for a given share or ETF, data contributors shall transmit to the data centre of the CTP, by reference to each best bid and offer and each price at which the auction system would best satisfy its trading algorithm, the details set out in Table 2 of Annex III. 3. With regard to regulatory data, data contributors shall transmit to the data centre of the CTP, by reference to each financial instrument, the details set out in Table 4 of Annex II that are flagged as ‘both’ in the last column of Table 4. 4. With regard to regulatory data, data contributors shall transmit to the data centre of the CTP, by reference to each trading system, the details set out in Table 5 of Annex II that are flagged as ‘both’ in the last column of Table 5.
Data to be disseminated by the CTP for bonds
1. With regard to core market data for a given bond, the CTP shall disseminate, by reference to each transaction, the details set out in Table 6 of Annex II that are flagged as ‘output’ or ‘both’ in the last column of Table 6. 2. With regard to regulatory data relating to bonds, the CTP shall disseminate: (a) by reference to each financial instrument, the details set out in Table 2 of Annex II that are flagged as ‘output’ or ‘both’ in the last column of Table 2; (b) by reference to each trading system, the details set out in Table 3 of Annex II that are flagged as ‘output’ or ‘both’ in the last column of Table 3.
Data to be disseminated by the CTP for shares and ETFs
1. With regard to post-trade core market data for a given share or ETF, the CTP shall disseminate, by reference to each transaction, the details set out in Table 7 of Annex II that are flagged as ‘output’ or ‘both’ in the last column of Table 7. 2. With regard to pre-trade core market data for a given share or ETF, the CTP shall disseminate, by reference to the European best bid and offer or the price at which the auction system would best satisfy its trading algorithm, the details set out in Tables 3, 4 and 5 of Annex III. 3. With regard to regulatory data relating to shares and ETFs, the CTP shall disseminate all of the following: (a) by reference to each financial instrument, the details set out in Table 4 of Annex II that are flagged as ‘output’ or ‘both’ in the last column of that Table; (b) by reference to each trading system, the details set out in Table 5 of Annex II that are flagged as ‘output’ or ‘both’ in the last column of Table 5.
Dissemination of output data to ensure machine-readability and human-readability
1. CTPs shall disseminate the output data in a Graphical User Interface to ensure human readability. 2. CTPs shall also disseminate the output data in at least the following two formats simultaneously: (a) Comma-Separated Values; (b) a format that adheres to the ISO 20022 methodology. 3. CTPs shall: (a) make instructions available to the public, explaining how and where to easily access and use the data, including the identification of the electronic format; (b) make public any changes to the instructions referred to in point (a) at least three months before they come into effect, unless there is an urgent and duly justified need for changes in instructions to take effect more quickly; (c) include on the homepage of their website a link to the instructions referred to in point (a).
Management of incomplete or potentially erroneous information by CTPs
1. CTPs shall set up and maintain appropriate arrangements that ensure that they accurately collect, consolidate and publish the information received from data contributors and do not introduce any errors or omit information. CTPs shall correct the information where they have themselves caused the error or omission. 2. CTPs shall continuously monitor in real-time the performance of their IT systems to ensure that the input data they have received are successfully consolidated and published. 3. CTPs shall perform periodic reconciliations between the input data they receive and the output data they publish to verify whether the output data have been correctly published. 4. CTPs shall put in place mechanisms to confirm to data contributors that they have received the input data and shall assign a transaction identification code to each input data message they receive. CTPs shall refer to the transaction identification code in any subsequent communication with the data contributor in relation to a specific set of information reported. 5. CTPs shall set up and maintain arrangements to identify received input data that are incomplete, do not fulfil the requirements laid down in Articles 5 and 6, or contain information that is likely to be erroneous. Those arrangements shall include automated price and volume alerts, taking into account: (a) the sector and the segment in which the financial instrument is traded; (b) liquidity levels, including historical trading levels; (c) appropriate price and volume benchmarks; (d) where needed, other parameters that are proper for the characteristics of the financial instrument. 6. CTPs that find out that the input data they received are incomplete or do not fulfil any other reporting requirements in this Regulation shall not publish those input data and shall promptly alert the data contributor submitting those input data. 7. CTPs that find out that the input data they received are likely to be erroneous shall disseminate the corresponding output data and shall promptly flag the potential data quality issue both to the public and to the data contributor. 8. Upon receiving a notification of a data quality issue, data contributors shall acknowledge the issue and, where necessary, initiate the process of resubmitting corrected data. 9. CTPs shall monitor the timeliness of input data received from data contributors for the identification of serious and repeated breaches of the requirements laid down in Article 3. 10. CTPs shall delete and amend information in a trade report upon request from the data contributor providing the information where that data contributor cannot delete or amend its own information for technical reasons. 11. CTPs shall communicate with their clients via formalised interactive communication mechanisms through which data users may flag to the CTP any potential inaccuracies in the dissemination of output data. 12. CTPs shall publish non-discretionary policies describing the measures to enforce data quality and how those measures are applied. Those policies shall contain clear guidance on the application of such measures, ensuring adherence to non-discretionary application, proportionality, timeliness, consistency, and transparency.
Reference time
Operators of trading venues and their members, participants or users, systematic internalisers, DPEs, APAs and CTPs shall synchronise the business clocks they use to record the date and time of any reportable event with the Coordinated Universal Time (‘UTC’) issued and maintained by the timing centres listed in the database maintained by the Bureau international des poids et mesures. Operators of trading venues and their members, participants or users, systematic internalisers, DPEs, APAs and CTPs may also synchronise the business clocks they use to record the date and time of any reportable event with UTC disseminated by a satellite system, provided that any offset from UTC is accounted for and removed from the timestamp.
Level of accuracy for operators of trading venues and systematic internalisers
1. Operators of trading venues and systematic internalisers shall ensure that their business clocks adhere to the levels of accuracy specified in Table 1 of Annex IV according to the gateway-to-gateway latency of each of their trading systems. Gateway-to-gateway latency shall be the time measured from the moment a message is received by an outer gateway of the trading venue’s system, sent through the order submission protocol, processed by the matching engine, and then sent back until an acknowledgement is sent from the gateway. 2. By way of derogation from paragraph 1, operators of trading venues and systematic internalisers that operate a voice trading system, or a request for quote trading system where the response requires human intervention or does not allow for algorithmic trading, or a system that formalises negotiated transactions in accordance with Article 4(1), point (b), of Regulation (EU) No 600/2014, shall ensure that their business clocks do not diverge by more than one second from UTC referred to in Article 11. The operator of the trading venue or systematic internaliser shall ensure that times are recorded to at least a one second granularity. 3. Operators of trading venues and systematic internalisers that operate multiple types of trading systems shall ensure that each system adheres to the level of accuracy applicable to that system in accordance with paragraphs 1 and 2.
Level of accuracy for members, participants or users of a trading venue
1. Members, participants, or users of trading venues shall ensure that their business clocks used to record the time of reportable events adhere to the level of accuracy specified in Table 2 of Annex IV. 2. Members, participants or users of trading venues that engage in multiple types of trading activities shall ensure that the systems that they use to record the time of reportable events adhere to the level of accuracy applicable to each of those trading activities in accordance with the requirements set out in Table 2 of Annex IV.
Level of accuracy for DPEs
1. DPEs shall record the date and time of reportable events up to one millisecond or better. 2. DPEs shall ensure that their business clocks used to record the time of reportable events do not diverge by more than one millisecond from the reference time laid down in Article 11. 3. By way of derogation from paragraphs 1 and 2, DPEs that have also acquired the status of systematic internaliser shall comply with Article 12.
Level of accuracy for APAs and CTPs
1. APAs and CTPs shall record the date and time of reportable events up to one millisecond or better. 2. APAs and CTPs shall ensure that their business clocks used to record the time of reportable events do not diverge by more than one millisecond from the reference time laid down in Article 11.
Compliance with the maximum divergence requirements
Operators of trading venues and their members, participants, or users shall establish a system of traceability to UTC. They shall be able to demonstrate traceability to UTC by documenting the system design, functioning and specifications. They shall be able to identify the exact point at which a timestamp is applied and to demonstrate that the point within the system where the timestamp is applied remains consistent. They shall review the compliance of the system of traceability to UTC with this Regulation at least once a year.
Determination of the amount of the revenue to be redistributed, of the eligible data contributors, and the relevant assessment periods
1. For the purposes of redistributing part of the revenue generated by the consolidated tape to data contributors that meet one or more of the criteria laid down in Article 27h(6) of Regulation (EU) No 600/2014, the CTP for shares and ETFs shall determine: (a) the amount of the revenue to be redistributed, based on the total revenue generated by the consolidated tape over the calculation window, as specified by the CTP; and (b) the list of regulated markets, MTFs, and SME growth markets that transmitted input data over the assessment period, either for the full period or for part of it (the ‘eligible data contributors’). 2. After having determined the amount of revenue to be redistributed and the list of eligible data contributors in accordance with paragraph 1, the CTP for shares and ETFs shall perform the calculations set out in Articles 18 to 21. The CTP for shares and ETFs shall perform such calculations at least on an annual basis and, in any case, before the twentieth day of the month following the calculation window, using the trades recorded by each data contributor over the assessment period. The CTP for shares and ETFs shall apply the resulting percentages of such calculations retroactively over the latest calculation window. 3. For the purposes of paragraphs 1 and 2, the calculation window shall correspond to each individual period over which part of the revenue of the consolidated tape is redistributed. 4. For the purposes of paragraph 2, the assessment period shall correspond to the 12 months over which the relevant trading volume to be multiplied by each individual weighting is considered.
Methodology for calculating the amount of the revenue to be redistributed to eligible data contributors meeting the criterion under Article 27h(6), point (a), of Regulation (EU) No 600/2014
1. To calculate the amount of the revenue to be redistributed to eligible data contributors that meet the criterion under Article 27h(6), point (a), of Regulation (EU) No 600/2014, the CTP for shares and ETFs shall determine the total annual trading volume generated in shares for each eligible data contributor that is a regulated market or an SME growth market by summing each transaction record received by that data contributor. 2. The CTP for shares and ETFs shall determine the total annual trading volume in shares in the Union by summing all transaction records received by all data contributors. 3. For the purposes of the calculations referred to in paragraphs 1 and 2, transactions shall be single counted. 4. To determine whether an eligible data contributor meets the criterion laid down in Article 27h(6), point (a), of Regulation (EU) No 600/2014, the CTP for shares and ETFs shall divide the amount determined under paragraph 1 by the amount determined under paragraph 2 for each regulated market and SME growth market, identified by operating Market Identifier Code (‘MIC’), as specified in ISO 10383. 5. For each eligible data contributor meeting the criterion laid down in Article 27h(6), point (a), of Regulation (EU) No 600/2014, identified by segment MIC, as specified in ISO 10383, or by operating MIC, whenever there is no segment MIC, the CTP for shares and ETFs shall multiply the relevant trading volume generated by that MIC, as determined under paragraph 1, by a weighting of 4,5.
Methodology for calculating the amount of revenues to be redistributed to eligible data contributors meeting the criterion under Article 27h(6), point (b), of Regulation (EU) No 600/2014
1. To determine whether an eligible data contributor meets the criterion laid down in Article 27h(6), point (b), of Regulation (EU) No 600/2014, the CTP for shares and ETFs shall, for each eligible data contributor, assess whether such data contributor provided initial admission to trading of shares or ETFs on 27 March 2019 or thereafter. That assessment shall be based on the information published by ESMA in accordance with Article 7(6) of Commission Delegated Regulation (EU) 2017/585 ( 9 ) . The CTP for shares and ETFs shall determine: (a) for each eligible data contributor meeting the criterion laid down in Article 27h(6), point (a), of Regulation (EU) No 600/2014, the total annual trading volume generated in shares and ETFs, by summing each transaction record received by that data contributor; (b) for each eligible data contributor not meeting the criterion laid down in Article 27h(6), point (a), of Regulation (EU) No 600/2014, the total annual trading volume pertaining to the shares and ETFs that were initially admitted to trading on 27 March 2019 or thereafter, by summing each relevant transaction record received by that data contributor. For the purposes of the calculations referred to in points (a) and (b), transactions shall be single counted. 2. For each eligible data contributor meeting the criterion laid down in Article 27h(6), point (b), of Regulation (EU) No 600/2014, identified by segment MIC, as specified in ISO 10383, or by operating MIC, whenever there is no segment MIC, the CTP for shares and ETFs shall multiply the relevant trading volume generated by that MIC, as determined under paragraph 1, second subparagraph, by a weighting of 4,0.
Methodology for calculating the amount of revenues to be redistributed to eligible data contributors meeting the criterion under Article 27h(6), point (c), of Regulation (EU) No 600/2014
1. To determine whether an eligible data contributor meets the criterion laid down in Article 27h(6), point (c), of Regulation (EU) No 600/2014, the CTP for shares and ETFs shall, for each eligible data contributor, determine the total annual pre-trade transparent trading volume generated in shares and ETFs. For the purposes of the calculation referred to in the first subparagraph, the CTP for shares and ETFs shall include all transaction records received from the eligible data contributors which are not flagged as negotiated transactions subject to conditions other than the current market price (‘PRIC flag’), reference price transactions (‘RFPT flag’), negotiated transactions in liquid financial instruments (‘NLIQ flag’), negotiated transactions in illiquid financial instruments (‘OILQ flag’) as set out in Table 4 of Annex I to Delegated Regulation (EU) 2017/587, or as transactions subject to the pre-trade large in scale waiver as set out in Article 6(1), point (b). Transactions shall in all cases be single counted. 2. For each eligible data contributor meeting the criterion laid down in Article 27h(6), point (c), of Regulation (EU) No 600/2014, identified by segment MIC, as specified in ISO 10383, or by operating MIC whenever there is no segment MIC, the CTP for shares and ETFs shall multiply the relevant trading volume generated by that MIC, as determined under paragraph 1 of this Article, by a weighting of 1,5.
Methodology for determining the amount of revenue to be redistributed
1. For each eligible data contributor, the CTP for shares and ETFs shall sum up the results of the multiplications of the weightings by the trading volumes, as set out in Articles 18 to 20. 2. The CTP for shares and ETFs shall determine the total sum of the results of the calculations under paragraph 1 for all eligible data contributors. 3. The CTP for shares and ETFs shall divide the sum per data contributor, as set out in paragraph 1, by the total sum, as set out in paragraph 2. The resulting percentages for each data contributor shall be multiplied by the total amount of the revenue to be redistributed.
Criteria for the temporary suspension of the participation in the revenue redistribution scheme
1. When deciding whether to suspend the participation of a data contributor in the revenue redistribution scheme as laid down in Article 27h(8), point (c), of Regulation (EU) No 600/2014, the CTP for shares and ETFs shall take into account whether any of the following criteria is met: (a) for three consecutive days, the data contributor has failed to submit trade reports or order reports or has submitted more than three trade reports or order reports later than as close to real time as is technically possible, as laid down in Article 3, and those trade reports or order reports account for at least a volume of transactions or orders that in a percentage is not lower than 10 % of the total volume of transactions or orders submitted in a single day; (b) for three consecutive days, the data contributor has submitted more than three trade reports or order reports that are incomplete or contain potentially erroneous data, as laid down in Article 10, and those trade reports or order reports account for at least a volume of transactions or orders that in percentage is not lower than 10 % of the total volume of transactions or orders submitted in a single day; (c) the data contributor no longer meets the minimum requirements for the quality of the transmission protocols set out in Article 2; (d) the data contributor no longer meets the requirements on the level of accuracy to which business clocks are to be synchronised, as set out in Chapter III. 2. The CTP for shares and ETFs may decide not to suspend the participation of a data contributor in the revenue redistribution scheme where the situations set out in paragraph 1 occurred due to circumstances that were out of the ordinary, unavoidable, or unexpected.
Procedure for the temporary suspension of the participation in the revenue redistribution scheme
1. Where the CTP for shares and ETFs has found a repeated and serious breach by a data contributor of the criteria set out in Article 22(1), points (a) and (b), it shall inform the data contributor thereof as soon as possible and, in any case, within two business days from the moment it has found the repeated and serious breach. In the notification to the data contributor, the CTP shall: (a) identify the trade reports or order reports in relation to which the data contributor is deemed in breach and the number of days for which the revenue redistribution may be suspended; (b) provide information to the data contributor supporting its assessment. Within one week from the notification referred to in the first subparagraph, the data contributor may provide additional information to the CTP seeking to prove that the data requirements were not breached, or that an exceptional circumstance, as referred to in Article 22(2), occurred, and request that the CTP reviews its assessment based on the additional information. The CTP shall review its assessment taking into account the additional information provided by the data contributor and, where it considers the information not to be complete, set a deadline by which the data contributor is to provide additional information. 2. On the last day of the period in relation to which the revenue is redistributed, the CTP shall draw up its final assessment on whether the criteria for the temporary suspension of the participation of a data contributor in the revenue redistribution scheme, in accordance with Article 22(1), are met. The CTP shall inform the data contributor of its final assessment within two business days after the last day of the period in relation to which revenue is redistributed. The CTP shall inform the data contributor of the reasons for its final assessment, including the data requirements deemed in breach, and specify the amount of revenue that may be retained. Within one week from receipt of the information referred to in the second subparagraph of this paragraph, the data contributor may provide additional information to the CTP proving that the data requirements referred to in Article 22a, 22b and 22c of Regulation (EU) No 600/2014 were not breached, or that an exceptional circumstance, as referred to in Article 22(2), occurred, and request that the CTP reviews its final assessment based on the additional information. The CTP shall review its final assessment taking into account the additional information provided by the data contributor and, where it considers the information not to be complete, set a deadline by which the data contributor is to provide additional information. 3. The CTP shall inform the data contributor concerned of its final decision on the suspension of the participation in the revenue redistribution scheme no later than two weeks after informing the data contributor of the final assessment referred to in the second subparagraph of paragraph 2. Where the CTP takes a final decision to suspend a data contributor from the revenue redistribution scheme it may redistribute the retained revenue to the other eligible data contributors in the redistribution window following that decision.
Conditions for the resumption of revenue redistribution and for the provision of revenue retained plus interest
1. Where the CTP for shares and ETFs finds, on the basis of the additional information provided by the data contributor in accordance with Article 23(1), second subparagraph, and Article 23(2), third subparagraph, that the data requirements referred to in Articles 22a, 22b and 22c of Regulation (EU) No 600/2014 have not been breached, it shall redistribute the revenue retained, with interest, no later than two weeks after the final decision referred to in Article 23(3). 2. For the purposes of the calculation of the interest referred to in paragraph 1, the CTP shall take into account the average rate of the European Central Bank’s deposit facility, or where the CTP is established in a Member State whose currency is not the euro, the official interest rate for overnight credit charged by the central bank of the Member State where the CTP is established, over the period of the suspension of the revenue redistribution scheme.
Repeal
Delegated Regulation (EU) 2017/574 is repealed with effect from 2 March 2026. References to the repealed Delegated Regulation shall be construed as references to this Regulation and shall be read in accordance with the correlation table set out in Annex V.
Entry into force and application
This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union . Articles 11 to 16 shall apply from 2 March 2026.
ANNEX I Minimum requirements for the quality of the transmission protocols referred to in Article 2 Table 1 Performance requirements Metrics/features Minimum requirements Primary OSI Layers Latency Latency shall be maintained below 50 milliseconds for the transmission of data to the CTP for shares and ETFs. Latency shall be maintained below 500 milliseconds for the transmission of data to the CTP for bonds. Latency shall be maintained below 500 milliseconds for the transmission of data to the CTP for derivatives. Layer 3 (Network) Throughput Throughput shall exceed 100 Megabits per second (Mbps). Layer 1 (Physical), Layer 2 (Data link) Connection setup time Round Trip Time (RTT) for connection setup shall be less than 500 milliseconds. Layer 4 (Transport) Scalability The protocol shall support operation in clustered or load-balanced environments. Layer 2 (Data link), Layer 3 (Network), Layer 4 (Transport) and Layer 7 (Application) Table 2 Reliability requirements Metrics/features Minimum requirements Primary OSI Layers Error detection mechanism The protocol shall include error detection mechanisms to ensure accurate identification of data transmission errors. Layer 2 (Data link), or Layer 4 (Transport), or Layer 7 (Application) Error correction mechanism The protocol shall incorporate error correction mechanisms to automatically rectify detected errors. Layer 2 (Data link), or Layer 4 (Transport), or Layer 7 (Application) Recovery mechanism The protocol shall feature recovery mechanisms to swiftly recover from transmission failures or interruptions, ensuring seamless continuity of data transmission operations. Layer 4 (Transport), or Layer 5 (Session), or Layer 7 (Application) Table 3 Security requirements Metrics/features Minimum requirements Primary OSI Layers Secure transport layer The protocol shall support a secure transport layer to ensure the confidentiality of data during transmission. Layer 4 (Transport), Layer 7 (Application) Authentication The protocol shall support credentials-based or certificate-based authentication mechanisms to verify the identity of communicating parties. Layer 7 (Application) Authorisation The protocol shall implement authorisation mechanisms to control access to specific resources or functionalities based on user roles or permissions. Layer 7 (Application) Non-repudiation The protocol shall incorporate non-repudiation mechanisms to ensure that the originator of a message cannot deny sending it. Layer 7 (Application) Table 4 Compatibility requirements Metrics/features Minimum requirements Primary OSI Layers Open solution The implementation of the protocols shall adhere to non-proprietary standards. Layer 7 (Application) Interoperability The protocol shall support at least one widely recognised internet standard. Layer 7 (Application) Backward compatibility The protocol shall be capable to work with older versions of itself or previous technologies. Layer 7 (Application)
ANNEX II Regulatory data and post-trade core market data to be transmitted to and disseminated by the CTP for bonds, and the CTP for shares and ETFS according to Articles 5, 6, 7 and 8 Table 1 Symbols used in Tables 2, 3, 4, 5, 6 and 7 Symbol Data Type Definition {DATE_TIME_FORMAT} ISO 8601 date and time format Date and time in the following format: YYYY-MM-DDThh:mm:ss.ddddddZ. — ‘YYYY’ is the year; — ‘MM’ is the month; — ‘DD’ is the day; — ‘T’ – means that the letter ‘T’ shall be used — ‘hh’ is the hour; — ‘mm’ is the minute; — ‘ss.dddddd’ is the second and its fraction of a second; — ‘Z’ is UTC time. Dates and times shall be reported in UTC. {ISIN} 12 alphanumerical characters ISIN code, as defined in ISO 6166 {MIC} 4 alphanumerical characters Market identifier as defined in ISO 10383 {CURRENCYCODE_3} 3 alphanumerical characters 3-letter currency code, as defined by ISO 4217 currency codes Table 2 Regulatory data for bonds, per instrument # Field identifier Description Format Equivalent formats can be used, depending on the syntax used for data transmission Input/Output data field 1 Instrument identification code Code used to identify the financial instrument. {ISIN} Both 2 Instrument status start date and time Date and time from which the instrument status is valid. The level of granularity shall be in accordance with the requirements set out in Article 12. {DATE_TIME_FORMAT} Both 3 Currency Major currency in which the instrument is traded. {CURRENCYCODE_3} Both 4 Dissemination date and time Date and time when the instrument status is disseminated by the CTP. The level of granularity shall be in accordance with the requirements set out in Article 15. {DATE_TIME_FORMAT} Output 5 Instrument status Description of the status of the financial instrument. The status of the financial instrument shall be one of the following: (1) suspended from trading, on the trading venue identified in the field ‘Trading venue’, in accordance with Articles 32 and 52 of Directive 2014/65/EU; (2) removed from trading, on the trading venue identified in the field ‘Trading venue’, in accordance with Articles 32 and 52 of Directive 2014/65/EU; (3) subject to a trading halt, on the trading venue identified in the field ‘Trading venue’, in accordance with Articles 18(5) and 48(5) of Directive 2014/65/EU; (4) available for trading after a suspension, removal or halt. ‘SUSP’ – the instrument is suspended ‘RMOV’ – the instrument is removed ‘HALT’ – the instrument is subject to a trading halt ‘ACTV ” – the instrument is available for trading after a suspension, removal or halt Both 6 Trading venue Identification of the trading venue on which the instrument status is valid (segment MIC where available, otherwise operating MIC). The trading venue is a regulated market, an MTF or an OTF. {MIC} Both 7 Trading system Type of trading system on which the instrument is traded ‘CLOB’ – Central Limit Order Book ‘QDTS’ – Quote Driven Market ‘PATS’ – Periodic Auction ‘RFQT’ Request for Quotes ‘VOIC’ – Voice trading system ‘HYBR’ – Hybrid System ‘OTHR’ – Other Both Table 3 Regulatory data for bonds, per order matching system # Field identifier Description Format Equivalent formats can be used, depending on the syntax used for data transmission Input/Output data field 1 Trading venue Identification of the trading venue on which the order matching system status is valid (segment MIC, where available, otherwise operating MIC). The trading venue is a regulated market, an MTF or an OTF. {MIC} Both 2 Trading system Type of trading system on which the system status is provided ‘CLOB’ – Central Limit Order Book ‘QDTS’ – Quote Driven Market ‘PATS’ – Periodic Auction ‘RFQT’ – Request for Quotes ‘VOIC’ – Voice trading system ‘HYBR’ – Hybrid System ‘OTHR’ – Other Both 3 System status start date and time Date and time from which the system status is valid The level of granularity shall be in accordance with the requirements set out in Article 12. {DATE_TIME_FORMAT} Both 4 Dissemination date and time Date and time on which the system status is disseminated by the CTP. The level of granularity shall be in accordance with the requirements set out in Article 15. {DATE_TIME_FORMAT} Output 5 Trading system status Status of the trading system on which the instrument is traded. ‘ACTV’ – Active System ‘OTAG’ – Outage of the trading system ‘POTG’ – Partial outage of the trading system Both Table 4 Regulatory data for shares and ETFs, per instrument # Field identifier Description Format Equivalent formats can be used, depending on the syntax used for data transmission Input/Output data field 1 Instrument identification code Code used to identify the financial instrument. {ISIN} Both 2 Instrument status start date and time Date and time from which the instrument status is valid. The level of granularity shall be in accordance with the requirements set out in Article 12. {DATE_TIME_FORMAT} Both 3 Currency Major currency in which the instrument trades. {CURRENCYCODE_3} Both 4 Dissemination date and time Date and time on which the regulatory data is disseminated by the CTP. The level of granularity shall be in accordance with the requirements set out in Article 15. {DATE_TIME_FORMAT} Output 5 Instrument status Description of the status of the financial instrument. The status of the financial instrument shall be one of the following: (1) suspended from trading, on the trading venue identified in the field ‘Trading venue’, in accordance with Articles 32 and 52 of Directive 2014/65/EU; (2) removed from trading, on the trading venue identified in the field ‘Trading venue’, in accordance with Articles 32 and 52 of Directive 2014/65/EU; (3) subject to a trading halt, on the trading venue identified in the field ‘Trading venue’, in accordance with Articles 18(5) and 48(5) of Directive 2014/65/EU; (4) available for trading after a suspension, removal or halt. ‘SUSP’ – the instrument is suspended ‘RMOV’ – the instrument is removed ‘HALT’ – the instrument is subject to a trading halt ‘ACTV ’ – the instrument is available for trading after a suspension, removal or halt Both 6 Trading venue Identification of the trading venue on which the instrument status is valid (segment MIC where available, otherwise operating MIC). The trading venue is a regulated market or an MTF. {MIC} Both 7 Trading system Type of trading system on which the instrument is traded. ‘CLOB’ – Central Limit Order Book ‘QDTS’ – Quote Driven Market ‘PATS’ – Periodic Auction ‘RFQT’ – Request for Quotes ‘HYBR’ – Hybrid System ‘OTHR’ – Other Both 8 Trading system phase Type of trading phase of the trading system on which the instrument is traded. ‘UDUC’ – Undefined Auction ‘SOAU’ – Scheduled Opening Auction ‘SCAU’ – Scheduled Closing Auction ‘SIAU’ – Scheduled Intraday Auction ‘UAUC’ – Unscheduled Auction ‘ODAU’ – On Demand Auction (Frequent Batch Auction) ‘COTR’ – Continuous Trading ‘MACT’ – At Market Close Trading ‘OMST’– Out of Main Session Trading ‘TROE’ – Trade Reporting (On Exchange) ‘TROF’ – Trade Reporting (Off Exchange) ‘TRSI’ – Trade Reporting (Systematic Internaliser) ‘OTSP’ – Other Both 9 Most Relevant Market in terms of liquidity Whether the trading venue in Field 6 is the most relevant market in terms of liquidity. TRUE – Yes FALSE – No Output Table 5 Regulatory data for shares and ETFs, per order matching system # Field identifier Description Format Equivalent formats can be used, depending on the syntax used for data transmission Input/Output data field 1 Trading venue Identification of the trading venue on which the order matching system status is valid (segment MIC where available, otherwise operating MIC). The trading venue is a regulated market or an MTF. {MIC} Both 2 Trading system Type of trading system on which the system status is provided. ‘CLOB’ – Central Limit Order Book ‘QDTS’ – Quote Driven Market ‘PATS’ – Periodic Auction ‘RFQT’ – Request for Quotes ‘HYBR’ – Hybrid System ‘OTHR’ – Other Both 3 System status start date and time Date and time from which the system status is valid. The level of granularity shall be in accordance with the requirements set out in Article 12. {DATE_TIME_FORMAT} Both 4 System status dissemination date and time Date and time on which the system status is disseminated by the CTP. The level of granularity shall be in accordance with the requirements set out in Article 15. {DATE_TIME_FORMAT} Output 5 Trading system status Status of the trading system. ‘ACTV’ – Active System ‘OTAG’ – Outage of the trading system ‘POTG’ – Partial outage of the trading system Both Table 6 Post-trade core market data for bonds # Field identifier Description and details to be published Type of execution or publication venue Format to be populated as defined in Table 1 Equivalent formats can be used, depending on the syntax used for data transmission Input/Output data field 1 Trading date and time Table 2, Field 1, of Annex II to Delegated Regulation (EU) 2017/583. Both 2 Instrument identification code Table 2, Field 2, of Annex II to Delegated Regulation (EU) 2017/583. Both 3 Price Table 2, Field 3, of Annex II to Delegated Regulation (EU) 2017/583. Both 4 Missing Price Table 2, Field 4, of Annex II to Delegated Regulation (EU) 2017/583. Both 5 Price currency Table 2, Field 5, of Annex II to Delegated Regulation (EU) 2017/583. Both 6 Price notation Table 2, Field 6, of Annex II to Delegated Regulation (EU) 2017/583. Both 7 Notional amount Table 2, Field 10, of Annex II to Delegated Regulation (EU) 2017/583. Both 8 Notional currency Table 2, Field 11, of Annex II to Delegated Regulation (EU) 2017/583. Both 9 Venue of execution Table 2, Field 13, of Annex II to Delegated Regulation (EU) 2017/583. Both 10 Third-country trading venue of execution Table 2, Field 14, of Annex II to Delegated Regulation (EU) 2017/583. Both 11 Date and Time when the data contributor received the data Date and time when the transaction report was received by an APA. The level of granularity shall be in accordance with the requirements set out in Article 15. APA {DATE_TIME_ FORMAT} Input 12 Date and Time when the data contributor published the transaction Table 2, Field 15, of Annex II to Delegated Regulation (EU) 2017/583. Both 13 Venue of publication Table 2, Field 16, of Annex II to Delegated Regulation (EU) 2017/583. Both 14 Transaction Identification Code Table 2, Field 17, of Annex II to Delegated Regulation (EU) 2017/583. Both 15 Date and Time of reception by the CTP Date and time when the transaction was received by the CTP. The level of granularity shall be in accordance with the requirements set out in Article 15. CTP {DATE_TIME_ FORMAT} Output 16 Date and Time of publication by the CTP Date and time when the transaction was published by the CTP. The level of granularity shall be in accordance with the requirements set out in Article 15. CTP {DATE_TIME_ FORMAT} Output 17 Flags Table 2, Field 19, of Annex II to Delegated Regulation (EU) 2017/583. Both 18 Suspicious Data Flag Data quality flag to be populated by the CTP when the APA or the CTP have identified trades that, in their view, might be subject to data quality issues. CTP TRUE or FALSE Output 19 Trading System Type Table 2, Field 20, of Annex II to Delegated Regulation (EU) 2017/583. Both 20 Number of transactions Table 2, Field 21, of Annex II to Delegated Regulation (EU) 2017/583. Both Table 7 Post-trade core market data for shares and ETFs # Field identifier Description and details to be published Type of execution or publication venue Format to be populated as defined in Table 1 Equivalent formats can be used, depending on the syntax used for data transmission Input/ Output data field 1 Trading date and time Table 3, Field 1, of Annex I to Delegated Regulation (EU) 2017/587. Both 2 Instrument identification code Table 3, Field 2, of Annex I to Delegated Regulation (EU) 2017/587. Both 3 Price Table 3, Field 3, of Annex I to Delegated Regulation (EU) 2017/587. Both 4 Missing Price Table 3, Field 4, of Annex I to Delegated Regulation (EU) 2017/587. Both 5 Price currency Table 3, Field 5, of Annex I to Delegated Regulation (EU) 2017/587. Both 6 Quantity Table 3, Field 7, of Annex I to Delegated Regulation (EU) 2017/587. Both 7 Venue of execution Table 3, Field 8, of Annex I to Delegated Regulation (EU) 2017/587. Both 8 Third-country trading venue of execution Table 3, Field 9, of Annex I to Delegated Regulation (EU) 2017/587. Both 9 Date and Time when the data contributor received the data Date and time when the transaction report was received by an APA. The level of granularity shall be in accordance with the requirements set out in Article 15. APA {DATE_TIME_ FORMAT} Input 10 Trading system Table 3, Field 10, of Annex I to Delegated Regulation (EU) 2017/587. Both 11 Date and Time when the data contributor published the transaction Table 3, Field 11, of Annex I to Delegated Regulation (EU) 2017/587. Both 12 Venue of Publication Table 3, Field 12, of Annex I to Delegated Regulation (EU) 2017/587. Both 13 Transaction identification code Table 3, Field 13, of Annex I to Delegated Regulation (EU) 2017/587. Both 14 Date and Time of reception by the CTP Date and time when the transaction was received by the CTP. The level of granularity shall be in accordance with the requirements set out in Article 15. CTP {DATE_TIME_ FORMAT} Output 15 Date and Time of publication by the CTP Date and time when the transaction was published by the CTP. The level of granularity shall be in accordance with the requirements set out in Article 15. CTP {DATE_TIME_ FORMAT} Output 16 Flags This field shall be populated with the list of all applicable flags set out in Table 4 of Annex I to Delegated Regulation (EU) 2017/587. Where none of the specified circumstances apply, the transaction shall be published without a flag. RM, MTF, APA As per Table 4 of Annex I to Delegated Regulation (EU) 2017/587 Both 17 Suspicious Data Flag Data quality flag to be populated by the CTP when the APA or the CTP have identified trades that, in their view, might be subject to data quality issues. CTP TRUE or FALSE Output
ANNEX III Pre-trade data to be transmitted to and disseminated by the CTP for shares and ETFs according to Articles 6 and 8 Table 1 Symbols used in Tables 2, 3 and 4 Symbol Data Type Definition {DATE_TIME_FORMAT} ISO 8601 date and time format Date and time in the following format: YYYY-MM-DDThh:mm:ss.ddddddZ. — ‘YYYY’ is the year; — ‘MM’ is the month; — ‘DD’ is the day; — ‘T’ – means that the letter ‘T’ shall be used — ‘hh’ is the hour; — ‘mm’ is the minute; — ‘ss.dddddd’ is the second and its fraction of a second; — ‘Z’ is UTC time. Dates and times shall be reported in UTC. {ISIN} 12 alphanumerical characters ISIN code, as defined in ISO 6166 {MIC} 4 alphanumerical characters Market identifier as defined in ISO 10383 {DECIMAL-n/m} Decimal number of up to n digits in total of which up to m digits can be fraction digits Numerical field for both positive and negative values. — decimal separator is ‘.’ (full stop); — negative numbers are prefixed with ‘–’ (minus); Where applicable, values shall be rounded and not truncated. {CURRENCYCODE_3} 3 alphanumerical characters 3-letter currency code, as defined by ISO 4217 currency codes Table 2 Pre-trade data to be transmitted to the CTP for shares and ETFs # Field identifier Description and details to be published Format to be populated as defined in Table 1 Equivalent formats may be used, depending on the syntax used for data transmission 1 Update date and time For continuous order book trading systems, Table 1b, Field 1, of Annex I to Delegated Regulation (EU) 2017/587. For periodic auction trading systems, Table 1b, Field 1, of Annex I to Delegated Regulation (EU) 2017/587. For auction trading systems, the date and time at which the price would best satisfy the trading algorithm and any modification of the price (Field 4) or quantity (Field 6) thereafter. The level of granularity shall be in accordance with the requirements set out in Article 12. 2 Instrument identification code Table 1b, Field 2, of Annex I to Delegated Regulation (EU) 2017/587. 3 Side Table 1b, Field 3, of Annex I to Delegated Regulation (EU) 2017/587. This field is mandatory only for continuous order book trading systems. 4 Price For continuous order book trading systems, Table 1b, Field 5, of Annex I to Delegated Regulation (EU) 2017/587 of the best bid and offer. For periodic auction trading systems, Table 1b, Field 5, of Annex I to Delegated Regulation (EU) 2017/587. For auction trading systems, the price at which the auction trading system would best satisfy its trading algorithm. The price shall be provided in the major currency unit. Where price is currently not available but pending (‘PNDG’) or not applicable (‘NOAP’), this field shall not be populated. 5 Price currency Table 1b, Field 6, of Annex I to Delegated Regulation (EU) 2017/587. 6 Quantity For continuous order book trading systems, Table 1b, Field 8, of Annex I to Delegated Regulation (EU) 2017/587. For periodic auction trading systems, Table 1b, Field 8, of Annex I to Delegated Regulation (EU) 2017/587. For auction trading systems the aggregated quantity attached to the price that would best satisfying the trading algorithm. 7 Venue Table 1b, Field 11, of Annex I to Delegated Regulation (EU) 2017/587. 8 Trading system Table 1b, Field 12, of Annex I to Delegated Regulation (EU) 2017/587. This field shall be populated for central limit order book trading systems and periodic auction trading systems. 9 Trading system phase Table 1b, Field 13, of Annex I to Delegated Regulation (EU) 2017/587. 10 Publication date and time Table 1b, Field 14, of Annex I to Delegated Regulation (EU) 2017/587. Table 3 Pre-trade core market data to be disseminated by the CTP for shares and ETFs – EBBO # Field identifier Description Format as defined in Table 1 Equivalent formats can be used, depending on the syntax used for data transmission 1 Entry date and time Table 2, Field 1, of Annex III to this Regulation applied to the best bids and offers entered into the order book, as reported by the trading venue. The CTP shall publish the most recent amongst the dates and times of the best bids and offers entered into the order book that participate in the EBBO as reported by the data contributors. {DATE_TIME_FORMAT} 2 Instrument identification code Table 2, Field 2, of Annex III to this Regulation. {ISIN} 3 Currency Major currency unit in which the European best bid and offer prices are expressed. This corresponds to Table 2, Field 5, of Annex III to this Regulation. {CURRENCYCODE_3} 4 Best bid European best bid in continuous order books. This corresponds to Table 2, Field 4, of Annex III to this Regulation. {DECIMAL-18/13} 5 Best bid volume The aggregated volume attached to the European best bid. This corresponds to Table 2, Field 6, of Annex III to this Regulation. {DECIMAL-18/17} 6 EBBO timestamp Date and time of the calculation of the EBBO. The level of granularity shall be in accordance with the requirements set out in Article 12. {DATE_TIME_FORMAT} 7 Most Relevant Market in terms of liquidity Most relevant market in terms of liquidity as laid down in Article 4 of Delegated Regulation (EU) 2017/587. {MIC} 8 Best offer European best offer in continuous order books. This corresponds to Table 2, Field 4, of Annex III to this Regulation. {DECIMAL-18/13} 9 Best offer volume The aggregated volume attached to the European best offer. This corresponds to Table 2, Field 6, of Annex III to this Regulation. {DECIMAL-18/17} 10 Dissemination date and time Date and time when the data related to the order was disseminated by the CTP. The level of granularity shall be in accordance with the requirements set out in Article 15. {DATE_TIME_FORMAT} 11 Publication date and time Table 2, Field 10, of Annex III to this Regulation. {DATE_TIME_FORMAT} Table 4 Pre-trade core market data to be disseminated by the CTP for shares and ETFs – indicative auction price (except when trading phase is set to ‘ODAU’) # Field identifier Description Format as defined in Table 1 Equivalent formats can be used, depending on the syntax used for data transmission 1 Indicative date and time Table 2, Field 1, of Annex III to this Regulation. The CTP shall publish the most recent amongst the dates and times of the prices that participate in the CTP’s indicative auction price as reported by the data contributors. {DATE_TIME_FORMAT} 2 Instrument identification code Table 2, Field 2, of Annex III to this Regulation. {ISIN} 3a Lowest auction price Table 2, Field 4, of Annex III to this Regulation applied to the lowest auction price. {DECIMAL-18/17} 3b Highest auction price Table 2, Field 4, of Annex III to this Regulation applied to the highest auction price. {DECIMAL-18/17} 3c Volume weighted auction price Volume weighted auction price. This field corresponds to Table 2, Field 4, of Annex III to this Regulation weighted by Table 2, Field 6, of Annex III to this Regulation. {DECIMAL-18/17} 4 Currency Major currency unit in which the auction price is expressed. This field corresponds to Table 2, Field 5, of Annex III to this Regulation. {CURRENCYCODE_3} 5 Auction volume Total auction volume, where applicable, across venues. This corresponds to Table 2, Field 6, of Annex III to this Regulation. {DECIMAL-18/13} 6 Dissemination date and time Date and time when the data related to the indicative auction price and size was disseminated by the CTP to the subscribers. The level of granularity shall be in accordance with the requirements set out in Article 15. {DATE_TIME_FORMAT} 7 Publication date and time Table 2, Field 10, of Annex III to this Regulation. {DATE_TIME_FORMAT} 8 Most Relevant Market in terms of liquidity Most relevant market in terms of liquidity as laid down in Article 4 of Delegated Regulation (EU) 2017/587. {MIC} Table 5 Pre-trade core market data to be disseminated by the CTP for shares and ETFs – indicative auction price when trading phase is set to ‘ODAU’ # Field identifier Description Format as defined in Table 1 Equivalent formats can be used, depending on the syntax used for data transmission 1 Indicative date and time Table 2, Field 1, of Annex III to this Regulation. The CTP shall publish the most recent amongst the dates and times of the prices that participate in the CTP’s indicative auction price as reported by the data contributors. {DATE_TIME_FORMAT} 2 Instrument identification code Table 2, Field 2, of Annex III to this Regulation. {ISIN} 3a Lowest auction price Table 2, Field 4, of Annex III to this Regulation applied to the lowest auction price. {DECIMAL-18/17} 3b Highest auction price Table 2, Field 4, of Annex III to this Regulation applied to the highest auction price. {DECIMAL-18/17} 3c Volume weighted auction price Volume weighted auction price. This field corresponds to Table 2, Field 4, of Annex III to this Regulation weighted by Table 2, Field 6, of Annex III to this Regulation. {DECIMAL-18/17} 4 Currency Major currency unit in which the auction price is expressed. This field corresponds to Table 2, Field 5, of Annex III to this Regulation. {CURRENCYCODE_3} 5 Auction volume Total auction volume, where applicable, across venues. This corresponds to Table 2, Field 6, of Annex III to this Regulation. {DECIMAL-18/13} 6 Dissemination date and time Date and time when the data related to the indicative auction price and size was disseminated by the CTP to the subscribers. The level of granularity shall be in accordance with the requirements set out in Article 15. {DATE_TIME_FORMAT} 7 Publication date and time Table 2, Field 10, of Annex III to this Regulation. {DATE_TIME_FORMAT} 8 Most Relevant Market in terms of liquidity Most relevant market in terms of liquidity as laid down in Article 4 of Delegated Regulation (EU) 2017/587. {MIC}
ANNEX IV Level of accuracy of business clocks Table 1 Level of accuracy for operators of trading venues and systematic internalisers Gateway-to-gateway latency time of the trading system Maximum divergence from UTC Granularity of the timestamp > 1 millisecond 1 millisecond 1 millisecond or better ≤ 1 millisecond 100 microseconds Increase granularity to 0,1 microseconds or better Table 2 Level of accuracy for members, participants or users of a trading venue Type of trading activity Description Maximum divergence from UTC Granularity of the timestamp Activity using high frequency algorithmic trading technique High frequency algorithmic trading technique. 100 microseconds 0,1 microseconds or better Activity on voice trading systems Voice trading systems as defined in Table 2 of Annex II to Delegated Regulation (EU) 2017/583. 1 second 1 second or better Activity on request for quote systems where the response requires human intervention or where the system does not allow algorithmic trading Request for quotes systems as defined in Table 2 of Annex II to Delegated Regulation (EU) 2017/583. 1 second 1 second or better Activity of concluding negotiated transactions Negotiated transaction as set out in Article 4(1)(b) of Regulation (EU) No 600/2014. 1 second 1 second or better
ANNEX V Correlation table referred to in Article 25 Delegated Regulation (EU) 2017/574 Delegated Regulation (EU) 2025/1155 Article 1 Article 11 Article 2 Article 12 Article 3 Article 13 Article 14 Article 15 Article 4 Article 16 Article 5 Annex Annex IV
Source: EUR-Lex (Publications Office of the EU), © European Union, reuse permitted under Commission Decision 2011/833/EU.