How Matched-Maturity FTP Algorithms Split Repricing Risk from Contingent Liquidity: Dual Horizons, Behavioural Deposits and Stress Consistency

Reader question: A five-year loan may reprice every three months, while the bank may fund itself with deposits, secured borrowing and long-term wholesale debt. What internal funding cost should the lending business be charged so that its reported margin reflects the funding and liquidity risk it actually creates?

Funds transfer pricing, or FTP, is the internal algorithm that answers this. A central treasury or balance-sheet function assigns funding costs and benefits to products and business lines using a documented curve and product-specific maturity, repricing and liquidity assumptions.

The important mathematical idea is that one transaction can contain several different horizons. A five-year floating loan has short interest-rate repricing risk but long funding/liquidity need. A non-maturity deposit has no contractual maturity but may behave like stable funding for years. An undrawn credit commitment has little current balance-sheet funding need but can create a stressed liquidity draw.

Good FTP therefore does not apply one average bank funding rate to everything. It maps each product’s economic characteristics to the relevant points on one or more internal transfer curves.

What this page owns — and what it does not

This page owns the computational transformation:

central funding/liquidity curves + product cash-flow/behaviour assumptions → internal transfer rate or charge/credit → risk-adjusted business margin.

It does not replace net-interest-income simulation, which owns balance-sheet earnings under rate scenarios; deposit-pricing algorithms, which own customer-facing rate choice; or wholesale-funding rollover-risk models, which own refinancing capacity and spread stress.

This is banking mathematics and risk-management education. It is not a recommendation about how any particular bank should price a loan, deposit or funding instrument.

Why FTP exists

Suppose a lending desk books a five-year fixed-rate loan at 6%. If its profitability report subtracts only today’s overnight rate of 3%, it appears to earn a 3% spread.

But the bank has committed capital and funding capacity for five years. If five-year marginal funding is 4.5%, the economic funding margin is much smaller.

Conversely, a stable deposit business provides funding value to the bank. If it is judged only by customer interest expense and fee income, the business can be under-credited for the balance-sheet benefit it creates.

FTP moves those funding and liquidity economics to the business line that creates them while centralising the residual treasury risk.

Regulatory guidance treats FTP as a risk-allocation system

The Federal Reserve, FDIC and OCC jointly issued U.S. interagency guidance on FTP related to funding and contingent liquidity risk in March 2016.

The guidance describes FTP as a process that allocates funding and contingent liquidity costs and benefits to business lines, products and activities. It says the framework should be consistent, transparent, repeatable and granular enough to align incentives with the firm’s risk appetite.

The Basel Committee’s Principles for Sound Liquidity Risk Management similarly state that banks should incorporate liquidity costs, benefits and risks into internal pricing, performance measurement and new-product approval for significant business activities.

The matched-maturity marginal-cost idea

The interagency guidance identifies matched-maturity marginal cost of funding as a commonly used methodology for non-trading exposures.

Conceptually, build a term structure:

f(T) = marginal cost of bank funding for horizon T.

Then a product with expected funding horizon T receives a transfer cost or benefit related to f(T), rather than one average cost of all historical funding.

This matches long-lived assets with long-horizon funding economics and gives stable liabilities a longer-horizon funding benefit.

Marginal cost versus average cost

Suppose a bank has old five-year debt issued cheaply three years ago and new five-year debt would now be expensive.

Average historical cost reflects the funding stock already on the balance sheet.

Marginal cost asks what an additional unit of economically comparable funding costs now.

For new-product pricing, the marginal concept usually aligns incentives more directly because the new asset changes the bank’s future funding need. But a framework can use different methods for different purposes if governance makes the distinction explicit.

A stylised FTP curve

One simplified decomposition is:

FTP(T) = reference rate(T) + bank funding spread(T) + liquidity adjustment(T).

This is not a universal regulatory formula. It is a useful computational decomposition.

The reference component captures the market time value of money. The bank funding spread captures the institution’s incremental borrowing economics. The liquidity adjustment can capture the value or cost associated with stability, tenor or standby liquidity under the bank’s framework.

Credit risk of the customer should not be silently mixed into the central funding curve unless the framework explicitly intends that. Otherwise the business line cannot distinguish funding margin from customer credit margin.

One product can require two horizons

