United States: SDNY Bankruptcy Court Interprets Section 546(e)’s Safe Harbors In Lehman-JPMorgan Dispute

On April 19, 2012, the U.S. Bankruptcy Court for the Southern District of New York granted in part and denied in part JPMorgan Chase, N.A.'s motion to dismiss an adversary complaint filed by Lehman Brothers Holdings Inc. ("LBHI") and its Official Committee of Unsecured Creditors. The Complaint seeks to recover approximately $8.6 billion in prepetition transfers made by LBHI to JPMorgan in the days leading up to LBHI's bankruptcy. JPMorgan filed a motion to dismiss the Complaint, arguing that it acted reasonably in requiring additional collateral at a time of great financial risk, and that the transfers that the Plaintiffs sought to unwind are immunized by the safe harbor protections of section 546(e) of the Bankruptcy Code.1

The Court ultimately dismissed twenty-two counts of the Complaint related to claims of preferential and constructively fraudulent transfers, on the grounds that section 546(e) protected the transfers from avoidance by the Debtors. The Court refused to dismiss the remaining twenty-seven counts, which related to, among other things, common law legal doctrines, turnover of estate property, and equitable subordination, finding that the safe harbors do not offer "fail safe protection against every cognizable claim" related to a covered transaction and are not an "impenetrable barrier" to all claims against a market participant.2

The Relationship Between JPMorgan and Lehman Brothers

JPMorgan was the principal clearing bank for Lehman Brothers Inc. ("LBI"), and performed clearing activities for LBI pursuant to a Clearance Agreement dated June 15, 2000. The Clearance Agreement remained unaltered until August 2008, when JPMorgan drafted a new set of documents that materially changed the clearance relationship between JPMorgan and the Lehman entities. These "August Agreements" included (i) an Amendment to the Clearance Agreement that added LBHI and several of its subsidiaries as parties to the Clearance Agreement; (ii) a Guaranty, pursuant to which LBHI guaranteed payment of all obligations and liabilities owed to JPMorgan under the Clearance Agreement; and (iii) a Security Agreement that granted JPMorgan a lien on certain LBHI accounts at JPMorgan in which LBHI posted collateral.

On September 9, 2008, as LBHI's financial condition deteriorated, JPMorgan requested that LBHI execute another new set of documents. These "September Agreements" included (i) a further Amendment to the Clearance Agreement, which expanded the Lehman entities' obligations under the Clearance Agreement to all Lehman obligations of whatever nature to all JPMorgan entities, including clearance, trading, and derivatives obligations; (ii) a Guaranty that expanded LBHI's liabilities to include all obligations of Lehman entities to all JPMorgan entities; (iii) a Security Agreement that granted JPMorgan a lien on all of LBHI's accounts at JPMorgan or its affiliates; and (iv) an Account Control Agreement that perfected JPMorgan's security interest LBHI's posted collateral.

The parties executed the September Agreements on September 10, 2008. JPMorgan immediately requested additional collateral under the Agreements, although the Plaintiffs allege that it already held sufficient collateral to secure its risks. Between Tuesday, September 9, 2008 and Friday, September 12, 2008, LBHI posted approximately $8.6 billion in collateral with JPMorgan (the "Disputed Collateral Transfers"). LBHI filed a petition for relief under chapter 11 on Monday, September 15, 2008.

The Adversary Complaint

In the Complaint, the Plaintiffs asserted forty-nine separate claims, including claims seeking the avoidance and recovery of actually fraudulent transfers under section 548 of the Bankruptcy Code; claims seeking avoidance and recovery of constructively fraudulent and preferential transfers under sections 544, 547 and 548 of the Bankruptcy Code; claims under various common law legal doctrines; and claims under other sections of the Bankruptcy Code, including turnover of estate property under section 542, setoff under section 553, equitable subordination under section 510(c), and disallowance of claims under section 502(d). The Court dismissed the claims for recovery and avoidance of constructively fraudulent and preferential transfers made under the August and September Agreements, finding that the transfers are protected under section 546(e)'s safe harbors.

