United States: Two Adverse Decisions Against Church Plans Reached At Appellate Court Level

Summary

Since 2014, large church-controlled health systems that offer defined benefit pension plans have seen lawsuits filed as to whether such plans are eligible to qualify for the ERISA church-plan exemption, which governs those arrangements. When a retirement plan meets the ERISA church-plan exemption, it is exempt from the typical funding and vesting requirements of ERISA and the Internal Revenue Code as well as from the ERISA reporting and disclosure requirements. As the church-plan litigation moves to the appellate level, two adverse decisions are reached denying ERISA church-plan exemption to two health systems.

In Depth

Since 2013, there have been more than 10 lawsuits filed against various health care systems across the country that maintain and operate defined benefit pension church plans. These suits allege that the retirement plans are not eligible for church-plan status and, therefore, cannot be exempt from the funding and disclosure requirements of the Employee Retirement Income Security Act of 1974 (ERISA). As the litigation has progressed over the past two years, the district courts have been divided on the issue, with district courts in Colorado, Maryland and Michigan affirming church-plan status for certain health care system and district courts in California, Illinois and New Jersey denying church-plan status for other health care systems. The remaining district courts where complaints have been filed have either not yet reached a decision or have put their decisions on hold pending decisions in other cases.

In the past four months, two federal appellate courts have decided appeals on the church-plan argument. On December 29, 2015, the US Court of Appeals for the Third Circuit issued its opinion in Kaplan v. Saint Peter's Healthcare System, concluding that although a church agency can "maintain" an exempt church plan, it cannot "establish" such a plan. The Third Circuit concluded that under ERISA's plain text, only a church can establish a plan that qualifies for the ERISA church-plan exemption. The Third Circuit determined that because the St. Peter's Healthcare System retirement plan was not established by a church (it was instead established by the health care system), it was ineligible for the ERISA church-plan exemption. Similarly, on March 17, 2016, the US Court of Appeals for the Seventh Circuit reached its decision in Stapleton v. Advocate Healthcare Network, concluding that a retirement plan established by a church-affiliated organization, such as a hospital, was not exempt from ERISA.

Dissecting the "Plain Meaning" of the Church-Plan Exemption

The key turning point issue in each of these two appellate cases is the precise language used in the originally enacted ERISA provision in 1974 and then the extension of that church-plan provision in 1982 under the Multiemployer Pension Plan Amendments Act of 1980. The original church-plan exemption language enacted in 1974 read as follows:

ERISA Section 3(33)

  1. The term "church plan" means a plan established and maintained (to the extent required in clause (ii) of subparagraph (B)) for its employees (or their beneficiaries) by a church or by a convention or association of churches which is exempt from tax under section 501 of title 26.
  2. The term "church plan" does not include a plan—

    1. which is established and maintained primarily for the benefit of employees (or their beneficiaries) of such church or convention or association of churches who are employed in connection with one or more unrelated trades or businesses (within the meaning of section 513 of title 26), or
    2. if less than substantially all of the individuals included in the plan are individuals described in subparagraph (A) or in clause (ii) of subparagraph (C) (or their beneficiaries).

In 1980, subparagraph (C) was added to ERISA Section 3(33), which relevant portions for the litigation read as follows:

  1. For purposes of this paragraph—

    1. A plan established and maintained for its employees (or their beneficiaries) by a church or by a convention or association of churches includes a plan maintained by an organization, whether a civil law corporation or otherwise, the principal purpose or function of which is the administration or funding of a plan or program for the provision of retirement benefits or welfare benefits, or both, for the employees of a church or a convention or association of churches, if such organization is controlled by or associated with a church or a convention or association of churches.

Both the Third and Seventh Circuits focused on the fact that the precursory language of new ERISA Section 3(33)(C)(i) iterated the language "a plan established and maintained for its employees...by a church..." before further stating which types of plans would be "included" within that definition. Both courts found it significant from a plain-meaning interpretation that the phrase "includes a plan maintained by an organization...for the employees of a church or a convention..." did not articulate that the "inclusion" also captured a plan "established" by such organization for the employees of the church. In other words, both courts held that the precursory language always requires that the plan be established by a church, but the inclusion merely clarified that if such a church-established plan was then later maintained by another organization for the church, it would equally meet the church-plan exception. Both courts determined that although the underlying health care system was affiliated with a church, the health care system itself had "established" the retirement plan, not the underlying church. Therefore, the retirement plans failed to meet the requisite church-plan definition.

