Chapter 11
JPMorgan Chase and the “London Whale”

In 2012, JPMorgan Chase Bank (JPM Bank) lost $6.2 billion from trading activities of its Synthetic Credit Portfolio (SCP), a relatively obscure and seemingly innocuous London-based operation.409 These oversized losses immediately focused the attention of JPM’s most senior managers on why they occurred and how to prevent them in the future. They also riveted the attention of financial regulators and shareholders, as well as many others—and for good reasons. After the dust settled, two especially disturbing facts (i.e., speculation and misrepresentation) emerged. First, the SCP was created to hedge JPM’s credit risks, but its activities were clearly speculative and partly funded with federally insured customer deposits, which may have violated the “Volcker Rule” of the 2010 Dodd-Frank Act. Second, senior management intentionally misrepresented the SCP’s financial figures by hiding losses and manipulating important risk measures, leaving regulators, shareholders, and even key internal risk-managers clueless as to the size, nature, and purpose of the SCP’s positions and operations. These massive derivatives losses also exposed significant weaknesses in the effectiveness of U.S. financial regulations and regulators, but perhaps most disconcerting of all was the realization that gaps in JPM Bank’s management, reporting, and regulation were occurring on a much broader scale around the world.

The media blamed JPM’s losses on the “London Whale,” giving the impression that a lone rogue trader, such as Nick Leeson at Barings Bank (1994) or Jérôme Kerviel at Société Générale (2009), was responsible; but this was not the case. JPM’s failed strategies, financial manipulations, careless attention to risk management, and misrepresentations had the unmistakable fingerprints of senior management all over them. In short, it was not “a” London Whale who caused these losses but rather a “pod” of them, most of whom were upper-level managers located in London and New York.410

With its stellar reputation for risk management and performance under stressful financial conditions, why did JPM’s senior management allow the SCP to triple its size in three months during 2012, resulting in a speculative, complex, and illiquid portfolio of credit derivatives, with a notional value worth more than $157 billion? Why was the SCP allowed to persistently and massively breach risk limits while its senior managers stubbornly questioned and trivialized their relevance, significance, and soundness—especially when they were flashing warning signals so brightly? As for JPM’s main financial regulators, such as the U.S. Office of the Comptroller of the Currency (OCC), why was little or nothing done to stop the SCP’s high-stakes speculation before it reached stratospheric heights?

JPMorgan & Company, the CIO, and the SCP

To understand the “London Whale” fiasco, it is helpful to distinguish among JPMorgan Chase and Company (JPM or JPM parent), JPMorgan Chase Bank (JPM Bank), the Chief Investment Office (CIO), and the Synthetic Credit Portfolio (SCP):

JPM was the holding company

JPM Bank was a large commercial bank, which was a subsidiary of JPM

The CIO was part of JPM Bank

The SCP was under the supervision of the CIO411

In the United States, bank holding companies and commercial banks have different regulators. The main regulator of U.S. bank holding companies is the Federal Reserve – especially for matters dealing with capital requirements, inspections, and approvals of mergers and acquisitions. By contrast, the two main regulators of nationally chartered U.S. banks are the (1) OCC, an independent bureau of the U.S. Department of Treasury; and the (2) Federal Deposit Insurance Corporation, an independent agency created by Congress.

JPM and JPM Bank

In 2012, JPM had assets with a book value worth $2.4 trillion, making it the largest financial holding company in the United States, as well as the world’s largest derivatives dealer and credit derivatives trader. JPM’s main bank subsidiary, JPM Bank, was also the largest bank in the United States, having branches in twenty-three states. With historic roots in the nineteenth century, JPM started as a commercial bank and then evolved into the large and highly diversified company it is today. During the twentieth century, JPM’s growth was spirited by passage of the 1999 Gramm-Leach-Bliley Act, repealing the 1933 Glass-Stegall Act and permitting financial institutions to engage, once again, in both commercial and investment banking activities. JPM responded quickly and assertively by (1) merging with Chase Manhattan Bank (2000) and Bank One (2004); (2) acquiring Bear Stearns (2008), an investment bank; and (3) purchasing most of the banking operations of Washington Mutual (2008), a major thrift institution.

JPM (parent) had six lines of businesses, (1) Retail Financial Services; (2) Credit Card Services and Automobile Loans; (3) Commercial Banking; (4) Investment Banking; (5) Treasury and Securities Services; and (6) Asset Management, but none of them caused its $6.2 billion credit derivatives losses. Rather, the SCP caused them (see “The SCP” section, below).

The CIO

Prior to 2005, JPM Bank’s internal treasury department managed the risks of both its long-term and short-term assets. This changed in 2005 when the Treasury and CIO Office (CIO) was spun off as a separate group, with the intended purpose of focusing on JPM Bank’s long-term asset management. Short-term asset management remained the responsibility of the bank’s internal treasury department. Led by banking veteran Ina Drew, the CIO had a staff of about 425 people, including 140 traders located mainly in New York and London. Drew had direct reporting access to top management echelons of both JPM Bank and JPM Parent. Because the CIO was part of JPM Bank, its main regulator was the OCC, but oversight was loose because the CIO had no client-facing activities.

The CIO had two major responsibilities, optimizing the bank’s “excess deposits” and managing JPM Bank’s risks.

Optimizing the bank’s “excess deposits” meant temporarily investing customer-deposited funds which were sitting idle. In this role, the CIO’s key priorities were safety and stability. Consequently, it placed these excess funds in highly liquid (available for sale) assets, such as U.S. government securities and high-quality municipal, corporate, and mortgage-backed securities. The CIO managed nine different portfolios. Two of them were short-term, focusing on North American and international assets. Three were medium-term, focusing on strategic asset allocations, foreign exchange, and mortgage servicing rights. Finally, the CIO’s four long-term portfolios concentrated on funding the bank’s retirement liabilities and optimizing tax-advantaged investments of life insurance premiums, private equity, and relatively high-risk (stressed) investments.

The CIO’s second major responsibility was managing JPM Bank’s risks, particularly those related to liquidity, interest rates, foreign currency prices, credit quality, and other structural exposures.

From the beginning, the CIO’s mandate was nebulous and became even more so as it morphed over time, largely due to the Great Recession (December 2007–June 2009), which reorganized many of JPM Bank’s priorities. Threatened by the potential failure of both the U.S. and global financial systems, customer funds flowed massively into safe bank deposits. This flight to safety, combined with JPM’s acquisition of Bear Stearns and Washington Mutual Bank, greatly expanded JPM Bank’s customer deposit base. In 2008, alone, deposits rose by approximately $100 billion, and by 2012, the CIO found itself managing an investment portfolio worth approximately $350 billion, which would have ranked this office (alone) as the seventh largest bank in the United States.

The SCP

Because the CIO’s responsibilities included credit risk management, in 2006, the CIO’s International Chief Investment Officer, Achilles Macris, sought and won internal approval for a new business initiative, focusing on “credit trading.” Soon thereafter, the CIO had credit derivatives positions on individual securities, security indices, and security tranches.

