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.

258<br />

The following day, Javier Martin-Artajo, head of the CIO’s equity and credit trading<br />

operations, wrote to Ms. Drew, describing how JPMorgan Chase’s response to the press articles<br />

was successfully reducing market pressure:<br />

“Ina, the market is quiet today. To[o] early to tell but so far about flat P/L<br />

[profit/loss]. The tension has stopped now. The bank’s communications<br />

yesterday are starting to work. I hope that it keeps this way tomorrow.” 1453<br />

At the end of that day, the CIO reported a final loss total of only $6 million, compared to<br />

1454<br />

$415 million in losses the prior day, and $5 million the next day, which seemed to<br />

confirm that the bank’s communications were calming the market.<br />

The next day, April 13, 2012, one week after the initial news reports about the SCP,<br />

JPMorgan Chase filed a Form 8-K with the SEC and held an earnings call with analysts,<br />

investors, the media, and others to discuss its expected first quarter earnings. The bank’s filing<br />

1455<br />

and written materials did not address the SCP or the whale trades directly, but Mr. Braunstein<br />

volunteered a number of comments about them during the earnings call.<br />

On the call, Mr. Braunstein stated that he wanted to “talk about the topics in the news<br />

around CIO, and just sort of take a step back and remind our investors about that activity and<br />

1456<br />

performance.” In his remarks, Mr. Braunstein described the CIO and its excess deposits<br />

portfolio. He then went on to state:<br />

“[W]e also need to manage the stress loss associated with that portfolio, and so<br />

we have put on positions to manage for a significant stress event in Credit. We<br />

have had that position on for many years and the activities that have been reported<br />

in the paper are basically part of managing that stress loss position, which we<br />

moderate and change over time depending upon our views as to what the risks are<br />

for stress loss from credit.<br />

All of those decisions are made on a very long-term basis. They are done to keep<br />

the Company effectively balanced from a risk standpoint. We are very<br />

comfortable with our positions as they are held today.<br />

And I would add that all of those positions are fully transparent to the regulators.<br />

They review them, have access to them at any point in time, get the information<br />

on those positions on a regular and recurring basis as part of our normalized<br />

1453<br />

4/11/2012 email from Javier Martin-Artajo, CIO, to Ina Drew, CIO, “Single names CDS basis relative to IG 9<br />

CDS – URGENT update,” JPM-CIO-PSI-H 0002340 (emphasis in original).<br />

1454<br />

See chart, prepared by the Subcommittee and printed in Chapter IV, tracking SCP’s daily reported profit and<br />

loss (P&L) from January 3 to May 15, 2012, derived from an OCC spreadsheet, OCC-SPI-00000298-304, at 302.<br />

Numbers do not reflect restated P&L figures after JPMorgan Chase’s restatement in July 2012. It is unclear whether<br />

the CIO calculated these losses using midpoint prices or more favorable prices to minimize the total reported losses.<br />

1455<br />

The 8-K filing did, however, contain a chart tracking the CIO’s VaR totals, as discussed below. See 4/13/2012<br />

JPMorgan Chase & Co., Form 8-K, at 42, http://files.shareholder.com/downloads/ONE/2063348229x0xS1193125-<br />

12-161533/19617/filing.pdf.<br />

1456<br />

4/13/2012 “Edited Transcript JPM - Q1 JPMorgan Chase & Co. Earnings Conference Call,” at 7, JPM-CIO-PSI<br />

0001151.

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

Saved successfully!

Ooh no, something went wrong!