What Is Funds Transfer Pricing?
Funds transfer pricing (FTP) is the internal pricing system a bank uses to charge business units for the funds they use and to credit business units for the funds they raise. A lending desk that writes a five-year loan is charged an internal rate for the funding that loan consumes. A branch network that gathers deposits is credited an internal rate for the funding those deposits provide. Neither side transacts with the external market directly; both transact with the bank's treasury at the FTP rate.
The point of the exercise is to measure profitability honestly. Without FTP, a lending business looks profitable simply because it earns interest, and a deposit business looks like a cost centre because it pays interest. FTP separates each unit's genuine commercial margin from the funding and interest-rate position embedded in its balance sheet, and it moves that position to the one place equipped to manage it: the treasury.
FTP also shapes behaviour. If a business line pays nothing for the liquidity risk its products create, it will create too much of it. Getting the internal price right aligns each desk's incentives with the risk its activities generate for the bank as a whole. That behavioural role is exactly why regulators took a close interest in FTP after 2008, and why the topic sits in the FRM Part II syllabus.
How FTP Works: Treasury as the Internal Bank
Under an FTP framework, the treasury operates as an internal bank. Every asset a business unit books is notionally funded by a matching internal borrowing from treasury, and every liability a unit raises is notionally placed with treasury as an internal deposit. The result is a transfer-priced balance sheet in which each business unit is match-funded and the residual interest-rate and liquidity mismatch sits centrally.
A simplified example shows how the margins decompose. Suppose a branch raises a deposit paying the customer 2%, and treasury credits the branch an FTP rate of 3% for providing those funds. The deposit business earns a 1% margin for gathering funding cheaply. Suppose a lending desk writes a loan at 6%, and treasury charges it an FTP rate of 3.5% for consuming term funding. The lending business earns a 2.5% margin for its credit decision. The 0.5% between the two FTP rates stays with treasury, which carries the maturity mismatch between the two positions and the cost of managing it. (These figures are illustrative, and are chosen only to show the mechanics.)
The decomposition matters because each margin now reflects a decision the relevant unit actually controls. The deposit desk is rewarded for raising stable funding and the lending desk is rewarded for pricing credit risk well, and neither is rewarded for taking an interest-rate bet it has no mandate to manage.
FTP Methodologies: Single Pool, Multiple Pool and Matched Maturity
The FRM curriculum distinguishes three broad approaches, in increasing order of sophistication.
Single pool. One average rate applies to all funds, regardless of maturity. Users of funds are charged the pooled rate and providers of funds are credited it (in some variants the credit rate and charge rate differ, but there is still only one rate on each side). The approach is simple to run and easy to explain, and that is where its advantages end. A three-month loan and a ten-year loan are charged identical funding costs, so the system tells the bank nothing about the term liquidity each product consumes. Long-dated lending is systematically subsidised and short-dated lending is systematically penalised.
Multiple pool. Funds are grouped into buckets, typically by maturity band, and each bucket carries its own rate. A five-year asset draws from a longer-dated pool at a higher rate than a six-month asset. This captures the term structure of funding costs at a coarse level, and it remains an approximation: everything inside a bucket is treated identically, and the bucket rates are usually averages rather than marginal costs.
Matched maturity. Each transaction is assigned a transfer price built from the bank's marginal cost of funds at that transaction's own maturity and repricing profile, typically constructed from a market base curve (such as the swap curve) plus the bank's own term funding spread. A seven-year fixed-rate loan is priced against seven-year funding at origination, and that rate is locked for the life of the transaction. Matched-maturity FTP is the approach recommended in the post-crisis supervisory literature because it is the only one of the three that charges each product for the term liquidity it actually uses.
The Financial Stability Institute's guide to better practice in liquidity transfer pricing, written by Joel Grant and published by the Bank for International Settlements in 2011, is direct on this point: it describes the zero cost of funds approach as extremely poor practice that supervisors should not tolerate, and it identifies matched-maturity marginal cost as the direction banks should be moving in.
FTP and Liquidity Risk
A funding curve does more than describe interest-rate expectations. The spread a bank pays over the swap curve for term funding is a liquidity premium, and a well-built FTP system passes that premium through to the products that consume term liquidity. This is where FTP becomes liquidity transfer pricing (LTP), the framing the FRM Part II curriculum uses.
Three liquidity-related charges matter for the exam.
The term liquidity premium. Long-dated, illiquid assets should bear the cost of the long-dated funding that prudent management requires them to have. If they do not, the bank accumulates illiquid assets funded short, which is precisely the position that failed in 2007 and 2008.
Contingent liquidity. Committed credit lines, backup facilities, and other off-balance-sheet commitments consume no funding today and may consume a great deal of it in a stress, exactly when funding is scarcest. Banks hold liquidity cushions against these exposures, and holding a cushion of low-yielding liquid assets has a real carrying cost. Good LTP practice allocates that cost to the business units whose commitments make the cushion necessary. Before the crisis, most banks did not charge for contingent liquidity at all.
Regulatory ratio costs. The Basel III liquidity standards give this internal pricing a concrete anchor. Products that generate stressed outflows under the Liquidity Coverage Ratio, and assets that require stable funding under the Net Stable Funding Ratio, create funding requirements for the bank. An FTP framework that passes those costs to the originating business gives every desk an incentive to prefer LCR-friendly and NSFR-friendly business, and it does so through prices rather than through committee edicts.
Why FTP Matters in the FRM Exam
FTP sits in the Liquidity and Treasury Risk Measurement and Management section of FRM Part II, which GARP's exam study guide weights at approximately 15% of the exam. Part II consists of 80 equally weighted questions over four hours, so that weighting corresponds to roughly 12 questions across the liquidity section as a whole.
The curriculum's FTP reading is the Grant paper discussed above, and the exam tests it the way it tests most Part II liquidity material: conceptually, through scenario questions. You should be able to:
- Explain what FTP is for, and how a transfer-priced balance sheet moves interest-rate and liquidity risk to the centre
- Compare the single pool, multiple pool, and matched-maturity approaches, and identify the weaknesses of the simpler methods
- Explain how liquidity transfer pricing charges for the term liquidity premium and for contingent liquidity exposures
- Connect poor FTP practice to the pre-crisis build-up of illiquid assets and undrawn commitments
A typical question describes a bank's FTP regime and asks you to identify the flaw, or presents two products and asks which should carry the higher liquidity charge and why. Practice questions for the Liquidity and Treasury Risk unit include a dedicated Funds Transfer Pricing topic, and the unit overview page shows how FTP fits alongside the LCR, the NSFR, and the rest of the liquidity syllabus within Part II.
Common FTP Pitfalls and the Post-2008 Lessons
The clearest evidence on what goes wrong comes from a survey conducted by a group of prudential regulators in 2009, covering 38 large banks from nine countries, and analysed in the FSI paper. According to that paper, many surveyed banks lacked LTP policies altogether, employed inconsistent regimes across business lines, relied on manual off-line processes to update funding costs, and had poor oversight of the process. The most striking finding was that some banks applied a zero charge for funding liquidity on the premise that liquidity was a free good. Others used a single pooled average rate for all maturities, and liquidity cushions were frequently not linked to stress-testing outcomes.
Treating liquidity as free was rational-looking in the benign funding conditions before 2007, and it proved disastrous. Businesses originated long-dated illiquid assets and wrote large contingent commitments because the internal price of doing so was zero, and the resulting exposures crystallised together when wholesale funding markets closed.
The regulatory response was explicit. Principle 4 of the Basel Committee's Principles for Sound Liquidity Risk Management and Supervision, published in September 2008, states that a bank should incorporate liquidity costs, benefits and risks in the internal pricing, performance measurement and new product approval process for all significant business activities, both on and off balance sheet, thereby aligning the risk-taking incentives of individual business lines with the liquidity risk exposures their activities create for the bank as a whole. The Committee of European Banking Supervisors followed with dedicated Guidelines on Liquidity Cost Benefit Allocation in 2010, and in the United States the Federal Reserve, FDIC, and OCC issued interagency guidance on funds transfer pricing for funding and contingent liquidity risks in 2016, directed at firms with $250 billion or more in consolidated assets.
For exam purposes, the pitfalls reduce to a short list worth memorising: no charge for liquidity, one average rate for all maturities, no charge for contingent exposures, cushions sized independently of stress tests, and weak governance of the FTP process itself. Each of these appears in the curriculum as a named deficiency, and each is a plausible wrong-practice option in a Part II question.
Practising FTP Questions
FTP is a concept-heavy topic where the exam rewards precise understanding of why each methodology succeeds or fails, and question practice exposes the distinctions faster than re-reading does. The Liquidity and Treasury Risk practice questions on passfrm.com cover FTP alongside the LCR, the NSFR, intraday liquidity, and contingency funding planning.
If you are earlier in your FRM journey, Foundations of Risk Management practice questions are free on passfrm.com, with no account required to begin.