Foundations of Markets & Treasury

Start with the operating map, then follow the cash-flow case and control architecture. The practical workbook at the end traces an event from execution to settlement evidence.

1. Why Markets & Treasury exists

A bank is not only a collection of customer relationships. It is also a highly leveraged financial portfolio that must remain liquid, solvent and profitable every single day. Customer deposits arrive and leave according to customer needs. Loans are drawn and repaid on their own schedules. Interest rates move. Exchange rates move. Credit spreads widen and tighten. Payment systems settle in real time. Regulators demand specific ratios every reporting date. Someone must sit in the middle of all these moving parts, absorb the mismatches, manage the risks, and keep the institution alive.

That function is Markets & Treasury.

In plain language: the rest of the bank creates the raw material of the balance sheet - deposits, loans, payment flows, customer requests. Markets & Treasury turns that raw material into a coherent, risk-managed, regulated and (where possible) profitable whole. Without it, a bank is simply a set of customer promises that can collapse the moment the economic weather changes.

Retail, corporate, cards and payments create obligations at different times and in different currencies. Treasury coordinates the funding and available settlement balances; Markets executes client trades and manages market positions within its mandate. Independent Risk, Finance and Operations provide challenge and evidence that those obligations are measured and discharged.

This domain is deliberately different from retail banking, corporate banking or pure investment banking. It lives closer to the market price screens, the central bank facilities, the interbank market and the regulatory liquidity and capital rules. Its language is the language of limits, duration, value-at-risk, funds-transfer pricing, mark-to-market and contingency funding plans. Its culture is a mixture of defensive caution (Treasury) and commercial market-making (Markets). The two sit together because the risks they manage are intertwined, the systems they use are shared, and the people who understand one usually understand the other.

If you have ever wondered why a bank can look profitable on paper and still get into serious trouble, or why a large deposit can create work for people who never meet the customer, or why boards spend so much time on liquidity and interest-rate risk even when credit looks fine, this is the chapter that answers those questions.

The purpose of this foundation is to give you the mental map before we walk the territory in detail. Everything that follows - money markets, bonds, foreign exchange, interest-rate derivatives, asset-liability management, market risk limits - rests on the distinctions and principles introduced here. Master this chapter and the later material will feel like natural extensions rather than disconnected topics.

Learning objectives for this foundation

By the end of this long foundation section you should be able to:

• Explain in simple language why a bank needs a Markets & Treasury function at all.
• Distinguish the defensive mandate of Treasury from the commercial mandate of Markets and describe how they interact.
• Describe the banking book versus the trading book and why the wall between them is one of the most important control lines in the bank.
• Trace a realistic set of customer cash flows through the treasury and markets desks and show where risk is absorbed or transferred.
• List the core risk types that Markets & Treasury owns and the typical governance structures that oversee them.
• Understand the high-level organisation of a typical Markets & Treasury division and what each major desk actually does day to day.
• Recognise the key vocabulary (FTP, ALCO, LCR, NSFR, VaR, DV01, mark-to-market, contingency funding plan, and more) and use it accurately.
• Identify the classic misconceptions that cause people to misunderstand this domain.
• See how this foundation connects to every later section of the Markets & Treasury curriculum.
• Feel confident enough to read a simple desk report, an ALCO pack summary, or a market-risk limit dashboard without getting lost in jargon.

2. The two faces of the domain - Treasury and Markets

People often use the words “Treasury” and “Markets” as if they were interchangeable. They are related and frequently sit under the same senior executive, but their core purposes are different. Getting this distinction right is the single most important mental step in the whole domain.

2.1 Treasury - the bank’s internal financial manager

Treasury’s primary duty is the survival and optimisation of the bank’s own balance sheet. It is fundamentally a defensive function. Its classic responsibilities are four big jobs that never go away.

First, liquidity management. Treasury must ensure the bank has enough cash, or assets that can be turned into cash quickly and without large losses, to meet every obligation that falls due today, this week, this month and under stress. This includes daily cash positioning, management of the liquidity buffer (high-quality liquid assets), access to central bank facilities, and the maintenance of a tested contingency funding plan. Liquidity is about timing. A bank can be solvent on every accounting measure and still fail if it cannot meet cash obligations when they fall due.

Second, interest-rate risk management in the banking book. Treasury measures and controls the sensitivity of the bank’s earnings and economic value to movements in market interest rates. This is usually done through gap analysis, duration analysis, simulation of rate scenarios, and the use of interest-rate derivatives as hedges. Banks typically borrow short and lend long. Non-maturity deposits and administered-rate products do not reprice in a simple mechanical way. Someone has to own that structural mismatch.

Third, funding and investment of the structural balance sheet. When customer deposits are insufficient, Treasury raises wholesale funds. When deposits exceed lending opportunities, it places surplus funds. This includes interbank borrowing and lending, repurchase agreements, issuance of certificates of deposit and longer-term bonds, and management of the investment portfolio that serves both yield and liquidity purposes. The goal is not to maximise trading profit. The goal is to keep the balance sheet funded and resilient at a sensible cost.

Fourth, funds-transfer pricing and the internal price of money. Treasury sets the internal price at which business units “buy” and “sell” funds from the centre. This mechanism concentrates interest-rate risk in one place, makes product profitability honest, and turns Treasury into the bank’s internal central bank. Without a clean FTP framework, every business unit can claim it is profitable while the bank as a whole is taking risks that nobody owns.

A successful Treasury year is usually a quiet year. Dramatic trading profits from the Treasury desk are often a warning sign that risk has been taken outside the defensive mandate. Treasury is the function that must still be standing after a market panic, a deposit run, or a sudden tightening of wholesale funding. When people say “Treasury made a lot of money this quarter,” the next question from a good risk manager is always: “From what, and at what risk?”

2.2 Markets - the commercial and client-facing market franchise

Markets (often called Global Markets or Financial Markets) is the client execution, market-making and trading franchise. The term Capital Markets may instead refer to primary debt and equity issuance; organisation names must be read in the context of each bank. Its primary duties are different in character.

Client facilitation and market access. Markets helps corporate and institutional clients buy or sell bonds, foreign exchange, equities, interest-rate derivatives, credit products and other market instruments. The desk stands ready to quote prices and execute, providing liquidity that clients cannot easily find elsewhere. A corporate treasurer who needs to hedge a large currency exposure or an insurer that needs to buy government bonds for its portfolio both come to the Markets franchise.

Market-making. Market-makers quote bid and offer prices within their product coverage, market conditions and risk capacity. A quote is not a guarantee of executable liquidity for every size or during stress. They earn the bid-offer spread and manage the inventory risk that arises from standing ready to trade. Market-making is a service business with risk attached. The better the franchise, the more natural two-way flow the desk sees, and the less it has to warehouse risk for long periods.

Position-taking within the permitted mandate. A desk may warehouse client risk or take positions permitted by its mandate, applicable law and bank policy. An internal limit does not make a legally prohibited activity permissible. Distinguish authorised market-making and hedging from standalone proprietary trading; permitted activities vary by jurisdiction and entity.

Structuring and solutions. Markets designs more complex risk-management or investment solutions for clients - for example, interest-rate hedges that match a specific loan profile, or structured notes that deliver a particular payoff. Structuring sits at the intersection of sales, trading, quantitative analytics and legal documentation.

Markets is more commercial and more market-driven than pure Treasury. It lives closer to the price screens, the sales coverage of institutional clients, and the daily profit-and-loss account. Its success is measured in client franchise strength, market share, and risk-adjusted returns. A strong Markets franchise can be a real competitive advantage. A weak one that takes outsized risk can destroy capital very quickly.

2.3 Why the two functions sit together

Treasury and Markets may report separately, for example through the CFO and the Markets business, or through a common executive. They often share risk systems and limit frameworks, middle-office and settlement platforms, quantitative analytics and pricing models, technology infrastructure, regulatory reporting obligations, and a common risk culture and vocabulary.

The risks they manage are intertwined. A large client FX order executed by the Markets desk immediately creates a position that Treasury’s liquidity and funding desks must absorb or hedge. A sudden deposit outflow managed by Treasury may require the Markets desks to sell liquid assets or raise short-term funds. The wall between the defensive mandate and the commercial mandate is deliberately maintained by governance, but the operational reality is continuous interaction.

Think of it this way. Treasury is the bank’s immune system and balance-sheet manager. Markets is the bank’s client-facing market muscle. Both need the same nervous system (risk, systems, data, controls). Putting them under one senior leader is not about mixing mandates. It is about coordinating the parts of the bank that live closest to market prices and wholesale funding.

3. The banking book and the trading book - the most important wall

The banking-book/trading-book boundary is a prudential classification used for risk and capital. Financial accounting classification is a separate decision. Both must be documented, but they are not two interchangeable accounting regimes. This distinction prevents incorrect conclusions about valuation, capital and liquidity.

3.1 The banking book

The banking book is the set of positions outside the regulatory trading book. Customer loans and deposits are familiar examples. Investment securities and structural hedges may also belong here, subject to the applicable boundary rules. Long maturity, an accounting label or successful hedge-accounting designation does not alone determine regulatory book allocation.

Banking-book interest-rate risk is assessed through earnings and economic-value measures, alongside credit, liquidity and other risks. The bank must still monitor fair value where needed for risk, collateral, disclosure or accounting, even when an asset is measured at amortised cost. FX and commodity exposures may attract market-risk capital irrespective of regulatory book allocation; the local implementation governs the exact treatment.

3.2 The trading book

The regulatory trading book includes eligible instruments held for trading purposes, such as short-term resale, market-making or hedging trading-book risk. Eligibility, presumptions and restrictions are defined by the prudential framework. Daily valuation, active risk management and independent controls are central obligations; a desk cannot move a loss-making position into another book merely to reduce capital or conceal a loss.

Trading instruments are generally measured at fair value through profit or loss under the applicable accounting framework. This correlation is useful, but it is not a substitute for separate accounting assessment. Basel's revised market-risk framework uses a risk-sensitive standardised approach and an approved internal-model approach based on expected shortfall, including non-modellable risk factors. VaR and stressed VaR remain useful risk measures and may appear under earlier local regimes; they are not a universal description of current capital requirements. Implementation dates and scope vary by jurisdiction. Basel market-risk standard.

3.3 Why the wall matters

The boundary assigns prudential treatment and control obligations. It does not make a position economically safe. A correctly classified banking-book liquidity portfolio can still lose market value when rates rise. If assets must be sold to fund withdrawals, sale proceeds may fall short of the funding plan. Sovereign credit quality does not remove duration, market-liquidity or settlement risk.

Equally, holding a trading position longer than expected does not by itself permit moving it to the banking book. Transfers are subject to the applicable boundary rules and approval requirements. Accounting recognition and measurement must continue under the relevant framework; a change of internal desk label cannot conceal a loss.

For every position, establish the regulatory book, accounting category, purpose, risk owner and usable liquidity separately. Reconcile those classifications across trade capture, risk, Finance and regulatory reporting, and investigate changes against documented policy. This is more useful than treating the boundary as a substitute for economic risk analysis.

4. A realistic cash-flow story that shows how the pieces fit together

Abstract definitions become real when you follow money through a normal day. Consider a mid-sized commercial bank on an ordinary Tuesday. The following events occur during the morning.

A large corporate customer deposits 120 million into its main operating account after receiving a major payment from a client. Another corporate customer draws 45 million on an existing revolving credit facility and pays a supplier at another bank. A customer buys foreign currency for a cross-border transfer using 8 million of the bank's local currency. Assume the local-currency funding leg settles today; record the foreign-currency payment separately. Sixty million of short-term government securities held in the liquidity buffer mature and the cash is credited. A 35 million interbank loan that the bank had previously lent to another institution matures and is repaid. The Markets sales desk receives an order from an insurance company client to buy 75 million of five-year government bonds.

Treasury sees the net cash impact of the first five items almost immediately through the bank’s cash and liquidity systems. The arriving deposit and the repaid interbank asset increase settlement cash. The loan drawdown reduces cash only when funds leave this bank; a credit to a customer account at the same bank initially changes balances internally. Maturing securities add cash when the paying agent settles. A booked FX trade creates future currency legs, not proof of immediate external payment. Treasury therefore separates contractual flows, instructions and final settled cash.

For a numerical training view, assume all five flows settle today in one legal entity and express the local-currency amounts in millions. Ignore interest, fees and FX conversion differences in this table.

This is a change in cash, not the closing balance. Add the opening balance and all other flows, reserve requirements and intraday buffers before deciding how much is available. If the corporate deposit fails to arrive, the change is +42, not a deficit by itself. The stress case becomes a deficit only after additional outflows or a low opening balance. The insurer's 75 million bond purchase is a separate client trade: whether it affects this bank's cash depends on principal/agency execution, inventory and settlement date.

The money-market desk within Treasury places the usable surplus in approved short-term instruments, taking care not to take excessive credit or liquidity risk. At the same time the foreign-exchange desk covers the customer's transfer by buying the required currency in the market, or by using an existing position and rebalancing later. ALM assesses the deposit's concentration, contractual terms and assumed behavioural repricing and withdrawal profile. Its arrival does not automatically shorten average liability maturity; that depends on the existing portfolio and the measurement assumptions.

Meanwhile the Markets rates desk receives the insurance company’s order. The salesperson checks current inventory and market prices, shows a two-way price, and executes. The market-making desk temporarily warehouses the risk. Later in the day it may offset the position with another client, in the secondary market, or with a futures or swap hedge. The profit and loss of that trade, the market risk it creates, and the capital it consumes are all tracked under the trading-book regime.

None of these actions is visible to the branch staff or the relationship managers who originated the original customer activity. Yet every one of them is essential to the bank remaining liquid, solvent and able to serve the next customer. This continuous absorption and transfer of customer-driven risk is the daily reality of Markets & Treasury.

Now imagine the same day with one change: the large corporate deposit does not arrive, and instead several large corporates draw on facilities at once while wholesale funding markets are nervous. Suddenly Treasury is not placing a surplus. It is covering a deficit, checking the contingency funding plan, talking to the funding desk, and possibly asking Markets to help by selling liquid assets carefully. Same bank, same systems, completely different stress. That is why the function exists.

