- Question ID
-
2022_6330
- Legal act
- Regulation (EU) No 575/2013 (CRR)
- Topic
- Liquidity risk
- Article
-
460
- COM Delegated or Implementing Acts/RTS/ITS/GLs/Recommendations
- Delegated Regulation (EU) 2015/61 - DR with regard to liquidity coverage requirement
- Article/Paragraph
-
32(3)(f)
- Name of institution / submitter
-
International Cpaital Market Association
- Country of incorporation / residence
-
Switzerland
- Type of submitter
-
Industry association
- Subject matter
-
Reuse of collateral in a repo transaction with collateral substitution rights
- Question
-
Can a bank record an inflow for a reverse repo with a residual maturity of up to 30 days under the LCR, where collateral is being funded in a repo with a residual maturity of more than 30 days, where collateral is allocated on an automated basis and managed by a third party (ie triparty repo), and where the repo has automatic rights of substitution for collateral of the same or better HQLA classification?
- Background on the question
-
Base FAQ 27 -d406 (now Basel CF LCR40.79) Paragraph 146 states that there is an inflow rate of 0% when collateral received through a secured lending transaction is reused to cover a short position, including matched repo books where the collateral reuse transaction has a longer maturity than the secured lending transaction. This rule reflects the risk that it may not be possible to roll-over the shorter-term transaction at maturity in order to continue borrowing the collateral reused in the longer-term transaction.
The rule overlooks the fact that, in the case of a triparty allocation, the triparty agent would automatically substitute the collateral being reused in the longer-term transaction were it no longer available to the party reusing it (because the short-term transaction supplying the collateral had not been rolled over). This substitution involves no action by either counterparty to the triparty transaction. Furthermore, triparty allocation logic cannot distinguish between long-term and short-term sources or uses, so inadvertently creates inflow reuse (such reuse can be prevented where collateral can be directed bilaterally). Any such reuse is automatically resolved by the triparty agent upon the unwind of short-dated transactions.
Take, for example, a scenario whereby a counterparty enters into a one-week reverse repo (say in ISIN A) and a three-month reverse repo (ISIN B). They also enter into a one-week triparty repo and a three-month triparty repo, where the eligible collateral is allocated automatically by a third party and is continuously substitutable. In the case that both ISIN A and B are eligible under the triparty transactions, it is equally possible that either ISIN A or B, or a combination of both, could be allocated to either triparty repo. In the case that ISIN A (the shorter-term reversed collateral) is allocated under the three-month triparty repo, CF LCR40.79 would measure the three-month repo as a zero inflow for the purpose of LCR. This is despite the fact that at the end of the one-week reverse transaction in ISIN A (when it is no longer available for allocation in any triparty repo), it will automatically be substituted with ISIN B or another available, eligible ISIN. This highlights the seamless fungibility of ISINs A and B in this scenario.
It could be argued that if in this scenario the counterparty ensured that ISIN A was allocated under the shorter-term triparty repo and ISIN B under the longer-term triparty repo, then CF LCR40.79 would record an LCR inflow for the longer-term reverse. However, it is important to recognize that in the case of triparty, specific collateral positions cannot be directed to a specific term-matched use because triparty allocations are solely based on an instrument’s eligibility to a given basket. All collateral positions held at triparty are fully fungible and allocated based solely on their eligibility and availability at a point in time. They may be substituted in a later cycle with another available eligible position if they need to be withdrawn from triparty to satisfy a bilateral delivery obligation. The sole constraint is on availability of eligible collateral, not on the availability of any specific instrument.
Hence CF LCR40.79 potentially overlooks the inherent fungibility of collateral in the case of triparty funding transactions.
- Submission date
- Rejected publishing date
-
- Rationale for rejection
-
This question has been rejected because it is considered that EBA guidance or clarification is not needed with regard to the issue that it raises. For example, this can be the case where it is considered that the existing regulatory framework is sufficiently clear and unambiguous, or where different practices may be possible but it is not currently necessary to harmonise these further through the Q&A process.
The Single Rule Book Q&A tool has been established to provide explanations and non-binding interpretations on questions relating to the practical application or implementation of the provisions of legislative acts referred to in Article 1(2) of the EBA’s founding Regulation, as well as associated delegated and implementing acts, and guidelines and recommendations, adopted under these legislative acts.
For further information on the purpose of this tool and on how to submit questions, please see “Additional background and guidance for asking questions”.
- Status
-
Rejected question