Unethical Conduct by IB

Discussion in 'Interactive Brokers' started by TRADERguy, Apr 27, 2006.

Thread Status:
Not open for further replies.
  1. Here is how I think he screwed up. First, he had a responsibility to make sure he was confirmed out immediately, on every single order cancellation request, but he didn't know how to do so (how to look for the red order status code). Second, from the time he issued the cancellation request, until almost 40 minutes later, he did nothing to alert IB to the problem, or to ask IB to determine whether or not his order had been executed and resulted in a position requiring further management on his part. He lost 43 pips because of his 40 minute delay. He delayed until he noticed that his new position had unexpectedly showed up on the TWS. He should have been all over this problem 40 minutes before that time, so that any loss would have been far smaller, and so that he would have been at least able to make a case that the inevitable small loss should be eaten by IB and/or by the counterparty.

    I'm willing to consider placing some blame on IB for possibly bad documentation which might have led to this guy's uninformed use of TWS and his resulting mistake.
     
    #31     Apr 27, 2006
  2. No, IB does do things wrong sometimes, and many complaints are well-founded complaints, and I myself have made some of them, sometimes privately, and sometimes in this public forum. But I make my criticisms in the spirit of constructive criticism, because I think overall, IB is imperfect but it is the best deal. I think that bad documentation is very severe and persistent problem at IB, and that it MAY have contributed to this situation.
     
    #32     Apr 27, 2006
  3. tomcole

    tomcole

    If it takes 37 minutes to report a fill and IB blames it on DB, I'd simply tell them you DK the trade, close your account and sue them for the money. Sounds like IB and DB should make it up to you.

    Your lawyer will subpoena everyone's records for a deposition. Once IB and DB see you're serious, I would guess they settle quickly.

    IMHO, at worst, its mutual error and you can split the amount, but you should never have to wait that long for a notification.

    If all the players point at their docs and say, "Tough luck", tell them they know the risks of trading and a 38 minute delay appears to be negligent. See you in court.


     
    #33     Apr 27, 2006
  4. that's somewhat besides da point if da order don't show on da tws window'n'doesn't appear on da trail or on trades confirmation: it is possible to miss da change in colour if it happens fast, i don't know if he checked on 'trades' window but am not willin' to speculate until we know da whole story.
     
    #34     Apr 27, 2006
  5. Htrader,
    let me first note that I have great respect for your postings and opinions and your presentation of facts, and I always look forward to reading a post with your name on it.

    It is not true that cancelled orders always disappear from the TWS. This is a user-selectable option. I don't allow my cancelled orders to disappear automatically. I don't want a cancelled order to disappear until I see the red code confirming I am out. This is why I set my TWS to keep cancelled orders displayed until I first observe them and then hit a hotkey to clear them manually from the TWS.

    I seem to recall reading, in IB documentation, that the disappearance of an order from the TWS does not imply that a cancellation request was successful, and that the customer is still responsible for making sure he receives a confirmed out on an order, even after it disappears from the TWS. If you have contrary information, that the customer may rely on the automatic disappearance of an order, from the TWS, as confirmation that a cancellation request was successful, then I would very much appreciate your educating me by providing me with a pointer to the source of your info, so that I can verify it. I would also then owe an apology to the originator of this thread.
     
    #35     Apr 27, 2006
  6. bitrend

    bitrend

    I agree that software release should be attached with good documentation. The point is what the good document can help if the person doesn't want to read it. :D

    By the way, did it say canceled or canceling? I had a similar problem with TD the status was still canceling but after calling my broker he confirmed that the order got fully filled. You need a canceled status, not canceling status, to be sure the order has been officially canceled.

     
    #36     Apr 27, 2006
  7. It is irresponsible to issue a request to cancel an order, and then to just forget about it, before receiving confirmation that the cancellation request was successful. It is irresponsible to trade without knowing how the trading platform would represent such a confirmation to the customer. I would also that IB's generally poor documentation is also an example of irresponsibility, and that it may have contributed to the customer's failure to catch it immediately, instead of 40 minutes later when the trade notification reached his TWS.
     
    #37     Apr 27, 2006
  8. Please see my earlier post, Htrader. I would really appreciate it you can provide me with some info source to verify your interpretation of TWS behaviour.
     
    #38     Apr 27, 2006
  9. I seem to recall reading warnings that sometimes, failed cancellations do not turn pink and stay in TWS, so that the customer must ensure that he gets a confirmed out message (red-colored order status). I am eager to see any verification from IB you can provide on this question, as I previously posted.
     
    #39     Apr 27, 2006
  10. Maybe you are legally correct, tomcole, but certainly this is not the way things are presented in the customer agreement we signed with IB. Perhaps you are correct that the agreement doesn't really matter in this situation. I wonder.

    I think IB should clarify how it does things, and how it believes its customers should do things, with respect to cancelling orders and then handling situations such as this one.
     
    #40     Apr 27, 2006
Thread Status:
Not open for further replies.