Boar Team
GitHub

TradeCaptureReport (MsgType AE)

applicationFIX 4.4FIX 5.0 SP2

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

A real TradeCaptureReport

TradeCaptureReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength165
35MsgTypeAETrade Capture Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
571TradeReportIDEXAMPLE
570PreviouslyReportedNnot reported to counterparty
32LastQty1000000
31LastPx1.09210
75TradeDate20240101
60TransactTime20240101-12:00:00.000
552NoSides1 entry1repeating group
54Side1Buy
37OrderIDORD-10042
10CheckSum175
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 5.0 SP2

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 (2)

tag 39, OrderQtyData

Present in FIX 5.0 SP2 only (38)

ApplicationSequenceControl, tag 1003, tag 1040, tag 1041, tag 1042, tag 939, tag 1123, tag 1124, tag 1125, tag 1126, tag 1127, RootParties, tag 1015, tag 716, tag 717, tag 1430, tag 1300, tag 1301, tag 1056, tag 15, tag 120, tag 1071, tag 987, tag 1188, tag 1380, tag 1190, tag 1382, TrdRepIndicatorsGrp, tag 1390, tag 994, tag 1011, tag 779, tag 991, tag 1132, tag 1134, tag 381, tag 1328, tag 1329

Handle TradeCaptureReport 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 === "AE") {  message.name;            // "TradeCaptureReport"  // 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