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

ExecID <17>

Tag
17
Type
String
FIXML name
ExecID
Pedigree
Added FIX 2.7 · Updated FIX 5.0SP1 EP95
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

ExecID <17> in plain English

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

ExecID is the sell side's unique identifier for an execution message. It must be unique within a trading day, or the life of a multi-day order, and is 0 on an order-status report (ExecType (150) = I).

Where it is used

ExecutionReport (35=8), TradeCaptureReport (35=AE), DontKnowTrade (35=Q), TradeCaptureReportRequest (35=AD), TradeCaptureReportAck (35=AR), ExecutionAck (35=BN), ExecutionAggregationGrp (repeating group), ExecAllocGrp (repeating group) and 1 more. In all, 17 messages in FIX Latest can carry it. Full list.

Example message

8=FIXT.1.1|9=210|35=8|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|37=OID-5001|11=ORD-1001|17=EXEC-7001|150=F|39=1|55=AAPL|54=1|38=1000|40=2|44=190.50|32=400|31=190.48|151=600|14=400|6=190.48|60=20261116-08:30:00.000|10=123

Illustrative example, not real orders or market data. An ExecutionReport (35=8) 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: ExecType <150>

Description (from the Orchestra file)

Unique identifier of execution message as assigned by sell-side (broker, exchange, ECN) (will be 0 (zero) for ExecType (150)=I (Order Status)). Uniqueness must be guaranteed within a single trading day or the life of a multi-day order. Firms which accept multi-day orders should consider embedding a date within the ExecID field to assure uniqueness across days. (Prior to FIX 4.1 this field was of type int).

Used in

Messages (6)

MessageMsgTypePresence
ExecutionReport8Required
DontKnowTradeQRequired
TradeCaptureReportRequestADOptional
TradeCaptureReportAEOptional
TradeCaptureReportAckAROptional
ExecutionAckBNRequired

Components and repeating groups (3)

NameKindPresence
ExecutionAggregationGrpRepeating groupOptional
ExecAllocGrpRepeating groupOptional
ExecCollGrpRepeating groupOptional
All 17 messages that can carry ExecID, including through components and groups