Task

To add a WSE account:

1. Click Accounts in the left navigation pane.

2. Click +New Account at the top of the Accounts screen.

   The Account Information section is displayed.

   

3. In the Account Name/Number field when creating an account, enter the up to 10-digit number provided by the exchange and required for order routing by DMA Traders (Desk Traders are not required to submit an account number on orders). The user’s TT account is sent to the exchange as the routing/clearing account on each order action in Tag 1.

   Note: When adding an account, consider the following account number restrictions at B3:

   • Only numeric account values are accepted. If an order is entered with an invalid account value, the exchange rejects the order.
   • Account numbers are restricted to a maximum length of 10 digits. For longer account numbers, the exchange truncates any additional digits beyond the 10 character limit, which results in orders being rejected by the exchange.
4. If this is a sub-account, select a “parent” account in the Parent field.
5. Click the Type field and select an account type.

   Use this field to define the routing behavior for the account and set up its
   account hierarchy for tiered risk. All order routing
   is based on the user account. Select one of the following:

   • Routing (external clearing): Defines the parent account as a clearing account sent to the exchange
     on all orders. If assigned to a user, the account appears in the user’s list of routable accounts. When
     selected by a user, the account is used to route orders and identify the account to the exchange (e.g,
     FIX Tag 1). If configuring this account as an omnibus account, select this option. If an internal
     sub-account is assigned to a parent account, the sub-account inherits the exchange connectivity of the
     parent account.

   • Routing (internal sub-account): Defines the account as a sub-account that is not routed to the
     exchange. This allows you to assign the user to an internal account for routing and risk purposes, even
     though a parent account will be sent to the exchange as the actual clearing or omnibus account.

     Tip: Sub-accounts set as “Routing (internal sub-account)” can be selected by client trading
     applications for submitting orders, but only their parent account’s clearing account is routed to the
     exchange.

   • Non-Routing: Not sent to the exchange. Recorded internally and can be used for back-office
     purposes, or as a parent risk account that allows you to group a set of sub-accounts together and set
     risk for the non-routing parent.

     Tip: Accounts set as “Non-Routing” are not selectable by client trading applications.

   • Audit Trail Only: Not sent to the exchange. Use this account type for the TT FIX Inbound Drop Copy
     service, which allows third parties to import their data sources into TT. When selected, the “Order
     Cross Prevention” option is disabled for this account.

   • Error Routing: An account that can be used to route order reject messages created by FIX Order
     Router or FIX Inbound Drop Copy to specific Drop Copy sessions. Error accounts can be assigned to users
     and to FIX Order Routing and Inbound FIX Drop Copy sessions. An error account is not routed to the
     exchange and is not part of account hierarchies.

6. To prevent order crossing using this account or any of its sub-accounts, click the
   Order Cross Prevention field and select an order crossing rule. The TT Trade
   application performs the following order actions based on which rule is selected:
   • Not Applied — No order cross prevention rule is applied to the account.
   • Reject New — Reject a new order that could potentially fill resting orders in the same account or account tree. Applies to only Limit orders and native Iceberg orders.
   • Cancel Resting (wait for ACK) — Send a cancel request to the exchange for the
     resting order. When the exchange acknowledges the request and cancels the order, submit the new order. Applies to only Limit orders and native Iceberg orders.

   • Position Transfer —
     When a match is detected, the resting order is canceled or the working order quantity is reduced by the size of the aggressive order. A fill is created by TT and sent to each account. If the aggressive order was larger than the resting order, then the remainder of it will be sent to market. For a description of how Position Transfer works, refer to Position Transfer.

   • Position Transfer (if resting order is best bid/offer) — This rule works the same as Position Transfer except that the internal matching occurs only if an order has the potential to fill a resting order at the current best bid/ask price.

     Note: When using this rule, the resting order may get matched and filled at the exchange while the aggressive order is in flight.

