Settlement Instruction

Overview

A settlement instruction is a formal message or record directing the transfer or posting of funds, securities, or other assets to discharge an obligation. It states the parties, accounts, asset, amount, timing, and reference needed for settlement. They may be sent individually, included in a batch file, transmitted through a financial message network, or applied directly to an internal or distributed ledger.

Before submission, the system should validate authority, participant eligibility, destination, asset or currency, amount, available funding, cutoff, duplicate status, and relationship to the source obligation. Changes after approval should create a new version or replacement rather than silently altering the authorized record. An instruction can be accepted, rejected, queued, partially processed, canceled where allowed, or finally settled. The implementation should identify the obligation, participants, settlement asset, accounts or addresses, value date, liquidity source, posting sequence, and evidence of finality.

Settlement Instruction should remain distinct from Settlement and Settlement Asset, because each can represent a different stage, record, control, or financial outcome.

Reconciliation connects the instruction with actual account entries and confirms that retry or timeout handling did not create duplicate settlement. Teams should design for incorrect obligations, liquidity shortfalls, participant default, wrong settlement assets, premature finality, and unreconciled movements.

Every response and external identifier should be preserved. Controls should validate instructions, funding, destination, currency or asset, cutoffs, and participant positions before treating a settlement step as complete. Important failure modes include insufficient liquidity, duplicate instructions, wrong settlement assets, delayed delivery, participant default, unmatched evidence, and premature claims of finality.