SettlementInstructions (MsgType T)
SettlementInstructions is the FIX message with MsgType T, defined in FIX 4.4 and FIX 4.2. It is an application-level message: it carries a business event rather than managing the session. Its body has 12 top-level members once the standard header and trailer are counted.
T is SettlementInstructions, but t is a different message entirely — CrossOrderCancelReplaceRequest. Twenty-three FIX message types differ from another only by letter case.A real SettlementInstructions
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 106 | |
| 35 | MsgType | T | Settlement Instructions |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 777 | SettlInstMsgID | EXAMPLE | |
| 160 | SettlInstMode | 1 | Standing Instructions Provided |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 10 | CheckSum | 165 |
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.
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.
Message body — FIX 4.4
Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.
- —Standard Message HeadercomponentRequired
- 777SettlInstMsgIDRequired
- 791SettlInstReqIDOptional
- 160SettlInstModeRequired
- 792SettlInstReqRejCodeConditional
- 58TextOptional
- 354EncodedTextLenConditional
- 355EncodedTextConditional
- 11ClOrdIDConditional
- 60TransactTimeRequired
- —SettlInstGrpcomponentOptional
- —Standard Message TrailercomponentRequired
Message body — FIX 4.2
Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.
- —Standard Message HeadercomponentRequired
- 162SettlInstIDRequired
- 163SettlInstTransTypeRequired
- 214SettlInstRefIDRequired
- 160SettlInstModeRequired
- 165SettlInstSourceRequired
- 79AllocAccountRequired
- 166SettlLocationOptional
- 75TradeDateOptional
- 70AllocIDOptional
- 30LastMktOptional
- 336TradingSessionIDOptional
- 54SideOptional
- 167SecurityTypeOptional
- 168EffectiveTimeOptional
- 60TransactTimeRequired
- 109ClientIDOptional
- 76ExecBrokerOptional
- 169StandInstDbTypeOptional
- 170StandInstDbNameOptional
- 171StandInstDbIDOptional
- 172SettlDeliveryTypeOptional
- 173SettlDepositoryCodeOptional
- 174SettlBrkrCodeOptional
- 175SettlInstCodeOptional
- 176SecuritySettlAgentNameOptional
- 177SecuritySettlAgentCodeOptional
- 178SecuritySettlAgentAcctNumOptional
- 179SecuritySettlAgentAcctNameOptional
- 180SecuritySettlAgentContactNameOptional
- 181SecuritySettlAgentContactPhoneOptional
- 182CashSettlAgentNameOptional
- 183CashSettlAgentCodeOptional
- 184CashSettlAgentAcctNumOptional
- 185CashSettlAgentAcctNameOptional
- 186CashSettlAgentContactNameOptional
- 187CashSettlAgentContactPhoneOptional
- —Standard Message TrailercomponentRequired
What changed between the dialects
Present in FIX 4.4 only (8)
tag 777, tag 791, tag 792, tag 58, tag 354, tag 355, tag 11, SettlInstGrp
Present in FIX 4.2 only (34)
tag 162, tag 163, tag 214, tag 165, tag 79, tag 166, tag 75, tag 70, tag 30, tag 336, tag 54, tag 167, tag 168, tag 109, tag 76, tag 169, tag 170, tag 171, tag 172, tag 173, tag 174, tag 175, tag 176, tag 177, tag 178, tag 179, tag 180, tag 181, tag 182, tag 183, tag 184, tag 185, tag 186, tag 187
Handle SettlementInstructions in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);if (message.msgType === "T") { message.name; // "SettlementInstructions" // fields are keyed by tag; repeating groups live on message.groups}// Problems come back as data, never as exceptions:issues; // FixIssue[]fix.validate(message); // dictionary-level problemsDecode 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