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.

53<br />

Subcommittee for more complete RWA records, the bank responded that such records were not<br />

prepared and were not available, although a former CIO employee who worked on RWA models<br />

recalled that monthly RWA reports for CIO and SCP did exist. 328<br />

In any event, when Mr. Macris was asked about the 2011 effort to reduce the SCP’s<br />

RWA, he told the JPMorgan Chase Task Force investigation that, as a result of the trading<br />

strategy to reduce the RWA, by August 30, 2011, the SCP had “a long front leg and a short back<br />

329<br />

leg,” adding further complexity to the Synthetic Credit Portfolio. Mr. Macris also told the<br />

investigation that the traders – and he – knew they were using “dangerous” instruments. 330<br />

(3) 2011 SCP Profit From Bankruptcies<br />

In late 2011, the CIO engaged in a series of short term credit index tranche trades that<br />

ended up producing a large payoff for the bank. The trading strategy behind this gain was<br />

intended from its inception to last no more than four months, in sharp contrast to the type of long<br />

term, conservative investments often attributed to the CIO.<br />

According to the OCC and an internal CIO audit report, during the fall of 2011, the CIO<br />

placed a massive bet on a high yield credit index that tracked credit default swaps for 100 higher<br />

risk companies. 331 Beginning in September 2011, the CIO, through its trader Bruno Iksil, began<br />

to purchase the short side of several tranches of the index, building a short position that would<br />

pay off only if at least two companies declared bankruptcy or otherwise defaulted before the<br />

position expired on December 20, 2011. 332<br />

As the short party, the CIO was required to pay premiums to its counterparties, but the<br />

amounts required were not viewed by the CIO traders as significant since the position was<br />

expiring in less than four months. In addition, to offset the initial cost of buying the position as<br />

well as the cost of the ongoing premiums, the CIO purchased the long side of another credit<br />

index, the CDX.NA.IG9 which tracked investment grade companies. By taking the long side on<br />

that index, the CIO became the recipient of the premiums paid by its short counterparties and<br />

could use those incoming cash premium payments to offset other SCP costs.<br />

CIO RWA at start of 2012 was about $43 billion); 1/19/2012 email from Achilles Macris, CIO, to Ina Drew, CIO,<br />

and others, “Credit book Decision Table – Scenario clarification,” JPM-CIO-PSI 0000152 (indicating CIO RWA at<br />

start of 2012 was $43 billion).<br />

328<br />

Subcommittee interview of Patrick Hagan, CIO (2/7/2013). The Subcommittee also located some RWA data in<br />

the monthly Executive Management Reports prepared by the bank. See, e.g., December 2011 “Chief Investment<br />

Office – Executive Management Report,” OCC-SPI-00033116 at 8, 10; April 2012 “Chief Investment Office –<br />

Executive Management Report,” OCC-SPI-00033162 at 4.<br />

329<br />

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

330<br />

Id.<br />

331<br />

Subcommittee interview of Doug McLaughlin, OCC (8/30/2012); 2011 CA Quarterly Summary: Global Chief<br />

Investment Office 4 th Quarter CA summary,” OCC-SPI-00002483. See also JPMorgan Corporate Sector Executive<br />

Management Report (Full Year 2011 Actuals), JPM-CIO-PSI 0018046, at 26.<br />

332<br />

For more information on credit index tranches, see Chapter 2.

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

Saved successfully!

Ooh no, something went wrong!