5. The core risk types owned by the domain

Markets & Treasury is paid to manage, measure, limit and, where appropriate, transfer a set of risks that sit at the heart of the bank’s survival. Understanding each risk type in plain language is more important than memorising formulas on day one.

Liquidity risk is the risk that the bank cannot meet its cash obligations when they fall due without incurring unacceptable losses or damaging its franchise. It includes intraday liquidity, overnight and short-term liquidity, and structural liquidity over months and years. It is managed through buffers of high-quality liquid assets, diversified funding, contingency plans and regulatory ratios such as the Liquidity Coverage Ratio and the Net Stable Funding Ratio. Liquidity risk is often the silent killer. It does not always announce itself with a big market move. It announces itself when the bank needs cash and cannot get it at a reasonable price, or at any price.

Interest-rate risk in the banking book (IRRBB) is the risk that movements in market interest rates change the bank’s net interest income or the economic value of its banking-book equity. It arises because the bank borrows short and lends long, and because non-maturity deposits and administered-rate products do not reprice in a simple mechanical way. It is measured by gap analysis, duration analysis, earnings-at-risk and economic-value simulations, and is managed by portfolio construction and interest-rate derivatives. IRRBB is not the same as trading interest-rate risk. It lives in the banking book and is governed through ALCO, not through daily trading limits alone.

Market risk is the risk of loss from movements in market prices, including interest rates, foreign-exchange rates, equity prices, commodity prices and credit spreads. Such economic exposure can exist in either regulatory book. Its prudential capital scope is a separate question. It is measured through sensitivities such as DV01, CS01, delta, gamma and vega, portfolio measures such as VaR or expected shortfall, and stress scenarios. The chosen internal measures and applicable capital regime must be identified. Limits and independent oversight apply; accounting measurement determines how a change appears in P&L or other comprehensive income.

Credit risk on market instruments includes the risk that a counterparty fails to perform on a derivative, repo or securities-financing transaction, and the risk that an issuer of a bond held in the trading or investment portfolio defaults or suffers a sharp widening of credit spreads. Counterparty credit risk is mitigated by collateral, netting, central clearing and credit limits. Issuer credit risk is managed by issuer limits, rating constraints and portfolio diversification. Even “safe” market instruments carry credit dimensions that must be owned.

Funding risk, or refinancing risk, is the risk that the bank cannot roll its wholesale funding at reasonable cost or, in extreme cases, at any cost. It is managed by lengthening the maturity profile of wholesale liabilities, diversifying funding sources and maintaining strong relationships with investors and interbank counterparties. A bank that depends too heavily on short-term wholesale money is living on a shorter fuse than its accounting statements sometimes reveal.

Operational risk on the Markets & Treasury side includes settlement failures, trade capture errors, system outages, model failures, unauthorised trading and people risk on the dealing floor. Controls include dual input, independent confirmation, reconciliation, access rights, and a strong conduct and compliance culture. One wrong trade booking or one failed settlement can create outsized pain.

Model risk is the risk that the pricing models, risk models or valuation adjustments used by the desks are incorrect or are used outside their valid range. Independent model validation, regular back-testing and conservative valuation adjustments are the main mitigants. Models are tools. They are not the truth. Treating them as the truth is a classic source of large losses.

Regulatory and conduct risk covers breaches of position limits, reporting rules, market-abuse regulations, best-execution obligations or capital and liquidity requirements. This is managed by compliance monitoring, surveillance systems, and a clear escalation culture. In modern markets businesses, conduct is not a soft topic. It is a hard control.

A well-run Markets & Treasury division has explicit limits, independent monitoring, and clear escalation paths for each of these risks. The desk that generates the risk does not set its own limits. Risk management and the Board’s risk committee do. That separation of duty is not bureaucracy. It is survival architecture.

6. Typical organisation of a Markets & Treasury division

While every bank is different, a common high-level structure helps you know who does what when you hear desk names in conversation or see them on an organisation chart.

On the Treasury side you will typically find a Liquidity and Funding desk that handles daily cash positioning, short-term interbank and repo activity, and contingency planning. An Asset-Liability Management or Interest-Rate Risk desk runs gap analysis, structural hedging and ALCO support. An Investment Portfolio or Liquidity Buffer team manages government and high-quality securities held for liquidity and yield. A Funds-Transfer Pricing team constructs the internal curve and supports product pricing. Capital management is often shared with Group Finance.

On the Markets side you will typically find Rates (government bonds, interest-rate swaps, futures, options, money-market instruments), Credit (corporate bonds, credit default swaps, credit indices), Foreign Exchange and Local Markets (spot, forwards, swaps, options, emerging-market currencies), and in some banks Equities and Equity Derivatives or Commodities. Sales and Institutional Coverage manages relationships with corporates, asset managers, insurers, hedge funds and other banks. Structuring designs more complex client solutions. Research and Strategy provide macro, rates, credit and FX views that support both clients and the trading desks.

Shared support functions are critical. Trade support, Middle Office and Operations divide validation, confirmation, affirmation, settlement instruction and collateral tasks according to each bank's operating model; department labels do not establish independence. Market Risk monitors limits, VaR, stress testing and independent risk reporting. Product Control and Valuations perform independent price verification, P&L explain and valuation adjustments. Quantitative Analytics builds and maintains models. Technology runs the trading platforms. Compliance, Conduct and Surveillance watch behaviour and rules. Legal and documentation own the agreements that make the trades enforceable - ISDA, CSA, GMRA and related documents.

Reporting lines vary. In some banks the Treasurer reports to the CFO and Markets reports to a Markets CEO. In others both report to a single Markets & Treasury head who sits on the executive committee. What matters is that the defensive Treasury mandate is never subordinated to short-term Markets P&L pressure, and that independent risk and control functions have a direct line to senior management and the Board.

When you meet someone from “Rates,” “ALM,” “Funding,” “FX Sales,” or “Product Control,” you should now be able to place them on this map and understand roughly what problem they own.

7. Core vocabulary you will meet every day

Markets & Treasury has its own everyday language. You do not need every formula on day one, but you do need to become comfortable with the concepts so that conversations, reports and limit breaches make sense.

P&L means profit and loss. For trading books it is calculated daily. For the banking book it is calculated over longer periods and in different ways. When someone says “the desk is up two million today,” they are talking about mark-to-market P&L on the trading book unless they specify otherwise.

Mark-to-market means valuing a position at the current observable market price. It is the honesty mechanism of the trading book. It is also why trading losses appear quickly and why trading profits can reverse quickly.

VaR, or Value at Risk, is a statistical estimate of potential loss over a given time horizon at a given confidence level. Stressed VaR is VaR calibrated to a period of significant market stress. VaR is widely used and widely criticised. It is a tool, not a complete picture. Good risk frameworks use VaR alongside sensitivities and stress scenarios.

DV01 or PV01 expresses value sensitivity to a one-basis-point interest-rate change. Desks may report a positive magnitude or a signed sensitivity; identify the convention, curve and bump direction before aggregating it. CS01 is the change in value for a one-basis-point move in credit spreads. These sensitivity measures are the daily language of rates and credit desks. When a risk manager asks for the DV01 of a position, they want a simple, comparable number for interest-rate exposure.

Limit means the maximum risk a desk or portfolio is allowed to take. Hard limits cannot be exceeded without escalation. Soft limits may trigger discussion. Living without clear limits is how desks get into trouble.

Hedge means a position taken to offset or reduce another risk. Hedges are rarely perfect. Basis is the difference between two related rates or prices that do not move in perfect lockstep. Basis risk is the risk that remains after an imperfect hedge.

Notional is the face amount of a derivative contract on which payments are calculated. A large notional does not always mean a large risk, but it is still a number that must be understood and controlled.

Collateral or margin means assets posted to secure a derivative, repo or securities-financing exposure. Collateral reduces counterparty credit risk but creates its own operational and liquidity demands.

Settlement is completion of the transfer of cash or securities under the relevant system and legal rules. The intended value date is not proof of final settlement. Principal settlement risk arises when one party delivers value but does not receive the corresponding value; replacement-cost and liquidity risks can remain even where linked settlement prevents principal loss.

ALCO is the Asset-Liability Committee, the senior body that oversees banking-book interest-rate risk, liquidity and funding strategy. ALCO is where structural decisions are debated and owned.

FTP, or Funds Transfer Pricing, is the internal price at which Treasury buys deposits from and sells funds to the business units. Clean FTP makes product profitability honest and concentrates interest-rate risk where it can be managed.

LCR, or Liquidity Coverage Ratio, is the regulatory requirement to hold enough high-quality liquid assets to survive a 30-day stress scenario. NSFR, or Net Stable Funding Ratio, is the regulatory requirement to maintain stable funding over a one-year horizon. Together they form the core of post-crisis liquidity regulation.

Contingency Funding Plan is the pre-written and regularly tested playbook for raising cash in a liquidity emergency. A plan that exists only on paper is not a plan. Testing and governance matter as much as the document.

Banking book and trading book are prudential book classifications. Accounting measurement is assessed separately. The first question about any position is still: which book does it sit in?

Mastery of this vocabulary is practical, not academic. When a risk manager asks “what is the DV01 of the position and which book does it sit in?”, a clear answer is expected. When an ALCO pack mentions LCR, NSFR and FTP, you should know what problem each one is trying to solve.

8. Common misconceptions that cause lasting confusion

Several misconceptions keep reappearing in conversations with people who are new to this domain. Clearing them early saves years of confusion.

“Treasury is just the department that invests the bank’s spare cash.” Investing surplus cash is only one of its jobs, and often the least critical on a stressed day. Liquidity survival, interest-rate risk control and funding resilience come first. On a quiet day Treasury may look like an investment function. On a stressed day it looks like the bank’s emergency services.

“Markets is the same as investment banking.” Investment banking - mergers and acquisitions, equity capital markets, debt capital markets origination - is a different franchise. Markets is the secondary-market trading, sales, market-making and risk-management side. The two may sit near each other organisationally in some banks, but the jobs, the risks and the cultures are different.

“If the trading desks are making money, the bank must be healthy.” Trading profits can coexist with a deteriorating liquidity position, an unhedged structural interest-rate exposure, or an over-reliance on short-term wholesale funding. The two must be examined separately. A good year in Markets does not automatically mean a safe year for the balance sheet.

“Regulators only care about capital.” Since the 2008 crisis, liquidity regulation - LCR, NSFR, intraday liquidity monitoring, contingency funding plans - has become at least as important as capital for the Treasury function. A solvent bank can still fail if it cannot meet cash obligations when they fall due. Capital is about loss absorption. Liquidity is about timing.

“Everything can be perfectly hedged.” Many risks can only be reduced, not eliminated. Basis risk, the behavioural uncertainty of non-maturity deposits, gap risk around rate-fix periods, and the possibility of market freezes remain even after the best available hedges. Risk management is about understanding residual risk, not pretending it is zero.

“A profitable bank cannot have a liquidity problem.” Profitability is about values over time. Liquidity is about timing tomorrow morning. A bank can be solvent on every accounting measure and still be unable to pay its obligations if assets cannot be converted to cash fast enough. History has repeated this lesson more than once.

“Government bonds are always safe.” Major sovereign bonds are often treated as high-quality assets, but sovereign default, restructuring and convertibility risk are not universally zero. They also carry interest-rate risk. Long-duration government bonds can generate large mark-to-market losses when rates rise, and those losses become real if the bonds have to be sold to meet liquidity needs. Safety has more than one dimension.

“ALCO is just another committee.” ALCO is where the bank decides how much structural interest-rate risk and liquidity risk it is willing to run, and how it will fund itself over time. Weak ALCO governance is a leading indicator of balance-sheet trouble. Strong ALCO governance is quiet, boring and invaluable.

9. Governance, culture and why culture matters

Markets & Treasury does not run on models alone. It runs on governance and culture.

Independent risk management must have the authority to say no, or at least to escalate clearly, when desks want to take risk outside appetite. Product Control must be able to challenge valuations without fear. Compliance and conduct surveillance must be real, not decorative. Internal audit must be able to test controls without being captured by the business.

Culture shows up in small behaviours. Does a desk escalate a limit breach immediately or try to “manage it overnight”? Does a salesperson protect the client and the bank, or only the trade? Does Treasury report bad liquidity news early or late? Does senior management reward quiet resilience as much as visible P&L?

The best Markets & Treasury organisations treat defensive excellence as a first-class outcome. They do not apologise for a quiet Treasury year. They do not celebrate Markets revenue that was earned by taking risks the Board did not understand. They keep the banking-book and trading-book wall honest. They test the contingency funding plan. They make FTP real. They invest in people who can explain risk in plain language to non-specialists.

If you are building a career in this domain, learn the technical tools, but also learn the governance and the culture. Technical skill without judgement is dangerous. Judgement without technical skill is incomplete. The combination is what the bank actually needs.

10. How this foundation connects to the rest of the curriculum

This chapter is the map. The remaining sections of the Markets & Treasury curriculum walk the territory in full operational detail.

Bank Treasury and Liquidity Management expands the pure defensive disciplines: daily cash positioning, liquidity buffers, LCR and NSFR mechanics, contingency funding, and the practical operation of the Treasury desk. You will see how a day is actually run, what reports matter, and how stress is handled.

Money Markets shows where short-term cash is placed and raised every day and how the interbank and repo markets actually function. This is the plumbing of wholesale liquidity.

Fixed Income and Bond Markets covers both the liquidity portfolio and the major client and trading franchise in government and corporate bonds. Duration, DV01, yield curves and client flow all become concrete.

Foreign Exchange sits at the intersection of customer flows, market risk and the bank’s own multi-currency balance sheet. Spot, forwards, swaps and the management of FX risk for the bank itself are covered in depth.

Interest-Rate and Credit Derivatives are the primary tools used to transfer risks that the bank does not want to keep. Swaps, futures, options and credit derivatives are explained as practical risk tools, not as abstract contracts.

