RefOrderIDSource (FIX tag 1081)

charFIX 5.0 SP2

RefOrderIDSource (tag 1081) is a char field defined in FIX 5.0 SP2. It appears in 5 message types, always optionally. It is an enumerated field with 5 defined values.

At a glance

Tag: 1081
Name: RefOrderIDSource
Datatype: char
Dialects: FIX 5.0 SP2
Messages: 5
Valid values: 5

What the specification says

Used to specify the source for the identifier in RefOrderID(1080). This can be an identifier provided in order depth market data when hitting (taking) a specific order or to identify what type of order or quote reference is being provided when seeking credit limit check. In the context of US CAT this can be used to identify related orders and quotes which are parent, previous, or manual orders or quotes. Previous relates to orders changing their unique system assigned order identifier.

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

A real message using tag 1081

NewOrderSingle · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	118
35	MsgType	D	NewOrderSingle
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
1081	RefOrderIDSource	0	Secondary order ID
10	CheckSum	125

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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Value	Meaning	Symbolic name
0	Secondary order ID	SECONDARYORDERID
1	Order ID	ORDERID
2	Market data entry ID	MDENTRYID
3	Quote entry ID	QUOTEENTRYID
4	Original order ID	ORIGINAL_ORDER_ID

Where tag 1081 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	Requiredness	Where in the message
NewOrderList	E	Optional	inside the ListOrdGrp component
NewOrderMultileg	AB	Optional	directly on the message body
NewOrderSingle	D	Optional	directly on the message body
TradeCaptureReport	AE	Optional	inside TrdCapRptSideGrp › TradeReportOrderDetail
TradeCaptureReportAck	AR	Optional	inside TrdCapRptAckSideGrp › TradeReportOrderDetail

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 1081 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const refOrderIDSource = message.fields[1081]?.raw;// e.g. "0" — Secondary order ID// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1081)  ?.enumValues?.find((e) => e.value === refOrderIDSource)  ?.description;

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-fix50sp2

Try the decoder Source on GitHub