GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX

Articles / Learning brief

High-value, netting, and instant settlement systems compared

Your notes

What this means in plain language

A comparison of the main interbank settlement models — real-time gross settlement, deferred multilateral netting, and instant retail settlement — across speed, liquidity use, finality, and settlement risk.

Banks move money between themselves through shared systems, and those systems make one core choice: settle each payment on its own, or bundle many payments and settle the difference later. Real-time gross settlement, or RTGS, settles each instruction one at a time in central-bank money, so finality arrives within seconds but every payment needs funds available at that moment. Deferred net settlement, or DNS, holds payments through the day and settles only the net amounts owed between members at set times, which saves liquidity but leaves obligations open until the cycle closes. Instant settlement systems bring RTGS-style, payment-by-payment finality to everyday retail transfers around the clock, usually within ten seconds. Each model trades speed, liquidity cost, and risk against the others, and large economies typically run more than one so that different payment types use the design that fits them.

Understand the full idea, step by step

If gross settlement is so safe, why does anyone net? And if netting is so efficient, why do the world's largest payments avoid it? The two questions answer each other. Every interbank settlement system makes one core choice — settle each payment on its own, or accumulate obligations and settle the difference — and everything else about the system follows from that choice.

The two shapes

Under gross settlement, each accepted instruction settles individually and in full, in central bank money, and is final at that moment. Nordbank can rely on every incoming payment as it lands — no exposure to Bank Alfa lingers. Under deferred net settlement, payments accumulate; at the cycle's end the system offsets what the banks owe each other in both directions and settles only the net difference. The obligations are just as real either way. What differs is when they are discharged, how much cash that takes, and who is exposed to whom in the meantime.

Bank Alfa → Nordbank, whole day (gross)EUR 5,200,000.00
Nordbank → Bank Alfa, whole day (gross)EUR 4,830,000.00
Value moved if settled one by one (RTGS)EUR 10,030,000.00
Value moved if settled as one net position (DNS)EUR 370,000.00 — Bank Alfa pays

Netting shrinks the cash that must actually change hands, not the obligations themselves. Under RTGS, over ten million euro of balances move across Central Bank Omega's books during the day, and each payment is final as it settles. Under DNS, a few hundred thousand move once — but until that moment, every accepted payment is an open promise between the banks.

Deferred net settlement (DNS)settlement of the net difference between accumulated obligations, at one or more scheduled times

In a DNS system, the clearing layer continuously tracks each participant's multilateral position — what it owes to and is owed by all others combined. At the settlement time, only these net positions move across the settlement accounts. The design conserves liquidity dramatically, and its cost is the exposure window: between acceptance and settlement, participants are relying on each other to pay.

Three models side by side
RTGS (high-value)Deferred net (DNS)Instant (retail)
Settlement unitEach accepted instruction, individuallyNet position per cycleEach payment, individually
FinalityImmediate on settlementAt the cycle's settlementWithin seconds of acceptance
Liquidity needHigh — full amounts, when each payment settlesLow — only differences moveA pool set aside in advance (prefunding)
Interbank exposureNone once settledOpen until the cycle settlesNone once settled
Typical useHigh-value, time-critical paymentsBulk retail — salaries, bills, collectionsEveryday transfers, around the clock

If RTGS settles payments one by one, does that mean there is no clearing?

No — and this mistake is common enough to flag hard. Every RTGS payment is still exchanged, validated, accepted, and often queued and prioritised before it settles: all of that is clearing. What RTGS removes is prior netting — the accumulation of obligations into a later net position. Clearing and netting are not the same thing; RTGS keeps the first and drops the second.

WHAT IF — An RTGS payment arrives for settlement but Bank Alfa's account at Central Bank Omega cannot cover it

What happens: The payment does not fail — it queues. It waits, in order of priority, until incoming payments or added liquidity cover it. Many RTGS systems also run liquidity-saving mechanisms that spot offsetting queued payments in both directions and release them together, so the queue itself does some of the work netting would have done.

How it is handled: Bank Alfa's treasury sees the queued item and decides: add liquidity against collateral, wait for expected inflows, or re-prioritise so the urgent payment jumps the queue. A queued payment is the system managing liquidity, not a technical failure — but it becomes an incident if nobody is watching the queue.

Instant systems: gross settlement, retail clothes

Instant settlement systems — TIPS in the euro area, FedNow in the United States, and their peers — take the gross, per-payment idea and tune it for everyday transfers: high volumes, small amounts, around the clock. Each payment settles individually and finally in central bank money within seconds. The liquidity answer is prefunding: because central-bank operating hours do not cover nights and weekends, participants park balances in the instant system in advance, and every payment settles from that dedicated pool. Technically these are RTGS-style systems; operationally they are a third animal, always on and sized for millions of small payments rather than a day's worth of very large ones.

STRICTLY SPEAKING

Strictly speaking, real systems blur these categories. Liquidity-saving mechanisms inside an RTGS perform offsetting that looks a lot like netting; some net systems settle many times a day, or continuously against prefunded balances, precisely to shrink the exposure window; and the safeguards a netting system carries — collateral, position caps, loss-sharing rules — are set by each system's rulebook. Treat the three models as points on a spectrum of when finality arrives and who funds the wait.

REMEMBER IT

Gross buys safety with liquidity; netting buys liquidity with exposure; instant buys always-on finality with prefunding. Every settlement system you will ever meet is spending one of those three currencies.

