Tag85 is a specific identifier used in the FIX (Financial Information eXchange) protocol, which is a messaging standard widely employed in the financial services industry. Your understanding of this tag can enhance your trading strategies, especially in complex scenarios such as algorithmic trading and high-frequency trading.

The NoDlvyInst FIX tag is utilized to indicate whether a particular message excludes any delivery instructions for the trades or orders it describes. When you set Tag 85, you inform your trading counterparties that there are no additional delivery instructions associated with the transaction. Essentially, it helps streamline communications by signaling that no further details are needed regarding how the trade should be settled or delivered.

In trading, the use of Tag 85 becomes pertinent primarily in the context of messages that deal with order execution and confirmation. For instance, if you are using this tag in an order originally submitted, it reinforces your intention to execute the order without additional delivery concerns such as specific handling requirements or special settlement procedures.

This tag is commonly found in various FIX messages that revolve around the structure of orders and trades. Some prominent FIX messages that may employ Tag 85 include:

  • Execution Report (Message Type 8): This message is typically sent from a broker or exchange to inform you about the execution status of an order. Incorporating Tag 85 helps clarify that no delivery instructions should be attached to the order’s execution.
  • Order Cancel/Replace Request (Message Type 35): When you handle changes to an order, you may use Tag 85 to specify that the revised order does not require any additional delivery instructions.

When using Tag 85, you also have to ensure that your trading platform and the counterparties you engage with are synchronized in understanding and effectively processing this tag. Proper usage facilitates smoother workflows and enhances overall trading efficiency, especially when dealing with a high volume of transactions.

As a final point, you should view Tag 85 (NoDlvyInst) not merely as a technical specification but as an crucial tool to streamline your trading operations. Its application in key messages like Execution Reports and Order Cancel/Replace Requests serves to simplify your interactions and decisions in the market. By understanding and using this tag wisely, you can improve the clarity of your trade communications and ensure seamless execution of your trading practices.

Oh hi there 👋
It’s nice to meet you.

Sign up to get access and receive our gift: FIX Standard introductory book.

We don’t spam! Read our privacy policy for more info.

Explore More

FIX Protocol > FIX tag 52 meaning SendingTime in FIX Standard

Most traders and developers working with the FIX Protocol understand the importance of effectively communicating trading information. One crucial element in this communication is the FIX tag 52, which denotes SendingTime. Understanding FIX tag 52 is fundamental as it plays a pivotal role in the timing of messages transmitted across

FIX Protocol > FIX tag 113 ReportToExch. What is FIX tag 113 ReportToExch in FIX Dictionary? How is it used in trading? What FIX messages use FIX tag 113?

Over the course of your trading journey, understanding the intricacies of the FIX Protocol and its specific tags can significantly enhance your efficiency. One such important component is FIX tag 113, known as ReportToExch. This tag plays a vital role in indicating whether a report is to be sent to

FIX Protocol > FIX tag 42 meaning OrigTime in FIX Standard

You may have encountered the FIX Protocol while working in the world of electronic trading. One of the many tags in this comprehensive messaging standard is FIX tag 42, which stands for OrigTime. Understanding the meaning and application of this tag can enhance your knowledge of how data is transmitted