Banking And Finance Mathematics | Payments, Clearing, Settlement and Intraday Liquidity Mathematics

Payments and settlement mathematics studies how obligations move from instruction to final discharge while controlling credit risk, liquidity risk, principal risk, timing risk and operational capacity. A payment is not complete merely because one customer sees “sent”. Behind the screen are ledgers, queues, clearing rules, netting, settlement accounts, collateral, intraday credit and finality. In securities and FX markets, the mathematics must also link two legs so value is not delivered without payment.

For readers searching for payments mathematics, settlement mathematics, clearing and settlement, RTGS, real time gross settlement, net settlement, payment netting, settlement finality, intraday liquidity, payment queue, delivery versus payment, DVP, payment versus payment, PVP, securities settlement, FX settlement risk, Herstatt risk, payment system liquidity or MEPS+ Singapore, the central distinction is between message, obligation, clearing and final settlement. They are related stages, not synonyms.

The CPMI-IOSCO Principles for Financial Market Infrastructures require systemically important infrastructures to manage credit and liquidity risks robustly, maintain sufficient liquid resources for same-day and where appropriate intraday settlement, and provide clear settlement finality. In Singapore, MAS operates MEPS+, a real-time gross settlement system used for SGD interbank funds transfers and settlement of Singapore Government Securities and MAS securities. MAS’s current directory also lists FAST, IBG and MEPS+ among designated payment-system activities. This page develops the mathematics behind those systems. It is educational, not operational or regulatory advice.

50-Second Router

• Payment instruction: message requesting transfer of value; not necessarily final settlement.
• Clearing: calculation/transmission of obligations before settlement.
• Settlement: discharge of obligations by transfer of funds or assets.
• Gross settlement: each instruction settles individually.
• Net settlement: offset obligations and settle net balances.
• RTGS: real-time gross settlement; finality transaction by transaction as liquidity permits.
• Queue: payments wait when liquidity or controls prevent immediate settlement.
• Intraday liquidity: cash/collateral needed throughout the day, not just at close.
• Settlement finality: point after which transfer cannot be revoked under system rules/law.
• DVP: securities delivery occurs if and only if payment occurs under linked settlement.
• PVP: one currency settles if and only if the other currency settles, reducing FX principal risk.
• Netting: reduces gross funding needs but creates dependency on netting rules and participant performance.
• Verification: reconcile opening balances + settled inflows − settled outflows to closing balances and prove no participant spends unavailable liquidity.

The Central Proposition: Payments Are Flows Through a Constrained Network

A payment system can be represented as participants connected by directed obligations. If Bank A owes Bank B S$100 and B owes A S$90, gross obligations total S$190 but bilateral net obligation is only S$10 from A to B. Netting can reduce liquidity dramatically. But it changes timing and dependency: if one participant fails before settlement, obligations may need recalculation or loss allocation depending on the system.

RTGS takes the opposite approach: settle each payment individually in real time, reducing build-up of settlement credit exposure but increasing intraday liquidity needs. Payment-system design is therefore a mathematical trade-off among finality, liquidity usage, credit exposure and operational throughput.

Adrian’s rule is to distinguish gross economic value transferred from liquidity needed to settle it. Efficient systems can settle enormous gross values with much less net liquidity, but only through careful timing, netting, collateral and queue design.

1. Payment instruction

Payment instruction is message authorising/requesting a transfer of funds. It starts the process but may not itself move final money. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Instruction contains payer,payee,amount,value date. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. A mobile-app confirmation is not necessarily final settlement between banks. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

2. Payment obligation

Payment obligation is amount one participant owes another. It is the economic claim to be discharged. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Obligation O_ij from i to j. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Messages can be cancelled before obligation becomes final depending on system. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into clearing. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

3. Clearing

Clearing is process of transmitting,reconciling and possibly netting payment obligations before settlement. It determines who owes whom how much. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Net obligation derived from gross instructions. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Clearing can occur without final transfer of settlement asset. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payment systems. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

4. Settlement

Settlement is discharge of obligations by transfer of settlement asset. It completes payment at infrastructure level. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Debit payer settlement account, credit receiver account. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Customer ledger credit before interbank finality can create provisional exposure. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into settlement. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

5. Settlement asset

Settlement asset is asset used to discharge obligations. Central-bank money minimises settlement-bank credit risk where available. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Balances in central bank/commercial settlement bank. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Commercial bank money introduces settlement-bank risk. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

6. Central-bank money

Central-bank money is claims on central bank used for settlement. It has minimal credit risk in domestic currency context. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. RTGS accounts at central bank. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Access is limited to eligible participants. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into settlement. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

7. Commercial-bank money

Commercial-bank money is deposit claims on commercial bank used for settlement. It introduces credit/liquidity risk to settlement bank. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Transfer across commercial bank books. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Large concentration in one settlement bank can be systemic. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into settlement. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

8. Finality

Finality is legally defined point when transfer becomes irrevocable/unconditional. It removes uncertainty about reversal. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. System rules specify final settlement time. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Operational message status is not enough without legal finality. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

9. Value date

Value date is date on which payment/settlement has economic effect. It anchors interest and obligations. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Cash available for value date. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Processing date can differ from value date. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into operations. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

10. Real-time gross settlement

Real-time gross settlement is individual payments settle continuously in real time. It reduces settlement-credit build-up. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Each payment debited/credited separately. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. High gross liquidity need without optimisation. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into RTGS. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

11. Gross settlement

Gross settlement is settlement of each obligation separately. It preserves original transaction amounts. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Liquidity need can approach peak gross outflow. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. It can be expensive in liquidity. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

12. Net settlement

Net settlement is settlement only of net obligations after offsetting. It reduces liquidity usage. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Net_i=Σoutflows_i−Σinflows_i. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Participant default can disrupt multilateral positions. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into DNS. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

13. Deferred net settlement

Deferred net settlement is obligations accumulated/netted then settled at designated times. It saves liquidity but defers finality. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. End-cycle net positions settled. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Credit exposures accumulate during cycle. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payment systems. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

14. Bilateral netting

Bilateral netting is offset obligations between two parties. It reduces two-way gross flows. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Net_AB=max(O_AB−O_BA,0). Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Legal enforceability is essential. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into netting. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

