Boar Team
GitHub

PartySubID (FIX tag 523)

StringFIX 4.4

PartySubID (tag 523) is a String field defined in FIX 4.4. It appears in 44 message types, always optionally.

At a glance

Tag
523
Name
PartySubID
Datatype
String
Dialects
FIX 4.4
Messages
44

What the specification says

Sub-identifier (e.g. Clearing Account for PartyRole (452)=Clearing Firm, Locate ID # for PartyRole=Locate/Lending Firm, etc). Not required when using PartyID (448), PartyIDSource (447), and PartyRole.

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

A real message using tag 523

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength159
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
453NoPartyIDs1 entry1repeating group
448PartyIDEXAMPLE
802NoPartySubIDs2 entries2repeating group
523PartySubIDEXAMPLE
523PartySubIDEXAMPLE
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum195
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 523 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.

MessageMsgTypeRequirednessWhere in the message
AllocationInstructionJOptionalinside Parties › PtysSubGrp
AllocationInstructionAckPOptionalinside Parties › PtysSubGrp
AllocationReportASOptionalinside Parties › PtysSubGrp
AllocationReportAckATOptionalinside Parties › PtysSubGrp
AssignmentReportAWOptionalinside Parties › PtysSubGrp
CollateralAssignmentAYOptionalinside Parties › PtysSubGrp
CollateralInquiryBBOptionalinside Parties › PtysSubGrp
CollateralInquiryAckBGOptionalinside Parties › PtysSubGrp
CollateralReportBAOptionalinside Parties › PtysSubGrp
CollateralRequestAXOptionalinside Parties › PtysSubGrp
CollateralResponseAZOptionalinside Parties › PtysSubGrp
ConfirmationAKOptionalinside Parties › PtysSubGrp
CrossOrderCancelReplaceRequesttOptionalinside SideCrossOrdModGrp › Parties › PtysSubGrp
CrossOrderCancelRequestuOptionalinside SideCrossOrdCxlGrp › Parties › PtysSubGrp
ExecutionReport8Optionalinside Parties › PtysSubGrp
MassQuoteiOptionalinside Parties › PtysSubGrp
MassQuoteAcknowledgementbOptionalinside Parties › PtysSubGrp
MultilegOrderCancelReplaceACOptionalinside Parties › PtysSubGrp
NewOrderCrosssOptionalinside SideCrossOrdModGrp › Parties › PtysSubGrp
NewOrderListEOptionalinside ListOrdGrp › Parties › PtysSubGrp
NewOrderMultilegABOptionalinside Parties › PtysSubGrp
NewOrderSingleDOptionalinside Parties › PtysSubGrp
OrderCancelReplaceRequestGOptionalinside Parties › PtysSubGrp
OrderCancelRequestFOptionalinside Parties › PtysSubGrp
OrderMassStatusRequestAFOptionalinside Parties › PtysSubGrp
OrderStatusRequestHOptionalinside Parties › PtysSubGrp
PositionMaintenanceReportAMOptionalinside Parties › PtysSubGrp
PositionMaintenanceRequestALOptionalinside Parties › PtysSubGrp
PositionReportAPOptionalinside Parties › PtysSubGrp
QuoteSOptionalinside Parties › PtysSubGrp
QuoteCancelZOptionalinside Parties › PtysSubGrp
QuoteRequestROptionalinside QuotReqGrp › Parties › PtysSubGrp
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › Parties › PtysSubGrp
QuoteResponseAJOptionalinside Parties › PtysSubGrp
QuoteStatusReportAIOptionalinside Parties › PtysSubGrp
QuoteStatusRequestaOptionalinside Parties › PtysSubGrp
RegistrationInstructionsoOptionalinside Parties › PtysSubGrp
RegistrationInstructionsResponsepOptionalinside Parties › PtysSubGrp
RequestForPositionsANOptionalinside Parties › PtysSubGrp
RequestForPositionsAckAOOptionalinside Parties › PtysSubGrp
SettlementInstructionRequestAVOptionalinside Parties › PtysSubGrp
SettlementInstructionsTOptionalinside SettlInstGrp › Parties › PtysSubGrp
TradeCaptureReportAEOptionalinside TrdCapRptSideGrp › Parties › PtysSubGrp
TradeCaptureReportRequestADOptionalinside Parties › PtysSubGrp

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 523 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[523];field?.name;   // "PartySubID"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
Try the decoderSource on GitHub