WorkflowInvestment Operations & Middle Office

Learn · the settlement chain

What is a settlement instruction? From the SSI to the CSD by 23:59

A settlement instruction is the trade-specific order a participant sends to the central securities depository to deliver or receive securities and cash; the standing settlement instruction is the reference data it is built from. This guide follows one trade from SSI to matched instruction under the new EU and UK trade-date deadlines, and shows where Standard Settlement Instruction Management fits.

Updated · 13 min read

See one case, screen by screen →
Watch with transcript →

A settlement instruction is the order a participant in a central securities depository (CSD) sends to deliver or receive a specific quantity of a security, usually against a specific amount of cash, on a specific date. It is built from two things: the trade's own details, such as the security, quantity, price and dates, and the counterparty's standard settlement instruction (SSI), which supplies the accounts, the participants and the place of settlement. Each side sends its own instruction, and the CSD settles only when the two match. Under the EU's 2026 rules, CSDs must ask their participants to send instructions by 23:59 CET on trade date where feasible from October 2027, and the UK plan sets 05:59 on the morning after the trade, so an error in the SSI now surfaces at night, when no one is at the desk to fix it. Botminds' Standard Settlement Instruction Management works upstream of the instruction: it keeps each SSI current and proven, and makes every approved change live at a set time, so the instructions built from it are right the first time.

The examples use a fictional asset manager, Quillfield Capital, and its fictional counterparties as they run through the solution; the rules are linked where they appear.

From standing instruction to matched settlement: what each step adds, and who does it

  1. A person decides

    SSI agreed and approved

    The counterparty’s accounts, agents and place of settlement are verified with it and approved by two people, once.

    Never: Taken from an unverified email

  2. Agent

    Trade booked, SSI attached

    The order management system adds the SSI for this counterparty, market and asset to the trade.

  3. A person decides

    Allocation and confirmation

    The asset manager allocates the block to funds and confirms terms with the broker on trade date, with the accounts and place of settlement from the SSI.

  4. Agent

    Settlement instruction generated

    Each side’s custodian builds its instruction from the trade and the SSI it holds, and sends it to the CSD.

  5. Agent

    Matching at the CSD

    The CSD compares the two instructions field by field; a match makes them eligible to settle on the intended date.

  6. Agent

    Settlement

    Securities and cash move, delivery against payment, if both sides have the assets.

Our summary of the chain for an institutional trade settled through a custodian. Steps marked agent here are automated systems, such as order management, the custodian's instruction engine and the CSD's matching. Who acts varies: some asset managers instruct the CSD through their custodian, some brokers instruct directly as CSD participants. The first step is the one Standard Settlement Instruction Management covers; the agents assist, and a person verifies and a different person approves.

What is a settlement instruction?

In EU law a settlement instruction is "a transfer order as defined in point (i) of Article 2 of Directive 98/26/EC" (Delegated Regulation (EU) 2018/1229, Article 1). That directive, on settlement finality, describes a transfer order for securities as an instruction by a participant to transfer title to, or an interest in, securities by a book entry on a register, and for cash as an instruction to place money at a recipient's disposal (Directive 98/26/EC, original text). In plain terms: it is the order that actually moves the asset, and once a system has accepted it under its rules, the finality protections attach to it.

An instruction is specific. It names one security by its ISIN, one quantity, one cash amount, one trade date and one intended settlement date, whether it delivers or receives, and the two participants. It exists for one trade, or one allocation of a trade, and disappears once settled or cancelled.

How is a settlement instruction different from an SSI?

The SSI is standing data and the settlement instruction is a message: the SSI says where a counterparty settles every trade of a type, and the instruction says what to settle on this trade. The UK's T+1 report draws the line in the same place when it says SSIs should make it unnecessary for counterparties to exchange instructions trade by trade, because each side can build the instruction from the trade and the SSI it already holds (UK Accelerated Settlement Technical Group, February 2025). What are standard settlement instructions in detail is covered in what an SSI holds and who owns each line.

