OrdRejReason (FIX tag 103)

intFIX 4.4FIX 4.2FIX 5.0 SP2

OrdRejReason (tag 103) is an int field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 2 message types, always optionally. It is an enumerated field with 16 defined values.

At a glance

Tag: 103
Name: OrdRejReason
Datatype: int
Dialects: FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages: 2
Valid values: 16

What the specification says

FIX 4.4

Code to identify reason for order rejection.

FIX 4.2

Code to identify reason for order rejection.

FIX 5.0 SP2

Code to identify reason for order rejection. Note: Values 3, 4, and 5 will be used when rejecting an order due to pre-allocation information errors.

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

A real message using tag 103

ExecutionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	139
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
17	ExecID	EXEC-88117
150	ExecType	0	New
39	OrdStatus	0	New
103	OrdRejReason	0	Broker / Exchange option
54	Side	1	Buy
151	LeavesQty	0
14	CumQty	1000000
6	AvgPx	1.09215
10	CheckSum	033

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.

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	Dialects
0	Broker / Exchange option	BROKER / BrokerCredit / BROKER_EXCHANGE_OPTION	FIX 4.4, FIX 4.2, FIX 5.0 SP2
1	Unknown symbol	UNKNOWN_SYMBOL / UnknownSymbol	FIX 4.4, FIX 4.2, FIX 5.0 SP2
2	Exchange closed	EXCHANGE_CLOSED / ExchangeClosed	FIX 4.4, FIX 4.2, FIX 5.0 SP2
3	Order exceeds limit	ORDER_EXCEEDS_LIMIT / OrderExceedsLimit	FIX 4.4, FIX 4.2, FIX 5.0 SP2
4	Too late to enter	TOO_LATE_TO_ENTER / TooLateToEnter	FIX 4.4, FIX 4.2, FIX 5.0 SP2
5	Unknown Order	UNKNOWN_ORDER / UnknownOrder	FIX 4.4, FIX 4.2, FIX 5.0 SP2
6	Duplicate Order (e.g. dupe ClOrdID (11))	DUPLICATE_ORDER / DuplicateOrder	FIX 4.4, FIX 4.2, FIX 5.0 SP2
7	Duplicate of a verbally communicated order	DUPLICATE_OF_A_VERBALLY_COMMUNICATED_ORDER / DuplicateOfAVerballyCommunicatedOrder	FIX 4.4, FIX 4.2, FIX 5.0 SP2
8	Stale Order	STALE_ORDER / StaleOrder	FIX 4.4, FIX 4.2, FIX 5.0 SP2
9	Trade Along required	TRADE_ALONG_REQUIRED	FIX 4.4, FIX 5.0 SP2
10	Invalid Investor ID	INVALID_INVESTOR_ID	FIX 4.4, FIX 5.0 SP2
11	Unsupported order characteristic	UNSUPPORTED_ORDER_CHARACTERISTIC12_SURVEILLENCE_OPTION / UNSUPPORTED_ORDER_CHARACTERISTIC	FIX 4.4, FIX 5.0 SP2
13	Incorrect quantity	INCORRECT_QUANTITY	FIX 4.4, FIX 5.0 SP2
14	Incorrect allocated quantity	INCORRECT_ALLOCATED_QUANTITY	FIX 4.4, FIX 5.0 SP2
15	Unknown account(s)	UNKNOWN_ACCOUNT	FIX 4.4, FIX 5.0 SP2
99	Other	OTHER	FIX 4.4, FIX 5.0 SP2
12	Surveillance option	SURVEILLENCE_OPTION	FIX 5.0 SP2
16	Price exceeds current price band	PRICE_EXCEEDS_CURRENT_PRICE_BAND	FIX 5.0 SP2
18	Invalid price increment	INVALID_PRICE_INCREMENT	FIX 5.0 SP2

Where tag 103 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	FIX 5.0 SP2	Where in the message
ExecutionReport	8	Optional	Optional	Optional	directly on the message body
ListStatus	N	Optional	Optional	Optional	inside the OrdListStatGrp component

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 103 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 ordRejReason = message.fields[103]?.raw;// e.g. "0" — Broker / Exchange option// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(103)  ?.enumValues?.find((e) => e.value === ordRejReason)  ?.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-fix44

Try the decoder Source on GitHub