SecondaryClOrdID (FIX tag 526)

StringFIX 4.4FIX 5.0 SP2

SecondaryClOrdID (tag 526) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 27 message types, always optionally.

At a glance

Tag: 526
Name: SecondaryClOrdID
Datatype: String
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 27

What the specification says

Assigned by the party which originates the order. Can be used to provide the ClOrdID (11) used by an exchange or executing system.

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

A real message using tag 526

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
526	SecondaryClOrdID	EXAMPLE
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	218

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 526 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	inside the OrdAllocGrp component
AllocationInstructionAlert	BM	—	Optional	inside the OrdAllocGrp component
AllocationReport	AS	Optional	Optional	inside the OrdAllocGrp component
CollateralAssignment	AY	Optional	Optional	directly on the message body
CollateralInquiry	BB	Optional	Optional	directly on the message body
CollateralInquiryAck	BG	Optional	Optional	directly on the message body
CollateralReport	BA	Optional	Optional	directly on the message body
CollateralRequest	AX	Optional	Optional	directly on the message body
CollateralResponse	AZ	Optional	Optional	directly on the message body
Confirmation	AK	Optional	Optional	inside the OrdAllocGrp component
ConfirmationRequest	BH	Optional	Optional	inside the OrdAllocGrp component
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
ListStatus	N	Optional	Optional	inside the OrdListStatGrp component
ListStrikePrice	m	Optional	Optional	inside the UndInstrmtStrkPxGrp component
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
OrderCancelRequest	F	Optional	Optional	directly on the message body
OrderMassActionReport	BZ	—	Optional	directly on the message body
OrderMassActionRequest	CA	—	Optional	directly on the message body
OrderMassCancelReport	r	Optional	Optional	directly on the message body
OrderMassCancelRequest	q	Optional	Optional	directly on the message body
OrderStatusRequest	H	Optional	Optional	directly on the message body
TradeCaptureReport	AE	Optional	Optional	inside the TrdCapRptSideGrp component
TradeCaptureReportAck	AR	—	Optional	inside TrdCapRptAckSideGrp › TradeReportOrderDetail

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 526 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[526];field?.name;   // "SecondaryClOrdID"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