JPM Bank’s credit derivative activities had a checkered history. Prior to 2006, they were in various parts of JPM Bank with (portfolio) names, such as the “EMEA Credit Tranche,” “CIO International Synthetic Tranche Book,” “Synthetic Credit Tranche Book,” “Tactical Asset Allocation Portfolio,” “Discretionary Trading Portfolio,” and “Mark-to-Market Overlay Portfolio.” To the average customer or investor, most (if not all) of these names were nebulous and confusing. It was not until 2008 that the “Synthetic Credit Portfolio” was created as part of the CIO.

More importantly for the London Whale saga is it was not until January 27, 2012 (roughly four years after its creation) that JPM Bank informed its main regulator, the OCC, about the SCP functioning as a separate portfolio. During 2011, the SCP grew by 1,175% (from $4 billion to $51 billion) and, by January 26, 2012, had already lost $100 million, with at least $300 million more expected to come. Despite its size and rapid growth, the CIO was still making major presentations in March 2012 without listing the SCP as one of its primary investment portfolios.

As late as April 2012, some senior managers within JPM knew little or nothing about the SCP’s activities and size. Whatever camouflage may have existed, the Wall Street Journal and Bloomberg News bluntly removed it on April 6, 2012, when they revealed the SCP’s enormous trading volumes and nicknamed its lead trader, Bruno Iksil, the “London Whale.” JPM Bank’s Operating Committee waited until April 13 to inform the Securities and Exchange Commission (SEC), and it was not until May, just a few days before JPM Bank disclosed the SCP’s initial $2 billion loss, that JPM Bank provided the OCC with detailed information on the portfolio’s positions, losses, and collateral disputes. These collateral disputes amounted to $690 million, involved ten different counterparties, and centered on disagreements over credit index valuations.

The SCP earned positive returns from 2006 to 2011. Therefore, its mandate did not come under intense internal scrutiny. A consensus view was JPM Bank created the SCP to hedge the bank’s tail-end risks, which are low-probability events that can have oversized negative financial consequences. There were considerable differences of opinion over exactly what the SCP’s responsibilities were supposed to be.

The SCP Time Line

Figure 11.1 summarizes the timing of major events surrounding the rise and fall of the SCP.

Figure 11.1: The CIO’s and the SCP’s Derivative Trading Time Line: 2006–2012

The CIO’s derivatives trading operations began in 2006, but the SCP was formally created in 2008. Between 2008 and 2011, the CIO raised and lowered the SCP’s risk limits in line with prevailing bank and market conditions. As a result, the SCP’s revenues fluctuated widely (see Table 11.1). Because the SCP was created to hedge JPM’s credit risks, it was a net buyer of credit protection (i.e., long credit protection).412 For this reason, rising market volatility (i.e., credit risk) during the Great Recession caused the SCP’s exposures to increase significantly. As these exposures rose, so did the SCP’s activities and revenues. In 2009 especially, the SCP’s earnings rose by more than 500 percent, when the portfolio cashed in its long credit protection positions on General Motors (GM), which had filed for bankruptcy.

Table 11.1: The SCP’s Revenues: 2008–2011

Year The SCP’s Revenues
2008 $170 million
2009 $1,050 million
2010 $149 million
2011 $453 million
Total $1,822 million$1.8 billion

Source: United States Senate Permanent Subcommittee on Investigations: Committee on Homeland Security and Governmental Affairs, Majority and Minority Staff Report. JPMorgan Chase Whale Trades: A Case History of Derivatives Risks and Abuses, Released in Conjunction with Permanent Subcommittee on Investigations, March 15, 2013.

When the CIO started its credit trading activities in 2006, JPM Bank assigned it a daily risk limit of $5 million, intentionally low to keep this office and its activities under close control, but these limits increased rapidly.413 In 2008, the SCP was created, and with time, limits on its credit derivatives trading were lifted. By 2010, global financial markets had become more tranquil, reducing JPM Bank’s need to use the SCP as a hedge. As a result, the CIO lowered the SCP’s daily risk limits to $50 million (Yes! It was “lowered” to $50 million from the entire CIO initial limit of $5 million), reducing the portfolio’s revenues. This sharp drop in revenues was accentuated by GM’s default in 2009, which eliminated this company from the SCP’s credit tranche positions. Together, these factors reduced the SCP’s revenues by nearly 86 percent (see Table 11.1).

The forecast JPM Bank made for calmer financial conditions did not last long. Storm clouds appeared on the horizon in 2011, spurred by fears of credit market deterioration and European financial uncertainty. As a result, the SCP’s risk limits were raised and revenues surged. Later that year, approximately $400 million of the portfolio’s gains came from its $1 billion bet that American Airlines (AA) would experience a credit event.

The year 2011 was also significant because it marked the beginning of a trading strategy at the SCP that involved buying short-term credit protection on high-yield, high-risk, noninvestment grade indices and financing the positions by selling protection on low-yield, low-risk investment-grade indices. This strategy proved effective until the end of the year but turned disastrously sour, in 2012, when the SCP modified it and dramatically enlarged its positions.

Despite its three-fold increased revenues during 2011, JPM decided to reduce the SCP’s exposures in 2012, for three reasons:

  1. Perceptions that international macroeconomic conditions were improving
  2. The need to reduce the bank’s risk-weighted assets to meet impending equity requirements
  3. The realization that profits earned in 2011 were not sustainable

First, the bank’s perception that international macroeconomic conditions were improving and Europe’s bubbling debt turmoil had diminished meant there was less need for the SCP to hedge JPM Bank’s credit risks. The SCP was ordered to reduce its positions, but this instruction was ignored. By March 2012 (just three months later), the SCP had grown by more than 300 percent to $157 billion.

Second, JPM Bank wanted to cut its risk-weighted assets (RWA) across all business lines.414 Due to the relatively high capital cost of derivative positions, the SCP’s RWA were costing JPM more capital than they were worth. During the last half of 2011, the SCP was able to reduce its RWA by $37 billion. During 2012, JPM Bank requested the SCP to reduce them by an additional $25 billion, but this request was ignored.

Risk Notepad 11.1
What Are Risk-Weighted Assets?

Banks are required to have equity in proportion to their risk-weighted assets (RWA). To calculate RWA, a bank multiplies its on-balance-sheet and off-balance-sheet assets by risk weights prescribed by the authorized regulator (e.g., central bank or government banking authority). For example, mortgages have a risk weight of 50 percent because borrowers tend to repay these loans. If a bank owned mortgages worth $100 million and had a capital requirement equal to 8 percent, it would need $4 million in equity (i.e., 50% × $100 million × 8%) to back those assets. By contrast, corporate loans have a risk weight equal to 100 percent. A $100 million corporate loan would need $8 million in equity backing it (i.e., 100% × $100 million × 8%). Because many factors enter into the calculation of a bank’s RWA, U.S. regulators do not mandate any specific model. As a result, banks have considerable discretion to develop and use the methods they prefer.

The amount of capital (i.e., equity and retained earnings) U.S. banks need to back their assets is heavily influenced by the Basel Accords (see Risk Notepad 11.2), a series of international agreements seeking to build a healthier global financial system. The Basel III Accord (2010) was especially important for JPM because it raised the minimum capital banks are required to hold and set liquidity standards. Basel III gave banks three years to comply with the new guidelines, meaning it was expected to be phased in starting in 2013. The Accord’s aim was to address some of the financial weaknesses revealed by the Great Recession and focus directly on capital adequacy, leveraged exposures, liquidity requirements, financial transparency, and the reduction of systemic risks. In anticipation of the Basel III requirements coming into force during 2013, JPM Bank wanted to reduce the SCP’s RWA in 2012.

