MatchStatus (FIX tag 573)

charFIX 4.4FIX 5.0 SP2

MatchStatus (tag 573) is a char field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 8 message types, always optionally. It is an enumerated field with 3 defined values.

At a glance

Tag
573
Name
MatchStatus
Datatype
char
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
8
Valid values
3

What the specification says

FIX 4.4

The status of this trade with respect to matching or comparison

FIX 5.0 SP2

The status of this trade with respect to matching or comparison.

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

A real message using tag 573

TradeCaptureReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength171
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
573MatchStatus0compared, matched or affirmed
552NoSides1 entry1repeating group
54Side1Buy
37OrderIDORD-10042
10CheckSum185
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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

ValueMeaningSymbolic name
0compared, matched or affirmedCOMPARED_MATCHED_OR_AFFIRMED
1uncompared, unmatched, or unaffirmedUNCOMPARED_UNMATCHED_OR_UNAFFIRMED
2advisory or alertADVISORY_OR_ALERT

Where tag 573 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
AllocationInstructionJOptionalOptionalinside the AllocGrp component
AllocationInstructionAckPConditionalOptionaldirectly on the message body
AllocationInstructionAlertBMOptionalinside the AllocGrp component
AllocationReportASOptionalOptionalinside the AllocGrp component
AllocationReportAckATOptionalOptionaldirectly on the message body
ConfirmationAckAUOptionalOptionaldirectly on the message body
PositionReportAPOptionaldirectly on the message body
RequestForPositionsANOptionalOptionaldirectly on the message body
RequestForPositionsAckAOOptionaldirectly on the message body
TradeCaptureReportAEOptionalOptionaldirectly on the message body
TradeCaptureReportAckAROptionaldirectly on the message body
TradeCaptureReportRequestADOptionalOptionaldirectly on the message body

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 573 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 matchStatus = message.fields[573]?.raw;// e.g. "0" — compared, matched or affirmed// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(573)  ?.enumValues?.find((e) => e.value === matchStatus)  ?.description;

Other char 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