United States: Current Structuring May Not Shield Private Equity Firms From ERISA Liabilities

Last Updated: April 19 2016
Article by Robert A. Davis, Jr., James Frazier, Gillian Emmett Moldowan, Shane J. Stroud and Linda Z. Swartz

Most Read Contributor in United States, September 2017

On March 28, 2016, the U.S. District Court for the District of Massachusetts held that two private equity funds within Sun Capital were jointly and severally liable under the Employee Retirement Income Security Act of 1974, as amended (ERISA), for the $4.5 million multiemployer pension plan withdrawal liability of a portfolio company. This landmark decision appreciably changes the landscape for private equity investment in companies with pension plans or potential pension liabilities.

Practical Takeaways

Whether the analytical principles underpinning the Sun Capital decisions spread beyond the First Circuit or impact other areas of the law where controlled group concepts apply is an open question. However, even outside of the First Circuit, private equity firms and those buying portfolio companies from private equity owners should consider the following in light of Sun Capital:

  • Pricing It In. When valuing a new investment opportunity with pension liabilities, consider the increased possibility that pension liability could go beyond the portfolio company and become a liability of a private equity fund investor. For private equity portfolio companies with existing pension liabilities, consider evaluating the existing business model for the portfolio company to ensure economic assumptions cover the possibility of pension liabilities reaching fund investors – for example, increasing management and other fees charged to such companies on an ongoing basis to factor in the possibility that such liabilities could be assessed against the private equity investor.
  • Impact on Diligence. Many private equity firm buyers already have pension liabilities high on their list of diligence priorities when investigating a new investment opportunity, but additional focus on the scope of those liabilities, the likelihood of underfunding issues and the possibility of withdrawal (in the case of multiemployer pension plans) may be warranted. For those buying a portfolio company from a private equity firm, consideration should be given to expanding questions about pension liabilities beyond the target company to the private equity firm and its other portfolio companies as well. While not addressed by Sun Capital, if pension liabilities can reach up to fund investors on a "partnership-in-fact" theory, then using an ERISA controlled group analysis it is possible that a court could find that such liabilities reach back down to other portfolio companies deemed to be in the same controlled group. To the extent a private equity firm does not have centralized data about portfolio company pension contributions, it may want to consider implementing new record keeping procedures in light of the potential for expanded diligence requests.
  • Approach to ERISA Representations. In the context of financing and M&A agreements with respect to which private equity firms or portfolio companies are a party, lenders and buyers should consider expanding ERISA representations to expressly cover the private equity firm and its applicable funds and other portfolio companies. Likewise, private equity borrowers and sellers should evaluate their comfort with the scope of ERISA representations, even if not expanded from current market standard, as the entities that are deemed to be ERISA affiliates may be expanded.
  • Making Use of Club Deals. Based on the factors used by the District Court in finding that the Sun Capital funds and their portfolio company were under "common control," club deals where separately controlled private equity firms invest in a portfolio company each at a level below 80% may better insulate the firms and their funds from pension liability under ERISA.

Background

Under the Multiemployer Pension Plan Amendments Act (MPPAA), all "trades or businesses" under "common control" with an entity contributing to a multiemployer pension fund are jointly and severally liable for any withdrawal liability of the contributing entity. Generally, common control requires companies to be part of a corporate family with a common 80% owner. In light of this control test, private equity funds often structure investments so that no single fund owns more than 80% of a portfolio company.

In Sun Capital, two funds advised by Sun Capital Advisors, Inc. (Fund III and Fund IV) purchased indirect interests in an operating company, Scott Brass, Inc. (Scott Brass). Scott Brass later withdrew from a multiemployer pension plan to which it had contributed and filed for bankruptcy. The pension plan sought to assess withdrawal liability against Fund III (the 30% indirect owner of Scott Brass) and Fund IV (the 70% indirect owner of Scott Brass), arguing the funds were members of a controlled group with Scott Brass.

In 2013, the U.S. Court of Appeals for the First Circuit found that Fund IV was engaged in a "trade or business" for purposes of ERISA's controlled group test, stating that Fund IV, "through layers of fund-related entities, was not merely a 'passive' investor [in Scott Brass], but sufficiently operated, managed, and was advantaged by its relationship with" Scott Brass. The First Circuit remanded the case to the District Court to determine: (1) whether Fund III was also engaged in a "trade or business" and (2) whether Fund III and Fund IV were under "common control" with Scott Brass.