Risk Notepad 11.2
What Are the Basel Accords?

Between 1988 and 2010, four Basel Accords were published: Basel I in 1988, Basel II in 1999, Basel II.5 in 2009, and Basel III in 2010. These accords were negotiated under the umbrella of the Basel Committee on Banking Supervision (BCBS), part of the Bank for International Settlements (BIS), located in Basel, Switzerland. Since World War II, the BIS has supported global financial safety and stability by means of international coordination among central banks. With each new accord, the BCBS has issued an updated set of capital guidelines, based on the premise that capital should back a bank’s RWA. The higher the risk, the greater the capital requirements against a certain asset class’s value.

The third reason JPM may have been keen to decrease the SCP’s positions in 2012 was knowledge that nearly 90 percent of the portfolio’s revenues in 2011 had been due to returns from a lucky billion-dollar trade on several high-yield, high-risk credit indices linked to the credit rating of American Airlines (AA). The bankruptcy of AA triggered, virtually overnight, a $400 million payment to the SCP. These revenues were so great, the SCP’s trading persistence so strong, and its positions so large that Bruno Iksil earned the nickname “caveman.” Why were these trades “lucky”? Iksil bought these positions in a soon-to-expire credit index series and just a few months later (on November 27, 2012), AA declared bankruptcy. Had this bankruptcy been declared just three weeks later (December 20), the SCP would have earned nothing because its protection contracts would have expired.415

What Went Wrong at the SCP?

The SCP’s $6.2 billion loss in 2012 was not just large, it was colossal, and the root cause can be attributed to JPM’s senior managers, who directed traders to speculate wildly on the top of a Matterhorn-sized mountain of existing credit derivatives positions.416 The mistakes JPM made can be classified under five major headings:

  1. Ignoring the SCP’s strategic purpose
  2. A failed trading strategy
  3. Disregarding JPM Bank’s internal and external risk measures
  4. Manipulating JPM Bank’s risk metrics instead of fixing the underlying problems
  5. Publicly misrepresenting the SCP’s financial condition

Mistake #1: Ignoring the SCP’s Strategic Purpose

From 2006 to 2011, the SCP’s activities seemed to be broadly and consistently in line with the strategic purpose for which it was created, namely to mitigate JPM Bank’s credit risks. JPM Bank’s loan portfolio exposed the company to credit risk; so, the SCP bought credit protection to hedge these positions. During the 2008–11 period, prices changed in ways that allowed SCP traders to earn revenues of $1.8 billion. Life was good because the SCP’s strategic purpose (i.e., hedging) dovetailed so nicely with evolving market conditions. When substantial losses were incurred in 2012, JPM took a second look at the SCP’s trades and positions, revealing many discomforting issues. U.S. Senate investigations that followed the SCP’s losses exposed even more.

As early as 2007, an internal audit labeled the SCP’s trading activities as “proprietary position strategies” (i.e., speculations, not hedges) and scolded the portfolio’s managers for their multiple calculation errors. In May 2012, five years later, an OCC bank examiner called the SCP a “make believe voodoo magic composite hedge.” Post-crisis testimony before U.S. Senate subcommittees uncovered wide differences of opinion among senior JPM managers about whether the SCP’s job was to hedge or speculate, whether its time horizon was short-term or long-term, and whether the portfolio was a conservative user of known trading strategies or a test-ground for new ones. This testimony also exposed considerable differences of opinion about whether the SCP was supposed to focus on controlling JPM Bank’s tail-end risks, the CIO’s risks, exposures of dedicated assets in JPM Bank’s balance sheet, or international positions.

Critics rightly asked: If the SCP was really hedging, then: Why weren’t its trades identified as such, beforehand, as they are supposed to be? Why weren’t they tracked and tested for effectiveness? Why did JPM Bank’s firm-wide risk managers know little or nothing about the SCP’s activities and have no role in creating, approving, coordinating, or executing its trades? Defiantly, one senior JPM Bank manager went so far as to criticize the OCC for expecting there to be a “reasonable correlation” between the SCP’s macro hedges and JPM’s assets. In his 2012 testimony before a U.S. Senate subcommittee, CEO Jamie Dimon asserted that the SCP’s purpose was to make “a little money” when market conditions were benign but be positioned to earn more significant returns if there was a credit crisis. By contrast, Ina Drew testified that the CIO’s (and, by inference, the SCP’s) mandate was to “optimize and protect the firm’s balance sheet from potential losses and create and preserve economic value over the long term.”

Table 11.1 shows the SCP’s record of success from 2008 to 2011. As satisfying as these returns must have been, scratching just slightly below the surface revealed a disturbing fact. SCP was not hedging; rather, it was speculating. In post-crisis investigations, no documents could be found detailing the SCP’s hedging objectives or strategies, and there were no records identifying the specific assets, portfolios, or tail-end events that this portfolio was supposed to protect. Nowhere was there information on the size, nature, or effectiveness of the SCP’s hedges. When asked for correlation estimates between changes in the value of the SCP’s holdings and any other JPM Bank activity, senior managers had none. Similarly, there was no justification for why the SCP’s hedges were treated differently from the CIO’s other hedges, such as mortgage servicing rights and interest rate hedges. Only weak justification could be given for why the SCP’s senior managers were compensated on the profits they earned, rather than the effectiveness of their hedges. Some CIO employees were among the highest paid workers at JPM. Summing just two years of compensation (2010 and 2011), the salaries of Achilles Macris, Ina Drew, Javier Martin Artajo, and Bruno Iksil amounted to $32 million, $29 million, $24 million, and $14 million, respectively. Most people in the world could live comfortably for the rest of their lives on what each of them earned in just one year.

Two additional pieces of information raised special concerns about the SCP’s true strategic purpose. First, between January and March 2012, the SCP’s balance sheet footings increased from $51 billion to $157 billion (i.e., more than 300%), totally out of line with changes in both the size and composition of JPM Bank’s loan portfolio. Second, instead of reducing its RWA by $25 billion (from $51 billion to $26 billion) during 2012, as directed, the SCP significantly increased them, costing JPM Bank millions of dollars in additional capital requirements.

Mistake #2: A Failed Trading Strategy

In 2012, JPM Bank ordered the SCP to reduce its credit protection positions. The most direct way to do so would have been to sell them at market value, but this option was dismissed quickly because the SCP had become such a large part of the market that finding counterparties to its trades would have adversely affected credit spreads, causing estimated losses between $400 million and $600 million. In retrospect, this would have been a bargain. To get an idea of how large the SCP was, consider this: In April 2012, the notional value of the SCP’s short credit protection positions was $836 billion and its long credit protection positions was $678 billion. Traders estimated that hedging these positions would take eight to fifteen days, assuming they had 100 percent of the daily trading volume. In some contracts, the SCP held more than 50 percent of open interest. Neutralizing so much in such a short period would have significantly narrowed credit spreads and increased the SCP’s losses.

Despite the order to reduce the SCP’s RWA, Ina Drew, who headed the CIO, complicated her traders’ strategic task by simultaneously requesting that they position the portfolio to earn profits from credit events caused by defaults of high-risk borrowers. It is likely that Drew had become accustomed to profits the SCP had earned since 2008 and was especially smitten by the $453 million gain in 2011, of which $400 million came from AA’s declared bankruptcy. Drew’s “competing and inconsistent priorities” led the SCP to implement a dangerous trading strategy, which was made even more so by its size.

