SettlDate2 (FIX tag 193)

LocalMktDateFIX 4.4FIX 4.2

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

Also known as FutSettDate2

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

At a glance

Tag: 193
Name: SettlDate2
Datatype: LocalMktDate (String)
Format: YYYYMMDD
Dialects: FIX 4.4 and FIX 4.2
Messages: 11

What the specification says

FIX 4.4

SettDate (64) of the future part of an F/X swap order.

FIX 4.2

FutSettDate of the future part of an F/X swap order.

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

A real message using tag 193

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	124
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
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
193	SettlDate2	20240101
10	CheckSum	089

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 193 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
ExecutionReport	8	Optional	Optional	directly on the message body
MassQuote	i	Optional	Optional	inside QuotSetGrp › QuotEntryGrp
MassQuoteAcknowledgement	b	Optional	—	inside QuotSetAckGrp › QuotEntryAckGrp
NewOrderList	E	Optional	Optional	inside the ListOrdGrp component
NewOrderSingle	D	Optional	Optional	directly on the message body
OrderCancelReplaceRequest	G	Optional	Optional	directly on the message body
Quote	S	Optional	Optional	directly on the message body
QuoteRequest	R	Optional	Optional	inside the QuotReqGrp component
QuoteRequestReject	AG	Optional	—	inside the QuotReqRjctGrp component
QuoteResponse	AJ	Optional	—	directly on the message body
QuoteStatusReport	AI	Optional	—	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 193 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[193];field?.name;   // "SettlDate2"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