15. Multilateral netting

Multilateral netting is offset obligations across many participants. It can dramatically reduce system liquidity. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Net_i=Σ_j O_ij−Σ_j O_ji. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. System-wide dependency increases. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into clearing. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

16. Netting efficiency

Netting efficiency is reduction in settlement liquidity from gross to net. It quantifies liquidity savings. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Efficiency=1−Σ|Net debit|/Gross value under chosen metric. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. High netting does not eliminate credit risk automatically. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

17. Liquidity saving mechanism

Liquidity saving mechanism is algorithm/rule coordinating queued payments to reduce liquidity usage. It combines RTGS finality with offsetting opportunities. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Settle compatible payment cycles/net positions. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Complexity and queue incentives matter. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into RTGS. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

18. Payment queue

Payment queue is ordered/unordered list of unsettled instructions awaiting liquidity/conditions. It manages scarce intraday funds. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Queue balance evolves with incoming liquidity. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Long queues can create gridlock. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into intraday liquidity. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

19. FIFO queue

FIFO queue is first-in-first-out priority. It is simple and fair by time. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Oldest eligible payment settles first. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. May waste liquidity if a large early payment blocks many small ones. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into queue design. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

20. Priority queue

Priority queue is participants assign payment priorities. It protects critical payments. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. High-priority settled before ordinary. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Everyone marking everything urgent destroys usefulness. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into queue design. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

21. Bilateral offset in queue

Bilateral offset in queue is two opposite queued payments settle together with less liquidity. It saves cash. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Settle A→B and B→A net. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Requires algorithm/rule permissions. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into LSM. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

22. Multilateral offset in queue

Multilateral offset in queue is cycle of payments settled simultaneously. It unlocks gridlock. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Find payment set whose net liquidity need fits balances. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Computation/governance complexity rises. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into LSM. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

23. Gridlock

Gridlock is many payments wait because each participant holds liquidity waiting for incoming payments. It can freeze system despite enough total liquidity. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Circular dependency among queues. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Coordination mechanism can unlock. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into RTGS. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

24. Throughput

Throughput is value/number of payments settled over time. It measures system processing performance. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Throughput rate=value settled/hour. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. High throughput can consume liquidity early; low throughput can create deadline risk. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into operations. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

25. Throughput guideline

Throughput guideline is rule encouraging participants to settle proportions by certain times. It reduces late-day concentration. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Target % by midday etc. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Rigid targets can be costly in legitimate liquidity patterns. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into RTGS. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

26. Intraday liquidity

Intraday liquidity is funds/collateral available to make payments during day. It is needed even when end-of-day net position is small. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Peak net cumulative outflow determines need. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. End-of-day cash can hide noon shortfall. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into bank treasury. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

27. Peak intraday need

Peak intraday need is maximum cumulative net outflow before inflows. It measures minimum opening/credit liquidity under sequence. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Peak=max_t cumulative(outflows−inflows). Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Payment ordering changes peak need. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into intraday. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

28. Daylight overdraft

Daylight overdraft is temporary intraday negative central-bank account balance under allowed arrangements. It provides settlement liquidity. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Exposure exists only intraday if repaid. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Limits/collateral/pricing apply by system. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

29. Intraday credit

Intraday credit is central-bank/system credit for settlement during day. It reduces payment delays. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Credit line backed/unbacked per rules. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Availability can change under stress. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into RTGS. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

30. Collateralised intraday credit

Collateralised intraday credit is daylight liquidity secured by eligible assets. It converts collateral into payment capacity. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Credit≈CollateralValue×(1−haircut). Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Encumbering collateral has opportunity cost. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into intraday. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

31. Liquidity buffer

Liquidity buffer is cash/reserves available for payments. It prevents queue build-up. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. OpeningReserve+credit capacity. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Too little creates delays; too much has opportunity cost. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

32. Payment timing

Payment timing is schedule of outgoing/incoming instructions. It strongly influences liquidity need. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Same daily net can produce different peak exposure. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Aggregating daily totals hides sequence. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into intraday. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

33. Payment coordination

Payment coordination is timing payments relative to expected inflows. It reduces liquidity use but can cause strategic delay. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Optimise sequence subject to deadlines. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Everyone delaying can cause gridlock. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into game theory. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

34. Free-riding

Free-riding is participant delays payments expecting others to provide liquidity first. It is collective-action problem. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Private liquidity saving can increase system queue. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Rules/incentives address. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payment systems. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

35. Settlement delay

Settlement delay is payment settles later than intended. It can cause penalties/liquidity cascades. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Delay time=settlement timestamp−submission timestamp. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Late settlement can propagate to downstream payments. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into operations. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

36. Deadline risk

Deadline risk is large queued value near end of settlement day. It increases chance of failed settlement. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Measure late-day queue concentration. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Operational outage late in day becomes critical. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into resilience. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

37. Credit risk in settlement

Credit risk in settlement is counterparty may fail before meeting obligation. It arises especially when obligations are deferred. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Exposure can be replacement/principal risk. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Gross/netting structures alter exposure. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

38. Liquidity risk in settlement

Liquidity risk in settlement is participant lacks funds when due though solvent later. It can delay system-wide settlement. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Shortfall=max(required−available liquidity,0). Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Solvency does not guarantee payment capacity. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

39. Principal risk

Principal risk is risk one leg delivered but countervalue not received. It can equal full transaction principal. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Eliminated by DVP/PVP mechanisms. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Market-value VaR can understate principal risk. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into settlement. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

40. Replacement-cost risk

Replacement-cost risk is loss of unrealised gain if counterparty fails before settlement. It is smaller than principal but market-sensitive. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. ReplacementCost=max(MTM,0). Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Volatile markets can increase quickly. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into settlement. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

41. Settlement bank risk

Settlement bank risk is risk commercial bank providing settlement asset fails. It affects participants/FMI. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Exposure to balances at settlement bank. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Central-bank money preferred where practical. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

42. Nostro account

Nostro account is bank account held with correspondent in foreign currency. It supports cross-border payments. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Nostro balance funds outgoing payments. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Trapped/insufficient nostro creates FX payment delays. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into correspondent banking. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

