Trade
Overview
TT Platform
Description
Task
Browser Access
Description
Task
Videos
TT Desktop
Description
Task
Videos
Reference
Workspace Windows
Description
Task
Videos
Widgets
Description
Task
Preferences
Description
Viewing Market Data
Time and Sales
Task
Reference
Description
Depth
Description
Task
Reference
Market Grid
Description
Task
Videos
Reference
Product Grid
Description
Task
Reference
Spread Matrix
Description
Task
Videos
Reference
Basic Order Entry
TT Order Types
Description
Task
Videos
Reference
Case Studies
TT Premium Order Types
Description
Task
Reference
Order Ticket
Description
Task
Use Cases
Reference
MD Trader®
Description
Task
Videos
Reference
Order Profiles
Description
Task
Reference
Routing Rules
Description
Task
Blocktrader
Description
Task
Videos
Reference
Trading Crypto on TT
Description
Task
Videos
Reference
Trading on B3
Order Management
Order Book
Description
Task
Reference
Floating Order Book
Description
Task
Reference
Fills
Description
Task
Reference
Positions
Description
Task
Reference
Orders and Fills
Description
Task
Reference
Audit Trail
Description
Task
Reference
Audit Query
Description
Task
Reference
Account List
Description
Task
Videos
Reference
Position Manager
Description
Task
Reference
Alert Manager and Alert Viewer
Description
Task
Videos
Reference
Account & User Restrictions
Description
Task
Reference
Balances
Description
Task
Reference
TT® OMS
Care Orders
Description
Task
Videos
Reference
Lock and Release
Description
Task
Bulking
Description
Task
Videos
Stitching and Splitting
Description
Task
Combining
Description
Task
Order Passing
Description
Task
Use Cases
Order Exceptions
Description
Task
Options
Options on TT
Description
Videos
Options Chain
Description
Task
Use Cases
Videos
Reference
Options Trade Monitor
Description
Task
Videos
Reference
Vol Curve Manager
Description
Task
Use Cases
Videos
Reference
Electronic Eye
Description
Task
Videos
Reference
RFQ Viewer
Description
Task
Videos
Reference
RFQ with Counterparties
Description
Task
Counterparty Manager
Description
Task
Strategy Creation
Description
Task
Use Cases
Reference
Options Risk
Description
Task
Videos
Reference
Options Risk Matrix
Description
Task
Videos
Reference
Watchlist
Description
Task
Videos
Reference
Expiration Manager
Description
Task
Volatility Calculator
Description
Task
TT Uncovered 2.0
Description
Task
TT Uncovered 3.0
Description
Task
QuikStrike
Description
Task
Spread Trading
Autospreader
Description
Task
Use Cases
Videos
Reference
Autospreader Rules
Description
Task
Videos
Reference
Hedge Manager
Description
Task
Videos
Reference
Trading in Yield
Description
Task
Use Cases
Reference
Aggregator
Description
Task
Videos
Reference
Algo Trading
Algo Dashboard
Description
Task
Videos
Reference
Template Manager
Description
Task
Order Management Algos (OMAs)
Autotrader
Description
Task
Reference
Videos
Excel integration with TT
Description
Task
Videos
Reference
Market-Making Algos
Analytics
Charts
Description
Technical Indicators
Task
Videos
Reference
Trader Analytics
Description
Task
Reference
ADL
ADL Overview
Introduction to ADL
Description
Task
Videos
Reference
ADL Basic Concepts
Description
Task
Reference
Building your first algo
Lessons
Advanced concepts
Description
Task
Case Studies
Jump blocks
Group blocks
Virtualized blocks
Library blocks
Trading Blocks
Discrete blocks
Arithmetic blocks
Basic blocks
Logic blocks
Miscellaneous blocks
Setup
Setup Overview
Getting Started
Description
Task
Videos
Reference
Supported Order Types and TIFs
Company Administration
Connections
Description
Task
Videos
Reference
Accounts
Description
Task
Videos
Use Cases
Reference
Users
Description
Task
Videos
Reference
Company
Description
Task
Reference
Order Tag Defaults
Description
Task
Account Administrators
Description
Task
TT Premium Services
Description
Task
TT Access
Description
Task
Advanced Features
Description
Risk Management
Risk Administration
Description
Task
Risk Limits
Description
Task
Videos
Reference
Pre-Trade Portfolio Risk
Description
Task
Reference
Order Cross Prevention
Description
Task
Videos
KRM Limits
Description
Task
TT® OMS
TT OMS Administration
Description
Task
Use Cases
Reference
Exchanges: Americas
B3
Description
Task
CBOE
Description
Task
Cboe FX
Description
Task
Reference
CFE
Description
Task
CME
Description
Task
Dealerweb
Description
Task
EBS Direct
Description
Task
EBS Market
Description
Task
Fenics
Description
Task
FMX
Description
Task
FMX_USTF
Description
Task
Goldman Sachs Commodity Blocks (GSCB)
Description
Task
Referece
ICE
Description
Task
MexDer
Description
Task
MIAX_FUT_CH
Description
Task
MIAX_FUT_NY
Description
Task
MX
Description
Task
Nodal
Description
Task
NFI
Task
Exchanges: EMEA
ATHEX
Description
Task
BIST
Description
Task
DGCX
Description
Task
EEX
Description
Task
EPEX SPOT
Description
Task
Reference
Eris
Description
Task
Eurex
Description
Task
Videos
Euronext
Description
Task
GFO-X
Description
Task
ICE_L
Description
Task
JSE
Description
Task
LME
Description
Task
LME NTP
Description
Task
LSE
Description
Task
MEFF
Description
Task
NDAQ_EU
Description
Task
NASDAQ_NED
Description
Task
Nord Pool
Description
Task
Reference
WSE
Description
Task
Exchanges: Asia/Pacific
ABX
Description
Task
ASX
Description
Task
FEX
Description
Task
HKEx
Description
Task
JPX
Description
Task
NSE
Description
Task
NZX
Description
Task
SGX
Description
Task
SGX GIFT
Description
Task
TAIFEX
Description
Task
TFEX
Description
Task
TFX
Description
Task
CoinFLEX
Task
Exchanges: Crypto
Coinbase
Description
Task
Kraken
Description
Task
FIX Support
FIX Ruleset
Description
Task
FIX Sessions
Description
Task
Secondary Accounts
Description
Task
Monitor
TT Mobile
TT Backtesting
APIs
TT REST API 2.0
Getting Started
API Reference
TT REST API 2.0 (UAT)
Getting Started
API Reference
TT .NET SDK
Getting started with TT .NET SDK
Creating the application framework
Working with instruments
Subscribing for market data
More about prices
An in-depth look at the Price class
Working with orders and fills
Handling trade subscriptions
Working with trade subscriptions
Working with Algos
Algo Server
TT Order Types
TT Premium Order Types
Advanced Concepts and Options
Appendix
TT CORE SDK
Getting Started with TT Core SDK
Creating Application Framework
Working With Instruments
Subscribing for Market Data
Working with Orders and Fills
Creating a TT Application Server
Appendix
TT Trade Surveillance
Overview
Using TT Trade Surveillance
Cluster View
Core Models
Market Abuse Models
Cross Product Models
Spoofing Models
Improperly Matched Trade Models
Market Rate Models
Trading Behaviors Models
Miscellaneous Models
Configurable Models
Reports
Wachlists
Reference
TT FIX Services
TT FIX General
Getting Started
FIX Message Structure
Session messages
TT FIX Order Routing
Overview
TT FIX message conversations
Supported application messages
TT FIX Market Data
Overview
TT FIX message conversations
Supported application messages
TT FIX Drop Copy Out
Overview
TT FIX Message Conversations
Supported application messages
Compliance Feed messages
TT FIX Drop Copy In
Overview
Supported application messages
TT FIX Gateway
Getting Started
FIX Message Structure
Components
Session messages
Price Gateway Messages
Order Gateway Messages
TT FIX Recovery
Overview
FIX Recovery Methods
Supported application messages
Compliance Feed Messages
MiFID II Support

