TradeCaptureReportAck (MsgType AR)

applicationFIX 4.4FIX 5.0 SP2

TradeCaptureReportAck is the FIX message with MsgType AR, 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 39 top-level members once the standard header and trailer are counted.

A real TradeCaptureReportAck

TradeCaptureReportAck · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength82
35MsgTypeARTrade Capture Report Ack
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
571TradeReportIDEXAMPLE
150ExecType0New
10CheckSum253
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 (9)

tag 528, tag 529, tag 582, tag 1, tag 660, tag 581, tag 77, tag 591, TrdAllocGrp

Present in FIX 5.0 SP2 only (57)

tag 1003, tag 1040, tag 1041, tag 1042, tag 1123, tag 1124, tag 1125, tag 1126, tag 1127, RootParties, tag 378, tag 570, tag 423, tag 822, tag 823, tag 716, tag 717, tag 854, tag 32, tag 31, tag 1430, tag 1300, tag 1301, tag 669, tag 1056, tag 1071, tag 15, tag 120, tag 194, tag 195, tag 30, tag 75, tag 715, tag 6, tag 819, tag 442, tag 824, tag 63, UndInstrmtGrp, tag 573, tag 574, tag 797, TrdRepIndicatorsGrp, tag 852, tag 1390, tag 853, tag 1015, PositionAmountData, tag 994, tag 1011, tag 779, tag 991, TrdCapRptAckSideGrp, tag 1135, tag 381, tag 64, tag 1329

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