ExecID (FIX tag 17)

StringFIX 4.4FIX 4.2FIX 5.0 SP2

ExecID (tag 17) is a String field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 13 message types and is required in 2 of them.

At a glance

Tag: 17
Name: ExecID
Datatype: String
Dialects: FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages: 13

What the specification says

FIX 4.4

Unique identifier of execution message as assigned by sell-side (broker, exchange, ECN) (will be 0 (zero) for ExecType (50) =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)

FIX 4.2

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)

FIX 5.0 SP2

Unique identifier of execution message as assigned by sell-side (broker, exchange, ECN) (will be 0 (zero) for ExecType (150)=I (Order Status)).

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 17

TradeCaptureReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	179
35	MsgType	AE	Trade Capture Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
571	TradeReportID	EXAMPLE
17	ExecID	EXEC-88117
570	PreviouslyReported	N	not reported to counterparty
32	LastQty	1000000
31	LastPx	1.09210
75	TradeDate	20240101
60	TransactTime	20240101-12:00:00.000
552	NoSides1 entry	1	repeating group
54	Side	1	Buy
37	OrderID	ORD-10042
10	CheckSum	181

Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 17 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

Message	MsgType	FIX 4.4	FIX 4.2	FIX 5.0 SP2	Where in the message
AllocationInstruction	J	Conditional	Optional	Optional	inside the ExecAllocGrp component
AllocationInstructionAlert	BM	—	—	Optional	inside the ExecAllocGrp component
AllocationReport	AS	Conditional	—	Optional	inside the ExecAllocGrp component
CollateralAssignment	AY	Conditional	—	Optional	inside the ExecCollGrp component
CollateralInquiry	BB	Conditional	—	Optional	inside the ExecCollGrp component
CollateralInquiryAck	BG	Conditional	—	Optional	inside the ExecCollGrp component
CollateralReport	BA	Conditional	—	Optional	inside the ExecCollGrp component
CollateralRequest	AX	Conditional	—	Optional	inside the ExecCollGrp component
CollateralResponse	AZ	Conditional	—	Optional	inside the ExecCollGrp component
DontKnowTrade	Q	Required	Required	Required	directly on the message body
ExecutionAcknowledgement	BN	—	—	Required	directly on the message body
ExecutionReport	8	Required	Required	Required	directly on the message body
TradeCaptureReport	AE	Optional	—	Optional	directly on the message body
TradeCaptureReportAck	AR	Optional	—	Optional	directly on the message body
TradeCaptureReportRequest	AD	Optional	—	Optional	directly on the message body

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 17 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[17];field?.name;   // "ExecID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix44

Try the decoder Source on GitHub