ALM, FTP and Balance-Sheet Management are the pure Treasury disciplines that turn the customer balance sheet into a managed portfolio and set the internal price of money. This is where structural decisions live.

Market Risk, Limits and Controls is the independent control framework that keeps the whole machine inside the Board’s risk appetite. VaR, stresses, limits, escalations and independent oversight are the focus.

Later sections on organisation, career paths and case studies show how the theory appears in real desk life and in major historical episodes. Those stories only make sense if the distinctions in this foundation are solid.

11. Extended key takeaways

1. Markets & Treasury exists because a bank is itself a leveraged financial portfolio that must be managed continuously, not only a set of customer relationships.
2. Treasury is primarily defensive and balance-sheet focused. Markets is primarily commercial, client-facing and trading focused. The two sit together because their risks and systems are intertwined.
3. The regulatory banking-book/trading-book boundary assigns prudential treatment and control obligations. Assess accounting classification separately; neither classification removes economic risk.
4. Liquidity risk, interest-rate risk in the banking book, market risk, counterparty and issuer credit risk, funding risk and operational risk are the core risks this area owns.
5. Good governance deliberately separates the “keep the bank alive” mandate from the “make money in the markets” mandate and gives independent risk and control functions real authority.
6. Every material customer deposit, loan drawdown, payment and market order ultimately creates a position that lands on a Markets or Treasury desk.
7. The daily language of limits, VaR, duration, mark-to-market, FTP and contingency planning is the operating system of the domain.
8. A quiet, well-controlled year in Treasury is usually a successful year. Dramatic profits from the defensive functions are often a warning sign.
9. Liquidity is about timing. Solvency is about value. A bank can be solvent and still fail if it cannot meet cash obligations when they fall due.
10. Government bonds can be credit-safe and still dangerous from an interest-rate and liquidity perspective if duration and forced-sale risk are ignored.
11. ALCO, FTP, LCR and NSFR are not bureaucratic decorations. They are the practical tools through which the bank manages structural survival.
12. This foundation is the map. The remaining sections of the Markets & Treasury curriculum walk the territory in full operational detail. If the map is clear, the journey is much easier.

12. A day in the life of Treasury - what “defensive” actually looks like

It is 7:15 on a weekday morning. The Liquidity and Funding desk is already looking at overnight cash positions, expected maturities, large known payments, and any news that could affect wholesale funding or central bank operations. The first job is not to make money. The first job is to understand whether the bank will end the day with a surplus or a deficit, and whether that position is normal or stressed.

Through the morning, corporate deposits arrive, loan drawdowns hit, payment flows settle, and maturing money-market deals roll off or are renewed. Each flow changes the cash position. The desk places surplus funds carefully - not chasing the last basis point of yield if it means taking the wrong credit or liquidity risk - or covers a deficit through interbank borrowing, repo, or other approved channels. Everything is done inside limits and with an eye on the regulatory liquidity ratios.

Later in the day the ALM team reviews rate moves and the shape of the structural gap. If the bank has more rate-sensitive liabilities than assets in a certain tenor, a rise in rates may compress net interest income. If the opposite is true, the picture is different. The team may recommend adjusting hedges, changing the investment portfolio mix, or simply documenting the risk for the next ALCO. None of this is glamorous. All of it is essential.

In the background, the Contingency Funding Plan sits ready. It is not opened every day. It is tested on a schedule. It lists who can be called, which assets can be sold or repo’d, which central bank facilities exist, and in what order actions should be taken if retail or wholesale funding becomes difficult. A plan that has never been tested is a hope, not a control.

By evening the cash position is square or intentionally left with a small, understood residual. Reports are updated. Exceptions are escalated. Tomorrow the cycle starts again. That is the defensive mandate in practice: continuous, disciplined, mostly invisible work that keeps the bank able to open its doors.

13. A day in the life of Markets - what “commercial” actually looks like

On the same morning, a Rates salesperson is preparing for a call with an insurance company client that needs to buy a block of government bonds to match long-dated liabilities. The salesperson checks inventory, current market levels, recent flow, and the desk’s risk capacity. A two-way price is shown. The client lifts the offer. The trade is booked. Market risk now sits with the bank until it is offset, hedged, or run off within limits.

Across the floor, an FX desk is covering corporate client flows - exporters selling foreign currency, importers buying it, and internal treasury requests related to the bank’s own multi-currency balance sheet. Each ticket is small relative to the whole bank, but the aggregate flow is large. The desk earns spread from facilitation and manages residual risk with care.

A credit trader is watching spreads and client enquiry in corporate bonds. A structurer is working with a corporate treasurer on an interest-rate hedge that matches the schedule of a floating-rate loan. Middle Office is confirming trades. Product Control is preparing the P&L explain. Market Risk is monitoring VaR and sensitivity limits. Compliance is watching for unusual patterns.

The commercial mandate is real work with real clients and real P&L. It is also real risk. The difference between a strong Markets franchise and a dangerous one is not only revenue. It is the quality of risk discipline, the honesty of mark-to-market, the clarity of limits, and the culture that escalates problems early.

When Markets and Treasury work well together, client flow is facilitated, the bank’s own balance sheet is protected, and risk is visible. When they work poorly - when defensive controls are weak or commercial pressure overrides governance - the bank becomes fragile even if the month’s revenue looks good.

14. How an ALCO decision actually feels

ALCO is not a theatre. It is a working committee. A typical pack includes the liquidity position and outlook, LCR and NSFR trends, structural interest-rate risk metrics, funding plan updates, significant market moves, and any breaches or near-breaches of internal limits. Members include the Treasurer, ALM, Funding, Finance, Risk, and often business representatives.

A decision might look like this. The ALM team reports that a large shift in non-maturity deposit behaviour has lengthened the effective duration of liabilities less than previously assumed. Net interest income sensitivity to a rate cut has increased. Options include doing nothing and accepting higher earnings volatility, adjusting the investment portfolio, or adding hedges. Each option has a cost and a residual risk. ALCO debates, decides, and records the decision with owners and review dates.

Another decision might concern wholesale funding. A planned bond issuance could be brought forward because markets are open and the bank wants to pre-fund. Or it could be delayed because pricing is unattractive and short-term funding remains available inside appetite. The point is not that there is one correct answer. The point is that structural choices are owned, documented, and revisited.

If you ever sit in an ALCO, listen for three things: Is liquidity discussed with the same seriousness as P&L? Is residual risk after hedges acknowledged? Are decisions written down with clear owners? Those three signals tell you more about the bank’s true risk culture than any single slide.

15. Lessons history keeps teaching this domain

Educational history in Markets & Treasury is not about drama for its own sake. It is about patterns that repeat when the same mistakes are made.

When funding is too short-term and too concentrated, a loss of confidence can become a liquidity crisis faster than capital ratios suggest. When long-duration securities are treated as “safe” without regard to interest-rate risk and forced-sale risk, paper losses become real losses at the worst moment. When trading positions are allowed to sit without honest mark-to-market and hard limits, losses compound in the dark. When ALCO is weak, structural mismatches grow until they are expensive to fix. When conduct and controls are treated as secondary to revenue, the franchise itself becomes a risk.

The constructive lesson is simple. Liquidity, structural interest-rate risk, trading-book discipline, and governance are not optional extras. They are the core of the job. Banks that treat them as core tend to survive bad weather. Banks that treat them as paperwork tend to learn the hard way.

16. How to read a simple desk or risk view without panic

You do not need to be a quant to read a basic Markets & Treasury report with intelligence. Start with four questions.

What book is this position in - banking or trading? What is the main risk factor - rates, FX, credit spread, liquidity timing, or something else? What is the size of the sensitivity (for example DV01) or the limit utilisation? What would make this position painful - a rate shock, a funding freeze, a client default, an operational failure?

If you can answer those four questions, you are already thinking like someone who belongs in the conversation. The formulas and systems come later. The questions come first.

17. Self-check - have the foundations landed?

Try to answer these in plain language, without looking back.

1. Why does a bank need Markets & Treasury at all, in one or two sentences?
2. What is the difference between Treasury’s mandate and Markets’ mandate?
3. What is the banking book versus the trading book, and why does the wall matter?
4. Name four core risks this domain owns and one sentence on how each is managed.
5. What do LCR, NSFR, FTP, ALCO, VaR and DV01 each try to do?
6. Why can a profitable bank still have a liquidity problem?
7. Why are government bonds not automatically “safe” for a liquidity portfolio?

If you can answer most of these clearly, the foundation has landed. If some answers are still fuzzy, re-read the matching section. This material is meant to be learned, not skimmed once.

18. Final picture and what comes next

Picture the bank as a large ship. Retail and corporate businesses load and unload cargo every day - deposits, loans, payments, client requests. The ship must stay upright, stay fuelled, and stay able to enter port even in bad weather.

Treasury is the team that watches the ballast, the fuel, the weather forecasts, and the emergency drills. Markets is the team that trades with other ships and ports, earns from facilitation, and sometimes takes controlled positions when the rules allow. Both teams share the same navigation instruments, the same radio, and the same responsibility not to sink the vessel.

You now have the map of that ship’s critical systems. In the next chapters we open each system in turn - liquidity, money markets, bonds, FX, derivatives, ALM, risk limits - and learn how they actually work in real banks, in clear human language, with the same practical focus you have seen here.

When you finish this foundation, you should be able to explain to a smart non-specialist why Markets & Treasury exists, what the main risks are, why the banking book and trading book must stay separate, and what a normal day of cash flows looks like behind the scenes. That ability is the true test of whether the foundation has landed.

19. The regulatory spine behind Markets & Treasury

Markets & Treasury is not built only from bank habit or desk tradition. It is shaped very strongly by regulation, especially the post-2008 Basel framework. That does not mean every learner must become a regulatory specialist before understanding the domain. It means the learner must know which regulatory ideas sit behind normal desk language. When a treasurer talks about HQLA, survival horizon, funding concentration, stress outflows, available stable funding, required stable funding, IRRBB, market-risk capital or trading-book boundaries, those are not private words invented by one bank. They are connected to supervisory expectations that have been formalised over many years.

The Liquidity Coverage Ratio is one of the cleanest examples. Basel introduced the LCR to promote short-term liquidity resilience by requiring banks to hold an adequate stock of unencumbered high-quality liquid assets that can be converted into cash to meet liquidity needs during a 30-day stress scenario. In practical bank language, this changed Treasury conversations permanently. Before the post-crisis reforms, many institutions paid too much attention to accounting liquidity and cheap wholesale funding, and too little attention to whether cash could actually be raised under stress. The LCR forced banks to ask a harder question: if markets are stressed, depositors are nervous, committed facilities are drawn and unsecured funding becomes difficult, do we still have enough truly usable liquidity for the next month?

That is why the word HQLA matters. High-quality liquid assets are not simply assets with good credit ratings. They must be usable. A government bond may be credit strong, but if it is encumbered, pledged, stuck in the wrong legal entity, held in the wrong custodian, missing from the collateral system, or operationally impossible to monetize quickly, it is not useful in the way a liquidity manager needs. The LCR therefore connects regulation with systems, custody, collateral, legal entity management, stress assumptions and day-to-day operational readiness. It also changes behavior. A bank that wants to grow balance-sheet activity must think about the liquidity outflow and HQLA impact of that growth.

The Net Stable Funding Ratio looks at a longer horizon. The NSFR is designed to promote a more stable funding profile by comparing available stable funding with required stable funding over a one-year horizon. The principle is simple but powerful: long-term or illiquid assets should not be funded too heavily by fragile short-term liabilities. A bank can survive today with enough cash and still be structurally fragile if it depends on funding that can disappear quickly. NSFR pushes banks to think about the quality and stability of funding, not only the amount. Equity and long-term debt are more stable than overnight wholesale money. Retail transactional balances may be more stable than hot institutional balances. Long-dated loans and illiquid assets require more stable funding support than short-term liquid assets.

IRRBB, or Interest Rate Risk in the Banking Book, gives the other major regulatory backbone for Treasury. The Basel standards on IRRBB recognise that changes in interest rates can affect both the bank's earnings and the economic value of its banking-book positions. This is not trading risk. It arises from deposits, loans, securities held outside the trading book, administered-rate products, prepayment options and balance-sheet structure. When rates move sharply, a bank with large structural mismatches can suffer even if credit losses are low. The 2022-2023 rate environment taught many people this lesson in a very practical way. Deposits repriced differently from assets. Securities portfolios lost market value. Customers changed behaviour. Treasury and ALM functions had to prove whether their assumptions were still honest.

Market-risk capital standards shape the trading side. Basel's market-risk framework, including the Fundamental Review of the Trading Book, reflects the need for trading-book risks to be captured more robustly, especially under stress and for less liquid positions. Again, the important foundation point is not to memorise every capital formula. The important point is that trading activity consumes capital, requires risk sensitivity, demands clear book classification, and must be supported by independent valuation, limit control and stress measurement. A Markets desk that looks profitable before capital and risk costs may look very different after those costs are recognised.

For a business analyst or product owner, these regulatory anchors translate into concrete questions. Does the product create cash outflows under LCR? Does it require stable funding under NSFR? Does it create structural interest-rate risk in the banking book? Does it belong in the trading book or banking book? Does it need fair value measurement? Does it feed market-risk systems? Does it affect regulatory reporting? Does it require collateral data? Does it create liquidity stress under customer behaviour assumptions? Good requirements in this domain are impossible without these questions.

The official Basel sources should be used as anchors, not as decoration. The Basel LCR framework explains the purpose of short-term liquidity resilience and HQLA. The Basel NSFR framework explains stable funding over a longer horizon. The Basel IRRBB standard explains why banking-book interest-rate risk is a board-level discipline. The Basel market-risk framework explains why trading-book capital and risk measurement cannot be casual. A learner who understands this regulatory spine will read a Treasury pack with far more confidence because the pack will stop looking like a collection of acronyms and start looking like a survival architecture.

20. How the balance sheet creates Treasury work before any trader appears