The Court's Application of the Safe Harbors of Section 546(e) of the Bankruptcy Code

Section 546(e) of the Bankruptcy Code expressly limits a debtor's or trustee's power to avoid a transfer as preferential under section 547(b) of the Bankruptcy Code or as constructively fraudulent under section 548(a)(1)(B) of the Bankruptcy Code. Specifically, section 546(e) exempts from avoidance "a transfer made by or to (or for the benefit of) a . . . financial institution [or] financial participant . . . in connection with a securities contract, as defined in section 741(7) . . . that is made before the commencement of the case."3

Section 741(7) defines "securities contracts" as, among other things,

(A)(i) a contract for the purchase, sale or loan of a security; . . . (v) any extension of credit for the clearance or settlement of securities transactions; . . . (x) a master agreement that provides for an agreement or transaction referred to in cause (i) [or] (v); . . .[and] (xi) any security agreement or arrangement or other credit enhancement related to any agreement or transaction referred to in this subparagraph, including any guarantee . . . .4

As a threshold matter, the Court found that the recent Enron and Quebecor World decisions require courts to strictly interpret the language of the safe harbors, "even when the outcome may be prejudicial to the interests of the estate and its creditors."5

The key issue in the Court's application of the safe harbors was whether the August and September Agreements qualified as securities contracts under section 741(7). The Court first addressed the Clearance Agreement, as amended by the August and September Amendments, finding that it qualified as a securities contract because it was an "extension of credit for the clearance or settlement of securities transactions" under section 741(7)(A)(v). Moreover, the Court found that because subsection (v)'s definition of securities contract refers to securities transactions, each individual extension of credit by JPMorgan to LBI under the Clearance Agreement was a stand-alone securities contract. As a result, the Court found that the Clearance Agreement was also a securities contract because it was a master agreement under section 741(7)(A)(x). The Court then found that the August Agreements, the September Security Agreement and the September Guaranty met the definition of securities contract contained in section 741(7)(A)(xi), because they were credit enhancements related to other securities contracts.

Next, the Court addressed whether the grant and perfection of liens under the securities contracts constituted transfers for purposes of section 546(e). The Court found that courts generally agree that the grant of a lien and the perfection of a security interest are transfers for purposes of section 546(e). Thus, the Court found that the liens granted under the September Agreements were transfers pursuant to safe harbored securities contracts, and are exempt from avoidance under section 546(e). The Court also found that the Account Control Agreement's perfection of liens granted by other September Agreements was a safe harbored transfer. The Court found that even though the Account Control Agreement itself was not a securities contract, the perfection of liens granted by other securities contracts was a transfer in connection with protected securities contracts.

Another key issue addressed by the Court was whether the Disputed Collateral Transfers were transfers made in connection with safe harbored securities contracts. JPMorgan ultimately applied the Disputed Collateral Transfers to safe harbored contracts, but the Plaintiffs argued that the Disputed Collateral Transfers were not protected by section 546(e) because at the time the transfers were made, they "had nothing to do with" JPMorgan's exposure under the Clearance Agreement or any derivatives contracts.6 In essence, the Plaintiffs argued that JPMorgan should not be permitted to retroactively sanitize the Disputed Collateral Transfers by applying them to safe harbored contracts. The Court disagreed, finding that section 546(e)'s requirement that a transfer be "in connection with" a securities contract does not contain a temporal requirement. Accordingly, the Court held that LBHI and the Committee could not avoid the Disputed Collateral Transfers because they were made in connection with safe harbored agreements.

