Friday, 20 November 2026 · Free. No paywall. No subscription.
Search The MidPoint News

Search articles, videos and sections. Press / to open, Esc to close.

FIX 4.4Field

PreviouslyReported <570>

Tag
570
Type
Boolean (base char) · code set PreviouslyReportedCodeSet
FIXML name
PrevlyRpted
Pedigree
Added FIX 4.3
Versions
FIX Latest ✓ · FIX 4.4 ✓ · Not in FIX 4.2

This page shows PreviouslyReported <570> as defined in FIX 4.4. For the current standard, see tag 570 PreviouslyReported in FIX Latest.

PreviouslyReported <570> in plain English

Summary by The MidPoint News, based on the FIX Latest description in the Orchestra file. The FIX 4.4 description is quoted in full below and may differ.

PreviouslyReported says whether the transaction was already reported to the counterparty or market.

Common values

ValueNameMeaning (from the Orchestra file)
570=YPerviouslyReportedToCounterpartypreviously reported to counterpartypreviously reported to counterparty
570=NNotReportedToCounterpartynot reported to counterpartynot reported to counterparty

A selection. The full list of values is in the table further down.

Where it is used

TradeCaptureReport (35=AE), AllocationInstruction (35=J), AllocationReport (35=AS) . In all, 3 messages in FIX 4.4 can carry it. Full list.

Example message

8=FIX.4.4|9=182|35=AE|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|571=TR-1000|487=0|856=0|828=0|570=N|55=AAPL|32=500|31=190.40|75=20261116|60=20261116-08:30:00.000|552=1|54=1|37=OID-5001|10=009

Illustrative example, not real orders or market data. A TradeCaptureReport (35=AE) in FIX 4.4, shown with BeginString FIX.4.4. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.4 dictionary, but it is not a complete specification of the message.

Description (from the Orchestra file)

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

Values (2)

ValueNameDescriptionPedigreeIn LatestIn 4.2
Y PerviouslyReportedToCounterpartypreviously reported to counterparty previously reported to counterparty Added FIX 4.3 ✓n/a
N NotReportedToCounterpartynot reported to counterparty not reported to counterparty Added FIX 4.3 ✓n/a

Used in

Messages (3)

MessageMsgTypePresence
AllocationInstructionJOptional
TradeCaptureReportAERequired
AllocationReportASOptional