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?
|109 - ClientID ● #||Optional String|
Used for firm identification in third-party transactions (should not be a substitute for OnBehalfOfCompID/DeliverToCompID). Firm identifier used in third party-transactions (should not be a substitute for OnBehalfOfCompID/DeliverToCompID).
|76 - ExecBroker ● #||Optional String|
Used for firm identification in third-party transactions (should not be a substitute for OnBehalfOfCompID/DeliverToCompID). Identifies executing / give-up broker. Standard NASD market-maker mnemonic is preferred.
|70 - AllocID ● #||Required String|
Unique identifier for allocation message.
|75 - TradeDate ● #||Required LocalMktDate|
Indicates date of trade referenced in this message in YYYYMMDD format. Absence of this field indicates current day (expressed in local time at place of trade).
|60 - TransactTime ● #||Optional UTCTimestamp|
Date/Time AllocationACK generated Time of execution/order creation (expressed in UTC (Universal Time Coordinated, also known as "GMT")
|87 - AllocStatus ● #||Required int|
Identifies status of allocation.
|88 - AllocRejCode ● #||Optional int|
Required for AllocStatus = 1 (rejected) Identifies reason for rejection.
|58 - Text ● #||Optional String|
Can include explanation for AllocRejCode = 7 (other) Free format text string. Note: this field does not have a specified maximum length
|354 - EncodedTextLen ● #||Optional Length|
Must be set if EncodedText field is specified and must immediately precede it. Byte length of encoded (non-ASCII characters) EncodedText field.
|355 - EncodedText ● #||Optional data|
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 field in the encoded format specified via the MessageEncoding 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 firstname.lastname@example.org.
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.