Many people think Markets & Treasury starts when a dealer looks at a price screen. In a commercial bank, the work starts much earlier, inside the ordinary customer balance sheet. A bank accepts deposits, grants loans, processes payments, issues guarantees, provides credit facilities, invests surplus cash, raises wholesale funding and holds securities. Every one of these activities changes the shape of assets, liabilities, cash flows, currencies, maturities, repricing dates and optionality. Treasury work is born from that shape.

Start with deposits. A current account balance looks simple to a customer. To Treasury it is a liability that can leave, stay, grow, shrink, reprice, behave differently by segment and become concentrated in a few large names. Retail operating balances may be sticky in normal times. A large corporate balance may move in one payment instruction. A financial-institution deposit may be highly rate sensitive. A digital savings product may attract money quickly when the rate is high and lose it quickly when competitors reprice. The bank must decide how much of each deposit category is stable enough to fund assets, how much liquidity buffer is needed against possible outflows, and how the business should be internally credited through FTP.

Loans create the other side. A mortgage, an overdraft, a corporate term loan and a revolving credit facility all create different treasury problems. A mortgage may be long term and fixed rate. A corporate term loan may reprice every few months. A revolver may be undrawn today but drawn tomorrow under stress. An overdraft may behave like a flexible liquidity source for the customer but like an uncertain asset for the bank. Treasury and ALM need to know not just current outstanding amount, but contractual maturity, repricing date, behavioural life, prepayment risk, currency, margin, product type, customer segment and drawdown commitment.

Payments create intraday pressure. A bank can have a fine end-of-day liquidity position and still face intraday liquidity stress if outgoing payments hit before incoming payments arrive. Real-time payment systems and instant schemes make this more important. In older batch worlds, banks had more time to manage flows. In real-time environments, liquidity moves continuously. A large corporate payroll file, a securities settlement batch, a central-bank payment and retail instant payments can all affect cash during the day. Treasury therefore needs payment-flow visibility, not only general ledger balances after close.

Securities portfolios create both protection and risk. A bank holds high-quality securities for liquidity, collateral and yield. The same portfolio can protect liquidity and create interest-rate risk. If rates rise, the market value of fixed-rate securities falls. If the bank can hold the securities and they remain eligible collateral, the loss may remain unrealised for accounting purposes. But if the bank must sell securities to meet cash outflows, the loss becomes real. This is why liquidity management and interest-rate risk cannot be separated. The asset that saves liquidity may damage capital if sold at the wrong time.

Wholesale funding adds another layer. A bank may issue certificates of deposit, commercial paper, covered bonds, senior unsecured debt, subordinated debt or capital instruments. Each instrument has a maturity, investor base, currency, cost, covenant, rating sensitivity and rollover risk. Funding is not only about finding money today. It is about building a maturity ladder that does not create cliffs. A bank that has too much debt maturing in one month has created a future funding event. A bank that relies too much on one investor segment has created concentration risk. A bank that funds long assets with very short liabilities has created structural vulnerability.

Derivatives appear because the raw balance sheet rarely has the risk profile the bank wants. Interest-rate swaps may help hedge fixed-rate loans or securities. FX swaps may help manage currency funding. Futures may help hedge government-bond duration. But derivatives do not remove the need for governance. They introduce valuation, collateral, counterparty, accounting and operational requirements. A hedge can reduce one risk while creating another. That is why Treasury cannot be a pure execution desk. It must be a balance-sheet-thinking function.

The key foundation point is this: Treasury does not invent work. The balance sheet creates it. Customers create deposits and loans. Payment systems create timing. Markets create prices. Regulators create ratios. The board creates risk appetite. Treasury sits in the middle and turns all of that into a controlled position.

21. Funds Transfer Pricing as the hidden language of product profitability

Funds Transfer Pricing is one of the most important ideas in bank management and one of the least understood outside Treasury, ALM and Finance. It is the internal pricing mechanism that tells business units what their funding really costs or what their deposits are really worth. Without FTP, a bank can fool itself. A lending team may think a product is profitable because the customer rate is higher than the visible accounting cost. A deposit team may think it is unattractive because the customer pays low fees. Treasury sees the deeper truth: the loan consumes funding and liquidity; the deposit may provide stable funding and reduce wholesale funding need.

Imagine a business unit writes a five-year fixed-rate loan. The customer pays interest. The business unit sees revenue. But the bank must fund that asset for five years or manage the risk that funding costs will change. Treasury therefore charges the business an internal five-year funding rate, possibly with liquidity premium and optionality cost. If the product margin is still attractive after that charge, the business is genuinely profitable. If not, the product was relying on free funding that did not really exist.

Now imagine a retail bank gathers stable current-account balances. The customer rate may be low or zero. From a pure product income view, the account may look modest. But stable deposits can be valuable because they provide funding to the bank. FTP may credit the business for bringing that stable liability. The credit should reflect behavioural life, stability, rate sensitivity and regulatory value. A deposit that stays through stress is not the same as a large hot-money balance that leaves the moment another bank offers a better rate.

FTP therefore changes behaviour. If long-term loans are charged correctly, business units price them more honestly. If unstable deposits receive lower FTP credit, business units understand that volume alone is not quality. If currency funding is expensive, products in that currency must reflect it. If liquidity premiums rise, FTP can transmit that cost to the front line before the bank grows into a dangerous position.

A poor FTP framework creates bad incentives. Business units may chase products that look profitable locally but damage the bank centrally. Treasury may absorb risks without the originating business feeling the cost. Product managers may underprice long-term fixed-rate loans in a rising-rate environment. Relationship managers may bring in large deposits that look impressive but are expensive or unstable. FTP exists to prevent these distortions.

For a BA, FTP should be treated as a business rule engine with serious consequences. The key data includes product type, currency, tenor, behavioural maturity, repricing frequency, optionality, customer segment, legal entity, funding curve, liquidity premium, capital or regulatory adjustment where applicable, and effective date of the curve. Requirements should define when FTP is calculated, when it is locked, how changes are versioned, how exceptions are approved, how product profitability receives the result, and how Finance reconciles the internal charge.

Testing FTP needs more than one happy path. Test a new fixed-rate loan, a floating-rate loan, a deposit with behavioural maturity, a product with early repayment option, a multi-currency product, a repricing event, an FTP curve update, a backdated correction, a product mapping error and a profitability report reconciliation. If a product moves from one FTP bucket to another, the bank should know why. If an FTP curve changes, historical profitability should not be silently rewritten unless the policy explicitly says so.

FTP is the hidden language of product profitability because most customers never see it and many front-line teams only feel its output. But inside a bank, it is one of the few mechanisms that turns balance-sheet reality into business behaviour. When FTP is strong, growth becomes more intelligent. When FTP is weak, growth can become a beautiful-looking risk problem.

22. ALCO as the governance room where balance-sheet truth is tested

The Asset Liability Committee is often mentioned casually, but in a serious bank it is one of the most important governance rooms. ALCO is where Treasury, ALM, Finance, Risk and business leadership test the truth of the balance sheet. The committee does not exist to admire dashboards. It exists to make decisions about liquidity, funding, structural interest-rate risk, FTP, deposit strategy, investment portfolio positioning, hedging and contingency readiness.

A good ALCO pack should tell a connected story. What changed since the last meeting? Did deposits grow or shrink? Which customer segments changed? Did wholesale funding spreads widen? Are there funding maturities coming due? Did the LCR and NSFR move materially? Did interest-rate risk increase? Did hedge effectiveness change? Are there concentration risks? Are there limit breaches or early-warning triggers? Are there material assumptions that need approval? Which decisions are needed now?

The best ALCO conversations do not hide uncertainty. Deposit behaviour is uncertain. Loan prepayments are uncertain. Customer drawdowns are uncertain. Market access is uncertain under stress. Rate pass-through is uncertain. The committee should understand the assumptions and their weakness. A pack that reports one neat number without sensitivity or challenge can create false comfort. A strong pack says: this is the base case, this is the stress, this is what would hurt us, this is what we can do, this is what we recommend.

ALCO also owns time. Some balance-sheet risks build slowly and then appear suddenly. A large concentration of wholesale funding maturing in six months may not be a crisis today, but it is a decision today. A growing fixed-rate loan book may not hurt earnings this month, but it may create sensitivity to future rate moves. A deposit campaign may be successful commercially but change funding composition. ALCO must see these effects before they become urgent.

Decision quality matters as much as measurement. If ALCO approves a hedge strategy, the decision should state the purpose, instrument type, risk being hedged, limit impact, accounting intention, owner, implementation timing and review trigger. If ALCO approves a funding issuance plan, it should record target tenor, currency, investor base, size, fallback options and market-window dependency. If ALCO changes FTP methodology, the committee should understand business impact and transition handling.

For a learner, ALCO is where the defensive philosophy becomes visible. Does the bank talk honestly about uncomfortable liquidity signals? Does Risk challenge Treasury? Does Treasury challenge business growth? Does Finance reconcile numbers back to official books? Does senior management make clear decisions? Do actions from the last meeting actually close? These questions show whether ALCO is a real control or a calendar ritual.

In system terms, ALCO depends on data lineage. A liquidity ratio reported to ALCO may start in core banking, payment systems, trade systems, securities systems, collateral systems, GL, market data and manual overlays. If source-to-report lineage is weak, the committee may debate a number that nobody can defend. This is why ALCO reporting projects are not just reporting projects. They are data-governance, process-governance and decision-governance projects.

A BA working near ALCO should focus on definitions and traceability. What is a stable deposit? What is operational deposit treatment? What is a wholesale funding concentration? What is a maturity bucket? Which legal entity is in scope? Which currency view matters? Which stress scenario is official? Which manual adjustments are allowed? Who approves assumptions? Where is decision history stored? This is how business analysis becomes useful in Treasury.

23. Liquidity is about timing, confidence and operational access

The phrase liquidity risk is often simplified as the risk of not having enough cash. That is true but incomplete. Liquidity is about timing, confidence and operational access. The bank must have cash or cash-like assets when obligations fall due. It must be able to raise cash without destroying market confidence. It must also have operational access to the tools it claims to have.

Timing is the first dimension. A bank may have valuable assets maturing next month, but if payments are due this afternoon, those future maturities do not solve today's problem. A loan book may be high quality, but it cannot usually be turned into cash quickly without securitization, pledge arrangements or central-bank eligibility. A bond portfolio may be liquid in normal times, but if settlement fails or the securities are pledged elsewhere, the liquidity is not available at the moment needed.

Confidence is the second dimension. Funding markets are social systems. A bank that is trusted can borrow more easily. A bank that is doubted may find that funding lines reduce, repo haircuts rise, investors demand higher spreads, and depositors become more sensitive. Liquidity stress can therefore become self-reinforcing. The bank needs cash because confidence is falling, and confidence falls further because the market sees the bank needing cash. Treasury must manage not only numbers but signals.

Operational access is the third dimension. If a bank says it can repo securities, can it actually deliver them through the right custodian, under the right legal agreement, in the right currency, with the right counterparty, before the cut-off? If a bank says it has central-bank facility access, has it tested collateral mobilisation? Are legal entity permissions clear? Are signatures, systems and people available? Is the collateral data accurate? A liquidity plan that fails operationally is not a plan.

This is why contingency funding plans must be rehearsed. A CFP should define early-warning indicators, escalation levels, action menus, communication protocols, asset monetization options, central-bank access, investor communication, internal governance and post-event review. The document should be practical enough for a stressed morning. Long philosophical documents do not help when cash is moving fast. People need to know who calls whom, what can be sold, what can be pledged, what approvals are required and what communication is allowed.

Liquidity also has intraday behaviour. Payment systems do not wait for end-of-day accounting. A bank may need cash at specific moments to settle high-value payments, securities transactions, CLS obligations or central-bank operations. In real-time payment environments, even retail flows can become continuous liquidity movement. Treasury therefore needs tools that show expected and actual flows during the day. Static reports after close are not enough for intraday control.

Customer communication matters too. In a liquidity event, careless communication can worsen confidence. Silence can also worsen confidence. The bank must coordinate Treasury, Corporate Communications, Investor Relations, Risk, Legal and senior management. A funding action that is technically correct but poorly explained can create market anxiety. A calm message without real liquidity action is also dangerous. Liquidity management is both balance-sheet science and confidence management.

When you understand liquidity this way, the LCR becomes more than a ratio. It becomes a regulatory expression of a deeper survival question. Do we have enough usable assets to survive stress? Are they unencumbered? Are assumptions realistic? Is the operational path tested? Is management ready? That is the foundation every Treasury professional must carry.

24. Interest-rate risk in the banking book without textbook fog

Interest-rate risk in the banking book sounds technical, but the core idea is human and simple. A bank's assets and liabilities do not reprice at the same time or in the same way. When market rates move, the bank's earnings and economic value can change. Treasury and ALM must understand that change before it becomes a surprise.

Suppose a bank has many fixed-rate mortgages that earn 3 percent for several years. Suppose the funding side is made of deposits that can reprice faster as market rates rise. If rates move up sharply, the income from the mortgages stays fixed while the cost of keeping deposits may rise. Net interest income can compress. If the bank hedged properly, the pain may be reduced. If assumptions were weak, the bank may discover too late that earnings sensitivity was understated.

Now take the reverse situation. A bank has many floating-rate assets and stable low-cost deposits. Rising rates may initially help earnings because asset yields increase faster than deposit costs. But if customers demand higher deposit rates or move money to competitors, the benefit can shrink. If rates later fall, asset yields may drop while deposit costs cannot fall as much below zero or below customer expectations. Rate environments change the story.

IRRBB therefore needs both contractual and behavioural analysis. Contractual data tells when cash flows mature and reprice according to legal terms. Behavioural modelling estimates how customers actually behave. Non-maturity deposits are the classic challenge. Legally, many can leave immediately. Behaviourally, some stay for years. But behaviour changes when rates, trust and digital switching habits change. A model based on calm historical data may be wrong during stress.

The Basel IRRBB standards reinforce effective governance and measurement of earnings and economic value under interest-rate scenarios. The Committee recalibrated the prescribed shocks in July 2024, with implementation specified for 1 January 2026; use the applicable national implementation and current currency shock set rather than treating the 2016 calibration as timeless. Basel IRRBB shock recalibration. For a foundation learner, the important point is that IRRBB is not optional and not merely internal management preference. Supervisors expect boards and senior management to understand it.

