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.

sources, and inadequate procedures for requiring reserves. 805 For example, the internal audit<br />

report rated the following as “Needs Improvement” 806<br />

:<br />

141<br />

“CIO VCG practices where a number of risk & valuation models have not been<br />

reviewed by Model Review Group and included the absence of a formally applied<br />

price sourcing hierarchy, insufficient consideration of potentially applicable fair<br />

value adjustments (e.g. concentration reserves for significant credit indices<br />

positions) and the lack of formally documented/consistently applied price testing<br />

thresholds.” 807<br />

With respect to price testing “thresholds,” which determined how much a booked value could<br />

deviate from a specified midprice, the internal audit report concluded that the CIO VCG<br />

thresholds had been applied “without sufficient transparency or evidence.” It also found that the<br />

“root cause” of the problems with the CIO VCG’s price testing practices was an “insufficient<br />

assessment/formalization of certain price testing methodologies and poorly documented CIO<br />

VCG practices.” 808<br />

The audit report should have encouraged the VCG to conduct a more careful review of the CIO<br />

valuations at quarter’s end. In addition, the CIO itself was experiencing an unusual series of<br />

escalating losses and an unprecedented amount of collateral disputes, both of which also should<br />

have raised red flags about the CIO’s valuations and led to a more careful review. Adding still<br />

more sensitivity was that both the VCG quarter-end review and the Controller’s special<br />

assessment were undertaken in April 2012, just after the whale trades attracted media attention<br />

and raised multiple concerns within the bank.<br />

Controller’s Assessment. The Controller’s office began its work reviewing the CIO’s<br />

marks in early April 2012. In a late April email responding to a bank colleague’s inquiry into the<br />

CIO’s valuation practices, an analyst described how the CIO had valued the SCP positions in<br />

March:<br />

“There were differences between the [CIO] desk and the independent marks at<br />

month end. The desk marked the book at the boundary of the bid/offer spread<br />

depending on whether the position was long or short. We then applied a tolerance<br />

to make sure the prices were within tolerance and the majority of positions were.<br />

805<br />

See March 2012 Continuous Audit Quarterly Summary of Global Chief Investment Office, OCC-SPI-00033688,<br />

at 692.<br />

806<br />

JPMorgan’s internal audit group used three ratings in its reports: Satisfactory, Needs Improvement, and<br />

Inadequate. “The latter two are considered ‘adverse’ ratings.” 2013 JPMorgan Chase Task Force Report, at 55,<br />

footnote 69.<br />

807<br />

See March 2012 Continuous Audit Quarterly Summary of Global Chief Investment Office, OCC-SPI-00033688,<br />

at 692. The internal audit report also noted that the CIO’s London office was “using unapproved models in the<br />

calculation of risk including VaR,” and that “associated risk measurement methodologies ha[d] not been<br />

appropriately documented and or catalogued.” Id.<br />

808<br />

Id. See also 2013 JPMorgan Chase Task Force Report, at 55-56.

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

Saved successfully!

Ooh no, something went wrong!