To get the full experience of our online specs, you really need to use something a little bigger. Do you mind firing up your tablet or computer please?
|859 - ConfirmReqID ● #||Required String|
Unique identifier for this message Unique identifier for a Confirmation Request message
|773 - ConfirmType ● #||Required int|
Denotes whether this message is being used to request a confirmation or a trade status message Identifies the type of Confirmation message being sent
|73 - NoOrders ● #||Optional NumInGroup|
Indicates number of orders to be combined for average pricing and allocation.
|11 - ClOrdID ● #||Optional String|
Unique identifier for Order as assigned by the buy-side (institution, broker, intermediary etc.) (identified by SenderCompID (49) or OnBehalfOfCompID (5) as appropriate). Uniqueness must be guaranteed within a single trading day. Firms, particularly those which electronically submit multi-day orders, trade globally or throughout market close periods, should ensure uniqueness across days, for example by embedding a date within the ClOrdID field.
|37 - OrderID ● #||Optional String|
Unique identifier for Order as assigned by sell-side (broker, exchange, ECN). Uniqueness must be guaranteed within a single trading day. Firms which accept multi-day orders should consider embedding a date within the OrderID field to assure uniqueness across days.
|198 - SecondaryOrderID ● #||Optional String|
Assigned by the party which accepts the order. Can be used to provide the OrderID (37) used by an exchange or executing system.
|526 - SecondaryClOrdID ● #||Optional String|
Assigned by the party which originates the order. Can be used to provide the ClOrdID (11) used by an exchange or executing system.
|66 - ListID ● #||Optional String|
Unique identifier for list as assigned by institution, used to associate multiple individual orders. Uniqueness must be guaranteed within a single trading day. Firms which generate multi-day orders should consider embedding a date within the ListID field to assure uniqueness across days.
|756 - NoNested2PartyIDs ● #||Optional NumInGroup|
Repeating group below should contain unique combinations of Nested2PartyID, Nested2PartyIDSource, and Nested2PartyRole Number of Nested2PartyID (757), Nested2PartyIDSource (758), and Nested2PartyRole (759) entries
|757 - Nested2PartyID ● #||Optional String|
Used to identify source of Nested2PartyID. Required if Nested2PartyIDSource is specified. Required if NoNested2PartyIDs > 0. PartyID value within a "second instance" Nested repeating group. Same values as PartyID (448)
|758 - Nested2PartyIDSource ● #||Optional char|
Used to identify class source of Nested2PartyID value (e.g. BIC). Required if Nested2PartyID is specified. Required if NoNested2PartyIDs > 0. PartyIDSource value within a "second instance" Nested repeating group. Same values as PartyIDSource (447)
|759 - Nested2PartyRole ● #||Optional int|
Identifies the type of Nested2PartyID (e.g. Executing Broker). Required if NoNested2PartyIDs > 0. PartyRole value within a "second instance" Nested repeating group. Same values as PartyRole (452)
|806 - NoNested2PartySubIDs ● #||Optional NumInGroup|
Number of Nested2PartySubID (760) and Nested2PartySubIDType (807) entries. Second instance of NestedParties.
|760 - Nested2PartySubID ● #||Optional String|
PartySubID value within a "second instance" Nested repeating group. Same values as PartySubID (523)
|807 - Nested2PartySubIDType ● #||Optional int|
Type of Nested2PartySubID (760) value. Second instance of NestedParties. Same values as PartySubIDType (803)
|38 - OrderQty ● #||Optional Qty|
Quantity ordered. This represents the number of shares for equities or par, face or nominal value for FI instruments.
|799 - OrderAvgPx ● #||Optional Price|
Average price for a specific order
|800 - OrderBookingQty ● #||Optional Qty|
Quantity of the order that is being booked out as part of an Allocation Instruction or Allocation Report message
|70 - AllocID ● #||Optional String|
Used to refer to an earlier Allocation Instruction. Unique identifier for allocation message.
|793 - SecondaryAllocID ● #||Optional String|
Used to refer to an earlier Allocation Instruction via its secondary identifier 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.).
|467 - IndividualAllocID ● #||Optional String|
Used to refer to an allocation account within an earlier Allocation Instruction. Unique identifier for a specific NoAllocs (78) repeating group instance (e.g. for an AllocAccount).
|60 - TransactTime ● #||Required UTCTimestamp|
Represents the time this message was generated Time of execution/order creation (expressed in UTC (Universal Time Coordinated, also known as "GMT")
|79 - AllocAccount ● #||Optional String|
Account number for the trade being confirmed by this message Sub-account mnemonic
|661 - AllocAcctIDSource ● #||Optional int|
Used to identify the source of the AllocAccount (79) code. See AcctIDSource (660) for valid values.
|798 - AllocAccountType ● #||Optional int|
Type of account associated with a confirmation or other trade-level message
|58 - Text ● #||Optional String|
Free format text string. Note: this field does not have a specified maximum length
|354 - EncodedTextLen ● #||Optional Length|
Byte length of encoded (non-ASCII characters) EncodedText (355) field.
|355 - EncodedText ● #||Optional data|
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.
Seems this is the only instance of this field in this spec unfortunately.
The field also appears in the following technical messages:
The field also appears in the following functional views:
Want a head start on a new FIX spec using a FIXatdl file?
Import the XML and we'll create a skeleton spec based on the content.
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.
We are so glad you decided to sign up.
We aim to make this website as simple and enjoyable as possible, but if you get stuck at any point or have any suggestions then please get in touch.
Use the "Help" tab on the right, or email us at email@example.com.
To help you find your way around, we've built a short interactive tour of the site.Start the whirlwind tour! (2-3 mins) No thanks, I'll just look around myself.