43. Vostro account

Vostro account is correspondent’s account on bank’s books. It is opposite perspective of nostro. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Ledger liability to correspondent. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Perspective errors are common. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into correspondent banking. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

44. Correspondent banking

Correspondent banking is banks provide payment services/accounts to each other across currencies/jurisdictions. It enables global settlement. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Payments route through nested accounts. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Chains create timing, credit and compliance complexity. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into cross-border payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

45. Securities settlement

Securities settlement is final transfer of securities ownership/cash. It requires coordination of asset and money legs. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Book-entry security + payment. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Failing one leg creates principal risk. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into DVP. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

46. Delivery versus payment

Delivery versus payment is linking securities delivery to payment so one occurs iff other occurs. It reduces principal risk. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. DVP condition: DeliverSecurity ⇔ ReceiveFunds. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Timing mismatch undermines protection. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

47. DVP Model 1

DVP Model 1 is gross securities and gross funds simultaneous settlement. It offers strong finality with high liquidity need. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Trade-by-trade DVP. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Liquidity usage can be large. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into securities. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

48. DVP Model 2

DVP Model 2 is gross securities with net funds settlement. It mixes gross asset transfer/net cash. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Funds netted end cycle. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Settlement-bank/credit exposures differ. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into securities. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

49. DVP Model 3

DVP Model 3 is net securities and net funds settlement. It maximises netting efficiency Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Net obligations settle. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Default management more complex. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into securities. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

50. Payment versus payment

Payment versus payment is FX settlement where one currency settles iff other settles. It reduces Herstatt/principal risk. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. PVP condition currency A final ↔ currency B final. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Liquidity remains needed in each currency. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into FX settlement. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

51. Herstatt risk

Herstatt risk is FX principal risk from time-zone/asynchronous settlement. It can expose full currency principal. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. One currency paid before other. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. PVP/CLS-style mechanisms mitigate. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into FX. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

52. CLS

CLS is multicurrency settlement infrastructure using PVP principles for eligible FX. It reduces principal settlement risk. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Matched instructions, pay-in schedules, simultaneous settlement. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Not all currencies/trades are eligible. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into FX settlement. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

53. Settlement finality risk

Settlement finality risk is uncertainty that a transfer thought completed can be revoked. It undermines liquidity/credit certainty. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Legal/system rules define irrevocability. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Cross-border insolvency law can complicate. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

54. Reconciliation

Reconciliation is matching internal/system records. It ensures ledger integrity. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Compare amount,currency,date,ID,status. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Unreconciled breaks can create duplicate/missing payments. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into operations. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

55. Exception queue

Exception queue is payments/records needing manual/automated investigation. It concentrates operational risk. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Aging and value metrics monitor. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Backlogs can delay settlement. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into operations. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

56. Straight-through processing

Straight-through processing is automation from instruction to settlement without manual intervention. It reduces errors/time. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. STP rate=% automated. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Bad reference data can automate wrong processing faster. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into operations. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

57. Message standard

Message standard is structured format for payment data. It improves interoperability. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. ISO 20022 is widely used. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Message conformity does not guarantee semantic/data quality. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

58. ISO 20022

ISO 20022 is international financial messaging standard. It provides rich structured payment data. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. XML/message definitions by business process. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Migration is operational/data project, not settlement mechanism itself. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

59. Payment identifier

Payment identifier is unique reference for tracing transaction. It supports reconciliation and duplicate control. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Unique key across lifecycle. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Poor uniqueness creates duplicate payments. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into operations. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

60. Duplicate payment

Duplicate payment is same obligation settled more than once. It is operational loss risk. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Duplicate detection by keys/amount/date/payee. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Overly broad matching can block legitimate repeats. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into controls. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

61. Checksum

Checksum is validation digit/method catching data-entry errors. It reduces invalid instructions. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. MOD algorithms common. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Checksum validates format, not account ownership. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

62. IBAN

IBAN is international account-number format with checksum in relevant countries. It standardises cross-border account identification. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. MOD 97 validation. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Singapore accounts do not use IBAN domestically in the same way as IBAN countries. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

63. Routing identifier

Routing identifier is code identifying bank/branch/system endpoint. It directs message correctly. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. SWIFT/BIC/local clearing codes. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Correct routing code does not guarantee beneficiary identity. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

64. SWIFT message

SWIFT message is secure financial messaging instruction. It is not itself settlement money. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Messages instruct correspondent transfers. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Confusing messaging with settlement is common. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into cross-border. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

65. FAST

FAST is Singapore Fast and Secure Transfers system. It supports near-real-time retail interbank transfers under designated payment-system framework. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Retail instruction settles through system arrangements. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Retail customer instant experience still relies on interbank settlement infrastructure. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into Singapore payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

66. PayNow

PayNow is Singapore proxy-based retail payment service using identifiers linked to bank accounts. It simplifies addressing for FAST transfers. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Proxy→bank account mapping. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Proxy service is not separate settlement asset. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into Singapore payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

67. GIRO

GIRO is batch/deferred account transfer mechanism. It is efficient for recurring payments. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Net/batch processing can apply. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Settlement timing differs from FAST/RTGS. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into Singapore payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

68. MEPS+

MEPS+ is MAS Electronic Payment System used for SGD interbank funds and securities settlement. It is Singapore’s core RTGS/book-entry infrastructure. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. RTGS accounts and securities accounts at MAS. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Retail transfers and MEPS+ serve different transaction types/layers. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into Singapore payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

69. SGS settlement

SGS settlement is settlement of Singapore Government Securities through book-entry system. It uses DVP in MEPS+ Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Securities transfer and RTGS cash leg linked. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Securities settlement liquidity matters. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into Singapore. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

70. MAS securities settlement

MAS securities settlement is book-entry settlement for MAS-issued securities. It shares core infrastructure. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. DVP/RTGS mechanics. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Operational cutoffs and eligibility govern. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into Singapore. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

71. Retail payment

Retail payment is high-volume lower-value customer transfer. It prioritises speed, cost and availability. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. FAST/card/QR etc. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Retail front-end does not eliminate settlement risk. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

