The Reject 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 ResendRequest (35=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 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 BusinessMessageReject <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 BusinessMessageReject <j> with BusinessRejectReason <380> = "Application not available at this time" should be issued.
Scenarios for session-level Reject (35=3):
|Component Block - <StandardHeader>||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 of the FIX message being referenced.|
|1130||RefApplVerID||N||Recommended when rejecting an application message that does not explicitly provide ApplVerID <1128> on the message being rejected. In this case the value from the DefaultApplVerID <1137> or the default value specified in the NoMsgTypes <384> repeating group on the logon message should be provided.|
|1406||RefApplExtID||N||Recommended when rejecting an application message that does not explicitly provide ApplExtID <1156> on the rejected message. In this case the value from the DefaultApplExtID <1407> or the default value specified in the NoMsgTypes <384> repeating group on the logon message should be provided.|
|1131||RefCstmApplVerID||N||Recommended when rejecting an application message that does not explicitly provide CstmApplVerID <1129> on the message being rejected. In this case the value from the DefaultCstmApplVerID <1408> or the default value specified in the NoMsgTypes <384> repeating group on the logon message should be provided.|
|373||SessionRejectReason||N||Code to identify reason for a session-level Reject 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.|
|Component Block - <StandardTrailer>||Y|
^ character is used to represent
8=FIXT.1.1^9=141^35=3^49=SellSide^56=BuySide^34=4^52=20190606-10:22:07.617^1128=9^45=5^58=Invalid Resend Request: BeginSeqNo (5) is greater than expected (3)^10=239^