The FIX Protocol in Trading

Table of Contents

    The FIX protocol in trading helps an investment manager, broker and trading venue exchange order instructions and reports in a shared language. Understanding that language answers a practical question: has an order merely been received, has some of it traded, or has its remaining quantity actually been canceled? Those are different events, even when they arrive in messages with the same name.

    This guide explains the messages and records behind electronic trading. For choosing order types, understanding spreads and evaluating routing, see trading execution. Here, the focus is how systems communicate what was requested and what happened.

    What Is the FIX Protocol?

    FIX stands for Financial Information eXchange. It is an open financial messaging standard maintained by the FIX Trading Community. Its business definitions cover orders, executions, market data and other parts of the trade lifecycle across multiple asset classes. A FIX message describes a business instruction or event; the standard itself does not match buyers with sellers. [1]

    Receiving an Order Is Different from Filling It

    A broker can acknowledge a valid order while none of its quantity has traded. Likewise, acknowledging a cancellation request does not establish that the order has been canceled. Read the report’s purpose, current order state and quantities together.

    FIX’s business meaning is separate from its technical delivery. Four questions help keep the layers clear:

    • Application: What business message is this, and what do its fields mean?
    • Encoding: How are those fields represented, such as tag/value, FIXML or a supported binary encoding?
    • Session: How do the two systems establish communication, track messages and handle recovery?
    • Transport: How do bytes move between the systems, and what protection is configured?

    Modern FIX standards separate these responsibilities. FIX 5.0 separated the application and session specifications; FIXT is a session profile, while FIXP is a different session standard. A FIX implementation must agree on compatible specifications and capabilities. “Supports FIX” alone does not describe the complete interface. [2]

    Version convention: The tag numbers and event codes below use FIX 4.4 application definitions. The FIX Trading Community also maintains FIX Latest through extension packs. A counterparty’s implementation guide determines the supported subset, extensions and workflows; do not assume that examples from another FIX version can be copied unchanged. [1]

    Key FIX Messages: Requests and Reports

    In tag/value FIX, MsgType(35) identifies the message type. The following messages form a useful starting vocabulary for a single-order workflow. The direction shown is between an order sender and its receiving broker or venue, rather than a rule that every market has the same architecture.

    Selected FIX 4.4 order messages
    Message Typical direction What it communicates
    NewOrderSingle, 35=D Sender to receiver A request to place a new single order.
    ExecutionReport, 35=8 Receiver to sender An acknowledgment, order-state update, fill, rejection or other supported execution-report event.
    OrderCancelRequest, 35=F Sender to receiver A request to cancel an order’s remaining quantity.
    OrderCancelReplaceRequest, 35=G Sender to receiver A request to change an existing order’s parameters.
    OrderCancelReject, 35=9 Receiver to sender A cancellation or replacement request that cannot be honored.

    These definitions come from the versioned message specifications. Crucially, an ExecutionReport is not necessarily a trade. Its name covers several different events. A cancel reject also differs from rejection of the original new order: the change request may fail while the existing order remains active or has already filled. [3] [4] [7] [8]

    Codes are specific to their fields. For example, 35=F identifies an OrderCancelRequest, whereas 150=F identifies a Trade event within an ExecutionReport. The same letter does not mean the same thing in every field.

    How to Read Selected FIX Fields

    A tag identifies a field, and its value supplies the content. For example, 35=D means NewOrderSingle; 38=1000 supplies an order quantity of 1,000 under the example’s share convention. The field’s meaning and allowed values matter more than memorizing every tag.

    Suppose an institution sends a hypothetical day order to buy 1,000 Apple shares with a $185.00 limit. The quantities are shares and the prices are U.S. dollars per share. These are fictional assumptions, not observed Apple prices or a trading recommendation. Selected FIX 4.4 application fields could read:

    Selected fields for the hypothetical Apple request
    Field Value Meaning in this example
    MsgType(35) D NewOrderSingle.
    ClOrdID(11) AAPL-01 The sender’s client-order identifier.
    Side(54) 1 Buy.
    OrderQty(38) 1000 Total requested shares.
    OrdType(40) 2 Limit order.
    Price(44) 185.00 Limit price, not a reported fill price.
    TimeInForce(59) 0 Day/session, subject to the applicable market rules.

    This is a field excerpt, not a complete wire message: instrument identification, timestamps, required framing and other fields are omitted. Readable examples sometimes separate fields with a vertical bar, as in 35=D | 38=1000; actual tag/value encoding uses the Start of Heading control character as its delimiter. [3] [11]

    A FIX Order Lifecycle: Acknowledgment, Fills and Cancellation

    Two fields on an ExecutionReport answer different questions: ExecType(150) explains why the report was sent; OrdStatus(39) describes the current order state. Quantity fields then show the economic result: LastQty(32) is the latest fill quantity, CumQty(14) is cumulative executed quantity and LeavesQty(151) is quantity still open for execution. [4]

    For an ordinary completed order without a pending change, a final fill can be reported with ExecType=F (Trade) and OrdStatus=2 (Filled). An acknowledgment instead uses ExecType=0 (New) in this example. Both are ExecutionReports, but only the trade adds executed shares.

    Continue the hypothetical Apple order. First, 400 shares fill at $184.98. The sender then requests cancellation of the remainder using a new request ID, AAPL-C1, referring to AAPL-01. While the cancellation is pending, another 100 shares fill at $184.99. Finally, the receiver confirms cancellation of the unfilled remainder. Assume no other fills, replacements or corrections.

    Hypothetical receiver reports for a 1,000-share order
    Report event ExecType / OrdStatus Cumulative shares Open shares
    New-order acknowledgment 0 New / 0 New 0 1,000
    400-share fill F Trade / 1 Partially filled 400 600
    Cancel request acknowledged as pending 6 Pending Cancel / 6 Pending Cancel 400 600
    Further 100-share fill F Trade / 6 Pending Cancel 500 500
    Cancellation confirmed 4 Canceled / 4 Canceled 500 0

    The order ends canceled with 500 shares already executed. Cancellation removes the remaining 500 shares from further execution; it does not undo the fills. Before cancellation, 1,000 − 400 = 600 shares remain, then 1,000 − 500 = 500. At the final inactive state, LeavesQty is zero even though CumQty is below the original OrderQty.

    The fourth row also shows why status alone is insufficient. A Trade report can carry Pending Cancel status because that state has precedence while the cancel is outstanding. The FIX order-state specification explicitly illustrates fills during a pending cancellation. Actual interfaces may use fewer intermediate reports, and a cancellation may instead be rejected if the order has already filled. [5]

    The two fills total 400 + 100 = 500 shares. Their gross consideration is 400 × $184.98 + 100 × $184.99 = $92,491, giving an average fill price of $92,491 / 500 = $184.982 per share before charges. The $185.00 order limit was an instruction; it is not the average fill price.

    Order Replacements vs Trade Corrections

    Identifiers connect the records. ClOrdID(11) identifies the sender’s order or change request; OrigClOrdID(41) connects a change request to its predecessor. OrderID(37) is assigned by the receiving sell-side system, while ExecID(17) identifies an execution report within the specified scope. None is interchangeable with a session message sequence number. [4] [7]

    Replacement Quantity Includes Earlier Fills

    For a separate hypothetical Microsoft order, suppose the original quantity is 1,000 shares and 300 have filled. A FIX 4.4 replacement requesting a total OrderQty of 1,200 means 1,200 shares for the order chain, including the earlier 300. If accepted with no intervening fills, the remaining quantity is 1,200 − 300 = 900 shares. It does not request 1,200 additional shares. [8]

    Submitting the replacement does not establish acceptance. The receiver can report a pending replacement, accept the change or reject it. Whether a change is permitted and whether it affects queue priority are venue-specific questions; the common message format does not settle them.

    A trade correction or trade cancellation concerns an execution already reported. In FIX 4.4, ExecType G means Trade Correct and H means Trade Cancel. ExecRefID(19) links these reports to the execution being changed. This is different from an OrderCancelRequest, which concerns unexecuted quantity. [4]

    In a separate scenario, a price correction to an Apple fill changes the affected trade record and potentially the average price and cash amount. Receiving another report does not mean another purchase occurred. A trade bust can also change executed quantity; the resulting order treatment must follow the applicable workflow rather than a blanket assumption that every busted trade reopens an order.

    Session Sequencing and Recovery Are Separate from Order State

    In the classic FIX session, MsgSeqNum(34) tracks message sequence. If an incoming stream advances from 102 to 105, the missing numbers are 103 and 104: two messages, not necessarily two trades. A ResendRequest(35=2) requests recovery; retransmissions use their original sequence numbers and PossDupFlag(43)=Y. Permitted skipped messages can be covered by a gap fill. These are session mechanics, not new order instructions. [6]

    Heartbeats and test requests assess session responsiveness. They do not establish that an order was accepted or filled. Application-level duplicate detection is also necessary: a new sequence number alone does not establish a new economic event. Losing a connection does not universally cancel working orders; disconnect behavior belongs to the venue or counterparty’s application rules. [6]

    After an interruption, the practical task is to reconcile known requests, reports, current orders and positions through the agreed recovery process. Sending a fresh order merely because an acknowledgment is missing can create unintended additional exposure. Recovery procedures need to resolve uncertainty about the earlier request first.

    Drop Copies, OMS, EMS and Transaction Cost Analysis

    A drop copy supplies another recipient with copies of specified order or trade reports. It can support monitoring, reconciliation and risk controls without relying solely on the trading application’s display. The precise events, accounts, identifiers and recovery coverage depend on the service.

    For a concrete U.S. market example, CME Group’s Drop Copy distributes copies of Globex execution reports and acknowledgments, including trade-bust messages, through a FIX-based interface. CME expressly describes that service as read-only: it does not support order entry or cancellation. Those are CME service characteristics, not a promise that every drop-copy implementation works identically. [9]

    If the trading connection and a drop-copy feed both report the same 400-share fill, the position does not become 800 shares. Reconciliation must identify the underlying event across the relevant source, account and order identifiers, then apply any corrections. A missing or delayed copy also needs investigation; an additional receipt path does not guarantee a complete, independent record under every failure.

    Where OMS and EMS Fit

    In a typical institutional workflow, an order management system (OMS) organizes investment orders, their ownership and lifecycle records. An execution management system (EMS) helps the trading desk work those orders and interact with execution destinations. Products can combine these functions, so the labels describe roles rather than mandatory separate boxes.

    FIX can carry instructions and reports between these systems and brokers or venues. The portfolio manager’s parent order may produce several working orders and fills. Keeping their relationships intact helps explain which investment decision each execution belongs to. Proof Trading’s market-structure primer illustrates these OMS/EMS roles and their overlap. Monitoring this chain is one part of operational risk management. [12]

    What FIX Records Contribute to TCA

    Transaction cost analysis (TCA) can use order and execution identifiers, quantities, prices and transaction timestamps to reconstruct activity. But execution reports alone may omit the original investment-decision time, benchmark market data, unexecuted intentions or complete charges. Comparing the order’s results with a benchmark requires those additional inputs and consistent definitions.

    A report’s sending time and its transaction time also answer different questions: when the message was sent and when the represented event occurred. A copy’s arrival time adds another clock. Treating them as interchangeable can distort an analysis. For cost measurement and the treatment of unfilled shares, use the dedicated implementation shortfall guide. CFA Institute likewise treats trade-cost measurement and execution evaluation as distinct analytical tasks. [4] [10]

    FIX vs APIs, Market Data Feeds and Trading Venues

    These terms overlap in real systems, but describe different things. A broker can expose a FIX interface as one of its APIs, and FIX can carry market-data messages as well as orders.

    What each term describes
    Term Main role What to establish separately
    FIX Standardized trading-message meanings and workflows. Version, supported fields, session, encoding and counterparty rules.
    API A software interface offered by a system. Its functions, permissions, format and operating requirements.
    Market data feed Delivery of quotes, trades or other market information. Coverage, timeliness, licenses and whether order entry is separately available.
    Trading venue A market where trading takes place under its rules. Access, instruments, matching rules and accepted order instructions.

    A data subscription therefore does not establish FIX order access, and a FIX connection does not establish permission to trade every instrument. For example, short selling involves requirements beyond transmitting a sell-side instruction. Interfaces for futures contracts also require instrument and quantity conventions appropriate to contracts rather than this article’s cash-equity shares.

    How to Evaluate a FIX Workflow

    1. Identify the business relationship. Establish who submits orders, who accepts them, who executes them and who receives monitoring copies.
    2. Read the agreed specification. Confirm application version, supported messages, required fields, identifier scope, units and any extensions.
    3. Trace an order through exceptions. Include a partial fill, rejected change request, fill during pending cancellation and later correction, where supported.
    4. Separate recovery from business decisions. Establish how message gaps, unknown order outcomes and duplicate reports are reconciled.
    5. Connect records to the intended analysis. Match fills and unfilled quantities to parent orders and benchmarks before drawing conclusions about execution quality.

    For an equity-futures workflow, that last step also requires the appropriate contract definition and exposure units. A familiar underlying index or ticker is insufficient to make unlike order records directly comparable.

    Common Mistakes

    • Counting every ExecutionReport as a fill. Check its event type, quantities and references before updating holdings.
    • Treating Pending Cancel as Canceled. Fills can still occur before the cancellation is confirmed.
    • Assuming zero open quantity means fully filled. A canceled or rejected order can have zero LeavesQty with little or no executed quantity.
    • Adding cumulative quantities across reports. CumQty is a running total for the order chain, not each message’s incremental fill.
    • Confusing session numbers with trade identifiers. Message sequencing and economic-event reconciliation solve different problems.
    • Double-counting drop copies or corrections. Multiple reports can describe the same underlying execution.
    • Mixing FIX versions or venue rules. A valid field or event in one guide need not be supported in another interface.

    Limitations of FIX

    A Communication Standard Does Not Guarantee an Investment Outcome

    FIX does not guarantee liquidity, a fill, a favorable price, best execution or successful settlement. It also does not replace permissions, risk controls, reconciliation or operational procedures. A correctly delivered message can still contain an instruction the receiver rejects.

    Standardization reduces ambiguity only when both parties agree on what they implement. Asset-specific conventions, optional fields, extensions and venue workflows still matter. An incomplete identifier mapping can produce incorrect positions even when the messages are syntactically valid.

    Security also requires explicit design and configuration. FIXS defines the use of TLS for protecting FIX sessions; the word “FIX” alone does not establish encryption, authentication quality or protection of stored logs. This article explains message interpretation, not how to configure a secure trading gateway. [2]

    Frequently Asked Questions

    A FIX interface can be one API a broker or venue offers. FIX supplies standardized message meanings and workflows; the provider determines the functions, permissions and supported implementation. A REST API or market-data subscription does not automatically include a FIX order interface.

    No. It may acknowledge a new order, report a fill, reject an order or communicate another supported event. In the FIX 4.4 examples, ExecType identifies the report’s purpose, OrdStatus describes the current state, and the quantity fields show how much has executed and remains open.

    Yes. Pending Cancel acknowledges an outstanding request; it does not establish completed cancellation. A later fill can increase cumulative executed quantity before the remaining quantity is canceled. If the order completes first, the cancellation request may be rejected.

    It supplies copies of specified reports for another recipient’s monitoring or reconciliation. Supported events and coverage depend on the service. Copies represent existing activity rather than extra trades; CME’s cited Drop Copy service is read-only and cannot submit or cancel orders.

    No. Tag/value is a familiar encoding, but the FIX family separates business semantics from encoding, session and transport. Other standards and mappings support different representations. The actual combination must be supported and agreed by both parties, including its security requirements.

    Sources

    1. FIX Trading Community: The FIX Protocol. Application scope, layered business semantics and supported versions.
    2. FIX Trading Community: Technical Standards. Encoding, session and transport standards, including FIXT, FIXP and FIXS.
    3. FIX Trading specification: FIX 4.4 NewOrderSingle, with Side, OrdType and TimeInForce code sets. Online repository reached through FIXimate’s current redirect.
    4. FIX Trading specification: FIX 4.4 ExecutionReport, with ExecType and OrdStatus code sets.
    5. FIX Trading Community: Order State Changes, FIX Latest as of EP284, November 2023. Introduction, precedence and cancellation scenarios, especially B.1.b and B.1.c.
    6. FIX Trading Community: FIX Session Layer, June 2020 technical standard. Session recovery and application-duplicate distinctions; sections 4.6, 4.8 and 4.9.
    7. FIX Trading specification: FIX 4.4 OrderCancelRequest and OrderCancelReject.
    8. FIX Trading specification: FIX 4.4 OrderCancelReplaceRequest. Replacement identifiers and total-intended-quantity convention.
    9. CME Group: FAQ, Drop Copy. Service-specific monitoring, copied messages and read-only restrictions.
    10. CFA Institute: Trade Strategy and Execution, 2026 public refresher reading. Public introduction, learning outcomes and summary on implementation and execution evaluation.
    11. FIX Trading Community: FIX Tagvalue Encoding Standard overview. Tag/value serialization and the SOH delimiter.
    12. Proof Trading: Market Structure Primer, Mechanisms of Communication between Participants. October 1, 2022 PDF; OMS/EMS discussion on PDF pages 5–6. Used for functional roles, not current vendor assessments or market-rule claims.

    Sources accessed November 14, 2026. Examples are hypothetical, use selected FIX 4.4 fields and do not replace a counterparty’s current implementation guide. The EP284 document is cited by its specific version, not as the newest extension pack.

    Disclaimer

    This article is for educational and informational purposes only and does not constitute investment advice or instructions to connect to a trading system. Its fictional orders are not recommendations. Actual access, supported messages, execution outcomes and recovery procedures depend on the provider, market rules and agreed implementation.