Finally, the Court addressed whether LBHI could avoid obligations it incurred to JPMorgan under the August Guaranty and the September Guaranty. Section 546(e) does not mention the incurrence of obligations, thus the Plaintiffs argued that the Guarantees were not protected from avoidance. The Court agreed that section 546(e) clearly does not cover the incurrence of obligations, and that obligations are distinguishable from transfers because an obligation is merely a legal prerequisite for a possible future transaction, rather than a transaction. Although the Court found that the obligations that LBHI incurred under the Guarantees were not protected by the safe harbor, it found that the Plaintiffs' argument was a dead end. The liens and related collateral transfers made by LBHI pursuant to the Guarantees, which the Plaintiffs were ultimately seeking to avoid, were transfers in connection with a securities contract. Thus, the liens and collateral transfers were independently immune from avoidance, even if the obligations secured were not.

Because the Court determined that the relevant August and September Agreements were securities contracts, and that the collateral transfers at issue were made in connection with the August and September Agreements, the Court determined that the transfers were protected from avoidance under section 546(e)'s safe harbors. However, the Court found that the protection of the safe harbors did not extend to claims not specifically described in section 546(e). Thus, the Court did not dismiss the remaining twenty-seven counts relating to claims such as to common law legal doctrines, turnover of estate property, and equitable subordination.

Conclusion

The Court's decision, which extends to nearly one hundred pages, is significant in that it sheds light on several issues of first impression. It also shows, however, that the safe harbors will not protect against every claim that could arise out of a trading relationship.

Footnotes

1 Lehman Bros. Holdings Inc. v. JPMorgan Chase Bank, N.A. (In re Lehman Bros. Holdings Inc.), --- B.R. ----, 2012 WL 1355659 (Bankr. S.D.N.Y. April 19, 2012).

2 Id. at *32.

3 11 U.S.C. § 546(e). Notably, section 546(e) does not exempt from avoidance actually fraudulent transfers under section 548(a)(1)(A) of the Bankruptcy Code.

4 11 U.S.C. § 741(7)(A)(i)-(xi).

5 Lehman Bros., 2012 WL 1355659 at *17. See also In re Enron Creditors Recovery Corp. v. Alfa S.A.B. de C.V., 651 F.3d 329 (2d Cir. 2011); Official Comm. of Unsecured Creditors of Quebecor World (USA) Inc. v. Am. United Life Ins. Co. (In re Quebecor World (USA) Inc., 453 B.R. 201 (Bankr. S.D.N.Y. 2011).

6 Id. at *23.

www.cadwalader.com

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

More Popular Related Articles on Finance and Banking from USA
The EU’s financial transaction tax is due to apply from the beginning of 2014.
The US Commodity Futures Trading Commission has recently granted last minute no-action relief from portions of the CFTC's swap reporting rules.
Standards for banking organizations regulated by the Federal Reserve for Retail Forex are generally comparable to rules adopted by other regulators
A senior SEC lawyer has recently encouraged the private equity and hedge fund communities to consider whether certain practices of private fund managers could subject these firms to SEC registration as broker-dealers.
In November 2012, the U.S. District Court for the Eastern District of New York preliminarily approved a settlement agreement in the In re Payment Card Interchange Fee and Merchant Discount Antitrust Litigation.
Federal bank regulatory agencies have served notice that deposit advance products will soon be subject to significant new restrictions and heightened supervisory scrutiny.
On 15 March, the first six implementing measures of the European Market Infrastructure Regulation (EMIR) entered into force.
 
In association with
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert
Email Address
Company Name
Password
Confirm Password
Mondaq Topics -- Select your Interests
Accounting and Audit
Anti-trust/Competition Law
Consumer Protection
Corporate/Commercial Law
Criminal Law
Employment and HR
Energy and Natural Resources
Environment
Family and Matrimonial
Finance and Banking
Food, Drugs, Healthcare, Life Sciences
Government, Public Sector
Immigration
Insolvency/Bankruptcy, Re-structuring
Insurance
Intellectual Property
International Law
Litigation, Mediation & Arbitration
Media, Telecoms, IT, Entertainment
Privacy
Real Estate and Construction
Strategy
Tax
Transport
Wealth Management
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.