Funds Transfer Pricing: Calculation & Impact on Profitability

Search Fintrev

Search our guides, reviews and glossary.

Funds transfer pricing (FTP) is the internal system a bank uses to charge or credit each business unit for the funds it uses or supplies, so that the bank’s total net interest income can be split among lending, deposit-gathering and treasury activities. A central treasury (or a dedicated FTP function) “buys” money from units that bring in deposits and “sells” it to units that make loans, at an internal rate called the FTP rate. The spread each unit earns against that rate shows how much of the bank’s margin it actually generates.

How funds transfer pricing works

A bank’s net interest income comes from the gap between what it earns on loans and what it pays on deposits and other funding. Without FTP, that profit is easy to see for the bank as a whole but hard to attribute. A deposit-rich branch that makes few loans would look unprofitable, and a lending desk funded by those deposits would look as though it earned the entire spread.

FTP solves this by inserting treasury between the two sides:

1. Liability units (retail deposits, for example) are credited an FTP rate for the funds they raise. Their margin is the FTP credit minus the rate paid to customers.
2. Asset units (mortgages, commercial loans) are charged an FTP rate for the funds they use. Their margin is the customer yield minus the FTP charge.
3. Treasury holds the difference between what it charges and what it credits, along with the interest rate and liquidity risk that the FTP mechanism transfers to it from the business lines.

Because every internal charge has a matching internal credit, the transfers net to zero at the consolidated level. FTP changes how profit is attributed, not how much the bank earns.

Calculating funds transfer pricing

There is no single regulatory formula, but most frameworks follow the same structure:

FTP rate = base rate for the matching term or repricing period + adjustments

Asset unit margin = customer loan rate − FTP charge rate

Liability unit margin = FTP credit rate − customer deposit rate

The base rate comes from a reference yield curve chosen by the bank, read at the maturity or repricing date of the product. The adjustments vary by institution and product. Common components:

• Funding liquidity spread: the cost of term funding beyond the base curve.
• Contingent liquidity spread: the cost of holding liquid buffers against undrawn commitments or deposit outflows.
• Credit spread: an adjustment some frameworks apply for the credit component of funding costs.
• Option spread: the cost of embedded options, such as a borrower’s right to prepay or a depositor’s right to withdraw early.
• Basis spread: the difference between the index a product is priced on and the curve used for transfer pricing.

Interpreting funds transfer pricing

FTP work centers on a yield curve built from pooled asset and liability data and the chosen reference rates. Each product sits on the curve at its term, which is why a five-year fixed loan carries a different internal charge from a variable-rate overdraft. Management dashboards track FTP metrics alongside net interest margin (NIM) and net income.

A positive unit margin means the business earns more than the bank’s internal cost of funds for that product. A thin or negative margin signals mispricing, excessive risk or a product that only appears profitable because it was never charged for liquidity.

FTP methodologies

Single-rate FTP

Every asset and liability receives the same transfer rate, regardless of product type or maturity. It is simple to run and gives a broad view of assets against liabilities, but it ignores differences in term and liquidity. Long-dated fixed loans and overnight funding are treated alike, so interest rate risk stays mixed into the business units’ results.

Multi-rate FTP

Assets and liabilities are grouped by chosen characteristics, often product and maturity, and each group gets its own rate built with the spread components above. This shows management the risk embedded in each group.

Matched-maturity FTP

The most granular approach prices each instrument, or each tranche of cash flows, off the reference curve at its own term or repricing date. It moves interest rate risk out of the business lines and into treasury, where it can be managed and hedged centrally. The trade-off is heavier data and modeling requirements, especially for products without a contractual maturity.

Worked example

Hypothetical figures, for illustration only. A bank gathers $100 million in savings deposits paying customers 1.5% and lends the same $100 million as five-year business loans at 7.0%. Its FTP framework credits the deposits at 4.0% (based on an assumed behavioral life for the balances) and charges the loans 4.5% (the five-year base rate plus a liquidity spread).

The three margins add up to the bank’s overall spread. The example assumes equal balances and ignores credit losses, operating costs and capital. Without FTP, the lending unit would appear to earn the full 5.5% and the deposit unit nothing. With FTP, management can see that cheap, stable deposits are worth almost as much as the loans they fund. If the lending desk wanted to price loans at 4.0%, the FTP charge would show immediately that the product loses money even though the bank’s average cost of deposits is only 1.5%.

How banks use FTP

• Product pricing: setting loan and deposit rates above or below the internal cost of funds, for example when pricing a mortgage with a long fixed term and prepayment option.
• Profitability reporting: measuring results by product line, customer relationship and branch.
• Branch decisions: comparing each location’s deposits, loan balances and customer numbers against its FTP-adjusted contribution. A branch that keeps underperforming its baseline may be closed.
• Risk transfer: centralizing interest rate and liquidity risk in treasury so that business units are judged on what they control. FTP is run alongside asset/liability management.

Regulation

After the 2007 to 2008 financial crisis, the Dodd-Frank Act pushed large U.S. banks toward stronger liquidity and capital positions, and supervisors looked harder at how banks charge for liquidity internally. In 2016 the Federal Reserve and other agencies issued SR 16-3, interagency guidance on funds transfer pricing for funding and contingent liquidity risks at larger institutions. It sets expectations for governance and practice, not a prescribed formula or a standard reporting metric. FTP complements, rather than replaces, regulatory measures such as the capital adequacy ratio.

Limitations

• Assumption-driven results: the choice of reference curve and liquidity spreads directly shifts profit between units. A different curve can turn a “profitable” product into a loss-maker.
• Behavioral modeling: checking and savings balances have no contractual maturity, so their FTP credit depends on assumed balance lives that may not hold.
• Excess deposits: when deposits exceed loan demand, crediting every deposit at a term funding rate can overstate their value.
• Complexity and gaming: matched-maturity systems need detailed data, and units may steer toward products the methodology happens to favor.

Distinctions readers confuse

• Transfer pricing (accounting and tax): the prices one division or affiliate charges another for goods and services, often across borders. FTP deals only with the internal price of money inside a bank.
• Net interest margin: NIM measures the bank’s overall spread on earning assets. FTP divides that spread among units.
• FTP in computing: File Transfer Protocol is a network standard for moving files and has no connection to banking.

FAQs

The Bottom Line

FTP matters to bank managers, analysts and anyone judging which products, branches and desks actually generate margin. It reveals the value of cheap, stable deposits and exposes loans priced below the internal cost of funds. Its results depend heavily on the reference curve, liquidity spreads and assumed deposit lives, so the outputs deserve as much scrutiny as the assumptions behind them.