The interagency guidance gives a particularly useful example: a five-year commercial loan whose interest rate resets every three months and is expected to be held to maturity.

It notes that the interest-rate component of funding risk could use a three-month horizon, while the liquidity component could use a five-year horizon.

A stylised transfer charge can therefore be written:

FTP = r_3m + λ_5y,

where r_3m is the relevant short repricing component and λ_5y is the longer-horizon liquidity/funding component.

This decomposition prevents a floating-rate asset from being treated as if its entire funding economics reset every three months.

Fixed-rate assets

For a bullet fixed-rate loan, a simple matched-maturity approach can charge the transfer rate at the expected funding life.

For amortising assets, one point on the curve can be too crude. A cash-flow-weighted transfer price can instead use the scheduled principal profile.

Let expected principal cash flows occur at times t_i. A stylised weighted funding spread is:

λ̄ = Σ w_i λ(t_i)

with weights based on present-value or outstanding-balance exposure to each horizon.

The exact weighting rule belongs to the bank’s documented methodology, but the mathematical principle is clear: funding tenor should follow expected cash-flow life rather than contractual label alone.

Prepayment changes expected life

A 30-year mortgage rarely behaves like a deterministic 30-year bullet loan.

If borrowers can prepay, the expected funding life depends on the prepayment model. Faster prepayment shortens the effective horizon and can reduce long-term funding need; slower prepayment extends it.

This links FTP to mortgage prepayment mathematics. The same expected-life assumptions used for funding should be reconciled with the assumptions used in interest-rate and liquidity-risk models.

Non-maturity deposits

A current account or savings deposit may be withdrawable on demand, so contractual maturity is effectively overnight.

Yet a diversified deposit base can remain behaviorally stable for years.

FTP therefore often assigns a behavioural maturity rather than mechanically using one-day funding value.

A simplified distributional model can assign fractions:

q₁, q₂, …, q_n

to behavioral maturity buckets:

T₁, T₂, …, T_n

with:

Σ q_j = 1.

The funding benefit can then be approximated by:

FTP benefit = Σ q_j f(T_j).

This makes behavioural assumptions mathematically visible instead of hiding them inside one invented “deposit maturity.”

Deposit beta is not behavioural maturity

Deposit beta measures how customer deposit rates respond to changes in market rates.

Behavioural maturity measures how long the deposit balance is expected to remain economically available.

They are related but distinct.

A low-beta deposit can still run quickly in stress. A high-beta deposit can still be operationally sticky. An FTP engine that equates “cheap” with “stable” can misprice funding value.

Contingent liquidity risk

An undrawn revolving credit facility may have little current balance-sheet exposure but can create a large future funding demand if customers draw during stress.

The interagency guidance says contingent liquidity charges can use behavioral assumptions such as modeled drawdown likelihood, customer history and credit quality. Similar logic applies to collateral calls and stressed secured-funding haircuts.

A stylised expected standby-liquidity charge is:

charge ≈ stressed draw amount × cost of standby liquidity / facility notional.

The actual framework can be more conservative and nonlinear. The important point is that off-balance-sheet liquidity is not free merely because current funded balance is zero.

Liquidity value of stable funding

Stable deposits or term funding reduce the bank’s reliance on less reliable short-term funding.

An FTP system can therefore credit the originating business with a funding benefit linked to tenor and stability.

This aligns with Basel liquidity principles, which state that internal pricing should consider the benefits of relatively stable funding sources as well as costs and risks.

FTP and business-line margin decomposition

For a loan with customer rate r_cust, a stylised decomposition is:

customer rate = FTP + credit/operating/business margin.

Therefore:

business margin = customer rate − FTP − other allocated costs.

For a deposit, the signs reverse conceptually:

deposit franchise margin ≈ FTP funding benefit − customer deposit rate − allocated costs.

These are managerial decompositions, not accounting identities. Their usefulness depends on whether FTP accurately transfers the risks the framework claims to centralize.

Why FTP can change business incentives

Suppose a desk can book either:

• a short liquid asset;
• a long illiquid asset with the same customer spread over a reference rate.

If both receive the same internal funding charge, the long illiquid asset looks artificially attractive.

A matched-maturity liquidity charge reduces that distortion by making the business line pay for the longer funding commitment it creates.

This incentive effect is central to the regulatory rationale for FTP.