By late January 2012, after brainstorming the conflicting goals facing them, the SCP’s senior managers and traders found (what they thought was) an answer that might satisfy both JPM Bank’s and Ina Drew’s orders. The strategy had two legs—front and back. Figure 11.2 shows this two-legged trading strategy and its net results. Notice that the top portion of the figure shows the strategy and the bottom portion its net results. The SCP’s strategy can be explained using two credit derivative contracts, a one-year (short-term) contract on non-investment grade securities maturing in 2012, and a six-year (long-term) contract on investment-grade securities maturing in 2017.417

Figure 11.2: The SCP’s Forward Strategy

Short-Term Front Leg

To satisfy Ina Drew’s wish that the SCP position itself to profit from adverse credit events, traders bought credit protection on non-investment grade credit indices and tranches maturing at the end of 2012 (i.e., with one-year maturities). Their hope was that these relatively high-yield, high-risk bets would, by chance, pay off, as they did with AA’s bankruptcy in 2011. The problem was finding a way to finance the new positions, which was a major reason the back leg became so important.

Long-Term Back Leg

The SCP had a financing problem larger than just funding its new one-year front leg. The portfolio also needed to finance: (1) the credit protection positions with which it entered 2012, (2) mounting losses, and (3) new positions. To solve these funding problems, the SCP sold credit protection on investment-grade credit indices and tranches maturing in 2017 (i.e., six-year maturities). As a result, during the first year (2012), the SCP paid credit spreads on the investment-grade, one-year credit protection positions bought prior to 2012 (i.e., long positions) and received credit spreads on the new six-year credit protection positions it sold (i.e., short positions). Because the short positions were larger than the long ones, the SCP earned net revenues for the first year. From the end of 2012 to 2017, the SCP’s short credit protection positions (i.e. the ones taken out at the beginning of 2012 and expired in 2017) were fully exposed because there were no existing investment-grade credit protection positions to offset them (see Figure 11.2). The result was clear. The SCP had turned itself from a net buyer of investment-grade credit protection into a net seller, meaning it was no longer hedging JPM’s credit risks, but increasing them.

Gearing problems

For the new strategy to work, the SCP had to scale the sales of its protection contracts to satisfy all its funding needs. This proved to be problematic because short-term and long-term credit indices do not always move in tandem. Not only do the different maturities cause problems, but the composition (i.e., constituent companies) in short-term and long-term credit derivatives indices differ, adding to the misalignment. In addition, the SCP had become its own worst enemy because its massive sales of credit derivatives adversely affected credit spreads, causing its revenues per contract to fall and complicating efforts to estimate the correct number of credit protection contracts to sell.

The SCP created arbitrage opportunities

At times, the SCP sales of credit protection were so large that credit spreads narrowed to the point where the cost to insure the entire credit index was less than the cost to insure its component parts (i.e., the single-name credit derivatives in the index). As a result, the SCP created arbitrage opportunities for its trading counterparties, such as Blue Mountain Capital, BlueCrest Capital, CQS, Hutchin Hill, Lucidus Capital Partners, and Saba Capital Management, and they responded in force, using three different strategies.

The first was to simultaneously buy inexpensive credit protection on investment-grade credit indices, at spreads made low by the SCP’s massive sales, and then sell protection on each of the individual securities in the index. The second was to purchase the underlying securities in the index and hedge their credit risks by buying credit protection at profitably narrow spreads, due to the SCP’s sales. If held to maturity, these trades should have ensured net profits. The final strategy was to speculate against the “London Whale.” Believing that credit protection spreads were artificially low and unsustainable, they bought underpriced credit protection and waited until credit spreads rose—and they did!

Results of the SCP’s Two-Legged Strategy

The SCP’s aggressive new strategy suffered losses almost immediately. On January 19, 2012, Eastman Kodak defaulted, resulting in portfolio losses of $50 million. With the SCP’s large holdings of long credit protection positions, one might have expected Eastman Kodak’s default to boost revenues, but the SCP was under orders to reduce its RWA. As a result, some of its risk positions (including Eastman Kodak) expired on December 20 and were not renewed. Similarly, on February 13, 2012, Ally Financial, Inc. announced bankruptcy preparations for Residential Capital LLC (ResCap), its mortgage subsidiary. Almost unbelievably, this announcement resulted in the SCP losing value on both its long and short positions.

The Eastman Kodak and ResCap defaults were not symptomatic of general market conditions. Overall credit health improved, causing credit spreads to fall, reducing the value of the SCP’s long credit protection positions on non-investment-grade indices, and decreasing the income it earned from sales of long-term investment-grade credit protection contracts. Finally, the SCP’s explosive trading resulted in a collection of approximately 100 different credit derivatives instruments, most on indices and tranches but each in need of monitoring and control. The level of complexity they added to the job of managing this already-complex portfolio increased the chances that the new strategy would run aground—and it did!

Table 11.2 shows the SCP’s monthly and quarterly losses from January to September 2012. Because virtually all its positions were transferred to JPM’s Investment Bank on July 2, 2012 and closed out as soon as possible, the reported losses end in September.

Table 11.2: The SCP’s Reported Mark-to-Market Losses, January–September 2012

Month or Quarter End Monthly or Quarterly Losses Cumulative Losses
(Year-to-Year)
January $100 million $100 million
February $69 million $169 million
March $550 million $719 million
April $1.413 billion $2.132 billion
As of May 15 $1.563 billion $3.695 billion
June Not available $4.4 billion
July restatement of first quarter losses $660 million $5.8 billion
September $449 million $6.2 billion

Source: JPMorgan Chase & Co., 2012 SEC filings; OCC spreadsheet, OCC-SPI-00000298. The PSI Report, pg. 94.

During January 2012, the SCP had losses on seventeen of twenty-one trading days, followed by losses on fifteen of twenty-one days in February, and sixteen of twenty-two trading days in March. The CIO’s and the SCP’s senior managers were perplexed but convinced that, with time, their new strategy would prove its worth. Partial relief came when the SCP was given permission by JPM Bank to unwind its existing positions “opportunistically.” But instead of reducing positions, the SCP doubled down and then tripled down by dramatically increasing long-term credit protection sales, causing the portfolio’s notional value to rise from $51 billion in January 2012 to more than $157 billion by the end of March—with $40 billion added in just a couple weeks during March.

Mistake #3: Disregarding JPM Bank’s Internal and External Risk Measures

Setting the SCP’s risk limits was supposed to be the combined responsibility of CIO head, Ina Drew, JPM Bank’s Chief Risk Officer, John Hogan, and the CIO’s Chief Risk Officer, but it was not until January 2012 that the SCP hired its Chief Risk Officer. Consequently, the SCP’s traders and risk managers both reported directly to Drew. These reporting lines created potential conflicts of interest. At JPM Bank, risk management and derivative trading decisions were supposed to be separated. Combining them removed important checks and balances from bank operations.

