The settlement instruction life cycle is the sequence of stages a securities settlement instruction passes through inside a securities settlement system or central securities depository. It runs from the moment the instruction is sent, through checks, matching and settlement, to its final status of settled, partly settled or cancelled. At each step the system sends status messages so that both parties and their custodians know where the trade stands.
The stages are broadly similar across markets, but the Eurosystem's TARGET2-Securities (T2S) platform, which settles for most euro area CSDs, gives a clear and well documented model and is used here as the main example. Life-cycle management matters for operations teams because every failed or delayed instruction carries funding costs, and in the EU it can lead to cash penalties under the Central Securities Depositories Regulation (CSDR).
Submission and validation
An instruction is usually sent by a CSD participant, or by the CSD on its behalf, and states the security, quantity, cash amount, counterparties, trade date and intended settlement date. On arrival it goes through validation: the system checks the format, that the accounts and security exist and are open, and that the participant is allowed to use them. An instruction that fails validation is rejected with a reason code and never enters the later stages.
Matching
Most instructions have two sides: a delivery and a receipt, sent separately by the seller and the buyer. The system compares them on a set of mandatory matching fields and some optional ones, with a small tolerance for the cash amount. When the counterparty has not yet instructed, its side may receive an allegement telling it that an instruction is waiting against it. Once the two sides agree they are matched and, in most systems, can no longer be changed by one party alone. In T2S, unmatched instructions are cancelled automatically after a set number of business days. Some instructions, such as those sent by a CSD for internal transfers or by a central counterparty on behalf of both sides, arrive already matched, which saves time and removes one common cause of delay.
Eligibility and settlement
A matched instruction is eligible for settlement when its intended settlement date has arrived, it is not on hold, any linked instructions are ready and no settlement restriction blocks it. The system then checks provision: whether the seller holds enough securities and the buyer enough cash or credit, including any auto-collateralisation that can be generated on the spot. If both legs are covered, securities and cash move together under delivery versus payment and the transfer is final.
In T2S most instructions for a given date are first processed in night-time settlement cycles at the start of the settlement day, and those that remain are tried continuously during day-time settlement.
Partial settlement, recycling and failure
If one side lacks enough securities, the system may settle part of the quantity where both parties allow partial settlement, leaving the rest pending. Instructions that cannot settle are not rejected; they are recycled and tried again whenever new securities or cash arrive, and optimisation routines look for chains of instructions that can settle together. An instruction still unsettled at the end of its intended settlement date becomes a settlement fail and carries over to the next day.
Holds, amendments and cancellations
Participants can put their own instructions on hold and release them later, a tool used by custodians that wait for client confirmation or funding; see Hold and Release Mechanism. Some fields, such as the priority or partial settlement indicator, may be amended after matching, but core trade details cannot. A matched instruction can only be cancelled when both sides ask, through bilateral cancellation, while an unmatched one can be cancelled by its sender alone.
Status reporting
Throughout the cycle the system reports each change: accepted or rejected, matched or unmatched, pending with a reason such as lack of securities, partly settled, settled or cancelled. In ISO 20022 these updates travel in the settlement status advice and settlement confirmation messages, while older markets still use equivalent SWIFT MT messages. Participants use these reports to manage fails, chase counterparties and reconcile their records with the CSD. Many firms feed them into exception dashboards that rank pending trades by value and age, so that operations staff can deal first with those most likely to fail or attract penalties.
External links
Ref 1130000831