SettlPartySubID (FIX tag 785)
SettlPartySubID (tag 785) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 7 message types, always optionally.
At a glance
- Tag
- 785
- Name
- SettlPartySubID
- Datatype
- String
- Dialects
- FIX 4.4 and FIX 5.0 SP2
- Messages
- 7
What the specification says
FIX 4.4
PartySubID value within a settlement parties component. Same values as PartySubID (523)
FIX 5.0 SP2
PartySubID value within a settlement parties component.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 785
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 204 | |
| 35 | MsgType | J | Allocation Instruction |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 70 | AllocID | EXAMPLE | |
| 71 | AllocTransType | 0 | New |
| 626 | AllocType | 1 | Calculated (includes MiscFees and NetMoney) |
| 857 | AllocNoOrdersType | 0 | Not specified |
| 54 | Side | 1 | Buy |
| 53 | Quantity | 1000000 | |
| 6 | AvgPx | 1.09215 | |
| 75 | TradeDate | 20240101 | |
| 78 | NoAllocs1 entry | 1 | repeating group |
| 79 | AllocAccount | EXAMPLE | |
| 85 | NoDlvyInst1 entry | 1 | repeating group |
| 165 | SettlInstSource | 1 | Broker’s Instructions |
| 781 | NoSettlPartyIDs1 entry | 1 | repeating group |
| 782 | SettlPartyID | EXAMPLE | |
| 801 | NoSettlPartySubIDs2 entries | 2 | repeating group |
| 785 | SettlPartySubID | EXAMPLE | |
| 785 | SettlPartySubID | EXAMPLE | |
| 10 | CheckSum | 208 |
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.
Where tag 785 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 5.0 SP2 | Where in the message |
|---|---|---|---|---|
| AllocationInstruction | J | Optional | Optional | inside AllocGrp › SettlInstructionsData › DlvyInstGrp › SettlParties › SettlPtysSubGrp |
| AllocationInstructionAlert | BM | — | Optional | inside AllocGrp › SettlInstructionsData › DlvyInstGrp › SettlParties › SettlPtysSubGrp |
| AllocationReport | AS | Optional | Optional | inside AllocGrp › SettlInstructionsData › DlvyInstGrp › SettlParties › SettlPtysSubGrp |
| CollateralAssignment | AY | Optional | Optional | inside SettlInstructionsData › DlvyInstGrp › SettlParties › SettlPtysSubGrp |
| CollateralInquiry | BB | Optional | Optional | inside SettlInstructionsData › DlvyInstGrp › SettlParties › SettlPtysSubGrp |
| CollateralReport | BA | Optional | Optional | inside SettlInstructionsData › DlvyInstGrp › SettlParties › SettlPtysSubGrp |
| Confirmation | AK | Optional | Optional | inside SettlInstructionsData › DlvyInstGrp › SettlParties › SettlPtysSubGrp |
| SettlementInstructions | T | Optional | Optional | inside SettlInstGrp › SettlInstructionsData › DlvyInstGrp › SettlParties › SettlPtysSubGrp |
| SettlementObligationReport | BQ | — | Optional | inside SettlObligationInstructions › SettlDetails › SettlParties › SettlPtysSubGrp |
| TradeCaptureReport | AE | — | Optional | inside TrdCapRptSideGrp › SettlDetails › SettlParties › SettlPtysSubGrp |
| TradeCaptureReportAck | AR | — | Optional | inside TrdCapRptAckSideGrp › SettlDetails › SettlParties › SettlPtysSubGrp |
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 785 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[785];field?.name; // "SettlPartySubID"field?.raw; // the verbatim wire stringfield?.value; // coerced to a stringOther String fields
- 782SettlPartyID
- 790OrdStatusReqID
- 791SettlInstReqID
- 777SettlInstMsgID
- 793SecondaryAllocID
- 795AllocReportRefID
- 772ConfirmRefID
- 771TrdRegTimestampOrigin
- 764LegSecuritySubType
- 763UnderlyingSecuritySubType
- 762SecuritySubType
- 761BenchmarkSecurityIDSource
- 760Nested2PartySubID
- 757Nested2PartyID
- 755AllocReportID
- 817AltMDSourceID
- 818SecondaryTradeReportID
- 820TradeLinkID
- 821OrderInputDevice
- 822UnderlyingTradingSessionID
- 823UnderlyingTradingSessionSubID
- 824TradeLegRefID
- 825ExchangeRule
- 740LegPool
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