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.
274<br />
standpoint. We are very comfortable with our positions as they are held<br />
today.” 1539<br />
When Mr. Dimon was asked about the Synthetic Credit Portfolio on April 13, he said that<br />
it “offset” other bank exposures:<br />
“It's a complete tempest in a teapot. Every bank has a major portfolio. In those<br />
portfolios, you make investments that you think are wise, that offset your exposures.<br />
Obviously, it's a big portfolio. … But at the end of the day, that's our job, is to invest<br />
that portfolio wisely and intelligently to – over a long period of time to earn income and<br />
to offset other exposures we have.” 1540<br />
A month later, during the May 10 business update call, Mr. Dimon three times described<br />
the Synthetic Credit Portfolio as a hedge:<br />
“[T]he synthetic credit portfolio was a strategy to hedge the Firm’s overall credit<br />
exposure, which is our largest risk overall …. We’re reducing that hedge. …<br />
The portfolio has proven to be riskier, more volatile and less effective [an]<br />
economic hedge than we thought.” 1541<br />
While their language varied, these communications all made the same point, which is that the<br />
SCP was a counterbalance to potential losses in other parts of the bank. Given the briefing<br />
materials executives had, however, it was inaccurate for the bank to describe the SCP as a hedge<br />
because it did not reflect the true nature of the portfolio and its potential for losses at that time.<br />
No Clear Offsets. As described in Chapter III, the purpose of the SCP was<br />
undocumented, unclear, and changed over time. 1542 The assets that the SCP was purportedly<br />
hedging were not identified or defined in writing, and calculating the size and nature of the<br />
hedge was treated as a “guesstimate.” 1543 Days before the April 13 earnings call, Mr. Dimon<br />
asked his colleagues, including Mr. Braunstein, for the correlation between the SCP and the<br />
portfolio the SCP was meant to hedge. 1544 Mr. Dimon told the Subcommittee that he did not<br />
recall if he received a response. 1545 Ms. Drew, who had told her colleagues she was “working on<br />
Jamie’s request for correlation,” 1546 told the Subcommittee that so many events were unfolding<br />
at the time, that she did not recall if the correlation analysis was sent to him. 1547<br />
The<br />
Subcommittee found no evidence that it was. Mr. Hogan also requested a correlation analysis to<br />
1539<br />
4/13/2012 “Edited Transcript JPM - Q1 JPMorgan Chase & Co. Earnings Conference Call,” at 7, JPM-CIO-PSI<br />
0001151.<br />
1540<br />
Id. at 10.<br />
1541<br />
5/10/2012 “Business Update Call,” JPMorgan Chase transcript, at 2, http://i.mktw.net/_newsimages/pdf/jpmconference-call.pdf.<br />
In addition, Mr. Dimon characterized the portfolio as a hedge five more times when responding<br />
to questions on the May 10 call.<br />
1542<br />
See Chapter III, section entitled “Purpose of the Synthetic Credit Portfolio: Undocumented, Unclear, and Subject<br />
to Change.”<br />
1543<br />
Subcommittee interview of Ina Drew, CIO (9/7/2012).<br />
1544<br />
See 4/11/2012 email from Ina Drew, CIO, to Jamie Dimon, JPMorgan Chase, and others, “updated,” JPM-CIO-<br />
PSI 0001077 (“[w]e are working on Jamie’s request for [c]orrelation of the credit book against the portfolio”).<br />
1545<br />
Subcommittee interview of Jamie Dimon, JPMorgan Chase (9/19/2012).<br />
1546<br />
See 4/11/2012 email from Ina Drew, CIO, to Jamie Dimon, JPMorgan Chase, and others, “updated,” JPM-CIO-<br />
PSI 0001077 (“[w]e are working on Jamie’s request for [c]orrelation of the credit book against the portfolio”).<br />
1547<br />
Subcommittee interview of Ina Drew, CIO (12/11/2012).