PreviouslyReported (FIX tag 570)

BooleanFIX 4.4FIX 5.0 SP2

PreviouslyReported (tag 570) is a Boolean field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 3 message types and is required in 1 of them. It is an enumerated field with 2 defined values.

At a glance

Tag: 570
Name: PreviouslyReported
Datatype: Boolean (char)
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 3
Valid values: 2

What the specification says

FIX 4.4

Indicates if the trade capture report was previously reported to the counterparty

FIX 5.0 SP2

Indicates if the transaction was previously reported to the counterparty or market.

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

A real message using tag 570

TradeCaptureReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	165
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
552	NoSides1 entry	1	repeating group
54	Side	1	Buy
37	OrderID	ORD-10042
10	CheckSum	175

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
Y	previously reported to counterparty	YES / PERVIOUSLY_REPORTED_TO_COUNTERPARTY
N	not reported to counterparty	NO / NOT_REPORTED_TO_COUNTERPARTY

Where tag 570 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	FIX 4.4	FIX 5.0 SP2	Where in the message
AllocationInstruction	J	Optional	Optional	directly on the message body
AllocationInstructionAlert	BM	—	Optional	directly on the message body
AllocationReport	AS	Optional	Optional	directly on the message body
TradeCaptureReport	AE	Required	Optional	directly on the message body
TradeCaptureReportAck	AR	—	Optional	directly on the message body

Wire format

Y or N. Not 1/0, and not true/false. @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 570 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 previouslyReported = message.fields[570]?.raw;// e.g. "Y" — previously reported to counterparty// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(570)  ?.enumValues?.find((e) => e.value === previouslyReported)  ?.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