17.03.2013 Views

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

77<br />

asked the OCC about those losses, the OCC explained that the bank had not informed it of either<br />

the losses or the new trading strategy at the time, but since the CIO was already losing money<br />

with its trading strategy, the traders should have stopped, rather than expanded its use. 487 The<br />

OCC further told the Subcommittee that the CIO apparently did not stop, because it did not want<br />

to take the additional, short-term losses that would have resulted from simply reducing the size<br />

of the SCP. 488<br />

The losses continued for the rest of January, including after Mr. Iksil began to execute the<br />

January 26 strategy and increase the size of the SCP book. On January 30, 2012, Mr. Iksil sent<br />

his supervisor, Mr. Martin-Artajo, an email warning of additional losses and poor liquidity in the<br />

credit markets, and seeking guidance on what to do. He noted that the trading strategy called for<br />

purchasing more credit instruments – adding “notionals” – which “increase[d] the issues with the<br />

risks and the size” of the portfolio.<br />

“[W]e have to report a loss in the widening today, much less because the book has<br />

a long risk bias. Comes month end and we cannot really prevent the forward<br />

spreads from moving up .... To trade ... is costly and leads to increase in<br />

notionals. We need to discuss at this stage I guess: All I see is that liquidity is so<br />

poor that we just add notionals with the stress. So that improves the outright final<br />

P&L [profit and loss] number but this increases the issues with the risks and the<br />

size, as well as our sensitivity to price moves and trading costs .... [T]he only one<br />

I see is to stay as we are and let the book simply die ....” 489<br />

In his email, Mr. Iksil singled out the “poor” liquidity then in the market, which meant<br />

that he had difficulty locating buyers for the SCP’s assets. He also alluded to how purchasing<br />

long credit instruments meant the book received premium payments from the short parties which<br />

“improve[d] the outright final P&L number,” but at the same time increased the size of the<br />

portfolio and its “sensitivity to price moves and trading costs.” In other words, buying new long<br />

positions brought in more valuable positions as well as cash carry that could be used to offset the<br />

book’s daily losses, but it also increased the portfolio size which meant that even small price<br />

drops rolled into large daily losses. After noting the tradeoffs between the portfolio’s increasing<br />

size and risk of loss, Mr. Iksil wrote that in his view the “only” course of action was “to stay as<br />

we are and let the book simply die.” In other words, he advocated against buying additional<br />

credit positions and allowing the existing positions to expire with the attendant losses.<br />

In the same January 30 email, Mr. Iksil expressed concern about the danger of taking on<br />

ever-increasing positions under the new trading strategy:<br />

“[T]he control of the drawdown [loss] now is generating issues that make the<br />

book only bigger in notionals …. [T]he notionals become scary and [the] upside<br />

is limited unless we have really unexpected scenarios. In the meantime, we face<br />

487<br />

Subcommittee interview of Mike Sullivan, OCC (8/30/2012).<br />

488<br />

Subcommittee interview of Doug McLaughlin, OCC (8/30/2012).<br />

489<br />

1/30/2012 email from Bruno Iksil, CIO, to Javier Martin-Artajo, CIO, “update on core credit book,” JPM-CIO-<br />

PSI 0001223.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!