YieldRedemptionDate (FIX tag 696)

LocalMktDateFIX 4.4FIX 5.0 SP2

YieldRedemptionDate (tag 696) is a LocalMktDate field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 17 message types, always optionally.

At a glance

Tag
696
Name
YieldRedemptionDate
Datatype
LocalMktDate (String)
Format
YYYYMMDD
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
17

What the specification says

Date to which the yield has been calculated (i.e. maturity, par call or current call, pre-refunded date).

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

A real message using tag 696

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength124
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
696YieldRedemptionDate20240101
10CheckSum097
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 696 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
AllocationInstructionJOptionalOptionalinside the YieldData component
AllocationInstructionAlertBMOptionalinside the YieldData component
AllocationReportASOptionalOptionalinside the YieldData component
ConfirmationAKOptionalOptionalinside the YieldData component
CrossOrderCancelReplaceRequesttOptionalOptionalinside the YieldData component
ExecutionReport8OptionalOptionalinside the YieldData component
IOI6OptionalOptionalinside the YieldData component
MarketDataIncrementalRefreshXOptionalinside MDIncGrp › YieldData
MarketDataSnapshotFullRefreshWOptionalinside MDFullGrp › YieldData
NewOrderCrosssOptionalOptionalinside the YieldData component
NewOrderListEOptionalOptionalinside ListOrdGrp › YieldData
NewOrderSingleDOptionalOptionalinside the YieldData component
OrderCancelReplaceRequestGOptionalOptionalinside the YieldData component
QuoteSOptionalOptionalinside the YieldData component
QuoteRequestROptionalOptionalinside QuotReqGrp › YieldData
QuoteRequestRejectAGOptionalOptionalinside QuotReqRjctGrp › YieldData
QuoteResponseAJOptionalOptionalinside the YieldData component
QuoteStatusReportAIOptionalOptionalinside the YieldData component
SecurityDefinitiondOptionalinside the YieldData component
SecurityDefinitionRequestcOptionalinside the YieldData component
SecurityDefinitionUpdateReportBPOptionalinside the YieldData component
SecurityListyOptionalOptionalinside SecListGrp › YieldData
SecurityListUpdateReportBKOptionalinside SecLstUpdRelSymGrp › YieldData
TradeCaptureReportAEOptionalOptionalinside the YieldData component

Wire format

A calendar date in the market's local timezone, with no time component and no offset. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

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

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