Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
ClOrdID <11>
- Tag
11- Type
- String
- Pedigree
- Added FIX 2.7
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓
This page shows ClOrdID <11> as defined in FIX 4.2. For the current standard, see tag 11 ClOrdID in FIX Latest.
ClOrdID <11> in plain English
Summary by The MidPoint News, based on the FIX Latest description in the Orchestra file. The FIX 4.2 description is quoted in full below and may differ.
ClOrdID is the buy side's unique identifier for an order, assigned by the firm in SenderCompID (49) or OnBehalfOfCompID (115). It must be unique within a trading day. A cancel or replace request carries a new ClOrdID, with the previous one in OrigClOrdID (41).
Where it is used
NewOrderSingle (35=D), ExecutionReport (35=8), OrderCancelRequest (35=F), OrderCancelReplaceRequest (35=G), OrderCancelReject (35=9), Email (35=C), OrderStatusRequest (35=H), InstrmtStrkPxGrp (repeating group) and 3 more.
In all, 11 messages in FIX 4.2 can carry it. Full list.
Example message
8=FIX.4.2|9=153|35=D|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|11=ORD-1001|1=ACCT-01|21=1|55=AAPL|54=1|60=20261116-08:30:00.000|38=1000|40=2|44=190.50|59=0|10=128 Illustrative example, not real orders or market data. A NewOrderSingle (35=D) in FIX 4.2, shown with BeginString FIX.4.2. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.2 dictionary, but it is not a complete specification of the message.
Related tags: SenderCompID <49> · OnBehalfOfCompID <115> · OrigClOrdID <41>
Description (from the Orchestra file)
Unique identifier for Order as assigned by institution (identified by SenderCompID or OnBehalfOfCompID as appropriate). Uniqueness must be guaranteed within a single trading day. Firms, particularly those which electronically submit multi-day orders, trade globally or throughout market close periods,should ensure uniqueness across days, for example by embedding a date within the ClOrdID field.
Used in
Messages (7)
| Message | MsgType | Presence |
|---|---|---|
| ExecutionReport | 8 | Optional |
| OrderCancelReject | 9 | Required |
| C | Optional | |
| NewOrderSingle | D | Required |
| OrderCancelRequest | F | Required |
| OrderCancelReplaceRequest | G | Required |
| OrderStatusRequest | H | Required |
Components and repeating groups (4)
| Name | Kind | Presence |
|---|---|---|
| InstrmtStrkPxGrp | Repeating group | Optional |
| ListOrdGrp | Repeating group | Required |
| OrdAllocGrp | Repeating group | Optional |
| OrdListStatGrp | Repeating group | Required |