Boar Team
GitHub

OrdRejReason (FIX tag 103)

intFIX 4.4FIX 4.2

OrdRejReason (tag 103) is an int field defined in FIX 4.4 and FIX 4.2. 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 and FIX 4.2
Messages
2
Valid values
16

What the specification says

Code to identify reason for order rejection.

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

A real message using tag 103

ExecutionReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength139
35MsgType8Execution Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
17ExecIDEXEC-88117
150ExecType0New
39OrdStatus0New
103OrdRejReason0Broker / Exchange option
54Side1Buy
151LeavesQty0
14CumQty1000000
6AvgPx1.09215
10CheckSum033
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.

ValueMeaningSymbolic nameDialects
0Broker / Exchange optionBROKER / BrokerCreditFIX 4.4, FIX 4.2
1Unknown symbolUNKNOWN_SYMBOL / UnknownSymbolFIX 4.4, FIX 4.2
2Exchange closedEXCHANGE_CLOSED / ExchangeClosedFIX 4.4, FIX 4.2
3Order exceeds limitORDER_EXCEEDS_LIMIT / OrderExceedsLimitFIX 4.4, FIX 4.2
4Too late to enterTOO_LATE_TO_ENTER / TooLateToEnterFIX 4.4, FIX 4.2
5Unknown OrderUNKNOWN_ORDER / UnknownOrderFIX 4.4, FIX 4.2
6Duplicate Order (e.g. dupe ClOrdID (11))DUPLICATE_ORDER / DuplicateOrderFIX 4.4, FIX 4.2
7Duplicate of a verbally communicated orderDUPLICATE_OF_A_VERBALLY_COMMUNICATED_ORDER / DuplicateOfAVerballyCommunicatedOrderFIX 4.4, FIX 4.2
8Stale OrderSTALE_ORDER / StaleOrderFIX 4.4, FIX 4.2
9Trade Along requiredTRADE_ALONG_REQUIREDFIX 4.4
10Invalid Investor IDINVALID_INVESTOR_IDFIX 4.4
11Unsupported order characteristicUNSUPPORTED_ORDER_CHARACTERISTIC12_SURVEILLENCE_OPTIONFIX 4.4
13Incorrect quantityINCORRECT_QUANTITYFIX 4.4
14Incorrect allocated quantityINCORRECT_ALLOCATED_QUANTITYFIX 4.4
15Unknown account(s)UNKNOWN_ACCOUNTFIX 4.4
99OtherOTHERFIX 4.4

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.

MessageMsgTypeFIX 4.4FIX 4.2Where in the message
ExecutionReport8OptionalOptionaldirectly on the message body
ListStatusNOptionalOptionalinside 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;

Other int fields

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 decoderSource on GitHub