Message AllocationReportAck Scenario base

SYNOPSIS: The Allocation Report Ack message is used to acknowledge the receipt of and provide status for an Allocation Report message.

ID MsgType Abbr Flow
79ATAllocRptAck

Pedigree

Added EP Updated EP Deprecated EP
FIX.4.4

Responses

None

Members

AllocationReportAck base members
ID Name Abbr Presence Description
1024StandardHeaderBaseHeaderrequiredSYNOPSIS: The standard FIX message header
ELABORATION:
755AllocReportIDRptID required SYNOPSIS: Unique identifier for Allocation Report message.
70AllocIDAllocID optional SYNOPSIS: Unique identifier for allocation message. (Prior to FIX 4.1 this field was of type int)
2758AllocRequestIDReqID optional SYNOPSIS: Unique identifier for the request message.
715ClearingBusinessDateBizDt optional SYNOPSIS: The business date for which the trade is expected to be cleared.
819AvgPxIndicatorAvgPxInd optional SYNOPSIS: Average pricing indicator.
53QuantityQty optional SYNOPSIS: Overall/total quantity (e.g. number of shares) (Prior to FIX 4.2 this field was of type int)
71AllocTransTypeTransTyp optional SYNOPSIS: Identifies allocation transaction type *** SOME VALUES HAVE BEEN REPLACED - See "Replaced Features and Supported Approach" ***
1003InstrumentInstrmtoptionalSYNOPSIS: The Instrument component block contains all the fields commonly used to describe a security or instrument. Typically the data elements in this component block are considered the static data of a security, data that may be commonly found in a security master database. The Instrument component block can be used to describe any asset type supported by FIX.
ELABORATION:
1012PartiesPtyoptionalSYNOPSIS: The Parties component block is used to identify and convey information on the entities both central and peripheral to the financial transaction represented by the FIX message containing the Parties Block. The Parties block allows many different types of entites to be expressed through use of the PartyRole field and identifies the source of the PartyID through the the PartyIDSource.
ELABORATION:
793SecondaryAllocIDAllocID2 optional SYNOPSIS: Secondary allocation identifier. Unlike the AllocID (70), this can be shared across a number of allocation instruction or allocation report messages, thereby making it possible to pass an identifier for an original allocation message on multiple messages (e.g. from one party to a second to a third, across cancel and replace messages etc.).
1730AllocGroupIDGrpID optional SYNOPSIS: Intended to be used by a central counterparty to assign an identifier to allocations of trades for the same instrument traded at the same price.
1728FirmGroupIDFirmGrpID optional SYNOPSIS: Firm assigned group allocation entity identifier.
1731AvgPxGroupIDAvgPxGrpID optional SYNOPSIS: Used by submitting firm to group trades being allocated into an average price group. The trades in average price group will be used to calculate an average price for the group.
75TradeDateTrdDt optional SYNOPSIS: Indicates date of trading day. Absence of this field indicates current day (expressed in local time at place of trade).
60TransactTimeTxnTm optional SYNOPSIS: Timestamp when the business transaction represented by the message occurred.
87AllocStatusStat optional SYNOPSIS: Identifies status of allocation.
88AllocRejCodeRejCode optional SYNOPSIS: Identifies reason for rejection.
794AllocReportTypeRptTyp optional SYNOPSIS: Describes the specific type or purpose of an Allocation Report message
808AllocIntermedReqTypeIntermedReqTyp optional SYNOPSIS: Response to allocation to be communicated to a counterparty through an intermediary, i.e. clearing house. Used in conjunction with AllocType = "Request to Intermediary" and AllocReportType = "Request to Intermediary"
573MatchStatusMtchStat optional SYNOPSIS: The status of this trade with respect to matching or comparison.
1031CustOrderHandlingInstCustOrdHdlInst optional SYNOPSIS: Codes that apply special information that the Broker / Dealer needs to report, as specified by the customer. NOTE: This field and its values have no bearing on the ExecInst and TimeInForce fields. These values should not be used instead of ExecInst or TimeInForce. This field and its values are intended for compliance reporting and/or billing purposes only. For OrderHandlingInstSrc(1032) = 1 (FINRA OATS), valid values are (as of OATS Phase 3 as provided by FINRA. See also http://www.finra.org/Industry/Compliance/MarketTransparency/OATS/PhaseIII/index.htm for a complete list. For OrderHandlingInstSrc(1032) = 2 (FIA Execution Source Code), only one enumeration value may be specified.
1032OrderHandlingInstSourceOrdHndlInstSrc optional SYNOPSIS: Identifies the class or source of the order handling instruction values.  Scope of this will apply to both CustOrderHandlingInst(1031) and DeskOrderHandlingInst(1035). Conditionally required when CustOrderHandlingInst(1031) or DeskOrderHandlingInst(1035) is specified.
58TextTxt optional SYNOPSIS: Free format text string (Note: this field does not have a specified maximum length)
354EncodedTextLenEncTxtLen optional SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedText (355) field.
355EncodedTextEncTxt optional SYNOPSIS: Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text(58) field.
1328RejectTextRejTxt optional SYNOPSIS: Identifies the reason for rejection.
1664EncodedRejectTextLenEncRejTxtLen optional SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedRejectText(1665) field.
1665EncodedRejectTextEncRejTxt optional SYNOPSIS: Encoded (non-ASCII characters) representation of the RejectText(1328) field in the encoded format specified via the MessageEncoding(347) field. If used, the ASCII (English) representation should also be specified in the RejectText(1328) field.
2220RegulatoryTradeIDGrpRegTrdIDoptionalSYNOPSIS: The RegulatoryTradeIDGrp is a repeating component within the TradeCaptureReport message used to report the source, value and relationship of multiple identifiers for the same trade or position. This component can be used to meet regulatory trade reporting requirements where identifiers such as the Unique Swaps Identifier (USI) in the US or the Unique Trade Identifier (UTI) in Europe and Canada are required to be reported, showing the chaining of these identifiers as needed.
ELABORATION:
2002AllocAckGrpAllocAckoptionalSYNOPSIS: This repeating group is optionally used for messages with AllocStatus(87) = 2 (Account level reject), to provide details of the individual accounts that were accepted or rejected. In the case of a reject, the reasons for the rejection should be specified.
ELABORATION:
1025StandardTrailerTrlrrequiredSYNOPSIS: The standard FIX message trailer
ELABORATION: