UnderlyingMaturityMonthYear (FIX tag 313)

MonthYearFIX 4.4FIX 4.2FIX 5.0 SP2

UnderlyingMaturityMonthYear (tag 313) is a MonthYear field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 59 message types, always optionally.

At a glance

Tag
313
Name
UnderlyingMaturityMonthYear
Datatype
MonthYear (String)
Format
YYYYMM[DD|WW]
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
59

What the specification says

FIX 4.4

Underlying security’s MaturityMonthYear. Can be used with standardized derivatives vs. the UnderlyingMaturityDate (542) field. See MaturityMonthYear (200) field for description

FIX 4.2

Underlying security’s MaturityMonthYear. Required if UnderlyingMaturityDay is specified. See MaturityMonthYear field for description

FIX 5.0 SP2

Underlying security's MaturityMonthYear. Can be used with standardized derivatives vs. the UnderlyingMaturityDate (542) field.

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

A real message using tag 313

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength163
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
711NoUnderlyings2 entries2repeating group
311UnderlyingSymbolEXAMPLE
313UnderlyingMaturityMonthYear202401
311UnderlyingSymbolEXAMPLE
313UnderlyingMaturityMonthYear202401
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum186
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 313 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
Advertisement7OptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
AllocationInstructionJOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
AllocationInstructionAlertBMOptionalinside UndInstrmtGrp › UnderlyingInstrument
AllocationReportASOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
AssignmentReportAWOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralAssignmentAYOptionalOptionalinside UndInstrmtCollGrp › UnderlyingInstrument
CollateralInquiryBBOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralInquiryAckBGOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralReportBAOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralRequestAXOptionalOptionalinside UndInstrmtCollGrp › UnderlyingInstrument
CollateralResponseAZOptionalOptionalinside UndInstrmtCollGrp › UnderlyingInstrument
ConfirmationAKOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
ContraryIntentionReportBOOptionalinside UndInstrmtGrp › UnderlyingInstrument
CrossOrderCancelReplaceRequesttOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
CrossOrderCancelRequestuOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
DerivativeSecurityListAAOptionalOptionalinside the UnderlyingInstrument component
DerivativeSecurityListRequestzOptionalOptionalinside the UnderlyingInstrument component
DerivativeSecurityListUpdateReportBROptionalinside the UnderlyingInstrument component
DontKnowTradeQOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
EmailCOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
ExecutionAcknowledgementBNOptionalinside UndInstrmtGrp › UnderlyingInstrument
ExecutionReport8OptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
IOI6OptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
ListStrikePricemOptionalOptionalinside UndInstrmtStrkPxGrp › UnderlyingInstrument
MarketDataIncrementalRefreshXOptionalOptionalinside MDIncGrp › UndInstrmtGrp › UnderlyingInstrument
MarketDataRequestVOptionalOptionalinside InstrmtMDReqGrp › UndInstrmtGrp › UnderlyingInstrument
MarketDataSnapshotFullRefreshWOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
MassQuoteiOptionalOptionalOptionalinside QuotSetGrp › UnderlyingInstrument
MassQuoteAcknowledgementbOptionalOptionalOptionalinside QuotSetAckGrp › UnderlyingInstrument
MultilegOrderCancelReplaceACOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderCrosssOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderListEOptionalOptionalinside ListOrdGrp › UndInstrmtGrp › UnderlyingInstrument
NewOrderMultilegABOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderSingleDOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewsBOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
OrderCancelReplaceRequestGOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
OrderCancelRequestFOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
OrderMassActionReportBZOptionalinside the UnderlyingInstrument component
OrderMassActionRequestCAOptionalinside the UnderlyingInstrument component
OrderMassCancelReportrOptionalOptionalinside the UnderlyingInstrument component
OrderMassCancelRequestqOptionalOptionalinside the UnderlyingInstrument component
OrderMassStatusRequestAFOptionalOptionalinside the UnderlyingInstrument component
OrderStatusRequestHOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
PositionMaintenanceReportAMOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
PositionMaintenanceRequestALOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
PositionReportAPOptionalOptionalinside PosUndInstrmtGrp › UnderlyingInstrument
QuoteSOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteCancelZOptionalOptionalinside QuotCxlEntriesGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteRequestROptionalOptionalinside QuotReqGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteRequestRejectAGOptionalOptionalinside QuotReqRjctGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteResponseAJOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteStatusReportAIOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteStatusRequestaOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
RFQRequestAHOptionalOptionalinside RFQReqGrp › UndInstrmtGrp › UnderlyingInstrument
RequestForPositionsANOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
RequestForPositionsAckAOOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityDefinitiondOptionalOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityDefinitionRequestcOptionalOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityDefinitionUpdateReportBPOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityListyOptionalOptionalinside SecListGrp › UndInstrmtGrp › UnderlyingInstrument
SecurityListRequestxOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityListUpdateReportBKOptionalinside SecLstUpdRelSymGrp › UndInstrmtGrp › UnderlyingInstrument
SecurityStatusfOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityStatusRequesteOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportAEOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportAckAROptionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportRequestADOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportRequestAckAQOptionalOptionalinside UndInstrmtGrp › UnderlyingInstrument

Wire format

A month, optionally with a day or week — the format pattern shows which forms are legal. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 313 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[313];field?.name;   // "UnderlyingMaturityMonthYear"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other MonthYear 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