The District Court Decision

The District Court found that Fund III was engaged in a "trade or business." In considering whether Fund III qualified as a trade or business, the District Court applied the "investment plus" approach used by the First Circuit to determine that Fund IV was engaged in a trade or business.1 The District Court determined that Fund III received an economic benefit from its investment in Scott Brass that was beyond that available to an ordinary passive investor – carryforwards with the potential to offset management fees the fund may otherwise owe to its general partner for managing the investment. The District Court concluded that Fund III and Fund IV engaged in identical activities, and the court would not accept arguments that differences in the timing of the funds' economic benefit, or the contingencies of Fund III's benefit, distinguished Fund III from Fund IV with respect to being engaged in a trade or business.

The District Court found that Fund III and Fund IV were in "common control" with Scott Brass. The District Court found that Fund III and Fund IV were in common control with Scott Brass because the funds were a "partnership-in-fact", with a 100% ownership interest in Scott Brass, and that the "partnership-in-fact" was engaged in a trade or business. Because the funds were in "common control" with Scott Brass, they were jointly and severally liable for the withdrawal liabilities of Scott Brass.

Fund III and Fund IV were members of an ERISA controlled group with Scott Brass. The District Court acknowledged that absent the aggregation of Fund III's and Fund IV's interests, neither would be in an ERISA controlled group with Scott Brass because their individual interests would not put them in an 80% ownership group with Scott Brass. The court went on to find aggregation of the funds' interests was appropriate based on the existence of a "partnership-in-fact" between the funds that together held a 100% interest in Scott Brass, despite the funds' separate legal forms and the fact that all co-investment agreements between Fund III and Fund IV disclaimed any intent to form a partnership or joint venture. The District Court noted that the intent of ERISA's common control provisions is to prevent organizations from forming separate organizations to avoid ERISA obligations, and a bright-line ownership test is in some tension with that purpose. This tension is heightened where ownership is divorced from control.

The District Court worked from a position that the MPPAA "is a statute that allows for, and may in certain circumstances require, the disregard of such formalities." Further, the formal structure of each fund entity is a creature of state law that may not be respected at the federal level if the facts of operation are in contrast to the formalities. In finding a partnership-in-fact between the funds under federal law, the District Court stated that the funds were not separate investors in the portfolio company brought together by happenstance or coincidence. Rather, prior to making the investment, the funds acted jointly in deciding to co-invest in the portfolio company. The funds also had an existing pattern of investing together. The funds made a conscious decision to split their ownership in the portfolio company so that neither fund owned the requisite 80%, which evidenced a unity of decision making between the funds. The District Court explained that the smooth coordination between the funds of the management and operation of the portfolio company was indicative of a partnership-in-fact, resulting in the funds being in common control with the portfolio company. The District Court also noted that all of the funds advised by Sun Capital Advisors, although formally independent entities with separate owners, tax returns, financial statements, reports to partners, and bank accounts, and largely non-overlapping investors and investments, ultimately made their investment decisions under the direction of the co-CEOs of the funds' advisor.

The "partnership-in-fact" between Fund III and Fund IV was engaged in a "trade or business." In determining whether the "partnership-in-fact" was engaged in a trade or business, the District Court acknowledged the need to look at the activities of the partnership-in-fact and not just the activities of its partners; however, the court seemed to effectively ignore this pronouncement and impute the activities of the funds onto the "partnership-in-fact." Sun Capital argued that if Fund III and Fund IV are engaged in trades or businesses actively involved in the management of Scott Brass, there would be no active management work left for the partnership-in-fact to do and, as a result, the partnership-in-fact could not be engaged in a trade or business. The District Court did not accept this argument and instead found that like its partners, the partnership-in-fact's purpose in the investment was to make a profit and that it too was involved in the active management of Scott Brass.

Footnotes

1  See our Client & Friends Memo from 2013 for further discussion of the First Circuit's 2013 decision and the "investment plus" analysis.

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.

Authors
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
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
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
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.

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.