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.

187<br />

The newest VaR model “resulted in a reduction to average fixed income VaR of $26<br />

million, average Total IB [Investment Bank] VaR of $26 million, average CIO VaR of<br />

$17 million, and average Total VaR of $36 million” for the third quarter of 2012. 1051<br />

Bank officials told the Subcommittee that the new VaR model had the effect of reducing<br />

the bank’s overall VaR by 20%. 1052<br />

This action by the bank indicates that lowering VaR<br />

results by changing the VaR model is part of an ongoing pattern at JPMorgan Chase.<br />

(2) Ignoring Comprehensive Risk Measure<br />

The VaR was not the only risk metric that flagged the increasing risk in the Synthetic<br />

Credit Portfolio; nor was it the only risk metric that was disregarded. Another example of a risk<br />

metric that was triggered but disregarded by CIO traders, risk personnel, and management alike<br />

is the Comprehensive Risk Measure, or CRM. After the SCP exploded in size at the beginning<br />

of 2012, the portfolio’s CRM projected, at the end of February 2012, that the SCP risked losses<br />

totaling $6.3 billion. A key CIO risk manager immediately dismissed the CRM figure as<br />

“difficult for us to imagine” and “garbage.” The CIO’s senior risk analyst also attacked the<br />

CRM model as inaccurate and sought to game the method used to determine which SCP assets<br />

would be subjected to that model in order to produce the “optimal” – meaning lowest possible –<br />

CRM and RWA totals for the SCP.<br />

(a) Background<br />

CRM, like VaR, produces a dollar figure representing potential losses. While VaR<br />

quantifies possible losses over the course of day in the context of ordinary markets, CRM<br />

quantifies possible losses over the course of a year in markets undergoing a high level of stress.<br />

As the bank’s top quantitative analyst told the Subcommittee, CRM represents how much money<br />

a portfolio can lose in a worst case scenario over the course of a year, with a 99% level of<br />

confidence. 1053<br />

Along with VaR and several other risk metrics, CRM is a key component used to<br />

calculate a bank’s overall Risk Weighted Assets (RWA) which, in turn, is used to determine how<br />

much capital the bank is required to have on its books to absorb any losses generated by those<br />

assets. 1054 The CRM metric was created by Basel 2.5, “a complex package of international rules<br />

that imposes higher capital charges on banks for the market risks they run in their trading books,<br />

particularly credit-related products.” 1055<br />

Basel 2.5 established four new risk measures to help<br />

calculate RWA:<br />

1051 Id. at 98.<br />

1052 Subcommittee briefing by JPMorgan Chase (1/28/13) (Neila Radin).<br />

1053 Subcommittee interview of C. S. Venkatakrishnan, JPMorgan Chase (10/25/2012). A new federal regulation,<br />

that took effect on January 1, 2013, defines CRM as a measure of risk “over a one-year time horizon at a one-tail,<br />

99.9 percent confidence level, either under the assumption of a constant level of risk, or under the assumption of<br />

constant positions.” See 8/30/2012, Joint Final Rule, “Risk-Based Capital Guidelines: Market Risk,” Federal<br />

Register, at 53106, http://www.gpo.gov/fdsys/pkg/FR-2012-08-30/pdf/2012-16759.pdf.<br />

1054 Subcommittee briefing by JPMorgan Chase (8/15/2012).<br />

1055 5/14/2012 “Basel 2.5 Increases The Squeeze On Investment Banking Returns,” Standard & Poors publication,<br />

https://www.standardandpoors.com/ratings/articles/en/us/?articleType=HTML&assetID=1245334380388.

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

Saved successfully!

Ooh no, something went wrong!