NestedPartySubID (FIX tag 545)

StringFIX 4.4FIX 5.0 SP2

NestedPartySubID (tag 545) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 22 message types, always optionally.

At a glance

Tag
545
Name
NestedPartySubID
Datatype
String
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
22

What the specification says

FIX 4.4

PartySubID value within a nested repeating group. Same values as PartySubID (523)

FIX 5.0 SP2

PartySubID value within a nested repeating group.

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

A real message using tag 545

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength175
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
78NoAllocs1 entry1repeating group
79AllocAccountEXAMPLE
539NoNestedPartyIDs1 entry1repeating group
524NestedPartyIDEXAMPLE
804NoNestedPartySubIDs2 entries2repeating group
545NestedPartySubIDEXAMPLE
545NestedPartySubIDEXAMPLE
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum099
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.

Where tag 545 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
AdjustedPositionReportBLOptionalinside PositionQty › NestedParties › NstdPtysSubGrp
AllocationInstructionJOptionalOptionalinside AllocGrp › NestedParties › NstdPtysSubGrp
AllocationInstructionAckPOptionalinside AllocAckGrp › NestedParties › NstdPtysSubGrp
AllocationInstructionAlertBMOptionalinside AllocGrp › NestedParties › NstdPtysSubGrp
AllocationReportASOptionalOptionalinside AllocGrp › NestedParties › NstdPtysSubGrp
AllocationReportAckATOptionalinside AllocAckGrp › NestedParties › NstdPtysSubGrp
ApplicationMessageRequestBWOptionalinside ApplIDRequestGrp › NestedParties › NstdPtysSubGrp
ApplicationMessageRequestAckBXOptionalinside ApplIDRequestAckGrp › NestedParties › NstdPtysSubGrp
AssignmentReportAWOptionalOptionalinside PositionQty › NestedParties › NstdPtysSubGrp
CrossOrderCancelReplaceRequesttOptionalOptionalinside SideCrossOrdModGrp › PreAllocGrp › NestedParties › NstdPtysSubGrp
ExecutionReport8OptionalOptionalinside InstrmtLegExecGrp › NestedParties › NstdPtysSubGrp
MultilegOrderCancelReplaceACOptionalOptionalinside LegOrdGrp › NestedParties › NstdPtysSubGrp
NewOrderCrosssOptionalOptionalinside SideCrossOrdModGrp › PreAllocGrp › NestedParties › NstdPtysSubGrp
NewOrderListEOptionalOptionalinside ListOrdGrp › PreAllocGrp › NestedParties › NstdPtysSubGrp
NewOrderMultilegABOptionalOptionalinside LegOrdGrp › NestedParties › NstdPtysSubGrp
NewOrderSingleDOptionalOptionalinside PreAllocGrp › NestedParties › NstdPtysSubGrp
OrderCancelReplaceRequestGOptionalOptionalinside PreAllocGrp › NestedParties › NstdPtysSubGrp
PositionMaintenanceReportAMOptionalOptionalinside PositionQty › NestedParties › NstdPtysSubGrp
PositionMaintenanceRequestALOptionalOptionalinside PositionQty › NestedParties › NstdPtysSubGrp
PositionReportAPOptionalOptionalinside PositionQty › NestedParties › NstdPtysSubGrp
QuoteSOptionalOptionalinside LegQuotGrp › NestedParties › NstdPtysSubGrp
QuoteRequestROptionalOptionalinside QuotReqGrp › QuotReqLegsGrp › NestedParties › NstdPtysSubGrp
QuoteRequestRejectAGOptionalOptionalinside QuotReqRjctGrp › QuotReqLegsGrp › NestedParties › NstdPtysSubGrp
QuoteResponseAJOptionalOptionalinside LegQuotGrp › NestedParties › NstdPtysSubGrp
QuoteStatusReportAIOptionalOptionalinside LegQuotStatGrp › NestedParties › NstdPtysSubGrp
RegistrationInstructionsoOptionalOptionalinside RgstDtlsGrp › NestedParties › NstdPtysSubGrp
TradeCaptureReportAEOptionalOptionalinside TrdInstrmtLegGrp › NestedParties › NstdPtysSubGrp
TradeCaptureReportAckAROptionalOptionalinside TrdInstrmtLegGrp › NestedParties › NstdPtysSubGrp

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 545 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 field = message.fields[545];field?.name;   // "NestedPartySubID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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