Both the Third and Seventh Circuits noted that if Congress chose to include particular language in one section of ERISA but omitted it in another section of the same statue, it should generally be presumed that such decision was intentional and purposeful. Further, the Third Circuit in Kaplan stated that because ERISA is a "remedial" statute, it should be liberally construed in favor of protecting the participants in employee benefit plans. As such, excluding plans established by church agencies could take a large number of employees outside the scope of the ERISA protections.

Settlement Developments

These adverse decisions for church-plan status have caused several health care systems in pending cases to consider resolving their cases before further appellate decisions are issued. For example, in Overall v. Ascension Health, a case in which the Eastern District of Michigan previously ruled that Ascension Health's retirement plan did in fact qualify as a church plan, the parties ultimately decided in May 2015 to settle the issues while the case was on appeal. After fully briefing an appeal pending in the US Court of Appeals for the Sixth Circuit, Ascension agreed to provide for certain retirement plan provisions that would enhance the retirement security of the members in the settlement class. Specifically, barring a significant change in the law surrounding church plans, the Ascension pension plan would remain a non-ERISA church plan. However, because church plans are generally financially responsible only for pension obligations to the extent those plans are funded, Ascension agreed to guarantee participants would receive the level of benefits stated in the retirement plan through June 30, 2022. Notwithstanding this agreement, Ascension was only required to make an $8 million contribution to the retirement plan and pay the plaintiff's attorneys' fees and expenses of roughly $2 million. Further, Ascension agreed to provide certain "ERISA-type" protections for employees, including production of summary plan descriptions, issuance of pension benefit statements and adherence to claims review procedures similar to those under ERISA.

Equally, in December 2015, two additional health care systems decided to settle their church-plan disputes rather than wait for an appellate court decision on the plan's status. Specifically, Trinity Health, which was successful in defending its church-plan status in in Lann v. Trinity Health Corp. (pending in the District of Maryland), entered into an undisclosed joint settlement with participants; while Catholic Health East, which was unsuccessful in defending its church plan status in Chavies v. Catholic Health East (pending in the Eastern District of Pennsylvania), entered into an undisclosed joint settlement with participants.

Because the settlement terms in cases like these are typically kept confidential, it is difficult to draw any conclusions as to the impetus for the settlements or if there will be longer-term impacts on church-plan litigation generally. However, plan sponsor decisions to settle litigation in lieu of long and protracted litigation does appear to provide plan sponsors some breathing room to increase their funding status and comply with some of the more innocuous ERISA disclosure requirements without having to manage the litigation process at the same time.

Next Foreseeable Wrinkle in the Church-Plan Argument

In Kaplan v. Saint Peter's Healthcare System, the Third Circuit opined on an issue that was not directly before the court. Specifically, the Third Circuit stated that ERISA Section 3(33)(C)(i) expressly states that if a plan is to be maintained by an organization that is not a church, it must be an organization "the principal purpose or function of which is the administration or funding of a plan or program for the provision of retirement benefits or welfare benefits, or both for the employees of a church or a convention or association of churches..." The court noted that Saint Peter's itself did not meet the "principal purpose or function" test because it primarily provided health care, not administration or funding of the retirement plan. Consequently, the court stated that it had "substantial reservations over whether St. Peter's can even maintain an exempt plan." Although St. Peter's argued that it had a retirement plan committee and that committee's principal purpose was to maintain and administer the retirement plan, the court noted that ERISA does not provide that the organization may have a committee who administers the plan; instead, ERISA requires that the organization itself act as the administrator of the plan and act in that capacity as its principal purpose.

While this issue has not received considerable attention or vetting by the courts up to this point, it may become a significant issue applying the Third and Seventh Circuits' "plain meaning" test to church-plan status. The question that may arise is: If a health care system can in fact meet the ERISA church-plan exemption, will it be best to have a separate nonprofit entity within the system, whose sole role is to maintain and administer the respective church plans? That question may well impact the final determinations as to church-plan status for retirement plans of health care systems.

Two Adverse Decisions Against Church Plans Reached At Appellate Court Level

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.