Some deferred compensation plans are covered by ERISA, but many are not. It boils down to the type of plan – certain retirement plans fall under ERISA’s protections, while others (especially non-qualified executive arrangements and government/church plans) are exempt from most ERISA rules.
Roughly 93% of large public companies offer non-qualified deferred compensation plans, yet most of these plans operate outside ERISA’s protective umbrella. Billions in executive retirement promises lack the same federal safeguards as a 401(k).
- 🛡️ Covered or Not? – Learn which deferred comp plans fall under ERISA’s shield and which leave you unprotected.
- 📚 Key Terms Decoded – Understand ERISA, non-qualified plans, Top Hat plans, 457(b) plans, Rabbi Trusts, and more in simple terms.
- ⚠️ Pitfalls to Avoid – Discover common mistakes (like misclassifying a plan) that can trigger legal trouble or loss of ERISA exemptions.
- 🔍 Real Examples & Cases – Dive into real-world scenarios: executive “Top Hat” plans, government 457(b) plans, a Rabbi Trust, and even a $3M legal battle – illustrating ERISA vs. non-ERISA outcomes.
- ✅ Charts & Takeaways – Get handy comparison tables of ERISA-covered vs. exempt plans, a quick pros/cons rundown for each scenario, and an FAQ section answering your burning questions.
Quick Answer & Overview of ERISA Coverage 📊
Deferred compensation plans can be covered by ERISA – if they’re the type of retirement plan ERISA was designed to regulate – but many deferred comp arrangements are specifically exempt or excluded from ERISA coverage.
ERISA covers most broad-based retirement plans set up by private employers for their employees, while executive and specialty deferred comp plans often dodge ERISA (either by design or by law).
Why the split? ERISA (the Employee Retirement Income Security Act of 1974) is a federal law that sets strict standards for private-sector employee benefit plans. It mostly targets two categories: pension plans (which provide retirement income or defer pay to termination/retirement) and welfare plans (like health insurance).
Deferred compensation plans that look like retirement programs will typically count as “pension benefit plans” under ERISA, unless they fall into an exemption. ERISA coverage brings a host of rules – minimum participation and vesting standards, funding requirements, fiduciary duties, reporting/disclosure mandates, and a federal insurance backstop for some pensions. But not all deferred comp plans trigger these rules.
Here’s the high-level breakdown:
- ✅ Covered by ERISA: Qualified retirement plans (e.g. 401(k) plans, traditional pensions, 403(b) plans for private employers) are fully under ERISA. These are the mainstream plans that cover broad groups of employees and meet IRS qualification rules. If a deferred comp arrangement is offered to many employees and defers income to termination or retirement, it’s usually considered an ERISA pension plan. For example, a standard 401(k) plan or a company pension plan is squarely within ERISA’s scope and must follow all ERISA guidelines.
- ❌ Not Covered by ERISA: Governmental and church plans are explicitly exempt from ERISA by federal law. A 457(b) plan for state or city employees, for instance, is a deferred compensation plan not subject to ERISA (since it’s a government plan). Similarly, a pension or 403(b) plan run by a church or synagogue for its staff can elect to stay exempt from ERISA. These plans follow other laws (like state law or the Internal Revenue Code) but not ERISA.
- ❌ Not Covered (or Limited Coverage): Non-qualified deferred compensation (NQDC) plans for executives often avoid most ERISA requirements. These are plans that selectively cover key people (executives or other high-paid employees) and are unfunded promises rather than trust-backed funds. Under ERISA, there’s a special exclusion for a “Top Hat” plan – which is a plan for a select group of management or highly compensated employees, that is unfunded. A properly structured Top Hat deferred comp plan is considered an ERISA plan in name, but it is exempt from ERISA’s toughest rules (like funding, vesting, fiduciary oversight, and nondiscrimination). In practice, that means most executive NQDC plans do not have to meet ERISA’s minimum standards – no need to include rank-and-file workers, no trust funding requirement, no minimum vesting rules, etc. Important: Even though Top Hat plans are technically within ERISA’s definition of a pension plan, they get a free pass from most substantive ERISA provisions. We’ll explain this nuance more later.
- ⚠️ Gray Areas: Some compensation arrangements might look like deferred comp but aren’t meant to provide retirement income – these might fall outside ERISA’s definition of a pension plan altogether. For example, a short-term bonus deferral or a stock grant plan intended as incentive pay (not retirement savings) may not be an ERISA-covered plan at all. ERISA only kicks in if a plan’s purpose is providing retirement income or deferring pay to the end of employment. So, an annual bonus plan that pays out after two years likely avoids ERISA because it’s a short-term incentive, not a retirement plan. We’ll see an example where a court said a stock rights plan was not an ERISA pension because it wasn’t designed for retirement.
ERISA covers broad, tax-qualified retirement plans in the private sector, ensuring those plans follow uniform protections. However, executive deferred comp arrangements (Top Hat plans), along with plans for government or church employees, are carved out – they operate either outside ERISA or under a lighter touch.
This federal design lets top executives and special groups have extra retirement deals without the red tape of ERISA, and it lets governments/churches manage their own plans. But it also means participants in those plans don’t get ERISA’s full safety net.
[Keep in mind:] If a deferred compensation plan is covered by ERISA, federal law preempts (overrides) any state laws regarding that plan. If a plan is not covered by ERISA, then state laws and general contract principles will govern disputes or rights under that plan. We’ll delve into why that matters – for example, if your plan isn’t under ERISA, you might have to rely on state courts and contract law to claim your benefits (and state laws vary).
Key Terms & Definitions 🤓
To navigate deferred comp plans and ERISA, you’ll want to understand a few core concepts and entities. Here’s a quick primer:
- Deferred Compensation Plan: At its simplest, this is an arrangement where an employee elects to delay receiving part of their compensation until a future date (often retirement or leaving the company). The amount deferred (plus any investment growth on it) will be paid later, per the plan’s terms. There are two main flavors:
- Qualified Deferred Compensation Plan: This means a plan that meets strict IRS and ERISA rules – like a 401(k) or traditional pension. Qualified plans get special tax benefits (employer contributions are tax-deductible; employees aren’t taxed until distribution) and must comply with ERISA (e.g. cover a broad group, not just execs, and follow funding/vesting rules). These are subject to contribution limits and nondiscrimination tests.
- Non-Qualified Deferred Compensation (NQDC) Plan: This is a more flexible, often selective plan that does not meet the ERISA/IRS qualification criteria. It’s typically used to supplement executives’ retirement savings beyond the qualified plan limits. NQDC plans don’t have the contribution limits of qualified plans, and they can discriminate (i.e. only offered to certain people). However, because they’re not qualified, they don’t enjoy ERISA’s full protection – and they have different tax rules (see IRC 409A below). Most executive “deferred comp” plans you hear about fall in this category.
- ERISA: The Employee Retirement Income Security Act – a federal law that governs private employer-sponsored benefit plans in the U.S. For our purposes, ERISA sets the ground rules for pension (retirement) plans: it requires things like minimum vesting periods, fiduciary oversight of plan investments, disclosure of plan information to participants, strict funding for pensions, and fairness in coverage. ERISA also gives participants the right to sue in federal court for their benefits and breaches of fiduciary duty, and it established the PBGC (Pension Benefit Guaranty Corporation) which insures certain pension benefits if a company’s defined benefit plan fails. If a plan is “covered by ERISA,” it must follow these rules and the employer faces penalties for non-compliance. If a plan is exempt or not covered, none of those federal standards apply.
- “Employee Pension Benefit Plan”: This is the ERISA term for any plan, fund, or program that either provides retirement income to employees or results in deferral of income past employment. If a deferred comp arrangement fits this definition (and isn’t otherwise exempt), ERISA views it as a pension plan. The definition is broad – even if a plan’s primary purpose isn’t retirement, if by its terms it lets employees stash income away until they leave the job or retire, it can fall under ERISA’s umbrella. This definition was at the heart of a recent case where a court said: if it walks like a duck (defers income to post-employment), it’s a duck (an ERISA pension plan) – even if the company insists it’s just a bonus plan. We’ll cover that case later.
- Top Hat Plan: This is a crucial concept. A Top Hat plan is a special subset of deferred comp plan that is unfunded and limited to a “select group” of management or highly compensated employees. The term “Top Hat” isn’t actually in the ERISA statute, but it’s the common lingo. If a deferred comp plan meets the Top Hat criteria, ERISA exempts it from most substantive requirements:
- Unfunded means the plan’s benefits are not secured in a trust separate from the employer’s general assets. Instead, it’s just a promise – the funds remain part of the company’s assets (perhaps informally set aside, but still reachable by creditors). This is done on purpose: funding a non-qualified plan would trigger both immediate taxation for participants and full ERISA compliance. So Top Hat plans must remain unfunded promises to keep tax deferral and the ERISA exemptions.
- Select Group of Management or Highly Compensated Employees means the plan can’t include rank-and-file workers. It should cover only a small percentage of employees who are in high-level positions or earning top pay. (There’s no hard number in the law, but courts have signaled that if more than, say, ~15% of employees are in the plan or if it includes people of modest pay, it might not qualify as “select”. Most Top Hat plans cover far fewer – often just a handful of execs or a few percent of the workforce).
- Primarily for Deferred Compensation means the plan’s main purpose must be providing deferred comp to that select group (as opposed to something like an incentive stock option plan which might be more about short-term performance).
- Church Plan & Governmental Plan: These are two categories of plans explicitly excluded from ERISA coverage by the statute:
- A Church Plan is a retirement or deferred comp plan established by a church or association of churches (or their controlled organizations, like church-run hospitals or schools) for their employees. By default, church plans do not have to comply with ERISA. (Church plans can elect to be covered by ERISA, but many choose not to, as they often have their own governance structures). So, for instance, a diocesan pension fund for clergy is outside ERISA – it’s governed by internal church rules and sometimes state law.
- A Governmental Plan refers to plans for government employees – federal, state, or local government. This includes the federal Thrift Savings Plan, state teacher retirement systems, county or city 457 plans, etc. These plans are exempt from ERISA. They are typically governed by specific federal or state laws instead. For example, a 457(b) plan for city employees is authorized by the tax code and often by state statute, and it’s not subject to ERISA’s requirements. (The IRS imposes rules on 457 plans – like contribution limits and distribution restrictions – but the labor law aspects of ERISA don’t apply).
- IRC 409A: This is a section of the Internal Revenue Code that applies to non-qualified deferred compensation. It’s not part of ERISA, but it’s vital for anyone dealing with deferred comp. 409A sets strict timing rules on elections and distributions for NQDC plans – if you break them, employees face hefty tax penalties (immediate income inclusion plus 20% penalty). For example, electing to defer compensation must be done in advance, and payouts can typically only happen on fixed dates, death, disability, separation, etc., not whimsically. Why mention this? Because even if an executive deferred comp plan isn’t covered by ERISA, it is covered by 409A. Employers must design NQDC plans to satisfy 409A to preserve the tax deferral. So compliance in deferred comp world means both navigating ERISA (or an ERISA exemption) and obeying 409A’s tax rules.
- Rabbi Trust: This is a commonly used mechanism in NQDC plans. A Rabbi Trust is an irrevocable trust established by the employer to hold assets set aside for paying the deferred compensation in the future. It gives employees some peace of mind that money is earmarked for them. However – and this is key – a properly structured rabbi trust is written so that the assets in the trust are still available to the employer’s general creditors if the company goes bankrupt. That feature is what keeps the plan “unfunded” in ERISA/409A terms. In other words, a rabbi trust provides a measure of security (the employer can’t just decide not to pay since assets are in trust with a trustee), but it does not protect against insolvency risk. The name comes from the first IRS ruling on such a trust (for a rabbi’s contract). For ERISA, using a rabbi trust does not jeopardize the Top Hat status – the plan is still deemed unfunded because if the employer tanks, the trust money can be taken by creditors. Most Top Hat plans for executives use rabbi trusts to informally fund the promised benefits.
- Secular Trust: In contrast to a rabbi trust, a secular trust actually does secure the deferred comp solely for the employees and is shielded from company creditors. Sounds great? The catch: if you use a secular trust, the IRS treats the money as immediately taxable to the employee (no deferral), and ERISA would likely view the plan as funded – meaning you lose the Top Hat exemption and trigger ERISA requirements. Because of those downsides, secular trusts are rare in non-qualified plans. Essentially, secular trust = strong security but no tax deferral; rabbi trust = tax deferral but no bankruptcy security.
- Department of Labor (DOL) & Employee Benefits Security Administration (EBSA): This is the federal agency (and division) charged with enforcing ERISA’s provisions for private-sector plans. If your plan is covered by ERISA, DOL/EBSA can investigate compliance (e.g. did you file your Form 5500? Are the plan fiduciaries acting prudently?). The DOL also processes the one-time Top Hat plan filings that employers send in. If a plan should be under ERISA but isn’t complying, the DOL can take action or impose penalties. For Top Hat plans, DOL mostly just expects that notification letter and that the plan truly only covers a select group.
- Internal Revenue Service (IRS): The IRS cares about all retirement plans from the tax angle. It sets qualification rules for 401(k)s and pensions (and grants them tax-favored status if rules are met). It also enforces 409A for non-qualified plans and Section 457 rules for governmental plans. The IRS doesn’t police ERISA directly, but there’s overlap: a plan might be disqualified for tax purposes if it doesn’t meet certain standards. For example, if a 401(k) plan discriminates in favor of highly paid employees, it could lose its tax-qualified status (which indirectly means it’s violating ERISA too). With NQDC, the IRS’s main hammer is 409A – ensure deferrals and payouts follow the allowed pattern or suffer tax consequences.
- Securities and Exchange Commission (SEC): The SEC comes into play for public companies offering deferred comp. While the SEC doesn’t regulate ERISA, it does oversee executive compensation disclosure and any arrangements involving company stock. For instance, if a non-qualified plan offers executives company stock or stock units as deferred comp, it may need to comply with securities laws or registration requirements (though many such plans rely on exemptions for private offerings to a limited group of execs). Also, public companies must disclose major executive compensation plans (including deferred comp balances) in proxy statements, so shareholders are aware. In some cases, if a deferred comp plan significantly affects financial statements, the SEC ensures proper accounting (like ensuring liabilities for NQDC are reported). So, SEC is part of the picture primarily for transparency and securities compliance, not for protecting the employee’s benefit per se.
- Employer (Plan Sponsor): Finally, the role of the employer is central. The employer sponsors the plan and chooses its design:
- If they sponsor a qualified, ERISA-covered plan, they accept the regulatory burdens in exchange for giving broad benefits and tax advantages to all employees.
- If they set up a non-qualified exec plan, they often design it to fit the Top Hat criteria (to avoid ERISA burdens) and to comply with tax law. The employer must then administer the plan accordingly (tracking deferrals, abiding by payout schedules, etc.). The employer also bears the creditor risk – if the business struggles, those deferred comp liabilities might compete with other debts.
- In all cases, the employer (or a committee it appoints) typically acts as the “plan administrator” – meaning it makes decisions on benefit claims, interprets plan terms, and, if ERISA applies, owes fiduciary duties to the participants. For Top Hat plans, there’s no statutory fiduciary duty, but wise employers still handle them carefully to maintain trust with their executives (and to avoid lawsuits for breach of contract or ERISA benefit claims).
With these concepts defined, we can now explore common pitfalls and real examples, which will make a lot more sense now that you know the lingo.
Mistakes to Avoid 🚫 (Common Pitfalls in Deferred Comp Compliance)
Designing or handling deferred compensation plans can be a legal minefield. Here are some common mistakes companies and individuals should avoid when it comes to ERISA coverage:
1. Assuming All Deferred Comp Plans Have ERISA Protection: Don’t make the mistake of thinking your deferred comp account is as safe as your 401(k). A huge pitfall for employees is assuming that their deferred compensation is secured by ERISA. In reality, most non-qualified plans lack ERISA’s protective features. For example, if you’re deferring part of your bonus in a company executive plan, those dollars are not held in a trust for your benefit (unless it’s a rabbi trust, which still isn’t 100% safe).
If the company hits hard times, your deferred comp is just an unsecured promise. Actionable Tip: Always clarify what kind of plan you’re in. If it’s not a qualified ERISA plan, recognize that you’re essentially a creditor of your employer for that amount. Plan accordingly – consider the company’s financial health and don’t bank your entire retirement on an unfunded promise.
2. Misclassifying a Plan (or the Workforce): Employers often err by covering the wrong people in a deferred comp plan. For a Top Hat plan, including too many employees or the wrong ranks can destroy the ERISA exemption. For instance, if a company lets mid-level employees or a large percentage of staff into what is supposed to be a select executive plan, a court could later rule the plan was not truly a Top Hat plan. The consequence? The plan would retroactively be seen as an ERISA-covered pension that failed to comply (no trust, no vesting, etc.) – a legal nightmare.
In one case, a plan included about 15% of employees; the court warned that was “at or near the upper limit” of a select group. Including even more (or including employees making relatively low salaries) could invalidate the Top Hat status. Actionable Tip: Keep NQDC plans exclusive. Ensure participation is limited to a small, clearly defined high-compensated group. And document why they qualify (job titles, salary thresholds, etc.). When in doubt, use objective criteria like “vice presidents and above” or salary > a certain high amount, to avoid any rank-and-file creeping in.
3. Failing to File the Top Hat Statement: When a company establishes a Top Hat plan, ERISA’s regulations provide an alternative reporting method: just file a one-time statement with the DOL within 120 days of plan inception. It’s a simple letter (basically stating “We have a Top Hat plan, here’s the employer name, number of participants, plan administrator info”). This filing exempts the employer from annual reports and other disclosures.
One big mistake is forgetting to send this notice. The penalty for not filing can be steep (the DOL can impose fines for missing required filings, even if the plan is exempt from the full 5500). It also just looks bad if later audited. Actionable Tip: Always submit the Top Hat plan statement on time. It’s quick and preserves the plan’s ERISA reporting exemption. Keep a file copy and confirmation for your records. While the DOL has sometimes been forgiving if a company later complies, it’s not worth the risk – especially since failing to file might raise questions about whether you were even aware of the ERISA implications.
4. Violating 409A or Other Tax Rules: It’s easy to focus on ERISA and forget the tax side (since our main question is about ERISA coverage). But messing up the tax compliance of a deferred comp plan is equally dangerous. A common mistake is allowing an executive to change their payout timing or election last-minute, or providing an impermissible perk (like an unallowed distribution trigger) – thus violating IRC 409A. The result is immediate taxation of all deferred amounts plus a 20% penalt
y and interest – an expensive mistake for the employee (and potentially the employer might owe withholding penalties). Actionable Tip: Coordinate plan operations with both ERISA and IRS rules. If you have a non-qualified plan, make sure any deferral elections are made in the prior tax year (or when first eligible, per 409A rules) and that payouts only happen on allowed events (separation, a set date, etc.). No sneaky early payouts or extensions unless 409A permits. Always involve legal/tax counsel when designing these plans to avoid running afoul of 409A, Section 457 (for nonprofits/government) or other applicable tax provisions.
5. Treating a Deferred Comp Arrangement Too Casually (or Off-the-Books): Some small or mid-sized businesses make the mistake of informal deferred comp promises without realizing they might have created an ERISA plan. For example, an employer might say to a key employee, “Work for me for 5 years, and I’ll pay you a lump sum of deferred salary when you retire.” That’s essentially a pension promise. If the deal isn’t documented properly or operated within an exemption, it could inadvertently be an ERISA plan that’s not in compliance. Another scenario: a company sets up a “bonus” plan that actually pays after employment ends – that could trigger ERISA if it looks like a retirement plan.
Actionable Tip: Don’t “wing it” with deferred comp. If you want to reward an employee later, either structure it as a proper plan (and take the necessary steps to comply or fit an exemption) or ensure it’s a short-term payout (within 2½ months after the end of the year, which generally avoids ERISA by being a short-term deferral). A good rule of thumb: any promise of money paid in the future when the employment is over should set off ERISA alarm bells. Consult an ERISA attorney to either draft a compliant plan or confirm that what you’re doing is outside ERISA’s scope.
6. Ignoring State Law Implications: If your deferred comp plan is not covered by ERISA (for example, it’s a pure contractual arrangement or a government plan), don’t forget that state laws will govern disputes. One mistake is assuming you’re in a law-free zone if ERISA doesn’t apply. In reality, you might face state wage law issues or contract law claims. Some states have strict rules about paying earned wages. While deferred compensation for executives often isn’t considered “wages” until due, a misstep could lead to arguments that an executive’s deferred amounts should have been paid at termination under state law. Also, without ERISA preemption, participants can bring state common law claims like breach of contract or promissory estoppel.
Actionable Tip: For non-ERISA plans, ensure your plan documents are crystal clear under state contract law (specifying when the benefit is earned and due). Be mindful of states like California or New York – their courts will enforce the plan as a contract and may apply pro-employee interpretations if terms are ambiguous. If you operate in multiple states, remember state laws differ on things like non-compete enforceability tied to benefits, creditor protection, etc. ERISA preemption would wipe those differences away; without it, you must navigate them. In short, when ERISA doesn’t apply, loop in a good contracts lawyer and consider choice-of-law provisions in your plan.
Detailed Examples (Top Hat Plans, Rabbi Trusts, 457(b), etc.) 📑
Nothing beats real-world examples to illustrate how ERISA coverage works for deferred comp. Let’s look at a few common scenarios and notable examples:
Example 1: The Executive “Top Hat” Deferred Comp Plan – Suppose a mid-size tech company offers its CEO and top 5 executives a special deferred bonus plan. Each year, execs can elect to defer up to 50% of their bonus, which the company promises to pay at retirement (with interest). The plan is unfunded – amounts are recorded on the company’s books as a liability, but not set aside in a separate trust (aside from a rabbi trust perhaps). ERISA status? This is a textbook Top Hat plan. It’s an unfunded plan for a select group of management. The company files the one-time Top Hat notice with the DOL. As a result, the plan is technically an ERISA pension plan, but it’s exempt from ERISA’s participation, vesting, funding, and fiduciary rules.
The execs cannot rely on ERISA’s fiduciary standards or funding guarantees – if the company later refuses payment or goes bankrupt, the execs have limited recourse. They can sue under ERISA Section 502(a)(1)(B) for their benefits (since ERISA still covers enforcement), but they’ll be standing in line as unsecured creditors if the company is insolvent. This example shows how companies use the Top Hat concept to reward execs without the complexity of a qualified plan. It also highlights the risk: those deferred bonuses are only as good as the company’s promise. (Many such plans do use a Rabbi Trust to somewhat mitigate the risk – so let’s cover that next.)
Example 2: Rabbi Trust Funding – Securing the Promise (Sort Of) – Building on the previous scenario, say the tech company also sets up a Rabbi Trust with an independent trustee. Each year, when executives defer their bonuses, the company contributes an equivalent amount of stock or cash into the trust, invested to mirror the deferred accounts. The trust is irrevocable (company can’t withdraw assets arbitrarily). How it works: If the executives retire and the company is solvent, the trust funds are used to pay their deferred comp as promised. If the company faces a hostile takeover or management change, the trust might contain “trigger” provisions to become funded to a higher level (to protect execs from new owners reneging).
ERISA status? Even with the trust, this plan is still unfunded in ERISA’s eyes because of a key feature: the trust document states that if the company goes bankrupt, trust assets are available to creditors. Thus, it meets the Top Hat “unfunded” requirement. There’s no ERISA violation. The benefit of the rabbi trust: it helps ensure that if management changes or if the company just tries to back out of paying while still solvent, the executives have a dedicated pot of assets to claim against. The limitation: if it’s a bankruptcy or insolvency situation, the trust doesn’t save them – it expressly provides that creditors get dibs alongside the execs. This example shows how a rabbi trust offers some security but not full ERISA-level security. It’s a popular tool because it balances risk and reward (maintaining tax deferral and ERISA exemption while giving execs more confidence). Most Fortune 500 Top Hat plans feature rabbi trusts.
Example 3: Government 457(b) Deferred Comp Plan – Imagine you work for a city government which offers a 457(b) plan. These are deferred comp plans for public sector employees, somewhat analogous to 401(k)s but with key differences. You contribute a portion of your salary pre-tax into the plan, and your account grows tax-deferred until retirement. Under IRS rules, 457(b) contributions are capped (similar to 401(k) limits, around ~$22,500/year in recent years, with catch-ups). ERISA status? Not covered by ERISA. Governmental plans are exempt. However, 457(b) plans have their own safeguards: since 1996, government entities are required to hold 457(b) assets in trust (or annuity or custodial account) for participants. That means your deferred comp is actually funded and secured (the opposite of a private Top Hat plan!). If the city were in financial trouble, those funds are in a trust separate from general coffers – good news for you. But that’s due to the tax code and state law mandates, not ERISA.
There’s no PBGC insurance or ERISA fiduciary requirements – instead, state fiduciary laws or trust laws would govern the plan’s management. If something went wrong (say, mismanagement of the account), your recourse would be under state law or whatever dispute process the plan provides, not an ERISA claim. This example highlights the state/federal split: public sector employees get retirement plans outside ERISA, often with strong protections provided by other means. (A quick note: 457(f) plans – another type of nonqualified plan for certain government or nonprofit execs – are also outside ERISA and come with their own quirks, like requiring a “substantial risk of forfeiture” to achieve tax deferral. Those are usually for top officials, with payouts contingent on staying for X years, etc. They too are basically handshake deals governed by contract law and IRS rules, not ERISA.)
Example 4: Nonprofit Executive Deferred Comp (Non-Governmental 457(b)/457(f)) – Consider a large hospital system that’s a tax-exempt nonprofit. They can’t have equity-based plans (no stock), but they want to reward top doctors and executives with extra retirement savings beyond the 403(b) plan. Tax-exempts can use 457(b) plans for a select management group (they’re essentially the nonprofit equivalent of a Top Hat plan, with a contribution limit). The hospital’s 457(b) might allow, say, the CEO and VPs to defer salary up to the IRS limit, with maybe a small employer match. Because it’s not a governmental plan, this 457(b) is technically a private plan that could fall under ERISA’s pension definition. But to avoid ERISA, it’s offered only to a select group of management, making it a Top Hat plan by design. (ERISA actually does count it as a pension plan, but because it’s unfunded and select, it’s exempt from most rules – similar to any corporate Top Hat plan.)
Many nonprofits also have 457(f) plans, where they promise a certain amount to an executive if they stay a number of years (these amounts vest all at once at a future date, then are paid and taxed because 457(f) doesn’t allow indefinite deferral once vested). ERISA status? These are also typically treated as Top Hat plans (select execs only, unfunded), thus avoiding ERISA’s main provisions. The key takeaway: Non-government, tax-exempt employers have deferred comp plans that look like corporate Top Hat plans – and they intentionally limit participation to high-level employees to stay out of ERISA compliance. Participants should note that their money is not as secure as in the qualified pension plan; it’s at the organization’s mercy. If the nonprofit hits financial difficulty, deferred comp balances (457(f) accruals, etc.) are vulnerable.
Example 5: Stock Compensation Plan – ERISA or Not? – A Fortune 500 company grants key employees restricted stock units (RSUs) that vest over 3 years. Upon vesting, the employee can choose to defer delivery of the shares for another 5 years. This has an element of deferred compensation (they’re deferring receipt of shares, which is like deferring income). But is it an ERISA pension plan? Probably No – not an ERISA plan, if the program is designed primarily as an incentive, not retirement income. In fact, one real case (Rich v. Shrader, 9th Cir. 2016) involved a stock rights plan at Booz Allen Hamilton where employees could take restricted stock units as part of pay. The plan wasn’t aimed at retirement – the stock vested on a career event, not necessarily at retirement age.
The court held it was not an ERISA-covered plan because its primary purpose wasn’t to provide retirement income or systematically defer pay to termination; it was more of a long-term incentive/bonus arrangement. Thus, the executive who sued couldn’t invoke ERISA – he had to rely on state contract law (and unfortunately for him, his claim was time-barred). This example illustrates that not every deferred payout is an ERISA plan. Companies often argue a plan is just a bonus or incentive, not a pension, to avoid ERISA. The flip side: other courts (like the Fifth Circuit in the RBC case we’ll discuss) have taken a broader view and said if it allows deferral to termination, it counts as a pension plan. So, the line can be thin. But generally, pure compensation awards that vest or pay out well before retirement, or at employee choice, may escape ERISA.
These examples show a spectrum: fully ERISA-protected plans (like a funded 401(k) or gov’t trust), partially protected Top Hat setups (executive plans with rabbi trusts), and completely non-ERISA situations (church, government, or incentive plans). Now, let’s explicitly compare the features of covered vs. non-covered plans so you know what practical differences to expect.
Covered vs. Non-Covered Plans: Key Differences ⚖️
What changes when a plan is subject to ERISA versus when it’s not? Here’s a rundown of the key differences between an ERISA-covered retirement plan and a deferred comp plan that isn’t under ERISA:
- Participation and Nondiscrimination: An ERISA-covered plan (like a 401(k)) must follow rules that ensure a broad range of employees can participate – it can’t just favor owners or top brass. There are tests to make sure contributions or benefits for lower-paid employees are proportional to those for higher-paid. In contrast, a non-ERISA deferred comp plan (Top Hat or similar) can be highly selective. The employer is free to cover only certain people (and in fact must limit participation if it’s a Top Hat). There’s no fairness testing – it’s discriminatory by design, favoring key employees.
- Vesting and Benefit Security: ERISA plans have minimum vesting standards (for example, a qualified plan might require benefits to vest 100% after 3 years, or 20% per year from years 2-6, etc.). They also generally must have anti-forfeiture rules – once vested, benefits can’t be lost (except in rare cases like plan termination with insufficient funds, which is where PBGC might step in for pensions). Non-ERISA plans often include forfeiture provisions – e.g. if an executive quits early or violates a non-compete, they might forfeit their deferred comp. Top Hat plans commonly use vesting schedules or conditions like “you only get your payout if you stay until age 65” or “if you go to a competitor, you forfeit”. Those kind of clauses couldn’t be enforced in an ERISA qualified plan (ERISA would override them), but in a non-ERISA plan they are allowed. This gives employers a “golden handcuff” tool with NQDC plans, but obviously it’s a downside for participants who might lose unvested deferrals.
- Funding and Trust Requirements: ERISA-covered pension plans (except for some small insurance-funded arrangements) are generally funded – meaning plan assets are held in trust separate from the employer’s operating assets. For example, your 401(k) contributions go into a trust account under the plan’s name, not the company’s bank account. By law, an employer must remit employee deferrals quickly to the trust. Those assets are then off-limits to the employer’s creditors and can only be used to pay plan benefits. Additionally, defined benefit plans must meet strict funding targets each year. Non-ERISA deferred comp is unfunded – no segregated pot is legally required (even if a rabbi trust exists, it’s not truly secure). The money often just goes back into the company’s general treasury after they note your “IOU”. This means if the company folds, there is no dedicated fund – you line up with other unsecured creditors hoping to get pennies on the dollar. Also, no PBGC insurance for non-qualified plans: if a qualified pension plan fails, the PBGC may cover some benefits; if a Top Hat plan fails, PBGC does nothing (it only insures qualified defined-benefit pensions).
- Fiduciary Duties and Oversight: Under ERISA, those who manage plan assets or make decisions about the plan owe fiduciary duties to participants. That means they must act prudently, solely in the interest of participants, diversify investments, and avoid conflicts of interest. If they mismanage funds or act disloyally, participants can sue for breach of fiduciary duty. Also, ERISA plans require a formal claims and appeals process for benefits, giving participants the right to a full and fair review of denied claims. In a non-ERISA plan, fiduciary standards do not formally apply. The plan is basically a contract. The people running it have no ERISA-imposed obligations to act in the participant’s best interest. They could even be the company’s same finance folks who consider the company’s interest first. If a benefit is denied or cut, the participant’s recourse is a breach of contract claim (or if it’s a Top Hat plan, an ERISA Section 502(a)(1)(B) claim to enforce the plan’s terms, but not a fiduciary claim). There’s also no requirement for a written Summary Plan Description or an appeals procedure (though many companies voluntarily include claim procedures in the plan document). Bottom line: less formal accountability on management of a non-ERISA plan.
- Reporting and Disclosure: ERISA plans must provide participants with information – for example, an annual report (Form 5500 is filed with DOL, and certain info can be requested by participants), Summary Annual Report, and, importantly, a Summary Plan Description (SPD) detailing how the plan works. Many ERISA plans also have to disclose fees, investment options, etc. Top Hat/exempt plans have minimal to no public reporting. The only disclosure might be whatever the employer chooses to share in a plan agreement or summary to the participants. They do file that one-time Top Hat statement to DOL (which isn’t detailed, just a notification). This lack of disclosure means, as an executive in an NQDC plan, you might not have the wealth of information you’d get about your 401(k). It’s wise to ask for plan documents and understand provisions, because you won’t get an SPD mailed automatically.
- Preemption of State Law: We touched on this, but to emphasize: An ERISA-covered plan benefits from ERISA §514 preemption, meaning state laws that “relate to” the plan are mostly preempted (with some narrow exceptions). This uniform federal umbrella prevents a patchwork of state regulations. So participants can’t, for example, invoke a state consumer protection law or wage law to claim benefits under an ERISA plan – it all goes through federal ERISA remedies. Conversely, if a plan is not under ERISA, then state laws apply fully. That could be good or bad. Good in that, if you have a dispute, you might use state contract law (which could allow broader damages like interest, or other equitable remedies ERISA might not). Bad in that your rights might be less clear or robust (ERISA, for instance, allows attorney’s fees for a prevailing participant; your state contract claim might not). Also, without preemption, states could enforce, say, their insurance or securities regulations on how the plan is set up – but many Top Hat plans fly under the radar because they are offered to so few people (and often those people are involved in company leadership decisions).
- Regulatory Oversight: With an ERISA plan, agencies like the DOL and IRS keep an eye on things. DOL can audit for fiduciary breaches or reporting failures; IRS audits for contribution limits and nondiscrimination. In a non-ERISA plan, the DOL generally isn’t monitoring (unless someone complains or there’s a question of whether it should’ve been an ERISA plan). The IRS will still enforce 409A and payroll tax timing (note: in NQDC, FICA payroll taxes are due at vesting, even though income tax is deferred). But overall, less regulator attention is paid to a supplemental exec plan – it’s mostly a private arrangement.
To visualize these differences, the next section provides a quick pros and cons table of ERISA coverage vs. non-coverage.
Pros & Cons of ERISA Coverage ✅❌
When it comes to deferred compensation arrangements, being covered by ERISA has distinct advantages and drawbacks compared to being exempt from ERISA. Here’s a side-by-side look at the upsides and downsides of each approach:
| ERISA-Covered Plan (e.g. Qualified 401(k) or Pension) | Non-ERISA Plan (e.g. Top Hat NQDC or Government Plan) |
|---|---|
| Pros: Participants enjoy strong legal protections – fiduciary oversight, required funding (for pensions), and federal insurance (PBGC for pensions). Benefits are held in trust, generally safe from employer’s creditors. Uniform federal rules ensure transparency (disclosures, statements) and a clear claims process. | Pros: Maximum design flexibility – employers can tailor who participates and how much they defer with no IRS contribution caps or nondiscrimination tests. Can reward only key talent. Administration is simpler (no annual Form 5500, fewer compliance burdens). Companies can impose conditions (vesting, non-compete forfeitures) to encourage retention. |
| Cons: Complex compliance burden – must meet many rules (vesting schedules, coverage tests, funding requirements) and file annual reports. Contributions/benefits are capped by law (can’t exceed certain IRS limits, which may not meet some executives’ retirement needs). Plan must generally be offered broadly, limiting a company’s ability to target rewards. Fiduciary liability is high – plan sponsors and managers can be sued for investment or administrative missteps. | Cons: No guaranteed security – participants are unsecured creditors with no ERISA safety net. If the employer fails financially, deferred amounts can be lost entirely. No fiduciary duty means less accountability on how the plan is managed. Participants have to trust the employer’s promise and financial health. Also, because these plans primarily benefit executives, there’s public/shareholder perception risk (these arrangements lack the egalitarian aspect of ERISA plans). Finally, any dispute might lead to litigation under contract law, which can be costly and inconsistent (and typically, no attorneys’ fees awarded like under ERISA). |
In short, ERISA coverage = more security for employees, more regulatory burden for employers, whereas ERISA exemption = flexibility and simplicity for employers, but more risk for employees. Depending on your role (employer designing a plan or an employee participating), these pros and cons will frame how you approach a deferred comp program.
Sometimes employers offer a mix – a qualified plan up to the legal limits (ERISA-covered) and then a non-qualified Top Hat plan for excess – attempting to balance both worlds. Understanding these trade-offs is crucial when deciding to participate in or sponsor a deferred comp plan.
Next, let’s examine a few common scenarios of deferred comp plans in a quick-reference format. This will help solidify what happens under different circumstances.
3 Common Deferred Compensation Scenarios (With Comparison Tables) 📋
Below are three typical scenarios for deferred compensation arrangements, each with a two-column table summarizing their ERISA coverage, features, and examples:
Scenario 1: Qualified 401(k) or Pension Plan (ERISA-Covered)
This is the standard retirement plan most people are familiar with.
| Aspect | Details |
|---|---|
| ERISA Coverage | Yes. Fully covered by ERISA. Must follow all ERISA Title I rules (participation, vesting, funding, fiduciary standards, reporting, etc.). |
| Who’s Eligible | Broad eligibility – generally all employees meeting age and service requirements. Cannot limit to execs only; must pass nondiscrimination tests to include lower-paid employees. |
| Funding & Assets | Funded in trust. Employee deferrals and employer contributions are placed in a separate trust or insurance contract. Assets are protected from employer’s creditors. Defined benefit plans also have minimum funding requirements. |
| Regulatory | Subject to extensive IRS rules (e.g. contribution limits, required minimum distributions) and DOL oversight. Annual Form 5500 filing required. Participants receive Summary Plan Descriptions and regular benefit statements. |
| Example | A 401(k) plan offered to all employees of a small business, with employer match. Employees contribute pre-tax, money is held in a plan trust, and the plan must treat all eligible workers fairly (nondiscrimination). ERISA ensures the plan fiduciaries manage the funds prudently, and employees are entitled to their vested account balances on leaving. |
Scenario 2: Top Hat Executive Deferred Comp Plan (ERISA-Exempt for Select Executives)
A non-qualified plan for a select group of top employees at a private company.
| Aspect | Details |
|---|---|
| ERISA Coverage | Partially. Considered an ERISA “pension plan” but exempt from most requirements due to Top Hat status. ERISA’s funding, vesting, fiduciary duty provisions do not apply. Only minimal reporting (one-time DOL notice) and enforcement provisions apply. |
| Who’s Eligible | Select group only. Typically limited to senior management or highly-compensated employees (often well under 10% of workforce). No need to include lower-level employees. This selective nature is what allows ERISA exemption. |
| Funding & Assets | Unfunded. No segregated trust required (though a Rabbi Trust may be used). Deferred amounts are a promise on paper; assets remain part of employer’s general funds. Participants have no claim to specific assets and are unsecured creditors if the company defaults. |
| Regulatory | Must comply with IRS 409A rules for deferrals and payouts. DOL requires a one-time Top Hat statement filing. No annual 5500 or broad disclosures to participants mandated. Company often provides a plan document or agreement outlining terms, but there’s flexibility in design. |
| Example | A deferred bonus plan for the CEO and vice presidents of a corporation. Each year, they can defer some of their bonus until 5 years after retirement. The plan document says benefits vest only if the exec stays 5 years. The company files the Top Hat notice with DOL. When an exec leaves, they request their benefit; if denied or partially forfeited, they could sue under ERISA for the benefit (since it’s still an ERISA plan), but they can’t claim any fiduciary breach because none are required. The plan wasn’t funded, so if the company is bankrupt, the execs likely lose the deferred amounts. |
Scenario 3: Government or Church Deferred Comp Plan (Non-ERISA Plan)
Retirement or deferred comp plan for public sector or church employees.
| Aspect | Details |
|---|---|
| ERISA Coverage | No. Completely exempt from ERISA by law. Governed by applicable federal/state laws and plan documents, but not by ERISA’s Title I provisions. |
| Who’s Eligible | Depends on the plan design and law. Government plans (like a public 457(b)) can cover a broad range of employees or specific groups (often voluntary participation). Church plans can be tailored by the church authority; they might mimic 401(k) style or be specialized clergy pension programs. No ERISA nondiscrimination rules, but public policy or specific statutes may impose fairness. |
| Funding & Assets | Variable funding rules: Government plans are often funded (e.g., assets of a state deferred comp plan are held in trust as required by the IRC). Church plans may or may not fund assets – some operate on a pay-as-you-go basis, others have trust funds. Regardless, assets aren’t subject to ERISA trust requirements or PBGC insurance. For example, a state pension is backed by the state’s commitment (and sometimes a trust) but not by PBGC. |
| Regulatory | Other laws apply: Government plans follow state law or specific federal tax rules (e.g., 457(b) rules, state pension codes). Church plans follow internal governance and IRS rules for church plans. These plans don’t file Form 5500s. Participants rely on the plan’s governing body for information – for instance, a state retirement system will issue handbooks or statements per its statutes. Disputes are handled via state administrative processes or courts, not ERISA claims. |
| Example | A state university offers faculty a 457(b) deferred comp plan in addition to a basic pension. Faculty can defer extra salary, choose investment options, and receive payouts after retirement. The plan’s assets are held in a trust managed by a board created by state law. If a dispute arises (say miscalculation of a benefit), the faculty member appeals to the state retirement board or through a process defined by state statute. ERISA plays no role. Similarly, a national church denomination has a retirement plan for its ministers – it might be administered by a church benefits board and have its own vesting and distribution rules, all outside of ERISA’s purview. |
These scenarios cover the most common setups: an ERISA-qualified plan for the masses, an executive carve-out plan, and a non-ERISA plan in the public/faith sector. Most deferred comp situations you encounter will resemble one of these. Understanding which scenario you’re in tells you what protections you have (or lack) and what laws guide your plan.
Case Law Spotlight: Key Rulings on Deferred Comp & ERISA 🏛️
Over the years, courts have weighed in on what counts as an ERISA-covered plan and how exemptions play out. Here are a few notable case law rulings that shape this landscape:
- Tolbert v. RBC Capital Markets (5th Circuit, 2019): This case is a landmark for defining an ERISA pension plan. RBC had a deferred compensation plan for its financial advisors called the Wealth Accumulation Plan (WAP). Advisors could defer some income and also had bonuses paid into the plan, with payouts often on termination of employment. RBC argued the plan wasn’t meant as retirement income, so it shouldn’t be an ERISA plan. A Texas federal court initially agreed with RBC, citing that the primary purpose wasn’t retirement. On appeal, the Fifth Circuit reversed – crucially, the court said that even if the plan’s primary aim wasn’t retirement, the fact that it resulted in deferral of income to termination or beyond was enough to meet ERISA’s definition. The Fifth Circuit explicitly held that the statutory definition’s second prong (deferral of income past employment) doesn’t require a “primary purpose” test. Because the plan allowed deferral until after leaving the company, it was an ERISA pension plan. This decision effectively broadened ERISA coverage: even optional deferrals can trigger ERISA. The twist: RBC had foreseen this and had structured the plan as a Top Hat plan in case ERISA applied. The advisors who sued claimed it wasn’t a valid Top Hat (arguing maybe too many were included or forfeiture provisions were improper). The litigation then also revolved around whether forfeiting deferred amounts when advisors left violated ERISA’s vesting rules – which it would, unless the plan was a Top Hat (Top Hat plans are exempt from vesting rules, so they can have forfeitures). The Fifth Circuit’s stance underscores that in some jurisdictions, virtually any plan that lets you choose to defer comp to post-employment will be deemed an ERISA plan – meaning companies must either structure it as a Top Hat (if only for execs) or, if it’s broad-based, comply fully with ERISA.
- Rich v. Shrader (9th Circuit, 2016): We introduced this earlier – an example where a plan was not an ERISA plan. Booz Allen Hamilton had a stock-based incentive plan for certain employees. The plaintiff, Rich, argued it was an ERISA pension plan because it deferred compensation. But the court disagreed, finding the plan was not “designed or intended to provide retirement benefits.” It was more of a long-term incentive/bonus arrangement. Thus, ERISA didn’t apply at all. This meant Mr. Rich’s only claims were under state law (and unfortunately for him, his breach of contract claim was time-barred). The significance: courts (especially the Ninth Circuit covering western states including California) may look at the primary purpose of the plan – if it’s not primarily for retirement, they can rule ERISA doesn’t cover it. This creates a contrast with the Fifth Circuit’s approach in RBC’s case. Geographic differences in court rulings mean the outcome can depend on where a lawsuit is filed. In practice, companies in the Ninth Circuit might be a bit more comfortable offering deferral features in bonus plans without treating them as ERISA plans, whereas in the Fifth Circuit (Texas, Louisiana, Mississippi) that could be riskier.
- Demery v. Extebank (2nd Circuit, 2000): This is a Top Hat criteria case. Extebank had a deferred comp plan for select employees that ended up covering about 15% of the workforce. Participants who were denied benefits argued it wasn’t a valid Top Hat because it covered too many people and some not highly paid. The Second Circuit observed that 15.34% participation was “at or near the upper limit” of what could be considered a select group, but the court still treated it as a Top Hat plan. They leaned on qualitative factors too – the average salary of participants was 3.5 times that of other employees, indicating they were indeed the highly-compensated group. The takeaway: courts have not set a bright line, but many have hinted that beyond a certain small percentage of employees, a plan can’t be a Top Hat. Also, including even one or two lower-paid folks could jeopardize the status. Demery is frequently cited in Top Hat cases to argue boundaries (others like a Fourth Circuit case Dugan suggested even 18% might be too high). For employers, Demery is a caution – keep that percentage low and be ready to show participants are clearly in the upper echelon.
- In re Enron (Bankruptcy Court, early 2000s): Although not a single appellate decision, the Enron collapse provided a harsh lesson. Enron had a sizeable executive deferred comp plan (a Top Hat plan). When Enron went bankrupt, the plan’s participants (executives) found themselves as unsecured creditors in bankruptcy court. They recovered only a small fraction of their account values, while their coworkers in the 401(k) plan, despite losing value from stock investments, at least had their remaining account assets protected from creditors. The bankruptcy court treated the deferred comp claims just like any other debt. Some executives tried creative arguments, like claiming the plan was misrepresented or should have been funded – but none of that saved their benefits. Lesson: No matter how large or secure a company seems, a Top Hat plan’s promises can evaporate in bankruptcy. This isn’t a court establishing new law, but it’s a real outcome that’s widely discussed in executive comp circles.
- Morgan Stanley Deferred Comp Case (ongoing, 2025 Second Circuit): In a very recent development, a group of Morgan Stanley financial advisors challenged the firm’s deferred comp plan. The plan had forfeiture provisions (if an advisor left and went to a competitor, they’d forfeit unvested deferred amounts – common in Wall Street “bonus bank” plans). A lower court found that Morgan Stanley’s plan was an ERISA-covered plan (because it allowed deferral beyond termination and was related to compensation arrangements). The advisors argue that if ERISA applies, those forfeitures violate ERISA’s vesting and anti-forfeiture rules. Morgan Stanley, interestingly, won an order to compel arbitration of the dispute (meaning the fight goes to FINRA arbitration rather than court), but then tried to appeal the judge’s statement that ERISA governs the plan. In July 2025, a Second Circuit panel was skeptical of Morgan Stanley’s attempt to overturn the ERISA coverage finding since Morgan had technically won on arbitration (you usually can’t appeal a win). The big picture: if the Second Circuit (covering New York) affirms that this type of plan is under ERISA, it could upend how Wall Street firms handle their bonus/deferred comp plans. Many such plans consider themselves Top Hat plans. If a court says “no, you have to follow ERISA vesting – you can’t make people forfeit deferred comp just for leaving,” it will change plan designs or at least how companies enforce them. Key point: This shows employees are increasingly savvy in using ERISA as a shield – if they can get their plan deemed an ERISA plan, they can strike down conditions like non-compete forfeitures. We’ll have to watch how the courts decide, but it underscores the tension: employers want the freedom of Top Hat plans; employees sometimes want the protection of ERISA when things go sour.
- Gilliam v. Nevada Power (9th Circuit, 2007): This case dealt with a different angle – the standard of review in Top Hat plan disputes. The Ninth Circuit held that even though Top Hat plans are exempt from most of ERISA, they are still subject to the same judicial review principles as other ERISA plans. Specifically, if the plan document gives the administrator discretion, a court will use a deferential “abuse of discretion” standard to review benefit denials (just like in a normal ERISA plan). Some other circuits (3rd and 8th) had hinted that because Top Hat plans have no fiduciary duties, maybe courts should review denials de novo. But the Ninth Circuit said no, that would create confusion; Top Hat plans, while unique, are still ERISA plans for enforcement, so the usual rules apply. For participants, this means if your claim for benefit under a Top Hat plan is denied and you sue, the court might give deference to the plan administrator’s decision – making it harder to win unless the decision was clearly unreasonable. This is an example of how being under ERISA (even in limited fashion) can actually hurt participants in some scenarios, due to the deferential review standard, whereas a pure contract claim in state court might get a fresh look at all the facts.
The thread through these rulings: definition and scope matter – courts examine what the plan’s purpose and design are to decide ERISA applicability, and Top Hat status can be contentious – too broad a plan can lose its exemption. The cases also highlight why careful drafting and adherence to criteria are essential for employers, and conversely, how participants might challenge plans to gain ERISA protections when advantageous.
Staying on top of case law is important for practitioners, but the major takeaways for most readers are: if you’re an executive with a deferred comp benefit, know that if push comes to shove, the legal outcome could depend on fine details of your plan’s design (and even which court has jurisdiction). And for employers: structure your plans carefully, because a misclassified plan can lead to litigation and potentially owing unexpectedly vested benefits.
ERISA vs. State Law: The Preemption Puzzle 🗽🤠
One more important angle: federal ERISA coverage vs. state law coverage. We’ve hinted at it, but let’s clarify with a state-specific lens (California, New York, Texas as examples):
- California: Known for strong employee protections, California law generally treats bonus and commission agreements strictly under wage laws. However, if a plan is an ERISA plan, those state laws are preempted. For instance, in California, unpaid wages must be paid promptly on termination, and there are waiting time penalties for delays. If an executive’s deferred comp isn’t ERISA-covered, could it be deemed wages that should have been paid at termination? Typically, deferred comp is documented such that it’s not “earned” or due until the future date (so California’s wage payment timing laws wouldn’t force immediate payout). In the case of Rich v. Shrader, since ERISA didn’t apply, it was purely a contract issue – subject to California’s statute of limitations, which barred the claim. Another California-related matter was CalSavers, the state’s automatic IRA program for workers. Businesses argued it should be preempted by ERISA; the courts disagreed because it’s a state-run program, not an employer plan – indicating California’s push to fill retirement gaps without running afoul of ERISA. For California executives, the key is: if ERISA doesn’t protect you, you turn to contract law. California courts will enforce the deferred comp contract as written. If there are any ambiguities, they might construe them in favor of the employee (since the employer drafted it). Also, California doesn’t allow non-compete agreements, but companies sometimes tie deferred comp to non-compete compliance. If ERISA doesn’t apply, a California court might refuse to enforce a forfeiture for competing, viewing it as an unlawful restraint on employment. (ERISA would preempt that state public policy – another way ERISA can actually help employers enforce non-competes via benefit plans). So, in CA, being outside ERISA could give an employee an argument that a forfeiture-for-competition clause is void under state law.
- New York: New York state law is generally more limited on wage protections for high earners (for example, certain Labor Law provisions exempt employees earning over a certain amount). If an executive deferred comp plan is not ERISA, New York employees might sue for breach of contract or under New York Labor Law Article 6 (wage payment laws), depending on the nature of the comp. New York courts have often had to decide if a plan is a “retirement system” (ERISA or not) or just a bonus. One Second Circuit case (Paneccasio v. Unisource, 2007) held that a severance arrangement was an ERISA plan, thus preempting state age discrimination and contract claims. In contrast, if it’s not an ERISA plan, those state claims proceed. New York also has a strong history of financial industry cases – e.g., brokers suing for unpaid bonuses. If those bonus deferral plans are ERISA (Top Hat), state claims are out and it goes to arbitration or federal court under ERISA. If not ERISA, brokers have won cases under contract law. The ongoing Morgan Stanley dispute is in New York – advisors got some big arbitration wins by invoking ERISA (one FINRA panel awarded over $3 million to advisors, citing ERISA violations). That shows in NY, if you get ERISA on your side, you might have an easier path to remedy (ERISA vesting rules voiding the forfeitures). If ERISA didn’t apply, each advisor’s claim would hinge on contract and possibly be limited by what the contract allows (which favored the company). So in New York, ERISA can significantly change the outcome; but if a plan is firmly not under ERISA, employees have to navigate more difficult state-law routes to recovery.
- Texas: Texas falls under the Fifth Circuit (which gave us the RBC case). The Fifth Circuit has been relatively expansive in calling plans ERISA plans (when in doubt, they lean toward coverage). Texas state law, on the other hand, is generally pro-employer in employment agreements. If a deferred comp plan in Texas is not ERISA, an executive’s breach of contract claim might face hurdles (Texas law might enforce the contract strictly, and Texas doesn’t have a robust wage law for high earners like some states). There was a notable Texas state case where an executive tried to claim his deferred comp should have been paid and that the plan wasn’t ERISA. The courts often find such plans are ERISA and thus preempt state claims. One example: in Halliburton Co. v. Admin. Review Bd. (5th Cir. 2008), a stock option/deferral plan was held not ERISA because it allowed a lump sum after a short period – but that’s an exception. In Texas, if you have a Top Hat plan and an executive tries to sue under state law for the benefit, the company will likely remove it to federal court saying “This is an ERISA Top Hat plan,” which preempts the state law. Then the fight is on ERISA terms, where often the deck is a bit stacked in favor of plan terms as written. For instance, in RBC’s case (Tolbert v RBC), once the Fifth Circuit said it’s an ERISA plan, the question became “was it a valid Top Hat?” If yes, the forfeiture on leaving stands (because Top Hat can do that); if no, RBC would have violated ERISA by causing forfeiture. The case ended up settling many claims in arbitration, but it put employers on notice in Texas: you better make sure your plan truly fits Top Hat, or you could owe a lot. Texas executives likewise learned: if you can frame it as not Top Hat (maybe too broad a group?) then the forfeitures might be illegal under ERISA.
In essence, ERISA preemption is a double-edged sword. It protects employers from varying state laws (which is why Congress created ERISA preemption – to have national uniformity in benefits law) and it gives employees a uniform set of rights. But if those ERISA rights are slim (like in a Top Hat plan), an employee might actually have fared better under a state law claim if ERISA didn’t preempt it. Meanwhile, if a plan is not covered by ERISA, employees can try to use more favorable state laws, but they lose the tidy enforcement mechanism ERISA offers.
For the target audience (business owners, HR, execs, employees), the practical point is: Know which law governs your plan. If ERISA governs, forget about state labor laws – focus on ERISA remedies. If ERISA doesn’t, then explore your rights under state law (and be aware of the statute of limitations and contract law nuances in your state). And for employers, if you want the predictability of ERISA (even just Top Hat minimal oversight), structure your plan accordingly so you can assert preemption if needed. If you’re fine with it being a pure contractual arrangement, then at least be mindful that you’ll be in state court if disputes arise.
FAQs: Deferred Compensation Plans & ERISA 💡
Below are some common questions (and quick answers) people have about deferred compensation plans and their ERISA coverage. Each answer starts with a “Yes” or “No” for clarity, followed by a brief explanation.
Q: Are non-qualified deferred compensation plans subject to ERISA like 401(k) plans?
A: No. Most non-qualified deferred compensation (NQDC) plans are exempt from ERISA’s strict rules. They’re usually set up as “Top Hat” plans for executives, so they don’t have to follow ERISA’s funding, vesting, and fiduciary standards.
Q: Do Top Hat plans have to comply with any ERISA requirements at all?
A: Yes. A Top Hat plan is exempt from most ERISA requirements, but not all. The company must still notify the DOL about the plan (one-time letter) and honor the plan’s promises – participants can sue under ERISA for their benefits, even though fiduciary and funding rules don’t apply.
Q: Is a deferred compensation plan for government employees (457 plan) covered by ERISA?
A: No. Government plans are not covered by ERISA. A public sector 457(b) or state/local pension is governed by public law, not ERISA. Participants rely on the government’s plan rules and state/federal statutes, without ERISA’s federal protections or preemption.
Q: Can a church-sponsored retirement plan opt into ERISA coverage?
A: Yes. Church plans are exempt from ERISA by default, but a church can elect to be covered by ERISA if it wishes. In practice, most church plans remain outside ERISA to avoid the compliance burden, unless they choose otherwise for specific reasons.
Q: If my company goes bankrupt, is my deferred compensation protected like my 401(k)?
A: No. Deferred comp in a non-qualified plan is not protected in bankruptcy – you’d be an unsecured creditor. By contrast, 401(k) assets are held in trust and shielded from the company’s creditors, so those remain yours even if the employer fails.
Q: Does ERISA preempt state law for all deferred compensation disputes?
A: Yes – if the plan is an ERISA-covered plan (even a Top Hat plan), then ERISA will preempt state law claims relating to that plan. If the plan is completely outside ERISA, then state law (contract, wage law, etc.) will govern any disputes.
Q: Can a plan lose its Top Hat status and get in trouble under ERISA?
A: Yes. If a plan that was meant to be Top Hat covers too many employees or isn’t truly limited to high-level folks, a court could rule it’s not a valid Top Hat plan. That would mean it was an ERISA plan that failed to comply (since it didn’t follow funding/vesting rules), leading to potential liability for the sponsor.
Q: Do I have any recourse if my non-qualified deferred comp plan refuses to pay out?
A: Yes. Even though NQDC plans lack ERISA’s full protections, you can still take legal action. If it’s a Top Hat ERISA plan, you’d sue under ERISA for benefits due. If ERISA doesn’t apply, you’d sue under state contract law. Either way, you can challenge a wrongful denial – but the legal pathway differs.
Q: Are there contribution limits in non-qualified deferred comp plans like there are in 401(k)s?
A: No. NQDC plans have no legal contribution caps. An executive can defer far more than the 401(k) limit (subject to plan terms). This flexibility is a big perk of non-qualified plans. However, extremely large deferrals could increase risk exposure if the company encounters financial issues.
Q: Does the SEC have anything to do with deferred compensation plans?
A: Yes, but indirectly. The SEC requires public companies to disclose executive deferred comp arrangements in proxies/filings, and if company stock is involved, securities laws must be followed. The SEC doesn’t regulate the plan’s terms (that’s ERISA/IRS territory), but it oversees transparency and any stock or insider-trading aspects of such plans.