Trading and Order Management Systems
What this domain tests
The exam tests the order lifecycle, the division of labour between OMS and EMS, FIX messaging, pre-trade risk controls, execution benchmarks and the record-keeping and clock-synchronisation rules that surround algorithmic trading.
Core rules and concepts
- Lifecycle: origination → pre-trade compliance and risk → routing → execution → allocation → confirmation → booking. Each step should leave an audit trail.
- OMS vs EMS: the OMS owns orders, compliance, allocation and booking; the EMS owns market data, broker connectivity, algorithms and smart order routing. Many vendors sell a combined OEMS.
- FIX: tag 35 is MsgType (D = NewOrderSingle, 8 = ExecutionReport), 11 ClOrdID, 55 Symbol, 54 Side, 38 OrderQty, 44 Price, 40 OrdType, 59 TimeInForce, 150 ExecType, 39 OrdStatus, 31 LastPx, 32 LastQty.
- Pre-trade controls (MiFID II RTS 6): price collars, maximum order value and volume, maximum message rate, kill functionality, annual self-assessment and controlled deployment of algorithms.
- Record keeping and clocks (RTS 24, RTS 25): order records must be retained; business clocks must be synchronised to specified tolerances (100 microseconds for high-frequency algorithmic trading, 1 millisecond for other automated trading, 1 second for voice).
- Best execution: judged on price, cost, speed, likelihood of execution and settlement, not price alone.
Worked example
Buy 10,000 shares with arrival price 100.0p. Fills: 4,000 at 100.2p, 4,000 at 100.5p, 2,000 at 100.9p. Total consideration = 400,800 + 402,000 + 201,800 = 1,004,600p, so average price = 100.46p. Reasoning: slippage versus arrival price is 0.46p, or 4.6 basis points (0.46/100.0 × 10,000). If market VWAP over the period was 100.30p, the order underperformed VWAP by 0.16p (1.6bp). Whether that is acceptable depends on the benchmark chosen in advance, order size and urgency - implementation shortfall would also capture the opportunity cost of any unfilled quantity.
Traps that cost marks
Equating best execution with best price; picking the benchmark after the trade; ignoring unfilled quantity and opportunity cost; misusing FIX tags in message-flow questions; allocating block trades other than pro rata or by a documented pre-trade policy; forgetting that RTS 6 controls must be tested and evidenced, not merely configured.