OrigOrdModTime (FIX tag 586)

UTCTimestampFIX 4.4FIX 5.0 SP2

OrigOrdModTime (tag 586) is an UTCTimestamp field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 5 message types, always optionally.

At a glance

Tag: 586
Name: OrigOrdModTime
Datatype: UTCTimestamp (String)
Format: YYYYMMDD-HH:MM:SS[.sss]
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 5

What the specification says

FIX 4.4

The most recent (or current) modification TransactTime (tag 60) reported on an Execution Report for the order. The OrigOrdModTime is provided as an optional field on Order Cancel Request and Order Cancel Replace Requests to identify that the state of the order has not changed since the request was issued. This is provided to support markets similar to Eurex and A/C/E.

FIX 5.0 SP2

The most recent (or current) modification TransactTime (tag 60) reported on an Execution Report for the order. The OrigOrdModTime is provided as an optional field on Order Cancel Request and Order Cancel Replace Requests to identify that the state of the order has not changed since the request was issued. The use of this approach is not recommended.

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

A real message using tag 586

OrderCancelReplaceRequest · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	150
35	MsgType	G	Order Cancel/Replace Request
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
41	OrigClOrdID	ORD-10041
11	ClOrdID	ORD-10042
586	OrigOrdModTime	20240101-12:00:00.000
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	142

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 586 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
CrossOrderCancelRequest	u	Optional	Optional	inside the SideCrossOrdCxlGrp component
MultilegOrderCancelReplace	AC	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
OrderCancelRequest	F	Optional	Optional	directly on the message body
TradeCaptureReport	AE	—	Optional	inside TrdCapRptSideGrp › TradeReportOrderDetail
TradeCaptureReportAck	AR	—	Optional	inside TrdCapRptAckSideGrp › TradeReportOrderDetail

Wire format

A UTC date and time. The fractional-seconds part is optional, so two timestamps can be equal but not byte-identical. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 586 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[586];field?.name;   // "OrigOrdModTime"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