In institutional trading systems, an order is never just a static database record; it is an active state machine governed by formal transition rules. From the instant a portfolio manager creates an order intention to the final settlement allocation, every stage is tracked with deterministic states that prevent invalid operations, double-executions, and race conditions.
The Financial Information eXchange (FIX) protocol standardizes order status using Tag 39 (OrdStatus) and Tag 150 (ExecType) within FIX Tag 35=8 (ExecutionReport) messages. An order begins in a staged or 'Pending New' (OrdStatus=A) state as it travels to the broker or exchange. Once acknowledged by the market venue, it transitions to 'New' (OrdStatus=0). As executions occur, the order moves to 'Partially Filled' (OrdStatus=1), accumulating filled quantity (Tag 14 CumQty) and updating the average price (Tag 6 AvgPx) until it reaches the terminal state of 'Filled' (OrdStatus=2).
Terminal states represent endpoints in the state machine: 'Filled' (2), 'Cancelled' (4), 'Rejected' (8), or 'Expired' (C). Once an order enters a terminal state, no further fills, cancels, or amendments can be processed against its client order ID (Tag 11 ClOrdID). If a broker gateway attempts to send an execution against a cancelled order, the OMS state machine rejects the message and raises an operational alert.
At Atlantic Horizon Asset Management, the central OMS processes hundreds of thousands of state transitions daily across global equity and fixed income desks. When Atlantic Horizon executes a 250,000 share parent order in AstraZeneca plc (AZN.L), the OMS orchestrates dozens of child order state machines concurrently. Each child transitions through Pending New, New, Partial Fill, and terminal Filled states across multiple venues, while the parent order state machine aggregates cumulative progress in real time.