OrigClOrdID (FIX tag 41)

StringFIX 4.4FIX 4.2

OrigClOrdID (tag 41) is a String field defined in FIX 4.4 and FIX 4.2. It appears in 7 message types and is required in 5 of them.

At a glance

Tag: 41
Name: OrigClOrdID
Datatype: String
Dialects: FIX 4.4 and FIX 4.2
Messages: 7

What the specification says

FIX 4.4

ClOrdID () of the previous order (NOT the initial order of the day) as assigned by the institution, used to identify the previous order in cancel and cancel/replace requests.

FIX 4.2

ClOrdID of the previous order (NOT the initial order of the day) as assigned by the institution, used to identify the previous order in cancel and cancel/replace requests.

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

A real message using tag 41

ExecutionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	146
35	MsgType	8	Execution Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
41	OrigClOrdID	ORD-10041
17	ExecID	EXEC-88117
150	ExecType	0	New
39	OrdStatus	0	New
54	Side	1	Buy
151	LeavesQty	0
14	CumQty	1000000
6	AvgPx	1.09215
10	CheckSum	200

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 41 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
CrossOrderCancelRequest	u	Required	—	inside the SideCrossOrdCxlGrp component
ExecutionReport	8	Optional	Optional	directly on the message body
MultilegOrderCancelReplace	AC	Required	—	directly on the message body
OrderCancelReject	9	Required	Required	directly on the message body
OrderCancelReplaceRequest	G	Required	Required	directly on the message body
OrderCancelRequest	F	Required	Required	directly on the message body
OrderMassCancelReport	r	Conditional	—	inside the AffectedOrdGrp component

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

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