GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
03 / CLEARING & SETTLEMENT11 MIN

Intraday liquidity and queues

A bank can be solvent and still miss a payment. Intraday liquidity, payment queues, and the timing games inside settlement systems.

NOT STARTED

L0 Explain simply

Analogy: money in savings, nothing in your wallet. You are not poor — your money just is not where it needs to be at lunchtime. Banks have the same problem compressed into every business day. Settling payments one by one, immediately, means a bank needs usable money on hand all day long, not just enough wealth overall. When the money on hand runs short, outgoing payments wait in a queue until something arrives to fund them. And because every bank would rather wait for incoming money than pay out first, a settlement system can slow to a crawl even though everyone is good for the money. Managing this — having enough ready money at the right moments without hoarding it — is a daily discipline with its own name: intraday liquidity management.

L1 Core concepts

Intraday liquidity is the funding available to a bank during the business day to make payments exactly when they fall due. Its sources are the opening balance on the bank's settlement account at the central bank, incoming payments from other participants, and intraday credit from the central bank, normally provided against collateral. In a real-time gross settlement system, a payment that cannot be funded does not fail — it queues, waiting for inflows or fresh liquidity. Queues create strategy: paying early consumes your liquidity to everyone else's benefit; paying late free-rides on others but risks cut-offs and, if everyone does it, gridlock, where large payments sit blocked in a circle. System design and behavioural rules both exist to keep that circle moving.

L2 Practitioner view

In practice a liquidity desk watches the settlement account in real time: balance, queued outflows, expected inflows, collateral headroom. Large payments are timed deliberately — some held for treasury release rather than sent the moment ops is ready — and priority flags decide what may jump the queue. Operations gets involved when a payment lingers: near a cut-off, a queued high-value payment becomes an incident, and the fix may be moving collateral, borrowing, or agreeing timing with the counterparty. Monitoring typically spans each currency and each settlement account separately, because liquidity trapped in one system does not help another. Supervisors expect banks to monitor and stress-test intraday liquidity positions; the sophistication of the tooling varies noticeably between institutions.

L3 Technical details

System-side, modern RTGS services embed liquidity-saving mechanisms. Queued payments are not simply first-in-first-out: offsetting algorithms search the queues for sets of payments that can settle simultaneously against each other, so two banks each short of funds can still exchange offsetting payments. Priority classes, timed transactions, and reservation facilities let participants ring-fence liquidity for critical obligations — settlement of ancillary systems, for example — while ordinary traffic competes for the remainder. Internationally, the CPMI-IOSCO principles make liquidity risk management an explicit requirement for financial market infrastructures, and supervisory frameworks require banks themselves to monitor intraday liquidity. The precise toolset differs per system; the pattern is universal.

SEE THE PAYMENT MOVE

A TARGET2 (T2) settlement (euro RTGS) — swimlane diagramA high-value euro payment settles one-for-one across the banks' accounts in central-bank money, in real time and with finality — each accepted instruction settles on its own, without any prior netting. The full step-by-step description follows this diagram as text.
MESSAGECLEARING OBLIGATIONSETTLEMENTPOSTING
A TARGET2 (T2) settlement (euro RTGS). One payment settling gross. Real RTGS operation depends on intraday liquidity management across CLM and RTGS accounts, queue optimisation, and settlement windows across the whole business day. PLAY IT STEP BY STEP →
Read the steps as text
  1. 01Message
    Bank Alfa submits the payment to T2Bank Alfa (sending bank) → TARGET2 (T2) · pacs.009

    Bank Alfa's payments desk sends a high-value interbank payment (a pacs.009) to TARGET2, which processes it the instant it arrives rather than batching it for a later cycle. Nothing has moved yet — it is an instruction.

  2. 02Processing
    T2 checks Bank Alfa's available liquidityTARGET2 (T2)

    TARGET2 checks whether Bank Alfa's RTGS account holds enough available liquidity — drawing on the Central Liquidity Management (CLM) component — to cover the full amount before it settles anything.

  3. 03Settlement
    T2 settles the payment in central-bank moneyBank Alfa (sending bank) → Nordbank (receiving bank)

    With liquidity confirmed, T2 debits Bank Alfa's account and credits Nordbank's account at the central bank, one payment at a time. RTGS settles each accepted instruction individually, without any prior netting, and the transfer is final the instant it settles.

    • DR Bank Alfa's RTGS account at the central bankEUR 2,000,000.00
    • CR Nordbank's RTGS account at the central bankEUR 2,000,000.00
  4. 04Message
    Nordbank is confirmed of the settled paymentTARGET2 (T2) → Nordbank (receiving bank)

    TARGET2 tells the receiving bank that the funds are on its account at the central bank and are final, with the details of the payment it needs to apply.

  5. 05Posting
    Nordbank books the incoming fundsNordbank (receiving bank)

    Because the interbank leg already settled with finality, Nordbank records the credit on its own ledger without waiting for anything else. The payment is complete end to end.

    • CR Incoming settlement account at NordbankEUR 2,000,000.00
Sources for this topic2
  1. Official requirement

    Principles for financial market infrastructuresCPMI and IOSCO (Bank for International Settlements) · Principle 7 (Liquidity risk)

    International risk-management standards for systemically important payment systems and other financial market infrastructures. · Checked 2026-07-12

    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.

  2. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: The queue and gridlock description is a simplified model; actual queue disciplines, offsetting algorithms, and priority schemes are specific to each settlement service.

    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.

Deepest material on this page: L3 Technical details. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.