SettlDate (FIX tag 64)

LocalMktDateFIX 4.4FIX 4.2

SettlDate (tag 64) is a LocalMktDate field defined in FIX 4.4 and FIX 4.2. It appears in 27 message types, always optionally. FIX 4.2 calls this field FutSettDate; the tag number is unchanged, so the two are the same field on the wire.

Also known as FutSettDate

FIX 4.2 calls tag 64 FutSettDate. It is the same field on the wire — only the name changed — so a message encoded by either side interoperates.

At a glance

Tag: 64
Name: SettlDate
Datatype: LocalMktDate (String)
Format: YYYYMMDD
Dialects: FIX 4.4 and FIX 4.2
Messages: 27

What the specification says

FIX 4.4

Specific date of trade settlement (SettlementDate) in YYYYMMDD format. If present, this field overrides SettlType (63). This field is required if the value of SettlType (63) is 6 (Future) or 8 (Sellers Option). This field must be omitted if the value of SettlType (63) is 7 (When and If Issued) (expressed in local time at place of settlement)

FIX 4.2

Specific date of trade settlement (SettlementDate) in YYYYMMDD format. Required when SettlmntTyp = 6 (Future) or SettlmntTyp = 8 (Sellers Option). (expressed in local time at place of settlement)

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

A real message using tag 64

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	123
35	MsgType	D	Order – Single
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
64	SettlDate	20240103
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	039

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 64 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.

Message	MsgType	FIX 4.4	FIX 4.2	Where in the message
AllocationInstruction	J	Conditional	Optional	directly on the message body
AllocationReport	AS	Conditional	—	directly on the message body
BidRequest	k	Conditional	Optional	inside the BidCompReqGrp component
BidResponse	l	Conditional	Optional	inside the BidCompRspGrp component
CollateralAssignment	AY	Optional	—	directly on the message body
CollateralInquiry	BB	Optional	—	directly on the message body
CollateralInquiryAck	BG	Optional	—	directly on the message body
CollateralReport	BA	Optional	—	directly on the message body
CollateralRequest	AX	Optional	—	directly on the message body
CollateralResponse	AZ	Optional	—	directly on the message body
Confirmation	AK	Conditional	—	directly on the message body
CrossOrderCancelReplaceRequest	t	Conditional	—	directly on the message body
ExecutionReport	8	Conditional	Optional	directly on the message body
MassQuote	i	Optional	Optional	inside QuotSetGrp › QuotEntryGrp
MassQuoteAcknowledgement	b	Optional	—	inside QuotSetAckGrp › QuotEntryAckGrp
MultilegOrderCancelReplace	AC	Conditional	—	directly on the message body
NewOrderCross	s	Conditional	—	directly on the message body
NewOrderList	E	Conditional	Optional	inside the ListOrdGrp component
NewOrderMultileg	AB	Conditional	—	directly on the message body
NewOrderSingle	D	Conditional	Optional	directly on the message body
OrderCancelReplaceRequest	G	Conditional	Optional	directly on the message body
Quote	S	Conditional	Optional	directly on the message body
QuoteRequest	R	Conditional	Optional	inside the QuotReqGrp component
QuoteRequestReject	AG	Conditional	—	inside the QuotReqRjctGrp component
QuoteResponse	AJ	Conditional	—	directly on the message body
QuoteStatusReport	AI	Conditional	—	directly on the message body
TradeCaptureReport	AE	Conditional	—	directly on the message body

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

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 decoder Source on GitHub