SettlObligSource (FIX tag 1164)

charFIX 5.0 SP2

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

At a glance

Tag: 1164
Name: SettlObligSource
Datatype: char
Dialects: FIX 5.0 SP2
Messages: 3
Valid values: 3

What the specification says

Used to identify whether these delivery instructions are for the buyside or the sellside.

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

A real message using tag 1164

SettlementObligationReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	118
35	MsgType	BQ	SettlementObligationReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
1160	SettlObligMsgID	EXAMPLE
1159	SettlObligMode	1	Preliminary
1165	NoSettlOblig1 entry	1	repeating group
430	NetGrossInd	1	Net
1158	NoSettlDetails2 entries	2	repeating group
1164	SettlObligSource	1	Instructions of Broker
1164	SettlObligSource	1	Instructions of Broker
10	CheckSum	216

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
1	Instructions of Broker	INSTRUCTIONS_OF_BROKER
2	Instructions for Institution	INSTRUCTIONS_FOR_INSTITUTION
3	Investor	INVESTOR

Where tag 1164 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
SettlementObligationReport	BQ	Optional	inside SettlObligationInstructions › SettlDetails
TradeCaptureReport	AE	Optional	inside TrdCapRptSideGrp › SettlDetails
TradeCaptureReportAck	AR	Optional	inside TrdCapRptAckSideGrp › SettlDetails

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 1164 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 settlObligSource = message.fields[1164]?.raw;// e.g. "1" — Instructions of Broker// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1164)  ?.enumValues?.find((e) => e.value === settlObligSource)  ?.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