72. Wholesale payment

Wholesale payment is large-value bank/financial-market transfer. It often uses RTGS due systemic importance. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. High value, time-critical. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Low transaction count can represent enormous value. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

73. Card authorisation

Card authorisation is real-time approval of card transaction against account/credit criteria. It precedes clearing/settlement. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Authorised amount reserves/approves spending. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Authorisation is not final merchant settlement. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into cards. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

74. Card clearing

Card clearing is exchange/calculation of card transaction obligations. It precedes issuer/acquirer settlement. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Scheme calculates net obligations. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Chargebacks can later adjust. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into cards. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

75. Card settlement

Card settlement is transfer of net funds among issuers/acquirers/scheme arrangements. It completes financial leg for batch. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Net settlement amounts. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Merchant funding timing can differ. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into cards. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

76. Chargeback

Chargeback is reversal/dispute process after card transaction. It changes obligations post-clearing under rules. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Reason codes/evidence deadlines. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. It does not mean original authorisation was invalid technically. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into cards. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

77. Merchant settlement

Merchant settlement is payment to merchant after acquiring/processing adjustments. It can be delayed relative to customer purchase. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Gross sales−fees−refunds/chargebacks. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Timing creates working capital. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into cards. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

78. Instant payment

Instant payment is customer transfer completed/credited quickly, often seconds. It requires 24/7 fraud/liquidity/settlement arrangements. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Service-level instant ≠ necessarily transaction-by-transaction central-bank settlement. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Architecture varies. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into retail payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

79. Prefunding

Prefunding is participants deposit funds before settlement to guarantee obligations. It reduces credit risk but ties up liquidity. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Available payments ≤prefunded amount+inflows. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. High prefunding lowers flexibility. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payment systems. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

80. Credit line

Credit line is committed liquidity source for settlement. It reduces payment delays. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Available liquidity includes line subject to terms. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Line may fail if provider stressed. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

81. Committed repo

Committed repo is prearranged securities-for-cash funding. It converts collateral to liquidity. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Cash≈collateral×(1−haircut). Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Operational readiness and haircut stress matter. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into liquidity. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

82. Committed FX swap

Committed FX swap is prearranged currency liquidity source. It helps meet foreign-currency settlement. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Exchange one currency now/return later. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Counterparty and basis risk remain. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

83. Haircut

Haircut is reduction in collateral lending value. It protects liquidity provider. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. EligibleValue=MV×(1−h). Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Haircuts can rise in stress. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into collateral. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

84. Collateral substitution

Collateral substitution is replace pledged asset with another eligible asset. It manages opportunity cost. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Maintain required collateral value. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Substitution timing can create operational risk. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into settlement. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

85. Encumbrance

Encumbrance is asset already pledged/restricted. It reduces available settlement liquidity. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Unencumbered collateral usable. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Double counting pledged collateral overstates capacity. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into liquidity. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

86. Settlement fail

Settlement fail is transaction not settled by expected date. It can create replacement/liquidity/penalty effects. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Fail rate=value/count failed. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. High fails can signal operational/liquidity stress. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into securities. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

87. Fail penalty

Fail penalty is charge/incentive for late settlement. It encourages timely delivery. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Penalty depends on amount/days/rules. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Penalty alone cannot create missing securities/cash. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into securities. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

88. Buy-in

Buy-in is process requiring purchase of securities to resolve delivery fail under certain regimes. It restores settlement at cost. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Replacement purchase difference charged per rules. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Market stress can make buy-in expensive. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into securities. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

89. Central securities depository

Central securities depository is infrastructure holding securities and enabling book-entry transfer. It supports issuance/settlement integrity. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Accounts represent holdings. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. CSD risk differs from custodian bank risk. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

90. Securities settlement system

Securities settlement system is rules/infrastructure for transferring securities. It coordinates delivery/finality. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Can be integrated with CSD. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Not every CSD/SSS has identical roles. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

91. Central counterparty

Central counterparty is entity interposed between buyers/sellers via novation. It manages counterparty risk with margin/default resources. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. CCP becomes buyer to every seller/seller to every buyer. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Clearing concentration creates systemic importance. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

92. Novation

Novation is original contract replaced by contracts with CCP. It centralises exposure. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. A-B becomes A-CCP and CCP-B. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Legal finality of novation matters. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into clearing. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

93. Initial margin

Initial margin is collateral against potential future exposure. It protects CCP. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. IM model based on stress/volatility. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. It consumes participant liquidity. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into CCP. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

94. Variation margin

Variation margin is cash/collateral settling current mark-to-market. It prevents exposure accumulation. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. VM≈daily/intraday MTM change. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Large VM calls create liquidity stress. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into CCP. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

95. Default fund

Default fund is mutualised resources available after defaulter resources in CCP waterfall. It supports extreme loss coverage. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Waterfall sequence applies. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Mutualisation creates contingent participant exposure. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into CCP. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

96. Default waterfall

Default waterfall is ordered resources used after participant default. It allocates losses. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Defaulter margin→default fund etc per rules. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Exact sequence is CCP-specific. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into clearing. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

97. Settlement guarantee

Settlement guarantee is FMI/CCP commitment structure ensuring completion under specified defaults. It changes participant credit exposure. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Backed by financial resources. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Guarantee does not eliminate liquidity risk. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into FMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

98. Cover 1

Cover 1 is resource standard involving largest participant default under certain PFMI contexts. It provides stress resilience. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Resources cover largest exposure/liquidity obligation. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Applicability differs by FMI type. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

99. Cover 2

Cover 2 is higher standard for certain complex/systemic CCPs covering two largest participant defaults. It raises resilience. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Resources cover two largest aggregates. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Not all FMIs are Cover 2. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

100. Liquidity stress test

Liquidity stress test is test of FMI/bank ability to settle under default/market shocks. It evaluates same-day/multiday needs. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Scenario peak obligations and resources. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Average liquidity is irrelevant at peak. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

101. Default liquidity shortfall

Default liquidity shortfall is cash need after participant fails to pay. It can exceed credit loss because timing matters. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Shortfall=Obligation due−available liquid resources. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Collateral may be valuable but not immediately cash. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into FMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

