TradeHandlingInstr (FIX tag 1123)

charFIX 5.0 SP2

TradeHandlingInstr (tag 1123) is a char field defined in FIX 5.0 SP2. It appears in 3 message types, always optionally. It is an enumerated field with 6 defined values.

At a glance

Tag: 1123
Name: TradeHandlingInstr
Datatype: char
Dialects: FIX 5.0 SP2
Messages: 3
Valid values: 6

What the specification says

Specified how the TradeCaptureReport(35=AE) should be handled by the respondent.

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

A real message using tag 1123

TradeCaptureReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	104
35	MsgType	AE	TradeCaptureReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
1123	TradeHandlingInstr	0	Trade confirmation
32	LastQty	1000000
31	LastPx	1.09210
552	NoSides1 entry	1	repeating group
54	Side	1	Buy
10	CheckSum	135

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.

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	Trade confirmation	TRADE_CONFIRMATION
1	Two-party report	TWO_PARTY_REPORT
2	One-party report for matching	ONE_PARTY_REPORT_FOR_MATCHING
3	One-party report for pass through	ONE_PARTY_REPORT_FOR_PASS_THROUGH
4	Automated floor order routing	AUTOMATED_FLOOR_ORDER_ROUTING
5	Two-party report for claim	TWO_PARTY_REPORT_FOR_CLAIM

Where tag 1123 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	directly on the message body
TradeCaptureReportAck	AR	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 1123 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 tradeHandlingInstr = message.fields[1123]?.raw;// e.g. "0" — Trade confirmation// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1123)  ?.enumValues?.find((e) => e.value === tradeHandlingInstr)  ?.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-fix50sp2

Try the decoder Source on GitHub