SettlInstSource (FIX tag 165)

charFIX 4.4FIX 4.2

SettlInstSource (tag 165) is a char field defined in FIX 4.4 and FIX 4.2. It appears in 7 message types, always optionally. It is an enumerated field with 3 defined values.

At a glance

Tag: 165
Name: SettlInstSource
Datatype: char
Dialects: FIX 4.4 and FIX 4.2
Messages: 7
Valid values: 3

What the specification says

Indicates source of Settlement Instructions

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

A real message using tag 165

Confirmation · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	237
35	MsgType	AK	Confirmation
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
664	ConfirmID	EXAMPLE
666	ConfirmTransType	0	New
773	ConfirmType	1	Status
665	ConfirmStatus	1	Received
60	TransactTime	20240101-12:00:00.000
75	TradeDate	20240101
80	AllocQty	1000000
54	Side	1	Buy
862	NoCapacities1 entry	1	repeating group
528	OrderCapacity	A	Agency
863	OrderCapacityQty	1000000
79	AllocAccount	EXAMPLE
6	AvgPx	1.09215
381	GrossTradeAmt	125000.00
118	NetMoney	125000.00
85	NoDlvyInst2 entries	2	repeating group
165	SettlInstSource	1	Broker’s Instructions
165	SettlInstSource	1	Broker’s Instructions
10	CheckSum	006

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	Dialects
1	Broker’s Instructions	BROKERS_INSTRUCTIONS / BrokerCredit	FIX 4.4, FIX 4.2
2	Institution’s Instructions	INSTITUTIONS_INSTRUCTIONS / Institution	FIX 4.4, FIX 4.2
3	Investor (e.g. CIV use)	INVESTOR	FIX 4.4

Where tag 165 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 4.2	Where in the message
AllocationInstruction	J	Conditional	—	inside AllocGrp › SettlInstructionsData › DlvyInstGrp
AllocationReport	AS	Conditional	—	inside AllocGrp › SettlInstructionsData › DlvyInstGrp
CollateralAssignment	AY	Conditional	—	inside SettlInstructionsData › DlvyInstGrp
CollateralInquiry	BB	Conditional	—	inside SettlInstructionsData › DlvyInstGrp
CollateralReport	BA	Conditional	—	inside SettlInstructionsData › DlvyInstGrp
Confirmation	AK	Conditional	—	inside SettlInstructionsData › DlvyInstGrp
SettlementInstructions	T	Conditional	Required	inside SettlInstGrp › SettlInstructionsData › DlvyInstGrp

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