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 4.2Field

ExecID <17>

Tag
17
Type
String
Pedigree
Added FIX 2.7
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

This page shows ExecID <17> as defined in FIX 4.2. For the current standard, see tag 17 ExecID in FIX Latest.

ExecID <17> 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.

ExecID is the broker'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 a status report (ExecTransType (20) = 3).

Where it is used

ExecutionReport (35=8), DontKnowTrade (35=Q), ExecAllocGrp (repeating group) . In all, 3 messages in FIX 4.2 can carry it. Full list.

Example message

8=FIX.4.2|9=215|35=8|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|37=OID-5001|11=ORD-1001|17=EXEC-7001|20=0|150=1|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=235

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

Description (from the Orchestra file)

Unique identifier of execution message as assigned by broker (will be 0 (zero) for ExecTransType=3 (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 (2)

MessageMsgTypePresence
ExecutionReport8Required
DontKnowTradeQRequired

Components and repeating groups (1)

NameKindPresence
ExecAllocGrpRepeating groupOptional
All 3 messages that can carry ExecID, including through components and groups