Optional second identifier for the allocation report being acknowledged (need not be unique) 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.).

Denotes the status of the allocation report; received (but not yet processed), rejected (at block or account level) or accepted (and processed). AllocStatus will be conditionally required in a 2-party model when used by a counterparty to convey a change in status. It will be optional in a 3-party model in which only the central counterparty may issue the status of an allocation Identifies status of allocation.

Required for AllocStatus = 1 ( block level reject) and for AllocStatus 2 (account level reject) if the individual accounts and reject reasons are not provided in this message Identifies reason for rejection.

Required if AllocReportType = 8 (Request to Intermediary) Indicates status that is requested to be transmitted to counterparty by the intermediary (i.e. clearing house) 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"

Encoded (non-ASCII characters) representation of the Text field in the encoded format specified via the MessageEncoding field. 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 field.

This repeating group is optionally used for messages with AllocStatus = 2 (account level reject), AllocStatus = 0 (accepted), 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. This group should not be populated where AllocStatus has any other value. Indicates number of allocation groups to follow. Number of repeating AllocAccount (79)/AllocPrice (366) entries.

Indicates whether the resulting position after a trade should be an opening position or closing position. Used for omnibus accounting - where accounts are held on a gross basis instead of being netted together.

Encoded (non-ASCII characters) representation of the AllocText field in the encoded format specified via the MessageEncoding field. Encoded (non-ASCII characters) representation of the AllocText (161) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the AllocText field.

Login to FixSpec

FixSpec.com is FREE website helping the financial services community to connect faster and easier. Registered users get access to an awesome range of developer tools and an ever-expanding specification repository.

Cool! Check your inbox for a password reset link. If you don't receive it, then your email may not be in our records so try registering it instead.