Friday, 20 November 2026 · Free. No paywall. No subscription.
Search The MidPoint News

Search articles, videos and sections. Press / to open, Esc to close.

FIX Latest · EP313Field

ClOrdID <11>

Tag
11
Type
String
FIXML name
ClOrdID
Category
SingleGeneralOrderHandling
Pedigree
Added FIX 2.7 · Updated FIX Latest EP282
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

ClOrdID <11> in plain English

Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).

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), QuoteRequest (35=R), Email (35=C), OrderStatusRequest (35=H) and 28 more. In all, 43 messages in FIX Latest can carry it. Full list.

Example message

8=FIXT.1.1|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=208

Illustrative example, not real orders or market data. A NewOrderSingle (35=D) in FIX Latest, shown with BeginString FIXT.1.1. 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 Latest 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 the buy-side (institution, broker, intermediary etc.) (identified by SenderCompID(49) or OnBehalfOfCompID(115) 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(11) field.

Used in

Messages (26)

Components and repeating groups (10)

NameKindPresence
TradeReportOrderDetailComponentOptional
OrderAggregationGrpRepeating groupOptional
InstrmtStrkPxGrpRepeating groupOptional
ListOrdGrpRepeating groupRequired
OrdAllocGrpRepeating groupOptional
OrdListStatGrpRepeating groupOptional
SideCrossOrdCxlGrpRepeating groupRequired
SideCrossOrdModGrpRepeating groupRequired
OrderEntryGrpRepeating groupOptional
OrderEntryAckGrpRepeating groupOptional
All 43 messages that can carry ClOrdID, including through components and groups