FIXT.1.1 (Always unencrypted, must be first field in message)

(Always unencrypted, must be second field in message)

(Always unencrypted, must be third field in message)

Indicates application version using a service pack identifier. The ApplVerID applies to a specific message occurrence.

Used to support bilaterally agreed custom functionality

(Always unencrypted)

(Always unencrypted)

Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)

Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)

Required to identify length of encrypted section of message. (Always unencrypted)

Required when message body is encrypted. Always immediately follows SecureDataLen field.

(Can be embedded within encrypted data section.)

(Can be embedded within encrypted data section.)

Sender's LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)

"ADMIN" reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.)

Trading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)

Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)

Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)

Always required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. (Can be embedded within encrypted data section.)

Required when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.)

(Can be embedded within encrypted data section.)

Required for message resent as a result of a ResendRequest. If data is not available set to same value as SendingTime (Can be embedded within encrypted data section.)

Required when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.)

Can contain a XML formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.)

See Volume 1: FIXML Support

Type of message encoding (non-ASCII characters) used in a message's "Encoded" fields. Required if any "Encoding" fields are used.

The last MsgSeqNum value received by the FIX engine and processed by downstream application, such as trading system or order routing system. Can be specified on every message sent. Useful for detecting a backlog with a counterparty.

Number of repeating groups of historical "hop" information. Only applicable if OnBehalfOfCompID is used, however, its use is optional. Note that some market regulations or counterparties may require tracking of message hops.

Identifies the application with which a message is associated. Used only if application sequencing is in effect.

Application sequence number assigned to the message by the application generating the message. Used only if application sequencing is in effect. Conditionally required if ApplID has been specified.

The previous sequence number in the application sequence stream. Permits an application to publish messages with sequence gaps where it cannot be avoided. Used only if application sequencing is in effect. Conditionally required if ApplID has been specified

Used to indicate that a message is being sent in response to an Application Message Request. Used only if application sequencing is in effect. It is possible for both ApplResendFlag and PossDupFlag to be set on the same message if the Sender's cache size is greater than zero and the message is being resent due to a session level resend request.

This block specifies the rules for determining how a security ticks, i.e. the price increments at which it can be quoted and traded, depending on the current price of the security

Specifies the lot types that are valid for trading.

Specifies the price limits that are valid for trading.

The minimum order quantity that can be submitted for an order.

The maximum order quantity that can be submitted for a security. For listed derivatives this indicates the minimum quantity necessary for an order or trade to qualify as a block trade

The maximum price variation of an execution from one event to the next for a given security. Expressed in absolute price terms.

Used when the trading currency can differ from the price currency

Trading lot size of security

Used for multileg security only. Defines whether the security is pre-defined or user-defined. Not that value = 2 (User-defined, Non-Securitized, Multileg) does not apply for Securities.

Used for multileg security only. Defines the method used when applying the multileg price to the legs.

Defines the default Price Type used for trading.

Number of order types

Indicates order types that are valid for the specified market segment.

Number of time in force techniques

Indicates time in force techniques that are valid for the specified market segment

Number of execution instructions

Indicates execution instructions that are valid for the specified market segment

Required when trailer contains signature. Note: Not to be included within SecureData field

Note: Not to be included within SecureData field

(Always unencrypted, always last field in message)