|
Execution Process
The unconditional close order is sent to the marketplace server and routed to the liquidity source having the best available price at that time. The order at this point may be executed in full, executed partially, or rejected. The reason for rejection would be that the price at this time was no longer satisfying the embedded conditions when the market order was sent. Remember that unconditional does not mean that the close order will be executed at any price condition. Indeed, if it was the case, orders would run the risk of being executed even if the market would be far away from the market the trader saw or traded when he sent the order. Again, there is a delay between the time the order is sent, and the time the order reaches the marketplace. This delay is understood to be the shortest possible one, but cannot be zero, and the market has no memory of the situation when the order was sent. As a result, the system embeds a maximum value of negative slippage even on unconditional market orders, where the slippage control is disabled on the trader side. This value is fixed and always the same for every client and every market order when the slippage control is disabled on the client application side. This is obviously to prevent executions at prices either far away from the price the trader acted on, or at prices away of the general market level. To avoid risk of multiple executions of a unique order amount, each order is routed on one liquidity source having the best price, but one at once. The order cannot be treated simultaneously by several liquidity sources, or counterparties. By opposition with the market order however, the close order will be resubmitted as long as the original position is not entirely closed. The trader must however follow closely the closing order process, especially when large positions are involved. It is likely that large positions will be closed after several partial executions, and it is wise for the trader to monitor this process. |
|