SettlLocation (FIX tag 166)

StringFIX 4.2

SettlLocation (tag 166) is a String field defined in FIX 4.2. It appears in 1 message type, always optionally. It is an enumerated field with 7 defined values.

At a glance

Tag: 166
Name: SettlLocation
Datatype: String
Dialects: FIX 4.2
Messages: 1
Valid values: 7

What the specification says

Identifies Settlement Depository or Country Code (ISITC spec) using ISO 3166 (2 character) representing the country of settlement.

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

A real message using tag 166

SettlementInstructions · FIX 4.2

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.2
9	BodyLength	149
35	MsgType	T	Settlement Instructions
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
162	SettlInstID	EXAMPLE
163	SettlInstTransType	C	Cancel
214	SettlInstRefID	EXAMPLE
160	SettlInstMode	0	Default
165	SettlInstSource	1	Brokers Instructions
79	AllocAccount	EXAMPLE
166	SettlLocation	CED	CEDEL
60	TransactTime	20240101-12:00:00.000
10	CheckSum	005

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.2 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
CED	CEDEL	CEDEL
DTC	Depository Trust Company	DepositoryTrustCompany
EUR	Euroclear	EuroClear
FED	Federal Book Entry	FederalBookEntry
ISO Country Code	Local Market Settle Location	LocalMarketSettleLocation
PNY	Physical	Physical
PTC	Participant Trust Company	ParticipantTrustCompany

Where tag 166 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
SettlementInstructions	T	Optional	directly on the message body

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 166 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix42";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const settlLocation = message.fields[166]?.raw;// e.g. "CED" — CEDEL// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(166)  ?.enumValues?.find((e) => e.value === settlLocation)  ?.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-fix42

Try the decoder Source on GitHub