Acknowledging The Elephant in The Room: The Mismatch Centre
Acknowledging The Elephant in The Room: The Mismatch Centre
risk.net
sections
Events Awards White papers Analytics Hub Futures & Options Hub Webinars Subscribe Follow us My account
Search risk.net
Mismatch Centre
David Green
Regardless of the risk profile, the magnitude (and possibly even the
direction) of the exposure to changes in interest rates and liquidity
costs is inherently unstable. The make-up of the balance sheet and
customer behaviours are constantly changing, or management might,
from time to time, deliberately manipulate the risk profile. For this
reason, IRR and LR, and the earnings related to these risks, must be
constantly monitored if the understanding of risk and profitability is to
be correct.
We now compare the earnings risk profile of a bank with no IRR (bank
earnings, πBank, do not vary across rate scenarios) with two banks that
have IRR: the first is liability-sensitive, and the second is asset-
sensitive; these are shown in Figure 15.2. Next we analyse business
unit earnings dynamics for each of these banks with and without the
benefit of FTP.12
where πLoans and πDeposits represent the earnings in the lending and
deposit-gathering business units respectively.
∂πBank
=?, (15.2)
∂r
∂πBank
=?, (15.3)
∂l
where l represents liquidity spreads for the bank. Within the context of
FTP, liquidity spreads represent the credit risk of the FI as measured
by the difference between the cost of issuing senior unsecured debt
and an interest rate swap rate with a corresponding term.
Equations 15.4 and 15.5 make very important points: if a bank has IRR
or LR, then one or more of the business units must have IRR or LR.
Put differently, IRR and LR are not just bank-level problems, they are
business unit-level problems as well. These risks make granular
earnings management particularly problematic as individual business
units within the bank do not generally have a mandate to take or
manage IRR or LR,14 much less the ability to even quantify these
risks. The existence of these risks also means that the analysis and
reconciliation of business unit earnings in any budgeting and
forecasting exercises will be complicated by differences between
forecasted and realised interest rates and liquidity spreads. In volatile
economic environments, these rate and liquidity spread differences
can be material; regardless of their magnitude, such rate and liquidity
spread driven differences must be accurately quantified, else the
attribution of earnings and earnings variances will necessarily be
incorrect.15 However, finance and the business units need not throw
their hands up in frustration, as this is a problem can be solved; in fact,
this is exactly the problem FTP is intended to solve.
∂πBUi
= 0, (15.6)
∂r
The introduction of FTP will not add to or subtract from the overall level
of earnings of the bank, but it will almost certainly change the
allocation of earnings to the lending and deposit-gathering business
units.17 Relative to the allocation where there was no mismatch centre
(Equation 15.1), for a given level of πBank, if πMM is positive then either
or both of πLoans and πDeposits will necessarily be lower – ie, there will
be a net transfer of earnings out of the lending and deposit-gathering
business units. Similarly, if πMM is negative then either or both of
πLoans and πDeposits will necessarily be higher – ie, there will be a net
transfer of earnings into the lending and deposit-gathering business
units.
The arrows indicate the direction of risk transfer. Eliminating the terms
that have a zero value, we get the following:
∂πBank ∂π
= MM , and (15.12)
∂r ∂r
∂πBank ∂π
= MM . (15.13)
∂l ∂l
If FTP is being used in any way such that Equations 15.12 and 15.13
do not hold, the lending and deposit-gathering business units will not
be immunised from IRR and LR.
Let’s return to the bank earnings risk profiles that were introduced
earlier and consider the earnings risk profiles of the business units and
the mismatch centre across rate scenarios.
Now let’s see what the allocation of earnings looks like in banks that
have non-zero IRR. This will begin to help us answer a very important
question: “What is the correct level of earnings in the mismatch
centre?”.
Note the two dotted brackets in Figure 15.4. The increase in bank
earnings in the BaseCase scenario (upper dotted bracket) resulting
from the shift to a liability-sensitive position is the same as the
increase in mismatch centre earnings (lower dotted bracket): the
increase in bank earnings associated with the change in the IRR
profile of the bank accrues entirely to the mismatch centre. This must
be the case if aggregate business unit earnings are to be unchanged
relative to the IRR-free bank. Business unit immunisation will also only
hold across all rate scenarios if the bank earnings risk profile and the
mismatch centre earnings risk profile have the same slope – ie, the
two earnings risk profiles are parallel. This is exactly what Equation
15.12 says and what is shown in Figure 15.4; all the brackets between
the two earnings profiles (which represent πBU) are of equal height.
No doubt, if you are a business unit head, this is not an optimal (or fair)
allocation of earnings. ALCO, the committee responsible for IRR
management, decided to bet against rising rates, but the business
units bore a portion of the earnings reduction when interest rates rose.
Conversely, although the business units are not likely to complain
about it, if rates decline and bank earnings increase, the business
units will be credited with some portion of the increase.
Most banks that employ FTP will deny the possibility of such a
discrepancy, but they cannot actually say to what extent the earnings
risk profiles of the bank and the mismatch centre are aligned because
most banks don’t bother to model the mismatch centre. While this
omission indicates a failure to model risk and profitability at a
sufficiently granular level, it ultimately reflects a governance problem
which will be addressed in more detail in the next section.
For this reason, in addition to the earnings risk profile of the mismatch
centre, the earnings risk profiles of each of the business units should
also be modelled and analysed. Although FTP may be used to
estimate margin contributions at a very granular level, without an
analysis of the earnings risk profiles of the individual business units
and the mismatch centre, there is no proof that FTP has immunised
each of the business units against IRR and LR, and that all IRR and
LR in the bank has been transferred to the mismatch centre. FTP
cannot be assumed to be functioning properly.
When it comes to FTP and defence of the mismatch centre, the latter
members have an innate conflict of interest: they are members of
ALCO and, as such, should be accountable for the earnings and risk in
the mismatch centre, but they also represent the interests of their
respective business units. When it comes to decisions about the price
of transferring risks from their business units to the mismatch centre,
they surely want the benefits of risk immunisation, but they may not
want to pay full price for it.
The conflict of interest does not require that the business unit heads
be excluded from ALCO. Quite the contrary, their input and knowledge
of product behaviours, not to mention their ability to influence product
behaviours, is essential knowledge for ALCO to be effective at risk
identification, risk measurement and risk management. To address the
conflict of interest, banks should consider establishing a sub-
committee of ALCO that has the authority to develop and manage FTP
methodologies and oversee the calculation of mismatch centre
earnings. In addition to managing conflicts of interest, it is up to
finance to hold ALCO accountable for these risk-related earnings,
especially considering that banks are required to hold capital against
IRR and LR. If ALCO is unable to generate consistent and stable
earnings on this capital, it is worth considering limiting the amount of
risk ALCO can take. Without a reasonable quantification of IRR- and
LR-related earnings, this issue cannot be addressed in any meaningful
way. Everyone just assumes that ALCO is a good steward of capital.
If ALCO structures the balance sheet to be free of IRR and LR, the
earnings in the mismatch centre should be zero.
IRR and LR are distinct risks that are quantified and managed
separately, and FTP rates, as we will see in the next section, have
separate components which correspond to duration and liquidity.
When these components are properly maintained, the earnings in the
mismatch centre can be disaggregated into the return to taking interest
rate risk πIRR and the return to taking liquidity risk πLR:
where πCR equals the earnings derived from credit risk, πIRR equals
the earnings derived from IRR, πLR equals the earnings derived from
LR, and πFV equals the earnings derived from the deposit franchise
(which is immunised, in large part, by access to deposit insurance).
This is essentially the same as Equation 15.7 that was described
earlier, where lending was substituted for credit risk and deposit-
gathering was substituted for the deposit franchise. Equation 15.15
should make it clear that if the returns to taking IRR and LR are not
computed correctly then either the return to taking credit risk or the
return to the deposit franchise, or both, will not be correctly stated. We
contend that the ability to solve this equation correctly is fundamental
to being able to claim that an FI is well-managed.
Over the years, I have known many FTP managers, often highly-
skilled “quants”, who either selected the wrong funding curve (or did
not argue against the selection of an inappropriate curve) or who
developed complex FTP methodologies which failed to acknowledge
the re-pricing and liquidity characteristics of the products to which they
were applied. Worse yet, they never bothered to consider the earnings
risk profiles of their mismatch centres. One look at the level of
mismatch centre earnings told me that there was a critical error
somewhere in their FTP framework.24 Absent consideration of the role
of the funding curve and how all the pieces come together dynamically,
it is easy to end up with a framework that is not effective at immunising
the business units against IRR and LR or at transferring these risks to
the mismatch centre. Remember the expression: “Be careful that you
can’t see the forest (or wood) for the trees”.
Note the use of the term “basis-adjusted” to describe the swap curve.
Swap rates are quoted with reference to a floating rate of some
specified term.25 The FI must decide on the basis for the swap curve it
will use in the calculation of FTP rates. My preference is to swap
everything back to the overnight rate as this brings all IRR into the
mismatch centre at a zero-duration equivalent. When adjustable-rate
instruments (here defined to mean that they reset less frequently than
overnight) are then transfer priced using such a curve, a basis
adjustment is required.
Once the all-in funding curve and swap curve have been defined, a
historical database of daily all-in funding rates and interest rate swap
rates must be developed; the FTP rate calculations for all existing
business will reference this database. The simulation engine that is
used in risk and profitability modelling work should also be able to
evolve all-in funding rates and swap rates into the future across
multiple scenarios to enable computation of the earnings risk profile of
the mismatch centre, and to compute FTP rates and spreads on new
business; the latter functionality is necessary to carry out budgeting
and forecasting exercises in a manner that is consistent with risk
quantification.
Once the curves are set, we can then consider FTP methodologies.
For FTP to immunise a transaction from IRR and LR, the methodology
must acknowledge all the re-pricing and liquidity cashflows of the
transaction. Approximations, such as the weighted average life (WAL)
or estimated duration, will not be accurate in many circumstances and
should be avoided as a general practice.
where Repr cashflowτ is the repricing cashflow, Spot swap rateτ is the
corresponding point on the basis-adjusted swap curve, τ is the term
point, Cashflowτ is the liquidity cashflow, and Spot LPτ is the
corresponding point on the liquidity premium curve (recall that this is
the difference between the all-in funding rate and the basis-adjusted
interest rate swap rate).
The first term reflects the cost to hedge (or hedging value of) the
duration of the instrument and the second term reflects the cost to
hedge (or hedging value of) the liquidity of the instrument. For fixed
rate instruments, these two terms are calculated at the origination date
of the transaction, and they do not change over the life of the
instrument. For floating and adjustable rate instruments, the first term
is recalculated at each rate reset date, while the second term is
calculated only at the time of origination and is held constant until
maturity.
There are a few special cases to consider. For fixed rate instruments,
because the re-pricing and liquidity cashflows are one and the same,
the two terms can be collapsed, and the all-in FTP rates can be
applied to the liquidity cashflow schedule. Where instruments have
embedded optionality, such as a loan prepayment option, an interest
rate cap or floor, an additional option charge can be added or
subtracted as appropriate.26 If an instrument should not receive a
liquidity charge, eg, a bond that is a high-quality liquid asset (HQLA),
or an instrument has no liquidity value, eg, a deposit that must be fully
collateralised, then the liquidity premium should be zero.
Let’s see what this looks like in practice using the output of a
behavioural model for NMDs that I developed to align the treatment of
deposit behaviours in risk and profitability management exercises. The
model combines vintage-level decay functions, rate beta functions and
processes for dynamically bifurcating balances into stable and non-
stable portions to produce a time series of re-pricing and liquidity
cashflows. For each behaviourally-distinct NMD product on the
balance sheet, the model produces cashflow schedules that can feed
any ALM model, and it produces FTP rates that can be loaded into
product pricing and budgeting/forecasting systems. Without having to
describe the cashflow logic within the model, or even the formulas
used to calculate the FTP rates, Figures 15.11 to 15.14 demonstrate a
logical evolution of FTP spreads for two different products over a span
of time where interest rate swaps and liquidity spreads changed
significantly and are anticipated to continue changing. One product is a
low rate, small balance savings account and the other is a high rate,
large balance money market deposit account (MMDA).28
The model was used to generate FTP rates using the estimated re-
pricing and liquidity cashflows for monthly vintages of deposits that go
back to early 2006 and reach to the end of 2018. The deposit
behaviours were analysed at the end of 2017, and were forecasted
through 2018 to populate the budget for the bank as well as one-year
IRR and LR simulations. Within the behavioural model, each vintage of
deposits was assigned an FTP rate that reflected swap rates and
liquidity premiums in effect at the time of its origination.29
Figure 15.11 shows the evolution of the FTP rate and FTP spread for
the savings product. One-month Libor (the reference rate to which the
beta function is indexed), the customer rate (coupon) and the one-
month liquidity premium are also shown for reference. Note how the
FTP rate increases in late 2008 even as the Federal Reserve was
reducing the Fed funds rate. The increase occurred because the
liquidity value of the balances rose dramatically when funding spreads
widened by several hundred basis points. While the value of the
deposit’s duration decreased, its liquidity value increased substantially.
The one-month liquidity premium (LP) is shown as a proxy for the
market price of the liquidity value of the deposit cashflows. In the
calculation of the FTP rate shown, each individual cashflow receives
an LP corresponding to its term to maturity; the first liquidity cashflow
receives the one-month LP, the second cashflow receives the two-
month LP, and so on, with the final cashflow, at month 120, receiving
the 10-year LP.30
When the liquidity crisis subsided in late 2009 and LPs contracted,
while marginal FTP rates decreased quickly, the FTP rate on the
product (which is a balance weighted average of the FTP rates on
each vintage) did not adjust down instantaneously.31 Each vintage has
a long life, and the LP for a vintage is set at the time of origination, so
the quantified value (hedging power) of balances originated in 2008
and 2009 persists until the decay functions controlling these vintages
terminate. The decline in the FTP rate on the product therefore
occurred over many years, as these very valuable vintages amortised
down and were slowly replaced with newer vintages that had both
lower duration values and lower liquidity values.
FTP rates and spreads on the savings product did not increase until
after the Federal Reserve began to increase the Fed funds rate, and
the yield curves re-steepened, and even then the increase has been
very slow (for the same reason that the downward adjustment in FTP
rates was slow). Note also that the FTP rate and spread extends on
through the 2018 budget horizon, a period over which the bank had
anticipated three more increases in the federal funds rate. Despite the
change in direction, the FTP spread on the product is anticipated to
remain relatively stable. The critical assumption is that its behaviour
will remain consistent with that observed over the calibration period. If
the product behaves as anticipated, the deposit-gathering business
units will be largely immunised from IRR- and LR-related volatility, and
the hedging value of the deposit will be transferred to the mismatch
centre.33 This analysis demonstrates a well-functioning FTP
methodology for this product. There are myriad other ways to produce
FTP rates for NMDs, but if the FTP rates behave materially different
than what has been shown here, it’s not clear that they have any
economic rationale and will not be effective at immunising deposit
gatherers against IRR and LR.
For many years prior to the financial crisis, LPs for highly-rated banks
were close to zero, even negative for some. Unfortunately, many of
these institutions assumed this would always be the case, and they did
not design internal transfer pricing processes that could handle non-
zero LPs. When the liquidity crisis hit, lenders kept lending as if
liquidity was free and deposit gatherers priced deposits as if they had
no liquidity value relative to wholesale funding. Seeing how banks
ignored this important component of economic value, it is clear why
the liquidity crisis was so severe.34 Despite the rapid recognition that
failures of FTP exacerbated the severity of the crisis, it was almost a
decade before US bank regulators introduced guidance mandating
that FTP methodologies should explicitly acknowledge the cost/value
of liquidity.35 Even so, the regulatory requirements are only applicable
to the SIFIs, as if smaller institutions should not bother to consider that
the value of liquidity is no longer zero and can change rapidly. In fact,
smaller institutions face higher absolute liquidity costs and are
exposed to great volatility in their funding spreads, and should
therefore be even more compelled to consider that the value of
liquidity is properly acknowledged in FTP rates for loans and deposits.
What about the following observation in the guidance is not applicable
to all levered FIs?
Figures 15.13 and 15.14 provide a similar analysis of FTP rates and
spreads for the MMDA product. Here, we see considerably more FTP
spread volatility, but this volatility does not indicate a failure of the
behavioural model. Rather, it is an indication that the behaviour of the
product was not stable or consistent with static behavioural
assumptions, and this is okay. When the Federal Reserve began to
lower the Fed funds rates in September 2007, the liquidity crisis was
still a year away. With a modelled rate beta of one (which feels risk-
averse, except, of course, when we consider behaviours in declining
rate environments), the bank would have been expected to decrease
the customer rate on the MMDA in line with the decrease in market
interest rates, but this is not what happened. As this product
represented a material source of funding, the bank was compelled to
pay above-market rates to ensure that it did not lose these deposits.
Initially, the economic value of the deposits declined, and therefore the
lag in the customer rate pushed the FTP spread below zero. It
returned to a positive value once the value of liquidity increased
dramatically (when the bank’s wholesale funding spreads blew out),
but the subsequent volatility in the value of liquidity continued to be
transmitted through the FTP rate, resulting in a volatile FTP spread.
Since this product is also modelled with a relatively high non-stable
haircut (~45%), changes in the month-to-month value of overnight
duration and liquidity flow instantly through the FTP rates. Again, this
is not a failure of the model to immunise against any spread volatility;
this product simply has a large portion of its balance that is no more
(or less) valuable than overnight funding. During the market turbulence
of 2008–09, this value was changing quickly.
Before turning to an analysis of the FTP rate and FTP spread where
the value of liquidity is ignored, it’s worth noting what happened with
the customer rate on this product during and after the crisis. When the
Federal Reserve began to lower the Fed funds rate in September
2007, the markets had yet to signal concerns about the price and
availability of liquidity. Even so, this bank understood the critical value
of these high balance deposits and deliberately chose to acknowledge
that value by keeping the customer rate high. By early to mid-2008, the
market began to express widespread concern about the value and
availability of liquidity, and it was at this point that the FTP rate
increased quickly. This is a great lesson of how a pricing model, even
one that is explicitly designed to acknowledge the contemporaneous
value of duration and liquidity, may not be sufficiently forward-looking
to anticipate dramatic shifts in economic value. It should be clear that
efforts to smooth spread volatility – for instance, through the use of
moving averages – will only serve to delay the recognition of such
market shifts; for institutions that were not otherwise self-aware, these
delays proved fatal.
Figure 15.14 shows the evolution of the FTP rate and FTP spread
where the liquidity spreads are set to zero. Given the relatively high
customer rate that persisted in the near-zero federal funds
environment, the FTP spreads would have remained negative for
almost a decade! Clearly, there is a compelling need to acknowledge
the value of liquidity when computing the hedging value of any deposit,
even ones with substantial balance volatility and rate sensitivity;
overnight liquidity may not seem like much, but at times it can be the
difference between survival and failure. It should also be clear that
when FTP rates are not economically rational, they get determined
arbitrarily and require constant adjustment to make sense in whatever
post-event narrative the company is trying to sell.
COMPUTATIONAL SYSTEMS
A comprehensive analysis of earnings and risk in a bank requires that
one is able to determine the slope of the earnings risk profile of the
bank and the mismatch centre, and be able to compare them. To do
this, one needs the ability to simulate bank and mismatch centre
earnings across a multiplicity of rate scenarios. ALM systems by their
nature are forward-looking, and have the capability to generate
earnings across multiple future business scenarios.36 With this
capability, they can produce an estimate of the earnings sensitivity of
the bank.
The optimal solution is a system that has the ability to compute IRR
and LR in the bank and the mismatch centre at the same time. If this
sounds like a super-capable ALM system, your instincts would be
correct. An ALM system that can simultaneously compute FTP rates
on existing and new business can be used to analyse the earnings risk
profile of the bank and the mismatch centre. To tackle the comparison
using two separate systems, one for the bank and one for the
mismatch centre, is to accept the unnecessary task of ensuring that
transactional and market data, cashflow rules, behavioural functions
and output are all fully synchronised. This is a tall order. It should be
evident that consideration of the mismatch and how it must be
modelled is an essential consideration in the selection of the
computational system.
CONCLUSION
We have covered an extraordinary amount of information about the
mismatch centre. If you made it this far, congratulations! In a nutshell,
this is what you should have learned:
banks and credit unions (and levered FIs in general) play the game of
maturity transformation;
the IRR and LR profile of the mismatch centre should be parallel to that
of the bank;
the earnings in the mismatch centre represent the returns to taking and
managing IRR and LR;
Contents
Introduction
16. Prepayment Risk Modelling for ALM, Finance and FTP: A Survival
Model
RECOMMENDED BOOKS
Risk Model Operational Risk Behavioural Risk Navigating Internal Models Systematic
Validation (3rd Capital Models Management European Energy and Solvency II Trading in
edition) (2nd edition) and Commodity Energy Markets
Markets
Regulation
About us Contact us Advertising Help Centre Terms and conditions Privacy policy
© Infopro Digital Risk (IP) Limited (2020). All rights reserved. Published by Infopro Digital Services Limited, 133
Houndsditch, London, EC3A 7BX. Companies are registered in England and Wales with company registration numbers
09232733 & 04699701.