Confusingly, "settlement instructions" is also what many people call the SSI letter a counterparty sends. A "settlement instruction letter" is almost always an SSI notice, not a trade instruction, and who signs a settlement instruction letter deals with it. In this guide, an instruction is the trade-level message.

Which fields must match at the CSD?

In the EU, Article 5(3) of the settlement discipline standards lists them: CSDs must require participants to use eleven named matching fields, plus any others the CSD needs (Delegated Regulation (EU) 2018/1229). Eight of the eleven come from the trade. Three come from standing data, and an error in standing data repeats on every trade.

The eleven EU matching fields, and where each value comes from

Matching field, Article 5(3)Comes fromWhat breaks it
(a) Type of settlement instructionThe tradeDelivery against payment on one side, free of payment on the other
(b) Intended settlement dateThe trade and the market calendarA holiday counted on one side and not the other
(c) Trade dateThe tradeA late booking re-dated
(d) CurrencyThe tradeSettlement currency differs from trade currency
(e) Settlement amountThe tradeOutside the CSD’s tolerance: EUR 2 up to EUR 100,000, EUR 25 above
(f) Nominal value or quantityThe tradeUnits on one side, face amount on the other
(g) Delivery or receiptThe tradeBoth sides instructing to receive
(h) ISINThe trade and the security masterA new line or a corporate action changes the ISIN
(i) Delivering participantThe SSIAn old participant code in a stale SSI
(j) Receiving participantThe SSIA counterparty that moved custodian
(k) CSD of the counterparty, on a common infrastructureThe SSIThe counterparty settles through another CSD than expected
Fields quoted in short form from Article 5(3) of Delegated Regulation (EU) 2018/1229; point (l) lets each CSD add its own. Tolerances from Article 6, which allows EUR 2 per instruction up to EUR 100,000 and EUR 25 above. The 'comes from' and 'what breaks it' columns are our reading.Source: Delegated Regulation (EU) 2018/1229

The place of settlement is not on the list. Respondents to ESMA's 2024 consultation noted that a mismatch in the place of settlement still stops matching even though it is "not a mandatory matching criteria at trade level" (ESMA, technical advice on the CSDR penalty mechanism, November 2024). The 2026 amendments put it on the allocation instead, which place of settlement (PSET) explains. They also extend the transaction-type field in instructions to buy-sell-backs from December 2026 and add a place-of-trading field, the trading venue's market identifier code, from July 2027 (Delegated Regulation (EU) 2026/1536).

What is the EU's 23:59 CET target, and the UK's 05:59 deadline?

They are the times by which settlement instructions should reach the CSD under T+1. In the EU, from 11 October 2027, "CSDs shall require participants to send settlement instructions as soon as possible and where feasible by 23:59 CET on the business day on which the transaction has taken place" (Delegated Regulation (EU) 2026/1536). In the UK, action SETT 02 of the T+1 plan says instructions to the CSD should be submitted "no later than 05.59 UK time on T+1", with CREST's opening hours on trade date extended to 21:00 (UK Accelerated Settlement Technical Group).

Trade-date night under T+1: what has to be done, by when, in each market's own time

EU (CET)from 7 Dec 2026 and 11 Oct 2027
Allocations and confirmations to the brokerby 23:00
To CSDby 23:59
Later instructions: still processedafter 23:59
  • Allocations and confirmations to the brokerby 23:00
  • To CSDby 23:59
  • Later instructions: still processedafter 23:59
UK (London)T+1 plan, SETT 01 and 02
Allocations and confirmationsby 23:59 T
Settlement instructions to the CSDby 05:59 T+1
  • Allocations and confirmationsby 23:59 T
  • Settlement instructions to the CSDby 05:59 T+1
US (New York)Rule 15c6-2, since May 2024
Allocation, confirmation, affirmationby end of T
Overnight to settlement on T+1T+1
  • Allocation, confirmation, affirmationby end of T
  • Overnight to settlement on T+1T+1
