The Committee on Payments and Market Infrastructures (CPMI) and the International Organization of Securities Commissions (IOSCO) today published the Framework for supervisory stress testing of central counterparties (CCPs). The framework provides authorities with guidance to support their design and implementation of supervisory stress tests for CCPs.
In April 2015, the G20 finance ministers and central bank Governors asked the Financial Stability Board to work with the CPMI, IOSCO and the Basel Committee on Banking Supervision to develop a workplan for identifying and addressing gaps and potential financial stability risks relating to CCPs that are systemic across multiple jurisdictions and for enhancing their resolvability (the joint CCP workplan).
Since then, the committees have published guidance to enhance CCPs’ resilience, recovery and resolvability. The report published today addresses another key aspect of the joint CCP workplan. The CCP supervisory stress testing framework is designed to support tests conducted by one or more authorities that examine the potential macro-level impact of a common stress event affecting multiple CCPs.
Among other things, such supervisory stress tests could help authorities better understand the scope and magnitude of the interdependencies between markets, CCPs and other entities such as participants, liquidity providers and custodians. This type of supervisory stress test is different from, yet may complement, other stress testing activities conducted by authorities seeking to evaluate the resilience of individual CCPs.
In June 2017, the CPMI and IOSCO published the Consultative report: Framework for supervisory stress testing of central counterparties (CCPs). During the consultation period, they held an industry workshop with representatives from
various market sectors and authorities from different jurisdictions. The comments received emphasised the importance of:
- Seeking feedback from different stakeholders on the design and operational aspects of a supervisory stress test;
- Managing the resource burden associated with these tests;
- Protecting data;
- Promoting the transparency of test methodology and results as much as possible