GO
Loading...

Ten Big Questions for JPMorgan

JPMorgan Chase, the largest U.S. bank in terms of assets, revealed on Thursday that it suffered a trading loss of at least $2 billion from a what it described as a failed hedging strategy.

JP Morgan Chase headquarters
Bloomberg | Getty Images
JP Morgan Chase headquarters

The news has sparked intense speculation about what caused the loss, how the bank's internal controls missed it coming, and how it will affect JPMorgan moving forward. As famed investor Dennis Gartman told CNBC on Friday, "when ill news comes out, there is usually more ill news to follow.”

As details emerge about the loss, a series of questions come to mind:

  1. Is the loss-making position still open?
  2. Have any of the losses been crystallized yet? If not, how big is the open position?
  3. When did it become apparent to the risk department at JPMorgan that the "hedge" wasn’t working?
  4. When were senior management and JPMorgan CEO Jamie Dimon informed about the magnitude of the potential losses?
  5. What is the client position being "hedged"?
  6. By how much did the original JPMorgan positional hedge offset the client portfolio position?
  7. JPMorgan reported first-quarter numbers in mid-April. Should the bank have informed investors of a material risk to future profits if this position had already started to become a problem for the bank?
  8. When was the "mark to market" calculation that revealed the loss made? Don’t investment banks make such calculations on a daily basis in order to ensure the position doesn’t become too prominent?
  9. Was this a single trader acting alone? Or was it a desk trading a position that was made with full knowledge of senior JPMorgan and risk management?
  10. What is JPMorgan’s interpretation of "proprietary trading" as opposed to "client position hedging"?

- By CNBC’s Stephen Sedgwick. Ted Kemp contributed to this story.

Contact Opinion

  • CNBC NEWSLETTERS

    Get the best of CNBC in your inbox

    To learn more about how we use your information,
    please read our Privacy Policy.
    › Learn More