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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

140<br />

Despite the extent and number of these collateral disputes generating questions about the<br />

CIO’s valuation process in March and April 2012, Ms. Drew and other JPMorgan personnel told<br />

the Subcommittee that the bank remained unaware at that time of the deliberate mismarking of<br />

the CIO’s books.<br />

On April 27, 2012, JPMorgan Chase sent its Deputy Chief Risk Officer Ashley Bacon to<br />

the London CIO office to examine the marks in the SCP book. Mr. Bacon told the<br />

Subcommittee that, sometime in May, he required the CIO to mark its positions at the midpoint<br />

and to use the same independent service used by the Investment Bank to value its derivative<br />

positions. 800 This change in valuation methodology erased the differences between the CIO and<br />

Investment Bank valuations and ultimately resolved the collateral disputes with Morgan Stanley<br />

and other counterparties by the end of May. 801<br />

D. Reviewing the SCP Valuations<br />

The Valuation Control Group (VCG) of the Chief Investment Office was charged with<br />

reviewing the accuracy of the CIO’s marks at both month-end and quarter-end. In April 2012,<br />

the CIO VCG conducted its regular review of the SCP book as of the last day in March. 802 That<br />

same month, the bank conducted a special, four-month assessment of the CIO’s P&L figures,<br />

from January to April 2012, essentially reviewing the VCG’s work. According to the bank, this<br />

special assessment was performed by “a combination of individuals from CIO Finance, the<br />

Firm’s internal accounting department, valuation experts from the Investment Bank, and<br />

others.” 803 The effort was headed by the bank’s Controller, Shannon Warren. 804<br />

The assessment<br />

uncovered evidence that the CIO, rather than marking at the midpoint, had used more<br />

“advantageous” prices, had exceeded some variance limits, and used increasingly “aggressive”<br />

marks over the course of the quarter. It also reported that, by the end of the quarter, the CIO had<br />

reported $512 million less in losses than it would have reported using midpoint prices. At the<br />

same time, because the CIO had generally used prices that fell within the relevant bid-ask spread<br />

for the derivatives being valued, the Controller validated the CIO’s quarter-end credit derivative<br />

marks as “consistent with industry practices” and acceptable under bank policy, and offered no<br />

criticism of its valuation practices.<br />

VCG Deficiencies. At the time that the VCG conducted its regular review of the SCP<br />

prices and the Controller’s office conducted its special assessment, the CIO VCG itself was<br />

under criticism. On March 30, 2012, JPMorgan Chase’s internal audit group released a report<br />

criticizing the VCG, noting among other problems that it was using unreviewed risk models,<br />

unsupported and undocumented pricing thresholds, inadequate procedures for evaluating pricing<br />

800<br />

Subcommittee interview of John Hogan and Ashley Bacon, JPMorgan Chase (9/4/2012).<br />

801<br />

Id. See also Subcommittee interview of Douglas Braunstein, JPMorgan Chase (9/12/2012) (Mr. Braunstein:<br />

“Ashley Bacon abandoned the traders marks in early May because we directed them to mark at the mid. The<br />

collateral disputes were noise in the markets that could be problematic.”).<br />

802<br />

See 2013 JPMorgan Chase Task Force Report, at 54.<br />

803<br />

Id. at 73.<br />

804<br />

Ms. Warren issued the memorandum summarizing the assessment. See 5/10/2012 JPMorgan Chase Controllers<br />

special assessment of CIO’s marks, January to April 2012, JPM-CIO 0003637-654.

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

Saved successfully!

Ooh no, something went wrong!