7. Optionally, check one of the following options:
   • Use Reject New instead of Position Transfer within the same account — When enabled, this setting prevents the use of position transfer within the same account and uses “Reject New” for order cross prevention. This setting is active when “Position Transfer” is selected for the account, otherwise, it is grayed-out.
   • Go to market with Position Transfer balances w/o waiting for Cancel/Reducing ACK — When enabled, Position Transfer does the following if the aggressive order quantity is larger than the resting order quantity:
     • Reduces the aggressive order quantity by the amount of the resting order
     • Submits a request to the exchange to cancel the resting order, followed immediately by an order for the remaining quantity without waiting for acknowledgement that the resting order was canceled or reduced.

     For example, if a 2-lot Sell order is resting when a 10-lot Buy order is entered that matches, Position Transfer immediately sends a cancel request to the exchange for the Sell order, followed by an 8-lot Buy order. Position Transfer then waits for the exchange to acknowledge that the 2-lot Sell order was canceled successfully. After receiving acknowledgement, the 2-lot fills are created internally and transferred to each trader’s account.

     Using this option, you can submit part of the order to the market sooner while the remainder of the order waits to be transferred. You can also reduce the risk of the entire aggressive order being rejected while waiting for the position transfer to complete.

     Note: With this option, there’s a risk that the crossing orders may match at the exchange if the two traders are using separate exchange connections on two different order routing servers.

   • Disable trading (this account only) — Disables trading for this account. This checkbox is checked by
     default.
   • Disable trading (sub-accounts) — Disables trading for all child accounts of this
     parent account.
   • Disable trading (autoliquidate) — Checked automatically after auto-liquidate is triggered
     on an account. Increase the credit limit and uncheck this option to restore trading to a liquidated account. This
     setting can only be checked by the Setup application when an account is liquidated (i.e., you cannot manually check
     this setting).
   • Disable trading (max order limit reached) — trading will be disabled after the specified maximum order limit, specified in connections, has been breached.
   • Include on Score — This account will be utilized for TT score Surveillance models.
   • Include on FIX Drop Copy — The trades from this account will be included on the FIX drop copies generated.
8. Optionally, configure the Prevent Duplicate Orders settings:
   • Check Quantity — Sets the number of duplicate orders to allow within
     the configured time frame.
   • Check Time Frame — Sets the time frame in milliseconds and enables the duplicate order check
     for the account. Enter a value from 1-999999999. When the number of orders for the same instrument and price
     set in the Check Quantity field occurs within the configured time frame, the
     duplicate orders are rejected. When Check Time Frame is blank, no duplicate order check is
     applied to the account.
   • Apply to sub-accounts — Copies the “Prevent Duplicate Orders” settings from the parent account
     to their child accounts. This ensures that any sub-accounts added to the shared parent account cannot have a
     differentmissing value in this field . When checked, the value cannot be changed on any sub-accounts added
     by your company or a shared company.
9. In the Order Management System (OMS) Settings section, configure the following:
   • Lock fill notifications on new staged orders — Controls how fills are reported back to the care order originator. When this setting is checked, new care orders are automatically locked when they are claimed. Fills for locked orders will have to be manually allocated and released. When unchecked, fills and fills prices are immediately released back to the customer using the average prices calculated by TT. This setting supports the Lock and Release functionality in TT OMS.
   • Only combine orders with the same price — Restricts how care orders are bulked. When this setting is checked, only care orders with the same price can be added as part of a bulk order. When unchecked, care orders at different prices can be bulked. Bulking requires that all care orders have the same product and Buy/Sell side. This setting supports the Bulking functionality in TT OMS.
   • Only combine orders with the same account — Restricts how care orders are bulked. When this setting is checked, only care orders with the same account can be added as part of a bulk order. When unchecked, care orders in different accounts can be bulked. Bulking requires that all care orders have the same product and Buy/Sell side. Supports the Bulking functionality in TT OMS.
   • Only combine orders with the same customer — Restricts how care orders are bulked. When this setting is checked, only care orders with the same order profile can be added as part of a bulk order. When unchecked, care orders with different customer order profiles can be bulked. Bulking requires that all care orders have the same product and Buy/Sell side. Supports the Bulking functionality in TT OMS.
10. Click Create.

    The new account appears in the Accounts list in the data grid. Sub-accounts appear as nested
    under their parent account.

Configuring WSE exchange properties

1. Click Accounts in the left navigation pane and select an account in the data grid.
2. Click the Exchanges tab for the selected account.
3. Click the Select an Exchange selector and select WSE.

The “Exchange Properties” section is displayed.



