JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES
JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES
JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
229<br />
understanding: “We were informed at year end 2011 that they were going to ‘take the book<br />
down, reduce the risk.’ That meant getting RWA down. My understanding, in my mind, they<br />
were going to reduce the book.” 1288 When asked about his statements to the OCC during the<br />
January 2012 meeting, Mr. Wilmot told the Subcommittee that when he spoke of “decreases,” it<br />
was only in terms of RWA, and that he was unaware of the tactics the CIO traders planned to use<br />
to decrease the RWA. 1289<br />
Yet, a few days earlier on January 26, 2012, the CIO traders had proposed lowering the<br />
SCP’s RWA, not by reducing the size of the trading book, but by purchasing increased amounts<br />
1290<br />
of long credit instruments to offset the book’s short positions. The notes of the quarterly<br />
meeting do not contain any reference to that proposal, and the OCC examiners informed the<br />
Subcommittee that the bank never raised it. 1291<br />
Because the bank’s strategy for reducing the<br />
CIO’s RWA – by adding long positions – would increase risk, and because it was contrary to<br />
usual practice for “decreasing” the portfolio, JPMorgan Chase should have told the OCC about<br />
its plans at the time.<br />
Moreover, at the time of the quarterly meeting on January 31, 2012, CIO trader Bruno<br />
Iksil had already informed CIO management that the SCP had lost $100 million and was<br />
1292<br />
expected to lose another $300 million. Together, that huge loss would eliminate the CIO’s<br />
entire fourth quarter 2011 gains and, according to the OCC examiner, constituted “material”<br />
information that the bank should have shared, but which Mr. Wilmot did not disclose. 1293 Mr.<br />
Wilmot told the Subcommittee that, even though he was the CIO’s Chief Financial Officer, he<br />
did not review the SCP’s daily profit and loss numbers, and that even if he had, the profits and<br />
losses for the book would have “moved around.” 1294<br />
It was the first of many SCP losses that the<br />
bank did not disclose to the OCC, but should have.<br />
The bottom line is that the OCC’s quarterly meeting with the CIO took place at a critical<br />
time. Had the CIO disclosed the size, risk profile, losses, and plans for the SCP to its regulator<br />
during the January 2012 meeting – rather than downplayed the portfolio by saying the CIO<br />
planned to reduce it – the OCC could have evaluated the trading strategy and raised questions<br />
about the rapid expansion in size and risk that took place over the next two months and later led<br />
to multi-billion-dollar losses.<br />
1288<br />
Subcommittee interview of Scott Waterhouse, OCC (9/17/2012).<br />
1289<br />
Subcommittee interview of John Wilmot, CIO (9/11/2012).<br />
1290<br />
1/26/2012 email from Bruno Iksil, CIO, to Andrew Perryman, CIO, “credit book last version,” JPM-CIO-PSI<br />
0000159, conveying “Core Credit Book Highlights,” (1/2012), prepared by Mr. Iksil; Subcommittee interview of<br />
Peter Weiland, CIO (8/29/2012). For more information about this proposal and its approval, see Chapter III.<br />
1291<br />
Subcommittee interview of Scott Waterhouse, OCC (9/17/2012). Subcommittee interview of Jaymin Berg, OCC<br />
(8/31/2012).<br />
1292<br />
1/26/2012 email from Bruno Iksil, JPMorgan Chase, to Julien Grout, JPMorgan Chase, “credit book last<br />
version,” conveying “Core Credit Book Highlights,” (1/2012), prepared by Mr. Iksil, JPM-CIO-PSI-0000159. The<br />
$100 million in losses was also reported in the daily profit and loss reports recorded internally by the CIO.<br />
1293<br />
Subcommittee interview of Jaymin Berg, OCC (8/31/2012).<br />
1294<br />
Subcommittee interview of John Wilmot, CIO (9/11/2012).