TradeOriginationDate (FIX tag 229)

LocalMktDateFIX 4.4FIX 5.0 SP2

TradeOriginationDate (tag 229) is a LocalMktDate field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 15 message types, always optionally.

At a glance

Tag: 229
Name: TradeOriginationDate
Datatype: LocalMktDate (String)
Format: YYYYMMDD
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 15

What the specification says

FIX 4.4

Used with Fixed Income for Municipal New Issue Market. Agreement in principal between counter-parties prior to actual trade date. (Note tag # was reserved in FIX 4.1, added in FIX 4.3) (prior to FIX 4.4 field was of type UTCDate)

FIX 5.0 SP2

Used with Fixed Income for Muncipal New Issue Market. Agreement in principal between counter-parties prior to actual trade date.

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

A real message using tag 229

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
229	TradeOriginationDate	20240101
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
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 229 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 5.0 SP2	Where in the message
AllocationInstruction	J	Optional	Optional	directly on the message body
AllocationInstructionAlert	BM	—	Optional	directly on the message body
AllocationReport	AS	Optional	Optional	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	directly on the message body
ListCancelRequest	K	Optional	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
QuoteRequest	R	Optional	Optional	inside the QuotReqGrp component
QuoteRequestReject	AG	Optional	Optional	inside the QuotReqRjctGrp 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 229 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[229];field?.name;   // "TradeOriginationDate"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