Friday, 20 November 2026 · Free. No paywall. No subscription.
Search The MidPoint News

Search articles, videos and sections. Press / to open, Esc to close.

FIX 4.2Field

SessionRejectReason <373>

Tag
373
Type
int · code set SessionRejectReasonCodeSet
Pedigree
Added FIX 4.2
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

This page shows SessionRejectReason <373> as defined in FIX 4.2. For the current standard, see tag 373 SessionRejectReason in FIX Latest.

SessionRejectReason <373> in plain English

Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).

SessionRejectReason gives the reason code for a session-level Reject message, such as a missing required tag or an incorrect value.

Common values

ValueNameMeaning (from the Orchestra file)
373=0InvalidTagNumberInvalid tag numberInvalid tag number
373=1RequiredTagMissingRequired tag missingRequired tag missing
373=2TagNotDefinedForThisMessageTypeTag not defined for this message typeTag not defined for this message type
373=3UndefinedTagUndefined TagUndefined Tag
373=4TagSpecifiedWithoutAValueTag specified without a valueTag specified without a value
373=5ValueIsIncorrectValue is incorrect (out of range) for this tagValue is incorrect (out of range) for this tag
373=6IncorrectDataFormatForValueIncorrect data format for valueIncorrect data format for value
373=9CompIDProblemCompID problemCompID problem
373=10SendingTimeAccuracyProblemSendingTime accuracy problemSendingTime accuracy problem
373=11InvalidMsgTypeInvalid MsgTypeInvalid MsgType

A selection. The full list of values is in the table further down.

Where it is used

Reject (35=3) . In all, 1 message in FIX 4.2 can carry it. Full list.

Example message

8=FIX.4.2|9=101|35=3|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|45=7|371=44|372=D|373=5|58=Invalid price|10=176

Illustrative example, not real orders or market data. A Reject (35=3) in FIX 4.2, shown with BeginString FIX.4.2. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.2 dictionary, but it is not a complete specification of the message.

Description (from the Orchestra file)

Code to identify reason for a session-level Reject message.

Values (12)

ValueNameDescriptionPedigreeIn LatestIn 4.4
0 InvalidTagNumberInvalid tag number Invalid tag number Added FIX 4.2 ✓✓
1 RequiredTagMissingRequired tag missing Required tag missing Added FIX 4.2 ✓✓
10 SendingTimeAccuracyProblemSendingTime accuracy problem SendingTime accuracy problem Added FIX 4.2 ✓✓
11 InvalidMsgTypeInvalid MsgType Invalid MsgType Added FIX 4.2 ✓✓
2 TagNotDefinedForThisMessageTypeTag not defined for this message type Tag not defined for this message type Added FIX 4.2 ✓✓
3 UndefinedTagUndefined Tag Undefined Tag Added FIX 4.2 ✓✓
4 TagSpecifiedWithoutAValueTag specified without a value Tag specified without a value Added FIX 4.2 ✓✓
5 ValueIsIncorrectValue is incorrect (out of range) for this tag Value is incorrect (out of range) for this tag Added FIX 4.2 ✓✓
6 IncorrectDataFormatForValueIncorrect data format for value Incorrect data format for value Added FIX 4.2 ✓✓
7 DecryptionProblemDecryption problem Decryption problem Added FIX 4.2 ✓✓
8 SignatureProblemSignature problem Signature problem Added FIX 4.2 ✓✓
9 CompIDProblemCompID problem CompID problem Added FIX 4.2 ✓✓

Used in

Messages (1)

MessageMsgTypePresence
Reject3Optional