2. Payments, Clearing and Settlement
Every loan disbursement, FX trade, bond purchase and salary payment ends with money or securities moving between accounts at different institutions. This chapter explains how that movement works: the concepts behind payment and settlement systems, the major payment rails, how securities settle, and how post-trade processing and custody are organized. Treasury depends on this plumbing every day, because settlement timing drives intraday liquidity, counterparty exposure and the cash positions that treasury systems must forecast and reconcile.
<a id="21-payment-system-foundations"></a>
2.1 Payment System Foundations
This subchapter introduces the vocabulary and mechanics shared by every payment system, from domestic rails to cross-border correspondent chains.
Clearing vs Settlement
Why the distinction exists. When a customer of Bank A pays a customer of Bank B, Bank A debits its customer immediately, but Bank B will only credit its customer once it is sure it will receive the money from Bank A. Between those two events the banks must do two separate things: agree exactly what is owed, and then actually transfer the value. These steps happen at different times, in different systems, and carry different risks, so the industry gives them different names.
What they are.
- Clearing is the process of transmitting, reconciling and confirming payment instructions before settlement, and of calculating the resulting obligations. It can include validation, matching, netting and producing settlement positions.
- Settlement is the act that discharges the obligation: the transfer of a settlement asset from the payer's account to the payee's account so that the debt no longer exists.
- Settlement asset: the thing used to settle. Banks settle either in central bank money (balances on accounts at the central bank, which carry no credit risk) or in commercial bank money (balances at a private settlement bank, which carry that bank's credit risk).
Analogy. After a group dinner, working out who owes whom how much (and cancelling out "you owe me 20, I owe you 15") is clearing. Actually handing over the cash is settlement. You can finish the first step perfectly and still be left unpaid if someone leaves without paying.
| Aspect | Clearing | Settlement |
|---|---|---|
| Question answered | What exactly is owed, and by whom? | Has the obligation been discharged? |
| Output | Validated instructions, net or gross positions | Debits and credits on settlement accounts |
| Typical operator | Clearing house, ACH, CCP | Central bank (RTGS) or settlement bank |
| Main risk while pending | Operational error, mismatched data | Credit and liquidity risk until final |
| Reversible? | Yes, instructions can still be rejected or recalled | No, once final (see Settlement Finality) |
Example: a SEPA credit transfer cleared by an ACH and settled at the central bank.
Customer of Bank A Clearing (ACH / CSM) Settlement (T2, central bank)
------------------ -------------------- -----------------------------
pays EUR 1,000 ----> receives Bank A's file
to customer of B validates format, IBANs
sorts by receiving bank
nets all A<->B payments ----> Debit Bank A account EUR 1.2m
in this cycle: Credit Bank B account EUR 1.2m
A owes B EUR 1.2m net (obligation discharged)
|
Customer of Bank B <---------------------------------------------------+
credited EUR 1,000 (Bank B credits its customer once settlement is confirmed,
or earlier at its own risk)
Key takeaways
- Clearing computes and confirms obligations; settlement discharges them by moving a settlement asset.
- Settlement in central bank money removes credit risk on the settlement agent; settlement in commercial bank money does not.
- The gap between clearing and settlement is where credit and liquidity risk live, and where many system designs differ.
- In a payments system, an instruction having been "cleared" does not mean the beneficiary bank has been paid.
🧪 Practice
- Beginner: Classify each step as clearing or settlement: validating an IBAN, computing a bank's net position for a cycle, debiting a bank's central bank account, sorting payments by receiving bank.
- Intermediate: A payment system settles in commercial bank money on the books of a private settlement bank. Describe what happens to participants with pending credits if that settlement bank fails mid-day.
- Interview: "Our ledger marks a payment as 'completed' when the clearing house acknowledges the file. What is wrong with that?" Hint: distinguish acknowledgement, acceptance and settlement, and think about what the beneficiary bank actually holds at each stage.
Gross vs Net Settlement
Why it matters. Banks send each other huge volumes of payments, many in opposite directions. Settling each one individually needs a lot of liquidity; offsetting them first needs far less, but introduces a delay and a risk that one participant cannot pay its net amount. Every payment system design picks a point on this trade-off between liquidity efficiency and risk.
What it is.
- Gross settlement: each payment is settled individually, in full. If it settles payment by payment, as soon as it is processed, it is real-time gross settlement (RTGS).
- Net settlement: payments are accumulated over a period, offset against each other, and only the net amounts are settled, usually at set times. This is often called deferred net settlement (DNS).
- Bilateral netting: each pair of participants settles the difference between what they owe each other.
- Multilateral netting: each participant settles a single net position against the system as a whole.
Analogy. Gross settlement is paying for every coffee as you buy it. Net settlement is running a tab with the cafe and paying the difference at the end of the month: fewer payments, but the cafe is exposed to you until you settle.
Example: three banks, six payments in one cycle.
Payments: A->B 100 B->A 80 B->C 50
C->A 30 A->C 20 C->B 40
Gross: 6 transfers, total value 320
Bilateral: A pays B 20, B pays C 10, C pays A 10
3 transfers, total value 40
Multilateral: net position per bank
A: receives 110, pays 120 -> -10 (pays 10)
B: receives 140, pays 130 -> +10 (receives 10)
C: receives 70, pays 70 -> 0
1 transfer, total value 10
Netting reduced the liquidity needed from 320 to 10. The price: no payment is final until the end of the cycle, and if Bank A cannot pay its 10, the whole cycle may have to be unwound, recalculating every bank's position without A's payments.
| Feature | RTGS | Deferred net settlement |
|---|---|---|
| Finality | Immediate, per payment | At end of cycle |
| Liquidity need | High (mitigated by queues, intraday credit) | Low |
| Settlement risk | Minimal | Exposure until cycle settles; unwind risk |
| Typical use | Large-value, urgent payments | Retail, high-volume, low-value payments |
| Examples | T2, Fedwire Funds, CHAPS | ACH batches, SEPA CSM cycles, card schemes |
Hybrid designs. Modern RTGS systems use liquidity-saving mechanisms: payments that cannot settle immediately wait in a queue, and an optimization algorithm periodically looks for sets of queued payments that offset each other and settles them simultaneously, in gross, using only the net liquidity. Chapter 5.3 covers how treasury manages intraday liquidity around this.
Key takeaways
- Gross settlement gives immediate finality at a high liquidity cost; net settlement saves liquidity at the cost of deferred finality and exposure.
- Multilateral netting saves more liquidity than bilateral netting.
- The main risk in deferred net systems is a participant failing to pay its net position, which can force an unwind.
- Liquidity-saving mechanisms in RTGS systems blur the line by offsetting queued gross payments.
🧪 Practice
- Beginner: Recompute the bilateral and multilateral positions in the example if C->B is 70 instead of 40.
- Intermediate: In the example, Bank A defaults before the cycle settles. Remove all of A's payments and recompute the multilateral positions for B and C. Which bank is worse off than it expected, and why?
- Interview: "Design an algorithm that settles queued RTGS payments using minimal liquidity." Hint: start with bilateral offsetting of queued payments, then consider multilateral cycles, each participant's available balance as a constraint, and the fact that payments must still settle fully, never partially.
Correspondent Banking
Why it exists. A bank in Milan cannot open an account at the Federal Reserve, and it cannot be a direct participant in every payment system in the world. Yet its customers need to pay suppliers in US dollars, yen and rand. Correspondent banking solves this: a bank that does have access to a currency's payment system holds accounts for, and makes payments on behalf of, banks that do not.
What it is. A correspondent bank provides accounts and payment services to a respondent bank. The respondent holds a balance with the correspondent in the foreign currency and instructs it to make and receive payments. Large global banks act as correspondents for thousands of smaller banks, forming chains that let a payment reach almost any account in the world.
Analogy. A local post office cannot deliver letters abroad itself. It hands them to a national carrier that has agreements with foreign carriers. Each carrier in the chain delivers to the next, and each charges for its part.
How a payment travels: serial and cover methods.
- Serial method: the full customer payment message (ISO 20022
pacs.008, formerly MT103) passes from bank to bank along the chain. Each bank settles with the next by debiting or crediting accounts. - Cover method: the ordering bank sends the customer payment message directly to the beneficiary's bank, and sends a separate bank-to-bank "cover" payment (
pacs.009 COV, formerly MT202COV) through the correspondent chain to move the funds. Since 2009 the cover message must carry the underlying customer details so intermediaries can screen them.
Example: an Italian company pays USD 50,000 to a US supplier (serial method).
Ordering customer Bank IT (Milan) Correspondent (New York) Bank US
(Italian company) respondent holds Bank IT's USD account beneficiary bank
| | | |
| pain.001 USD 50,000 | | |
|----------------------->| | |
| debit EUR equivalent | pacs.008 USD 50,000 | |
| |-------------------------->| |
| | | debit Bank IT's USD |
| | | account; pay via |
| | | Fedwire (pacs.008) |
| | |----------------------->|
| | | | credit supplier
| | | | USD 49,975
| | | | (fees deducted: OUR/SHA/BEN)
Charge codes. Who pays the fees is set in the instruction: OUR (ordering customer pays all), SHA (each side pays its own bank) or BEN (beneficiary pays all, deducted from the amount). With SHA or BEN, intermediaries may deduct fees, so the beneficiary receives less than was sent.
Risks and costs.
| Issue | Why it arises |
|---|---|
| Credit and liquidity exposure | The respondent holds unsecured balances at the correspondent, and may be given intraday or overnight credit |
| Financial crime risk | The correspondent processes payments for customers it does not know directly |
| Opacity and delay | Each hop adds fees, cut-offs and screening; historically, status was hard to track |
| De-risking | Correspondents have closed relationships in high-risk regions, reducing access for some countries |
Key takeaways
- Correspondent banking lets banks make payments in currencies whose payment systems they cannot access directly.
- Payments move along a chain of accounts; each hop is a settlement between two banks.
- Serial and cover methods differ in how the customer message and the funds travel.
- Fees, cut-offs, screening and limited transparency are the traditional pain points, addressed in part by SWIFT gpi (Chapter 2.2).
🧪 Practice
- Beginner: In the example, identify the respondent bank, the correspondent bank and the payment system used for the final leg.
- Intermediate: Explain why a beneficiary might receive USD 49,975 instead of USD 50,000, and how the ordering customer could guarantee the full amount arrives.
- Interview: "Why was the cover method changed to require the underlying customer details?" Hint: consider what an intermediary bank on the cover leg could and could not screen for sanctions before the change.
Nostro and Vostro Accounts
Why the terms exist. In correspondent banking, the same account is an asset for one bank and a liability for the other. Each bank needs to record it in its own books and talk about it unambiguously with its counterparty. Latin gives the shorthand: nostro ("ours") and vostro ("yours").
What they are.
- Nostro account: our account held at another bank, usually in a foreign currency. For the account holder it is an asset (a claim on the other bank).
- Vostro account: your account held at our bank. For the bank keeping it, it is a liability (it owes the money to the account holder).
- Loro account: "their" account, used when talking about a third bank's account with a correspondent.
- Mirror account: the account holder's internal record of its nostro. It should always match the correspondent's statement, after timing differences.
One account, two views:
Bank IT (Milan) Correspondent (New York)
+-------------------------------+ +-------------------------------+
| ASSETS | | LIABILITIES |
| Nostro USD at Correspondent | <======> | Vostro: Bank IT USD account |
| (mirror account) 10,000,000 | same | 10,000,000 |
+-------------------------------+ money +-------------------------------+
Why treasury cares.
- Funding: outgoing payments in USD fail or create costly overdrafts if the USD nostro is short. Treasury forecasts and funds nostro balances daily, often by FX swaps (Chapter 3.5).
- Idle cash: excess balances in dozens of nostros earn little and carry unsecured exposure to the correspondent. Treasury aims to hold just enough.
- Reconciliation: every entry the correspondent posts must be matched against the bank's expected entries.
Example: nostro reconciliation. The correspondent sends an end-of-day statement (camt.053, formerly MT950) and intraday debit/credit notifications (camt.054). The bank matches each statement line against its mirror account entries.
| Ref | Mirror account (our books) | Correspondent statement | Status |
|---|---|---|---|
| PAY-1001 | -50,000.00 | -50,000.00 | Matched |
| FX-7781 | +2,000,000.00 | +2,000,000.00 | Matched |
| PAY-1002 | -120,000.00 | (not yet on statement) | Open: our entry, timing difference |
| (none) | (not booked) | -35.00 fee | Open: their entry, book the fee |
| COUP-55 | +18,750.00 | +18,500.00 | Break: amount differs by 250.00 |
Open items are aged and investigated; unexplained breaks are escalated. Chapter 13.4 covers reconciliation engines in more depth.
Key takeaways
- A nostro is our account at another bank (our asset); a vostro is another bank's account with us (our liability). They are two views of one account.
- Banks keep a mirror of each nostro and reconcile it against correspondent statements.
- Treasury manages nostro balances to avoid shortfalls without leaving excess cash idle and exposed.
- Reconciliation breaks fall into timing differences, missing entries on either side, and amount or reference mismatches.
🧪 Practice
- Beginner: Bank IT holds EUR accounts for a Turkish bank. From Bank IT's perspective, is that a nostro or vostro? Where does it appear on Bank IT's balance sheet?
- Intermediate: Write the double-entry postings Bank IT makes when its New York correspondent debits its USD nostro for a USD 50,000 customer payment, and when it books the USD 35 fee from the statement.
- Interview: "Design a nostro reconciliation matcher. What are your matching keys, and how do you handle one-to-many matches?" Hint: consider references (UETR, end-to-end ID), amount, value date and tolerance, grouping several internal entries into one statement line, and how unmatched items are aged.
Settlement Finality
Why it matters. A payment that can be unwound later is not really a payment; it is a promise. If a bank credits its customer, lets the money be spent, and then the incoming payment is reversed because the sender went bankrupt, the bank takes the loss. Systemic risk follows: one participant's insolvency could unravel thousands of payments across the system. Legal certainty about when a transfer becomes irreversible is therefore a cornerstone of financial stability.
What it is.
- Settlement finality is the irrevocable and unconditional transfer of an asset, or discharge of an obligation, in accordance with the terms of the underlying contract.
- Final means that the transfer cannot be revoked by the sender, by the system, or by an insolvency administrator of a participant.
- Laws define the moments that matter. In the EU, the Settlement Finality Directive (98/26/EC) protects transfer orders entered into designated systems from insolvency law, including "zero-hour rules" that could otherwise void a bankrupt participant's transactions from the start of the day of insolvency. In the US, Fedwire finality rests on the Federal Reserve's Regulation J and UCC Article 4A. Internationally, the CPMI-IOSCO Principles for Financial Market Infrastructures (PFMI, Principle 8) require systems to define finality clearly.
Key moments in a system's rulebook.
| Moment | Meaning |
|---|---|
| Entry (acceptance) | The order has passed the system's checks and is now governed by its rules |
| Irrevocability | The sender can no longer cancel the order |
| Finality | The transfer is complete and protected from unwinding |
Analogy. A cheque is a promise that can bounce days later. Banknotes handed over in a shop are final at once: the shop does not care what happens to your bank afterwards. Central bank RTGS settlement gives banks the electronic equivalent of handing over banknotes.
Example: the same payment in two systems.
RTGS (e.g. T2):
10:02:15 order accepted -> 10:02:15 settled on central bank accounts = FINAL
Bank B can release funds to its customer immediately with no settlement risk.
Deferred net system:
10:02:15 order accepted, irrevocable
14:00:00 cycle closes, net positions calculated
14:05:00 net positions settled in RTGS = FINAL
If Bank B credits its customer at 10:02, it is exposed
to the system failing to settle until 14:05.
Finality is not the same as the end of disputes. A final interbank transfer can still lead to a new, separate payment back, for example a SEPA recall for a duplicate or fraud, or a card chargeback. These are new transactions under scheme rules, not reversals of the original settlement.
Key takeaways
- Settlement finality is the legal point after which a transfer cannot be unwound, even if a participant becomes insolvent.
- Laws such as the EU Settlement Finality Directive protect transfers in designated systems from insolvency rules.
- RTGS systems give finality per payment; deferred net systems give it only at the end of a cycle.
- Systems should record and expose the finality timestamp; downstream logic such as releasing funds or goods should depend on it.
🧪 Practice
- Beginner: Explain why a bank might wait for settlement finality before releasing securities or goods to a counterparty.
- Intermediate: A participant in a deferred net system is declared insolvent at 11:00 on a day when it has payments in a 14:00 cycle. Without settlement finality protection, what could the administrator try to do, and what effect would it have on other participants?
- Interview: "Which timestamp should our ledger use to mark an incoming payment as final, and where does it come from?" Hint: compare message receipt, scheme acceptance and the settlement confirmation (for example
pacs.002status ACSC or acamt.054credit notification), and which one the rulebook defines as final.
Payment Lifecycle
Why it matters. A payment is not one event but a sequence of steps across several systems, each of which can fail. Engineers who build payment hubs, treasury systems or ledgers need a clear model of the lifecycle so they can attach the right controls, statuses and exception handling to each step.
What it is. A typical credit transfer passes through these stages:
- Initiation: the customer or an internal system instructs the payment (for corporates, ISO 20022
pain.001). - Validation and enrichment: format, mandatory fields, account existence, IBAN/BIC checks, adding missing data such as routing details.
- Authorization and funds check: user entitlements, approval workflows, balance or limit check, funds reservation.
- Screening: sanctions screening, AML monitoring and fraud checks. Hits are held for review.
- Routing: choosing the rail (instant, ACH, RTGS, correspondent) based on currency, amount, urgency, cut-offs and cost.
- Clearing: submitting to the payment system (interbank
pacs.008) and receiving status (pacs.002). - Settlement: the interbank transfer becomes final.
- Posting and notification: the beneficiary bank credits the beneficiary; both sides send statements and notifications (
camt.053,camt.054). - Reconciliation: confirmations, statements and internal ledgers are matched.
Exceptions (R-transactions).
| Exception | When | Typical message |
|---|---|---|
| Reject | Before settlement, payment refused by a bank or the system | pacs.002 with status RJCT |
| Return | After settlement, beneficiary bank sends funds back (for example, closed account) | pacs.004 |
| Recall | After settlement, ordering bank asks for funds back (duplicate, fraud) | camt.056, answered by pacs.004 or camt.029 |
| Repair | Before submission, invalid data corrected manually or automatically | Internal |
Example: lifecycle as a state machine.
RECEIVED -> VALIDATED -> AUTHORIZED -> SCREENED --(hit)--> ON_HOLD --(released)--+
| | | | |
v v | (blocked) |
REJECTED REJECTED v v |
ROUTED <---------- REJECTED <-------+
|
v
SUBMITTED --(pacs.002 RJCT)--> REJECTED (release reservation)
|
(pacs.002 ACSC / camt.054)
v
SETTLED --(pacs.004)--> RETURNED
|
v
RECONCILED
Common pacs.002 status codes include ACTC (accepted after technical validation), ACSP (accepted, settlement in process), ACSC (accepted, settlement completed), PDNG (pending) and RJCT (rejected).
Engineering points.
- Idempotency: every payment carries unique identifiers (end-to-end ID, UETR). Retrying a submission must not create a duplicate payment.
- Funds reservation: reserve at authorization, consume at settlement, release on rejection.
- Audit trail: every state change, with timestamp and actor, must be stored.
Key takeaways
- A payment moves through initiation, validation, authorization, screening, routing, clearing, settlement, posting and reconciliation.
- Rejects happen before settlement; returns and recalls are new payments after settlement.
- Model the lifecycle as an explicit state machine with defined transitions and terminal states.
- Idempotency, funds reservation and a full audit trail are essential to correct payment processing.
🧪 Practice
- Beginner: Place these events in lifecycle order: sanctions screening,
camt.054credit notification received by the beneficiary,pain.001received,pacs.008submitted, funds reservation.- Intermediate: A payment receives a
pacs.002RJCT after funds were reserved and the customer's available balance reduced. List every action your system must take, including customer communication and ledger entries.- Interview: "The connection to the clearing system times out after we send a payment. Do we resend?" Hint: think about idempotency keys, status inquiries (
pacs.028), whether the system deduplicates on message ID, and the cost of a duplicate versus a delay.
<a id="22-major-payment-rails"></a>
2.2 Major Payment Rails
This subchapter surveys the payment systems a treasury interacts with most, from central bank RTGS systems to retail batch, instant, card, FX and cross-border rails. Operating hours, limits and cut-offs quoted here are indicative; always check the operator's current documentation.
RTGS Systems (TARGET2/T2, Fedwire, CHAPS)
Why they exist. Some payments are too large or too important to settle in batches with deferred finality: interbank money market loans, central bank operations, the cash legs of securities and FX settlement, and large corporate payments. A failure in one of these could spread through the system. Central banks therefore run real-time gross settlement systems where each payment settles individually and finally in central bank money.
What they are. An RTGS system is a set of accounts held by banks at the central bank, plus a payment engine that debits and credits them one payment at a time. Banks fund them with reserves and with intraday credit from the central bank, usually against collateral. When a bank lacks the balance for a payment, the payment waits in a queue until incoming payments or credit cover it.
The three systems treasury teams meet most.
| Feature | T2 (euro area) | Fedwire Funds (US) | CHAPS (UK) |
|---|---|---|---|
| Operator | Eurosystem (ECB and national central banks) | Federal Reserve Banks | Bank of England |
| Currency | EUR | USD | GBP |
| History | Replaced TARGET2 in March 2023 | Operating since 1918, electronic since the 1970s | Operating since 1984; run by the Bank of England since 2017 |
| Message standard | ISO 20022 | ISO 20022 (since July 2025) | ISO 20022 (since June 2023) |
| Intraday credit | Collateralized, free of charge | Daylight overdrafts; collateralized free, uncollateralized charged a fee | Collateralized intraday liquidity |
| Liquidity-saving | Priorities, reservations, limits, offsetting algorithms | Queuing with optional liquidity management | Liquidity-saving mechanism with offsetting |
T2 structure. T2 consolidated several services on the Eurosystem's platform:
+--------------------------------------+
| CLM - Central Liquidity Management |
| Main Cash Account (MCA): central bank |
| operations, standing facilities, |
| intraday credit, minimum reserves |
+----+------------+------------+--------+
| liquidity | liquidity | liquidity
| transfers | transfers | transfers
v v v
+-----------+ +--------------+ +-------------+
| RTGS DCA | | T2S DCA | | TIPS DCA |
| high-value| | securities | | instant |
| payments | | settlement | | payments |
+-----------+ +--------------+ +-------------+
A bank moves liquidity between its accounts during the day: for example, from its MCA to its RTGS dedicated cash account (DCA) ahead of a large payment, or to its T2S DCA ahead of the securities settlement batch.
Example: queue and offsetting in an RTGS system.
Opening balances: Bank A 10 Bank B 5
09:00 A -> B 30 A balance 10 < 30 -> queued
09:05 B -> A 28 B balance 5 < 28 -> queued
09:06 Offsetting algorithm finds A->B 30 and B->A 28 together:
A: 10 - 30 + 28 = 8 (>= 0)
B: 5 + 30 - 28 = 7 (>= 0)
Both settle simultaneously, in full and final.
Key takeaways
- RTGS systems settle each payment individually and finally in central bank money.
- T2, Fedwire Funds and CHAPS are the euro, US dollar and sterling RTGS systems; all now use ISO 20022.
- Banks manage liquidity through central bank intraday credit, queues, priorities and liquidity-saving algorithms.
- In T2, liquidity sits in a main cash account in CLM and is moved to dedicated accounts for RTGS, T2S and TIPS.
🧪 Practice
- Beginner: Why do RTGS systems need intraday credit, given that each bank must ultimately end the day with a non-negative balance?
- Intermediate: In the queue example, a third payment C -> A 4 arrives at 09:04 with Bank C's balance at 20. Show the balances after 09:04 and explain whether the algorithm at 09:06 would still be needed.
- Interview: "Our treasury system must keep enough liquidity on the RTGS account to settle all urgent payments by their deadline. How would you model this?" Hint: think about projected intraday balances by time slot, payment priorities, expected incoming flows, collateral available for intraday credit and liquidity transfers between accounts.
ACH and SEPA Credit Transfers
Why they exist. Salaries, supplier invoices, utility bills and pensions are high in number and low in value, and rarely need to arrive in seconds. Settling each one in an RTGS system would be expensive and needlessly liquidity-intensive. Automated clearing houses (ACHs) process these payments in batches, net them, and settle the net positions in central bank money.
What they are.
- ACH: an electronic clearing system that exchanges batches of payment files between banks, calculates net positions and submits them for settlement, usually in the RTGS system.
- US ACH: governed by Nacha rules, operated by FedACH (Federal Reserve) and EPN (The Clearing House). Supports credits (payroll) and debits (bill pay). Standard entries settle the next banking day; Same Day ACH has three daily settlement windows, with a per-payment limit of USD 1 million.
- SEPA: the Single Euro Payments Area, the EU plus several other European countries using common euro payment schemes defined by the European Payments Council (EPC):
- SEPA Credit Transfer (SCT): maximum execution time of one business day (D+1).
- SEPA Direct Debit (SDD) Core and B2B: creditor-initiated collections under a mandate. In Core, payers can request a no-questions refund within 8 weeks, and up to 13 months for unauthorized debits.
- Payments are cleared by clearing and settlement mechanisms (CSMs) such as EBA Clearing's STEP2 or national ACHs, and settled in T2.
Example: a SEPA CSM settlement cycle.
08:00 Banks submit files of pacs.008 (SCT) to the CSM
Bank A file: 120,000 payments Bank B file: 95,000 payments ...
09:00 Cycle cut-off. CSM validates, sorts, calculates multilateral net positions
Bank A -4.2m Bank B +1.7m Bank C +2.5m (sum = 0)
09:30 CSM submits settlement instructions to T2 (ancillary system settlement):
debit Bank A 4.2m; credit Bank B 1.7m, Bank C 2.5m
09:45 Settlement confirmed -> CSM delivers outgoing files to receiving banks
10:00+ Receiving banks credit beneficiaries
| Feature | US ACH | SEPA Credit Transfer |
|---|---|---|
| Rulebook | Nacha Operating Rules | EPC SCT Rulebook |
| Format | Nacha fixed-width file (ISO 20022 not used for core ACH) | ISO 20022 XML (pacs.008) |
| Account identifier | Routing number (ABA) + account number | IBAN (BIC optional) |
| Speed | Same day or next day | D+1 maximum; often same day |
| Debits | Supported in the same network | Separate SDD schemes |
| Returns | Return reason codes (R01 insufficient funds, R03 no account, ...) | pacs.004 with ISO reason codes (AC04 closed account, ...) |
Key takeaways
- ACHs batch, net and settle high-volume, low-value payments, saving liquidity at the cost of deferred finality.
- US ACH uses Nacha fixed-width files; SEPA uses ISO 20022 and IBANs.
- SEPA SCT has a D+1 maximum execution time; SDD Core gives payers broad refund rights.
- CSM net positions are settled in central bank money, in T2 for the euro.
🧪 Practice
- Beginner: Explain why a payroll run is better suited to ACH or SCT than to an RTGS system.
- Intermediate: A company collects EUR 2 million in SDD Core payments. Seven weeks later, 1% of payers request refunds. What does this mean for the company's cash forecast, and why is SDD B2B different?
- Interview: "We need to process returns for both US ACH and SEPA in one platform. How would you model return reasons?" Hint: consider a canonical internal reason taxonomy, mapping tables from Nacha R-codes and ISO reason codes, and which reasons should trigger automated actions such as blocking an account.
Instant Payments (SCT Inst, FedNow, RTP)
Why they exist. Consumers and businesses expect money to move as fast as messages do, at any hour. Batch ACH payments leave money in transit for hours or days, and RTGS systems close in the evening and at weekends. Instant payment systems close that gap: account-to-account credit transfers that complete within seconds, 24 hours a day, 365 days a year.
What they are. An instant payment is a credit transfer where the beneficiary's account is credited, and the payer is told so, within seconds of initiation, at any time. Most systems settle each payment individually and finally, using prefunded accounts so that settlement does not depend on the RTGS system being open.
| Feature | SCT Inst (euro) | FedNow (US) | RTP (US) |
|---|---|---|---|
| Operator | Scheme by the EPC; settled via TIPS (Eurosystem) or RT1 (EBA Clearing) | Federal Reserve | The Clearing House |
| Launch | 2017 | July 2023 | November 2017 |
| Target time | 10 seconds | Seconds | Seconds |
| Settlement | TIPS: central bank money; RT1: prefunded position backed by a T2 account | Directly in Fed master accounts | Joint account at the Federal Reserve, prefunded by participants |
| Transaction limit | No scheme-wide maximum since 2025; banks and users may set limits | Fed-set network cap; lower limits per participant | USD 10 million (since 2025) |
| Message standard | ISO 20022 | ISO 20022 | ISO 20022 |
Regulation in the EU. The Instant Payments Regulation (EU 2024/886) requires euro area payment service providers that offer SCT to also receive (from January 2025) and send (from October 2025) SCT Inst, at no higher price than standard SCT. It also requires Verification of Payee: before the payer authorizes, the bank checks whether the payee name matches the IBAN and reports a match, close match or no match.
Example: an SCT Inst flow via TIPS.
t = 0.0s Payer authorizes EUR 750 in mobile app
t = 0.2s Payer bank: validation, VoP done earlier, fraud/sanctions checks, reserve funds
-> sends pacs.008 to TIPS
t = 0.4s TIPS: checks payer bank DCA balance, reserves EUR 750, forwards to payee bank
t = 0.9s Payee bank: checks account, accepts -> pacs.002 ACCP to TIPS
t = 1.0s TIPS settles: debit payer bank DCA, credit payee bank DCA (FINAL)
-> confirmations to both banks
t = 1.1s Payee bank credits beneficiary; payer bank confirms to the app
If no positive answer arrives within the time-out, the payment is rejected
and the reservation released.
Treasury impact. Instant payments run when RTGS systems are closed. Banks must prefund their TIPS or RT1 positions before the RTGS closes on Friday evening to cover weekend outflows, and monitor balances continuously. A bank that runs out of prefunded liquidity at 03:00 on Sunday has its customers' payments rejected.
Key takeaways
- Instant payments credit the beneficiary within seconds, 24/7/365, with immediate finality.
- Settlement uses prefunded accounts so it does not depend on RTGS opening hours.
- In the EU, the Instant Payments Regulation makes SCT Inst mandatory to send and receive, with price parity and Verification of Payee.
- 24/7 settlement turns liquidity management into a continuous, weekend-inclusive activity.
🧪 Practice
- Beginner: Name two differences between an SCT and an SCT Inst payment, from the customer's and from the bank's perspective.
- Intermediate: A bank's weekend instant payment outflows averaged EUR 400 million net, with a worst observed weekend of EUR 650 million. How should treasury decide how much to prefund on Friday, and what does over-funding cost?
- Interview: "Instant payments are irrevocable within seconds. How does that change fraud controls compared to batch payments?" Hint: consider real-time risk scoring within the time budget, Verification of Payee, behavioral limits, authorized push payment fraud, and the absence of a window to stop a payment.
Card Schemes Overview
Why they matter. Card payments are among the most common consumer payments, and they settle very differently from credit transfers. Treasury teams at issuers and acquirers must fund daily scheme settlement, and corporate treasuries must forecast card receipts, which arrive net of fees and days after the sale.
What they are. A card scheme (Visa, Mastercard, American Express, and domestic schemes) sets the rules and runs the network that connects the parties:
- Cardholder: the payer.
- Issuer: the cardholder's bank, which issues the card and guarantees payment.
- Merchant: the payee.
- Acquirer: the merchant's bank or payment processor, which accepts card payments for the merchant.
- Scheme: the network and rulebook in between.
In a four-party model (Visa, Mastercard), issuer and acquirer are different institutions. In a three-party model (traditionally American Express), the scheme is both issuer and acquirer.
The three phases.
1. AUTHORIZATION (real time, seconds)
Card -> Merchant -> Acquirer -> Scheme -> Issuer: "approve EUR 100?"
Issuer checks card, fraud score, balance/limit, places a hold -> approve
No money moves yet.
2. CLEARING (batch, usually end of day)
Merchant/acquirer submit captured transactions -> Scheme -> Issuer
Final amounts confirmed (may differ: tips, partial shipments)
Issuer posts transaction to cardholder account / statement
3. SETTLEMENT (net, typically next business day)
Scheme calculates each member's net position across all transactions
Issuers pay (net), acquirers receive (net) via settlement banks
Acquirer pays the merchant, net of the merchant service charge
Example: who earns what on a EUR 100.00 consumer debit card purchase in the EU (illustrative).
| Flow | Amount (EUR) | Notes |
|---|---|---|
| Cardholder pays | 100.00 | |
| Interchange to issuer | 0.20 | Capped at 0.2% for consumer debit (0.3% for credit) under the EU Interchange Fee Regulation |
| Scheme fees | 0.10 | Charged to acquirer (issuer pays its own scheme fees too) |
| Acquirer margin | 0.80 | |
| Merchant service charge (MSC) | 1.10 | 0.20 + 0.10 + 0.80 |
| Merchant receives | 98.90 | Usually one or more days after the sale |
Chargebacks. A cardholder can dispute a transaction (fraud, goods not received). The issuer raises a chargeback through the scheme, and the amount is debited from the acquirer, which recovers it from the merchant. Unlike credit transfers, card payments therefore remain economically reversible for months, even though interbank settlement was final.
Key takeaways
- Card schemes connect cardholder, issuer, merchant and acquirer under one rulebook.
- Authorization is real time and moves no money; clearing confirms amounts; settlement is net and deferred.
- Merchants receive the amount net of the merchant service charge, which includes interchange, scheme fees and the acquirer's margin.
- Chargebacks make card payments reversible under scheme rules long after settlement.
🧪 Practice
- Beginner: For an online purchase, list which party performs each task: fraud scoring the transaction, paying the merchant, setting interchange rules, posting to the cardholder's statement.
- Intermediate: A merchant processes EUR 500,000 of card sales on Friday, Saturday and Sunday. The acquirer pays out on the next business day net of a 1.2% MSC. Build the expected cash receipt schedule for the following week.
- Interview: "Why does a hotel authorization hold sometimes differ from the final charge, and how should a ledger represent it?" Hint: distinguish authorization holds (reducing available balance) from cleared postings (reducing book balance), and think about hold expiry and incremental authorizations.
CLS for FX Settlement
Why it exists. An FX trade has two legs in two currencies, usually settled in two different payment systems in different time zones. If one bank pays its leg and the counterparty fails before paying the other, the first bank loses the full principal. This is FX settlement risk, also called Herstatt risk after Bankhaus Herstatt, which was closed by German regulators on 26 June 1974 after receiving Deutsche Mark payments but before paying out US dollars in New York. The FX market trades trillions of dollars a day, so the potential losses are enormous.
What it is. CLS (Continuous Linked Settlement), operated by CLS Bank International since 2002, settles FX trades on a payment-versus-payment (PvP) basis: both legs settle simultaneously, or neither does. It settles 18 major currencies. CLS has accounts at each relevant central bank, and its settlement members hold multi-currency accounts at CLS. Other banks and funds access CLS as third parties through a settlement member.
How it works.
- Both counterparties submit trade instructions to CLS, which matches them.
- CLS calculates each member's pay-in schedule: multilateral net amounts per currency, due in specific time slots, mostly between 07:00 and 12:00 CET, when the relevant RTGS systems overlap.
- Members pay in through their national RTGS systems.
- CLS settles trades one by one across its books, each only if both legs are covered and account balance tests pass.
- CLS pays out net long positions to members through the RTGS systems.
Example: netting effect in CLS.
Bank X trades during the day:
T1 buys USD 108m sells EUR 100m
T2 sells USD 50m buys EUR 46m
T3 sells USD 60m buys JPY 9,000m
Gross payments without CLS (X pays out): EUR 100m + USD 50m + USD 60m
Net positions in CLS:
USD: +108 - 50 - 60 = -2m -> X pays in USD 2m
EUR: -100 + 46 = -54m -> X pays in EUR 54m
JPY: +9,000m -> X receives JPY 9,000m
Each trade settles PvP: X never delivers a currency without receiving the counter-currency.
Multilateral netting typically reduces members' funding needs by more than 95% relative to gross values.
Limits of CLS. Not every currency, counterparty or trade is eligible. Same-day trades and trades in non-CLS currencies still settle bilaterally, with Herstatt risk managed through settlement limits (Chapter 8.3).
Key takeaways
- FX settlement risk (Herstatt risk) is the risk of paying one leg of an FX trade without receiving the other.
- CLS eliminates it for eligible trades by settling both legs simultaneously (PvP) on its books.
- Multilateral netting of pay-ins greatly reduces the liquidity members need.
- Pay-in deadlines fall in a narrow morning window, which treasury must plan liquidity around.
🧪 Practice
- Beginner: Explain in two sentences what happened at Bankhaus Herstatt and why time zones made it worse.
- Intermediate: Add a trade T4 to the example: Bank X buys USD 30m and sells JPY 4,500m. Recompute Bank X's net pay-in and pay-out positions.
- Interview: "A treasury must meet CLS pay-ins in five currencies before noon CET. What can go wrong, and how would you monitor it?" Hint: consider RTGS opening hours in Asia-Pacific currencies, nostro funding, late trade amendments changing the pay-in schedule, and real-time tracking of pay-in deadlines.
Cross-Border Payments and SWIFT gpi
Why it matters. Cross-border payments have historically been slow, expensive and opaque: a payment could take days, pass through several correspondents, arrive with unexpected fees deducted, and give the sender no visibility of where it was. The G20 made improving cross-border payments a priority in 2020, setting targets for 2027 on cost, speed, access and transparency.
What it is.
- SWIFT is the global financial messaging network, a cooperative owned by its member institutions. It carries payment instructions between banks but does not hold accounts or settle funds; settlement happens over correspondent accounts and payment systems (Chapter 12.1).
- SWIFT gpi (global payments innovation), launched in 2017, is a set of rules and services on top of SWIFT for cross-border payments:
- UETR (Unique End-to-End Transaction Reference): a UUID that stays with the payment across every hop.
- Tracker: a central database where each bank in the chain updates the payment's status, fees deducted and FX rate applied.
- Service levels: same-day use of funds (within the beneficiary bank's timezone), transparency of fees and FX, end-to-end tracking, and unaltered remittance information.
- ISO 20022 migration: the coexistence period for cross-border payment messages on SWIFT ended in November 2025. Payments now use
pacs.008andpacs.009(the CBPR+ usage guidelines) instead of MT103 and MT202, giving richer, structured data for screening and reconciliation.
Example: tracking a gpi payment.
UETR: 3f2a9c1e-7b4d-4e8a-9c01-5d6e7f8a9b0c
Time (UTC) Bank Status Amount Fee
08:02:11 Bank IT, Milan Sent to next agent USD 50,000.00 -
08:02:40 Correspondent, NY Processing (screening) USD 50,000.00 -
08:15:03 Correspondent, NY Sent to next agent USD 49,985.00 USD 15.00
08:15:20 Bank US Credited to beneficiary USD 49,975.00 USD 10.00
(ACCC)
End-to-end: 13 minutes; total deductions USD 25.00 (charge code SHA)
Alternatives and complements.
| Route | How it works | Typical use |
|---|---|---|
| Correspondent banking + gpi | Chain of accounts, tracked by UETR | Most wholesale and corporate cross-border payments |
| Intra-group / in-country accounts | Bank uses own branches or local accounts to pay locally | Banks and corporates with global footprint |
| Interlinked instant systems | Domestic instant systems connected across borders | Emerging; regional initiatives |
| Fintech / money transfer operators | Pre-funded local accounts in many countries, local payouts | Retail remittances, SME payments |
Key takeaways
- Cross-border payments usually travel over correspondent chains; SWIFT carries the messages, not the money.
- SWIFT gpi adds a unique end-to-end reference, a tracker and service levels for speed and transparency.
- Cross-border payments on SWIFT have moved from MT to ISO 20022 messages, enabling structured data.
- The G20 roadmap targets faster, cheaper and more transparent cross-border payments by 2027.
🧪 Practice
- Beginner: What is the UETR, who generates it, and why must it never change along the chain?
- Intermediate: In the example, the ordering customer used charge code SHA. Recompute the amount credited if
OURhad been used, and explain how the intermediary fees would then be paid.- Interview: "A corporate client says a cross-border payment has not arrived. Walk me through your investigation." Hint: start with the UETR in the gpi tracker, identify the last bank to update the status, check for screening holds, cut-offs, rejected or returned messages, and the beneficiary bank's credit confirmation.
<a id="23-securities-settlement"></a>
2.3 Securities Settlement
This subchapter covers how ownership of securities is recorded and transferred against cash, the infrastructures that do it, and what happens when settlement fails.
Central Securities Depositories
Why they exist. Securities used to be paper certificates. Settling a trade meant physically moving certificates between vaults, which was slow, expensive and risky; in the late 1960s, Wall Street's "paperwork crisis" forced exchanges to shorten trading hours because back offices could not keep up. The solution was to put securities in one central place and transfer ownership by book entry, the same way banks move money between accounts.
What they are. A central securities depository (CSD) is a financial market infrastructure that holds securities accounts and records ownership of securities electronically. Under the EU's Central Securities Depositories Regulation (CSDR, EU 909/2014), a CSD provides three core services:
| Core service | What it means |
|---|---|
| Notary | Initial recording of securities in the book-entry system when they are issued |
| Central maintenance | Keeping the top-tier securities accounts, and ensuring the total held equals the total issued |
| Settlement | Operating a securities settlement system that transfers securities between accounts |
- Immobilization: physical certificates (or a single global note) are kept in the CSD's vault and never move; ownership changes by book entry.
- Dematerialization: no certificate exists at all; the security exists only as an electronic record.
- National CSDs settle securities of their domestic market (for example Euroclear France, Clearstream Banking Frankfurt, Euronext Securities Milan, DTC in the US).
- International CSDs (ICSDs): Euroclear Bank and Clearstream Banking Luxembourg settle internationally traded securities such as Eurobonds, and are linked to each other through the "Bridge".
- T2S (TARGET2-Securities): a Eurosystem platform on which most euro area CSDs settle, in central bank money on T2S dedicated cash accounts. The CSDs keep their legal and customer relationships; T2S provides a single settlement engine.
Analogy. A CSD is to securities what a land registry is to property: the authoritative record of who owns what, where a transfer is only valid once the register is updated.
Example: the holding chain.
Issuer: XYZ S.p.A. issues 10,000,000 shares (ISIN IT0000000001)
|
v
CSD (Euronext Securities Milan) - top-tier accounts, total must equal 10,000,000
+-- Participant: Bank A (own account) 1,500,000
+-- Participant: Bank A (clients omnibus) 4,000,000
+-- Participant: Global Custodian G (clients) 3,000,000
+-- Participant: Broker B 1,500,000
---------
10,000,000 <- integrity check
|
v
Bank A's own books: the 4,000,000 in the omnibus account
are split across its clients (Fund 1: 2,500,000; Fund 2: 1,500,000)
The CSD knows its participants; the end investors are usually known only to the intermediaries below (see Custodians, Custody and Sub-Custody in Chapter 2.4).
Key takeaways
- CSDs record securities ownership by book entry and provide notary, central maintenance and settlement services.
- Immobilization and dematerialization replaced the physical movement of certificates.
- National CSDs serve domestic markets; ICSDs serve international securities; T2S provides a common settlement platform in the euro area.
- The CSD must ensure the total of securities in its accounts equals the amount issued.
🧪 Practice
- Beginner: Explain the difference between immobilization and dematerialization in one sentence each.
- Intermediate: In the example, the CSD's records show 10,000,050 shares in participant accounts. Which core service has failed, and what are the possible causes and consequences?
- Interview: "Why does the euro area run settlement for many CSDs on one platform, T2S, while each CSD remains a separate legal entity?" Hint: think about cross-border settlement costs before T2S, settlement in central bank money, and the legal and supervisory role of CSDs.
Delivery vs Payment (DvP)
Why it exists. A securities trade has two legs: securities move from seller to buyer, cash moves from buyer to seller. If the seller delivers first and the buyer defaults, the seller loses the securities; if the buyer pays first, the buyer can lose the cash. This principal risk is the securities equivalent of Herstatt risk. DvP removes it.
What it is. Delivery versus payment is a settlement mechanism that ensures the securities are delivered if and only if the corresponding cash payment occurs. The BIS (1992) defined three DvP models:
| Model | Securities | Cash | Characteristics | Examples |
|---|---|---|---|---|
| Model 1 | Gross | Gross | Trade-by-trade, real-time finality; high liquidity need | T2S (real-time settlement), Fedwire Securities |
| Model 2 | Gross | Net | Securities settle individually during the day; cash settles net at the end | DTC (end-of-day net funds settlement) |
| Model 3 | Net | Net | Both legs settled net in batch at set times | Some batch CSDs |
Related mechanisms:
- Receive versus payment (RvP): the buyer's view of DvP.
- Free of payment (FoP): securities move with no linked cash leg, for example a portfolio transfer between custodians or a collateral movement. The cash, if any, settles separately.
- Delivery with payment (DwP): both parties exchange securities and cash in the same direction, for example a collateral substitution with a cash adjustment.
Analogy. DvP is like an escrow agent at a house sale: the deed and the money are held together and released at the same moment, or not at all.
Example: a DvP purchase of an Italian government bond (BTP).
Trade: Bank A buys EUR 1,000,000 nominal BTP from Bank B
Clean price 101.25% Accrued interest EUR 4,500.00
Settlement amount = 1,000,000 x 101.25% + 4,500 = EUR 1,017,000.00
At the CSD (T2S), on intended settlement date:
Check 1: Bank B has >= 1,000,000 nominal available in its securities account
Check 2: Bank A has >= EUR 1,017,000 on its cash account (or auto-collateralization)
Both true -> one atomic step:
Securities: B -1,000,000 A +1,000,000
Cash: A -1,017,000 B +1,017,000
Either false -> nothing moves; the instruction is retried in later settlement attempts
Key takeaways
- DvP links the securities and cash legs so that neither moves without the other, eliminating principal risk.
- The three BIS models differ in whether each leg settles gross or net.
- FoP transfers move securities without a linked cash leg and must be controlled carefully.
- From a systems view, DvP settlement is an atomic transaction across two ledgers: securities and cash.
🧪 Practice
- Beginner: Recompute the settlement amount if the clean price is 99.80% and accrued interest is EUR 6,250.
- Intermediate: Explain why a Model 2 system needs strong risk controls on cash debits, while a Model 1 system does not need them to the same extent.
- Interview: "Implement DvP settlement across a securities ledger and a cash ledger held in two different services." Hint: consider why this must be atomic, two-phase reservations (reserve securities and cash, then commit both), timeouts and release, and how to make retries idempotent.
Settlement Cycles (T+1, T+2)
Why they matter. Between trade and settlement, buyer and seller are exposed to each other: if one defaults, the other must replace the trade at the current market price. The longer the gap, the larger the potential price move, so the larger the risk and the margin required. Shorter cycles reduce risk but leave less time to match, fund and fix problems.
What they are. The settlement cycle is the number of business days between trade date (T) and intended settlement date (ISD). T+1 means settlement on the first business day after trade date, counting business days in the relevant settlement calendar (Chapter 1.4 and Chapter 11.1).
| Market | Current cycle | History and plans |
|---|---|---|
| US equities and corporate bonds | T+1 | Moved from T+2 on 28 May 2024 (Canada and Mexico on 27 May 2024) |
| US Treasuries | T+1 standard; T+0 common | Long-standing |
| India equities | T+1 (T+0 optional for some stocks) | Full T+1 from January 2023 |
| EU equities and bonds | T+2 | T+2 since October 2014; T+1 scheduled for 11 October 2027 |
| UK and Switzerland | T+2 | T+1 scheduled for 11 October 2027, aligned with the EU |
| Spot FX | T+2 (T+1 for USD/CAD and some others) | Market convention |
| Repo | Often T+0 | Market convention |
Example: from trade to settlement.
Trade on Thursday 9 Oct 2025 (US equity, T+1):
T Thu 9 Oct trade executed; allocation, confirmation, affirmation by end of day
(SEC Rule 15c6-2; DTCC affirmation cut-off 21:00 ET)
T+1 Fri 10 Oct settlement at DTC
Same trade in an EU equity (T+2):
T Thu 9 Oct trade executed
T+1 Fri 10 Oct matching, funding, securities positioning
T+2 Mon 13 Oct settlement (weekend skipped)
With a settlement holiday on Monday, T+2 rolls to Tuesday 14 Oct.
What compression to T+1 changes.
- Trade-date processing: allocations, confirmations and affirmations must be done on T, often within hours.
- FX funding: a foreign investor buying US shares must buy USD in time. With US T+1 and spot FX at T+2, investors trade FX for value T+1 or same day, or pre-fund.
- Securities lending recalls: less time to recall lent securities before a sale settles.
- Batch to real time: overnight batches that ran on T+1 must move into T.
Key takeaways
- The settlement cycle is the number of business days from trade date to intended settlement date.
- Shorter cycles reduce counterparty risk and margin but compress the time for matching, funding and exception handling.
- The US moved to T+1 in May 2024; the EU, UK and Switzerland plan T+1 for 11 October 2027.
- T+1 forces same-day affirmation, earlier FX funding and real-time processing.
🧪 Practice
- Beginner: Compute the intended settlement date for a T+2 trade on Wednesday 23 December 2026, assuming 25 and 28 December are settlement holidays.
- Intermediate: A European fund buys US shares on Monday. Explain the funding problem created by US T+1 and EUR/USD spot at T+2, and give two ways to solve it.
- Interview: "Our post-trade platform runs matching as an overnight batch. What must change to support T+1?" Hint: event-driven or intraday processing, earlier cut-offs, exception queues worked during the trade day, monitoring of affirmation rates, and dependencies on reference data such as SSIs.
Settlement Fails and Penalties
Why it matters. A trade that does not settle on its intended settlement date is a settlement fail. Fails leave both counterparties exposed, tie up liquidity and collateral, and can cascade: a firm that does not receive securities may in turn fail to deliver them to someone else (a daisy chain). Regulators impose penalties to make failing more expensive than settling on time.
What it is. Common causes of fails:
| Cause | Example |
|---|---|
| Lack of securities | Seller sold securities it has lent out or not yet received |
| Lack of cash | Buyer's cash account or credit line insufficient |
| Unmatched instructions | Quantity, amount, date or counterparty details differ |
| Wrong standing settlement instructions (SSIs) | Instruction sent to the wrong account or custodian |
| Late instructions | Sent after the CSD's cut-off |
Tools to reduce fails include partial settlement (settling the available quantity), shaping (splitting large trades into smaller deliveries), auto-collateralization (automatic intraday credit against securities being received), hold and release mechanisms, and securities lending.
Penalty regimes.
- EU CSDR settlement discipline: since 1 February 2022, CSDs apply daily cash penalties to the failing participant for each business day a matched instruction fails, and pass the money to the receiving participant. Rates depend on asset type, for example 1.0 basis point per day on the value of failing liquid shares and 0.10 basis points for sovereign bonds; cash fails use a rate based on the central bank's overnight lending rate. Mandatory buy-ins were included in CSDR but have not been applied; the 2023 CSDR Refit made them a last-resort tool. Check ESMA's current parameters, as rates are reviewed.
- US: Regulation SHO requires broker-dealers to close out fails to deliver in equities within short deadlines. For US Treasuries and agency debt, the Treasury Market Practices Group fails charge applies: an annual rate of 3% minus the fed funds target rate (lower bound, floored at zero), charged on the failed amount.
Example: CSDR cash penalty.
Failing delivery of liquid shares, market value EUR 2,000,000
Penalty rate: 1.0 bp per business day
Daily penalty = 2,000,000 x 0.0001 = EUR 200
Fails for 3 business days (ISD, ISD+1, ISD+2)
-> penalties: 3 x 200 = EUR 600, charged to the failing participant,
credited to the receiving participant.
(In practice the reference price is updated daily, so each day's amount can differ.)
Key takeaways
- A settlement fail is a trade that does not settle on its intended date; causes include lack of securities or cash, mismatched instructions and bad SSIs.
- Partial settlement, shaping, auto-collateralization and securities lending reduce fails.
- The EU applies daily cash penalties under CSDR; mandatory buy-ins remain a last resort.
- Fails create exposure, funding costs and cascading fails, so they must be monitored and resolved daily.
🧪 Practice
- Beginner: Compute the CSDR penalty for a 5-day failing delivery of sovereign bonds worth EUR 25,000,000 at 0.10 bp per day, assuming a constant price.
- Intermediate: Bank A fails to deliver to Bank B because Bank C failed to deliver the same securities to Bank A. Describe the penalty flows under CSDR and explain why Bank A's net penalty may be close to zero.
- Interview: "Design a fails dashboard for the settlement operations team." Hint: consider fails by reason code, age and counterparty, penalty accruals, receivables versus deliverables, pending versus matched instructions, and alerts for trades at risk of failing before the cut-off.
Central Counterparties (CCPs)
Why they exist. In a market where every firm trades with every other, each firm is exposed to the default of all its counterparties, and nobody can see the whole web of exposures. When Lehman Brothers failed in 2008, its bilateral derivative positions took years to unwind. A central counterparty sits in the middle of every trade, so each firm faces only the CCP, whose risk management is designed to survive the default of its largest members.
What it is. A CCP interposes itself between buyer and seller through novation: the original trade is replaced by two new contracts, buyer-CCP and CCP-seller. The CCP then:
- Nets each member's positions across all its trades.
- Collects initial margin (IM) to cover potential future losses on a member's portfolio if it defaults, and variation margin (VM) to settle daily mark-to-market gains and losses.
- Maintains a default fund to which all clearing members contribute.
- Runs a default management process: auctioning or hedging the defaulter's positions.
Examples include LCH and Eurex Clearing (derivatives and repo), CME Clearing and ICE Clear (futures and derivatives), Euronext Clearing, and NSCC and FICC in the US. In the EU, CCPs are regulated under EMIR.
Example: netting through a CCP.
Bilateral trades in the same bond:
A buys 100 from B
A sells 60 to C
C sells 30 to B
After novation, each member faces only the CCP:
A: +100 - 60 = net receive 40
B: -100 + 30 = net deliver 70
C: +60 - 30 = net receive 30
CCP: receives 70 from B, delivers 40 to A and 30 to C (CCP is flat)
Three bilateral deliveries totalling 190 become three net deliveries totalling 140,
and no member is exposed to another member.
The default waterfall. If a member defaults and its losses exceed what was collected from it, resources are used in a fixed order:
1. Defaulter's initial margin
2. Defaulter's default fund contribution
3. CCP's own capital ("skin in the game")
4. Non-defaulting members' default fund contributions
5. Assessments on non-defaulting members (capped)
6. Remaining CCP capital / recovery tools
Trade-offs. CCPs reduce and simplify counterparty risk, but concentrate it in one institution and create procyclical liquidity demands: in March 2020, sharp market moves triggered large margin calls exactly when liquidity was scarce. Treasury must forecast margin calls as part of liquidity management (Chapter 5.4). In the US, an SEC rule will require most cash Treasury trades to be centrally cleared from 31 December 2026 and repo from 30 June 2027.
Key takeaways
- A CCP becomes buyer to every seller and seller to every buyer through novation.
- It manages risk with netting, initial and variation margin, a default fund and a default waterfall.
- CCPs reduce bilateral exposure but concentrate risk and can create sudden liquidity needs through margin calls.
- Clearing mandates (EMIR, US Treasury clearing) are extending central clearing to more products.
🧪 Practice
- Beginner: Explain the difference between initial margin and variation margin.
- Intermediate: In the netting example, Bank B defaults before settlement. Which members are affected, and how does the CCP protect them?
- Interview: "Margin calls from our CCPs doubled overnight. How should treasury systems have anticipated this?" Hint: consider margin simulation under stressed market moves, the CCP's margin model and its sensitivity to volatility, intraday margin calls, and the liquidity buffer reserved for them.
DTCC in the US (DTC, NSCC, FICC)
Why it matters. Almost every US equity trade, corporate and municipal bond trade, and most US government securities trades pass through one organization: the Depository Trust & Clearing Corporation (DTCC). Anyone building post-trade or treasury systems for US securities will interact with its subsidiaries, each with a distinct role.
What it is. DTCC is a user-owned holding company. Its main US clearing and settlement subsidiaries are:
| Entity | Role | Products | Key service |
|---|---|---|---|
| DTC (Depository Trust Company) | CSD | Equities, corporate and municipal bonds, money market instruments | Book-entry settlement; end-of-day net funds settlement (DvP Model 2); custody and asset servicing |
| NSCC (National Securities Clearing Corporation) | CCP | Equities, corporate and municipal bonds, ETFs | Continuous Net Settlement (CNS): nets each member's trades per security into one daily position |
| FICC (Fixed Income Clearing Corporation) | CCP | Government Securities Division (GSD): Treasuries, agencies, repo; Mortgage-Backed Securities Division (MBSD): agency MBS | Netting and novation of government securities and repo trades; sponsored clearing |
US Treasury securities themselves are held and transferred on Fedwire Securities Service, operated by the Federal Reserve, not at DTC. FICC nets Treasury trades, and the resulting deliveries settle over Fedwire Securities through clearing banks.
Example: how an equity trade flows through NSCC and DTC.
T Broker A buys 10,000 XYZ from Broker B on an exchange
-> trade reported to NSCC, novated; NSCC becomes counterparty to both
-> CNS nets all of A's XYZ trades for the day: A net long 25,000 XYZ
T+1 CNS positions settle at DTC:
NSCC's CNS account delivers 25,000 XYZ to Broker A's DTC account
(DvP; DTC checks A's net debit cap and collateral)
End of day: DTC calculates each participant's net cash position;
participants with net debits pay via Fedwire Funds, net creditors are paid.
Institutional trades (fund managers via custodians) are confirmed and affirmed
through DTCC's institutional matching services and settle trade-for-trade at DTC.
DTC risk controls. Because cash settles net at the end of the day, DTC limits each participant's intraday exposure with a net debit cap and a collateral monitor: a delivery is only completed if the receiver's resulting net debit stays within its cap and is covered by collateral.
Key takeaways
- DTCC's subsidiaries split the US post-trade chain: DTC is the CSD, NSCC is the equity CCP, FICC is the government and MBS CCP.
- NSCC's CNS nets each member's trades per security into a single position settled at DTC.
- DTC settles securities gross during the day and cash net at the end of the day, controlled by net debit caps and collateral.
- US Treasuries settle on Fedwire Securities, not DTC; FICC is the CCP for them.
🧪 Practice
- Beginner: For each of the following, name the DTCC entity involved: clearing a Treasury repo, holding shares of a US company, netting a broker's equity trades.
- Intermediate: Explain why DTC needs a net debit cap and collateral monitor, linking your answer to the DvP models.
- Interview: "A US broker-dealer must now clear its Treasury repo trades. What changes in its treasury and liquidity management?" Hint: consider margin posted to FICC, netting benefits on the balance sheet, sponsored versus direct membership, and the timing of settlement on Fedwire Securities.
<a id="24-post-trade-processing-and-custody"></a>
2.4 Post-Trade Processing and Custody
This subchapter follows a securities trade from execution to settlement and explains how custodians, accounts and ledgers record the result. It is the view most engineers working on securities or treasury back-office systems need.
Post-Trade Processing Flow (Execution to Settlement)
Why it matters. A trade agreed in seconds on a trading screen leads to a chain of processing steps across front office, middle office, back office, counterparties, custodians and market infrastructures. Most operational losses and settlement fails in securities come from this chain, not from the trade itself. Understanding it end to end helps you see where data must be correct, and by when.
What it is. The typical steps after execution (Chapter 4.3 covers the treasury trade lifecycle in more detail):
| Step | What happens | Who | Typical messages |
|---|---|---|---|
| 1. Trade capture | Trade booked in the trading or treasury system with economic details | Front office | Internal; FIX execution reports |
| 2. Enrichment | Settlement details added: SSIs, accounts, place of settlement, fees, accrued interest | Middle/back office | Reference data lookups |
| 3. Allocation | Block trades split across funds or sub-accounts (buy side) | Investment manager | Allocation messages |
| 4. Confirmation and affirmation | Both sides agree the trade details; institutional trades are affirmed by the investor or custodian | Middle office, counterparties | Confirmation platforms; MT515/MT518 |
| 5. Clearing | Trade novated to a CCP or netted, where applicable | CCP | CCP trade feeds |
| 6. Settlement instruction | Instructions sent to custodian or CSD | Back office | MT540-MT543 or ISO 20022 sese.023 |
| 7. Settlement matching | CSD matches the two sides' instructions | CSD | Status: MT548 or sese.024 |
| 8. Settlement | DvP or FoP settlement on the intended date | CSD | Confirmation: MT544-MT547 or sese.025 |
| 9. Post-settlement | Positions, cash and accounting updated; reconciliation; corporate actions | Back office, custodian | Statements: MT535 (holdings), MT536 (transactions) |
The four settlement instruction types:
| MT | Meaning | ISO 20022 equivalent |
|---|---|---|
| MT540 | Receive free | sese.023 (receive, free of payment) |
| MT541 | Receive against payment | sese.023 (receive, against payment) |
| MT542 | Deliver free | sese.023 (deliver, free of payment) |
| MT543 | Deliver against payment | sese.023 (deliver, against payment) |
Example: a bank buys a bond, traced end to end.
T 10:15 Trader books: BUY EUR 5m nominal DE000XXXXXXX @ 99.40, T+2, from Dealer D
T 10:16 Enrichment: SSI for Dealer D -> Clearstream Frankfurt, account 7xxx
Our SSI -> custodian C, account 1234; accrued EUR 12,345.21
T 10:30 Electronic confirmation matched with Dealer D
T 11:00 MT541 (receive against payment) sent to custodian C
T 11:05 Custodian forwards instruction to the CSD (T2S)
T 14:20 MT548: instruction MATCHED with Dealer D's delivery instruction
T+1 Treasury cash forecast includes EUR 4,982,345.21 outflow on T+2
T+2 Settled in T2S night-time settlement (the T+2 settlement day starts on the
evening of T+1) -> MT545 (receive against payment confirmation)
T+2 Positions and cash updated; GL postings; MT535/MT536 reconciled next day
Settlement amount check: 5,000,000 x 99.40% = 4,970,000.00, plus accrued 12,345.21 = 4,982,345.21.
Key takeaways
- Post-trade processing runs from trade capture through enrichment, confirmation, clearing, instruction, matching, settlement and reconciliation.
- Settlement instructions come in four types: receive or deliver, free or against payment (MT540-MT543, or
sese.023). - Most fails trace back to early steps: wrong SSIs, late confirmations or bad static data.
- Status messages (MT548,
sese.024) let systems track each instruction from sent to matched to settled.
🧪 Practice
- Beginner: Which MT message type does a seller send for a DvP sale? Which confirmation does it receive when the trade settles?
- Intermediate: In the example, the MT548 at 14:20 reports "unmatched" instead of "matched". List the fields you would compare against the counterparty's instruction and the most likely causes.
- Interview: "Design the status model for settlement instructions in a back-office system." Hint: consider statuses such as created, sent, acknowledged, unmatched, matched, pending (with reason), partially settled, settled, cancelled, and how each MT548/
sese.024reason code maps to them and to actions for operations.
Securities Clearing: Matching, Netting and Novation
Why it matters. "Clearing" for securities covers everything that happens between the trade and settlement to establish exactly what each party must deliver and pay. Three mechanisms do most of the work: matching makes sure both sides agree, netting reduces the number and size of deliveries, and novation moves counterparty risk to a CCP.
What it is.
- Matching happens at two levels:
- Trade matching (confirmation): buyer and seller confirm the economic terms (security, quantity, price, trade date, settlement date) shortly after execution.
- Settlement matching: the CSD compares the delivery instruction from the seller with the receipt instruction from the buyer. Only matched instructions are eligible for settlement.
- Netting: offsetting obligations so that only net quantities and amounts settle. It can be bilateral (two parties agree to net) or multilateral (through a CCP or a netting system such as NSCC's CNS).
- Novation: the legal replacement of the original contract between buyer and seller with two new contracts with the CCP. It is what makes multilateral netting legally robust.
Settlement matching fields. CSDs define mandatory fields that must match exactly, plus a tolerance on the cash amount. In T2S, for example:
| Field | Must match |
|---|---|
| Delivering and receiving parties | Yes |
| ISIN | Yes |
| Quantity | Yes |
| Trade date | Yes |
| Intended settlement date | Yes |
| Payment type (DvP / FoP) | Yes |
| Settlement currency | Yes |
| Settlement amount | Within tolerance: EUR 25 above EUR 100,000, EUR 2 at or below |
Example: settlement matching result.
Field Seller (deliver) Buyer (receive) Result
ISIN DE000XXXXXXX DE000XXXXXXX match
Quantity 5,000,000 5,000,000 match
Trade date 2025-10-06 2025-10-06 match
Settlement date 2025-10-08 2025-10-08 match
Settlement amount 4,982,345.21 4,982,330.00 diff 15.21 <= 25 match
Counterparty our BIC / account their BIC / account match
=> MATCHED; settles at the seller's amount, 4,982,345.21, under T2S rules
Netting example: one firm, one security, one day.
| Trade | Direction | Quantity | Amount (EUR) |
|---|---|---|---|
| 1 | Buy | 300,000 | -301,500 |
| 2 | Sell | 200,000 | +201,800 |
| 3 | Buy | 50,000 | -50,100 |
| Net | Buy | 150,000 | -149,800 |
Without netting: three settlements. With netting (through a CCP): one receipt of 150,000 against payment of EUR 149,800.
| Mechanism | Purpose | Reduces |
|---|---|---|
| Matching | Ensure both sides agree before settlement | Fails, disputes |
| Netting | Fewer and smaller deliveries | Liquidity and operational load |
| Novation | Replace bilateral exposure with exposure to the CCP | Counterparty risk |
Key takeaways
- Securities clearing establishes final obligations through matching, netting and, when a CCP is involved, novation.
- Settlement matching compares both parties' instructions on mandatory fields, with a small tolerance on the cash amount.
- Netting reduces settlement volume and liquidity needs; novation makes multilateral netting legally sound.
- Unmatched instructions cannot settle, so matching status is a key early-warning signal for fails.
🧪 Practice
- Beginner: In the netting table, add trade 4: sell 150,000 for EUR 151,050. What is the new net position and amount?
- Intermediate: Two instructions differ only in settlement amount: EUR 80,000.00 versus EUR 80,003.50. Will they match in T2S? What if the amounts were EUR 800,000.00 and EUR 800,003.50?
- Interview: "Implement a settlement instruction matcher for a CSD." Hint: think about indexing unmatched instructions by the mandatory fields, applying amount tolerance as a secondary check, handling multiple candidates, allowance for optional fields that must match only if both sides fill them, and re-evaluating when an instruction is amended.
Custodians, Custody and Sub-Custody
Why they exist. An asset manager investing in 40 countries cannot become a participant in 40 CSDs, each with its own rules, tax regime, corporate action conventions and technical connections. Custodian banks do this on its behalf: they hold its securities safely, settle its trades and service its assets across markets through one relationship.
What it is.
- Custody: safekeeping of securities on behalf of clients, plus related services.
- Global custodian: a bank providing custody across many markets through one contract and one interface (examples include BNY, State Street, J.P. Morgan, Citi and BNP Paribas).
- Sub-custodian (local agent): a bank that is a direct participant in a local CSD and holds securities for the global custodian in that market. Global custodians use their own branches where they have them, and sub-custodians elsewhere.
- Holding chain: investor -> global custodian -> sub-custodian -> CSD. Each level keeps accounts for the level above.
Services typically provided.
| Service | Description |
|---|---|
| Safekeeping | Holding securities in segregated client accounts |
| Settlement | Instructing and settling trades in local markets |
| Asset servicing | Collecting coupons, dividends and redemptions |
| Corporate actions | Notifying and processing events: splits, rights issues, tender offers, elections |
| Tax services | Withholding tax relief at source and tax reclaims |
| Proxy voting | Passing voting rights to investors |
| Reporting | Holdings and transaction statements (MT535, MT536), valuations |
| Ancillary | Cash management, FX, securities lending, collateral management |
Account segregation. The way securities are held at each level determines what happens if an intermediary fails:
| Model | Description | Pros | Cons |
|---|---|---|---|
| Omnibus account | One account at the CSD/sub-custodian holds many clients' securities together | Efficient, cheaper, simpler | Clients depend on the intermediary's books to prove ownership; slower recovery in insolvency |
| Segregated account | Separate account per client at the CSD/sub-custodian | Clear ownership; easier recovery | More accounts, more cost and complexity |
In all models, client assets must be kept separate from the custodian's own assets, so that they are not part of its estate if it becomes insolvent. CSDR (Article 38) requires CSD participants to offer clients a choice between omnibus and individual segregation, and national rules (such as the UK's CASS rules and the US SEC Rule 15c3-3) set further protections.
Example: the custody chain for a fund holding Japanese shares.
Fund F (asset manager in Luxembourg)
| account at
v
Global custodian G books: Fund F holds 200,000 shares ABC (JP)
| omnibus account "G clients" at
v
Sub-custodian S (Tokyo) books: G clients omnibus holds 1,200,000 shares ABC
| participant account at
v
CSD (JASDEC) books: S client account holds 5,000,000 shares ABC
Dividend of JPY 30/share on ABC:
JASDEC -> S (5,000,000 x 30) -> G omnibus (1,200,000 x 30) -> Fund F (200,000 x 30 = JPY 6,000,000)
each level applies withholding tax and passes on its clients' share
Key takeaways
- Custodians hold securities on behalf of clients and provide settlement, asset servicing, corporate actions, tax and reporting services.
- Global custodians reach local markets through their own branches or sub-custodians that participate in local CSDs.
- Omnibus accounts are efficient; segregated accounts make ownership clearer in insolvency.
- Client assets must always be separated from the custodian's own assets.
🧪 Practice
- Beginner: Name four services a global custodian provides beyond safekeeping.
- Intermediate: The sub-custodian in the example becomes insolvent. Compare the position of Fund F if G holds an omnibus account versus a segregated account at S, and explain what records the administrator needs.
- Interview: "Our custody system must process a voluntary corporate action (a tender offer) across 3,000 client accounts. What are the main steps and risks?" Hint: consider event capture and validation from multiple sources, client notification, election deadlines at each level of the chain, default options, blocking of tendered positions and reconciliation of entitlements.
Cash Accounts
Why they matter. Securities settlement is only half of a trade; the other half is cash. Every securities account used for DvP settlement is linked to one or more cash accounts, and the balance on those accounts at the right moment decides whether trades settle. Cash accounts are also where coupons, dividends, redemptions, fees and margin flows land.
What they are. In the post-trade and custody context, a cash account holds money in one currency, linked to securities activity:
| Type | Held at | Purpose |
|---|---|---|
| Central bank settlement account (for example a T2S DCA) | Central bank | Cash leg of DvP settlement in central bank money, for direct participants |
| Custody cash account | Custodian bank | Client cash for settlement, income collection, fees, FX; commercial bank money |
| Margin and collateral account | CCP or clearing broker | Initial and variation margin |
| Client money account | Broker or bank | Client cash protected under client asset rules |
Key features.
- Currency: one currency per account, or a multi-currency account with one balance per currency.
- Link to securities accounts: each securities account has a default cash account per currency for DvP settlement.
- Credit facilities: custodians may provide overdraft or intraday credit, often secured on the client's securities. In T2S, auto-collateralization gives automatic intraday credit from the central bank, collateralized by eligible securities on the account, including those being purchased.
- Balance types: booked balance (what has settled), available balance (booked minus blocked or reserved amounts plus available credit) and projected balance (including pending settlements).
Example: a custody cash account for one settlement day.
Fund F - EUR cash account at custodian G Date: Wed 8 Oct 2025
Booked Projected (end of day)
Opening balance 1,200,000.00 1,200,000.00
Pending DvP purchase (bond, settles today) -4,982,345.21
Pending DvP sale (shares, settles today) +3,150,000.00
Coupon received 09:12 +62,500.00 +62,500.00
Custody fee (month-end accrual, not today) - -
------------ -------------
Balance 1,262,500.00 -569,845.21
Credit line secured on securities: 1,000,000.00
-> purchase can settle if the sale settles first, or using the credit line;
treasury/ops must decide whether to fund the account or rely on credit.
Key takeaways
- Each securities account is linked to cash accounts that carry the cash leg of settlement and asset servicing flows.
- Cash may be held in central bank money (for example T2S DCAs) or commercial bank money (custodian accounts).
- Booked, available and projected balances answer different questions; settlement depends on available balance at the moment of settlement.
- Credit lines and auto-collateralization help trades settle when cash and securities flows are out of sequence.
🧪 Practice
- Beginner: Explain the difference between booked, available and projected balance using the example.
- Intermediate: In the example, the sale fails and the custodian's credit line is EUR 1,000,000. Can the bond purchase settle? Show the numbers and describe two ways treasury could avoid the fail.
- Interview: "How would you compute an intraday projected cash balance for settlement accounts?" Hint: combine booked balance, expected settlements by settlement batch or time, their matching status and probability of settling, income events, credit lines and auto-collateralization capacity.
Securities Accounts
Why they matter. A securities account is the securities equivalent of a bank account: the place where holdings are recorded and from which deliveries are made. But securities positions have more dimensions than cash: quantities may be units or nominal amounts, and the same holding can be split into available, blocked, pledged, lent or pending parts. Getting the account model right is the foundation of every custody, settlement and collateral system.
What it is. A securities account records, for an account owner, the holdings of each security (identified by ISIN). Key concepts:
- Quantity type: shares and funds are held in units; bonds in nominal (face) amount, for example EUR 5,000,000 nominal.
- Account owner and structure: own (proprietary) account versus client accounts; omnibus versus segregated (see previous topic).
- Position buckets: a holding is usually split by status:
| Bucket | Meaning |
|---|---|
| Available | Free to deliver |
| Blocked | Reserved, for example for a corporate action election or a pending delivery |
| Pledged / collateral | Encumbered in favor of a third party (central bank, CCP, lender) |
| On loan | Lent out through securities lending; the lender keeps economic exposure but not the securities |
| Pending receipt | Instructed and matched receipts not yet settled |
| Pending delivery | Instructed and matched deliveries not yet settled |
- Traded versus settled position: the traded position includes all executed trades; the settled position includes only completed settlements.
Example: securities account holdings statement.
Account: 1234 - Bank A treasury investment portfolio As of: 8 Oct 2025, 18:00
ISIN Type Settled Available Pledged On loan Pend. receipt Pend. delivery Traded
DE000XXXXXXX Nom. 5,000,000 3,000,000 2,000,000 0 0 0 5,000,000
IT000YYYYYYY Nom. 10,000,000 7,000,000 0 3,000,000 0 2,000,000 8,000,000
US000ZZZZZZZ Units 120,000 120,000 0 0 30,000 0 150,000
Rules: Settled = Available + Pledged + On loan (+ Blocked, if any)
Traded = Settled + Pending receipt - Pending delivery
Note the IT bond: 2,000,000 is pending delivery but 7,000,000 is available, so the delivery can settle. If the pending delivery had been 8,000,000, the bank would need to recall part of the 3,000,000 on loan or it would fail.
Key takeaways
- Securities accounts record holdings per ISIN, in units for equities and nominal amounts for bonds.
- Holdings are split into buckets: available, blocked, pledged, on loan and pending; only available securities can be delivered.
- Traded and settled positions differ by pending receipts and deliveries.
- Invariants (bucket totals, traded versus settled) should be enforced and checked continuously.
🧪 Practice
- Beginner: Using the statement, how much of the DE bond can Bank A deliver today? Why not all 5,000,000?
- Intermediate: Bank A sells another 6,000,000 of the IT bond for settlement tomorrow. Update the IT row and identify what action is needed to avoid a fail.
- Interview: "Model a securities position store that supports these buckets with high concurrency." Hint: think about storing movements (events) rather than only balances, deriving buckets from movement states, atomic transfers between buckets, optimistic locking or per-account serialization, and reconciling against custodian MT535 statements.
Cash Ledger and Securities Ledger
Why they matter. A securities firm, custodian or treasury needs to know, at any time, exactly what cash and securities it holds and expects, for itself and for each client. That requires two linked books of record: a cash ledger and a securities ledger. Most reconciliation breaks, funding errors and failed trades in securities processing come from these two ledgers being out of step with each other or with the outside world.
What they are.
- Cash ledger: records every cash movement (settlements, income, fees, FX, transfers) per account and currency, with value dates. It produces booked and projected cash balances.
- Securities ledger: records every securities movement per account and ISIN (receipts, deliveries, corporate action entitlements, pledges, lending). It produces settled and traded positions.
- Double entry for securities: like cash, each securities movement has two sides. A receipt from a counterparty is recorded as a debit to the client's (or own) position and a credit to a counterparty or "pending settlement" account; the sum of all positions in a security across all accounts, including the custodian's or CSD's account, must equal what is held at the next level in the chain.
- Trade date versus settlement date accounting:
- Trade date accounting records positions and cash obligations when the trade is executed, with pending settlement accounts until settlement.
- Settlement date accounting records them only when settlement happens. Many firms keep both views: trade date for risk and P&L, settlement date for actual holdings and cash.
Example: a DvP purchase in both ledgers.
Trade: buy 10,000 shares XYZ at EUR 50.00, T = 6 Oct, ISD = 8 Oct, cost EUR 500,000
T (6 Oct) - trade date entries
Securities ledger: Dr Account 1234 / XYZ (pending receipt) 10,000
Cr Counterparty D / XYZ (pending delivery) 10,000
Cash ledger: Dr Pending settlement payable (Cpty D) 500,000.00 value 8 Oct
Cr Cash account EUR (projected) 500,000.00 value 8 Oct
ISD (8 Oct) - on settlement confirmation (MT545)
Securities ledger: pending receipt -> settled: Account 1234 / XYZ settled +10,000
Custodian/CSD nostro position for XYZ +10,000
Cash ledger: pending payable cleared; booked cash -500,000.00
Positions over time:
Traded XYZ Settled XYZ Booked cash Projected cash
5 Oct 0 0 1,000,000.00 1,000,000.00
6 Oct 10,000 0 1,000,000.00 500,000.00
8 Oct 10,000 10,000 500,000.00 500,000.00
Reconciliations that must hold.
| Reconciliation | Compares |
|---|---|
| Securities position | Internal securities ledger (settled) vs custodian/CSD statement (MT535 / semt.002) |
| Cash | Internal cash ledger vs bank statement (MT940/950 / camt.053) |
| Cash vs securities | Every settled DvP has both a securities and a cash movement of the agreed amount |
| Ledger vs GL | Subledger balances vs general ledger accounts (Chapter 1.4) |
Key takeaways
- Securities processing needs two linked books of record: a cash ledger and a securities ledger.
- Both use double entry; securities positions across all accounts must agree with holdings at the next level of the chain.
- Trade date views show exposure and P&L; settlement date views show actual holdings and cash.
- DvP settlement must update both ledgers together, and reconciliations check each ledger against external statements and each other.
🧪 Practice
- Beginner: In the example, why does projected cash drop on 6 October while booked cash drops only on 8 October?
- Intermediate: The trade fails on 8 October and settles on 9 October. Rewrite the positions table, and explain what the treasury cash forecast should have shown on the morning of 8 October.
- Interview: "The custodian's statement shows 10,000 XYZ, our securities ledger shows 10,000 settled, but our cash ledger shows no payment. Where do you look?" Hint: consider a settlement confirmation processed only on the securities side, a missing or failed cash posting, different message flows for securities and cash confirmations, and why both legs should be posted from one settlement event.
Transfer Procedures (DvP, FoP, Internal and External Transfers)
Why they matter. Securities move for many reasons: trades, collateral, portfolio transfers between custodians, account restructuring, corporate actions. Each movement must be instructed with the right procedure, or it will fail to match, settle in the wrong way, or move assets without payment. Choosing and controlling the right procedure is a core operational and fraud-prevention concern.
What they are. Transfers are classified along two dimensions:
- Payment linkage:
- DvP / RvP: securities against cash, simultaneously (see Delivery vs Payment in Chapter 2.3).
- FoP: securities only, no linked cash (DFP: deliver free; RFP: receive free).
- Where the transfer happens:
- Internal transfer (book transfer): both accounts are at the same custodian. The custodian moves the securities in its own books; nothing changes at the CSD, because the securities remain in the same omnibus account there.
- External transfer: the accounts are at different custodians or CSD participants. The transfer settles at the CSD, between participant accounts.
- Cross-CSD transfer: the counterparties use different CSDs. The transfer uses CSD links (or a common platform such as T2S, or the Euroclear-Clearstream Bridge for ICSDs), and the issuer CSD's records must be realigned to reflect which investor CSD now holds the securities.
| Procedure | Cash leg | Settles at | Typical use | Key controls |
|---|---|---|---|---|
| Internal DvP | Internal cash accounts | Custodian books | Trade between two clients of the same custodian | Both accounts' balances; same-time posting |
| Internal FoP | None | Custodian books | Moving securities between a client's own accounts | Authorization; beneficial owner unchanged? |
| External DvP | Central bank or custodian cash | CSD | Market trades | Matching, cut-offs, cash and securities availability |
| External FoP | None, or settled separately | CSD | Custodian change, collateral, portfolio transfer | Strong authorization; four-eyes; payment confirmed separately |
| Cross-CSD | Either | Links between CSDs | Cross-border trades and collateral | Link cut-offs, realignment, longer timelines |
Example: internal vs external transfer.
Internal: Fund F sells 50,000 ABC to Fund H; both at custodian G
G's books: Fund F -50,000 ABC +EUR 2.5m
Fund H +50,000 ABC -EUR 2.5m
CSD: G's omnibus account unchanged (still holds both funds' shares)
External: Fund F sells 50,000 ABC to Fund K at custodian M
G sends MT543 (deliver vs payment) to the CSD on F's behalf
M sends MT541 (receive vs payment) to the CSD on K's behalf
CSD matches and settles: G omnibus -50,000 ABC / +EUR 2.5m
M omnibus +50,000 ABC / -EUR 2.5m
G then updates Fund F's account; M updates Fund K's account
Why FoP needs special controls. An FoP delivery moves value out of an account with nothing coming back. It is the procedure most open to error and fraud: a mistyped receiving account or a fraudulent instruction can move millions with no automatic counter-check. Typical controls include dual authorization, restricted user entitlements, pre-approved receiving accounts, call-back verification for client-initiated transfers, and checks that any related payment has been received.
Key takeaways
- Transfers differ by payment linkage (DvP/RvP versus FoP) and by location (internal, external at the CSD, or cross-CSD).
- Internal transfers change only the custodian's books; external transfers settle at the CSD between participants.
- Cross-CSD transfers rely on CSD links and realignment, and have longer timelines and earlier cut-offs.
- FoP transfers move value with no counter-leg and require the strongest controls.
🧪 Practice
- Beginner: For each scenario, choose internal or external, and DvP or FoP: a client moves its portfolio from custodian G to custodian M; two clients of G trade with each other; a bank posts bonds as collateral to a CCP.
- Intermediate: A client transfers its portfolio of 300 securities from custodian G to custodian M. Describe the sequence of instructions, the matching requirements on both sides, and how to handle securities with pending corporate actions.
- Interview: "A user submits an FoP delivery of EUR 40 million of bonds to an account never used before. What should the system do?" Hint: consider risk-based rules (amount, new receiving account, unusual time), mandatory second approval, independent verification, holding the instruction before the CSD cut-off, and audit logging.
<a id="3-financial-markets-and-instruments"></a>