MatchStatus (FIX tag 573)

charFIX 4.4

MatchStatus (tag 573) is a char field defined in FIX 4.4. 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
Messages: 8
Valid values: 3

What the specification says

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

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	171
35	MsgType	AE	Trade Capture Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
571	TradeReportID	EXAMPLE
570	PreviouslyReported	N	not reported to counterparty
32	LastQty	1000000
31	LastPx	1.09210
75	TradeDate	20240101
60	TransactTime	20240101-12:00:00.000
573	MatchStatus	0	compared, matched or affirmed
552	NoSides1 entry	1	repeating group
54	Side	1	Buy
37	OrderID	ORD-10042
10	CheckSum	185

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.

Value	Meaning	Symbolic name
0	compared, matched or affirmed	COMPARED_MATCHED_OR_AFFIRMED
1	uncompared, unmatched, or unaffirmed	UNCOMPARED_UNMATCHED_OR_UNAFFIRMED
2	advisory or alert	ADVISORY_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.

Message	MsgType	Requiredness	Where in the message
AllocationInstruction	J	Optional	inside the AllocGrp component
AllocationInstructionAck	P	Conditional	directly on the message body
AllocationReport	AS	Optional	inside the AllocGrp component
AllocationReportAck	AT	Optional	directly on the message body
ConfirmationAck	AU	Optional	directly on the message body
RequestForPositions	AN	Optional	directly on the message body
TradeCaptureReport	AE	Optional	directly on the message body
TradeCaptureReportRequest	AD	Optional	directly 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;

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 decoder Source on GitHub