This message can be used to reject an application-level message which fulfills session-level rules and cannot be rejected via any other means. If the message fails a session-level rule, e.g. body length is incorrect, a session-level Reject <35=3> message should be issued.

The only exception to this rule is when the FIX session protocol is not being used. An appropriate reject message of the given session protocol or the Business Message Reject message should be used instead.

It should not be used in the following situations:

In response to	Appropriate Response
A session-level problem meeting the criteria of the session-level Reject <35=3> message	Reject <35=3> message
Order Single <35=D>, Order Status Request <35=H>, New Order List <35=E>, List Execute <35=L>	Execution Report <35=8>
Order Cancel Request <35=F>, Order Cancel/Replace Request <35=G>, List Cancel Request <35=K>	Order Cancel Reject <35=9>
Execution Report <35=8>	Don't Know Trade <35=Q>
Allocation <35=J>	Allocation Ack <35=P>
List Status Request <35=M>	List Status <35=N>
Quote Request <35=R>, Quote <35=S>, Mass Quote <35=i>, Quote Cancel <35=Z>, Quote Status Request <35=a>	Quote Acknowledgement <35=b>
Market Data Request <35=V>	Market Data Request Reject <35=Y>
Security Definition Request <35=c>	Security Definition <35=d>
Security Status Request <35=e>	Security Status <35=f>
Trading Session Status Request <35=g>	Trading Session Status <35=h>
Bid Request <35=k>	Bid Response <35=l>

The only exceptions to this rule are:

1. In the event a business message is received, fulfills session-level rules, but cannot be communicated to the business-level processing system. In this situation a Business Message Reject with BusinessRejectReason (380) = "Application not available at this time" can be issued
2. In the event a valid business message is received, fulfills session-level rules, but contains a message type that's not supported by the recipient. In this situation a Business Message Reject with BusinessRejectReason (380) = "Unsupported Message Type" can be issued
3. In the event a business message is received, fulfills session-level rules, but lacks a field conditionally required by the FIX specification. In this situation a Business Message Reject with BusinessRejectReason (380) = "Conditionally Required Field Missing" can be issued

Messages which can be referenced within a Business Message Reject message are as follows. The ID field which BusinessRejectRefID (379) refers to is also noted:

Message	BusinessRejectRefID
Indication of Interest <35=6>	IOIid (23)
Advertisement <35=7>	AdvId (2)
News <35=B>	Headline (148)
Email <35=C>	EmailThreadID (164)
Order Cancel Reject <35=9>	ClOrdID (11)
Allocation Ack <35=P>	AllocID (70)
List Status <35=N>	ListID (66)
Don't Know Trade <35=Q>	ExecID (17)
Settlement Instructions <35=T>	SettlInstID (162)
Market Data Snapshot Full Refresh <35=W>	MDReqID (262)
Market Data Incremental Refresh <35=X>	MDReqID (262)
Market Data Request Reject <35=Y>	MDReqID (262)
Security Definition <35=d>	SecurityResponseID (322)
Security Status <35=f>	SecurityStatusReqID (324)
Trading Session Status <35=h>	TradSesReqID (335)
Bid Response <35=l>	BidID (390)

Whenever possible, it is strongly recommended that the cause of the failure be described in the Text (58) field.