Content Type: Article

  • Faber Responds to Aggressive Tax Planning Article

    ARTICLE

    Faber Responds to Aggressive Tax Planning Article

    September 19, 2016

    Read time: 2 min

    Key takeaways
    Overview

    Peter Faber wrote this bylined letter to the editor criticizing an earlier article which contended that a corporation should not engage in transactions designed solely to reduce taxes. “Transactions that have real economic consequences should be respected even if their only motivation is to save taxes,” Mr. Faber wrote, adding “there is no reason why [companies] should not be allowed to restructure later on for tax reasons.”

    In depth
    Authors
    More insights

  • New Form ADV: The Impact on Private Fund Advisers

    New Form ADV: The Impact on Private Fund Advisers

    ARTICLE / CLIENT ALERT

    New Form ADV: The Impact on Private Fund Advisers

    September 19, 2016

    Read time: 7 min

    Key takeaways
    Overview

    On Aug. 25, 2016, the U.S. Securities and Exchange Commission adopted a final rule that amends Form ADV — the filing that investment advisers registered with the SEC use to apply for and maintain their registration and that exempt reporting advisers utilize to claim and maintain their registration exemption. The SEC also amended its books and records rule to require more documentation with respect to performance reporting records.[1]

    While these amendments will go into technical effect in this calendar year, the SEC has delayed the substantive effectiveness of the amended ADV and the new books and records requirements until October 2017. This means that many advisers will not implement these new requirements until their first quarter 2018 annual updating amendment.

    ADV Amendments

    The proposed rule[2] generated a good amount of concern and consideration; the SEC received nearly 50 comment letters on the proposal from U.S. and non-U.S. industry participants, trade groups and law firms. Industry commenters focused on one large conceptual point (the new requirement to publicly disclose Form PF-style information for an adviser’s managed accounts) and several practical points (including the need to preserve, clarify and expand the ability of a family of advisers to file a single “umbrella registration”).

    The final rule, however, is substantially similar to the proposed one, which means that managers will need to prepare to make more disclosures in their Form ADV, and many managers (especially non-U.S. managers) will need to file multiple Form ADVs to cover their family of affiliated managers.

    In particular, the final rule contains the following provisions and requirements:

    • Separately Managed Accounts. Form ADV currently requires registered and reporting investment advisers publicly to schedule a good deal of information with respect to each private fund advised by them. The amended Form ADV will require new disclosures with respect to the portfolio investments of separately managed accounts, including — for certain advisers — with respect to asset categories and borrowings. These disclosures will be publicly available. This contrasts with the confidential treatment afforded by Form PF, which is currently required of certain registered investment advisers and which requires detailed disclosures of information with respect to the portfolio investments of private funds.
      • The SEC declined to formally adopt a definition of the term “separately managed account,” but, instead, provided in the Form ADV itself and the instructions that the new disclosures with respect to separately managed accounts exclude assets of clients that are investment companies, business development companies or other pooled investment vehicles.
      • All advisers with separately managed accounts will be required to provide a breakdown (by percentage) of the asset classes in which those accounts are invested (e.g., ETFs, non-exchange traded securities, bonds of various types, derivatives, securities issued by registered investment companies and other pooled investment vehicles, and cash and cash equivalents).
      • Advisers with $500 million or more of regulatory assets under management (which is gross assets, not net) in separately managed accounts must update the new portfolio investment reporting in Form ADV annually.
      • Advisers with $10 billion or more of regulatory assets under management in separately managed accounts must update this portfolio investment reporting on an annual basis, with information reported as of mid-year and end of year.
      • Information with respect to all separately managed accounts must be aggregated and disclosed, even those of non-U.S. clients. This requirement will apply to non-U.S. advisers, as well as advisers located in the United States.
      • Advisers must further identify all custodians that account for at least 10 percent of the adviser’s regulatory assets under management attributable to separately managed accounts.
      • There is also a new requirement that the amount of assets managed for clients that are non-U.S. persons be specifically disclosed.
    • Umbrella Registration. The amended Form ADV incorporates the “umbrella registration” concept from the SEC Staff’s no-action letter to the American Bar Association on Jan. 18, 2012. The adopting release states the Commission’s view that the final rule is codifying the SEC Staff’s umbrella registration regime.
      • The new form includes a “Schedule R” that will need to be completed for each relying adviser and will require disclosures specific to that adviser (irrespective of whether the adviser has been treated as a single, undifferentiated business unit). This will include entity-specific disclosures of eligibility for registration, large owner information, identification of control persons and any disciplinary history.
      • Notwithstanding numerous comments that urged the Commission to provide the benefits of umbrella registration to the ADV filings of registered investment advisers with a principal office outside the United States, the Commission declined to do so.
      • Similarly, the SEC declined to provide the benefits of umbrella registration to the ADV filings of exempt reporting advisers on the same terms as U.S.-based registered investment advisers. The Commission did indicate that the SEC Staff views expressed in Frequently Asked Questions permitting certain exempt reporting advisers to file a single Form ADV in certain circumstances are not withdrawn as a result of the ADV amendments.
    • Social Media Disclosures. The proposed rule would have required expanded disclosure of social media sites and portals. The final rule largely gives effect to the proposal.
      • Any social media sites controlled by the filing adviser must be listed on the new Form ADV and promptly updated following any change.
      • The SEC specifically acknowledged that the use of new social media outlets would trigger multiple amendments, but did not feel that this obligation was unduly burdensome.
    • Other Offices. The amended Form ADV will continue to require disclosures of other offices.
      • More other offices will be required to be disclosed (25).
      • Advisers will be required to specify the business activities occurring in each office other than the firm’s principal place of business.
    • Employee Compensation. If an adviser compensates an employee for finding “clients,” the amount of the compensation paid will need to be disclosed in the new Form ADV.
    • Use of Third-Party Compliance Auditors. The SEC did not include in the amended Form ADV a requirement that RIAs disclose third-party compliance auditors. (But note that the SEC Staff had previously indicated that they are working on a proposal that would involve mandatory annual audits of the private fund management business.)

    Performance Recordkeeping

    The Commission has adopted several final rules requiring registered advisers to retain a broader set of books and records related to performance advertising. First, advisers will be required to retain copies of all written communications sent by any such investment adviser relating to “the performance or rate of return of any or all managed accounts or securities recommendations.” Second, advisers will now be required to retain records that demonstrate the calculation of the performance or rate of return in any communication to any person (as opposed to the prior rule, which was limited to communications circulated to 10 or more persons). Accordingly, registered advisers should review their approval and retention procedures for both broadly distributed and narrowly tailored performance presentations.

    Authored by Marc E. Elovitz, Brian T. Daly and Christopher S. Avellaneda.

    If you have any questions concerning this Alert, please contact your attorney at Schulte Roth & Zabel or one of the authors.


    [1] Form ADV and Investment Advisers Act Rules, IA-4509 (Aug. 25, 2016). The Commission also made certain clarifying, technical and other amendments to Form ADV.

    [2] Amendments to Form ADV and Investment Advisers Act Rules, Release No. IA-4091 (May 20, 2015) (the “Proposing Release”).


    This information has been prepared by Schulte Roth & Zabel LLP (“SRZ”) for general informational purposes only. It does not constitute legal advice, and is presented without any representation or warranty as to its accuracy, completeness or timeliness. Transmission or receipt of this information does not create an attorney-client relationship with SRZ. Electronic mail or other communications with SRZ cannot be guaranteed to be confidential and will not (without SRZ agreement) create an attorney-client relationship with SRZ. Parties seeking advice should consult with legal counsel familiar with their particular circumstances. The contents of these materials may constitute attorney advertising under the regulations of various jurisdictions.

    In depth
    Authors

    Marc E. Elovitz

    Partner

    New York – 919 Third Avenue

    Christopher S. Avellaneda

    Partner

    New York – 919 Third Avenue

    More insights

  • NYDFS Proposes Detailed and Sweeping Cybersecurity Regulation for Financial Services Companies

    NYDFS Proposes Detailed and Sweeping Cybersecurity Regulation for Financial Services Companies

    ARTICLE / CLIENT ALERT

    NYDFS Proposes Detailed and Sweeping Cybersecurity Regulation for Financial Services Companies

    September 15, 2016

    Read time: 13 min

    Key takeaways
    Overview

    On Sept. 13, 2016, the New York State Department of Financial Services (“NYDFS”) issued a proposed regulation that would impose new, rigorous cybersecurity requirements on banks, consumer lenders, money transmitters, insurance companies and certain other financial service providers (each, a “Covered Entity”) regulated by the NYDFS (the “Proposed Regulation”).[1] Given New York’s importance in the financial services industry, not only would the effect of the Proposed Regulation be felt immediately across the country, other regulators may follow New York’s example.

    In some respects, the Proposed Regulation is consistent with the principles set forth in documents that other regulators have issued, such as the Information Technology Examination Handbook released by the Federal Financial Institutions Examination Council (FFIEC) and the Cybersecurity Framework released by the National Institute of Standards and Technology (NIST). This is true of the Proposed Regulation’s basic requirement that Covered Entities create and implement a written policy — overseen by a qualified Chief Information Security Officer (“CISO”) — to protect against, detect, document and respond to attempts to access, disrupt, or misuse Covered Entities’ consumer information or technology systems.

    But the NYDFS regulations also contain some specific commands that go significantly beyond what other regulators have suggested, much less required. Most notably, the Proposed Regulation has several directives tied to “Nonpublic Information,” and it defines that term broadly, including any information that would be considered nonpublic personal information under the Gramm-Leach-Bliley Act’s privacy rule (“GLBA Privacy Rule”). As a result, it captures far more data than what New York’s existing data protection law defines as “personal information.”[2] The requirement that “Nonpublic Information” be encrypted at rest (and not just in transit) may therefore be a significant burden on Covered Entities, as may the requirement that the Superintendent be notified of any “Cybersecurity Event” that “affects” Nonpublic Information. Further, senior management must certify annually that the Covered Entity is in compliance.

    The Proposed Regulation is open for public comment for the next 45 days and is slated to take effect Jan. 1, 2017.[3] The NYDFS states that the Proposed Regulation is intended to impose minimum standards on the industry while allowing sufficient flexibility for Covered Entities to adapt to the threats they face and the technologies available to secure their information and systems.[4] The NYDFS notes that it based the Proposed Regulation on extensive surveys of and discussions with Covered Entities; yet many of these surveys and the reports the NYDFS generated are already one or two years old.[5]

    Who and What the Proposed Regulation Covers

    The Proposed Regulation defines a “Covered Entity” as “any [p]erson operating under or required to operate under a license, registration, charter, certificate, permit, accreditation or similar authorization under the [New York] banking law, the insurance law or the financial services law.”[6] Recognizing that certain smaller entities may have difficulty reaching the NYDFS minimum standard, the Proposed Regulation exempts them from some but not all of the Proposed Regulation’s requirements.[7] Nonetheless, the Proposed Regulation may exert influence beyond Covered Entities insofar as it affects the third-party vendors of those entities.

    The goal of the Proposed Regulation is to secure “Nonpublic Information” from misuse, disruption and unauthorized access, and as noted above, such information is defined broadly.[8] It includes not only competitively sensitive information and intellectual property, but also numerous categories of information that a Covered Entity receives from or about consumers, including information considered nonpublic personal information under the GLBA Privacy Rule.[9] Accordingly, the Proposed Regulation’s definition of Nonpublic Information is far broader than what New York’s existing data protection law defines as “personal information.”[10]

    Formalizing a Cybersecurity Program

    Under the Proposed Regulation, Covered Entities must have a written cybersecurity policy that outlines every aspect of its cybersecurity program and explicitly addresses how the Covered Entity complies with each of the Proposed Regulation’s requirements.[11] At a minimum, the written policy must address:

    • Information security;
    • Data governance and classification;
    • Access controls and identity management;
    • Business continuity and disaster recovery planning and resources;
    • Capacity and performance planning;
    • Systems operations and availability concerns;
    • Systems and network security;
    • Systems and network monitoring;
    • Systems and application development and quality assurance;
    • Physical security and environmental controls;
    • Customer data privacy;
    • Vendor and third-party service provider management;
    • Risk assessment; and
    • Incident response.[12]

    In addition to outlining all the steps the Covered Entity is taking in these areas, the Covered Entity must also include an incident response plan that lays out how it will respond to any attempted or actual access, disruption or misuse of its systems and information. The incident response plan must also identify and allocate the precise roles and responsibilities of the individuals who will carry out the actions it specifies.[13]

    To helm those efforts, the Covered Entity must designate a “qualified” CISO who will oversee and implement the Covered Entity’s written policy and cybersecurity program.[14] In addition, the Covered Entity must also employ sufficient cybersecurity personnel to carry out its program, who must undergo sufficient training to stay abreast of cybersecurity threats and best practices.[15] Further, the Covered Entity must provide all staff with “regular” cybersecurity training that makes them aware of the threats and best practices specific to the Covered Entity’s risk assessment.

    The CISO must complete that risk assessment (including the vulnerabilities posed by third parties’ access to the Covered Entity’s information and systems), penetration testing and a comprehensive review and update of the cybersecurity policy at least once a year, and report on the Covered Entity’s efforts and any material attempts or attacks to the board and senior officers at least twice a year.[16]

    Limiting Access to Information and Systems

    In a major change, under the Proposed Regulation, Covered Entities will be required to encrypt their Nonpublic Information — by January 2018 for Nonpublic Information in transit and by January 2022 for Nonpublic Information at rest.[17] Covered Entities must also require multifactor authentication for remote access to its systems or for privileged access to the servers that contain Nonpublic Information. Web applications that capture, display or interface with Nonpublic Information must require risk-based authentication and must support multifactor authentication.[18] Because of the breadth of what the Proposed Regulation considers Nonpublic Information, implementation of those security measures may be costly for certain Covered Entities, as much of the electronic contact a Covered Entity has with its clients or customers will have to be conducted over secure platforms.

    The Proposed Regulation requires Covered Entities to consider which employees need access to which information and systems, and to curtail access to the systems and information accordingly.[19] The Proposed Regulation also makes Covered Entities responsible for the cybersecurity practices of the third parties who hold or can access Nonpublic Information. Covered Entities will be required to conduct due diligence on their third-party providers’ policies and procedures and assess the risks that stem from using those third parties. The Proposed Regulation suggests that Covered Entities include in their written policy the preferred provisions the Covered Entity will include in its vendor contracts, for example, to have the right to audit the third party’s cybersecurity capabilities.[20] Even with favorable contract terms, however, that level of responsibility over third parties will be challenging for many Covered Entities given that the third party’s cybersecurity is in someone else’s hands and the Covered Entity will in many cases not have full and direct access to examine or control the cybersecurity program the third party adopts.

    Reporting

    When something goes wrong, the Covered Entity must report it to the Superintendent. Specifically, any attempt or attack “that has a reasonable likelihood of materially affecting the normal operation of the Covered Entity or that affects Nonpublic Information” must be reported to the Superintendent within 72 hours after the Covered Entity becomes aware of the event. Any notice the Covered Entity provides to any government or self-regulatory agency must also be given to the Superintendent.[21] As a result, a Covered Entity may have to report a data breach or attempted breach to the Superintendent before the Covered Entity has established a full understanding of the nature and extent of the incident.

    Recordkeeping on the One Hand; Timely Destruction on the Other

    Covered Entities must maintain sufficiently detailed records to be able to reconstruct who accessed its digital and physical systems when, and to harness that information to successfully detect attempted and actual attacks. Covered Entities must also ensure that the logs that record such access are protected against tampering or alteration. Covered Entities must maintain those “audit trail” records for at least six years.[22]

    Nonetheless, Covered Entities are to evaluate and destroy Nonpublic Information that is no longer necessary for the provision of the product or services for which such information was originally provided or obtained, unless some other law (such as, at a minimum, the Proposed Regulation) requires that Nonpublic Information to be maintained.[23] It is often best practice to limit the personal information a business has about its customers to only what is necessary currently for legitimate business purposes, including so that any data breach that does occur will be less harmful to the customers and the business. However, Covered Entities are subject to extensive recordkeeping requirements from many sources and, in many cases, are under the threat of foreseeable litigation, for which they must preserve the materials they may need to exchange in discovery on pain of sanctions for spoliation.

    Annual Certification

    The Proposed Regulation provides that beginning Jan. 15, 2018, Covered Entities must have the chair of the board or another senior officer (if the Covered Entity has no board) certify in writing to the Superintendent that the Covered Entity is in full compliance with the Proposed Regulation.[24] The Proposed Regulation includes the text of that certification in an appendix. In addition to certifying that the signatory has reviewed all “necessary” material and that the Covered Entity is in compliance, the Covered Entity must provide a report on all remedial efforts planned or underway and all the attempts or attacks that occurred in the prior year that were required to be reported to the Superintendent. The records that support the certification must be maintained for at least five years and made available to the Superintendent upon request.[25] The fact that certification backup materials need only be maintained for five years, but the audit trail materials must be maintained for six years, suggests that the Superintendent may also rely on the audit trail to reach further back in time to find further errors when it enforces the Proposed Regulation.

    In fact, the individuals who sign that certification may be exposed to personal liability if the Covered Entity is ultimately found to be noncompliant. The Superintendent may enforce the Proposed Regulation pursuant to her “authority under any applicable laws.” Such laws include the provisions of the New York Banking Law, Insurance Law and Finance Law that impose civil and even criminal penalties for false disclosures made with an intent to deceive a regulator.[26]

    Conclusion

    While the Proposed Regulation is not yet law and remains open for public comment for the next 45 days, the NYDFS and the State of New York have indicated that securing New York’s financial services firms and consumers from the increasing threats posed by “nation-states, terrorist organizations, and independent criminal actors” is a top priority. In order to meet the Jan. 1, 2017 effective date, Covered Entities should now begin assessing their cybersecurity risks, policies and procedures to develop or enhance their cybersecurity program and to begin documenting and tracking their compliance efforts.

    Authored by Joseph P. Vitale, Michael L. Yaeger and Noah N. Gillespie.

    If you have any questions concerning this Alert, please contact your attorney at Schulte Roth & Zabel or one of the authors.


    [1] Cybersecurity Requirements for Financial Services Companies (“Proposed Regulation”) (Sept. 13, 2016) (to be codified at 23 NYCRR Part 500), available at http://www.dfs.ny.gov/legal/regulations/proposed/rp500t.pdf.

    [2] See N.Y. Gen Bus. L. § 899-aa2.

    [3] Persons wishing to submit a public comment on the Proposed Regulation may write to comments@dfs.ny.gov or to Maria T. Vullo, Superintendent of Financial Services, New York Department of Financial Services, One State Street, New York, NY 1004-1511.

    [4] Proposed Regulation at 2.

    [5] See Press Release, Governor Cuomo Announces Proposal of First-in-the-Nation Cybersecurity Regulation to Protect Consumers and Financial Institutions (Sept. 13, 2016), available at http://www.dfs.ny.gov/about/press/pr1609131.htm; DFS Reports and Publications (last visited Sept. 14, 2016), available at http://www.dfs.ny.gov/reportpub/dfs_reportpub.htm#misc.

    [6] Proposed Regulation § 500.01(c).

    [7] Specifically, otherwise Covered Entities that have: (1) fewer than 1,000 customers in each of the last three calendar years; (2) less than $5 million in gross annual revenue in the last three fiscal years; and (3) less than $10 million in total GAAP year-end assets (including the assets of all their affiliates) enjoy an exemption from designating a CISO, hiring sufficient cybersecurity personnel, training, encryption and multifactor authentication, conducting penetration testing, maintaining an audit trail, and verifying application security. Proposed Regulation § 500.18. In contrast, all Covered Entities (regardless of size) must undertake a cybersecurity program, draft a written cybersecurity policy, restrict access privileges, conduct a risk assessment, report material attacks to the NYDFS Superintendent (the “Superintendent”) within 72 hours, destroy old information, and assess the vulnerabilities of the third parties with access to their information — and are subject to enforcement by the Superintendent for any failure to do so. Id.

    [8] Proposed Regulation § 500.01(g).

    [9] Nonpublic Information includes “[a]ny information that an individual provides to a Covered Entity in connection with seeking or obtaining any financial product or service from the Covered Entity” and “[a]ny information that can be used to distinguish or trace an individual’s identity, including but not limited to … any information that is linked or linkable to an individual.” By contrast, N.Y. Gen Bus. L. § 899-aa2 defines “personal information” to include: (1) a social security number; (2) a driver’s license or non-driver ID number; or (3) an account number, credit card or debit card number, in combination with any required security code, access code or password that would permit access to an individual’s financial account. Personal information does not include publicly available info that is lawfully made available to the general public from federal, state, or local government records.

    [10] Id. However, the Proposed Regulation does not require Covered Entities to secure information that is generally available to the public or which an individual can direct not to be made available to the public but has not so directed. Id. § 500.01(j).

    [11] See id. § 500.02-.03.

    [12] Id. § 500.03(a).

    [13] Id. § 500.16.

    [14] Id. § 500.04.

    [15] Id. § 500.10.

    [16] Id. § 500.03-.05, .08-.09, .11.

    [17] Id. § 500.15.

    [18] Id. § 500.12. “Multifactor authentication means authentication through verification of at least two of the following types of authentication factors: (1) Knowledge factors, such as a password; or (2) Possession factors, such as a token or text message on a mobile phone; or (3) Inherence factors, such as a biometric characteristic.” Id. § 500.01(f). “Risk-based authentication means any risk-based system of authentication that detects anomalies or changes in the normal use patterns of a Person and requires additional verification of the Person’s identity when such deviations or changes are detected, such as through the use of challenge questions.” Id. § 500.01(k).

    [19] Id. § 500.07.

    [20] Id. § 500.11.

    [21] Id. § 500.17(a).

    [22] Id. § 500.06.

    [23] Id. § 500.13.

    [24] Id. § 500.17(b).

    [25] Id. § 500.17(b).

    [26] See, e.g., N.Y. Bank. Law § 672; see also “NYDFS Issues AML/Sanctions Programs and Annual Certification Requirements for Banks, Money Transmitters and Check Cashers,” SRZ Client Alert, July 6, 2016 (discussing a similar provision in a new, final NYDFS anti-money laundering regulation).


    This information has been prepared by Schulte Roth & Zabel LLP (“SRZ”) for general informational purposes only. It does not constitute legal advice, and is presented without any representation or warranty as to its accuracy, completeness or timeliness. Transmission or receipt of this information does not create an attorney-client relationship with SRZ. Electronic mail or other communications with SRZ cannot be guaranteed to be confidential and will not (without SRZ agreement) create an attorney-client relationship with SRZ. Parties seeking advice should consult with legal counsel familiar with their particular circumstances.
    The contents of these materials may constitute attorney advertising under the regulations of various jurisdictions.

    In depth
    Authors
    More insights

  • The Impact of the EU Data Protection Regulation

    ARTICLE

    The Impact of the EU Data Protection Regulation

    September 14, 2016

    Read time: 2 min

    Key takeaways
    Overview

    Paul Melot de Beauregard, Melanie Bruneau, Ann Killilea, Maximilian Baur and Antoine Rohan de Chabot wrote this bylined article concerning the EU General Data Protection Regulation 2016/679, which will replace the current legal privacy framework as of May 2018.

    In depth
    Authors
    More insights

  • Ninth Circuit Affirms Mandatory Subordination of Investor’s Securities Claim in Individual Debtor’s Reorganization Case

    Ninth Circuit Affirms Mandatory Subordination of Investor’s Securities Claim in Individual Debtor’s Reorganization Case

    ARTICLE / CLIENT ALERT

    Ninth Circuit Affirms Mandatory Subordination of Investor’s Securities Claim in Individual Debtor’s Reorganization Case

    September 14, 2016

    Read time: 7 min

    Key takeaways
    Overview

    “[T]he claims of [an individual debtor’s] general unsecured creditors are ‘senior to or equal [to]’” a defrauded investor’s security claim under Bankruptcy Code (“Code”) § 510(b), held the U.S. Court of Appeals for the Ninth Circuit on Aug. 22, 2016. In re Del Biaggio, 2016 WL 4435904, *9 (9th Cir. Aug. 22, 2016). The investor (“F”) had filed a claim against the debtor based on his wrongful failure to fund, through his affiliated limited liability company (“LLC”), his share in an acquisition venture with F. The Ninth Circuit affirmed the lower courts’ effective “superimpos[ing]” of the “capital structure [of the debtor’s affiliate] … on the debtor to determine the correct level of priority.” Id.

    F’s claim was thus rooted in damages he sustained by the conduct of LLC, the debtor’s affiliate. The court relied heavily on a recent Second Circuit decision, In re Lehman Bros. Inc., 808 F.3d 942, 946 (2d Cir. 2015) (“claims arising from securities of a debtor’s affiliate should be subordinated” to all other “senior or equal” claims in debtor’s bankruptcy case).

    Relevance

    Code § 510(b) provides in relevant part that “a claim … for damages arising from the purchase or sale of … a security [of the debtor] or of an affiliate of the debtor … shall be subordinated to all claims or interests that are senior to or equal to the claim … represented by such security” (emphasis added). As the Second Circuit noted, “[e]very other court that has applied § 510(b) to claims based on affiliate securities — when the debtor was a corporate entity — has required subordination.” 808 F.3d at 950, citing, among others, In re Am. Hous. Found., 785 F.3d 143 (5th Cir. 2015) (creditor’s guaranty claim “arising from equity investments in a debtor’s affiliate should be treated the same as equity investments in the debtor itself — i.e., … subordinated to the claims of general creditors”). According to the Fifth Circuit in American Housing, § 510(b) “serves to effectuate one of the general principles of corporate and bankruptcy law: that creditors are entitled to be paid ahead of shareholders in the distribution of corporate assets.” Id. at 153. This mandatory subordination clause “applies whether the securities were issued by the debtor or by an affiliate of the debtor.” Id., quoting 4 Collier, Bankruptcy 510.04[04] (16th ed. 2014) (emphasis added). Thus, “claims arising from equity investments in a debtor’s affiliate should be treated the same as equity investments in the debtor itself — i.e., both are subordinated to the claims of general creditors.” Id.

    Del Biaggio, unlike Lehman and American Housing, is an individual debtor case. The Ninth Circuit’s Bankruptcy Appellate Panel (“BAP”), an intermediate appellate court composed of three bankruptcy judges, had previously found that “§ 510(b) was ambiguous as to whether the law applies to individual debtors,” holding “that applying the statute to individual debtors was outside of Congress’ intent.” 2016 WL 4435904, *5, citing In re Kahn, 523 B.R. 175, 183 (B.A.P. 9th Cir. 2014). As shown below, though, the Ninth Circuit was “not persuaded,” Id., stressing that F held “a damages claim”; his “investments are securities”; and that the parties’ investment entity “is an affiliate.” Id. at *3.

    Facts

    F and the debtor had originally been part of a group to acquire a professional hockey team. The group’s acquisition vehicle was known as “Holdings,” and the debtor agreed to invest in Holdings through LLC, his wholly-owned affiliate. F learned later that the debtor “never had the funds to support his [promised] guarantees and that the [funds the debtor] already invested was in fact money he had embezzled from his clients.” Id. at *2.

    F then charged the debtor with fraud for misrepresenting his ability to invest about $40 million in equity through LLC and to pay part of the cost of debt financing. After defaulting on his obligations to Holdings, the debtor later filed a Chapter 11 petition and was convicted “for various financial frauds and sentenced to an eight-year prison term.” 2016 WL 4435904, at *2.

    F “filed a general unsecured claim against [the debtor’s] bankruptcy estate seeking damages of an undetermined amount arising from [the debtor’s] fraud in the [proposed investment] transaction,” later seeking “damages of $38,632,075,” which included his own “initial $31-million investment … the $5 million of subordinated debt he [had been forced to issue] to [the investment company] … and the $2,632,075 paid in [a capital call].” In response, the liquidating trust for the debtor’s estate sought subordination and disallowance of F’s claim, relying on Code § 510(b).

    The district court affirmed the bankruptcy court’s subordination of F’s claim. Both courts relied on the “plain language of the statute”; F’s “investor” status in bargaining “for both a greater share of profits and a greater share of risks” than the debtor’s unsecured creditors; and the “conclusion that notes or shares issued by a subsidiary create no claim to the assets of a parent.” Id. at *2.

    Analysis

    According to the Ninth Circuit, F’s “damages claim is clearly one ‘arising from’ the sale or purchase of securities in Holdings.” Id. at *4. His “claim is really no claim at all but for his investment in Holdings.” Nor did the court have to review the statute’s legislative history, for the language was clear. Id. at *5. Finally, because “Congress included within § 510(b)’s ambit claims arising from the purchase of the securities of an affiliate of the debtor,” it would be inequitable to allow F’s investor claim “to stand on par with” the debtor’s unsecured creditors. Id. at *5-*6 (emphasis in original).

    Section 510(b) is thus “not limited to corporate debtors.” Id. at *7. Regardless of the nature of F’s claim — an affiliate’s security or a claim represented by that security — under “any legitimate reading of § 510(b), the claims of [the debtor’s] general unsecured creditors are ‘senior or equal [to]’ [F’s] claim.” Id. at *9.

    Comment

    Del Biaggio is one more example of the obstacles facing individual Chapter 11 debtors. Although F’s claim was subordinated to the claims of the debtor’s unsecured creditors, it may still be valid, meaning that, in at least five Circuits, the debtor must still pay that claim in full, to the extent valid, before retaining any of its property. These Circuits, plus “a sizeable majority of the district, bankruptcy appellate and bankruptcy courts,” have agreed that “the absolute priority rule continue[s] to apply in Chapter 11 reorganizations … . ” In re Zachary, 2016 WL 360519, *1, *4 (9th Cir. Jan. 28, 2016); accord, In re Maharaj, 681 F. 3d 558, 563, 575 (4th Cir. 2012); Ice House Am., LLC v. Cardin, 751 F. 3d 734, 740 (6th Cir. 2014); In re Lively, 717 F. 3d 406, 410 (5th Cir. 2013); In re Stephens, 704 F. 3d 1279, 1287 (10th Cir. 2013). In short, creditors still have the better hand in individual Chapter 11 cases.

    Aside from the individual debtor issue, Del Biaggio’s reasoning is consistent with that of other Circuits, including Lehman. See, e.g., In re Med Diversified Inc., 461 F. 3d 251, 255, 259 (2d Cir. 2006); In re Am. Hous. Found., 785 F. 3d 143 (5th Cir. 2015); In re THC Fin. Corp., 679 F. 2d 784, 786 (9th Cir. 1982).

    Authored by Michael L. Cook.

    If you have any questions concerning this Alert, please contact your attorney at Schulte Roth & Zabel or the author.


    This information has been prepared by Schulte Roth & Zabel LLP (“SRZ”) for general informational purposes only. It does not constitute legal advice, and is presented without any representation or warranty as to its accuracy, completeness or timeliness. Transmission or receipt of this information does not create an attorney-client relationship with SRZ. Electronic mail or other communications with SRZ cannot be guaranteed to be confidential and will not (without SRZ agreement) create an attorney-client relationship with SRZ. Parties seeking advice should consult with legal counsel familiar with their particular circumstances. The contents of these materials may constitute attorney advertising under the regulations of various jurisdictions.

    In depth
    Authors
    More insights

  • View From McDermott: Section 457(f) Proposed Regulations—Not What We Expected (In a Good Way)

    ARTICLE

    View From McDermott: Section 457(f) Proposed Regulations—Not What We Expected (In a Good Way)

    September 12, 2016

    Read time: 2 min

    Key takeaways
    Overview

    Mary Samsa and Ruth Wimer wrote this bylined article on the new proposed regulations for Internal Revenue Code Section 457(f) retirement plans. The authors wrote that the proposal offers “welcome and surprising new opportunities” for deferred compensation arrangements, but cautioned that it will “require greater scrutiny with respect to drafting” such plans.

    In depth
    Authors
    More insights

  • Listed Companies and Antitrust Disclosure (Sociétés Cotées et Disclosure Antitrust )

    ARTICLE

    Listed Companies and Antitrust Disclosure (Sociétés Cotées et Disclosure Antitrust )

    September 12, 2016

    Read time: 2 min

    Key takeaways
    Overview

    Jacques Buhart and Lionel Lesur wrote this bylined article on the disclosure challenges for listed companies facing a competition regulatory action. “The company must ask quickly about how to reconcile its stock market disclosure obligations and confidentiality on the competition action,” the authors wrote, noting that while market authorities want full disclosure, competition authorities wish to preserve the confidentiality of investigations.Read the full article.

    In depth
    Authors
    More insights

  • Sociétés Cotées et Disclosure Antitrust (Listed Companies and Antitrust Disclosure)

    ARTICLE

    Sociétés Cotées et Disclosure Antitrust (Listed Companies and Antitrust Disclosure)

    September 11, 2016

    Read time: 2 min

    Key takeaways
    Overview

    Jacques Buhart and Lionel Lesur wrote this bylined article on conflicts listed companies face in disclosing a competition law enforcement action. “While the stock market authorities (such as the SEC in the US) frequently require companies to disclose to the market any information enabling informed investment decisions, the competition authorities are anxious to preserve confidentiality of investigations, at least while the matter is active,” the authors wrote. Read the full article.

    In depth
    Authors
    More insights

  • How to Get Your German Deal to the Goal Line

    ARTICLE

    How to Get Your German Deal to the Goal Line

    September 8, 2016

    Read time: 2 min

    Key takeaways
    Overview

    Soren Lindstrom and Lindsey Reighard wrote this bylined article on ways US companies can gain an advantage over competitors in the tough but attractive German cross-border transactions market. The authors discussed such tactics as lock-box financing, data disclosure, indemnity insurance, arbitration clauses and notarization to take advantage of Germany’s “strong growth and stability despite recent economic and political challenges in Europe.”

    In depth
    Authors

    Lindsey Reighard

    Partner

    Dallas

    More insights

  • Seventh Circuit Limits Bankruptcy Safe Harbor Protection

    Seventh Circuit Limits Bankruptcy Safe Harbor Protection

    ARTICLE / CLIENT ALERT

    Seventh Circuit Limits Bankruptcy Safe Harbor Protection

    September 8, 2016

    Read time: 8 min

    Key takeaways
    Overview

    The safe harbor protection of Bankruptcy Code (“Code”) §546(e) does not protect “transfers that are simply conducted through financial institutions,” held the U.S. Court of Appeals for the Seventh Circuit on July 28, 2016. FTI Consulting Inc. v. Merit Management Group LP, 2016 WL 4036408, *1 (7th Cir. July 28, 2016). Because the debtor’s transfer of funds to the transferee passed through a financial institution acting only as a conduit that was not one of the parties covered by §546(e) (i.e., “commodity broker, forward contract merchant, stockbroker, financial institution, financial participant, or securities clearing agency”), the asserted fraudulent transfer was not protected by §546(e) and was thus recoverable, said the court when reversing the district court’s dismissal of the trustee’s claim.

    Relevance

    Appellate courts, including the Seventh Circuit, have generally agreed on the vitality and breadth of the safe harbor defense contained in §546(e). It insulates from the trustee’s fraudulent transfer or preference attack a “settlement payment” or “margin payment” on a “securities contract,” “commodity contract,” or “forward contract … made by or to (or for the benefit of)” certain “financial institutions,” except when the debtor makes the payment with “actual intent to hinder, delay, or defraud” creditors under Code §548(a)(1)(A).

    Despite policy arguments by trustees, creditors and academics, the Courts of Appeals have generally refused to add to the Code’s plain language. See, e.g., In re Quebecor World (USA) Inc., 719 F.3d 94 (2d Cir. 2013) (held, payments by debtor to institutional noteholder trustee for noteholders “in exchange for private placement notes … clearly fell within the safe harbor for ‘transfers made … in connection with a securities contract.’“); In re QSI Holdings, Inc., 57 F.3d 545, 551 (6th Cir. 2009) (bank’s role in leveraged buyout “sufficient to satisfy the requirement that the transfer was made to a financial institution,” although bank was only an exchange agent). In FTI, however, the Seventh Circuit refused to “interpret the safe harbor so expansively that it covers any transaction involving securities that uses a financial institution … as a conduit for funds.” 2016 WL 4036408, at *6, agreeing with In re Munford, Inc., 98 F.3d 604, 610 (11th Cir. 1996) (2-1) (Code §546(e) inapplicable to payments made by debtor to shareholders when financial institutions acted as mere conduits). As the Seventh Circuit stressed, Congress never said “that acting as a conduit for a transaction between non-named entities is enough to qualify for the safe harbor … .” 2016 WL 4036408, at *7. The court, of course, recognized that it was “taking a different position from the one adopted by five of our sister circuits, which have interpreted section 546(e) to include the conduit situation.” Id. at *6. This circuit split makes FTI a likely candidate for Supreme Court review.

    Facts

    “Buyer” agreed to buy all of the shares of an entity known as B from certain entities, including “Seller,” a 30-percent shareholder of B, for $55 million, borrowing the funds from a group of lenders, with the transfer of the funds flowing through “Bank.” As the Seventh Circuit noted, “neither [Buyer] nor [Seller] were ‘parties in the securities industry,’ [but were] simply corporations that wanted to exchange money for privately held stock.” Id. at *6.

    After Buyer later filed a Chapter 11 petition, its litigation trustee sued Seller under Code §548 and applicable state law to recover $16.5 million, representing Seller’s 30-percent equity interest paid by Buyer to Seller. Seller argued that the transfer was “made by or to (or for the benefit of)” an entity named in Code §546(e),” namely, a “financial institution” (i.e., Bank), and was, therefore, protected by the safe harbor. Because the funds passed through Bank, the district court dismissed the trustee’s complaint, agreeing with Seller that the transfer had passed through a financial institution. Seller “did not rely on its own status …, because … neither [Buyer] nor [Seller] is a commodity broker, forward contract merchant, stock broker, financial institution, financial participant, or securities clearing agency (the entities named in section 546(e)).” Id. at *1. Rather, Seller argued that the safe harbor applied because of “the minor involvement of [Bank and the lenders].” Id.

    Analysis

    The Seventh Circuit carefully examined the language of §546(e), its statutory context, its legislative history and its significance in the securities industry.

    Statutory Language. First, said the court, the “language of the statute, standing alone … is unclear whether the safe harbor was meant to include intermediaries, or if it is limited to what we might think of as the real parties in interest — here, [Buyer and Seller].” Id. at *2. Because Code §548 refers to the avoidance of transfers to or for the benefit of entities subject to fraudulent transfer liability, the court understood “the safe harbor as applying to the transfers that are eligible for avoidance in the first place.” Id. at *3. And “because the safe harbor is meant to protect covered entities against avoidance where it might occur, … [§]546(e) provides a safe harbor only where the debtor has [made a transfer] to the covered entity.” Id. Most important, the court explained, the “$16.5 million transferred to [Seller] … was one made by the debtor using a bank as a conduit.” Id. Indeed, it is “the receipt of value [that] … gives an entity the safe-harbor protections of 546(e) … . [I]t is the economic substance of the transaction that matters.” Id. at *4.

    Relying on one of its earlier decisions, the court reasoned “that transfers ‘made by or to (or for the benefit of)’ in the context of 546(e) [apply only] to transfers made to ‘transferees’… .”. Id. at *5, citing Bonded Financial Services, Inc. v. European American Bank, 838 F.2d 890, 893 (7th Cir. 1988). In that case, when a bank “acted as a financial intermediary” and “received no benefit,” the court held it was not a “transferee” and, therefore, was not liable under the Code. In other words, Bank here was not a transferee, but only a conduit, and could not be held liable.

    Legislative History. When Congress created the safe harbor in 1982, “[n]othing … indicated that the safe harbor applied to financial institutions in their capacity as intermediaries.” Id., at *5. As the court had previously acknowledged in Grede v. FCStone LLC, 746 F.3d 244, 252 (7th Cir. 2014), Congress intended to “protect … the market from systemic risk and allow … parties in the securities industry to enter into transactions with greater confidence,” and to prevent “one large bankruptcy from rippling through the securities industry.” Id. Although the Seventh Circuit and other appellate courts have held that section 546 should be construed “broadly,” there are still “limits” on its construction. Here, neither Buyer nor Seller were “parties in the securities industry.” Id. at *6. “The safe harbor addresses cases where the debtor-transferor or transferee is a financial institution or the other named entity.” Id. Moreover, if the transfer to Seller were avoided here, “there is no evidence that it would have any impact on [the lenders, Bank] or any other bank or entity named in section 546(e).” Id. at *6.

    Circuit Split. The Seventh Circuit acknowledged that “five of our sister circuits … have interpreted section 546(e)” differently, but noted that the Eleventh Circuit “agrees with us.” Id., citing In re Munford, 98 F.3d 604, 610 (11th Cir. 1996) (2-1). Despite Seller’s argument that Congress had impliedly rejected Munford with a 2006 amendment, the Seventh Circuit did “not believe that Congress would have jettisoned Munford’s rule” indirectly. Nor had Congress said “that acting as a conduit for a transaction between non-named entities is enough to qualify for the safe harbor.” Id. at *7.

    Comment

    FTI confirms that entities uncovered by §546(e) will not be able to rely on the safe harbor because of the coincidental flow of funds through a “financial institution” intermediary. The Seventh and Eleventh Circuits, for example, would reverse a decision such as AP Services LLP v. Silva, 483 B.R. 63, 68-69, 71 (S.D.N.Y. 2012) (held, §546(e) required dismissal of the fraudulent transfer complaint when failed leverage buyout preceded bankruptcy; debtor transferred funds “directly to [the selling shareholder defendants’] bank accounts and [the funds] did not pass … through a clearinghouse or [similar] intermediary.”). In contrast, as noted, the Second, Third, Sixth, Eighth and Tenth Circuits do not accept the Seventh Circuit’s analysis. The issue may still remain open in the First, Fourth, Fifth, Ninth and D.C. Circuits. Only the Supreme Court can resolve this circuit split and prevent forum shopping.

    Authored by Michael L. Cook and David M. Hillman.

    If you have any questions concerning this Alert, please contact your attorney at Schulte Roth & Zabel or one of the authors.


    This information has been prepared by Schulte Roth & Zabel LLP (“SRZ”) for general informational purposes only. It does not constitute legal advice, and is presented without any representation or warranty as to its accuracy, completeness or timeliness. Transmission or receipt of this information does not create an attorney-client relationship with SRZ. Electronic mail or other communications with SRZ cannot be guaranteed to be confidential and will not (without SRZ agreement) create an attorney-client relationship with SRZ. Parties seeking advice should consult with legal counsel familiar with their particular circumstances. The contents of these materials may constitute attorney advertising under the regulations of various jurisdictions.

    In depth
    Authors
    More insights