Funds Transfer Pricing in Banks: Methods, Curves and Treasury Role (2026)

Funds transfer pricing in banks is the internal mechanism that gives every rupee raised or lent a notional cost or credit rate, so a branch's customer-relationship performance can be separated cleanly from the treasury's interest rate and liquidity risk-taking. For JAIIB/CAIIB Treasury Management candidates, this is one of the most testable ideas in the syllabus because it links three things examiners love to combine in one question: pricing, risk transfer, and profitability measurement.

Without an internal pricing mechanism, a branch that gathers cheap current account deposits and a branch that books long-tenor term loans would each report a distorted net interest margin — one flattered by funding luck, the other penalized by a funding mix it never controlled. Funds Transfer Pricing (FTP) fixes this by making every business unit "buy" funds from, or "sell" funds to, a central pool at a published internal rate. What remains after that internal transaction is the unit's true customer spread. This article walks through the mechanics, the two dominant methods, the curve construction logic, and where Treasury sits in governing the whole framework — grounded in how Indian banks actually run their ALM desks in 2026.

🏦 What Is Funds Transfer Pricing in Banks?

At its simplest, FTP is a transfer pricing system, not a customer-facing rate. A deposit-taking unit is "credited" an internal rate for every rupee of deposits it mobilises, as if it had sold those funds to the Treasury/ALM desk. A lending unit is "charged" an internal rate for every rupee it lends, as if it had bought those funds from the same desk. The difference between the customer rate and the internal transfer rate is the unit's own margin — cleanly separated from whatever the Treasury does with the resulting pool.

This separation matters for three reasons candidates should remember. First, it lets the bank measure product and branch profitability on a like-for-like basis, because funding cost is standardised rather than left to whichever wholesale rate happened to be available that week. Second, it moves interest rate risk and liquidity risk out of the branch network and concentrates it with the desk that is actually equipped to manage it — the Treasury, working under the broader Treasury function. Third, it becomes a pricing input: a relationship manager quoting a loan can see, in real time, whether the proposed rate clears the internal cost of funds plus a credit spread, before the deal is even booked.

💡 Exam Tip: If a question asks "why does FTP exist," the safest answer combines profitability measurement AND risk transfer to Treasury — examiners often mark down answers that mention only pricing.

⚙️ How the FTP Curve Is Constructed

The FTP curve is the backbone of the whole system — a tenor-wise schedule of internal rates that every asset and liability gets mapped onto. It is not copied wholesale from a market benchmark; it is built up from the bank's own marginal cost of raising incremental funds across different tenors, drawing on money market rates, wholesale and bulk deposit rates, and the cost implied by instruments such as certificates of deposit. Where the financial market is offering cheaper short-tenor funds than long-tenor funds, the curve slopes upward, and vice versa when the curve inverts.

A second layer sits on top of the pure cost-of-funds curve: a liquidity premium. Any asset that consumes liquidity — a long-tenor term loan, an undrawn credit commitment, an illiquid investment — is charged an additional premium reflecting the cost of holding contingency liquid assets against it. Conversely, stable-funding liabilities such as retail term deposits and a sticky core of current and savings account balances earn a liquidity credit for the stability they contribute. This liquidity component is why two loans of identical tenor and credit rating can still carry different FTP charges if one draws on a revolving facility and the other is a bullet disbursement.

Non-maturity deposits — CASA balances with no contractual maturity — need a behavioural overlay before they can even be placed on the curve. Banks typically run a core-versus-volatile split, using historical withdrawal behaviour to estimate what portion of CASA is effectively "long-tenor" stable funding and what portion could leave overnight. Only the behaviourally-derived tenor gets priced on the curve; treating all CASA as overnight money would understate its true funding value.

📊 Single Pool vs Matched Maturity FTP

Two broad methods dominate practice, and distinguishing them is a recurring MCQ theme. The single pool (average cost) method applies one blended internal rate to all assets and liabilities regardless of individual maturity. It is simple to administer and easy to explain to business heads, but it cross-subsidises: a five-year loan gets priced at the same internal rate as a three-month loan, so interest rate risk from the maturity mismatch is never explicitly recognised or charged to anyone.

