Good to hear the other side of the story. Thanks.
Too bad for the lawyers...
Too bad for the lawyers...


Quote from ssblack:
If you fully reimbursed him for the loss, my absolute f#$&ing hats off to you. You did the right thing.
Quote from IBj:
19:55:57 Client submits multiple orders in various currencies. This is the first time we can know with certainty that the client is using and attending the TWS. Had he covered the GBP position at this time, the loss would have been roughly 12000 USD.
Quote from IBj:
SUMMARY / ANALYSIS
- IB's client agreement says that the client is responsible for any order he/she submits and, strictly speaking, the client did submit these orders. But sorry to disappoint all the people with their hands on the speed dial to their attorneys, IB really tries to run its business based on business principles, not legal nuances. We live in a litigious world, so protective agreements are the universal way to define exposure limits around which we are always free to improve.
- The double click of the client was an error but so what. It is not reasonable to expect someone to recognize this extraordinarily arcane situation. The TWS was patched to prevent this about a week after the problem was reported to the developers.
- IB will indeed compensate the client for loss. We will need to decide how to interpret the activity from 19:55 onwards to determine the amount. It is a problem that the risk was not covered when first recognized. IB's standard position in all trading issues is "manage your risk" because the market will not sit around waiting while we research a problem.
- We absolutely dropped the ball in responding to the client. The problem occurred on 9/18. He contacted us a few hours later and then contacted one of our developers with whom he has previously communicated on October 5. It was escalated and it actually even got to me (as I just am discovering going through the contact history now) but I seem to have misunderstood the problem and passed it to the wrong person. It simply got buried as new issues piled in behind. Not good. I apologize to Zzzap that we did not resolve this more promptly.
[/list=1]