Measurement normally includes earnings sensitivity and economic value sensitivity. Earnings sensitivity asks what happens to net interest income over a near-term horizon if rates move. Economic value sensitivity asks how the present value of assets, liabilities and off-balance-sheet items changes. Both are useful. A bank may look fine on short-term earnings but have a dangerous long-term economic value exposure. Or it may have manageable economic value exposure but painful short-term earnings volatility.

Hedging IRRBB is a practical art. Interest-rate swaps, futures and securities portfolio decisions can reduce exposure, but hedges must be aligned to the risk being hedged. A hedge that matches contractual maturity may not match behavioural maturity. A hedge that reduces economic value sensitivity may affect accounting volatility. A hedge that works in one rate scenario may be less effective in another. ALM must explain residual risk, not pretend that hedging makes the problem disappear.

For business analysts, IRRBB projects depend heavily on data. Product type, balance, rate type, repricing date, maturity date, customer segment, currency, optionality, prepayment terms, caps, floors, administered-rate rules and behavioural assumptions all matter. Missing or wrong fields can materially distort risk. A loan without repricing frequency, a deposit mapped to the wrong behavioural bucket, or a hedge linked to the wrong portfolio can create false comfort.

The plain-language memory line is this: IRRBB is what happens when the bank's balance sheet has a different relationship with interest rates on the asset side and liability side. Treasury's job is to know that relationship before rates move, not after.

25. Market risk and the trading book discipline

Market risk belongs most visibly to the trading book. It is the risk that prices move against positions held for trading, market-making or short-term resale. Rates, FX, credit spreads, equity prices, commodities and volatility can all move. A trading desk lives with that movement every day. The discipline of the trading book is to make risk visible, value positions honestly, measure sensitivities, impose limits and escalate breaches.

The trading book is different from the banking book because intention and measurement are different. A bond held in a liquidity portfolio may be managed for liquidity and structural yield. A bond held by a market-making desk is inventory. It can be sold quickly, hedged, repriced and marked to market daily through P&L. The same legal instrument can therefore have different risk treatment depending on purpose, governance and classification. This is why book classification is so sensitive.

Mark-to-market is the honesty mechanism. If a trader buys a bond and the market price falls, the loss appears. If an FX position moves against the desk, the P&L moves. If volatility changes, option values change. Daily P&L is uncomfortable sometimes, but it prevents the illusion that risk has not moved. When trading positions are allowed to hide behind stale marks or optimistic models, the bank loses the ability to react early.

Sensitivities explain the P&L. DV01 tells how a rates position changes for a one-basis-point move in rates. CS01 tells how a credit position changes for a one-basis-point move in spread. Delta, gamma and vega explain option risk. FX delta explains currency exposure. These measures turn a large portfolio into risk-factor language. Without sensitivities, the desk may know it made or lost money but not why.

VaR and stress testing add portfolio-level views. VaR estimates potential loss under statistical assumptions. Stress tests ask what happens under severe moves or historical scenarios. Both are needed and both have limitations. VaR can fail when history is not a good guide. Stress scenarios can miss new vulnerabilities. A good risk framework uses multiple lenses and asks whether the combined picture makes sense.

Limits turn risk appetite into daily behaviour. A desk may have VaR limits, sensitivity limits, stop-loss limits, issuer limits, tenor limits, currency limits and stress limits. A breach should be visible, owned and escalated. Temporary approvals should be documented and aged. If a desk repeatedly operates above appetite through exceptions, governance has failed even if each exception was approved.

The Basel market-risk framework exists because trading-book risk has historically been difficult to capture, especially under stress and for less liquid products. FRTB strengthened the boundary between banking and trading books and improved market-risk capital approaches. For a foundation learner, the lesson is simple: trading risk needs capital, independent control, liquidity horizon thinking and honest classification.

A BA working on Markets systems should never stop at trade capture. The trade must flow to risk, P&L, valuation, limits, settlement, regulatory reporting and audit. A risk system that receives trades late can understate exposure. A pricing model without independent validation can misstate value. A limit system without intraday visibility may catch a breach too late. A P&L explain without reliable market data can tell the wrong story.

The human rule is: trading risk is allowed only when it is visible, measured, limited, valued and governed. Anything else is not a business model. It is a delayed incident.

26. Front office, middle office, back office and control functions

Markets & Treasury becomes easier when you understand role separation. Front office owns business execution and risk-taking within mandate. Middle office validates, monitors and supports controls. Back office settles, confirms, reconciles and maintains records. Independent Risk, Product Control, Compliance, Finance, Legal, Model Risk and Audit challenge and govern. The exact labels vary by bank, but the separation of responsibility is essential.

Front office includes traders, salespeople, structurers and sometimes treasury dealers. Traders quote prices, execute trades, manage inventory and hedge risk. Salespeople cover clients, understand needs, communicate prices and coordinate execution. Structurers design solutions that combine products, payoff profiles and client objectives. Treasury dealers place or raise cash, execute repo, manage funding transactions or hedge structural risk within treasury mandate. Front office is close to decisions and markets, so it also has the strongest risk of conflicts and pressure.

Middle office often handles trade validation, risk control support, limit monitoring, exception management and sometimes P&L attribution. In some banks, market risk sits fully outside middle office. In others, middle office performs the first control layer while independent risk performs challenge. The important point is that someone independent of the trader must verify that trades are complete, authorised, within limits and flowing correctly downstream.

Back office is where many failures become visible. Trade confirmation, settlement instruction, payment generation, custody movement, nostro reconciliation, collateral settlement, coupon processing and failed-trade management are operational disciplines. They may sound less glamorous than trading, but a poor back office can destroy a strong front office. A trade that is profitable on screen but fails settlement can create cost, risk and client damage.

Product Control is especially important in Markets. It independently explains P&L, verifies prices, challenges valuations, books valuation adjustments and ensures financial reporting integrity. If front office says a complex trade is worth a certain amount, Product Control asks whether the mark is independent, observable, model-supported and consistent with policy. This is not a personality conflict. It is a control design.

Market Risk sets and monitors risk limits, runs VaR and stress, reviews sensitivities, challenges desk positions and escalates breaches. Finance owns official books and financial statements. Compliance monitors conduct, market abuse, client treatment and regulatory obligations. Legal ensures documentation is enforceable. Model Risk validates pricing and risk models. Internal Audit later tests whether all these controls actually work.

For learners, role separation explains why a simple trade can touch so many teams. The trader books it. Middle office validates it. Risk measures it. Product Control explains its P&L. Back office confirms and settles it. Finance books it. Compliance watches conduct. Legal owns the agreement. Technology supports the systems. Data teams maintain reference and market data. If any team fails, the trade lifecycle weakens.

This is also why good requirements must name owners. A vague statement like the system should process trades is not enough. Which team validates? Which team repairs? Which team approves override? Which team receives alert? Which team owns reconciliation? Which team signs off end-of-day? In Markets & Treasury, ownership is a functional requirement.

27. Systems architecture of Markets & Treasury at foundation level

A Markets & Treasury architecture is a network of systems, not one magic platform. At the front are channels and execution venues: dealer screens, electronic trading platforms, client portals, voice capture, APIs, order management systems and sometimes treasury workstations. These capture intent and execution. Behind them are trade capture systems, position systems, pricing engines, market-data services, risk engines, confirmation systems, settlement systems, collateral systems, accounting systems, regulatory reporting engines and data warehouses.

The trade capture system is often the central operational record for Markets activity. It stores trade economics, counterparty, product type, dates, currency, notional, price, rate, index, settlement instructions, book, trader, legal entity and status. If the trade is wrong here, almost every downstream system inherits the problem. That is why trade validation rules are critical.

Pricing engines and market-data services calculate values and risk measures. They need curves, volatility surfaces, credit spreads, FX rates, calendars, day-count conventions and product models. Market data must be timely and governed. A stale price can distort valuation. A wrong curve can distort risk. A missing holiday can change settlement or cash-flow calculation.

Risk engines aggregate positions and calculate sensitivities, VaR, stress and limit utilization. They need clean trade data, product models, market data and hierarchy mapping. A trader may book into a desk, which rolls into a business line, which rolls into a legal entity, region and global risk view. If hierarchy mapping is wrong, limits and reporting become unreliable.

Settlement and confirmation systems transform trades into enforceable and operational events. Confirmations ensure both parties agree trade terms. Settlement systems produce cash or securities instructions. Collateral systems calculate margin requirements and manage eligible collateral. Reconciliation tools compare internal records with external statements, custodians, counterparties and nostro accounts.

Treasury systems may include cash-positioning tools, liquidity reporting engines, ALM systems, FTP engines, collateral management and central-bank facility tools. These systems consume data from the broader bank: core banking, payments, loans, deposits, securities, derivatives, GL and market data. Treasury architecture therefore depends heavily on integration with non-Markets systems.

Some banks use event-driven integration; others use controlled batch files, APIs or a combination. Neither pattern guarantees accuracy or timeliness. The following is an illustrative architecture, not a mandatory platform design.

In an event-driven architecture, trade booking, amendment, cancellation, settlement matching or failure, collateral calls, valuation and accounting events may flow through messaging or streaming platforms. This helps timeliness but raises challenges of idempotency, ordering, replay, schema governance, monitoring and reconciliation. In a bank, events are useful only if they are controlled.

For a BA, the architecture question is always: what is the golden source for each business object? The golden trade may live in one system. The golden counterparty may live in another. The golden security master may live in a reference-data platform. The official position may be a reconciled result. The official accounting balance may be in GL. If these truths are not named, teams will argue during every break.

28. Reference data and market data: the quiet foundation of correct risk

Reference data and market data are quiet until they break. Then everyone remembers how important they are. In Markets & Treasury, reference data describes the things the bank trades, the entities it trades with, the books that own risk, the accounts used for settlement, the calendars used for dates and the legal structures that make transactions valid. Market data describes prices, rates, curves, spreads, volatilities and other external variables used for valuation and risk.

A bond needs an identifier, issuer, currency, coupon, maturity, day count, payment frequency, issue date, settlement convention, listing or market, rating, collateral eligibility, haircut category, tax attributes and corporate action details. A derivative needs product taxonomy, rate index, calendars, conventions, fallback language and model mapping. A counterparty needs legal name, LEI where applicable, onboarding status, credit limit, documentation status, settlement instructions and regulatory classification.

Bad static data creates real risk. A wrong maturity date can distort liquidity ladder and IRRBB. A wrong coupon can distort valuation. A wrong settlement account can fail a trade. A missing counterparty documentation flag can allow an unauthorised transaction. A wrong product classification can send a position to the wrong regulatory report or risk engine. This is why reference-data governance is not clerical work. It is risk control.

Market data has a different failure pattern. A stale FX rate may misvalue positions. A missing curve point may force interpolation or fallback. A wrong volatility surface may distort option risk. An incorrect credit spread may change P&L. A price from an illiquid market may not represent executable value. Product Control and Risk therefore need price-source hierarchy, independent verification, stale-data checks and manual override governance.

Calendars deserve special attention. Markets operate across jurisdictions. A settlement date depends on currency calendars, market holidays and product conventions. A cross-currency transaction may need both currency calendars. A securities trade may need exchange and settlement-system calendars. A one-day calendar error can create failed settlement, funding mismatch or client complaint.

For testing, reference-data scenarios should be deliberate. Change a rating and verify collateral eligibility. Change a settlement calendar and verify value date. Amend SSI and verify approval. Create a new security and verify risk, settlement, accounting and reporting. Mark a counterparty as not fully onboarded and verify trade prevention. Use stale market data and verify warning or fallback. These tests protect the bank from quiet errors that become public problems.

In a mature bank, reference data and market data have ownership, stewardship, lineage, quality checks, exception queues and audit. In an immature bank, everyone downloads a spreadsheet and hopes. Markets & Treasury cannot run safely on hope.

29. Accounting and valuation at a foundation level

Markets & Treasury learners do not need to become accountants on day one, but they must understand that accounting classification changes how risk appears in financial statements. A position can be economically risky even if the accounting presentation delays the visible loss. A hedge can make economic sense but create accounting volatility if documentation and effectiveness rules are not met. A trading profit can be real but still require valuation adjustment if inputs are unobservable.

Regulatory book allocation and accounting measurement must be recorded as distinct fields. Under IFRS 9, financial-asset classification depends on the business model and contractual cash-flow characteristics. Debt assets may be measured at amortised cost, fair value through other comprehensive income or fair value through profit or loss, subject to the detailed conditions. A banking-book asset can therefore be FVTPL. US GAAP categories and hedge-accounting requirements differ. IFRS Foundation: IFRS 9. This means market movements in the trading book normally hit P&L immediately. Some banking-book securities may show fair-value movement in reserves rather than daily P&L, or may not show full fair-value movement in P&L if held at amortised cost. The economic risk still exists.

This distinction became very visible in rising-rate environments. A bank holding long-duration fixed-rate securities may see market values fall. If those securities are not intended for sale and accounting classification permits, losses may remain unrealised. But if liquidity pressure forces sales, those losses become realised. The accounting treatment did not create the risk. It affected when and where the risk became visible.

Hedge accounting is another important foundation idea. A bank may use derivatives to hedge interest-rate or FX risk. Economically the hedge may offset the risk, but accounting recognition depends on documentation, designation, effectiveness and ongoing testing. If hedge accounting fails, the derivative's fair-value movement may create P&L volatility that management did not expect. This is why ALM, Treasury, Finance and Risk must coordinate before executing hedges, not after.

Valuation adjustments matter for traded products. A theoretical model price may not equal the price at which the bank can exit the position. Credit valuation adjustment, debit valuation adjustment, funding valuation adjustment, model reserves, liquidity reserves and bid-offer reserves can all affect reported value. The details are advanced, but the foundation lesson is simple: fair value must be independently supportable, especially where markets are illiquid or models are complex.

For business analysis, accounting requirements should ask where the official accounting event is generated, how trade events map to GL, how valuation feeds Finance, how P&L is explained, how hedge relationships are documented, how manual adjustments are approved and how accounting breaks are reconciled. A Markets system that books trades but cannot support Finance is incomplete.