The matched-maturity (marginal cost) method instead prices every asset and liability against the specific point on the FTP curve that matches its own maturity or repricing tenor. A three-year fixed-rate loan is charged the three-year curve point; a 91-day deposit is credited the 91-day curve point. This is more work to run, but it reflects true marginal economics and pushes the entire interest rate risk of maturity mismatches onto the Treasury/ALM desk, which is where the scope and function of treasury management places that responsibility in the first place. Many banks run a hybrid — multiple pools by product or currency, matched-maturity within each pool — as a practical middle ground.

⚠️ Watch Out: Don't assume matched-maturity FTP is always "better" in every exam scenario — smaller banks with thin product ranges may deliberately stay on single pool because the operational cost of a full curve isn't justified by the benefit.

🎯 Role of Treasury in Governing FTP

FTP is not a treasury-only tool; it is owned at the ALCO level and operated by Treasury. The Asset-Liability Management Committee typically approves the FTP methodology, the curve construction principles, and any change to the liquidity premium framework, since these choices directly affect reported profitability across every business vertical. Once approved, the Treasury or ALM desk becomes the operational custodian — publishing the curve, updating it as market rates and the bank's own funding cost move, and applying it uniformly so no business head can negotiate a better internal rate.

This governance role sits squarely inside the broader integrated treasury mandate, where the same desk that runs FTP also manages the investment book, the money market book, and the derivatives overlay used to hedge residual gaps. Because Treasury absorbs the interest rate risk that FTP transfers away from branches, its own structure — how the front, mid and back office divide responsibilities — has a direct bearing on how disciplined the FTP framework stays in practice; candidates preparing this chapter alongside Treasury Organisation Structure will see the two topics reinforce each other repeatedly.

Internal audit and the risk function periodically revalidate the FTP methodology — checking that curve points are still tracking the bank's actual marginal cost, that liquidity premiums are updated as regulatory liquidity requirements evolve, and that no business unit is being systematically over- or under-charged in a way that quietly subsidises one line of business at another's expense. A stale or poorly governed FTP curve is a classic red flag examiners use in scenario-based questions.

📌 Remember: ALCO approves the FTP framework; Treasury/ALM desk operationalises it; internal audit revalidates it. Keep this ownership chain straight for scenario questions.

🔗 FTP, Duration and the Wider Treasury Toolkit

FTP does not operate in isolation from the rest of the treasury syllabus. The same marginal-cost thinking that prices a loan against a curve point underlies how Treasury values and hedges its own bond book, where clean price vs dirty price of bonds and duration-based sensitivity measures determine how a rate move on the FTP curve flows through to the value of the investment portfolio. A bank that runs matched-maturity FTP is, in effect, running an internal book of notional fixed-income exposures across every tenor bucket — which is why treasury desks that are strong in bond and derivative pricing tend to run tighter FTP frameworks.

The risk that FTP concentrates at the Treasury also has to sit inside the bank's broader risk limit structure. A desk absorbing every mismatch that branches generate needs its own boundaries on how much of that risk it can retain versus hedge — which is exactly the territory covered under treasury risk limits and controls, and increasingly through instruments discussed in interest rate swaps in treasury management to hedge the residual gap that FTP has transferred onto the book. For a broader library of treasury topics, browse the Treasury Management tag archive.

🧠 Practice MCQs: Funds Transfer Pricing

Want chapter-wise mock tests with 100+ MCQs? Start practising free

❓ Frequently Asked Questions

Funds transfer pricing in banks turns a messy question — "is this branch or this loan actually profitable?" — into a clean, comparable number by making every rupee pass through an internal price. Get comfortable with the single pool versus matched-maturity distinction, the liquidity premium overlay, and the ALCO-Treasury governance chain, and this becomes one of the more reliably scoring areas of the Treasury Management syllabus. Put it to the test with a full-length mock on the CAIIB course page before exam day.