102. Replenishment

Replenishment is restoring liquidity/default resources after use. It supports continued operation Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Rules define contributions/borrowing. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. One successful settlement day does not end crisis. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

103. Operational resilience

Operational resilience is ability to keep critical settlement services running through disruption. It is essential because time-critical payments cannot wait. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Recovery time objectives/secondary sites. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Capital cannot compensate for unavailable system today. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into PFMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

104. Recovery time objective

Recovery time objective is target time to restore critical system. It constrains outage duration. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. RTO in hours. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Data integrity must also be restored. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into operations. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

105. Business continuity

Business continuity is plans/resources for continuing operations. It reduces outage settlement risk. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Secondary sites/processes. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Untested plans may fail. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into operations. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

106. Cyber risk

Cyber risk is risk attack disrupts/confidentiality/integrity. It can stop or corrupt payments. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Controls+detection+recovery. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Fraud and outage can create systemic queues. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

107. Third-party risk

Third-party risk is dependency on cloud/network/vendor. It can create correlated outages. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Map critical service providers. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Outsourcing does not outsource responsibility. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into FMI. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

108. Settlement concentration

Settlement concentration is large share of flows through one participant/system. It raises systemic impact. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Concentration ratios. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Efficiency can increase systemic dependency. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into systemic risk. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

109. Network contagion

Network contagion is one payment failure causes others to miss obligations. It arises from interconnected flows. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Graph/fixed-point models. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Netting can reduce liquidity but increase dependency. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into systemic. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

110. Eisenberg-Noe network

Eisenberg-Noe network is mathematical clearing model for interbank liabilities under defaults. It studies payment fixed points. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Payments satisfy liability constraints. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Simplified recovery/no fire-sale assumptions limit realism. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into network risk. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

111. Payment fixed point

Payment fixed point is set of payments consistent with each participant resources/liabilities. It formalises network clearing under default. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. p=min(obligation,resources+incoming proportions). Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Multiple mechanisms beyond model matter in real systems. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into systemic. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

112. Liquidity recycling

Liquidity recycling is incoming settled funds reused for outgoing payments. It reduces external liquidity need. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Same unit of money settles many payments daily. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Delays reduce recycling efficiency. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into RTGS. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

113. Velocity of settlement liquidity

Velocity of settlement liquidity is gross settled value per unit of liquidity. It measures recycling efficiency. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Velocity=GrossValueSettled/AverageLiquidityUsed. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. High velocity can mean efficiency or thin buffer. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

114. Liquidity cost

Liquidity cost is opportunity/funding cost of holding settlement balances/collateral. It creates incentive to delay/net. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Cost≈liquidity×intraday funding rate. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Ignoring liquidity cost makes RTGS design look free. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

115. Delay cost

Delay cost is economic/operational cost of late settlement. It offsets liquidity-saving incentives. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Penalty/reputation/downstream impact. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Participants trade off liquidity vs delay. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into queue economics. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

116. Optimisation of payment timing

Optimisation of payment timing is choose settlement sequence minimizing liquidity+delay cost. It is an operations-research problem. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Min Σliquidity cost+delay penalties subject to balances/deadlines. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Private optimum can conflict with system optimum. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

117. System liquidity

System liquidity is aggregate settlement resources of participants. It determines throughput but distribution matters. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Total reserves/collateral. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Enough total liquidity can coexist with one participant shortfall. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into RTGS. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

118. Liquidity distribution

Liquidity distribution is which participant holds settlement cash at each time. It matters as much as aggregate total. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Vector of balances. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Cash trapped with net receivers can create payer queues. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into RTGS. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

119. Intraday redistribution

Intraday redistribution is payments/credit/repo shift liquidity among banks. It supports flow completion. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Incoming payments recycle reserves. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Stress can cause hoarding. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

120. Liquidity hoarding

Liquidity hoarding is participants retain cash instead of paying due to uncertainty. It can amplify gridlock. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Lower outgoing payments despite adequate balance. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Individually rational behaviour can harm system. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into systemic liquidity. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

121. Settlement currency

Settlement currency is currency in which obligation is finally discharged. It determines required liquidity source. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. SGD,USD etc. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Cross-currency positions need separate liquidity. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

122. Multicurrency settlement

Multicurrency settlement is coordinated settlement across currencies. It adds timing/time-zone complexity. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. PVP or correspondent arrangements. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. One currency surplus may not solve another. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into FX settlement. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

123. Time-zone risk

Time-zone risk is currencies/systems open at different times. It creates settlement gaps. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Payment windows overlap imperfectly. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. PVP infrastructure mitigates. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into cross-border. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

124. Cross-border payment chain

Cross-border payment chain is sequence of correspondent/intermediary banks. It increases fees,time and reconciliation points. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Sender→correspondents→receiver. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Each intermediary adds operational/compliance dependencies. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

125. Payment transparency

Payment transparency is ability to know fees,FX rate,status and timing. It improves customer/operational control. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Track end-to-end status. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Opaque deductions complicate reconciliation. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into cross-border. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

126. Settlement certainty

Settlement certainty is confidence payment will be final at known time. It supports downstream reuse of funds. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Finality rules+operational reliability. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Provisional credits create uncertainty. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into payments. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

127. Liquidity efficiency

Liquidity efficiency is amount of final value settled per unit of scarce liquidity. It is core design metric. Payment mathematics becomes reliable only when instruction, clearing, settlement asset and finality are separated.

Mathematics. Efficiency=gross value/liquidity usage. Track currency, participant, timestamp and legal status. Intraday sequence can matter even when daily net totals are identical.

Failure mode. Maximising efficiency alone can increase delay/credit risk. Jo’s diagnostic is to ask whether money has actually settled finally or whether only a message/claim has moved.

Connection. This feeds directly into system design. Ryan would replay the same obligations under gross, bilateral-net and multilateral-net structures to compare liquidity and credit exposure.

Worked Example 1: Bilateral Netting

Bank A owes B S$100m; B owes A S$70m. Gross settlement requires S$170m of two-way transfers. Bilateral net settlement requires one S$30m payment from A to B.

Liquidity need falls dramatically, but finality is delayed until netting cycle and depends on enforceable netting rules.

