| ID | 19 |
| Pedigree | Added FIX.2.7, Updated FIX.4.0 |
The allocation record is used to instruct a broker on how to allocate executed shares to sub-accounts. The allocation record can also be used as a confirmation message through which third parties can communicate execution and settlement instructions between trading partners.
An allocation message can be submitted as new, cancel or replace. The AllocTransType field indicates the purpose of the message. When submitting replace or cancel AllocTransType messages the RefAllocID field is required. Replacement allocation messages must contain all data for the replacement allocation.
The allocation record contains repeating fields for each order, sub-account and individual execution; the repeating fields are shown below in typeface Bold-Italic. The relative position of the repeating fields is important in this record, i.e. each instance of allocation must be in the order shown below.
- The total shares allocated must equal the
Sharesvalue which must equal the total executed quantity of the original order. If present, the total shares in the execution section must also be equal to this value. - The number of sub-account instances is indicated in
NoAllocs. - Multiple orders can be combined for allocation by identifying the number of orders in the
NoOrdersfield and each individual order in theOrderIDfields. Combined orders must have the same ticker, trade date, settlement date and side.
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
StandardHeader | Y | MsgType = J | Added FIX.2.7 | ||
70 | Y | Added FIX.2.7 | |||
71 | Y | Added FIX.2.7 | |||
72 | Required for AllocTransType = R (Replace) or C (Cancel) | Added FIX.2.7 | |||
OrdAllocGrp | Y | Indicates number of orders to be combined for allocation. If order(s) were manually delivered set to 1 (one). | Added FIX.2.7 Updated FIX.4.0 | ||
ExecAllocGrp | Indicates number of individual execution record groups to follow. Absence of this field indicates that no individual execution records are included. | Added FIX.4.0 | |||
54 | Y | Added FIX.2.7 | |||
55 | Y | Added FIX.2.7 | |||
65 | Added FIX.2.7 | ||||
48 | Added FIX.2.7 | ||||
22 | Added FIX.2.7 | ||||
106 | Added FIX.3.0 | ||||
107 | Added FIX.3.0 | ||||
53 | Y | Total number of shares allocated to all accounts | Added FIX.2.7 Updated FIX.4.0 | ||
6 | Y | Added FIX.2.7 | |||
15 | Currency of AvgPx, absence of this field indicates US dollars | Added FIX.4.0 | |||
74 | Absence of this field indicates that default precision arranged by the broker/institution is to be used | Added FIX.2.7 Updated FIX.4.0 | |||
75 | Y | Added FIX.2.7 Updated FIX.4.0 | |||
60 | Date/time when allocation is generated | Added FIX.4.0 | |||
63 | Absence of this field is interpreted as Regular | Added FIX.2.7 Updated FIX.4.0 | |||
64 | Required with SettlmntTyp other than regular | Added FIX.4.0 | |||
118 | Expressed in same currency as AvgPx | Added FIX.4.0 | |||
MiscFeesGrp | Required if any miscellaneous fees are reported. Indicates number of repeating entries | Added FIX.4.0 | |||
119 | Added FIX.4.0 | ||||
120 | Added FIX.4.0 | ||||
77 | Added FIX.2.7 | ||||
58 | Added FIX.2.7 | ||||
AllocGrp | Y | Indicates number of allocation groups to follow. | Added FIX.2.7 Updated FIX.4.0 | ||
StandardTrailer | Y | Added FIX.2.7 |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Service|Privacy Policy