Each lane runs from 18:00 on trade date to 06:00 the next morning in local time. EU: the 23:00 CET allocation deadline applies from 7 December 2026 and the 23:59 CET instruction target from 11 October 2027 (Delegated Regulation (EU) 2026/1536, Article 2). UK: actions SETT 01 and SETT 02 of the Accelerated Settlement Technical Group report; UK T+1 still needs legislation. US: under Rule 15c6-2, broker-dealers' agreements or procedures must see allocation, confirmation and affirmation done on trade date.Source: Delegated Regulation (EU) 2026/1536; UK Technical Group report; 17 CFR 240.15c6-2

The EU target is softer than it looks. The regulation's recital says that sending instructions after 23:59 "should not prevent CSDs from processing those settlement instructions, nor give rise to the application of cash penalties" unless the ordinary conditions for penalties are met. The deadline exists so that CSDs can run their overnight optimisation on as many instructions as possible; missing it costs a night's chance to settle, not a fine in itself.

How does an SSI become a settlement instruction?

Through two copies of it. Your custodian builds your instruction from the SSI you hold for the broker; the broker's custodian builds the broker's from the SSI the broker holds for your fund. If both copies are current, the participant fields match without anyone looking at them. If one is stale, the CSD sees two honest instructions that disagree, and neither side's system shows an error until matching fails.

That is why the timing of an SSI change matters as much as its content. A change must go live on both sides at the same moment, and trades already booked against the old details must settle there. In the sample, Kawabe Securities' new Japanese settlement agent took effect at 00:01 Tokyo on 26 October; trades settling before then stayed on the old agent, and 41 JPY equity trades settled to the new instruction afterwards.

Approved SSI changes go live at an agreed time, in every system that builds instructions from them

Go-live calendar in Standard Settlement Instruction Management: 27 changes from 20 to 26 October, 9 live today, each going live only at the agreed time in every system with a receipt from each. A warning banner says the link to custodian B failed at 07:58 London, with 3 messages queued for Calder Mount, Montclair Ridge and Thornbury Prime; they are live in the SSI master and order management but the custodian is not yet updated, retrying every 10 minutes, with a Retry now button. Calendar columns from Tuesday 20 to Monday 26 list changes at 00:01. A side panel for Kawabe Securities shows the JPY equities settlement agent change effective 26 October at 00:01 Tokyo, maker Wei Ling Tan, checker Marcus Lee, and receipts at 00:01 Tokyo from the SSI master, order management, custodian C and payments.
Fictional sample data. A change that is live in the SSI master but not at the custodian would produce instructions from the old details; the banner shows the gap and the three counterparties it affects until the custodian confirms.

What fails when the SSI and the instruction disagree?

Matching fails, and with it the trade's chance of settling on the intended date. EU CSDs must offer participants the option to be told about a counterparty's unmatched instruction within an hour of the first failed matching attempt, or at once close to the cut-off (what the resulting status codes mean is in MT548 reason codes), and must recycle failed instructions "until they have been settled or bilaterally cancelled" (Delegated Regulation (EU) 2018/1229, Articles 9 and 11). Someone then has to find which side is wrong, which under T+1 means doing it overnight or early on the settlement date.

One trade, two copies of the broker's SSI: current versus stale

Your copy is currentYour copy is stale
Trade date, 18:00

Your copy is current: Allocation sent with the broker’s current participant and accounts.

Your copy is stale: Allocation sent with the participant the broker left last month.

Confirmation

Your copy is current: Broker confirms; details agree.

Your copy is stale: Broker confirms the economics; few systems compare the settlement details at this stage.

Instruction to the CSD

Your copy is current: Both custodians instruct; participant fields agree.

Your copy is stale: Your custodian instructs to the old participant; the broker’s custodian instructs from its own data.

Matching

Your copy is current: Matched within minutes; eligible for the overnight cycle.

Your copy is stale: Unmatched; each side is told the other’s instruction is pending.

Settlement date

Your copy is current: Settles.

Your copy is stale: Someone traces the mismatch, corrects the SSI and re-instructs; the trade may settle late or fail.

Our illustration of the mechanics under EU matching rules. Where a fail follows, EU cash penalties, buy-in rules and the US close-out rules apply; Failed Trade Management covers that stage.