Under stressful conditions, the effects were easy to predict. From 2011 to April 2012, the SCP routinely breached its five most important risk limits (see Risk Notepad 11.3) and did so without internal or external repercussions. Instead of investigating, disciplining, and immediately reducing risks, JPM’s senior managers raised them for both the CIO and SCP and then trivialized these risk measures. There were periods in 2012 when the SCP breached all five of its major risk measures at the same time. Others were breached for long periods, and some violations were so blatantly large that they almost begged for intervention and supervision. For example, in January 2012, the SCP exceeded its CS01 limit (see Risk Notepad 11.3) by 100 percent, and then exceeded it by 270 percent in February and by more than 1,000 percent in April. On April 17, 2012, the CIO had exceeded its CS01 limit for seventy-one straight trading days. All totaled, during the first four months of 2012, the SCP breached its risk limits and advisories more than 330 times. An internal list of the many risk-limit violations was nine pages long.

Risk Notepad 11.3
The SCP’s Five Major Risk Measures

1. Value at Risk (VaR)

VaR measures the maximum loss a portfolio should sustain during a given time and level of confidence. A $50 million daily VaR with 99 percent confidence level means that for ninety-nine days out of 100, the bank should lose no more than $50 million, but there should be one day out of these 100, when losses exceed $50 million.

2. Credit Spread Widening 01 (CS01)

CS01 is also called the Credit Spread Basis Point Value (CSBPV) or Spr01. It measures the effect a one basis-point increase in credit spread should have on a portfolio’s value in one day. This measure is negative for protection sellers and positive for protection buyers.

3. Credit Spread Widening 10% (CSW10%)

CSW10% measures expected one-day changes in a portfolio’s value due to a widening of the credit spread by 10 percent. Because it shows relatively large (i.e., discrete) changes in risk, this measure is more reflective than CS01 of tail-end and stress-test losses.

4. Stress Loss Limits

Stress loss limits measure possible losses under extreme negative conditions that simultaneously affect all assets in a portfolio.

5. Stop loss advisories

Stop loss advisories are triggered when predefined loss levels are breached. In contrast to other risk measures, these advisories are sparked by actual losses relative to how much a portfolio can lose over a defined period (e.g., one, five, or twenty days).

By early 2012, the SCP had grown so large, its vulnerability so great, and strategy so poorly conceived and executed that the portfolio repeatedly breached both the CIO’s and the SCP’s risk limits. In fact, from January 16 to 19, the SCP’s disproportionate losses caused JPM Bank to exceed its value at risk (VaR) limits (see Risk Notepad 11.3)—a violation that triggered a “Level 1” notification within JPM.418 As a result, the violation was reported to JPM’s most senior managers, including Jamie Dimon and other members of JPM’s Operating Committee. In such cases, steps to reduce these exposures should have occurred immediately unless a temporary extension was approved.

JPM faced a decision. On one hand, it could have ordered the SCP to de-risk its portfolio. On the other, JPM could have raised the SCP’s VaR limits, but doing so would have also required raising them for both the CIO and JPM Bank (firm wide). CEO Jamie Dimon and Chief Risk Officer John Hogan decided to approve the request to temporarily raise JPM Bank’s firm-wide daily limits from $125 million to $140 million, and Ina Drew raised the CIO’s VaR limit to $105 million from $95 million. Nevertheless, on January 27, the SCP’s VaR reached $125.7 million, exceeding the newly raised limit for the CIO. These limit violations continued until January 30, 2012, when the SCP introduced a new VaR metric, immediately reducing the portfolio’s reported exposures by 50 percent.

Initially, the SCP’s exposures were tightly controlled by VaR, which restricted the portfolio’s losses with a 95 percent confidence level, to no more than $5 million per day (see Risk Notepad 11.3). This relatively diminutive VaR limit was imposed to reduce the risk the SCP might pose to JPM Bank. The potential threat was reduced further when the SCP was instructed to mark its positions to market, using the same credit spreads and valuation methodologies as JPM Investment Bank.

One of the most important risk measures for JPM Bank and its units was the Comprehensive Risk Measure (CRM), used to calculate JPM Bank’s RWA (see Risk Notepad 11.4). During January 2012, the CRM for JPM Bank rose from $2 billion to $3.2 billion, and in February 2012, it warned JPM’s senior executives that the SCP could cause year-end losses of $6.3 billion. No one at JPM Bank seemed to heed this warning. Instead of responding rapidly and decisively to this alarm, senior managers questioned, attacked, trivialized, and then ignored the CRM metric. More specifically, it was regarded as “garbage.”

Risk Notepad 11.4
Basel II.5 Accord’s Four New Risk Measures

The Basel II.5 Accord in 1999 created four risk measures that banks have used, ever since, to calculate their RWAs.419

  1. Comprehensive risk measure (CRM): CRM considers correlations among a portfolio’s assets and calculates possible yearly losses due to stressful credit conditions, such as defaults and credit migration risk. Credit migration risk is the possibility that a portfolio’s credit quality will materially worsen over time, without compensation to the seller because the pool’s component securities or loans are not repriced.
  2. Stressed value-at-risk (SVaR): SVaR is like the VaR measure, except it calculates results under financially unfriendly conditions.
  3. Incremental risk charge (IRC): IRC reflects the one-year default, credit migration, and recovery risks of unsecuritized credit products. It is usually calculated for a one-year period with a 99.9 percent confidence level. Relative to VaR, it is a better reflection of a portfolio’s liquidity.
  4. Charges for securitization and re-securitization positions: These measures take into consideration the significant growth in securitization and need to more precisely classify them.

A logical question to ask at this point is: “Where were the CIO’s risk managers while all of this was happening?” Before 2012, Peter Weiland was the CIO’s Senior Market Risk Officer, but JPM Bank’s job description focused his attention on ensuring that the CIO’s risk measures were correctly calculated and properly disseminated. In short, his responsibilities (or the way he interpreted them) were descriptive and not prescriptive or authoritative. Regrettably, it was not until January 2012 that CIO hired Irvin Goldman as its first Chief Risk Officer, but he was new to both the job and department and, therefore, did not react immediately and forcefully to the SCP’s risk limit breaches.

One risk metric that might have improved JPM’s supervision of the SCP and reduced losses is the concentration limit, a well-established fundamental risk management tool JPM Investment Bank was already using. Concentration levels measure exposures to specific counterparties, instruments, and indices. For example, calculating the Single Name Position Risk (SNPR, called “snapper”) measure would have shown the SCP’s gross positions. Because the SCP had mainly index and tranche positions, gross exposure measures masked individual company positions.

JPM Bank had not set up any concentration reserves for the SCP, even though it held more than 50 percent of the open interest in some index contracts. Its liquidity reserves were grossly inadequate and (apparently) misunderstood. In April 2012, JPM Bank’s Chief Financial Officer increased the CIO’s liquidity reserve from $33 million to $186 million, to reflect the pool of illiquid credit derivatives (especially credit tranche derivatives) held by the portfolio. When asked about liquidity reserves during her U.S. Senate testimony, Ina Drew professed not to know why provisions of $33 million were made for the SCP’s liquidity-reserve (not to mention the increase to $186 million), despite the fact that they reduced her unit’s revenues dollar for dollar.

Mistake #4: Manipulating JPM Bank’s Risk Metrics

