SettlSessID (FIX tag 716)

StringFIX 4.4FIX 5.0 SP2

SettlSessID (tag 716) is a String field defined in FIX 4.4 and FIX 5.0 SP2. 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 and FIX 5.0 SP2
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
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength147
35MsgTypeANRequest For Positions
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
710PosReqIDEXAMPLE
724PosReqType0Positions
1AccountACCT-11223
581AccountType1Account is carried on customer Side of Books
715ClearingBusinessDate20240101
716SettlSessIDITDIntraday
60TransactTime20240101-12:00:00.000
10CheckSum188
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.

ValueMeaningSymbolic nameDialects
ITDIntradayINTRADAYFIX 4.4, FIX 5.0 SP2
RTHRegular Trading HoursREGULAR_TRADING_HOURSFIX 4.4, FIX 5.0 SP2
ETHElectronic Trading HoursELECTRONIC_TRADING_HOURSFIX 4.4, FIX 5.0 SP2
EODEnd Of DayEND_OF_DAYFIX 5.0 SP2

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.

MessageMsgTypeFIX 4.4FIX 5.0 SP2Where in the message
AdjustedPositionReportBLOptionaldirectly on the message body
AssignmentReportAWRequiredOptionaldirectly on the message body
CollateralAssignmentAYOptionalOptionaldirectly on the message body
CollateralInquiryBBOptionalOptionaldirectly on the message body
CollateralInquiryAckBGOptionalOptionaldirectly on the message body
CollateralReportBAOptionalOptionaldirectly on the message body
CollateralRequestAXOptionalOptionaldirectly on the message body
PositionMaintenanceReportAMOptionalOptionaldirectly on the message body
PositionMaintenanceRequestALOptionalOptionaldirectly on the message body
PositionReportAPOptionalOptionaldirectly on the message body
RequestForPositionsANOptionalOptionaldirectly on the message body
RequestForPositionsAckAOOptionaldirectly on the message body
TradeCaptureReportAEOptionaldirectly on the message body
TradeCaptureReportAckAROptionaldirectly 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;

Other String fields

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