A practical control test might follow one bond trade through capture, settlement, position update, valuation, accrued interest, coupon payment, accounting entry and reporting. Another might follow an interest-rate swap through trade capture, confirmation, valuation, collateral movement, payment event and hedge accounting designation. This is how a learner sees that accounting is not separate from Markets & Treasury. It is one of the official languages through which the bank records the domain.

30. Controls that stop a small mistake becoming a bank-level problem

Markets & Treasury controls exist because small mistakes can scale quickly. A wrong trade booked for ten million instead of one million can create immediate market risk. A wrong currency can create settlement failure. A wrong counterparty can breach credit limits. A missed collateral call can create exposure. A late confirmation can hide disagreement. A stale valuation can misstate P&L. A limit breach left open can become a large loss.

Pre-trade controls protect the bank before risk is created. They include counterparty eligibility, product permission, trader mandate, credit limit check, market-risk limit check, price tolerance, sanctions or restricted-party controls where relevant, and documentation status. Not every product has the same pre-trade pattern. A simple FX spot trade and a complex structured derivative require different checks. But the principle is the same: the bank should know whether it is allowed to do the trade before it does the trade.

Trade capture controls ensure the booked trade matches the agreed economics. Mandatory fields, product templates, validation rules, maker-checker workflows, price reasonableness, booking model, desk assignment and amendment audit are all important. A trade should not be able to travel downstream with missing critical data unless a controlled exception process exists.

Post-trade controls include confirmation matching, settlement instruction validation, risk feed completeness, P&L explain, valuation review, collateral calculation, regulatory reporting and reconciliation. These controls catch problems that pre-trade controls cannot prevent. A trade may be valid but unmatched. A settlement instruction may be valid internally but wrong externally. A price may pass capture rules but fail independent verification.

Limit controls convert risk appetite into daily boundaries. Limits should have owners, thresholds, breach workflow, approval authority and aging. A breach without owner is a weak control. A breach with endless temporary approval is also weak. Good systems show headroom, utilization, trend and source of movement. They also distinguish genuine risk movement from data errors.

Access controls are often underestimated. Who can book trades? Who can amend trades after confirmation? Who can override prices? Who can change SSI? Who can approve a collateral substitution? Who can change a curve mapping? In Markets & Treasury, access is risk. Segregation of duties must be designed, tested and periodically reviewed.

Reconciliation is the final safety net. Internal trade records must reconcile with counterparty confirmations. Securities positions must reconcile with custodians and depositories. Cash must reconcile with nostro statements. GL must reconcile with sub-ledgers. Risk positions must reconcile with front-office systems. Breaks should be aged, owned and explained. A break that stays open too long becomes a risk object in itself.

The control culture matters more than the control list. If people treat controls as obstacles, they will find ways around them. If leadership treats early escalation as professional behavior, issues surface sooner. The goal is not to make work slow. The goal is to make risk visible before it becomes expensive.

31. How payment systems and Markets & Treasury connect

Because your wider academy focuses strongly on payments, it is important to make the connection clear. Payments and Markets & Treasury are not separate worlds. Payment flows are one of the main ways liquidity moves through the bank. Markets activity also generates payment and settlement flows. A large FX trade, a repo maturity, a bond purchase, a coupon receipt, a derivative cash-flow payment and a securities settlement all create cash movements that must pass through payment or settlement infrastructure.

A bank's nostro accounts are where this connection becomes visible. Cross-border payments, FX settlements and securities cash legs all affect currency balances. Treasury must know whether there is enough cash in the right currency and account at the right time. When Payment Operations sends an outgoing payment instruction over Swift, Treasury forecasts the cash requirement; the message or its network acknowledgement does not prove a nostro debit. Treasury replaces that forecast with the actual debit when settlement and account evidence support it, then recalculates usable cash and any funding need. When Securities Operations proves a DvP settlement, Treasury records the linked cash movement and relevant change in securities or collateral inventory.

Real-time payments increase the importance of intraday liquidity. When customer payments settle instantly or near instantly, liquidity forecasting cannot rely only on end-of-day batch assumptions. Corporate bulk payments, instant retail flows, treasury funding payments and securities settlements can interact during the day. If a bank delays liquidity visibility until after close, it is managing yesterday's picture.

Markets trades also require clean payment instructions. An FX spot trade may require two currency payments. A derivative coupon may generate periodic cash flow. A bond trade may settle DvP through a securities settlement system, but cash accounts are still affected. A repo has near-leg and far-leg cash and securities movements. Each flow needs correct value date, amount, currency, account, counterparty and settlement channel.

Payment controls and markets controls therefore overlap. Sanctions screening, AML monitoring, fraud controls, payment cut-offs, repair queues, nostro reconciliation, settlement status and client notifications can all touch market-related flows. If a Markets trade generates a payment that is blocked or delayed, the front office, operations, compliance and Treasury must understand the impact quickly.

For BA work, this connection produces excellent requirements questions. If an FX trade is booked for a customer payment, what happens if the payment is rejected? If a securities settlement fails, does Treasury receive a liquidity update? If a large repo maturity is due, is it included in the cash forecast? If a derivative payment is disputed, how is it reflected in liquidity reporting? If a nostro break appears, can it be traced to a market trade, customer payment, fee or correction?

The joined story is this: payments move value; Markets & Treasury manages the risk, funding, liquidity and price effects of that value movement. A bank that separates these worlds too strongly will miss important operational and liquidity signals.

32. Customer impact of a domain most customers never see

Most customers never meet Treasury or Markets teams. Yet the work of these teams affects customers every day. Deposit pricing, loan pricing, FX rates, payment cut-offs, availability of credit, execution quality, product availability, investment yields and the bank's resilience all depend partly on Markets & Treasury decisions.

When Treasury changes FTP, business units may change customer pricing. A mortgage rate may rise because long-term funding costs increased. A corporate loan margin may change because liquidity premiums increased. A deposit campaign may be launched because the bank wants more stable funding. A bank may reduce appetite for certain long-tenor products because ALM risk is high. Customers experience these as product decisions, but the logic often comes from Treasury.

Markets affects customers through execution and risk management. A corporate that imports goods needs FX. A pension fund needs bond execution. A borrower needs interest-rate hedging. An issuer needs access to investors. A client may not care about the bank's internal desk structure, but it cares about fair pricing, timely execution, clear confirmation, transparent costs and reliable settlement. Weak market operations become customer pain quickly.

Liquidity stress affects customers more directly than most people realise. If a bank becomes cautious on liquidity, it may tighten lending, reprice deposits, reduce credit lines, slow balance-sheet growth or change product terms. In severe stress, customer confidence becomes part of the liquidity problem. Treasury decisions therefore have real social and commercial consequences.

Operational failures also reach customers. A failed FX settlement can delay a supplier payment. A wrong rate can create a dispute. A failed securities settlement can affect an investment manager's portfolio. A late confirmation can create uncertainty. A payment linked to a market trade can be delayed by wrong static data. These are not abstract back-office issues. They are customer-impacting events.

Good customer communication requires internal clarity. If a payment linked to FX is delayed, the bank should explain accurately without exposing internal confusion. If a market order executes at a certain price, the client should understand the basis. If a product is repriced because funding costs changed, relationship managers need language that is commercially honest and compliant. Treasury and Markets knowledge should therefore travel to front-line teams in usable form.

For Malla Banking Academy learners, this is a key differentiator. Do not learn Markets & Treasury as a secret technical tower. Learn it as a domain that quietly shapes customer experience, product economics and bank stability. That makes the knowledge practical for business analysts, testers, architects, operations, compliance and product owners.

33. Requirements thinking for Markets & Treasury projects

A Markets & Treasury requirement must be precise because the domain punishes vague language. If a requirement says show liquidity position, that is not enough. Which liquidity position? By legal entity, currency, product, maturity bucket, time of day, stress scenario, regulatory view or management view? Is it opening position, forecast position, actual position or end-of-day position? Does it include committed but undrawn facilities? Does it include settlement fails? Does it include collateral that can be monetized? Does it include intraday payments?

If a requirement says calculate market risk, that is also not enough. Which risk measure? DV01, CS01, delta, vega, VaR, stress loss, limit utilization or P&L explain? Which positions are in scope? Which book? Which desk hierarchy? Which market data timestamp? Which model version? Which aggregation level? Which currencies? Which exceptions? Which sign convention? Risk requirements must be specific enough that independent teams can reproduce the number.

If a requirement says book FX trade, the BA must capture product type, currency pair, buy/sell direction, dealt currency, counter currency, trade date, value date, rate, amount, counterparty, client, book, trader, settlement instructions, quote validity, margin, confirmation method, payment generation, cancellation, amendment, audit and downstream feeds. FX is simple only when the details are ignored.

For Treasury requirements, behavioural assumptions need ownership. If deposits are mapped to behavioural maturity buckets, who approves the mapping? If a product's FTP treatment changes, who signs off? If a stress outflow factor is changed, is it regulatory, internal model or management overlay? If a manual adjustment is allowed, where is evidence stored? These questions protect the bank from invisible model drift.

Non-functional requirements are just as important. Markets & Treasury systems often need timeliness, availability, auditability, data lineage, access control, resiliency and reconciliation. A risk dashboard that is accurate after two days may be useless for intraday limits. A liquidity report that cannot trace its numbers to source systems may fail governance. A settlement system without high availability may create market penalties.

Acceptance criteria should use real scenarios. For example: Given a USD fixed-rate bond trade is booked into the trading book, when rates shift by one basis point, then the risk engine calculates DV01, aggregates it to the correct desk, updates limit utilization and stores audit details. Or: Given a large corporate deposit is withdrawn before cut-off, when the payment settles, then the cash forecast, liquidity position and intraday dashboard update within the agreed time. These criteria are testable and domain-relevant.

A good BA also separates official rule, bank policy, product design and example. Basel defines regulatory principles. The bank's policy implements them. The product design applies them to a specific service. An example illustrates them. Mixing these layers creates confusion. Clear requirements name the layer.

34. Testing mindset for topic 1 foundations

Testing Markets & Treasury foundations means proving that the bank understands its own risk objects. The tester should not only click screens. The tester should ask whether the system behaviour reflects the domain logic. If the system cannot distinguish banking book from trading book, the foundation is weak. If it cannot identify product, book, desk, counterparty, currency, maturity, repricing date and settlement status, many later controls will fail.

A strong foundation test pack begins with separate prudential and accounting classifications. Book a bond into each regulatory book and verify the applicable risk, capital, governance and reporting routes. Independently assign its accounting category under the relevant framework and verify recognition, valuation and journals. Both bonds may legitimately be measured at FVTPL; differing regulatory books do not require different accounting categories. Liquidity eligibility also needs its own assessment.

Next test liquidity flow. Create a deposit inflow, a loan drawdown, a maturing security, an outgoing high-value payment and a repo maturity. Verify that the cash-positioning view updates correctly by currency and value date. Verify that expected versus actual movement can be compared. Verify that late or failed flows create exceptions. Verify that the liquidity report does not simply wait for GL close if the requirement is intraday.

Then test market-risk flow. Book a simple FX position, a fixed-income position and an interest-rate swap. Verify that trades reach the risk engine, sensitivities calculate, limits update, P&L explain receives values and Product Control can identify valuation inputs. Introduce a missing market data point and verify warning or fallback. Introduce a desk-limit breach and verify escalation. This proves that risk is not trapped in front-office systems.

Test FTP and ALM. Create products with different maturities and repricing profiles. Verify FTP curve mapping. Change a curve version and verify effective dating. Move a deposit from stable to non-stable category and verify impact. Change a loan repricing date and verify ALM cash-flow bucket. This proves that balance-sheet economics are not treated as static.

Test controls. Try booking an unauthorised product. Try amending a confirmed trade. Try using missing settlement instruction. Try overriding a price without approval. Try moving a position between books. Try deleting an audit-relevant field. A strong system should either prevent the action or force controlled approval with traceability. The goal is not to frustrate users. The goal is to stop silent risk creation.

Finally test reporting reconciliation. A position count in front office should reconcile to risk. Settled cash should reconcile to nostro. Accounting entries should reconcile to sub-ledger. Limit utilization should reconcile to risk positions. Liquidity reports should reconcile to source balances and approved overlays. The foundation is only trustworthy when numbers can be traced and explained.

35. Case-style learning: a rising-rate stress without exaggeration

Consider a bank that has grown quickly during years of low interest rates. It gathered deposits cheaply and bought long-duration high-quality securities to earn spread while loan demand was moderate. The securities are mostly government or agency-related and credit quality appears strong. Management believes the portfolio is safe because default risk is low. Then market rates rise sharply.

The first effect is valuation. The fixed-rate securities fall in market value. If the portfolio is not classified through daily P&L, the loss may not immediately hit earnings in the same way a trading loss would. Some leaders may feel comfort because the bank can hold to maturity. That comfort may be valid only if liquidity remains stable. If deposits stay and funding access remains good, the bank may not need to sell. But if deposits leave or wholesale markets become nervous, the bank may need cash.

The second effect is deposit behaviour. Customers who accepted low rates during a low-rate period may demand more yield. Digital channels make it easier to move money. Large corporate treasurers actively manage cash. A deposit base that seemed stable can become more rate sensitive. Treasury's behavioural assumptions are tested. FTP may need adjustment. Product teams may need to reprice. Liquidity forecasts may change.

The third effect is realised-loss risk. If the bank sells securities to meet outflows, unrealised losses become realised. The bank may still be solvent in a long-term economic sense, but capital confidence can weaken. Market participants may ask how much loss remains. Rating agencies may react. Depositors may become more nervous. Liquidity and capital narratives interact.

The fourth effect is governance pressure. ALCO must decide whether to sell, repo, raise funding, use central-bank facilities, adjust deposit pricing, reduce asset growth or communicate differently. Risk must challenge assumptions. Finance must show accounting consequences. Treasury must identify available collateral and funding windows. Management must act before confidence deteriorates further.

