TrdRepIndicator (FIX tag 1389)

BooleanFIX 5.0 SP2

TrdRepIndicator (tag 1389) is a Boolean field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally.

At a glance

Tag: 1389
Name: TrdRepIndicator
Datatype: Boolean (char)
Dialects: FIX 5.0 SP2
Messages: 2

What the specification says

Specifies whether the trade should be reported (or not) to parties of the provided TrdRepPartyRole(1388). Used to override standard reporting behavior by the receiver of the trade report and thereby complements the PublTrdIndicator( tag1390).

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

A real message using tag 1389

TradeCaptureReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	132
35	MsgType	AE	TradeCaptureReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
32	LastQty	1000000
31	LastPx	1.09210
552	NoSides1 entry	1	repeating group
54	Side	1	Buy
1387	NoTrdRepIndicators2 entries	2	repeating group
1388	TrdRepPartyRole	1
1389	TrdRepIndicator	N
1388	TrdRepPartyRole	1
1389	TrdRepIndicator	N
10	CheckSum	222

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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 1389 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
TradeCaptureReport	AE	Optional	inside the TrdRepIndicatorsGrp component
TradeCaptureReportAck	AR	Optional	inside the TrdRepIndicatorsGrp component

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 1389 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1389];field?.name;   // "TrdRepIndicator"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a boolean

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-fix50sp2

Try the decoder Source on GitHub