Reject (3)

The reject message is 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 CheckSum and BodyLength checks.

Behaviour is as described in the FIX Trading Community FIX Session Layer.

Tag	Field Name	Data type	Req’d	Comments
Standard Header			Y	MsgType = 3
45	RefSeqNum	SeqNum	Y	MsgSeqNum of rejected message
371	RefTagID	int		The tag number of the FIX field being referenced. Supplied if the rejection was due to a specific tag.
372	RefMsgType	String		The MsgType (35) of the FIX message being referenced.
373	SessionRejectReason	int		Code to identify reason for a session-level Reject message. Valid values 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 9 = CompID problem 10 = SendingTime Accuracy Problem 11 = Invalid MsgType 12 = XML Validation Error 13 = Tag appears more than once 14 = Tag specified out of required order 15 = Repeating group fields out of order 16 = Incorrect NumInGroup count for repeating group 18 = Invalid/Unsupported Application Version 99 = Other
58	Text	String [unlimited]		Text describing the reason for the rejection. Supplied when SessionRejectReason=Other (373=99).
Standard Trailer			Y