Post

Financial News: On the Admission of Securities to REPO Transactions with the Central Counterparty from May 29, 2026

Financial News: On the Admission of Securities to REPO Transactions with the Central Counterparty from May 29, 2026

Published on: 2026-05-28

Source: Moscow Exchange –

An important disclaimer is at the bottom of this article.

To the participants of the trading

We inform you that, in accordance with Part I. General part of the Rules for conducting trades on the stock market, deposit market and credit market of PJSC “Moscow Exchange MICEX-RTS”, approved by the decision of the Supervisory Board on January 23, 2026 (Protocol No. 11), it has been established that from May 29, 2026, Table 1-O (Only REPO transactions) “Trading modes available for bonds and CSS with transactions concluded in the Stock Market Section and REPO Market Section” of the Appendix to the Additional terms for conducting trades on the stock market, approved by Order No. MB-P-2026-954 dated 16.03.2026 (with amendments and additions) and Order No. MB-P-2026-1010 dated 18.03.2026, will apply.(with changes and additions), will be supplemented with the following content lines:

Trade code Name Registration number Conducting trades Features
“REP with ЦК – Targeted Applications” “REPORT with TSCH – Without
“targeted applications”
“Interdealer
REPOST
Permissible calculation codes for individual trading modes
T0/Yn*,Y0/Yn*,Y1/Yn*,Y2/Yn* Y0/Y1, Y0/Y1W S0-S2, Rb, Z0
1 RU000A1081E2 Corporate Bond Bank VTB (PJSC) 6-994-01000-B-001P from 14.03.2024 RUB, CNY, KZT, BYN RUB, CNY 1; NCD is not counted; Allowed are calculation codes that provide for the REPO transaction period up to 1 trading day

* The value of “n” is defined as follows:https://fs.moex.com/files/20211
1 – No trading is conducted on the bond maturity date.

Contact information for the media
+7 (495) 363-3232
PR@moex.com

Please note; this information is raw content obtained directly from the information source. It represents an accurate report of what the source claims, and does not necessarily reflect the position of MIL-OSI or its clients.