Orchimate 1.5.0 /
FIX4.2

Indexes
Messages
Components
Groups
Fields
Code Sets
Datatypes
Message Layouts
Session
PreTrade
Trade
PostTrade
Infrastructure
  • Documentation
    • Message

    BusinessMessageReject (j)

    ID43
    PedigreeAdded FIX.4.2

    The Business Message Reject message can reject an application-level message which fulfills session-level rules and cannot be rejected via any other means. Note if the message fails a session-level rule (e.g. body length is incorrect), a session-level Reject message should be issued.

    See the session-level Reject message

    It should NOT be used in the following situations:

    Session-level problem meeting the criteria of the session-level Reject messageUse the session-level Reject message (MsgType=3)
    In response to
    • New Order - Single
    • Order Status Request
    • New Order - List
    • List Execute
    		Use the Execution Report message
    In response to:
    • Order Cancel Request
    • Order Cancel/Replace Request
    • List Cancel Request
    		Use the Order Cancel Reject message
    In response to:
    • Execution Report
    		Use the Don’t Know Trade (DK) message
    In response to:
    • Allocation
    		Use the Allocation ACK message
    In response to:
    • List Status Request
    		Use the List Status message
    In response to:
    • Quote Request
    • Quote
    • Mass Quote
    • Quote Cancel
    • Quote Status Request
    		Use the Quote Acknowledgment message
    In response to:
    • Market Data Request
    		Use the Market Data Request Reject message
    In response to:
    • Security Definition Request
    		Use the Security Definition message
    In response to:
    • Security Status Request
    		Use the Security Status message
    In response to:
    • Trading Session Status Request
    		Use the Trading Session Status message

    Note the only exception to this rule is in the event a business message is received, fulfills session-level rules, however, the message cannot be communicated to the business-level processing system. In this situation a Business Message Reject with BusinessRejectReason = “Application not available at this time” can be issued if the the system is unable to send the specific “reject” message listed above due to this condition.

    Messages which can be referenced via the Business Message Reject message are:

    (the “ID” field BusinessRejectRefID refers to noted in [ ])
    • Indication of Interest (IOI) [IOIid]
    • Advertisement [AdvId]
    • News [Headline]
    • Email [EmailThreadID]
    • Order Cancel Reject [ClOrdID]
    • Allocation ACK [AllocID]
    • List Status [ListID]
    • Don’t Know Trade (DK) – may respond with Order Cancel Reject if attempting to cancel order [ExecID]
    • Settlement Instructions [SettlInstID]
    • Market Data-Snapshot/Full Refresh [MDReqID]
    • Market Data-Incremental Refresh [MDReqID]
    • Market Data Request Reject [MDReqID]
    • Quote Acknowledgment [QuoteID]
    • Security Definition [SecurityResponseID]
    • Security Status [SecurityStatusReqID]
    • Trading Session Status [TradSesReqID]

    Scenarios for Business Message Reject:

    BusinessRejectReason
    0 = Other
    1 = Unknown ID
    2 = Unknown Security
    3 = Unsupported Message Type (receive a valid, but unsupported MsgType)
    4 = Application not available
    5 = Conditionally Required Field Missing

    Whenever possible, it is strongly recommended that the cause of the failure be described in the Text field (e.g. “UNKNOWN SYBMOL: XYZ”).

    Field
    Name
    Type
    Req'd
    Comments
    Pedigree
    StandardHeader
    StandardHeader
    Y
    MsgType = j (lowercase)
    Added FIX.4.2
    45
    RefSeqNum
    int
    MsgSeqNum of rejected message
    Added FIX.4.2
    372
    RefMsgType
    String
    Y
    The MsgType of the FIX message being referenced.
    Added FIX.4.2
    379
    BusinessRejectRefID
    String
    The value of the business-level “ID” field on the message being referenced. Required unless the corresponding ID field (see list above) was not specified.
    Added FIX.4.2
    380
    BusinessRejectReason
    BusinessRejectReasonCodeSet
    Y
    Code to identify reason for a Business Message Reject message.
    Added FIX.4.2
    58
    Text
    String
    Where possible, message to explain reason for rejection
    Added FIX.4.2
    354
    EncodedTextLen
    int
    Must be set if EncodedText field is specified and must immediately precede it.
    Added FIX.4.2
    355
    EncodedText
    data
    Encoded (non-ASCII characters) representation of the Text field in the encoded format specified via the MessageEncoding field.
    Added FIX.4.2
    StandardTrailer
    StandardTrailer
    Y
    Added FIX.4.2

    Orchimate Copyright 2026 Atomic Wire Technology Limited
    Orchestra Copyright 2026 FIX Protocol Ltd
    Terms of Service|Privacy Policy