PartySubID (FIX tag 523)

StringFIX 4.4FIX 5.0 SP2

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

At a glance

Tag
523
Name
PartySubID
Datatype
String
Dialects
FIX 4.4 and FIX 5.0 SP2
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.

MessageMsgTypeFIX 4.4FIX 5.0 SP2Where in the message
AdjustedPositionReportBLOptionalinside Parties › PtysSubGrp
AllocationInstructionJOptionalOptionalinside Parties › PtysSubGrp
AllocationInstructionAckPOptionalOptionalinside Parties › PtysSubGrp
AllocationInstructionAlertBMOptionalinside Parties › PtysSubGrp
AllocationReportASOptionalOptionalinside Parties › PtysSubGrp
AllocationReportAckATOptionalOptionalinside Parties › PtysSubGrp
ApplicationMessageRequestBWOptionalinside Parties › PtysSubGrp
ApplicationMessageRequestAckBXOptionalinside Parties › PtysSubGrp
AssignmentReportAWOptionalOptionalinside Parties › PtysSubGrp
CollateralAssignmentAYOptionalOptionalinside Parties › PtysSubGrp
CollateralInquiryBBOptionalOptionalinside Parties › PtysSubGrp
CollateralInquiryAckBGOptionalOptionalinside Parties › PtysSubGrp
CollateralReportBAOptionalOptionalinside Parties › PtysSubGrp
CollateralRequestAXOptionalOptionalinside Parties › PtysSubGrp
CollateralResponseAZOptionalOptionalinside Parties › PtysSubGrp
ConfirmationAKOptionalOptionalinside Parties › PtysSubGrp
ContraryIntentionReportBOOptionalinside Parties › PtysSubGrp
CrossOrderCancelReplaceRequesttOptionalOptionalinside SideCrossOrdModGrp › Parties › PtysSubGrp
CrossOrderCancelRequestuOptionalOptionalinside SideCrossOrdCxlGrp › Parties › PtysSubGrp
ExecutionReport8OptionalOptionalinside Parties › PtysSubGrp
IOI6Optionalinside Parties › PtysSubGrp
ListCancelRequestKOptionalinside Parties › PtysSubGrp
MarketDataIncrementalRefreshXOptionalinside MDIncGrp › Parties › PtysSubGrp
MarketDataRequestVOptionalinside Parties › PtysSubGrp
MarketDataRequestRejectYOptionalinside Parties › PtysSubGrp
MarketDataSnapshotFullRefreshWOptionalinside MDFullGrp › Parties › PtysSubGrp
MassQuoteiOptionalOptionalinside Parties › PtysSubGrp
MassQuoteAcknowledgementbOptionalOptionalinside Parties › PtysSubGrp
MultilegOrderCancelReplaceACOptionalOptionalinside Parties › PtysSubGrp
NewOrderCrosssOptionalOptionalinside SideCrossOrdModGrp › Parties › PtysSubGrp
NewOrderListEOptionalOptionalinside ListOrdGrp › Parties › PtysSubGrp
NewOrderMultilegABOptionalOptionalinside Parties › PtysSubGrp
NewOrderSingleDOptionalOptionalinside Parties › PtysSubGrp
OrderCancelReplaceRequestGOptionalOptionalinside Parties › PtysSubGrp
OrderCancelRequestFOptionalOptionalinside Parties › PtysSubGrp
OrderMassActionReportBZOptionalinside Parties › PtysSubGrp
OrderMassActionRequestCAOptionalinside Parties › PtysSubGrp
OrderMassCancelReportrOptionalinside Parties › PtysSubGrp
OrderMassCancelRequestqOptionalinside Parties › PtysSubGrp
OrderMassStatusRequestAFOptionalOptionalinside Parties › PtysSubGrp
OrderStatusRequestHOptionalOptionalinside Parties › PtysSubGrp
PositionMaintenanceReportAMOptionalOptionalinside Parties › PtysSubGrp
PositionMaintenanceRequestALOptionalOptionalinside Parties › PtysSubGrp
PositionReportAPOptionalOptionalinside Parties › PtysSubGrp
QuoteSOptionalOptionalinside Parties › PtysSubGrp
QuoteCancelZOptionalOptionalinside Parties › PtysSubGrp
QuoteRequestROptionalOptionalinside QuotReqGrp › Parties › PtysSubGrp
QuoteRequestRejectAGOptionalOptionalinside QuotReqRjctGrp › Parties › PtysSubGrp
QuoteResponseAJOptionalOptionalinside Parties › PtysSubGrp
QuoteStatusReportAIOptionalOptionalinside Parties › PtysSubGrp
QuoteStatusRequestaOptionalOptionalinside Parties › PtysSubGrp
RFQRequestAHOptionalinside Parties › PtysSubGrp
RegistrationInstructionsoOptionalOptionalinside Parties › PtysSubGrp
RegistrationInstructionsResponsepOptionalOptionalinside Parties › PtysSubGrp
RequestForPositionsANOptionalOptionalinside Parties › PtysSubGrp
RequestForPositionsAckAOOptionalOptionalinside Parties › PtysSubGrp
SettlementInstructionRequestAVOptionalOptionalinside Parties › PtysSubGrp
SettlementInstructionsTOptionalOptionalinside SettlInstGrp › Parties › PtysSubGrp
SettlementObligationReportBQOptionalinside SettlObligationInstructions › Parties › PtysSubGrp
StreamAssignmentReportCDOptionalinside StrmAsgnRptGrp › Parties › PtysSubGrp
StreamAssignmentRequestCCOptionalinside StrmAsgnReqGrp › Parties › PtysSubGrp
TradeCaptureReportAEOptionalOptionalinside TrdCapRptSideGrp › Parties › PtysSubGrp
TradeCaptureReportAckAROptionalinside TrdCapRptAckSideGrp › Parties › PtysSubGrp
TradeCaptureReportRequestADOptionalOptionalinside 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