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.
148<br />
that it was clear the CIO traders were “gaming the system.” 827 The OCC indicated that, by the<br />
end of March, the CIO traders were marking virtually all of the SCP positions at the very edge of<br />
“what they could get away with” and were booking “fictitious profits.” 828<br />
Yet neither the VCG<br />
nor the special assessment raised any objection to the SCP marks. The OCC disagreed that the<br />
SCP marks accurately reflected the fair market value of the SCP’s credit derivatives.<br />
The sole purpose of the Controller’s special assessment was to ensure that the CIO was<br />
accurately reporting the value of its derivative holdings, since those holdings helped determine<br />
the bank’s overall financial results. As part of its assessment, the Controller approved of the<br />
CIO’s failing to include $512 million in losses, which would have led to a 70% increase in the<br />
$719 million in SCP losses that the CIO did report. 829<br />
That the Controller concluded that the<br />
SCP’s losses could legitimately be reported at anywhere between $719 million and $1.2 billion<br />
at the end of March exposes the imprecise, malleable, and potentially biased nature of the credit<br />
derivative valuation process.<br />
The same prices upheld by the Controller had been privately disparaged by the CIO<br />
trader who played a key role in the marking process. In March 2012, Bruno Iksil called the SCP<br />
marks “idiotic.” 830 At another point, he said that his supervisor would have to “decide[ ] what<br />
we show. [B]ecause me, I don’t know anymore.” 831<br />
That type of undisciplined pricing process<br />
should not have received the bank’s seal of approval.<br />
The bank’s Controller could have but did not criticize the CIO’s valuation process or<br />
modify the reported derivative values, 832 based upon the “aggressive” nature of the prices, their<br />
failure to reflect the prices used in executed trades, or their role in minimizing the SCP losses.<br />
Instead, the bank’s Controller found that the CIO’s actions were “consistent with industry<br />
practices” and acceptable under bank policy. 833<br />
The Controller’s conclusion is all the more<br />
perplexing in light of the fact that the original authorization for the CIO to trade in derivatives<br />
indicated that the CIO would follow the Investment Bank’s lead on prices, since it was often a<br />
market-maker. If the CIO had done so, it would have effectively used the midpoint prices, and<br />
the price deviation between the CIO and Investment Bank would have been effectively<br />
eliminated. The Controller also failed to note that the CIO was not using the Investment Bank’s<br />
marks, contrary to the authorizing document, and that the two lines of business had very different<br />
valuations for the same credit derivatives.<br />
827 Subcommittee interview of Michael Kirk, OCC (8/22/2012).<br />
828 Id.<br />
829 JPMorgan Chase later restated its financial results to attribute $660 million in additional losses to the SCP by the<br />
end of March. See 7/13/2012 “Form 8-K,” JPMorgan Chase & Co., at 2,<br />
http://files.shareholder.com/downloads/ONE/2261741819x0xS1193125-12-301391/19617/filing.pdf.<br />
830 3/16/2012 transcript of a recorded telephone conversation between Julien Grout, CIO, and Bruno Iksil, CIO,<br />
JPM-CIO-PSI-A 0000162.<br />
831 3/23/2012 instant messaging session between Bruno Iksil, CIO, and Julien Grout, CIO, JPM-CIO 0003515-541,<br />
at 541.<br />
832 See 5/10/2012 JPMorgan Chase Controllers special assessment of CIO’s marks, January to April 2012, at 8,<br />
JPM-CIO 0003637-654, at 644 (“any difference between front office mark and the mid-market price may be<br />
adjusted, at CIO VCG’s discretion”).<br />
833 5/10/2012 JPMorgan Chase Controllers special assessment of CIO’s marks, January to April 2012, at JPM-CIO-<br />
0003646. See also 2013 JPMorgan Chase Task Force Report, at 55, 74.