TradeReportID (FIX tag 571)

StringFIX 4.4FIX 5.0 SP2

TradeReportID (tag 571) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 9 message types and is required in 2 of them.

At a glance

Tag
571
Name
TradeReportID
Datatype
String
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
9

What the specification says

Unique identifier of trade capture report

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

A real message using tag 571

TradeCaptureReportRequest · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength94
35MsgTypeADTrade Capture Report Request
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
568TradeRequestIDEXAMPLE
569TradeRequestType0All trades
571TradeReportIDEXAMPLE
10CheckSum237
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 571 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.

MessageMsgTypeFIX 4.4FIX 5.0 SP2Where in the message
CollateralAssignmentAYConditionalOptionalinside the TrdCollGrp component
CollateralInquiryBBConditionalOptionalinside the TrdCollGrp component
CollateralInquiryAckBGConditionalOptionalinside the TrdCollGrp component
CollateralReportBAConditionalOptionalinside the TrdCollGrp component
CollateralRequestAXConditionalOptionalinside the TrdCollGrp component
CollateralResponseAZConditionalOptionalinside the TrdCollGrp component
TradeCaptureReportAERequiredOptionaldirectly on the message body
TradeCaptureReportAckARRequiredOptionaldirectly on the message body
TradeCaptureReportRequestADOptionalOptionaldirectly 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 571 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[571];field?.name;   // "TradeReportID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other String fields

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