United States: Second Circuit Expands Bankruptcy Code's Safe Harbor Protection for Transferees of Ponzi Scheme Payments

Last Updated: April 14 2015
Article by Richard Bendix and Noel Susberry

Sections 548(a)(1)(A) and (B) of the Bankruptcy Code (the "Code") give a bankruptcy trustee the power to avoid intentional and constructive fraudulent transfers.1 Section 546(e) of the Code prevents a bankruptcy trustee from recovering a variety of transfers, including ones that would otherwise be avoidable as constructive fraudulent transfers, if the transfers are either settlement payments made by or to a stockbroker or financial institution, or are payments by or to a stockbroker or financial institution in connection with a securities contract.2 In a recent decision, the Second Circuit Court of Appeals has expanded section 546(e)'s protection for recipients of constructive fraudulent transfers in Ponzi schemes.3 Notably, section 546(e) does not prevent a trustee from recovering intentional fraudulent transfers.

The Section 546(e) Safe Harbor's Limitations on Avoiding Powers

Section 546(e) was enacted as a means of "minimiz[ing] the displacement caused in the commodities and securities markets in the event of a major bankruptcy affecting those industries"4 and is also designed to protect financial markets "from the instability caused by the reversal of settled securities transactions."5 Without such protection, attempts to avoid a debtor's securities transactions would discourage investors from investing and could potentially have a ripple effect on the entire market.6

Expanding the Scope of Section 546(e) in Ponzi Scheme Cases

In recent years, courts have applied section 546(e) to prevent avoidance of payments made in connection with leveraged buyouts of public7 and private corporations,8 early redemption of commercial paper,9 and redemption of investments in mutual funds that were operated as Ponzi schemes.10 Continuing the line of decisions applying section 546(e) to prevent recovery of Ponzi scheme payments, the Second Circuit Court of Appeals recently interpreted the phrases "securities contract" and "settlement payments" in sections 546(e) and 741 broadly to shield investors in Bernard Madoff 's Ponzi scheme who received payments in excess of their original investments.11 Following the collapse of Bernard L. Madoff 's notorious Ponzi scheme, Irving Picard was appointed as trustee (the "Trustee") of Bernard L. Madoff Investment Securities LLC ("BLMIS") pursuant to the Securities Investor Protection Act, 15 U.S.C. § 78aaa et seq., ("SIPA").12 BLMIS purported to execute a strategy for its customers which, if actually implemented, would have consisted of securities or options trading.13 In reality, however, BLMIS conducted no actual securities or options trading on behalf of its customers. 14 Instead, BLMIS deposited customer investments into a single commingled checking account. For years, BLMIS fabricated customer statements to show fictitious securities trading activity and returns that provided for annual increases of 10 to 17 percent.15 Thus, when customers sought to withdraw money from their accounts, they received cash from the commingled account. Many of those customers were "net winners," who received payments that exceeded the amounts of their original investment.16

The Trustee sued "net winners" to avoid as constructive fraudulent transfers BLMIS's payments to them of fictitious profits.17 The defendants responded that the transfers they received were protected by Code section 546(e). The trial court ruled in favor of the defendants, and the Trustee appealed. In that appeal, the Trustee argued that section 546(e) did not shield those payments for three reasons, all of which were based on the premise that section 546(e) would only apply if Madoff had actually completed the securities transactions he purported to effectuate.18 First, the Trustee argued that section 546(e) should not apply because BLMIS never initiated, executed, completed or settled the securities transactions contemplated by the agreements that BLMIS's customers signed when they opened their accounts ("Account Documents").19 Next, the Trustee argued that the transfers were not "made in connection with a securities contract" nor were they a "settlement payment," as those terms are defined in section 741 of the Code.20 Finally, the Trustee asserted that applying section 546(e) to BLMIS's payments would be tantamount to giving legal effect to Madoff 's fraud.21

The Second Circuit rejected the Trustee's arguments. The court held that the Account Documents were securities contracts even though they did not specifically "identify any security, issuer, quantity, price, or other terms necessary to describe a security transaction."22 Nothing in the Code indicated to the court that a "securities contract" required the degree of specificity argued for by the Trustee. The court also rejected the Trustee's argument that the Account Documents were not securities contracts because they did not expressly require BLMIS to carry out securities transactions. The court held that the Account Documents were sufficiently "similar to" a contract for the purchase or sale of a security to be treated as securities contracts under Code section 741(7)(A)(vii).23

Notably, the court agreed with the Trustee that the transfers he sought to avoid were made in connection with a Ponzi scheme, and that "BLMIS's conduct was in flagrant breach of the agreements it made with its customers." Nevertheless, the court stated that "the fact that a payment was made in connection with a Ponzi scheme does not mean that it was not at the same time made in connection with a (breached) securities contract."

In response to the Trustee's second argument, the Second Circuit held that section 546(e) shielded BLMIS's transfers from avoidance because those transfers were "made in connection with a securities contract" and were also "settlement payments."24 In reaching this decision, the Second Circuit noted the "extraordinary breadth" of the Code's definitions of "securities contract"25 and "settlement payment."26

The court stated that the term "securities contract" is expansive and includes contracts for the purchase or sale of securities, as well as any agreements that are similar to contracts for the purchase or sale of securities.27 The court also found that section 546(e) requires only that a covered transfer be broadly related to a "securities contract," not that it be connected to an actual transaction in securities.28 Thus, the application of section 546(e) did not depend on whether BLMIS actually engaged in securities transactions.29

