From order to settlement: the systems that change a trade’s state
A trade lifecycle is the sequence of instructions, executions, allocations and obligations through which a transaction reaches its financial outcomes. Different systems maintain different stages of that lifecycle, so a single success flag cannot describe the whole transaction.
Orders and executions
An order management system, or OMS, maintains intended orders and their lifecycle. An execution management system, or EMS, supports executing orders across available destinations. A venue interface accepts specified messages and returns venue status within a narrower boundary.
A parent order expresses the original intent. Child orders represent instructions routed to execution destinations. Acknowledgement records acceptance at a specified interface; a fill records executed quantity and price. An accepted order can remain partly or wholly unfilled.
The order record therefore needs relationships among the original quantity, routed quantity, fills, cancellations and remaining interest. A change to one child order does not automatically establish the state of the parent order.
Allocations and matched trades
Trade capture records executions. Allocation assigns executed activity to accounts. Confirmation records agreed economic details, while matching compares the relevant records from the parties or their agents. These operations prepare downstream processing without themselves transferring cash or securities.
Take an order for 1,000 shares filled in quantities of 600 and 400, then allocated as 700 and 300 to two accounts. The fills and allocations both total 1,000 shares, but they represent different relationships. Reconciliation needs those relationships, not an assumption that each fill corresponds to one allocation.
DTCC’s Central Trade Manager, or CTM, provides allocation, confirmation and matching functions. Its role differs from the Continuous Net Settlement service, or CNS, which nets eligible transactions by security and member. Access to one service does not identify every downstream participant or settlement arrangement.
Net obligations and settlement records
Netting combines eligible obligations under the relevant mechanism. Settlement discharges obligations through transfers. Gross trade details remain necessary to explain a net position, investigate a difference or process a correction.
A matched trade can still encounter an inventory shortage, missing funding or a downstream instruction problem. Matching establishes agreement at its defined boundary; settlement requires the subsequent transfer conditions to be met.
Corrections across the lifecycle
An amendment needs to retain the relationship to the original event. Overwriting the latest screen value without preserving that relationship makes it difficult to determine whether downstream records reflect the old instruction or the corrected one.
The exact sequence varies by asset, market and participant arrangement. The stable distinction is between intended activity, executed activity, account allocation, agreed obligations and completed transfers. Each state needs its own authoritative evidence and reconciliation boundary.
Questions about OMS
Does an accepted order mean a trade occurred?
No. Acceptance confirms an instruction entered a defined state; execution requires a fill.
Does a matched trade mean settlement finished?
No. Matching compares trade details; settlement discharges the resulting obligations.
Sources and method
- FlexTRADER Execution Management System FlexTrade
- OUCH Nasdaq
- CTM DTCC
- Continuous Net Settlement DTCC
- FIX Trading Community Standards FIX Trading Community
Read next
- Payment accepted, account posted, funds settled: three different states
Payment accepted does not mean funds settled. Separate an interface response, a customer ledger posting and the settlement event.
- Positions, accounting balances and risk exposures
A position, an accounting balance and a risk exposure describe different views of a trade. See where their numbers diverge.
- Execution benchmarks can reward unfinished orders
A benchmark based on filled orders can hide the cost of unfinished work. See how residual orders can reverse an execution ranking.