What it costs once a trade has failed is worked through in CSDR penalties calculation; the cost of one wrong SSI across every trade it touches is worked through in settlement instructions management: what one wrong SSI costs. The prevention is older than T+1. The CPSS–IOSCO recommendations for securities settlement systems of November 2001, which the 2012 principles keep in effect, put it in one sentence:

“Speedy, accurate verification of trades and matching settlement instructions is an essential precondition for avoiding settlement failures, especially when the settlement cycle is relatively short.”

CPSS-IOSCO, Principles for financial market infrastructures (April 2012), Annex C, Recommendation 2, explanatory note 3.10

Why the US settled the question differently

The US moved to T+1 on 28 May 2024 without trade-date deadlines for instructions to the depository. Its rule sits one step earlier: Rule 15c6-2 makes broker-dealers put agreements or procedures in place so that allocation, confirmation and affirmation are finished on trade date itself (17 CFR 240.15c6-2). The SEC was asked to require that settlement instructions be linked to the affirmation and declined: "the Commission is not modifying the rule to include a requirement for linking the transmission of settlement instructions to the receipt of an affirmation", noting that it would need custodians' cooperation (SEC, Shortening the Securities Transaction Settlement Cycle, 2023).

The market structure also differs. In the SEC's words, DTC "is the CSD that provides custody and book-entry transfer services for the vast majority of securities transactions in the U.S. market", so the US place-of-settlement question that divides European markets rarely arises for domestic trades. The SSI problem does not go away: the same release observed that firms' local matching tools "often rely on inconsistent SSI data independently maintained" across brokers, managers and custodians.

Where Standard Settlement Instruction Management sits in the chain

It sits before the first instruction, at the point where an SSI is created or changed. The CPMI–IOSCO principles describe straight-through processing as "procedures that require trade data to be entered only once and then use those same data for all post-trade requirements related to settlement" (PFMI, Annex C); for settlement data, that single entry is the SSI. If it is right and proven, every allocation and instruction built from it inherits that. If it is wrong, automation repeats the error faster.

The solution reads each change request in any language, cites every field to its source, compares it with the counterparty's own authenticated data, checks formats, the place of settlement and sanctions lists, and books a call-back to the number on file. An analyst verifies, a different team lead approves, and the Go-live agent makes the change live in the SSI master, order management, the custodians and payments at the agreed time, collecting a receipt from each. To see it on a month of your own change requests, start from Standard Settlement Instruction Management.

Questions people ask

What does "matched" mean for a settlement instruction?

It means the CSD has found the counterparty's instruction for the same trade and the matching fields agree, within the cash tolerance. A matched instruction is eligible to settle on its intended date if both sides have the securities and cash. In the EU, a matched instruction is cancelled bilaterally, through the CSD's cancellation facility.

What happens if an instruction is sent after 23:59 CET?

The CSD still processes it. Delegated Regulation (EU) 2026/1536 says late submission should not prevent processing or by itself give rise to cash penalties. The cost is practical: the instruction may miss the CSD's overnight settlement, leaving less of the settlement date to resolve any mismatch.

What is hold and release?

A CSD function that lets a participant put its own pending instruction on hold and release it later, wholly or, from October 2027 in the EU, partly. Firms use it to instruct early, so the instruction can match, while keeping control of when it settles, for example until a client's cash arrives.

Can a settlement instruction be changed after it is sent?

Not in place. A wrong instruction is cancelled and a new one sent; once matched, the cancellation needs both sides. That is why a stale SSI is costly under T+1: correcting one instruction means a cancellation, a new instruction and a new match, all before the settlement cut-off.

What is the tolerance for settlement amounts?

In the EU, CSDs match instructions whose cash amounts differ by up to EUR 2 for amounts up to EUR 100,000 and EUR 25 above, or the equivalent in other currencies. From December 2026, firms must require professional clients to apply the CSD's tolerance when they state the cash amount in their allocations.

Standard Settlement Instruction Management.
See it on your own files.

An agentic solution from Botminds. Keeps counterparty settlement instructions current and fraud-checked for settlement operations Book a demo, or explore how it works.