Skip to main content
  • I. Contractual Maturity Mismatch

    • A. Objective

      177. The contractual maturity mismatch profile identifies the gaps between the contractual inflows and outflows of liquidity for defined time bands. These maturity gaps indicate how much liquidity a bank would potentially need to raise in each of these time bands if all outflows occurred at the earliest possible date. This metric provides insight into the extent to which the bank relies on maturity transformation under its current contracts.
       
    • B. Definition and Practical Application of the Metric

      Contractual cash and security inflows and outflows from all on- and off-balance sheet items, mapped to defined time bands based on their respective maturities.
       
      178. A bank should report contractual cash and security flows in the relevant time bands based on their residual contractual maturity. Supervisors in each jurisdiction will determine the specific template, including required time bands, by which data must be reported. Supervisors should define the time buckets so as to be able to understand the bank’s cash flow position. Possibilities include requesting the cash flow mismatch to be constructed for the overnight, 7 day, 14 day, 1, 2, 3, 6 and 9 months, 1, 2, 3, 5 and beyond 5 years buckets. Instruments that have no specific maturity (non-defined or open maturity) should be reported separately, with details on the instruments, and with no assumptions applied as to when maturity occurs. Information on possible cash flows arising from derivatives such as interest rate swaps and options should also be included to the extent that their contractual maturities are relevant to the understanding of the cash flows.
       
      179. At a minimum, the data collected from the contractual maturity mismatch should provide data on the categories outlined in the LCR. Some additional accounting (non-dated) information such as capital or non-performing loans may need to be reported separately.
       
      • 1. Contractual Cashflow Assumptions

        180. No rollover of existing liabilities is assumed to take place. For assets, the bank is assumed not to enter into any new contracts.
         
        181. Contingent liability exposures that would require a change in the state of the world (such as contracts with triggers based on a change in prices of financial instruments or a downgrade in the bank's credit rating) need to be detailed, grouped by what would trigger the liability, with the respective exposures clearly identified.
         
        182. A bank should record all securities flows. This will allow supervisors to monitor securities movements that mirror corresponding cash flows as well as the contractual maturity of collateral swaps and any uncollateralised stock lending/borrowing where stock movements occur without any corresponding cash flows.
         
        183. A bank should report separately the customer collateral received that the bank is permitted to rehypothecate as well as the amount of such collateral that is rehypothecated at each reporting date. This also will highlight instances when the bank is generating mismatches in the borrowing and lending of customer collateral.
         
    • C. Utilisation of the Metric

      184. Banks will provide the raw data to the supervisors, with no assumptions included in the data. Standardised contractual data submission by banks enables supervisors to build a market-wide view and identify market outliers vis-à-vis liquidity.
       
      185. Given that the metric is based solely on contractual maturities with no behavioural assumptions, the data will not reflect actual future forecasted flows under the current, or future, strategy or plans, ie, under a going-concern view. Also, contractual maturity mismatches do not capture outflows that a bank may make in order to protect its franchise, even where contractually there is no obligation to do so. For analysis, supervisors can apply their own assumptions to reflect alternative behavioural responses in reviewing maturity gaps.
       
      186. As outlined in the Sound Principles, banks should also conduct their own maturity mismatch analyses, based on going-concern behavioural assumptions of the inflows and outflows of funds in both normal situations and under stress. These analyses should be based on strategic and business plans and should be shared and discussed with supervisors, and the data provided in the contractual maturity mismatch should be utilised as a basis of comparison. When firms are contemplating material changes to their business models, it is crucial for supervisors to request projected mismatch reports as part of an assessment of impact of such changes to prudential supervision. Examples of such changes include potential major acquisitions or mergers or the launch of new products that have not yet been contractually entered into. In assessing such data supervisors need to be mindful of assumptions underpinning the projected mismatches and whether they are prudent.
       
      187. A bank should be able to indicate how it plans to bridge any identified gaps in its internally generated maturity mismatches and explain why the assumptions applied differ from the contractual terms. The supervisor should challenge these explanations and assess the feasibility of the bank’s funding plans.