To add an ICE account:
Click +New Account at the top of the Accounts screen.
The Account Information section is displayed.
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 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.
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.
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 transfered. 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.
The new account appears in the Accounts list in the left navigation pane. Sub-accounts appear as nested under their parent account.
Configure the following settings:
Sent to the exchange as Tag 9700-DirectElectronicAccess. Required by the exchange for MiFID II.
Sent to the exchange as Tag 9701-TradingCapacity. Required by the exchange for MiFID II.
Sent to the exchange as Tag 9702-LiquidityProvision. Required by the exchange for MiFID II.
Sent to the exchange as Tag 9703-CommodityDerivIndicator. Required by the exchange for MiFID II.
Sent to the exchange as Tag 9704-InvestmentDecision. Required by the exchange for MiFID II. Enter up to 15 integers. Only numeric values are supported.
Sent to the exchange as Tag 9705-ExecutionDecision. Required by the exchange for MiFID II. Enter up to 15 integers. Only numeric values are supported.
Sent to the exchange as Tag 9706-ClientIDCode. Required by the exchange for MiFID II. Enter up to 15 integers. Only numeric values are supported.