FOR NOW, REMEMBER

  • RTGS settles each accepted instruction individually, immediately, and finally — without prior netting, which is not the same as without clearing.
  • DNS accumulates obligations and settles only net differences: far less cash moves, but exposures stay open until the cycle settles.
  • Instant systems apply gross, per-payment finality to retail transfers around the clock, funded from prefunded balances.
  • The models trade finality timing, liquidity cost, and interbank exposure against each other — which is why large economies run more than one.

TRY IT YOURSELF

Clearing System Delta runs deferred net settlement with one end-of-day cycle. At 11:00, Nordbank accepts a large payment from Bank Alfa through Delta and credits its customer at once. At 14:00, Bank Alfa is suddenly unable to meet its obligations. What is Nordbank's situation?

Nordbank is safe: the payment was accepted and cleared at 11:00, so it is final.

Not this one — Acceptance and clearing are not finality in a DNS system. Nothing settles until the end-of-day cycle, so at 14:00 the 11:00 payment is still an open obligation of Bank Alfa.

Nordbank is exposed: the payment will not settle until the cycle runs, yet it has already given its customer the money — this is exactly the DNS exposure window.

Correct — Right. Between acceptance and the settlement cycle, Nordbank is relying on Bank Alfa to pay. This open exposure is the price of netting's liquidity efficiency — and the reason netting systems carry collateral, caps, and default arrangements.

Nordbank is exposed only if the payment was above the system's per-payment settlement threshold.

Not this one — The exposure comes from the deferral itself, not from the payment's size. In a DNS cycle, every accepted-but-unsettled payment, large or small, remains an open obligation until the net positions settle.

Every model in this lesson ends the same way: balances moving on one trusted book. Next, why that book belongs to the central bank, and what a settlement account actually is.

KEEP GOING

Three things to remember

  1. 01

    RTGS settles each payment individually and finally, using more liquidity for lower risk.

  2. 02

    Deferred net settlement conserves liquidity but keeps obligations open until the netting cycle closes.

  3. 03

    Instant systems extend gross, per-payment finality to round-the-clock retail transfers.

Where you would use this

USE CASE 01

A treasury team choosing which rail to send a same-day high-value transfer through.

USE CASE 02

A central bank deciding which settlement model to operate for a given payment type.

USE CASE 03

A risk analyst measuring how much exposure builds up between two banks during a netting cycle.

Put the idea into a real situation

Illustrative example: a fictional bank, Meridian Trust, must move EUR 40,000,000.00 to a counterparty by 15:00. Sent through an RTGS rail, the full EUR 40,000,000.00 leaves Meridian's settlement account the instant the payment settles, and finality is immediate. Routed instead through a deferred net settlement system, Meridian also receives EUR 37,500,000.00 from other members during the day, so at the 16:00 cycle it settles only the net EUR 2,500,000.00 difference — using far less liquidity, but carrying the open obligation for the hours until the cycle completes.

Evidence & review

REVIEWED 2026-07-13

General settlement-model comparison; named examples are TIPS (euro area), FedNow and CHIPS (United States); safeguards and cycle designs vary by system rulebook

What this brief simplifies: Uses a fictional two-bank, one-cycle model to isolate the trade-offs. Real systems mix features: liquidity-saving mechanisms inside RTGS, frequent or continuous netting cycles, and system-specific default arrangements.

Sources for this brief6
  1. Official requirement

    Principles for financial market infrastructuresCPMI and IOSCO (Bank for International Settlements) · Principles on settlement finality, credit risk, and 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. Market practiceMarch 2003 edition

    A glossary of terms used in payments and settlement systemsCPSS (now CPMI), Bank for International Settlements · Definitions of RTGS, DNS, netting, finality

    Standard definitions for payment, clearing, and settlement terminology used across BIS committee reports and referenced by glossary entries on this site. · Checked 2026-07-12

    Terminology has evolved since this edition; newer CPMI publications refine some definitions.

  3. Market practice

    What is TIPS? (TARGET Instant Payment Settlement)European Central Bank · TIPS settlement model

    Describes TIPS, the Eurosystem service that settles instant payments in central bank money around the clock, in line with the SCT Inst scheme. · Checked 2026-07-12

    TIPS also settles instant payments in Swedish krona and Danish krone; detailed user documentation is published separately by the ECB.

  4. Market practice

    Fedwire Funds ServiceFederal Reserve Financial Services · FedNow settlement model

    Describes the Fedwire Funds Service, the US real-time gross settlement system for immediate, final, and irrevocable US dollar funds transfers. · Checked 2026-07-12

    The Fedwire Funds Service completed its ISO 20022 implementation on 14 July 2025.

  5. Market practice

    CHIPSThe Clearing House · Continuous offsetting against prefunded balances

    Describes CHIPS, the private-sector US dollar high-value clearing and settlement system operated by The Clearing House. · Checked 2026-07-12

    CHIPS migrated to ISO 20022 messaging in April 2024; participant rules are not fully public.

  6. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal · Clearing System Delta worked example and gross-vs-net calculation

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

    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.

Learn this properly

Related briefs

View Articles archive

High-value payments and HVPS+

High-value payment systems are usually central-bank real-time gross settlement systems that settle large payments individually and with finality. The HVPS+ (High Value Payments Plus) guidelines align how ISO 20022 messages are used across them, so a payment reads the same across borders.

READ BRIEF

Settlement through central banks

Why final settlement of interbank payments takes place in central-bank money, how direct and indirect participants are tiered, who may hold a settlement account, and why central-bank money is treated as the safest settlement asset.

READ BRIEF