Allocations and giveups

MESSAGE SPECIFICATION

Allocation Instruction (MsgType = J)

The Allocation Instruction message provides the ability to specify how an order should be subdivided amongst one or more accounts. To subdivided a order it may be create in a “to confirm” account.
Currently used:

By the client to request the allocation of the order to other of the broker accounts.
By the client to request the giveup of the order to another account from a different broker.

Tag	FixName	Req	Valid Values	Data Type	Description
Standard Header
6	AvgPx	N		Price	Calculated average price of all fills on this order.
53	Quantity	Y		Qty	Total quantity allocated to all accounts, or that is Ready-To-Book.
54	Side	Y	1 = Buy 2 = Sell	Char	Side of order.
55	Symbol	Y		String	Instrument symbol Name.
207	SecurityExchange	Y		String	Security exchange identifier. Value defined ROFX.
58	Text	N	“Allocation” “Giveup”	String	Free format text string.
70	AllocID	Y		String	Unique ID for this message.
71	AllocTransType	Y	0 = New	Char	Identifies allocation transaction type.
75	TradeDate	Y		LocalMktDate	Indicates date of trade referenced.
626	AllocType	Y	1 = Calculated	Int	Specifies the purpose or type of Allocation message.
754	AutoAcceptIndicator	Y	N = No	Boolean	Indicates if Allocation has been automatically accepted on behalf of the Carry Firm by the Clearing House.
828	TrdType	Y	1001 = Allocation 1002 = Give Up	Int	Specifies trade type when a trade is being reported.
857	AllocNoOrdersType	N	1 = ExplicitListProvided	Int	Indicates how the orders being booked and allocated by this message are identified, i.e. by explicit definition in the NoOrders group or not.
Block OrdAllocGrp		Y			Insert here the block defined in Block OrdAllocGrp In this case NoOrders(11) must be 1 and the tag OrderID(37) is not required.
Block AllocGrp		Y			Set of blocks defined in Block AllocGrp
Standard Trailer

AllocationInstructionAck (MsgType = P)

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

Currently used:

By the exchange to rejects “allocations” and “giveups”.
By the exchange to report of “giveups” requests pending confirmation.

Tag	FixName	Req	Valid Values	Data Type	Description
Standard Header
58	Text	N		String	In case of AllocStatus (87) = 3 the text message will be “Pendiente de confirmar” If AllocStatus (87) = 2 the text message could be other.
60	TransactTime	N		UTCTimestamp	Date/Time AllocationInstructionAck generated.
70	AllocID	Y		String	Unique ID for this message
87	AllocStatus	Y	1 = Block Level Reject 2 = Account Level Reject 3 = Received	Int	Identifies status of allocation. Block Level Reject (1) => used for entire Allocation Instruction message rejection. In this case the request could not be processed. Account Level Reject (2) => is used when the block level matches successfully but one or more (or all) of the constituent account level details failed validation (e.g. “Las cuentas deben ser del mismo agente”) Received (3) => used to inform that there is an allocation pending of confirmation.
Standard Trailer

Confirmation (MsgType = AK): Giveups

The Confirmation messages are used to provide individual trade level confirmations from the sell side to the buy side. Unlike the allocation message, the confirmation message operates at an allocation account (trade) level rather than block level, allowing for the affirmation or rejection of individual confirmations.

Currently used:

By the exchange to request confirmation from the giveup counterparty
By the exchange to report the confirmation, refuse or time out of a giveUp confirmation

Tag	FixName	Req	Valid Values	Data Type	Description
Standard Header
6	AvgPx	Y		Price	Calculated average price of all fills on this order.
54	Side	Y	1 = Buy 2 = Sell	Char	Side of order
55	Symbol	Y		String	Instrument symbol Name.
207	SecurityExchange	Y		String	Security exchange identifier. Value defined ROFX.
58	Text	N		String	Text string: “Confirmada”: used for allocation confirmation “Cancelada por el usuario” : used for user refused giveup “Ejecutada” : used for user accepted giveup “Time-out”: used to indicate timeout reached for giveup confirmation
60	TransactTime	Y		UTCTimestamp	Timestamp when the business transaction represented by the message occurred.
70	AllocID	Y		String	Used to refer to an earlier Allocation Instruction via its secondary identifier.
75	TradeDate	Y		LocalMktDate	Indicates date of trade referenced in this message in YYYYMMDD format.
79	AllocAccount	Y		String	Account number for the trade being confirmed by this message
80	AllocQty	Y		Qty	Quantity to be allocated to specific sub-account.
118	NetMoney	Y	0	Amt	Total amount due as the result of the transaction (e.g. for Buy order - principal + commission + fees) reported in currency of execution.
381	GrossTradeAmt	Y	0	Amt	Total amount traded expressed in units of currency. AllocQty(80) * AvgPx(6)
555	NoLegs	N	0		InstrumentLeg repeating group instances (From InstrmtLegGrp).
664	ConfirmID	Y		String	ID for this message. ”1” in case ConfirmStatus(665) is not “1”
665	ConfirmStatus	Y	1 = Received 4 = Confirmed 5 = RequestRejected	Int	Identifies the status of the Confirmation. Received (1) → Use when exchange request confirmation from the giveup counterparty Confirmed (4) → Use to report the confirmation RequestRejected (5) → Use to report refuse or time out of a giveUp confirmation
666	ConfirmTransType	Y	0 = New 2 = Cancel	Int	Identifies the Confirmation transaction type.
772	ConfirmRefID	C		String	Reference identifier to be used with ConfirmTransType (666) = Replace or Cancel
773	ConfirmType	Y	2 = Confirmation 3 = ConfirmationRequestRejected	Int	Identifies the type of Confirmation message being sent. ConfirmType (2) → for giveup confirmed. ConfirmType (3) → for user refused giveup.
793	SecondaryAllocID	N		String	Secondary allocation identifier. In this case the correspond to the client AllocID (70).
828	TrdType	Y	1001 = Allocation 1002 = Give Up	Int	Type of Trade.
861	ReportedPx	N