UnderlyingSecurityIDSource (FIX tag 305)

StringFIX 4.4FIX 4.2FIX 5.0 SP2

UnderlyingSecurityIDSource (tag 305) is a String field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 59 message types, always optionally. FIX 4.2 calls this field UnderlyingIDSource; the tag number is unchanged, so the two are the same field on the wire.

Also known as UnderlyingIDSource
FIX 4.2 calls tag 305 UnderlyingIDSource. It is the same field on the wire — only the name changed — so a message encoded by either side interoperates.

At a glance

Tag
305
Name
UnderlyingSecurityIDSource
Datatype
String
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
59

What the specification says

FIX 4.4

Underlying security’s SecurityIDSource. Valid values: see SecurityIDSource (22) field

FIX 4.2

Underlying security’s IDSource.

FIX 5.0 SP2

Identifies class or source of the UnderlyingSecurityID(309) value.

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

A real message using tag 305

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength165
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
711NoUnderlyings2 entries2repeating group
311UnderlyingSymbolEXAMPLE
305UnderlyingSecurityIDSourceEXAMPLE
311UnderlyingSymbolEXAMPLE
305UnderlyingSecurityIDSourceEXAMPLE
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum132
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 305 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 4.2FIX 5.0 SP2Where in the message
Advertisement7Optional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
AllocationInstructionJOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
AllocationInstructionAlertBM——Optionalinside UndInstrmtGrp › UnderlyingInstrument
AllocationReportASOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
AssignmentReportAWOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralAssignmentAYOptional—Optionalinside UndInstrmtCollGrp › UnderlyingInstrument
CollateralInquiryBBOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralInquiryAckBGOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralReportBAOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralRequestAXOptional—Optionalinside UndInstrmtCollGrp › UnderlyingInstrument
CollateralResponseAZOptional—Optionalinside UndInstrmtCollGrp › UnderlyingInstrument
ConfirmationAKOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
ContraryIntentionReportBO——Optionalinside UndInstrmtGrp › UnderlyingInstrument
CrossOrderCancelReplaceRequesttOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
CrossOrderCancelRequestuOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
DerivativeSecurityListAAOptional—Optionalinside the UnderlyingInstrument component
DerivativeSecurityListRequestzOptional—Optionalinside the UnderlyingInstrument component
DerivativeSecurityListUpdateReportBR——Optionalinside the UnderlyingInstrument component
DontKnowTradeQOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
EmailCOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
ExecutionAcknowledgementBN——Optionalinside UndInstrmtGrp › UnderlyingInstrument
ExecutionReport8Optional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
IOI6Optional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
ListStrikePricemOptional—Optionalinside UndInstrmtStrkPxGrp › UnderlyingInstrument
MarketDataIncrementalRefreshXOptional—Optionalinside MDIncGrp › UndInstrmtGrp › UnderlyingInstrument
MarketDataRequestVOptional—Optionalinside InstrmtMDReqGrp › UndInstrmtGrp › UnderlyingInstrument
MarketDataSnapshotFullRefreshWOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
MassQuoteiOptionalOptionalOptionalinside QuotSetGrp › UnderlyingInstrument
MassQuoteAcknowledgementbOptionalOptionalOptionalinside QuotSetAckGrp › UnderlyingInstrument
MultilegOrderCancelReplaceACOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderCrosssOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderListEOptional—Optionalinside ListOrdGrp › UndInstrmtGrp › UnderlyingInstrument
NewOrderMultilegABOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderSingleDOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
NewsBOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
OrderCancelReplaceRequestGOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
OrderCancelRequestFOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
OrderMassActionReportBZ——Optionalinside the UnderlyingInstrument component
OrderMassActionRequestCA——Optionalinside the UnderlyingInstrument component
OrderMassCancelReportrOptional—Optionalinside the UnderlyingInstrument component
OrderMassCancelRequestqOptional—Optionalinside the UnderlyingInstrument component
OrderMassStatusRequestAFOptional—Optionalinside the UnderlyingInstrument component
OrderStatusRequestHOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
PositionMaintenanceReportAMOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
PositionMaintenanceRequestALOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
PositionReportAPOptional—Optionalinside PosUndInstrmtGrp › UnderlyingInstrument
QuoteSOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteCancelZOptional—Optionalinside QuotCxlEntriesGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteRequestROptional—Optionalinside QuotReqGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteRequestRejectAGOptional—Optionalinside QuotReqRjctGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteResponseAJOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteStatusReportAIOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteStatusRequestaOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
RFQRequestAHOptional—Optionalinside RFQReqGrp › UndInstrmtGrp › UnderlyingInstrument
RequestForPositionsANOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
RequestForPositionsAckAOOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityDefinitiondOptionalOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityDefinitionRequestcOptionalOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityDefinitionUpdateReportBP——Optionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityListyOptional—Optionalinside SecListGrp › UndInstrmtGrp › UnderlyingInstrument
SecurityListRequestxOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityListUpdateReportBK——Optionalinside SecLstUpdRelSymGrp › UndInstrmtGrp › UnderlyingInstrument
SecurityStatusfOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityStatusRequesteOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportAEOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportAckAR——Optionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportRequestADOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportRequestAckAQOptional—Optionalinside UndInstrmtGrp › UnderlyingInstrument

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 305 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[305];field?.name;   // "UnderlyingSecurityIDSource"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