FIX.4.3 (Always unencrypted, must be first field in message)

(Always unencrypted, must be second field in message)

(Always unencrypted, must be third field in message)

(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.

(deprecated)

Used when a message is sent via a "hub" or "service bureau". If A sends to Q (the hub) who then sends to B via a separate FIX session, then when Q sends to B the value of this field should represent the SendingTime on the message A sent to Q. (always expressed in UTC (Universal Time Coordinated, also known as "GMT")

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.

Third party firm which delivered a specific message either from the firm which originated the message or from another third party (if multiple "hops" are performed). It is recommended that this value be the SenderCompID (49) of the third party.

Time that HopCompID (628) sent the message. It is recommended that this value be the SendingTime (52) of the message sent by the third party.

Reference identifier assigned by HopCompID (628) associated with the message sent. It is recommended that this value be the MsgSeqNum (34) of the message sent by the third party.

Repeating group below should contain unique combinations of PartyID, PartyIDSource, and PartyRole

Used to identify source of PartyID. Required if PartyIDSource is specified. Required if NoPartyIDs > 0.

Used to identify class source of PartyID value (e.g. BIC). Required if PartyID is specified. Required if NoPartyIDs > 0.

Identifies the type of PartyID (e.g. Executing Broker). Required if NoPartyIDs > 0.

Sub-identifier (e.g. Clearing Acct for PartyID=Clearing Firm) if applicable

One of CashOrderQty, OrderQty, or (for CIV only) OrderPercent is required. Note that unless otherwise specified, only one of CashOrderQty, OrderQty, or OrderPercent should be specified.

One of CashOrderQty, OrderQty, or (for CIV only) OrderPercent is required. Note that unless otherwise specified, only one of CashOrderQty, OrderQty, or OrderPercent should be specified. Specifies the approximate "monetary quantity" for the order. Broker is responsible for converting and calculating OrderQty in tradeable units (e.g. shares) for subsequent messages.

For CIV - Optional. One of CashOrderQty, OrderQty or (for CIV only) OrderPercent is required. Note that unless otherwise specified, only one of CashOrderQty, OrderQty, or OrderPercent should be specified.

For CIV – Optional

For CIV – Optional

Common, "human understood" representation of the security. SecurityID value can be specified if no symbol exists (e.g. non-exchange traded Collective Investment Vehicles)

Takes precedence in identifying security to counterparty over SecurityAltID block. Requires SecurityIDSource if specified.

Required if SecurityID is specified.

Number of alternate Security Identifiers

Security Alternate identifier for this security

First member of repeating group - must be specified if NoSecurityAltID > 0

The Security Alternative identifier block should not be populated unless SecurityID and SecurityIDSource are populated and should not duplicate the SecurityID and SecurityIDSource values contained in the SecurityID/SecurityIDSource tags. Use of SecurityAltID may be used if bilaterally agreed to assist in security identification, and does not imply an obligation on the receiver of the message to ensure validity or consistency with the SecurityID and SecurityIDSource fields which take precedence.

Source of SecurityAltID. Required if SecurityAltID is specified.

Indicates the type of product the security is associated with (high-level category)

Indicates the type of security using ISO 10962 standard, Classification of Financial Instruments (CFI code) values. It is recommended that CFICode be used instead of SecurityType for non-Fixed Income instruments.

It is recommended that CFICode be used instead of SecurityType for non-Fixed Income instruments.

Futures and Options should be specified using the CFICode[461] field instead of SecurityType[167] (Refer to Volume 7 – Recommendations and Guidelines for Futures and Options Markets.")

Specifies the month and year of maturity. Applicable for standardized derivatives which are typically only referenced by month and year (e.g. S&P futures). Note MaturityDate (a full date) can also be specified.

Specifies date of maturity (a full date). Note that standardized derivatives which are typically only referenced by month and year (e.g. S&P futures).may use MaturityMonthYear and/or this field.

When using MaturityMonthYear, it is recommended that markets and sell sides report the MaturityDate on all outbound messages as a means of data enrichment.

Date interest is to be paid. Used in identifying Corporate Bond issues.

Date instrument was issued. For Fixed Income IOIs for new issues, specifies the issue date.

Identifies the collateral used in the transaction. For Fixed Income, required for RP and RVRP security types.

Number of business days before repurchase of a repo.

Percent of par at which a Repo will be repaid. Represented as a percent, e.g. .9525 represents 95-1/4 percent of par.

Fraction for deriving Current face from Original face for TIPS, ABS or MBS Fixed Income securities. Note the fraction may be greater than, equal to or less than 1.

The location at which records of ownership are maintained for this instrument, and at which ownership changes must be recorded. Can be used in conjunction with ISIN to address ISIN uniqueness issues.

ISO Country code of instrument issue (e.g. the country portion typically used in ISIN). Can be used in conjunction with non-ISIN SecurityID (e.g. CUSIP for Municipal Bonds without ISIN) to provide uniqueness.

A two-character state or province abbreviation.

The three-character IATA code for a locale (e.g. airport code for Municipal Bonds).

Return of investor's principal in a security. Bond redemption can occur before maturity date.

Used for derivatives, such as options and covered warrants

Used for derivatives, such as options and covered warrants to indicate a versioning of the contract when required due to corporate actions to the underlying. Should not be used to indicate type of option – use the CFICode[461] for this purpose.

For Fixed Income, Convertible Bonds, Derivatives, etc. Note: If used, quantities should be expressed in the "nominal" (e.g. contracts vs. shares) amount.

For Fixed Income.

Can be used to identify the security.

Must be set if EncodedIssuer field is specified and must immediately precede it.

Encoded (non-ASCII characters) representation of the Issuer field in the encoded format specified via the MessageEncoding field.

Must be set if EncodedSecurityDesc field is specified and must immediately precede it.

Encoded (non-ASCII characters) representation of the SecurityDesc field in the encoded format specified via the MessageEncoding field.

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)