Curve construction

A bank can derive its marginal funding curve from combinations of:

• wholesale unsecured debt;
• secured funding;
• deposit funding;
• central-bank or home-loan-bank-style advances where relevant;
• market reference curves;
• cross-currency basis for foreign-currency funding;
• institution-specific issuance spreads.

The interagency guidance specifically gives the example of a wholesale long-term debt curve adjusted for alternate funding sources.

The chosen curve must be explainable to users. A transfer rate generated by a black-box blend of unrelated funding instruments can produce precise but ungovernable margins.

Interpolation between funding tenors

If the treasury curve is observed at 1, 3, 5 and 10 years but a product has expected life 4.2 years, the FTP engine needs interpolation.

Possible choices include:

• linear interpolation of zero rates;
• linear interpolation of spreads;
• discount-factor interpolation;
• piecewise forward interpolation.

Different interpolation rules can produce different transfer rates. The method should match the quantity being interpreted and be consistent with the bank’s broader curve framework.

Historical lock versus current curve

For performance measurement, many FTP systems lock the transfer rate at transaction inception so the originating business retains customer spread while treasury owns subsequent funding-rate movement.

For new-product pricing, the current marginal curve is usually more relevant.

This creates two valid but different questions:

• What FTP rate was assigned when the trade was booked?
• What would this product cost to fund if originated today?

Confusing them can make historical profitability appear to change merely because the current curve moved.

FTP is not a hedge

An internal transfer charge moves economic responsibility between business lines and treasury. It does not itself create an external market hedge.

If treasury receives the interest-rate or liquidity risk through FTP, treasury still has to manage that risk through funding, hedging, liquid-asset buffers or balance-sheet strategy.

This is why FTP complements rather than replaces interest-rate risk, liquidity stress testing and contingency funding.

Inputs and outputs

A robust FTP engine can require:

• product and transaction identifier;
• currency;
• origination date;
• contractual maturity;
• repricing schedule;
• expected cash-flow profile;
• prepayment/early-withdrawal assumptions;
• behavioural maturity distribution;
• funding-curve version;
• liquidity-spread curve;
• secured/unsecured funding treatment;
• contingent draw/haircut assumptions;
• interpolation rule;
• governance/model version.

Outputs can include an interest-rate transfer component, liquidity component, contingent-liquidity charge, total FTP rate, FTP benefit for funding products, locked historical transfer rate, margin decomposition and diagnostic reason codes.

Evidence polarity: what supports confidence?

Evidence for an FTP framework includes transfer rates that reconcile to observable marginal funding data, product horizons that match actual repricing and cash-flow behaviour, deposit maturities supported by historical stability evidence, consistency with liquidity stress assumptions, transparent curve construction and stable results across independent recalculation.

Evidence against confidence includes one flat FTP rate applied across all maturities, five-year floating loans priced as three-month funding in every component, non-maturity deposits assigned arbitrary long maturity, contingent commitments receiving zero liquidity cost, or business margins changing because historical FTP was silently overwritten by today’s curve.

Counterexample: a three-month reset does not make a five-year loan a three-month funding exposure

The customer rate may reset every three months, reducing fixed-rate sensitivity.

But the bank can still be committed to supply principal for five years.

Using only a three-month FTP point can therefore transfer the interest-rate component correctly while omitting the longer liquidity component.

Counterexample: stable deposits can become unstable in stress

A deposit cohort may have an average observed life of five years in normal conditions.

If the same model assigns five-year stability during a bank-specific run scenario, contingent liquidity risk can be severely understated.

The interagency guidance explicitly says behavioral assumptions used in FTP should be compared with those used in internal stress testing, and inconsistencies should be documented.

Counterexample: average funding cost can reward new long-risk business

If old low-cost debt pulls the average funding cost below current marginal market cost, a new long-dated asset can look profitable at a price that would not cover incremental funding economics.

Average-cost FTP can be useful for some management views, but it can distort new-business incentives if used without understanding this effect.

Counterexample: perfect FTP allocation does not eliminate bank-wide funding risk

Suppose every product is charged exactly the right internal liquidity cost.

The bank can still fail to raise external funding in stress.

FTP aligns incentives and centralizes risk ownership; it does not manufacture external liquidity.

Weak links in implementation

