Maturity Mismatch

Prime #

982

Origin domain

Finance Economics

Subdomain

banking and liquidity → Finance Economics

Core Idea

A system holds two-sided commitments whose durations differ — a short side that must be repeatedly refreshed against a long side that cannot accelerate. Steady rollover hides the mismatch; when refreshing stops, the system fails not for lack of resources but because they are locked in durations longer than the moment requires.

How would you explain it like I'm…

The Daily Cookie Promise

Imagine you promise to give a friend a cookie every single day, but your cookie machine only bakes a giant batch once a month. As long as you have cookies saved up, everything is fine. But if your saved cookies run out before the next batch is ready, you are stuck — not because you do not have enough cookies overall, but because they arrive too slowly for your daily promise.

Fast Promise, Slow Supply

Maturity Mismatch happens when a system owes things on a fast clock but earns the money to pay on a slow clock. Think of a bank that has to give people their savings back any day they ask, but it lent that money out as a 30-year house loan that only pays back slowly. As long as people keep leaving their money in, no one notices. But if everyone wants their money at once, the bank can't speed up the slow loan to keep up. It isn't broke — it just has its money stuck in the wrong timing.

Mismatched Clocks

Maturity Mismatch is when a system holds commitments on two sides whose durations don't line up: one side promises short — bills come due on a fast clock — while the other delivers long — the capacity to generate what's owed matures slowly. While you can keep refreshing the short side (rolling over, renewing, restocking), the mismatch stays invisible, because long-tenor flow keeps funding short-tenor demand. When refreshing fails, the long side can't accelerate to compensate, and the system fails not for lack of resources but because they're locked in durations longer than the moment requires. The crucial split is solvency versus timing: a system can be solvent on net — long flow exceeds short obligation on average — and still fail at a given moment because the timing doesn't align. Two systems with identical balance-sheet totals can differ enormously in this fragility, which the bare totals hide.

 

Maturity mismatch is the pattern in which a system holds commitments on two sides whose durations do not match. One side promises short — obligations come due on a short clock — while the other delivers long, its capacity to generate the needed resource maturing on a long clock. While conditions permit refreshing the short side (rolling over, renewing, restocking), the mismatch is invisible: long-tenor flow continues to fund short-tenor demand. When refreshing fails, for any reason that closes the short-side market, the long-tenor flow cannot accelerate to compensate, and the system fails not because it lacks resources but because the resources are locked up in durations longer than the moment requires. The roles are definite: two-sided commitments with mismatched maturity distributions; a short side that must be refreshed and a long side that cannot accelerate; steady rollover that renders the mismatch invisible; rollover failure that produces failure unrelated to net solvency; a defence of duration restructuring or liquidity bridging rather than added capacity; and the worst-case mismatch, not the average operating need, setting the required reserve. The frame's payoff is separating solvency from timing — a system can be solvent on net yet fail at a given moment because the durations do not align, a distinction the bare totals hide.

Broad Use

• Banking: Long-tenor loans funded by short-tenor deposits — lost deposit funding triggers a run even on sound loans.
• Supply chains: Long-lead-time inputs against short-cycle demand — a forecast error strands inventory while demand goes unfilled.
• Ecology: A species with long generation time facing short-cycle predation cannot accelerate reproduction, so the population collapses despite healthy individuals.
• Workforce: A decade-long training pipeline cannot flex to meet a sudden demand shock — an epidemic surge or retirement wave.
• Infrastructure: Multi-year generation build-times against hourly load — brownouts even when nameplate capacity is adequate.
• Policy: Short-term benefits backed by long-term obligations that cannot be funded fast enough when conditions shift.
• Tech platforms: Short-term contracts requiring long-build features — when churn outpaces shipping, the platform cannot reconfigure to retain customers.

Clarity

Separates solvency from timing: a system can be solvent on net and still fail because the duration ratio does not align — a difference two identical balance sheets render invisible.

Manages Complexity

Compresses fragility analysis into three quantities — the tenor distribution of obligations, of capacity, and rollover availability — so a stress test can vary the third while holding the structure fixed.

Abstract Reasoning

Yields three deductions: mismatch fragility is invisible in good times, the defence is duration not amount (more long-tenor capacity does nothing unless it shortens tenor), and liquidity is the worst-case-sized bridge across a rollover failure.

Knowledge Transfer

• Banking → supply chain: The machinery (liquidity coverage, stress tests) ports as safety stock, supplier diversification, and just-in-case buffers.
• Banking → ecology: It ports as life-history risk and minimum-viable-population analysis tuned to generation time.
• Banking → energy: It ports as the capacity-versus-flexibility distinction in grid planning.

Example

A community bank funding thirty-year mortgages with demand deposits fails on a run not because it is insolvent — the mortgages may be sound — but because the mortgage market clears in weeks while the run clears in hours. The same bank funded by five-year deposits rides through unchanged: the difference is duration, not amount.

Relationships to Other Primes

Parents (1) — more general patterns this builds on

• Maturity Mismatch is a kind of, typical Coupling — Maturity mismatch is the TEMPORAL dimension of coupling between two sides of a system — how fast each can respond — a specialized two-clock duration-ratio coupling. The file itself contrasts it with bare coupling (strength) as the temporal specialization.

Path to root: Maturity Mismatch → Coupling

Not to Be Confused With

• Maturity Mismatch is not Liquidity because the mismatch is the structural condition that creates the liquidity requirement (the threat), whereas liquidity is the property of being convertible (the defence).
• Maturity Mismatch is not Systemic Risk because the mismatch is vulnerability within one system, whereas systemic risk is contagion across institutions.
• Maturity Mismatch is not Coupling because it concerns the temporal dimension — how fast each side can respond — whereas coupling concerns the strength of interdependence.