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
Quote Request <35=R>	Quote Request Reject <35=AG>
Quote <35=S>, Quote Cancel <35=Z>, Quote Status Request <35=a>, Quote Response <35=AJ>	Quote Status Report <35=AI>
Mass Quote <35=i>	Mass 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 Type Request <35=v>	Security Types <35=w>
Security List Request <35=x>	Security List <35=y>
Derivative Security List Request <35=z>	Derivative Security List <35=AA>
Security Status Request <35=e>	Security Status <35=f>
Trading Session Status Request <35=g>	Trading Session Status <35=h>
New Order Single <35=D>, Order Status Request <35=H>, Order Mass Status Request <35=AF>, New Order Cross <35=s>, New Order Multileg <35=AB>, New Order List <35=E>, List Execute <35=L>	Execution Report <35=8>
Order Cancel Request <35=F>, Order Cancel/Replace Request <35=G>, Cross Order Cancel Request <35=u>, Cross Order Cancel/Replace Request <35=t>, Multileg Order Cancel/Replace <35=AC>, List Cancel Request <35=K>	Order Cancel Reject <35=9>
Execution Report <35=8>	Don't Know Trade <35=Q>
Order Mass Cancel Request <35=q>	Order Mass Cancel Report <35=r>
List Status Request <35=M>	List Status <35=N>
Allocation Instruction <35=J>	Allocation Instruction Ack <35=P>
Allocation Report <35=AS>	Allocation Report Ack <35=AT>
Confirmation <35=AK>	Confirmation Ack <35=AU>
Registration Instructions <35=o>	Registration Instructions Response <35=p>
Trade Capture Report Request <35=AD>	Trade Capture Report <35=AE>
Bid Request <35=k>	Bid Response <35=l>
Confirmation Request <35=BH>	Confirmation <35=AK>
Settlement Instruction Request <35=AV>	Settlement Instructions <35=T>
Position Maintenance Request <35=AL>	Position Maintenance Report <35=AM>
Request for Positions <35=AN>	Request for Positions Ack <35=AO>
Collateral Request <35=AX>	Collateral Assignment <35=AY>
Collateral Assignment <35=AY>	Collateral Response <35=AZ>
Collateral Inquiry <35=BB>	Collateral Inquiry Ack <35=BG>

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 Instruction Ack <35=P>	AllocID (70)
Allocation Report Ack <35=AT>	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)
Mass Quote Acknowledgement <35=b>	QuoteID (117)
Security Definition <35=d>	SecurityResponseID (322)
Security Status <35=f>	SecurityStatusReqID (324)
Trading Session Status <35=h>	TradSesReqID (335)
Order Mass Cancel Report <35=r>	OrderID (37)
Security Types <35=w>	SecurityResponseID (322)
Security List <35=y>	SecurityResponseID (322)
Derivative Security List <35=AA>	SecurityResponseID (322)
Quote Request Reject <35=AG>	QuoteReqID (131)
RFQ Request <35=AH>	RFQReqID (644)
Quote Status Report <35=AI>	QuoteID (117)
Registration Instructions Response <35=p>	RegistID (513)
Trade Capture Report <35=AE>	TradeReportID (571)
Confirmation Ack <35=AU>	ConfirmID (664)
Bid Response <35=l>	BidID (390)
List Strike Price <35=m>	ListID (66)
Settlement Instructions <35=T>	SettlInstMsgID (777)
Trade Capture Report Request Ack <35=AQ>	TradeRequestID (568)
Trade Capture Report Ack <35=AR>	TradeReportID (571)
Position Maintenance Report <35=AM>	PosMaintRptID (721)
Request for Positions Ack <35=AO>	PosMaintRptID (721)
Position Report <35=AP>	PosMaintRptID (721)
Assignment Report <35=AW>	AsgnRptID (833)
Collateral Response <35=AZ>	CollRespID (904)
Collateral Inquiry Ack <35=BG>	CollInquiryID (909)

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