| ID | 4 |
| Pedigree | Added FIX.2.7, Updated FIX.4.2 |
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=&) which successfully passes de-encryption, CheckSum and BodyLength 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 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.
Whenever possible, it is strongly recommended that the cause of the failure be described in the Text 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 message. See the Business Message Reject 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 with BusinessRejectReason = “Application not available at this time” should be issued.
Scenarios for session-level Reject:
SessionRejectReason |
|---|
| 0 = Invalid tag number |
| 1 = Required tag missing |
| 2 = Tag not defined for this message type |
| 3 = Undefined Tag |
| 4 = Tag specified without a value |
| 5 = Value is incorrect (out of range) for this tag |
| 6 = Incorrect data format for value |
| 7 = Decryption problem |
| 8 = Signature problem |
| 9 = CompID problem |
| 10 = SendingTime accuracy problem |
| 11 = Invalid MsgType |
| (Note other session-level rule violations may exist in which case SessionRejectReason is not specified) |
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
StandardHeader | Y | MsgType = 3 | Added FIX.2.7 | ||
45 | Y | MsgSeqNum of rejected message | Added FIX.2.7 Updated FIX.4.0 | ||
371 | The tag number of the FIX field being referenced. | Added FIX.4.2 | |||
372 | The MsgType of the FIX message being referenced. | Added FIX.4.2 | |||
373 | Code to identify reason for a session-level Reject message. | Added FIX.4.2 | |||
58 | Where possible, message to explain reason for rejection | Added FIX.2.7 | |||
354 | Must be set if EncodedText field is specified and must immediately precede it. | Added FIX.4.2 | |||
355 | Encoded (non-ASCII characters) representation of the Text field in the encoded format specified via the MessageEncoding field. | Added FIX.4.2 | |||
StandardTrailer | Y | Added FIX.2.7 |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Service|Privacy Policy