As the SCP’s losses mounted, senior managers reacted by changing the CIO’s risk models to something “more sensible.” In its crosshairs were the Comprehensive Risk Measurement (CRM), Stressed Value at Risk (SVaR), and Value at Risk (VaR). Prior to 2012, the SCP had never exceeded its VaR limits, but that changed. Repeated violations in 2012 led senior managers to conclude that the SCP’s VaR measure was “too conservative.” Consequently, focus was put on developing a new VaR model, and by the end of January 2012, one had been created, internally approved, and implemented. Normally, new risk measures are back-tested and compared for several months to current models to determine their accuracy and to ferret out any mistakes. The CIO chose not to follow this procedure and implemented its new VaR measure immediately, without back testing and without correcting problems identified, beforehand, by JPM’s Model Risk and Development Office.

Where were internal controllers?

The new VaR had the effect of reducing, overnight, the SCP’s VaR by 50 percent, from $132 billion to $66 billion. It also reduced JPM’s RWA and JPM Bank’s required capital. Criticism of the SCP’s new risk model should have come from a May 2012 investigation by JPM’s Controller’s office, but astonishingly, even though the SCP had understated its losses by approximately $500 million, JPM’s internal investigators determined that its methods were “consistent with industry practices.” Criticism should have also come from the CIO’s Valuation Control Group, which was supposed to crosscheck and validate, monthly, the accuracy of the SCP’s derivatives valuations, but all was quiet on this front as well.

Where were Federal Regulators?

JPM Bank notified the OCC that it had developed a new VaR model but did not explain why the new estimation methodology was more accurate or appropriate than the old one and provided no explanation for why the SCP’s risks changed so dramatically from one day to the next. Problems with the new model quickly surfaced. First, it required manual data entry, reducing scalability and making the model prone to human error. Furthermore, it contained formula and calculation mistakes, making it inaccurate and undependable. In May 2012 when the SCP abandoned its new VaR measure, JPM Bank notified the OCC but did so without explanation.

Data Manipulation

Changing its VaR model was only a part of the effort SCP put into window-dressing its deteriorating positions. The staff also began manipulating financial data entered into the unit’s new VaR model. An unbiased way to calculate the value of a credit derivatives index or CDS is to average the bid and ask values from several independent dealers or to hire an outside valuation service to provide fair market values. The SCP decided that market-based, midpoint values were inferior to those reflecting its own traders’ perceptions of prevailing market conditions. So, the SCP began using more favorable valuations in late January 2012 and by July 2012, the estimated difference between the SCP’s free-wheeling (dealer perception) method and the usual consensus, midpoint-valuation method was a whopping $660 million! Not only did the SCP’s new VaR metric reduce VaR by 50 percent but also kept this risk measure 30 to 50 percent below the midpoint valuation method until it was abandoned and replaced by the old model in May 2012.

From its start in 2008, the SCP was supposed to coordinate with and use the same credit spreads and valuation methodologies as JPM Investment Bank, but this rule somehow got lost in translation. There were times when the SCP and JPM Investment Bank were on opposite sides of the same credit derivatives deal, each valuing it differently. Responsibility for marking the SCP positions to market fell on the shoulders of Julien Grout, a junior trader who was supervised by Bruno Iksil. Grout must have had his hands full. For example on March 23, 2012, recorded banter among the SCP’s traders estimated that daily losses would be between $300 million and $600 million, but Grout’s internal report showed only a $12.5 million loss for the day. The SCP ended its data manipulation in May 2012, when the unit was ordered to use JPM Investment Bank’s methodology.

Mistake #5: Publicly Misrepresenting the SCP’s Financial Condition

By March 2012, JPM’s senior management was well aware that the SCP was in trouble. Nevertheless, in mid-April, CFO Douglas Braunstein hosted a meeting in connection with an SEC filing (8-K Report) and earnings call. Braunstein tried to sooth investors’ angst by stating that the SCP’s:

Trading activities were made on a long-term basis

Function was hedging credit risks

Trades and positions complied fully with the Volcker Rule of the 2010 Dodd Frank Wall Street Reform and Consumer Protection Act (see Risk Notepad 11.5) because they were risk-mitigating

Positions were fully transparent to regulators

Risk Notepad 11.5
What Is the Volcker Rule?

Paul Volcker was Chairman of the U.S. Federal Reserve from August 1979 to August 1987. On February 6, 2009, President Barack Obama appointed him Chairman of the President’s Economic Recovery Advisory Board. The Volcker Rule, part of the Dodd Frank Wall Street Reform and Consumer Protection Act of 2010, prohibits commercial banks, their affiliates, and subsidiaries operating in the United States from engaging in “proprietary” trading if financing for these activities comes from federally insured customer deposits. Because vibrant economies need healthy functioning banking systems, their vitality has benefits that extend far beyond any one bank’s stakeholders. Volcker realized that derivatives positions could be useful for reducing risks but constantly returned to the viewpoint that, in the past, too many hastily conceived (so-called) risk-mitigation schemes produced exactly the opposite results.

Senators Jeff Merkley and Carl Levin formally introduced the Volcker Rule as an amendment to the Dodd Frank Wall Street Reform and Consumer Protection Act, with “risk mitigation” included as a legitimate use of financial derivatives. The amendment was eventually approved, and the Volcker Rule was scheduled to go into force on July 21, 2010. Due to delays in approving regulations and dealing with lawsuits, implementation was further postponed until July 21, 2015. None of these statements was true. The SCP was a short-term, highly speculative portfolio. It had not been hedging during the first quarter of 2012 because it was a net seller of credit protection, meaning SCP was increasing JPM Bank’s credit risk, not mitigating it. Finally, the CIO was highly opaque to regulators, often failing to make formal required reports to the OCC on its positions, risks, and returns.

In addition to Braunstein’s sins of commission were those of omission. For instance, he should have mentioned to investors (but did not) that the SCP had: (1) tripled in size since January 2012; (2) suffered losses since the start of the year; (3) acquired numerous new credit derivatives positions, many of which were highly illiquid and could take weeks or months to unload at decent spreads, due to the SCP’s huge market share; (4) violated its risk limits repeatedly and dramatically since January; (5) reported a daily VaR about half its actual value; and (6) kept the SCP’s reported VaR relatively constant from the last quarter of 2011 ($67 million) to the first quarter of 2012 ($69 million) by changing its VaR model. SEC rules make it unlawful for corporate representatives to intentionally and recklessly misinform the public by making false statements of material facts or omitting material facts.420

The straw that seemed to break the camel’s bank at the CIO occurred on March 22, when the SCP breached its CSW10 risk limit (see Risk Notepad 11.3). Of all the risk metrics, Ina Drew (apparently) took this one most seriously. On March 23, she ordered the SCP to stop all trading (“phones down”). Unfortunately, she did not order traders to reduce their positions. As a result, the SCP’s cumulative losses continued rising, moving from $100 million at the end of January, 2012 to $169 million at the end of February, $719 million at the end of March, and to $2.1 billion, $4 billion, and $4.4 billion, respectively, at the end of April, May, and June. By September 30, it had lost an estimated $6.2 billion.

Dysfunctional Regulation