The lesson is not that long-duration securities are bad. They can be perfectly appropriate in a liquidity portfolio if duration, liquidity, accounting, funding and stress behaviour are understood. The lesson is that safety has dimensions. Credit safety is not interest-rate safety. Accounting classification is not liquidity. Unrealised loss is not irrelevant if forced-sale risk exists. Deposit stability is not permanent just because history looked calm.

This case-style pattern is useful because it ties together the whole foundations chapter: banking book versus trading book, Treasury survival mandate, ALCO governance, IRRBB, LCR, funding confidence, customer behaviour, accounting and communication. That is what real Markets & Treasury thinking looks like.

36. What “aligned” content means in this module

Alignment means every topic in Markets & Treasury should connect back to the same core map. Foundations explains why the domain exists. Bank Treasury & Liquidity explains survival cash, HQLA, funding, stress and FTP in operating depth. Money Markets explains how short-term cash is borrowed, lent and collateralised. Fixed Income explains bonds as investment assets, trading instruments, collateral and liquidity-buffer holdings. FX explains currency risk, settlement and payment-linked cash movement. Derivatives explains risk transformation and lifecycle discipline. ALM and FTP explain structural balance-sheet economics. Market Risk explains limits, valuation, stress and trading-book control.

No topic should drift into random finance education. Equities, bonds, FX or derivatives should not be taught as isolated textbook instruments. They should be taught through banking purpose: client need, bank balance sheet, risk ownership, system flow, settlement, accounting, reporting, regulation and customer impact. That is the Malla Banking Academy pattern.

For example, when explaining a bond, the content should not stop at coupon and maturity. It should ask: who issued it, why does the bank hold it, which book owns it, how is it valued, can it be repoed, how does it affect HQLA, how does duration affect IRRBB or market risk, how does settlement happen, what happens at coupon date, what happens if the issuer rating changes, and what does the customer or business line see?

When explaining FX, the content should not stop at spot and forward. It should ask: is the FX linked to a payment, trade finance, securities purchase, corporate hedge, treasury funding need or trading position? Which currency account is debited? Which nostro is credited? What is the value date? Does settlement use PvP or bilateral flows? What happens if one leg fails? How are sanctions, confirmations, cut-offs and rate disputes handled?

When explaining derivatives, the content should not stop at payoff diagrams. It should ask: what risk is being transformed, who owns residual basis risk, how is the trade documented, how is it valued, is it cleared, what collateral is exchanged, how are lifecycle events processed, and how does it affect accounting or regulatory reporting?

That is alignment. The learner should feel that each chapter adds a new room to the same building, not a new building every time.

37. Source references for Topic 1

The following official and primary sources anchor the foundation concepts in this chapter. They are included so learners can read the rule-level material after understanding the practical story.

• BIS Basel Committee - Basel III Liquidity Coverage Ratio and liquidity risk monitoring tools - primary Basel source for LCR, HQLA and short-term liquidity resilience.
• BIS Basel Committee - Basel III Net Stable Funding Ratio - primary Basel source for the stable funding framework and one-year structural funding perspective.
• BIS Basel Committee - Interest rate risk in the banking book - official Basel standard for IRRBB governance, measurement and supervisory expectations.
• BIS Basel Committee - Minimum capital requirements for market risk - official Basel market-risk capital standard integrated into the Basel Framework.
• SEC - T+1 settlement cycle implementation statement - official US source confirming the T+1 settlement-cycle implementation date of 28 May 2024.
• ESMA - July 2026 T+1 preparation statement - EU transition is scheduled for 11 October 2027. This future securities transition does not imply all FX or repo transactions use that cycle.

These sources should not be used to replace the human explanation. They should be used to verify it. The role of this chapter is to translate the official logic into practical banking understanding without losing accuracy.

38. Operational reports a learner should recognise early

A learner does not need access to a bank's confidential reports to understand the categories of reporting used in Markets & Treasury. The important thing is to recognise what each report is trying to prove. Reports are not decoration. They are control evidence, management decision tools and sometimes regulatory inputs. A report that looks impressive but does not answer a real control question is weak. A simple report that clearly shows risk, movement, owner and exception can be far more useful.

A daily cash position report shows where the bank expects to be in each material currency and account. It usually separates opening balance, known inflows, known outflows, maturities, expected customer flows, market transactions, central-bank or clearing-system obligations and projected closing position. The stronger version also compares forecast with actual, identifies unexplained variance and flags large single-name movements. For Treasury, this is not a historical report. It is a steering instrument. If the report is late, incomplete or not trusted, dealers may cover or place cash using partial information.

A liquidity buffer report shows the stock of assets available for stress survival. It should distinguish assets by quality, currency, legal entity, encumbrance, haircut, central-bank eligibility, repo eligibility, custodian location and monetization assumption. A high-level number alone is not enough. A bank may have a large nominal buffer but a smaller usable buffer after currency, legal entity, haircut and encumbrance constraints. A good liquidity report should therefore tell not only how much the bank owns, but how much can realistically produce cash under the relevant scenario.

A funding ladder shows the maturity profile of liabilities and funding sources. It tells the bank when money matures and must be replaced. A maturity wall is a warning sign because it concentrates refinancing need. If too much funding matures in the same week or month, the bank may be forced to issue or roll during poor market conditions. A funding ladder also helps management decide whether to pre-fund, extend tenor, diversify currency, issue covered bonds, issue senior debt or reduce asset growth.

An ALM gap report shows how assets and liabilities reprice or mature across time buckets. It may be contractual or behavioural. The distinction matters. Contractual gaps show legal cash-flow timing. Behavioural gaps include assumptions about deposit stability, loan prepayment, administered-rate changes and customer behaviour. A good ALM report should clearly label which view is being used. A bad report mixes behavioural assumptions into numbers without making the assumptions visible.

A market-risk dashboard shows risk taken by trading desks. It may include VaR, stressed VaR, sensitivities, P&L, limit utilization, breaches, stress results, issuer concentrations, tenor concentrations and product-level exposure. The dashboard should allow a risk manager to move from global view to desk view to trade or risk-factor view. If a limit is close to breach, the report should show why: new trades, market movement, model change, data correction or hierarchy change. Without explanation, a number is only noise.

A P&L explain report connects profit and loss to market movement and trading activity. It helps Product Control, traders and Risk understand whether daily P&L is explainable. If a rates desk loses money, was it because yields moved, curves steepened, basis changed, volatility moved, carry accrued, a new trade was booked, or a stale price was corrected? Unexplained P&L is not automatically fraud or error, but it is a signal that deserves investigation.

A settlement-fails report shows market trades that did not settle as expected. For securities, failed settlement can affect liquidity, client service, regulatory metrics, borrowing cost and reputation. For FX, failed settlement can create currency exposure and nostro breaks. For derivatives, missed payments or collateral movements can create credit exposure and dispute. The fails report should show age, amount, counterparty, product, reason, owner and escalation status. A fail that ages silently is not an operational item. It is risk.

A collateral report shows what collateral is held, posted, eligible, substituted, encumbered and available. It connects Treasury, Markets, Credit Risk and Operations. Repo, derivatives and central-bank facilities all depend on collateral data. A security that looks available in a position report may already be pledged elsewhere. A collateral report therefore needs a single truth about encumbrance and availability.

A regulatory liquidity report translates internal balances into regulatory categories. This is where LCR and NSFR logic appears. The report must be traceable and controlled because regulatory numbers need evidence. If a deposit receives a particular runoff treatment, the bank should know why. If an asset is classified as HQLA, the eligibility logic should be documented. If an overlay is applied, approval should be visible.

These reports teach a practical lesson: Markets & Treasury is not only about deals. It is about proving the bank knows what it owns, owes, risks, values, settles and can survive.

39. Data lineage from customer action to board-level risk

One of the hardest things in this domain is showing how a small customer or desk action becomes a board-level risk number. Data lineage is the bridge. Without lineage, people debate reports instead of managing risk. With lineage, the bank can trace a number from source event to calculation to decision.

Take a corporate loan drawdown. The customer submits a request through a relationship manager, portal or operational process. The loan system records the drawdown, value date, currency, amount, facility, borrower, product, maturity, pricing and commitment impact. The payment system may move funds to the customer or a beneficiary. The core or loan accounting system updates balance. Treasury forecasting consumes the cash movement. ALM consumes the asset cash flow and repricing profile. FTP consumes product attributes to calculate internal funding cost. Credit Risk consumes exposure. Finance consumes accounting. Regulatory liquidity reporting may consume drawdown behaviour and committed facility usage. A single drawdown becomes many truths across the bank.

Now take an FX trade linked to a customer payment. The channel captures customer instruction. Pricing service provides rate. FX trade capture books the deal. Payment engine generates currency movement. Sanctions screening and payment validation may hold or release the payment. Nostro reconciliation later confirms cash movement. Market Risk receives any residual FX position. Product Control receives valuation and P&L. Customer reporting shows payment status and rate. If the payment fails after FX booking, the bank needs a controlled unwind or repair process. Data lineage tells which event caused which downstream state.

Take a bond purchase for the liquidity buffer. Treasury decides to buy a security. The trade is booked. The security master provides coupon, maturity, rating, issuer and eligibility. Settlement sends cash and receives securities. Custody confirms holding. Liquidity reporting classifies HQLA treatment. ALM reads duration and cash flows. Finance books security classification. Risk monitors interest-rate sensitivity. Collateral management may mark it as available for repo or central-bank pledge. If the rating changes later, the same security may move eligibility bucket. Lineage must carry that change through the bank.

Board-level risk numbers are aggregations of thousands or millions of such events. The LCR is not born in the LCR report. It is born in deposits, loans, securities, derivatives, commitments, market data, legal-entity structure and assumptions. Market-risk utilization is not born in the risk dashboard. It is born in trades, prices, models, curves, mappings and hierarchy. FTP profitability is not born in a profitability report. It is born in product balances, behavioural assumptions, curve versions and internal charging rules.

This is why data lineage is not a luxury. It answers audit, regulation and management questions. Where did the number come from? Which system owns it? Which transformations changed it? Which assumptions were applied? Who approved overrides? When did the data arrive? Which report consumed it? Can the number be reproduced later?

For BA work, lineage should be explicit in requirements. Name source systems. Name golden fields. Name transformations. Name owners. Name control checks. Name reconciliation points. Name manual adjustments. Name report consumers. If requirements skip lineage, the project may deliver a screen that looks good but cannot defend its numbers.

The deeper lesson is this: in Markets & Treasury, a number without lineage is not a controlled number. It may be useful for conversation, but it is not enough for governance.

40. Human communication in a technical domain

Markets & Treasury is full of technical language, but the best professionals can explain it simply. This is not because the topic is easy. It is because unclear communication creates risk. If a treasurer cannot explain a liquidity problem to senior management, action may be delayed. If a risk manager cannot explain a limit breach to a desk head, the desk may treat it as bureaucracy. If a BA cannot explain a requirement to developers, the build may miss the real control.

Good communication starts with the business question. Instead of saying, "The LCR impact is adverse due to runoff assumptions and Level 1 HQLA constraints," a good communicator can say, "This product may create more stressed cash outflow than the liquid assets it helps us hold, so it can weaken our short-term liquidity ratio unless we price or limit it properly." The technical language can follow, but the human meaning comes first.

For IRRBB, instead of saying, "The economic value sensitivity under the parallel-up shock is outside internal trigger," say, "If rates rise in this scenario, the present value of our banking-book balance sheet falls more than our internal comfort level, mainly because this portfolio is too long in duration." That sentence gives management a route to action.

For market risk, instead of saying, "Desk DV01 utilisation is elevated due to curve exposure," say, "The rates desk is now more exposed to small movements in interest rates than usual, and the exposure is close to the approved limit." Again, the technical measure is still there, but the meaning is clear.

For FTP, instead of saying, "The liquidity premium uplift changes product contribution," say, "The product looked profitable before, but once we charge the real cost of stable funding, the margin is much thinner." This is the sentence a product owner needs.

Human communication is also essential in incidents. If a settlement fails, operations should not only say "trade unmatched." They should explain impact: "The bond purchase did not settle today because counterparty instructions did not match. Cash did not leave, securities were not received, and tomorrow's liquidity and position reports need to reflect the failed state." That is operational clarity.

Malla Banking Academy content should model this communication style. Use the correct terms, but always translate them into consequence. A learner should finish the chapter able to speak to developers, testers, architects, operations, finance, risk, compliance and product teams without sounding like a textbook or a sales pitch. The goal is not to simplify until accuracy is lost. The goal is to make accuracy usable.

41. Interview and workplace readiness from this foundation

A person who understands this foundation can handle many real workplace questions better than someone who memorised product definitions. In interviews, the question may not be "Define LCR." It may be "Why does Treasury care if a deposit is stable or not?" The answer should connect deposit behaviour, liquidity outflow assumptions, funding value, FTP and stress. That shows understanding.

If asked the difference between Treasury and Markets, do not only say Treasury manages liquidity and Markets trades. Say Treasury protects and optimises the bank's own balance sheet, while Markets serves clients and manages trading risk in market products. Then add that they sit close together because market prices, funding, collateral, liquidity, FX and risk systems connect them.

If asked why banking book and trading book matter, explain prudential classification, purpose, risk measurement and governance, then assess accounting independently. A banking-book security may be held for liquidity or structural balance-sheet purposes; a trading-book security may be held for market-making or short-term resale. Transfers are governed by boundary rules; desk labels cannot change accounting facts or remove economic exposure.

If asked about a liquidity crisis, do not jump straight to selling assets. Start with diagnosis: cash forecast, outflows, inflows, HQLA, encumbrance, repo capacity, central-bank access, wholesale funding, deposit behaviour, communication and contingency funding plan. Then explain that actions must be sequenced and governed because careless asset sales or poor communication can worsen confidence.

If asked how a BA would gather requirements for a Treasury system, say you would start with the management question and the source-to-report flow. What is the report or function trying to decide? Which products, currencies, legal entities and time horizons are in scope? Which source systems feed it? Which assumptions are applied? Which controls and reconciliations prove it? Who owns exceptions? How is audit maintained?

