RTS · European Commission
Commission Delegated Regulation (EU) 2017/590 of 28 July 2016 supplementing Regulation (EU) No 600/2014 of the European Parliament and of the Council with regard to regulatory technical standards for the reporting of transactions to competent authorities
RTS 22 on transaction reporting under Article 26 MiFIR: defines a reportable transaction and its execution, the conditions for transmitting orders instead of reporting, identification of firms, clients, decision makers and the persons or algorithms responsible for investment and execution decisions, flags for waivers and short sales, branch reporting and the most relevant market in terms of liquidity, with the reporting fields in its annex.
Details
| Reference | Delegated Regulation (EU) 2017/590 |
|---|---|
| Issuer | European Commission |
| Published | 31 Mar 2017 |
| CELEX | 32017R0590 |
| In force / applies from | 20 Apr 2017, 3 Jan 2018 |
Provisions it relates to
- Article 26 MiFIR · Obligation to report transactionsLegal basis
UK version: UK Delegated Regulation (EU) 2017/590.
Documents that refer to it
- Q&AAnsweredExplicit reference · 90%
AI summaryA complex trade under Article 12 of RTS 22 is a single transaction in several instruments at one price, even if the components also trade separately; ESMA explains how to report each leg (including TVTIC), mixed reportable and non-reportable components, and the reference data for strategies and their components.
- Q&AAnsweredExplicit reference · 90%
AI summaryESMA provides a table of the national client identifiers for natural persons to use in transaction reports, by country and in the priority order of Annex II of RTS 22, with CONCAT generated as set out in Article 6 of RTS 22.
- Q&AAnsweredExplicit reference · 90%
AI summaryA firm using another investment firm's execution algorithm reports as if it had sent the order to that firm, entering in field 59 of RTS 22 only its own person or algorithm responsible; this is the same if the algorithm provider is not a MiFID firm, and an algorithm provider that uses the first firm's membership is itself executing and must report.
- Q&AAnsweredExplicit reference · 90%
AI summaryRisk-free rates missing from the RTS 23 and RTS 22 code lists should be reported with their ISO 20022 four-letter code (for example 'ESTR' for €STR) and, where one exists, the rate's ISIN; ESMA also covers other unlisted reference rates, whether voluntary switches to risk-free rates are reportable transactions, and new ISINs for instruments with fallback rates.
- Q&AAnsweredExplicit reference
AI summaryAccumulators are reported as forwards or options, depending on any option features; the individual settlement trades are not reported but hedging trades with third parties are, and ESMA sets out how each RTS 22 field should be completed for the accumulator itself.
- Q&AAnsweredExplicit reference
AI summaryStateless natural persons should be identified in transaction reports with the country code 'ZZ' followed by a CONCAT code built under Article 6(4) of RTS 22.
- Q&AAnsweredExplicit reference · 90%
AI summaryESMA gives a worked RTS 22 example for an inflation-indexed bond, reporting the quantity as nominal value, the price as a percentage and the net amount as clean price plus accrued interest, multiplied by the index ratio.
- Q&AAnsweredExplicit reference
AI summaryA transaction in a convertible bond, reverse convertible bond or reverse convertible note is reportable under Article 26(2)(b) MiFIR where the instrument it converts into is traded on a trading venue, with that instrument reported as the underlying in field 47 of RTS 22; if the bond is itself in scope under Article 26(2)(a), only its own ISIN is reported.
FCA Handbook
Handbook provisions whose source note cites it:
FCA Handbook references © FCA, used under the Open Government Licence v3.0. Rulestack is independent and not endorsed by the FCA.