The OCC had sixty-five examiners physically located on JPM Bank’s premises at the time the “London Whale” losses occurred. A few of them were at the CIO. Nevertheless, for years this regulator remained (seemingly) unaware of the risks posed by the SCP. In its early days, the CIO sometimes referred to the SCP in official regulatory reports, as its “core credit book,” but regulators never picked up on the fact that this activity was significant and in need of regulatory attention. Investigations, audits, and simple requests for further clarification came too late. The SCP’s financial position was revealed to the OCC for the first time in January 2012, when losses had already reached $100 million. Having attracted unexpected media attention, JPM Bank reassured the OCC that it was winding down the SCP in 2012 so that it could reduce the bank’s RWA. No one at OCC checked to see if the SCP had truly unwound these positions—it hadn’t!

Eight times during the first half of 2011 and hundreds of times in 2012, the CIO exceeded its stress limits without an investigation by the OCC. In some cases, the breaches were for weeks at a time with multiple violations occurring simultaneously. Had an investigation taken place in 2011 or early in 2012, the source of the SCP’s monstrous losses might have been uncovered and stopped.

Critics forcefully assert that that the OCC should have been more attentive, competent, and focused. For example, in 2011, the SCP earned $400 million on a lucky $1 billion credit derivative trade on AA, but this gain triggered no regulatory inquiries about how the SCP could have earned so much on a hedge—especially when JPM Bank owned no AA securities. Similarly, in January 2012, the SCP began using new risk measures, immediately reducing its VaR and RWA by 50 percent. The OCC never asked: (1) why the VaR model was changed, (2) how the new one was more accurate than the old one, (3) why there was such a dramatic reduction in exposures, (4) why JPM did not reduce the CIO’s risk limits commensurate with the new measure, and (very importantly) (5) why this model was implemented without first getting approval from the OCC.

Starting in January 2012 but especially after February, JPM Bank stopped sending OCC some required risk reports and performance data on both the CIO’s and the SCP’s operations. No one at OCC seemed to notice—that is, until April 6, 2012, when the “London Whale” story was exposed by the media. In short, there was no real proof that anyone at the OCC made use of or even read the risk limit reports coming from JPM Bank.

Conclusion

In 2012, JPM lost $6.2 billion from speculative credit derivatives trades of an obscure, London-based unit called the Synthetic Credit Portfolio (SCP). These massive losses came as an enormous shock to many because the SCP was supposed to be in the conservative business of hedging.

JPM’s losses were caused by its own strategic mistakes, performed on an enormous and complex mound of credit derivatives. Not only was the SCP excessively large for the role it played at JPM Bank, it was also disproportionately overweight in relation to global credit derivatives markets, becoming the victim of an illiquid portfolio that it alone had created.

Losses on strategic bets are bound to happen from time to time, which is why JPM’s multi-billion-dollar financial black eye will not be the reason the “London Whale” story is remembered. Rather, its legacy will be in memories of successive and serious judgment errors made by senior managers at the SCP, the CIO, JPM Bank, and JPM, while trying to cover strategic mistakes. These individuals showed willful neglect by disregarding breaches of risk limits, dodging regulatory oversight, misrepresenting vital financial information, hiding losses, conjuring new, unauthorized, and ill-conceived risk models, cleansing data in biased ways, arbitrarily lowering risk-weighted assets, and engaging in other forms of risk mismanagement. Banks have a responsibility to accurately report their positions, gains, losses, and exposures. JPM openly violated the letter and spirit of its responsibility to shareholders, regulators, investors, and the public.

A significant portion of the blame for the “London Whale” losses falls on the shoulders of financial regulators. Between 2011 and 2012, U.S. (and English) regulators failed to react strongly when the CIO breached risk limits, delayed or denied requests for information, and misrepresented vital information. It is not at all clear that U.S. regulators put a fraction of the time and effort needed to effectively perform their jobs. For all the rules, regulations, and safeguards financial regulators develop to protect the public from misrepresentative financial information, none can be effective if submitted financial and risk reports go unread and banks are not immediately held accountable for their actions.

After the “London Whale” episode, JPM Bank took steps to address its risk-management deficiencies. For instance, it developed better ways to coordinate JPM Bank’s operations with those of JPM Investment Bank, and it established 260 new risk measures, focusing on six aspects of risk involving directionality (i.e., exposure to widening credit spreads), curve (long vs. short positions), decompression (investment grade vs. high-yield positions), off-the-run vs. on-the-run positions (i.e., previously issued vs. newly issued credit index contracts with the same maturity dates), tranche risk (i.e., senior vs. equity tranches), and single-name defaults (i.e., risks caused by individual corporate defaults). Despite all the work JPM Bank put into reforming its risk measures, there is no guarantee that they will provide a permanent solution. After all, when the SCP had just five major risk measures, they were routinely ignored, trivialized, and unenforced. What is to prevent the same happening with 260 new measures?

Aftermath

The SCP’s losses of $6.2 billion in 2012 were large, but they amounted to only 6.4 percent of net revenues that year, equaling $97 billion.421 As for shareholders, JPM’s year-end stock appreciation was slightly more than 29 percent.

How many of the players in the “London Whale” affair were fired, quit, went to jail, or paid fines? What price, if any, did JPM pay for its managers’ inattentive risk management practices? Yes, there were consequences. Some employees were fired or quit, fines were imposed, but no one went to jail. Risk Notepad 11.6 provides a year-by-year summary of how events played out until 2017.

Risk Notepad 11.6
Aftermath

2012

Ina Drew resigned on May 13.

In July, Achilles Macris, Javier Martin-Artajo, and Bruno Iksil were fired, and Irvin Goldman resigned.

Julien Grout was suspended and subsequently resigned from the bank on December 20.

The board cut Jamie Dimon’s 2012 compensation by 50 percent to $11.5 million, saying that he bore “ultimate responsibility for the failures that led to the losses.”

2013

On January 14, the OCC issued a “cease and desist” order to the SCP.

In September, JPM was fined $920 million for misstating financial results, “unsafe and unsound practices, lack of sufficient internal controls, and fraudulently overvaluing investments.” Of the total, $200 million went to the U.S. Federal Reserve, $300 million to the U.S. OCC, $200 million to the U.S. SEC, and $220 million to the United Kingdom’s Financial Conduct Authority (FCA).

JPM withheld 2012 severance payments and incentive compensation from the “London-Whale” participants. It also clawed back income from previous years, recovering the maximum possible under the bank’s rules, equal to two years’ total compensation per person. From Ina Drew, alone, JPM recovered $21.5 million.

In August, Bruno Iksil entered into a non-prosecution agreement with the U.S. Justice Department, absolving him from pleading guilty to any crime or civil claims. The SEC also decided to take no action against him.

Javier Martin-Artajo, a Spanish national, and Julien Grout, a French national, faced criminal charges and civil claims connected to conspiracy, wire fraud, and securities fraud for hiding the SCP’s losses from bank management, but Spanish and French courts refused U.S. extradition requests.

2015

In December, JPM agreed to pay $150 million to investors who purchased JPM shares between April 13 and May 21, 2012. This payment resolved a class action securities fraud lawsuit charging JPM with willfully hiding risks connected to the SCP.

2016

In February, England’s FCA fined Achilles Macris £782,000 (about $1,235,900) for his failure to communicate the SCP’s positions and losses to regulators, but no prohibition was placed on his ability to work for a regulated financial institution in the future.

In July, Britain’s FCA dropped its investigation and actions against Bruno Iksil.

2017