If asked how payments connect to Treasury, explain that payment flows move liquidity. High-value payments, customer transfers, securities settlement cash legs, FX settlements and instant payments all change intraday and end-of-day cash positions. Treasury needs visibility so the bank can fund accounts, avoid failed settlement and manage liquidity buffers.

In daily work, this foundation helps you ask better questions. When someone says a product is profitable, ask whether FTP is included. When someone says liquidity is strong, ask whether assets are usable and unencumbered. When someone says the trade is booked, ask whether it is confirmed, settled, valued, reported and inside limits. When someone says the report is ready, ask whether lineage and reconciliation are clear.

This is the difference between knowing vocabulary and being useful. The professional who connects flows, systems, risks, controls and customer impact becomes valuable quickly. The professional who only repeats definitions may sound confident for five minutes and then get lost in the first real issue.

42. Final foundation checklist before moving to topic 2

Before moving to Bank Treasury & Liquidity, the learner should be able to hold the whole map in mind. Markets & Treasury exists because the bank's customer business creates balance-sheet shape, liquidity timing, funding need, market exposure and structural risk. Treasury protects and optimises the bank's own balance sheet. Markets serves clients and manages trading risk in market products. The banking book and trading book must be separated honestly. Liquidity, IRRBB, market risk, credit risk, funding risk, operational risk, model risk, conduct risk and regulatory risk all sit in the landscape.

The learner should also understand that regulation is not separate from practical banking. LCR is short-term liquidity resilience. NSFR is stable funding structure. IRRBB is structural interest-rate risk in the banking book. Market-risk capital covers the applicable trading-book exposures and can also cover FX and commodity exposures outside that book. These frameworks influence products, pricing, systems, reporting, controls and management decisions.

The learner should be able to follow a simple event through the bank. A customer deposit changes funding. A loan drawdown changes cash and asset profile. A payment changes intraday liquidity. A bond purchase changes securities, cash, HQLA and duration. An FX trade changes two currency cash flows and settlement risk. A derivative changes risk profile, valuation and collateral. Each event produces downstream data and control needs.

The learner should be ready to read topic 2 with the right lens. Bank Treasury & Liquidity is not a random deep dive. It is the defensive half of this foundation opened fully. It will explain how daily cash, HQLA, LCR, NSFR, funding, stress, FTP, central-bank access and contingency planning actually work. If topic 1 has landed, topic 2 will feel like entering a room you already know from the map.

Use the next chapter to put this map into daily liquidity practice; the connected Capital Markets chapter explains primary issuance and distribution.

One final practical point matters before leaving the foundation. Markets & Treasury knowledge should never stay trapped inside specialist teams. In a real bank, the value of this domain increases when it travels clearly to product owners, business analysts, developers, testers, operations, finance, compliance, audit and customer-facing teams. A developer building a liquidity feed needs to understand why value date and currency matter. A tester validating an FX flow needs to understand why one failed leg can create settlement risk. A product owner pricing a lending product needs to understand why funding cost and FTP change the commercial truth. An operations analyst investigating a failed securities settlement needs to understand why a single instruction break can affect cash, position, client reporting and risk. A compliance reviewer looking at trading activity needs to understand where conduct, limits and client treatment meet.

This is why the foundation chapter is deliberately broad. It gives everyone the same map before the deeper rooms begin. The next chapters can go very deep because the learner now knows where each detail belongs. Liquidity belongs to survival timing. Money markets belong to short-term cash and collateral. Fixed income belongs to funding, investment, trading, collateral and duration. FX belongs to currency cash, payments and settlement. Derivatives belong to risk transformation and lifecycle control. ALM and FTP belong to structural economics. Market risk belongs to trading-book discipline. Once that placement is clear, detail no longer feels heavy. It becomes useful.

End of Foundations. Next: Bank Treasury & Liquidity Management - the defensive disciplines in full operational depth.

Markets & Treasury Foundations - Practical Addendum

Practical workbook: customer events, trade states, source data, journals, settlement evidence and incident ownership.

Why this addendum exists

Use this workbook after the foundations map to follow a banking event through its operational records. The same trade can be executed, validated, confirmed, matched, instructed, settled, accounted for and reconciled at different times. These are different facts, not synonyms for a single green status.

The examples are fictional. The roles and interfaces illustrate a controlled operating model; bank policy, accounting framework, contracts and market-infrastructure rules determine the actual design.

1. The real operating map of Markets & Treasury

Start with four records: the obligation agreed with the counterparty, the internal risk position, the cash or securities instruction, and the final external account movement. A dealer's ticket creates an agreed exposure; it does not create central-bank money or custody evidence. Treasury needs expected cash before settlement, while Finance recognises the instrument under the applicable accounting policy. Operations proves whether the obligation was discharged.

For example, a corporate deposit arriving from another bank can increase both this bank's settlement cash asset and its customer-deposit liability. A transfer between two customers of this same bank changes deposit ownership but ordinarily creates no external cash inflow. A loan drawdown credited internally creates a loan asset and customer-deposit liability; the customer's later payment to another bank consumes settlement cash. The event type and payment destination determine Treasury's cash effect.

A bond purchase creates market exposure and a settlement obligation before custody receipt. An FX trade creates currency legs for specified value dates. A derivative hedge can reduce rate exposure while creating collateral liquidity needs. A repo raises cash on its start leg and requires repayment on its end leg. Trace each event separately rather than netting unrelated risks into one amount.

2. The desk-to-system-to-report chain

The table is an illustrative front-to-back chain for a Treasury purchase of government bonds. Assume a fictional local-currency purchase with face value 10 million, clean consideration 9.95 million and accrued interest 0.04 million, making dirty consideration 9.99 million. Trade and settlement dates differ; fees, tax and FX are excluded.

Do not count clean consideration as the full settlement amount. Do not infer final custody from trade confirmation. A security may be bought for the liquidity portfolio and still fail HQLA eligibility or operational availability conditions. Confirmation agreement and settlement matching are separate controls, even when one provider supports both.

3. Product-to-risk translation

Ask which risk changes, which risk remains and which new obligation appears. A swap can reduce fixed-rate exposure while leaving basis risk and adding collateral calls. A government bond can have low issuer credit risk but significant duration and liquidation risk. A reverse repo can reduce unsecured credit exposure while creating collateral valuation, legal and settlement dependencies.

For requirements and testing, connect every residual risk to data and an owner. A rate reset requires a benchmark, observation rule and effective date. A collateral position requires location, eligibility, valuation time and encumbrance. A maturity requires contractual terms and evidence of actual repayment.

4. The control questions behind every topic

Use these questions when reviewing a desk ticket, project requirement or report. What has been agreed? Which entity owes what currency, security or margin? When is performance due? Which record owns the economics? Which system and account will discharge the obligation? Which independent checks have passed? What evidence shows final settlement? Which residual risks and accounting balances remain?

The answers must be product-specific. DvP links securities and cash transfers; PvP links two currency transfers. Central clearing substitutes a CCP relationship under its rules and creates margin/default-management obligations. A confirmation verifies agreement on terms. None of these automatically proves all other stages complete. CPMI-IOSCO principles for financial market infrastructures.

If an answer is unknown, identify the missing fact and the decision it blocks. An unknown SSI is an instruction-release issue. An unknown book classification is a risk/capital issue. An unknown final cash status is a liquidity and reconciliation issue.

5. The practical operating rhythm

Frequency follows the obligation and risk. Intraday cash and settlement controls use account balances, payment queues, margin deadlines and market cut-offs. Daily close checks trade completeness, valuation, cash, custody, collateral, GL and aged exceptions. Periodic ALCO decisions review structural funding, IRRBB, FTP assumptions and stress resilience. Model validation, policy and recovery-plan exercises follow their approved schedules rather than a universal calendar.

A report needs a measurement time, data cut-off, entity/currency scope and publication time. A 12:00 dashboard containing 09:00 account data must disclose that age. A late feed should trigger a stale-data warning and a controlled fallback, not silently retain yesterday's green result. Source-event time and ingestion time are distinct fields.

When a settlement window closes, reforecast the affected obligations and identify the next viable window. End-of-day ledger reconciliation cannot undo an intraday missed payment. Conversely, an intraday forecast is not a substitute for official close controls.

6. The missing stakeholder map

Responsibility follows the bank's operating model, but independent challenge must be identifiable. Treasury owns funding and cash decisions; Markets owns authorised execution and positions; trade support validates booking; Operations owns instruction release, settlement investigation and account reconciliation. Independent Risk challenges exposure and assumptions. Product Control verifies valuation/P&L. Finance owns official accounting; Compliance and Regulatory Reporting determine applicable reporting and conduct obligations with Legal support.

For a failed bond purchase, Operations investigates matching or delivery; Treasury replaces the expected cash/position forecast and monitors liquidity; the desk owns any hedge or market exposure; Finance assesses recognition and cutoff; Collateral prevents the unreceived asset being allocated elsewhere. A single coordinator can manage the incident, but that does not transfer each specialist's control responsibility.

Define who can approve an economic amendment, an SSI change, a limit exception and a write-off. These permissions should be separate from ordinary deal capture. Technology and Data teams support validation, lineage and recovery; they do not approve an economic correction solely because they can edit a database.

7. Foundation data fields every learner should recognise

The trade ID is the join key, but not the whole evidence chain. Keep the execution reference, event/version ID, counterparty legal entity, product, book, accounting category, currency/quantity, trade date, contractual value dates, scheduled and actual settlement times, rate/index/conventions and status for each lifecycle stage. Link instructions, external settlement references, valuation runs, journals and reporting submissions back to the trade and event.

For the 9.99 million bond case, retain face quantity, clean price, accrued interest, dirty amount and rounding separately. Cash forecast uses the dirty amount and expected date; valuation uses the approved security and market data; custody uses the security identifier and quantity; Finance uses the accounting classification and recognition facts. An unlabelled amount field cannot safely serve all four consumers.

Version SSI and calendars with effective dates and approval evidence. Preserve the original economics when amending a trade. Risk and accounting consumers need the correcting event and its relationship to the original, including whether they have already processed it.

8. How to read a Markets & Treasury issue

Diagnose an issue in five steps: establish facts, identify unsettled obligations, quantify current and potential impact, assign owners and choose a controlled action. Distinguish a data break from a genuine payment, risk or credit event using independent evidence. A matched confirmation with no account debit is not proof of payment; an unmatched instruction with a completed account movement is not safe to resend.

Suppose the bond purchase is matched but still pending at the custodian cut-off. Operations checks the exact external status and any partial settlement. Treasury retains the pending obligation in the forecast and does not count the securities as available collateral. The desk evaluates market exposure while the contractual trade remains in force. Finance applies its recognition policy rather than cancelling the asset because the cash did not move.

The incident closes when the economic outcome is agreed, instructions and final movements are reconciled, related accounting/risk/reporting states are corrected, costs or claims are resolved and root-cause actions are assigned. Deleting a red dashboard row is not closure evidence.

9. Practical examples that belong in the foundation

Consider a fictional bank receiving an external deposit of 20 million, then funding a customer's 6 million loan drawdown paid to another bank. Assume recognition and settlement happen on the same day and exclude fees, interest and impairment for this simplified journal exercise.

Each row balances. If the drawdown is first credited to the borrower's account here, use two steps: Dr loan / Cr customer deposit at drawdown; Dr customer deposit / Cr settlement cash when the external payment settles. The loan booking alone does not consume external cash. The simplified accounts are illustrative, not a mandatory chart of accounts.

Now revisit the bond. Under an assumed trade-date policy for a qualifying regular-way asset purchase, a simple sketch is Dr securities and separately tracked accrued interest 9.99m / Cr settlement payable 9.99m at recognition; at final settlement Dr settlement payable 9.99m / Cr cash 9.99m. The split of accrued interest, later measurement, impairment and hedge treatment depends on the applicable framework and policy. A settlement-date election for regular-way securities is not permission to ignore derivative recognition until cash moves. IFRS Foundation: IFRS 9.

Reconcile three separate assertions: the payable clears once, the cash account debits 9.99m once, and custody receives the agreed quantity once. A duplicate notification should update evidence without duplicating those entries. A failed or partially settled trade needs the remaining obligation, not a fabricated full settlement.

10. Why Capital Markets is connected but not the same module

Capital Markets is a connected discipline within this learning card. Debt Capital Markets and Equity Capital Markets focus on issuer financing, structuring, underwriting, primary issuance and distribution. Treasury's funding desk is an issuer-side user when the bank raises its own debt; Markets may distribute or trade that debt and Operations settles the issuance and subsequent trades.

A bank's new debt issue follows a connected chain: funding approval and tenor/currency choice, legal documentation, investor execution and allocation, settlement proceeds, liability recognition, interest accrual and maturity-ladder updates. Treasury cannot count a planned issuance as settled liquidity. An underwriting commitment may create risk before investors pay. Investor demand, documentation and operational readiness are distinct constraints.

The Capital Markets chapter covers primary issuance in detail. The foundation keeps the connection visible without repeating bookbuilding, prospectus or underwriting mechanics here.

11. Final alignment note

Use the same event discipline in each subsequent chapter: separate economics, records, instructions and completed movements; identify the residual risk and owner; reconcile external evidence to internal positions and official books. The Money Markets chapter develops short-term borrowing, repo and maturity processing. The Capital Markets chapter follows issuance and investor distribution.

Before moving on, explain why a deposit credit can occur without an external cash inflow, why a confirmation is not final settlement, why regulatory book allocation is not an accounting category, and why DvP reduces principal risk without guaranteeing timely funding. Use the worked cases above to support each answer.

Source anchors

• BIS Basel Committee - Basel III Liquidity Coverage Ratio and liquidity risk monitoring tools
• BIS Basel Committee - Basel III Net Stable Funding Ratio
• BIS Basel Committee - Interest rate risk in the banking book
• BIS Basel Committee - Minimum capital requirements for market risk
• SEC - T+1 settlement cycle implementation statement
• ESMA - Shortening the settlement cycle to T+1 in the EU

End of Markets & Treasury Foundations practical addendum.