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.

198<br />

(3) Ignoring Repeated Breaches of Credit Spread Risk Limits<br />

The VaR and CRM results were not the only risk metrics that warned the CIO of<br />

increasing risk in the Synthetic Credit Portfolio. So did two additional risk metrics that<br />

JPMorgan Chase used to track how its portfolios would perform based on changes in “credit<br />

spreads,” meaning risks linked to changes in credit derivative premiums. The credit spread risk<br />

limits were repeatedly breached in January and February 2012, with the SCP exceeding the limit<br />

by 100% in January, by 270% in early February, and by more than 1,000% in mid-April. But<br />

instead of heeding those risk warnings, which came on top of the VaR and CRM warnings, the<br />

CIO traders, risk managers, and management criticized the credit spread risk metrics as faulty<br />

and pushed for them to be replaced.<br />

The two credit spread risk metrics were known within the bank as, first, “Credit Spread<br />

Widening 01” (CS01), also often referred to as “Credit Spread Basis Point Value” (CSBPV) or<br />

Spr01; and second, the “Credit Spread Widening 10%” (CSW10%). As with VaR, each of these<br />

metrics produced a dollar value signifying the amount of money that could be lost by a portfolio<br />

in a single day under specified market conditions. The bank established the CS01 and CSW10%<br />

risk limits for the CIO. 1106<br />

(a) Breaching CS01 Risk Limit<br />

The Synthetic Credit Portfolio first breached the CS01 risk limit in January 2012. 1107 To<br />

understand how the CS01 works, it helps to understand how positions on a credit index are<br />

priced. Most credit positions operate somewhat like insurance. 1108<br />

The “short” party makes<br />

periodic premium payments to the “long” party over a specified period of time to obtain credit<br />

protection. If a “credit event” like a bankruptcy or loan default takes place during the covered<br />

period, the long party is required to make a sizeable payment to the short party.<br />

The amount of the premium payments paid by the short party is typically expressed in<br />

basis points. A basis point is equal to one-hundredth of one percent. So if the CIO purchased a<br />

$1 billion short position in a credit index for 150 basis points, the CIO was required to pay its<br />

long counterparty $15 million per year (1.5% of $1 billion) for the credit protection.<br />

Credit positions are often priced by looking at the amount of position’s premium<br />

payment, also called the “coupon” payment or “credit spread.” If the credit spread “widens,” as<br />

happens in a worsening credit environment, it means the value of the existing short position<br />

increases, because the premium amount that was contractually agreed to be paid for the existing<br />

position will be less than the premium required to obtain the same credit protection in the<br />

worsening marketplace. If the credit spread “narrows,” as happens in an improving credit<br />

environment, the value of the existing short position falls. That’s because the premium amount<br />

paid for that existing short position will likely be greater than the premium that could be paid to<br />

obtain the same type of credit protection in the improving market. In addition, because credit<br />

1106<br />

Subcommittee interviews of Ina Drew, CIO (9/7/2012, 12/11/2012).<br />

1107<br />

See 1/20/2012 email from Keith Stephan, CIO, to Irvin Goldman, CIO, and others, “Breach of firm var,” JPM-<br />

CIO-PSI 0000141.<br />

1108<br />

For more information about credit products, see Chapter II.

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

Saved successfully!

Ooh no, something went wrong!