Curve/source mismatch. FTP uses a stale funding spread while treasury’s actual marginal issuance spread has moved.

Currency mismatch. A domestic funding curve is applied to foreign-currency assets without basis/funding treatment.

Behavioural model drift. Deposit stability changes but the maturity distribution is not updated.

Prepayment inconsistency. FTP assumes one mortgage life while IRRBB and liquidity stress use another.

Credit/funding contamination. Customer credit risk is buried in the treasury curve and then charged again in business credit margin.

Historical overwrite. Locked FTP rates are recalculated with today’s curve.

Interpolation discontinuity. Small maturity changes jump between buckets and create cliff pricing.

Contingent-risk omission. Undrawn commitments and collateral calls are treated as zero-cost.

Diagnostics: how to test an FTP engine

• curve replay: reconstruct every transfer rate from the archived funding curve and methodology.
• matched-horizon test: compare repricing and liquidity horizons for floating long-dated assets.
• cash-flow test: calculate FTP on a bullet asset and an amortising asset with the same legal maturity.
• prepayment test: accelerate and slow expected life and verify the liquidity component responds in the expected direction.
• deposit-run test: shorten behavioural maturity under stress and measure loss of funding benefit.
• contingent-draw test: increase stressed drawdown probability on commitments and verify liquidity charges rise.
• marginal-versus-average benchmark: quantify the incentive difference under a steep change in market funding costs.
• currency-basis test: compare domestic and foreign-currency transfer prices under basis stress.
• historical-lock test: move today’s curve and verify booked historical FTP remains unchanged if policy requires locking.
• stress-consistency test: compare FTP behavioural assumptions with liquidity and IRRBB stress-model assumptions.

What would falsify confidence?

Confidence should be withdrawn if transfer rates cannot be reconstructed; if materially different products receive identical FTP without a documented reason; if funding-curve changes fail to affect new-business FTP; if behavioural assumptions contradict observed deposit/prepayment behaviour; if stress assumptions are inconsistent across FTP and liquidity models without governance; or if the framework systematically rewards products that create more funding/liquidity risk than their internal charges reflect.

Alternatives

Single-pool average-cost FTP is simple but weak at differentiating tenor and risk.

Multiple-pool FTP assigns product groups to maturity or funding pools, improving granularity while remaining simpler than transaction-level pricing.

Matched-maturity marginal FTP is more precise for transaction economics but requires robust curves and product behavioural models.

Cash-flow transfer pricing maps each expected cash flow to the term structure rather than assigning one maturity point.

The appropriate method depends on product complexity and the purpose of the framework. Regulatory guidance emphasizes transparency, repeatability, appropriate granularity and incentive alignment rather than prescribing one universal formula.

How this connects to the surrounding knowledge estate

FTP consumes term structures similar in spirit to yield-curve construction but adds bank-specific funding/liquidity spreads. Its behavioural assumptions interact with NII/IRRBB simulations, wholesale funding, liquidity stress constraints and customer deposit pricing. FTP is the internal bridge that assigns those central balance-sheet economics back to the products that create them.

Verification and update triggers

Preserve funding-curve sources, curve timestamps, interpolation rules, behavioural maturity/prepayment models, stress assumptions, transfer-rate locking policy, secured/unsecured treatment and governance version. Revalidate after large funding-spread moves, deposit-behaviour changes, liquidity stress events, new product launches, funding-strategy changes, model redevelopments or repeated profitability anomalies between product economics and realized treasury funding costs.

Primary and high-quality references

• Federal Reserve Board, Interagency Guidance on Funds Transfer Pricing Related to Funding and Contingent Liquidity Risks, including illustrative matched-maturity methodologies.
• Office of the Comptroller of the Currency, OCC Bulletin 2016-7: Funds Transfer Pricing.
• Federal Deposit Insurance Corporation, FIL-12-2016: Interagency Guidance on Funds Transfer Pricing.
• Basel Committee on Banking Supervision, Principles for Sound Liquidity Risk Management and Supervision, especially the principle on internal allocation of liquidity costs, benefits and risks.
• Basel Committee, 2019 review of the Sound Principles, confirming that the 2008 liquidity principles remained fit for purpose after review.

Educational boundary: This article explains internal bank funding and liquidity allocation mathematics. It does not recommend customer prices, treasury strategy or funding transactions for any specific institution.