In rejecting the Trustee's third argument, the court found compelling but ultimately not convincing the argument that allowing customers to retain their fictitious profits would give legal effect to Madoff 's fraud.30 The court emphasized the need for finality even in light of countervailing equity considerations.31 The court also held that the avoidance of millions, if not billions, of dollars of payments from BLMIS would likely cause the "very displacement" that Congress hoped to minimize.32


The Madoff case follows the decisions of other courts that have applied the section 546(e) safe harbor to protect Ponzi scheme payments from recovery as constructive fraudulent transfers. The Madoff case also expands the scope of section 546(e) in SIPA cases by interpreting the phrase "securities contract" broadly to encompass customer account documents that authorize brokers to trade on behalf of those customers, whether or not actual trading occurs. In the future, therefore, trustees seeking to avoid Ponzi scheme payments will have to prove that those payments were intentional fraudulent transfers in order to prevent application of Code section 546(e).33


1. Intentional fraudulent transfers are those made with the actual intent to hinder, delay, or defraud creditors. Code §548(a)(1)(A). Constructive fraudulent transfers are those made in exchange for less than a reasonably equivalent value when a debtor is either insolvent, is left with unreasonably small capital, or intends to incur debts beyond its ability to pay those debts as they mature. Code §548(a)(1)(B).

2. In re Bernard L. Madoff Inv. Sec. LLC, 773 F.3d 411, 414 (2d Cir. 2014).

3. Id.

4. Enron Creditors Recovery Corp. v. Alfa, S.A.B. de C.V. (In re Enron Creditors Recovery Corp.), 651 F.3d 329, 334 (2d Cir. 2011) (quoting H. R. Rep. No. 97-420, at 2 (1982), reprinted in 1982 U.S.C.C.A.N. 583, 583).

5. Weisfelner v. Fund 1 (In re Lyondell Chem. Co.), 503 B.R. 348, 365 (Bankr. S.D.N.Y. Jan. 14, 2014).

6. Kaiser Steel Corp. v. Charles Schwab & Co., 913 F.2d 846, 849 (10th Cir. 1990) (quoting H.R. Rep. 97-420, at 1 (1982), as reprinted in 1982 U.S.C.C.A.N. 583, 583).

7. Official Comm. of Unsecured Creditors v. Fleet Retail Fin. Group (In re Hechinger Inv. Co. of Delaware), 274 B.R. 71, 87 (D. Del. 2002) (holding that LBO payments made to both insider and non-insider shareholders of a publicly held company by a financial institution are protected by section 546(e)).

8. Cyganowski v. Lapides (In re Batavia Nursing Home, LLC) 2013 Bankr. LEXIS 3022, 1 (Bankr. W.D.N.Y. July 29, 2013) (applying section 546(e) to LBOs of privately held securities).

9. In re Enron Creditors Recovery Corp, 651 F.3d at 334-335.

10. Peterson v. Somers Dublin Ltd., 729 F.3d 741, 748 (7th Cir. Ill. 2013) (applying Code section 546(e) to prevent recovery of constructive fraudulent transfers in a Ponzi scheme, but noting that some courts have interpreted section 546(e) narrowly to prevent people who received money from a crooked enterprise from profiting, to the detriment of other investors who did not get out while the going was good).

11. See generally In re Bernard L. Madoff Inv. Sec. LLC, 773 F.3d 411 (2d Cir. 2014).

12. Id. at 414. Under SIPA, a trustee can "claw back" money paid by the debtor, as long as the money "would have been customer property" had the payment not occurred, and the transfers could be avoided under the Code. SIPA §78fff-2(c)(3).

13. Id. at 415 (citing SIPC v. Bernard L. Madoff Inv. Secs. LLC (In re Bernard L. Madoff Inv. Secs. LLC), 424 B.R. 122, 129-30 (Bankr. S.D.N.Y. 2010)). 14. Id.

15. Id.

16. Id.

17. Id.

18. Id. at 417-419 ("[b]ecause 'there are no securities transactions to unwind,' the Trustee argues that no such disruption would occur, and correspondingly, § 546(e) is inapplicable").

19. Id. at 416, 418. BLMIS customers were required to execute three documents when opening their accounts. The first, "Customer Agreement," authorized BLMIS to open or maintain one or more accounts for the customers' benefit. The second, "Trading Authorization," appointed BLMIS as the customers' "agent and attorney in fact" to "buy, sell, and trade stocks bonds, and other securities..." The third, "Option Agreement," authorized BLMIS to engage in options trading for customer accounts.

20. Id.

21. Id.

22. Id.

23. Id. at 421 ("[o]f course, BLMIS secretly intended to violate the agreement by using the deposits to fund the ongoing Ponzi scheme. But this is of no moment, because "[a]n agreement is a manifestation of mutual assent," and "[t]he conduct of a party may manifest assent even though he does not in fact assent").

24. Id. at 417.

25. 11 U.S.C. §§ 741(7)(A)(i), (vii).

26. See supra note 5.

27. Id. at 418.

28. Id. at 420.

29. Id. at 418.

30. Id. at 423.

31. Id. ("...in enacting the Bankruptcy Code, Congress struck careful balances between the need for an equitable result for the debtor and its creditors, and the need for finality") (internal citation omitted).

32. Id. at 420.

33. It may be difficult, however, for a trustee to prove that Ponzi scheme payments are made with the actual intent to hinder, delay or defraud the Ponzi schemer's creditors.

This article was originally published in The Metropolitan Corporate Counsel. www.metrocorpcounsel.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.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

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.


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.


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.


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.


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.


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.


From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

*** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .


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.