Efficiency is not free; it changes risk structure.

Worked Example 2: Multilateral Netting

A owes B 100; B owes C 90; C owes A 80. Gross value=270. Net positions: A pays 20, B receives 10? Calculate carefully: A out100 in80 => -20; B in100 out90 => +10; C in90 out80=>+10. Total net debit=20.

Only S$20m external settlement liquidity can discharge S$270m gross obligations in the idealised multilateral net if all participants perform.

The default of A before final settlement can therefore have disproportionate effect.

Worked Example 3: Intraday Peak

Bank begins with S$50m reserves. At 09:00 pays 80m; 10:00 receives 60m; noon pays 40m; 14:00 receives 30m. Cumulative net after first payment is −30m relative to opening balance, requiring 30m intraday credit; end day balance is 20m.

End-of-day liquidity looks positive, yet morning peak need is material.

Intraday models must preserve sequence.

Worked Example 4: Liquidity Recycling

A bank receives S$100m at 10:00 and uses the same funds to settle S$100m outgoing at 10:05. One S$100m unit supports S$200m gross flow across two instructions.

Across a day, repeated incoming/outgoing cycles can create settlement-liquidity velocity far above one.

Queue delays can interrupt this recycling and raise system liquidity need.

Worked Example 5: DVP

Investor buys S$50m bonds. Without DVP, buyer could pay cash while seller fails to deliver securities, losing principal exposure. DVP conditions bond transfer on payment finality.

The mechanism converts two separate obligations into linked settlement: either both settle or neither settles under the system model.

It reduces principal risk but still requires cash/securities liquidity.

Worked Example 6: PVP

Bank A delivers USD 10m for SGD at agreed FX rate. Without PVP, USD can settle hours before SGD; counterparty failure creates full principal risk. PVP links final USD transfer to final SGD transfer.

The exchange-rate market risk before settlement remains, but principal loss from asynchronous delivery is greatly reduced.

Liquidity in both currencies is still required according to pay-in schedules.

Worked Example 7: Queue Gridlock

Three banks each need to pay S$100m but hold only S$20m: A→B, B→C, C→A. Individually no payment can settle gross. A multilateral liquidity-saving algorithm can settle the cycle simultaneously because each participant’s net position is zero.

The example shows how coordination can unlock payments without injecting S$240m extra liquidity.

System design affects required liquidity dramatically.

Worked Example 8: Haircut and Intraday Credit

Bank pledges S$200m eligible securities with 10% haircut, generating S$180m intraday credit capacity. Stress haircut rises to 20%, capacity falls to S$160m.

Payment capacity can shrink without any change in payment obligations.

Collateral price and haircut stress should be included in settlement-liquidity tests.

Worked Example 9: Settlement Fail Chain

Broker expects S$20m securities-sale proceeds at noon to fund another purchase at 13:00. First settlement fails, so second purchase lacks cash, potentially creating another fail.

One operational/counterparty problem propagates through dependent cash flows.

Liquidity buffers and sequencing reduce contagion.

Worked Example 10: MEPS+ Context

In Singapore, MEPS+ is used for SGD interbank funds transfers and settlement of SGS/MAS securities. The funds side operates on RTGS principles, while securities settlement can use delivery-versus-payment links through book-entry accounts.

This architecture makes abstract concepts tangible: settlement accounts provide central-bank money, DVP links cash/security legs, and intraday liquidity determines payment throughput.

Retail systems such as FAST operate at a different layer and can ultimately depend on interbank settlement arrangements beneath the customer experience.

Gross Versus Net Is a Risk-Allocation Choice

Gross settlement reduces the build-up of bilateral credit exposure and increases finality speed, but demands more intraday liquidity. Net settlement economises liquidity by offsetting obligations, but defers finality and concentrates dependency into net cycles/default management.

Modern systems often combine both philosophies: RTGS for finality with queues and liquidity-saving mechanisms that exploit offsetting flows before settlement. The result is not purely gross or net in operational behaviour, even if legal finality is gross.

Mira’s question is: which risk are we paying to reduce—credit exposure, liquidity usage, delay or operational complexity?

Settlement Finality Is a Legal-Mathematical Boundary

A payment can be operationally processed but still revocable before a legal finality point. Finality gives economic certainty: participants can safely reuse received funds and assets because the transfer cannot be unwound under normal system rules.

This is why PFMI treats finality as a core principle rather than a software detail. The mathematics of cash positions depends on whether incoming funds are final or provisional. Counting provisional money as certain can create hidden liquidity risk.

The model should therefore attach status to every flow: submitted, validated, queued, settled, final.

A Professional Payment-Settlement Workflow

1. Identify obligation, currency, value date and participants.
2. Distinguish message transmission from clearing and settlement.
3. Choose gross/net settlement rule and finality point.
4. Map opening settlement balances and credit/collateral capacity.
5. Sequence payments through time and calculate peak intraday need.
6. Model queues, priorities and liquidity-saving mechanisms.
7. Measure bilateral/multilateral credit exposures before finality.
8. Use DVP/PVP for linked asset/currency obligations where applicable.
9. Reconcile settled instructions to participant ledgers.
10. Stress participant default, delayed inflows, haircut increases and outages.
11. Track legal-entity/currency-specific liquidity resources.
12. Confirm operational recovery can still complete critical settlement on time.

Common Failure Modes

1. Message equals money

A payment message can precede final settlement. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

2. Customer credit equals interbank finality

Front-end balances can be provisional. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

3. Daily net used for intraday liquidity

Payment sequence creates peak need. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

4. Gross value confused with liquidity requirement

Netting/recycling can reduce liquidity dramatically. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

5. Netting treated as riskless

Default dependencies and legal enforceability matter. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

6. End-of-day finality assumed

Some systems provide intraday finality; rules must be explicit. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

7. DVP/PVP confused with netting

They link two legs to remove principal risk. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

8. Settlement asset ignored

Commercial-bank money and central-bank money carry different risks. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

9. Collateral counted at market value

Haircuts/encumbrance reduce usable liquidity. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

10. Incoming payments assumed punctual

Delay can propagate queues. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

11. Operational outage separated from liquidity