4. Configure the following fields:
   • Order Capacity — Indicates the account type for which the order is entered. Sent to the exchange in Tag 47 (Rule80A). This is a required field. Select one of the following:
     • Client
     • House
     • Matched Principal
     • Non-Member LP
     • Member Liquidity Provider (LP)
     • Member Issuer LP
     • Non-member Issuer LP
   • Clearing Instruction — Indicates the pre-posting and give-up action to be taken by the clearing system when a trade has occurred, following a given order. Sent to the exchange as Tag 9938 (ClearingHandlingType) in the exchange API. Select one of the following options:
     • Systemic Posting
     • Manual Mode
     • Automatic Extraction
     • Automatic Allocation
   • Clearing Firm ID — Sets the identifier of the Clearing firm. Sent to the exchange as Tag 439 (ClearingFirm).
   • Clearing Account — Client Account Number of the investor account. Overrides the TT routing account value in FIX Tag 1 on order actions sent to the exchange. By default, the user’s routing account is sent as Tag 1.
   • Customer Order Handling Instruction — Available values include:
     • Desk
     • Electronic (Default)
     • Vendor-provided Platform, billed by Executing Broker
     • Sponsored Access via Exchange API or FIX, provided by Executing Broker
     • Premium Algorithmic Trading Provider, billed by Executing Broker
     • Other, including Other-provided Screen
   • TT SMP ID — A user-defined, alphanumeric identifier used to tag orders so the TT system can
     match potential crossed trades. For more information on TT Self Match Prevention, refer to the TT
     Self Match Prevention By ID section in the Setup help.
   • TT SMP Instruction — Sets the TT Self Match Prevention (TT SMP) behavior and determines which
     order is canceled (resting or aggressing) if self-match prevention occurs. For more information on TT Self
     Match Prevention, refer to the TT
     Self Match Prevention By ID section in the Setup help.
   • Direct Electronic Access — Sets whether or not the order is sent from direct/sponsored access, or from another source. Valid values:
     • None
     • Yes
     • No
   • Liquidity Provision — Indication of market making. Valid values:
     • None
     • Yes
     • No

     Sent to the exchange as FIX Tag 2594=2.

   • Commodity Derivative Indicator — Indication of whether the order is for hedging purposes to reduce risk. Valid values:
     • None
     • Yes
     • No

     Sent to the exchange as FIX Tag 2594=3.

   • Investment Decision ID — Code used to identify the person or the algorithm within the member or participant of the trading venue who is responsible for the investment decision. Sent to the exchange as FIX Tag 20053 (InvestmentDecisionShortCode).
   • Investment Decision Qualifier — Determines if the trading decision was made manually by a user or automatically by an automated trading application using this account. This is an optional field. Select one of the following:
     • Manual: Indicates the trading decision was made by a person.
     • Automatic: Indicates the trading decision was made by an automated trading application.
   • Execution Decision ID — User or firm that submitted the order. Enter a registered ID/Short Code. Sent to the exchange as FIX Tag 452=12 + 448.
   • Execution Decision Qualifier — Determines if the user or firm sent the order manually or automatically using an automated trading application with this account. Sent to the exchange as FIX Tag 20074 (ExecutionWithinFormAlgoOrderFlag). Select one of the following:
   • Manual: Indicates the order was sent manually.
   • Automatic: Indicates the order was sent automatically.
   • Secondary Execution Decision ID — Secondary user or firm associated with the order. This field can be used for trading on behalf of clients and used for internal reporting purposes. Enter a registered ID/Short Code.
   • Client ID — Code used to identify the client of the member or participant of the trading venue. Sent to the exchange as FIX Tag 20051 (ClientIdentificationShortCode).
   • Secondary Client ID — Secondary customer identifier associated with the order. This field can be used for trading on behalf of clients and used for internal reporting purposes. Enter the customer’s legal entity identifier (LEI/Short Code).
   • Client ID Type — Identifies the type of client submitting the order. Select either “Firm” or “Natural Person”.
   • Execution Firm — Identifies the firm or user managing the account. Enter a user-defined value.
   • Free-form 1-20 — Optional, user-defined text fields that can be populated for TT and FIX client application users. These values are not sent to the exchange, but are visible in the Order Book, Fills, and Audit Trail widgets and on FIX Drop Copy records.

   

   • Apply to all sub-accounts — Allows a company creating a sub-account or sharing an account with another company to apply the parent account exchange field to the sub-account. This ensures that any sub-accounts added to the shared parent account cannot have a different value in this field and that the value is sent to the exchange. Check the checkbox next to each field to apply its value as needed. When checked, the value cannot be changed on any sub-accounts added by your company or a shared company.
   • Lock sub-accounts — Allows a company creating a sub-account or sharing an account with another company to lock the value in a sub-account exchange field even if the sub-account is configured with a more specific order tag default match. This ensures that any child accounts (sub-accounts) created from the shared parent account cannot have a different value in this field and that the value is sent to the exchange. When checked, the value cannot be changed on any sub-accounts added by your company or a shared company. Note: The Apply to all sub-accounts setting must be enabled for the field in order to enable the Lock sub-accounts setting.
   • Client Can Override — Determines if a user can override the value in this field when submitting orders from trading applications or APIs. Check the check box to unlock the field and allow a user to override the value. When unchecked, the field is locked and the user cannot change it.
