Patent Grant
7640208
The present invention relates to processing low notional value orders for securities.
In certain circumstances, a client of a securities trading firm may want to place stock orders that are of a low notional value. Traders are often unable to add value to such orders, but are required to execute them nonetheless. In addition, prior art systems are manual, thereby creating even greater inefficiency in requiring traders to work on such orders manually.
The present invention is directed to a system and method for processing an order to trade securities. One or more tiers are established. The tiers represent a range of values associated with a trade size and a percentage of an average daily volume of trading in a security. Each of one or more of the tiers is associated with a price improvement. An order to trade in the security is received. The order is associated with an order size. The tier within which the order falls is determined based on the order size and the average daily volume. At least a portion of the order is automatically executed with the price improvement associated with the determined tier.
The present invention is further directed to a system and method for processing an order to trade securities. An order to trade securities is received. The order is associated with an indication. Based on the indication, the order is processed in accordance with one of a plurality of workflows. In accordance with at least one of the plurality of workflows, at least a portion of the order is automatically executed with a price improvement if the order meets one or more eligibility requirements, or is processed manually if the order fails to meet the eligibility requirements. In accordance with at least one other of the plurality of workflows, the order is returned unfilled if it fails to meet the eligibility requirements.
The present invention is still further directed to a method and system for processing orders to trade securities. One or more tiers are established. The tiers represent a range of values associated with a trade size and a percentage of an average daily volume of trading a security. Each of the one or more of the tiers is associated with a price improvement. An order to trade in the security is received. The order is associated with an order size and an indication. The tier within which the order falls is determined based on the order size and the average daily volume. Based on the indication, the order is processed in accordance with one of a plurality of workflows. In accordance with at least one of the plurality of workflows, a portion of the order, up to the size associated with the determined tier, is automatically executed with the price improvement associated with the determined tier if the order meets one or more eligibility requirements, and a residual of the order exceeding the size associated with the determined tier is processed manually. In accordance with at least one other of the plurality of workflows, the residual of the order exceeding the size associated with the determined tier is returned unfilled.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.
The accompanying drawings, which are included to provide further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention.
In the drawings:
Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings.
The present invention provides an efficient manner of executing securities trades, particularly those of low notional value. In particular, clients receive a price improvement on the fill and receive a guaranteed execution if the notional value is smaller than a certain threshold. By automating this order flow, the firm can provide a better execution to the client in the form of a price improvement. In the preferred embodiment, automatic execution is offered on low notional value orders without requiring the client to select the offering explicitly. The system supports multiple asset classes (i.e., equities and equity derivatives), as well as synthetics. The DTC system is risk-based meaning that orders (meeting the appropriate criteria) are automatically executed with a guaranteed price improvement, regardless of the state of the market, and the firm takes on any non natural trades as risk.
The way in which the order management system 300 handles such orders is determined based on the way in which the order is flagged. In particular, the client can flag the order identifying the intended execution service—Direct to Capital (“DTC”) or Auto-execute or Kill (“DTK”) described in more detail below. Orders may be flagged by the client using a customization of the FIX protocol described below, or phone orders may be flagged manually by the Sales Trader.
Flagged orders, if authorized (i.e., if the client is enabled to use the DTC system) are processed by the DTC engine 400. Orders flagged for the DTC execution channel are executed with a price improvement as per the client's entitlements (e.g., in accordance with the tiers described below). If the order does not meet the necessary criteria (e.g., the order supersedes the agreed consideration), the order is sent to the Sales Trader to be executed as a typical worked order. Orders flagged for the DTK execution channel are processed in a manner that is identical to that of DTC, except that orders with a DTK flag will be returned to the client, unfilled, if they are rejected by the auto-execution service. DTK provides the client with an anonymous trading channel, if desired.
A client can be set to one of three states regarding whether a trade will be executed automatically: On, Off or Explicit. If the automatic state is set to “On” for a given client, any order that is received for that client (i.e., through FIX or as a phone order), even if the order is not flagged, is processed using the DTC engine as if it were flagged DTC. “Explicit” refers to flagged orders. For clients in the “Explicit” state, only orders carrying a special DTC or DTK flag will be checked for auto-execution. If this flag is missing, the order will not get checked against the auto-execution service. Within the “Explicit” routing option, there are two scenarios that are supported via the FIX protocol, as shown in Tables 1 and 2. These tables represent one way in which the FIX protocol could be altered in order to process orders received via FIX using the DTC engine.
In some embodiments, exceptions may be put in place for some clients. In an exemplary exception, if a client cannot provide the expected tag information, the order may be overridden when it arrives at the routing system of the firm 200. For example, DTC or DTK may be stamped by the routing system on every order received from a particular client by the firm; these orders will then be treated as if the client had flagged the orders itself. Another example of this exception assumes that the client cannot send correct handling instructions. In this instance, the values sent by the client via the FIX protocol can be overridden (e.g., 21=1 (no broker intervention) is changed to 21=3 (manual best execution)).
In a preferred embodiment of the present invention, a number of different types of entitlements may be implemented, meaning that only certain clients are able to have certain types of orders auto-executed with a price improvement. For example, certain clients may be entitled to have orders for particular types of instrument processed by the inventive system (e.g., equities—single only). By way of further example, clients may only be authorized to trade in particular markets, and orders will be rejected if they are not within an established market for that client, or not within a market to which connectivity can be offered.
DTC order types may have their own specific entitlements, in the preferred embodiment. For example, clients can be enabled or disabled for auto-execution of stocks on an exchange-by-exchange basis. For example, a client may currently be enabled to auto-execute on all exchanges except Italy.
The decision as to whether an order is eligible for auto-execution and a price improvement, and the size of the price improvement, is determined by reference to a matrix, in the preferred embodiment.
An exemplary matrix (illustrated in Table 3) includes several tiers. In the illustrated example, five tiers are used. However, any number of tiers can be used in connection with the present invention. The tiers represent ranges of values associated with the size of the order that the firm will accept for auto-execution. In Table 3, the X variable represents the size of a given order; the Y variable represents the percentage value of the average daily volume (“ADV”) traded on the market in that security and the x variable represents the percentage value of the price improvement for a given tier. In a typical embodiment, the values associated with the X, Y and x variables are different for each tier. Specific values are not associated with these variables in the example shown, as such values can be set as appropriate for a given firm/client. Typically, the price improvements offered are based on limits agreed to with clients in advance. A given order received by the firm will, first, be checked against tier 1; if it falls within the limits of tier 1, it will be executed with the price improvement associated with that tier. If not executable in tier 1, it will be checked against tier 2, and so on. In a preferred embodiment, any given tier may not be used for a specific client (i.e., different tiers may be offered to some clients and not others based on the client's status with the firm).
The DTC engine 400 checks as to whether orders are available for auto-execution and a price improvement, in accordance with various stages, in the preferred embodiment. In particular, if an order is in a particular state that requests consideration for DTC (e.g., is flagged accordingly), then the order will pass through the stages set forth above in the exemplary matrix, from left to right, to determine eligibility for auto-execution. Moving from left to right in this table, the X value goes up; the Y value goes up; and the x value goes down. Thus, as received orders increase in size (X) and % ADV (Y) they will receive a smaller price improvement (x).
In the preferred embodiment, the class of the stock is also taken in consideration in determining whether an order for such stock is eligible for auto-execution and a price improvement. Class 0 is the default, effectively meaning un-classified. Class 5 stocks are high liquidity stocks for which the largest size order may be eligible for auto-execution and a price improvement. Class 1 stocks, on the other hand, have limited liquidity. For each client, a limit table is specified, from which the maximum dollar values for auto-execution of differently classified stocks can be queried.
Velocity checking may be implemented in connection with placing and filling of orders using the system described herein. The following provides an algorithm describing how velocity checking may be implemented. The following quantities are typically client- and security-specific:
st number of shares a client wants to trade in a specific security at time t.
lmax maximum number of shares a client is able to trade in one clip, based on his/her setup, i.e., the highest possible number of shares in a specific security according to client tier and ADV limits.
ldyn,t dynamic limit of the number of shares a client is allowed to traded at time t
lused,t number of shares which are currently used up from the max limit at time t
vt cumulative exchange volume in a specific security at time t
t points in time when a client traded in a specific security, t=0 is defined as beginning of the day.
r percent of permissible volume rate, typically 20% or 25%.
Initial values, at the beginning of the day:
lused,0=0
v0=0
If a client tries to trade st shares of a specific security at time t, let
ldyn,t=max(0.0,lused,t-1−(vt−vt-1)·r),
then the trade is accepted by the safety check, if the following condition holds true:
st≦ldyn,t
lused,t is updated thereafter:
lused,t=min(lmax,lused,t+|st|)
The velocity checking is used to limit, dynamically, trading in line with market volume. Conceptually, the principle of velocity checking can be explained with reference to a receptacle holding a liquid. The amount of liquid in the receptacle represents the dynamic client limit. At the start of the day, the receptacle is fully filled. Each time the client trades, liquid is removed in proportion from the receptacle. The receptacle is replenished in line with external market volume, as shown in
Synthetic equities represent derivative products structured around the market performance of underlying equity instruments. Such contracts have a number of commercial benefits to clients, including the ability to short, inclusion of leverage and ease and reduced cost of settlement. The system supports synthetic equity orders. Cash Settled (DVP) Represents physical delivery of stock on a delivery verses payment (DVP) basis. Contract for differences (CFD) represent over the counter derivatives products whereby the firm and the client agree to exchange cash flows over time based on the movement of a single security. An equity swap is a contract between two parties who agree to exchange cash flows, over a defined time, based on the movement of reference equity and interest instruments. Swaps allow a client to trade a changing portfolio of securities over time within one single equity swap. Requests for market data relate to the scenario in which a client wishes to enter into a CFD or an equity swap with a third party broker but communicates with the firm, as well the third party broker, in relation thereto. The legal documentation required in this regard confirms that the client is only requesting the firm to provide it with market data in relation to a reference equity transaction (such as data relating to pricing, availability, capacity, etc) (known as a “Request For Market Data”) rather than submitting an cash equity order. The firm may make a speculative purchase of the equities corresponding to a Request For Market Data which we may offer to the third party CFD/swap provider as a ready hedge to the CFD/swap it will be writing. The firm's documentation sets out that neither the Request For Market Data nor the firm's provision of data in respect thereto amounts to an agreement for the purchase or transfer of securities. Core requirements for trading synthetics via the DTC product are to: Entitle clients on a per market basis for CFDs, RFMD/IP and Swap when sending orders to the DTC product. Pass appropriate flags (tag 775 and 7750) to downstream systems (primarily, the DTC engine).
Table 4 sets forth the tags that may be used, in conjunction with the FIX protocol, for synthetics.
Synthetics are routed in the same way in which other orders with DTC flags are routed. Below shows exemplary ways in which the FIX protocol could be altered to handle synthetics. The below identifies
The client can only amend an order once it is carried on as a worked order for DTC (i.e., when the order arrives on the Sales Trader's desk for manual working, the Sales Trader can amend it). For DTK, amendments are not permitted.
A preferred embodiment of the system is set up to reject orders in a variety of circumstances such as, for example: the client is not authorized to use the system; the client is not authorized to send a CFD or Swap or RFMD; the client has been disabled; the order exceeds the client limit; lack of liquidity of the stock that is the subject of the order; the client sends both a DTC and DTK flag in the text field; receipt of a cancel/amend message; or the client sends anything other than 21=3 (unless an exception is implemented).
As well as providing complete execution for orders that fall within the tiers described above, the DTC engine also has the ability to partially fill an order up to the specified limit and then reject the residual of the order. In the case an order is flagged DTK, the residual of the order will be rejected directly back to the client, unfilled. In the case of the DTC flag, the residual will go on to the Sales Trader to be manually worked.
The methods of the present invention for processing orders to trade securities are illustrated in the following flow charts. The steps identified in these flow charts do not necessarily dictate the order in which the steps need be carried out. Further, one or more of the steps of the method may be carried out by software running on a data processing apparatus.
With reference to
With reference to
With reference to
In one embodiment, a system for processing an order to trade securities includes an order management component (e.g., order management system 300 of
In one embodiment, the system for processing an order to trade securities includes an order management component 300 that receives an order to trade securities. The order is associated with one of first and second execution indications. A processor 400 that automatically executes the order with a predetermined price improvement if the order meets one or more eligibility requirements. The order is processed manually if the order fails to meet one or more of the eligibility requirements and the order is associated with the first execution indication. The order is returned unfilled if the order fails to meet one or more of the eligibility requirements and the order is associated with the second execution indication.
In one embodiment, the system for processing an order to trade securities includes the order management component 300 that receives an order to trade in a security. The order being associated with an order size and one of first and second execution indications. The processor 400, in communication with the order management component 300, determines a tier within which the order falls based on the order size and an average daily volume of trading in the security. The tier includes one of a plurality of tiers representing a range of values associated with a trade size and an average daily volume of trading in a security. Each of one or more of the tiers is associated with a price improvement. The processor 400 automatically executes a portion of the order, up to the trade size associated with the determined tier, with the price improvement associated with the determined tier, if the order meets one or more predetermined eligibility requirements. A residual of the order exceeding the trade size associated with the determined tier being manually processed if the order is associated with the first execution indication. The residual of the order exceeding the trade size associated with the determined tier is returned unfilled if the order is not associated with the second execution indication.
In another embodiment, the system includes a routing component (e.g. routing system 200 of
While the invention has been described in detail and with reference to specific embodiments thereof, it will be apparent to one skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope thereof. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
This application claims priority to U.S. Provisional Patent Application No. 60/733,246, filed Nov. 3, 2005, which application is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7162448 | Madoff et al. | Jan 2007 | B2 |
| 20020184136 | Neubert et al. | Dec 2002 | A1 |
| 20040024689 | Zhou et al. | Feb 2004 | A1 |
| 20040143542 | Magill et al. | Jul 2004 | A1 |
| 20040210511 | Waelbroeck et al. | Oct 2004 | A1 |
| 20040243505 | Sweeting et al. | Dec 2004 | A1 |
| 20050240510 | Schweickert et al. | Oct 2005 | A1 |
| 20050240513 | Merold | Oct 2005 | A1 |
| 20060229967 | Sweeting | Oct 2006 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20070100742 A1 | May 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60733246 | Nov 2005 | US |