Adding an MX account

On this page

To add an MX 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 for MX, enter the up to 12-character name used for the TT routing account. The account name is user-defined and required for order routing. The user’s TT routing account is sent to the exchange as the clearing account on each order action in the Clearing Data field in the exchange API.

  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 MX 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 to find and select an exchange.
  4. Configure the settings in the Exchange Properties section.

    Configure the following settings:

    • Account Code — Select an MX-defined account code. This field is required for order routing. Sent to MX in the “Account Type” exchange API field. Available MX account codes are:
      • 1 (Customer)
      • I (Customer Insider)
      • H (Customer Shareholder)
      • 4 (Pro)
      • S (Pro Insider)
      • L (Pro Shareholder)
      • 2 (House)
      • N (House Insider)
      • O (House Shareholder)
      • 5 (N/C)
      • R (N/C Insider)
      • D (N/C Shareholder)
    • Intent to Cross — Required tag for exchange compliance purposes for brokers. TT requires all clients to consult with the MX exchange to determine the required use of this field.
    • Trading Capacity — Indication of dealing on own account (DEAL), matched principal (MTCH), or any other trading capacity (AOTC). Valid values:
      • Deal
      • Match
      • Any other capacity
    • Clearing Account — Overrides the TT account value in the Clearing Data field in the exchange API on order actions sent to the exchange. You can enter up to 12 characters and this field is optional. By default, the user’s TT account is sent in the Clearing Data field.
    • 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
    • Commodity Derivative Indicator — Indication of whether the order is for hedging purposes to reduce risk. Valid values:
      • None
      • Yes
      • No
    • Investment Decision ID — User or firm who made the trading decision. Enter a registered ID/Short Code.
    • 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.
    • Execution Decision Qualifier — Determines if the user or firm sent the order manually or automatically using an automated trading application with this account. This is an optional field. 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 — Customer identification. Enter the customer’s legal entity identifier (LEI/Short Code).
    • 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 — Sets the type of client submitting the order. Select either “Natural Person” or “Firm”.
    • 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.