5. Click Save Changes.

WSE のマーケット データを有効化するには

1. データ グリッドで選択したユーザーの [Users] – [Exchanges] タブをクリックします。
2. 取引所リスト ドロップダウン矢印をクリックし、スクロールして取引所を選択します。
3. [Subscriber Market Data] と [FIX Market Data] タブをクリックし、選択した取引所のユーザーを設定します。
   • [Subscriber Market Data] (マーケット データ) タブを使って、銘柄グループごとのすべてのマーケット データへのアクセスを許可または拒否できます。
   • [Fix Market Data] (FIX マーケット データ) タブを使って、銘柄グループごとの TT FIX を通じたすべてのマーケット データへのアクセスを許可または拒否できます。
4. [Subscriber Market Data] タブをクリックして、取引所で利用可能なすべてのマーケット データへのアクセスを許可または拒否できます。

   

   [Allow] が有効の場合、[Sessions] をクリックすると、異なった IP アドレスやアプリケーションを使って、同時に利用できる同時マーケット データ セッション数を設定することができます。[0 – Delay Only] を選択すると、遅延環境を除くすべての環境で、銘柄グループが拒否されたことを示しています。つまりリアルタイムのマーケット データへのアクセス許可がありません。

   注: 無効化された銘柄グループは会社にとって承認されていません。これらを有効化するにはトレーディング・テクノロジーズの担当者にお問い合わせください。

   マーケット データの同意書を必須付けている取引所に関しては、「セッション」欄の隣に以下の内容が表示されます。

   • － マーケット データの同意書が承認されたことを示します。
   • － マーケット データの同意書が未処理または承認の待機中であることを示します。

   ヒント: マーケット データ インジケータをクリックして [Agreements] タブを開きます。

5. [FIX Market Data] (FIX マーケット データ) タブをクリックして、取引所で利用可能なすべてのマーケット データへの FIX ユーザー アクセスを許可または拒否できます。

   

6. [FIX and SDK Server Market Data] タブをクリックして、TT FIX、TT .NET SDK Server Side、TT Core SDK 取引アプリケーションに対して取引所で利用可能なマーケット データ グループへのアクセスを許可または拒否できます。

   [Allow] をクリックしてマーケット データ グループを有効化する場合、[Quantity] をクリックして、FIX フィードの裏でマーケット データを表示しているユーザー数や、TT .NET SDK Server Side の数、TT Core SDK アプリケーションの数を設定します。

   FIX フィードや SDK サーバーサイドの取引アプリケーションは、取引所で定義された表示以外の目的であり (ブラックボックス アルゴリズム、損益の計算のためのプログラムなど)、[Allow] をクリックしてマーケット データ グループを有効化し、[Quantity] を設定して、[Non-display] を有効にします。

   マーケット データを外部に分配する場合 (会社外部のユーザーに対して等)、[External Distribution] チェックボックスを有効にします。

   注: 無効化された銘柄グループは会社にとって承認されていません。これらを有効化するにはトレーディング・テクノロジーズの担当者にお問い合わせください。

7. [Save Changes] (変更の保存) をクリックします。