TradeDate (FIX tag 75)

LocalMktDateFIX 4.4FIX 4.2FIX 5.0 SP2

TradeDate (tag 75) is a LocalMktDate field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 21 message types and is required in 5 of them.

At a glance

Tag: 75
Name: TradeDate
Datatype: LocalMktDate (String)
Format: YYYYMMDD
Dialects: FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages: 21

What the specification says

FIX 4.4

Indicates date of trade referenced in this message in YYYYMMDD format. Absence of this field indicates current day (expressed in local time at place of trade).

FIX 4.2

Indicates date of trade referenced in this message in YYYYMMDD format. Absence of this field indicates current day (expressed in local time at place of trade).

FIX 5.0 SP2

Indicates date of trading day. Absence of this field indicates current day (expressed in local time at place of trade).

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

A real message using tag 75

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
75	TradeDate	20240101
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 75 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	FIX 5.0 SP2	Where in the message
Advertisement	7	Optional	Optional	Optional	directly on the message body
AllocationInstruction	J	Required	Required	Required	directly on the message body
AllocationInstructionAck	P	Optional	Required	Optional	directly on the message body
AllocationInstructionAlert	BM	—	—	Required	directly on the message body
AllocationReport	AS	Required	—	Required	directly on the message body
AllocationReportAck	AT	Optional	—	Optional	directly on the message body
BidRequest	k	Optional	Optional	Optional	directly on the message body
Confirmation	AK	Required	—	Required	directly on the message body
ConfirmationAck	AU	Required	—	Required	directly on the message body
CrossOrderCancelReplaceRequest	t	Optional	—	Optional	inside the SideCrossOrdModGrp component
CrossOrderCancelRequest	u	Optional	—	Optional	inside the SideCrossOrdCxlGrp component
ExecutionReport	8	Optional	Optional	Optional	directly on the message body
ListCancelRequest	K	Optional	—	Optional	directly on the message body
MarketDataIncrementalRefresh	X	—	—	Optional	directly on the message body
MarketDataSnapshotFullRefresh	W	—	—	Optional	directly on the message body
MultilegOrderCancelReplace	AC	Optional	—	Optional	directly on the message body
NewOrderCross	s	Optional	—	Optional	inside the SideCrossOrdModGrp component
NewOrderList	E	Optional	—	Optional	inside the ListOrdGrp component
NewOrderMultileg	AB	Optional	—	Optional	directly on the message body
NewOrderSingle	D	Optional	—	Optional	directly on the message body
OrderCancelReject	9	Optional	—	Optional	directly on the message body
OrderCancelReplaceRequest	G	Optional	—	Optional	directly on the message body
SettlementInstructions	T	—	Optional	—	directly on the message body
TradeCaptureReport	AE	Required	—	Optional	directly on the message body
TradeCaptureReportAck	AR	—	—	Optional	directly on the message body
TradeCaptureReportRequest	AD	Conditional	—	Optional	inside the TrdCapDtGrp 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 75 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[75];field?.name;   // "TradeDate"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