SettlInstMode (FIX tag 160)

charFIX 4.4FIX 4.2

SettlInstMode (tag 160) is a char field defined in FIX 4.4 and FIX 4.2. It appears in 2 message types and is required in 1 of them. It is an enumerated field with 3 defined values.

At a glance

Tag: 160
Name: SettlInstMode
Datatype: char
Dialects: FIX 4.4 and FIX 4.2
Messages: 2
Valid values: 3

What the specification says

FIX 4.4

Indicates mode used for Settlement Instructions message. *** SOME VALUES HAVE BEEN REPLACED - See "Replaced Features and Supported Approach" ***

FIX 4.2

Indicates mode used for Settlement Instructions

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

A real message using tag 160

NewOrderList · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	148
35	MsgType	E	Order – List
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
66	ListID	EXAMPLE
394	BidType	1	"Non Disclosed" Style (e.g. US/European)
68	TotNoOrders	1
73	NoOrders2 entries	2	repeating group
11	ClOrdID	ORD-10042
67	ListSeqNo	1
160	SettlInstMode	1	Standing Instructions Provided
54	Side	1	Buy
11	ClOrdID	ORD-10042
67	ListSeqNo	1
160	SettlInstMode	1	Standing Instructions Provided
54	Side	1	Buy
10	CheckSum	057

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	Standing Instructions Provided	STANDING_INSTRUCTIONS_PROVIDED / StandingInstructionsProvided	FIX 4.4, FIX 4.2
4	Specific Order for a single account (for CIV)	SPECIFIC_ORDER_FOR_A_SINGLE_ACCOUNT	FIX 4.4
5	Request reject	REQUEST_REJECT	FIX 4.4
0	Default	Default	FIX 4.2
2	Specific Allocation Account Overriding	SpecificAllocationAccountOverriding	FIX 4.2
3	Specific Allocation Account Standing	SpecificAllocationAccountStanding	FIX 4.2

Where tag 160 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
Allocation	J	—	Optional	directly on the message body
NewOrderList	E	Optional	Optional	inside the ListOrdGrp component
SettlementInstructions	T	Required	Required	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 160 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 settlInstMode = message.fields[160]?.raw;// e.g. "1" — Standing Instructions Provided// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(160)  ?.enumValues?.find((e) => e.value === settlInstMode)  ?.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