Payments - Introduction / Learning brief
Liquidity and settlement risk in payment systems
Your notes
In simple terms / 01
What this means in plain language
Explains how banks fund settlement across real-time gross and deferred net systems, what intraday liquidity is, and how payment queues and settlement risk shape when a payment actually moves.
A bank can hold plenty of wealth overall and still fail to make a payment at the moment it falls due, because settlement needs usable money in the right account at the right time. Intraday liquidity is that ready money available to a bank during the business day. Settlement systems work in two broad ways. Real-time gross settlement (RTGS) moves each payment individually and finally the instant it is funded — safe, but it demands liquidity on hand all day. Deferred net settlement accumulates obligations and settles only the netted difference at set times, which saves liquidity but leaves participants exposed to one another until that moment. When ready money runs short, outgoing payments wait in a queue instead of failing. Settlement risk is the danger that an expected payment is not completed, and much of a system's design exists to keep queues moving and that risk contained.
Complete lesson / 02
Understand the full idea, step by step
A household can be comfortably paid for the month and still go overdrawn on the 29th, because the salary lands on the 30th and the rent left on the 28th. Banks live the same problem, magnified: a bank can hold plenty of assets and still lack usable money in the right account at the exact minute a large payment falls due. This lesson is about that gap — what fills it, and what happens when it is not filled.
Intraday liquidity
Intraday liquidity is the funding a bank can actually use during the business day to make payments at the moment they fall due. It has three main sources: the opening balance on the bank's settlement account at the central bank, incoming payments from other participants as the day unfolds, and intraday credit from the central bank — normally extended only against collateral the bank has positioned in advance. Notice what is not on the list: the bank's buildings, its loan book, its investments. Wealth that cannot pay a specific obligation right now is not intraday liquidity.
| Payments Bank Alfa must send today | EUR 190,000,000.00 |
|---|---|
| Payments Bank Alfa expects to receive | EUR 165,000,000.00 |
| Net position for the whole day (out minus in) | EUR 25,000,000.00 owed out |
| Opening balance at Central Bank Omega | EUR 40,000,000.00 |
| Headroom over the full day | EUR 15,000,000.00 |
Over the whole day, Bank Alfa is fine: its opening balance covers the net difference with room to spare. But settlement does not happen over the whole day — it happens payment by payment. If EUR 60,000,000.00 must leave before 09:30 and only EUR 10,000,000.00 has arrived by then, the account is EUR 10,000,000.00 short at that moment, and the day's comfortable arithmetic does not help. Liquidity is a timing problem before it is an amount problem. These figures are illustrative.
COMMON CONFUSION
“A solvent bank can always make its payments on time.”
Solvency says the bank's assets exceed its obligations overall. Liquidity says it has usable money in the right account at the right moment. A bank can be entirely solvent and still run short at 09:30 because the inflows it is counting on arrive at 11:00. The reverse is also true — a bank can keep paying smoothly for a while even as its solvency deteriorates. They are different measurements, watched by different people, and confusing them is one of the classic beginner errors in this field.
When funding is short, payments queue
In a real-time gross settlement (RTGS) system — one that settles each accepted payment individually and finally, without netting it against others first — a payment that cannot be funded does not fail. It waits in a queue until inflows or fresh liquidity cover it. The queue is the system working as designed, not an error. But it creates a quiet tension in every participant's behaviour: paying early spends your own liquidity for everyone else's benefit, while holding back lets you recycle other banks' inflows — and if every bank holds back, large payments can sit blocked in a circle, each participant waiting for the others to move first.
Gross versus net: the trade-off underneath
Two settlement models sit at opposite ends of a trade-off. RTGS settles each payment now, in central bank money, with no credit exposure between participants — but it demands funded accounts throughout the day. Deferred net settlement (DNS) accumulates obligations, offsets what participants owe each other in both directions, and settles only the net positions at designated times. Netting is far cheaper on liquidity: the amount that finally moves is a fraction of the amount cleared. The price is exposure — between clearing and settlement, participants are effectively trusting each other, and a failure to fund a net position at settlement time would be disruptive for everyone in the net.
Settlement risk
Settlement risk is the risk that settlement does not take place as expected — that a payment or an exchange completes late, partially, or not at all. In a deferred net system it is the exposure participants carry between clearing and the netted settlement. This is why net settlement systems hold defences sized to that risk: collateral, committed lines of liquidity, caps on how far into debit a participant may go, and loss-sharing rules — arrangements designed so settlement completes even if a large participant fails to pay in.
WHAT IF — A high-value payment is still queued as the system's cut-off approaches
What happens: What was routine queue management becomes an incident. If the cut-off passes, the payment may be rejected or carried into an exceptions process, and whatever obligation it was meant to discharge — a money-market repayment, a settlement of another system — is now late.
How it is handled: Maya's operations team and the liquidity desk work it together: move eligible collateral to Central Bank Omega to draw intraday credit, chase expected inflows, re-prioritise the queue, or agree revised timing with the counterparty. The discipline is watching the account all day — balance, queued outflows, expected inflows, collateral headroom — so that the cut-off never arrives as a surprise.
STRICTLY SPEAKING
Strictly speaking, pure RTGS and pure DNS are the two poles of a spectrum, and many real systems are hybrids that queue, offset, and settle in ways that borrow from both. Internationally, the Principles for Financial Market Infrastructures (PFMI) — the global standard for systemically important payment systems — make measuring and managing liquidity risk an explicit requirement, and supervisors expect banks to monitor and stress-test their intraday positions per currency and per system, because liquidity trapped in one system does not help another.
REMEMBER IT
Remember the split: solvency is enough money; liquidity is money now. Gross settlement spends liquidity to remove risk; net settlement saves liquidity by accepting risk and then defending against it.
FOR NOW, REMEMBER
- Intraday liquidity is usable money during the day: opening balance, incoming payments, and collateralised intraday credit from the central bank.
- A bank can be fully solvent and still be short at a specific moment — liquidity is a timing problem.
- In RTGS, an unfunded payment queues rather than fails; queue management is a daily discipline.
- RTGS spends liquidity for safety; deferred net settlement saves liquidity but carries settlement risk, which the system must defend against.
TRY IT YOURSELF
At 15:40, Maya sees a EUR 12,000,000.00 payment from Bank Alfa still queued in Clearing System Delta. The cut-off is 16:00. Bank Alfa's balance sheet is healthy. What is the most accurate reading of the situation?
Queues raise the obvious next question: what does the system itself do when several banks' payments are all waiting on each other? The answer — offsetting algorithms that break the circle — is the next lesson.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
A bank can be solvent overall yet still lack the ready money to settle a specific payment on time.
- 02
Real-time gross settlement spends liquidity for safety, while deferred net settlement saves liquidity but carries settlement risk between participants.
- 03
When funding is short a payment queues rather than fails, so timing and queue management become daily disciplines.
Practical use cases / 04
Where you would use this
A liquidity desk monitors the settlement account through the day to fund outgoing payments before each cut-off.
An operations analyst escalates a high-value payment that has queued for lack of funds as a cut-off approaches.
A treasury team times the release of large payments so liquidity stays available for time-critical obligations.
Worked example / 05
Put the idea into a real situation
Illustrative example: three fictional banks owe money into one deferred net settlement cycle. Meridian Trust owes EUR 900,000.00 to Northwind Bank, Northwind owes EUR 700,000.00 to Cedar Union, and Cedar owes EUR 800,000.00 to Meridian — EUR 2,400,000.00 of gross obligations. Multilateral netting reduces this to positions against the system: Meridian pays EUR 100,000.00, Cedar pays EUR 100,000.00, and Northwind receives EUR 200,000.00, so only EUR 200,000.00 actually settles. In a real-time gross settlement system the same three payments would instead move one by one, each needing its full amount funded at the instant it settles.
Evidence & review / 07
Evidence & review
General model of liquidity and settlement risk in high-value payment systems; queueing, credit, and risk-control specifics are set by each system's rules
What this brief simplifies: The funding calculation and cast scenario are illustrative. Real banks manage many accounts across currencies and systems, and real systems are often gross/net hybrids rather than pure RTGS or pure DNS.
Sources for this brief3
- Official requirement
Principles for financial market infrastructures ↗ — CPMI and IOSCO (Bank for International Settlements) · Principle 7 — liquidity risk
Published by the CPSS (now CPMI) and IOSCO; contains 24 principles plus responsibilities for authorities. This site uses it only for high-level concepts such as settlement finality.
- Market practiceMarch 2003 edition
A glossary of terms used in payments and settlement systems ↗ — CPSS (now CPMI), Bank for International Settlements · Intraday liquidity, settlement risk, RTGS, DNS
Terminology has evolved since this edition; newer CPMI publications refine some definitions.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.