Boar Team
GitHub

ExecutionReport (MsgType 8)

applicationFIX 4.4FIX 4.2

ExecutionReport is the FIX message with MsgType 8, defined in FIX 4.4 and FIX 4.2. It is an application-level message: it carries a business event rather than managing the session. Its body has 140 top-level members once the standard header and trailer are counted.

A real ExecutionReport

ExecutionReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength133
35MsgType8Execution Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
17ExecIDEXEC-88117
150ExecType0New
39OrdStatus0New
54Side1Buy
151LeavesQty0
14CumQty1000000
6AvgPx1.09215
10CheckSum025
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.

Message body — FIX 4.4

Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.

Message body — FIX 4.2

Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.

What changed between the dialects

Present in FIX 4.4 only (79)

tag 526, tag 527, tag 583, tag 693, tag 790, tag 584, tag 911, tag 912, Parties, tag 229, ContraGrp, tag 548, tag 551, tag 549, tag 636, tag 660, tag 581, tag 589, tag 590, tag 591, tag 544, tag 635, Instrument, FinancingDetails, UndInstrmtGrp, Stipulations, tag 854, OrderQtyData, tag 423, PegInstructions, DiscretionInstructions, tag 839, tag 845, tag 847, tag 848, tag 849, tag 850, tag 528, tag 529, tag 582, tag 652, tag 651, tag 669, tag 625, tag 943, CommissionData, SpreadOrBenchmarkCurveData, YieldData, tag 157, tag 230, tag 158, tag 159, tag 738, tag 920, tag 921, tag 922, tag 258, tag 259, tag 260, tag 238, tag 237, tag 118, tag 775, tag 641, tag 480, tag 481, tag 513, tag 494, tag 483, tag 515, tag 484, tag 485, tag 638, tag 639, tag 851, ContAmtGrp, InstrmtLegExecGrp, tag 797, MiscFeesGrp

Present in FIX 4.2 only (33)

tag 109, tag 76, group 382, tag 20, tag 55, tag 65, tag 48, tag 22, tag 167, tag 200, tag 205, tag 201, tag 202, tag 206, tag 231, tag 223, tag 207, tag 106, tag 348, tag 349, tag 107, tag 350, tag 351, tag 38, tag 152, tag 211, tag 388, tag 389, tag 47, tag 12, tag 13, tag 439, tag 440

Handle ExecutionReport 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);​if (message.msgType === "8") {  message.name;            // "ExecutionReport"  // fields are keyed by tag; repeating groups live on message.groups}​// Problems come back as data, never as exceptions:issues;                    // FixIssue[]fix.validate(message);     // dictionary-level problems

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 decoderSource on GitHub