System downtime can strand otherwise available cash. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

12. Retail instant experience treated as wholesale settlement architecture

Different layers can use different mechanisms. The repair is to reconstruct the payment lifecycle with timestamps, settlement asset and finality status.

Formula Map

Measure	Simplified formula	Meaning
Participant net position	Σoutflows−Σinflows	Net debit/credit before settlement.
Bilateral net	max(O_AB−O_BA,0)	One-way obligation after offset.
Peak intraday liquidity	max_t cumulative(outflows−inflows)	Maximum funding need from sequence.
Collateral funding value	MarketValue×(1−haircut)	Usable secured liquidity.
Settlement-liquidity velocity	Gross settled value/Liquidity used	Recycling efficiency.
Queue delay	Settlement time−Submission time	Payment waiting duration.

Authoritative Reference Map

• CPMI-IOSCO — Principles for Financial Market Infrastructures
• CPMI — Principles for Financial Market Infrastructures publication
• MAS Financial Institutions Directory — MAS designated payment-system roles including MEPS+, FAST and IBG
• Bukit Timah Tutor — Intraday Liquidity Algorithms
• CLS Payment-versus-Payment Settlement Algorithms
• Banking And Finance Closed Loop Systems — Payments, Clearing and Settlement

Connected Banking And Finance Mathematics Route

• Complete Banking And Finance Mathematics System
• Bank Liquidity Mathematics
• Foreign Exchange Mathematics
• Derivatives Mathematics
• Finance & Banking Algorithms

Applied Case Study 1: Large-value RTGS bank

Situation. Bank has huge morning outflows and afternoon inflows. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Calculate peak intraday need and test intraday credit/collateral. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. End-of-day net can look small while morning risk is large. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 2: Multilateral retail clearing

Situation. Thousands of payments are netted. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Compare gross customer value with participant net obligations. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. Netting saves liquidity but delays finality until settlement cycle. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 3: Securities purchase

Situation. Cash and securities legs settle. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Use DVP and model cash/securities availability. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. One-leg settlement creates principal risk. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 4: FX payment

Situation. Currencies settle in different time zones. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Use PVP/CLS-style linking and currency-specific pay-in liquidity. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. PVP removes principal risk but not liquidity needs. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 5: Queue gridlock

Situation. Several banks wait for incoming funds. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Apply bilateral/multilateral LSM cycle. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. Coordination can unlock payments without new aggregate liquidity. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 6: Collateral stress

Situation. Haircuts rise on securities used for intraday credit. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Recalculate borrowing capacity and queue effects. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. Market stress can become payment stress. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 7: Participant default

Situation. One bank cannot meet net debit. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Recalculate obligations/default resources and liquidity shortfall. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. Netting concentrates dependency on default management. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 8: Operational outage

Situation. RTGS participant loses connectivity. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Queue critical payments and activate contingency channel. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. Operational risk becomes liquidity and downstream settlement risk. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 9: FAST retail transfer

Situation. Customer sees near-instant credit. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Separate retail service event from underlying interbank settlement/finality architecture. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. Customer experience is not the full settlement model. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 10: Card purchase

Situation. Transaction is authorised today and settled later. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Map authorisation, clearing, net settlement and merchant funding. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. Authorisation does not equal final merchant cash. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 11: Cross-border correspondent chain

Situation. Payment passes through two correspondents. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Track nostro balances, fees and timestamps. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. Every intermediary creates another liquidity/reconciliation dependency. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Applied Case Study 12: SGS settlement in MEPS+

Situation. Bank buys government securities. The task is to identify when an obligation becomes final and how much liquidity is needed before that point.

Method. Link RTGS cash debit with book-entry securities delivery via DVP. Adrian maps obligations, Jo calculates net/gross positions, Aisha tracks finality/collateral, and Ryan computes peak liquidity and queue delays.

Boundary. Securities and cash liquidity must be available together. Mira then asks which participant or operational dependency could turn a local delay into system-wide stress.

Final Principle

Payments move value only when obligations are finally settled. Everything before finality is a promise, instruction, queue position or provisional claim.

Gross settlement maximises immediacy but consumes liquidity. Netting economises liquidity but builds dependencies. RTGS systems combine finality with queue management and liquidity-saving tools. DVP and PVP eliminate principal risk by linking two settlement legs. Intraday liquidity models make timing visible.

The strongest payment mathematics therefore tracks four things at once: who owes whom, when funds/assets become final, how much liquidity is required at each moment, and what happens if one participant or system fails.

With this page, the `BTT-BFM-WORLD-230` through `-260` risk-and-infrastructure batch is complete: stress testing → market risk → ALM → payments and settlement.

Deep Practice Lab 1: Simulate RTGS day

Create 20 timestamped payments among four banks. Give each opening liquidity. Process sequentially, queue unfunded items and calculate peak intraday needs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 2: Compare gross and net settlement

Use same obligation matrix under gross, bilateral net and multilateral net. Calculate external liquidity required and discuss default/finality trade-offs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 3: Build liquidity-saving cycle

Create circular queued obligations that cannot settle individually. Find a simultaneous subset whose net debit fits balances and calculate liquidity saved.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 4: Model DVP/PVP

Write state table showing principal exposure when one leg settles first versus linked settlement. Quantify maximum principal at risk.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 5: Stress payment system

Delay one major participant’s incoming funds, raise collateral haircuts and add operational outage. Measure queue growth, peak liquidity and failed obligations.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 6: Simulate RTGS day

Create 20 timestamped payments among four banks. Give each opening liquidity. Process sequentially, queue unfunded items and calculate peak intraday needs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 7: Compare gross and net settlement

Use same obligation matrix under gross, bilateral net and multilateral net. Calculate external liquidity required and discuss default/finality trade-offs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 8: Build liquidity-saving cycle

Create circular queued obligations that cannot settle individually. Find a simultaneous subset whose net debit fits balances and calculate liquidity saved.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 9: Model DVP/PVP

Write state table showing principal exposure when one leg settles first versus linked settlement. Quantify maximum principal at risk.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 10: Stress payment system

