FIX 4.4 : Reject <3> message

Structure | Sample Message | Related Messages


The Reject <3> message should be issued when a message is received but cannot be properly processed due to a session-level rule violation. An example of when a reject may be appropriate would be the receipt of a message with invalid basic data (e.g. MsgType <35>=&) which successfully passes de-encryption, CheckSum <10> and BodyLength <9> checks. As a rule, messages should be forwarded to the trading application for business level rejections whenever possible.

Rejected messages should be logged and the incoming sequence number incremented.

Note: The receiving application should disregard any message that is garbled, cannot be parsed or fails a data integrity check. Processing of the next valid FIX message will cause detection of a sequence gap and a Resend Request <2> will be generated. Logic should be included in the FIX engine to recognize the possible infinite resend loop, which may be encountered in this situation.

Generation and receipt of a Reject <3> message indicates a serious error that may be the result of faulty logic in either the sending or receiving application.

If the sending application chooses to retransmit the rejected message, it should be assigned a new sequence number and sent with PossResend <97>=Y.

Whenever possible, it is strongly recommended that the cause of the failure be described in the Text <58> field (e.g. INVALID DATA - FIELD 35).

If an application-level message received fulfills session-level rules, it should then be processed at a business message-level. If this processing detects a rule violation, a business-level reject should be issued. Many business-level messages have specific "reject" messages, which should be used. All others can be rejected at a business-level via the Business Message Reject <j> message.

Note that in the event a business message is received, fulfills session-level rules, however, the message cannot be communicated to the business-level processing system, a Business Message Reject <j> with BusinessRejectReason <380> = "Application not available at this time" should be issued.

Scenarios for session-level Reject <3>:


Invalid tag number


Required tag missing


Tag not defined for this message type


Undefined Tag


Tag specified without a value


Value is incorrect (out of range) for this tag


Incorrect data format for value


Decryption problem


Signature <89> problem


CompID problem


SendingTime <52> accuracy problem


Invalid MsgType <35>


XML Validation error


Tag appears more than once


Tag specified out of required order


Repeating group fields out of order


Incorrect NumInGroup count for repeating group


Non "data" value includes field delimiter (SOH character)



(Note other session-level rule violations may exist in which case SessionRejectReason <373> of Other may be used and further information may be in Text <58> field.)


Tag Field Name Req'd Comments
<MessageHeader> Y MsgType <35> = 3
45 RefSeqNum Y

MsgSeqNum <34> of rejected message

371 RefTagID N

The tag number of the FIX field being referenced.

372 RefMsgType N

The MsgType <35> of the FIX message being referenced.

373 SessionRejectReason N

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

58 Text N

Where possible, message to explain reason for rejection

354 EncodedTextLen N

Must be set if EncodedText <355> field is specified and must immediately precede it.

355 EncodedText N

Encoded (non-ASCII characters) representation of the Text <58> field in the encoded format specified via the MessageEncoding <347> field.

<MessageTrailer> Y


Sample Message

The '^' character is used to represent SOH character.

8=FIX.4.4^9=134^35=3^49=SellSide^56=BuySide^34=3^52=20190606-10:49:41.672^45=3^58=Invalid Resend Request: BeginSeqNo (5) is greater than expected (2)^10=100^

Related Messages