SettlSessID (FIX tag 716)

StringFIX 4.4

SettlSessID (tag 716) is a String field defined in FIX 4.4. It appears in 10 message types and is required in 1 of them. It is an enumerated field with 3 defined values.

At a glance

Tag: 716
Name: SettlSessID
Datatype: String
Dialects: FIX 4.4
Messages: 10
Valid values: 3

What the specification says

Identifies a specific settlement session

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

A real message using tag 716

RequestForPositions · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	147
35	MsgType	AN	Request For Positions
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
710	PosReqID	EXAMPLE
724	PosReqType	0	Positions
1	Account	ACCT-11223
581	AccountType	1	Account is carried on customer Side of Books
715	ClearingBusinessDate	20240101
716	SettlSessID	ITD	Intraday
60	TransactTime	20240101-12:00:00.000
10	CheckSum	188

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
ITD	Intraday	INTRADAY
RTH	Regular Trading Hours	REGULAR_TRADING_HOURS
ETH	Electronic Trading Hours	ELECTRONIC_TRADING_HOURS

Where tag 716 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
AssignmentReport	AW	Required	directly on the message body
CollateralAssignment	AY	Optional	directly on the message body
CollateralInquiry	BB	Optional	directly on the message body
CollateralInquiryAck	BG	Optional	directly on the message body
CollateralReport	BA	Optional	directly on the message body
CollateralRequest	AX	Optional	directly on the message body
PositionMaintenanceReport	AM	Optional	directly on the message body
PositionMaintenanceRequest	AL	Optional	directly on the message body
PositionReport	AP	Optional	directly on the message body
RequestForPositions	AN	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 716 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 settlSessID = message.fields[716]?.raw;// e.g. "ITD" — Intraday// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(716)  ?.enumValues?.find((e) => e.value === settlSessID)  ?.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