Delay one major participant’s incoming funds, raise collateral haircuts and add operational outage. Measure queue growth, peak liquidity and failed obligations.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 11: Simulate RTGS day

Create 20 timestamped payments among four banks. Give each opening liquidity. Process sequentially, queue unfunded items and calculate peak intraday needs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 12: Compare gross and net settlement

Use same obligation matrix under gross, bilateral net and multilateral net. Calculate external liquidity required and discuss default/finality trade-offs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 13: Build liquidity-saving cycle

Create circular queued obligations that cannot settle individually. Find a simultaneous subset whose net debit fits balances and calculate liquidity saved.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 14: Model DVP/PVP

Write state table showing principal exposure when one leg settles first versus linked settlement. Quantify maximum principal at risk.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 15: Stress payment system

Delay one major participant’s incoming funds, raise collateral haircuts and add operational outage. Measure queue growth, peak liquidity and failed obligations.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 16: Simulate RTGS day

Create 20 timestamped payments among four banks. Give each opening liquidity. Process sequentially, queue unfunded items and calculate peak intraday needs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 17: Compare gross and net settlement

Use same obligation matrix under gross, bilateral net and multilateral net. Calculate external liquidity required and discuss default/finality trade-offs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 18: Build liquidity-saving cycle

Create circular queued obligations that cannot settle individually. Find a simultaneous subset whose net debit fits balances and calculate liquidity saved.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 19: Model DVP/PVP

Write state table showing principal exposure when one leg settles first versus linked settlement. Quantify maximum principal at risk.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 20: Stress payment system

Delay one major participant’s incoming funds, raise collateral haircuts and add operational outage. Measure queue growth, peak liquidity and failed obligations.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 21: Simulate RTGS day

Create 20 timestamped payments among four banks. Give each opening liquidity. Process sequentially, queue unfunded items and calculate peak intraday needs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 22: Compare gross and net settlement

Use same obligation matrix under gross, bilateral net and multilateral net. Calculate external liquidity required and discuss default/finality trade-offs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 23: Build liquidity-saving cycle

Create circular queued obligations that cannot settle individually. Find a simultaneous subset whose net debit fits balances and calculate liquidity saved.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 24: Model DVP/PVP

Write state table showing principal exposure when one leg settles first versus linked settlement. Quantify maximum principal at risk.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 25: Stress payment system

Delay one major participant’s incoming funds, raise collateral haircuts and add operational outage. Measure queue growth, peak liquidity and failed obligations.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 26: Simulate RTGS day

Create 20 timestamped payments among four banks. Give each opening liquidity. Process sequentially, queue unfunded items and calculate peak intraday needs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 27: Compare gross and net settlement

Use same obligation matrix under gross, bilateral net and multilateral net. Calculate external liquidity required and discuss default/finality trade-offs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 28: Build liquidity-saving cycle

Create circular queued obligations that cannot settle individually. Find a simultaneous subset whose net debit fits balances and calculate liquidity saved.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 29: Model DVP/PVP

Write state table showing principal exposure when one leg settles first versus linked settlement. Quantify maximum principal at risk.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 30: Stress payment system

Delay one major participant’s incoming funds, raise collateral haircuts and add operational outage. Measure queue growth, peak liquidity and failed obligations.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 31: Simulate RTGS day

Create 20 timestamped payments among four banks. Give each opening liquidity. Process sequentially, queue unfunded items and calculate peak intraday needs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 32: Compare gross and net settlement

Use same obligation matrix under gross, bilateral net and multilateral net. Calculate external liquidity required and discuss default/finality trade-offs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 33: Build liquidity-saving cycle

Create circular queued obligations that cannot settle individually. Find a simultaneous subset whose net debit fits balances and calculate liquidity saved.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 34: Model DVP/PVP

Write state table showing principal exposure when one leg settles first versus linked settlement. Quantify maximum principal at risk.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 35: Stress payment system

Delay one major participant’s incoming funds, raise collateral haircuts and add operational outage. Measure queue growth, peak liquidity and failed obligations.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 36: Simulate RTGS day

Create 20 timestamped payments among four banks. Give each opening liquidity. Process sequentially, queue unfunded items and calculate peak intraday needs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 37: Compare gross and net settlement

Use same obligation matrix under gross, bilateral net and multilateral net. Calculate external liquidity required and discuss default/finality trade-offs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 38: Build liquidity-saving cycle

Create circular queued obligations that cannot settle individually. Find a simultaneous subset whose net debit fits balances and calculate liquidity saved.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 39: Model DVP/PVP

Write state table showing principal exposure when one leg settles first versus linked settlement. Quantify maximum principal at risk.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 40: Stress payment system

Delay one major participant’s incoming funds, raise collateral haircuts and add operational outage. Measure queue growth, peak liquidity and failed obligations.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 41: Simulate RTGS day

Create 20 timestamped payments among four banks. Give each opening liquidity. Process sequentially, queue unfunded items and calculate peak intraday needs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 42: Compare gross and net settlement

Use same obligation matrix under gross, bilateral net and multilateral net. Calculate external liquidity required and discuss default/finality trade-offs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 43: Build liquidity-saving cycle

Create circular queued obligations that cannot settle individually. Find a simultaneous subset whose net debit fits balances and calculate liquidity saved.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 44: Model DVP/PVP

Write state table showing principal exposure when one leg settles first versus linked settlement. Quantify maximum principal at risk.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 45: Stress payment system

Delay one major participant’s incoming funds, raise collateral haircuts and add operational outage. Measure queue growth, peak liquidity and failed obligations.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 46: Simulate RTGS day

Create 20 timestamped payments among four banks. Give each opening liquidity. Process sequentially, queue unfunded items and calculate peak intraday needs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.

Deep Practice Lab 47: Compare gross and net settlement

Use same obligation matrix under gross, bilateral net and multilateral net. Calculate external liquidity required and discuss default/finality trade-offs.

Complete the lab with exact timestamps and settlement status. Ben should reconcile participant balances, Clara should document finality/netting rules, and Ethan should identify the first payment whose delay creates downstream dependency.

Then reorder the same payments without changing daily gross totals. Recalculate peak intraday liquidity. The difference demonstrates why settlement mathematics is about sequence, not only totals.