The U.S. Federal Reserve decided not to proceed with legal action against Bruno Iksil, and in March, the five-year statute of limitations expired. His immunity from prosecution reduced or eliminated incentives for him to cooperate with U.S. and British authorities on other cases.

In July 2017, the U.S. Justice Department dropped remaining criminal charges against Javier Martin-Artajo and Julien Grout, but both men could still face civil charges by the SEC.

Review Questions

  1. Why did JPM create the SCP? What was its main function supposed to be?
  2. Was the SCP hedging or speculating? Provide examples to support your position.
  3. What is the “Volcker rule,” and how did it relate to JPM’s financial fiasco?
  4. The financial media called Bruno Iksil the “London Whale.” Do you agree? Was Iksil the “London Whale” or someone else?
  5. What are RWA? Explain why JPM wanted to reduce the SCP’s RWA in 2012.
  6. Explain the SCP’s failed trading strategy in 2012.
  7. In 2012, explain how Ina Drew’s orders to SCP traders complicated the unit’s ability to comply with JPM parent’s instructions.
  8. In 2012, did the SCP ignore its strategic purpose? Explain.
  9. What is the Basel II Accord, and what role did it play in the “London Whale” story?
  10. Explain how the SCP manipulated its risk metrics and data inputs.
  11. Why did JPM managers persistently question and trivialize the significance of the SCP’s risk measures?
  12. In what ways was financial regulation of the CIO and SCP dysfunctional?

Bibliography

17 C.F. R. Section 240.10b-5(b) (2011) pursuant to Section 10(b) of the Securities Exchange Act of 1934. 15 U.S.C. § 78(j)(b) (2006).

Bank for International Settlements. Guidelines for Computing Capital for Incremental Risk in the Trading Book—Final Version. Accessed November 2, 2017.

J.P. Morgan Chase & Co. Report of JPMorgan Chase & Co. Management Task Force Regarding 2012 CIO Losses. January 16, 2013. Accessed on August 10, 2017.

J.P. Morgan. Annual Report 2012 of J.P. Morgan Chase & Co. Accessed on August 10, 2017.

J.P. Morgan. Annual Report 2013 of JPMorgan Chase & Company. Available at https://www.jpmorganchase.com/corporate/investor-relations/document/01-2013AR_FULL_09.pdf. Accessed on August 10, 2017.

United States Senate Permanent Subcommittee on Investigations: Committee on Homeland Security and Governmental Affairs, Majority and Minority Staff Report. JPMorgan Chase Whale Trades: A Case History of Derivatives Risks and Abuses, Released in Conjunction with Permanent Subcommittee on Investigations. Accessed on August 10, 2017.

Appendix 11.1
Alphabetical List of the Main “London Whale” Decision Makers and Players

Name Function at JPM
Javier Martin-Artajo Based in London, Martin-Artajo was head of JPM Bank’s Credit and Equity unit, part of the Chief Investment Office (CIO). He was responsible for European trading and directly supervised Bruno Iksil and Julien Grout. Martin-Artajo was a major force behind the CIO’s decision to change the SCP’s value at risk (VaR) measure.
Douglas Braunstein Based in New York, Braunstein was JPM’s Chief Financial Officer.
James (Jamie) Dimon Based in New York, Dimon was Chairman of JPM’s Board of Directors and its Chief Executive Officer.
Ina Drew Based in New York, Drew was the CIO’s Chief Investment Officer, responsible for both trading and risk management activities. Drew answered directly to Jamie Dimon and supervised both Achilles Macris and Javier Martin-Artajo.
Irvin Goldman Based in London, Goldman was the CIO’s first Chief Risk Officer but assumed this position late in the game (i.e., January 2012).
Julien Grout Based in London, Grout was a junior trader at the SCP. He was responsible for marking to market his department’s portfolios daily.
John Hogan Based in New York, Hogan was the Chief Risk Officer at JPM.
Bruno Iksil Based in London, Iksil was the SCP’s lead trader and supervisor of Julien Grout. In 2011, the media nicknamed him the “caveman” and in 2012, the “London Whale.”
Achilles Macris Based in London, Macris was the CIO’s International Chief Investment Officer. He supervised the SCP’s management, including Javier Martin-Artajo, and was a force behind the CIO’s decision to actively trade credit derivatives.
Peter Weiland Based in London, Weiland was the CIO’s most senior risk manager from 2008 to 2012.

Appendix 11.2
Markit Group Limited

The SCP had a special preference for credit indices and tranches administered by Markit Group Limited, a global financial information and services company that owns, administers, operates, and services a broad range of credit index products. Markit also provides prices for more than 2,000 single-name credit default swaps (CDS) and processes derivatives trades.

The SCP favored Markit’s CDX and iTraxx indices. Its CDX indices cover a family of tradable CDS indices for North America and regional emerging markets. Its iTraxx indices cover a family of tradable CDS indices for European, Asian, and regional emerging markets. CDX and iTraxx prices are calculated and published daily. Risk Notepad A 11.2.1 provides a Rosetta Stone for understanding Markit Group’s credit indices and abbreviations.

Risk Notepad A 11.2.1
A Rosetta Stone for Understanding Markit Group’s Credit Indices and Abbreviations

Markit Group’s CDX and iTraxx credit indices have many important features and an abbreviation system that is both logical and descriptive.

A new CDX and iTraxx series is released every six months, each one comprised of the most liquid CDS in the targeted sectors, based on CDS trading volumes.

Credit derivatives on these indices are traded over the counter,422 and counterparties can choose among diversified indices that are investment grade, high yield, or crossover,423 and carry maturities of a few months to 3-, 5-, 7-, and 10-years. Of these alternatives, the 5-year maturity has been the most liquid.

Each index series is identified by a version number, with the genesis version set at “v1”. Subsequent version numbers appear when a constituent company is removed from the index. For example, Markit’s CDX.HY.11.v1 was launched in September 2008. After removal of Tribune Company, due to bankruptcy, Markit published CDX.HY.11.v2, and CDX.HY.11.v3 was published after Nortel Networks Corporation was removed.

CDX Indices and Abbreviations

CDX reflects the average credit risk of North American and regional emerging markets companies that comprise the index.

Investment-grade CDX indices track the credit rating of 125 companies with relatively high credit ratings and non-investment grade CDX indices track the credit rating of 100 companies with relatively low credit ratings.

For the abbreviation CDX.NA.IG.9, “CDX” stands for “Credit Index”; “NA” means it tracks the credit risk of “North American” companies; “IG” means the securities are “Investment Grade;” and “9” is Markit’s series number, with Series 9 issued in 2007.

In the abbreviation, CDX.NA.HY.9, “CDX,” “NA,” and “9” have the same meaning as above, but “HY” means the securities are “High Yield” (i.e., relatively risky).

iTraxx Indices and Abbreviations

iTraxx reflects the average credit risk of European, Asian and regional emerging market companies.

Investment-grade iTraxx indices track the credit rating of 125 companies with relatively low credit ratings and non-investment grade iTraxx indices track the credit rating of 100 companies with relatively low credit ratings.

For the abbreviation iTraxx.Main.S9, “Main” means it tracks Markit’s core index for investment-grade European securities, and “S9” is Markit’s series number, with Series 9 issued in 2007.

In the abbreviation iTraxx.hiVol, “hiVol” means the index tracks the 30 most-risky constituent companies in the iTraxx index.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset