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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

larger and larger drawdown pressure versus the risk due to notional increase.<br />

Please let me know the course of action I should take here.” 490<br />

The Subcommittee was unable to locate any written record of any guidance provided by<br />

Mr. Martin-Artajo in response.<br />

That same day, January 30, 2012, Mr. Macris sent an email to Mr. Martin-Artajo also<br />

expressing concern about the ongoing losses:<br />

78<br />

“We need to discuss the synthetic book. The current strategy doesn’t seem to<br />

work-out. The intention was to be more bullish, but the book doesn’t behave as<br />

intended . . . . The financial [p]erformance is worrisome.” 491<br />

In hindsight, it appears that the CIO essentially took the trading strategy that had worked<br />

during the bear market of the second half of 2011, and applied it to the bull market in the early<br />

492<br />

part of 2012, with disastrous results. Not only did the SCP’s short positions lose value as the<br />

economy improved, but the long credit protection the CIO purchased for investment grade<br />

companies did not increase in value as much as was needed to offset the losses. As Mr. Macris<br />

put it, the investment grade rally “lagged” the high yield rally. 493<br />

That meant that the mark-tomarket<br />

profits the CIO was able to post on the investment grade credit protection it sold was<br />

insufficient to offset the mark-to-market losses it had to post on the high yield protection they<br />

purchased.<br />

Mr. Iksil later told the JPMorgan Chase Task Force investigation that he had not been<br />

able to sell as much credit protection as he would have liked (which would have generated more<br />

carry and profits to keep pace with the high yield rally). He said that two risk metrics – the<br />

“VaR” and “CS01” – prevented him from doing so. He later wrote in an email: “[T]he need to<br />

reduce VAR – RWA and stay within the CS01 limit prevented the book from being long risk<br />

enough.”<br />

494<br />

However, had Mr. Iksil actually acquired even more long positions, it is unclear<br />

that he would have been able to offset the losses then being reported on the books; it is possible<br />

he would have dug the SCP hole even deeper.<br />

(2) February 2012<br />

Despite the concerns expressed by Mr. Iksil and Mr. Macris about the SCP trading<br />

strategy, the CIO traders continued to pursue it throughout February, acquiring even more credit<br />

490<br />

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

PSI 0001223.<br />

491<br />

1/31/2012 email from Achilles Macris, CIO, to Javier Martin-Artajo, CIO, “Core book P&L drawdown and main<br />

exposures,” JPM-CIO-PSI 0000221.<br />

492<br />

See, e.g., 1/31/2012 email from Bruno Iksil, CIO, to Javier Martin-Artajo, CIO, “Core book p&l drawdown and<br />

main exposures,” JPM-CIO-PSI 0000222 (forwarded to Achilles Macris and subsequently Ina Drew).<br />

493<br />

JPMorgan Chase Task Force interview of Achilles Macris, CIO (partial readout to Subcommittee on 9/6/2012).<br />

494<br />

3/29/2012 email from Bruno Iksil to Javier Martin-Artajo, “First draft of the presentation,” conveying “CIO<br />

Synthetic Credit Update” (3/2012) at JPM-CIO-PSI 0001256. As discussed below, Mr. Iksil was not able to start<br />

selling protection in earnest until a new VaR model entered into force on January 30, retroactive to January 27. He<br />

similarly was constrained by the CS01 limit which the SCP ultimately breached in February. For more information<br />

on these limits, see Chapter V.

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

Saved successfully!

Ooh no, something went wrong!