Skip to content
ERLG Employee Retirement Litigation Group

Explainer

Rajappan v. Bloomberg L.P.: What the ERISA Lawsuit Against Bloomberg's 401(k) Plan Means for Participants

Published
November 13, 2026
Last reviewed
November 13, 2026
Jurisdiction
Federal (ERISA)

If you are in Bloomberg's 401(k) plan, Rajappan v. Bloomberg L.P. is a proposed class action in federal court in New York. A participant alleges that the plan's fiduciaries breached their ERISA duty of prudence by keeping two underperforming funds in the plan for years. These are allegations. No court has found that anyone did anything wrong.

A headline about a lawsuit over your own retirement plan raises fair questions: whether your account is affected, what is actually being claimed, and what the law requires of the people running the plan. What follows takes those in order, using the court's own docket and the statute's own words, and keeps to what those records show.

What the Lawsuit Alleges in Plain Terms

If you have only seen the headline, the core of the case is narrower than many 401(k) lawsuits. The case is Rajappan v. Bloomberg L.P., No. 1:26-cv-00785, in the U.S. District Court for the Southern District of New York, filed on January 29, 2026, according to the court docket. Plaintiff Rajkumar Rajappan brings it on behalf of the Bloomberg L.P. 401(k) Plan and a proposed class of participants, against Bloomberg L.P., the Bloomberg Investment Committee, the Bloomberg Retirement Plan Committee and unnamed John Does.

According to the First Amended Complaint, the defendants failed to remove the Harbor Capital Appreciation Fund and the Parnassus Core Equity Fund from the plan after December 31, 2019. The complaint alleges that participants had over $437 million in the Harbor Fund and over $59 million in the Parnassus Fund as of December 31, 2024. It also alleges that the plan covered roughly 20,000 employees, former employees and beneficiaries during the class period. Those figures are the complaint's own, not findings.

The complaint as filed in that version centers on investment performance. It does not plead an excessive recordkeeping fee claim, and this page does not describe one as part of the case.

The defendants dispute the claims and have moved to dismiss them. Their reply brief, a party's argument rather than a ruling, contends the complaint rests on "hindsight-driven" criticism and asks that it be dismissed with prejudice.

ERISA's Fiduciary Duties and Why They Apply Here

When you wonder who is answerable for the funds on your plan menu, ERISA's answer is the fiduciary. A fiduciary is a person or entity that exercises discretionary authority or control over a plan's management or its assets. The status is functional: it turns on what someone actually does for the plan, not on a title. The plan sponsor is the employer that establishes and maintains the plan, here Bloomberg L.P. The complaint names the sponsor and two committees as defendants; whether each acted as a fiduciary for a given decision is a question for the court.

Under 29 U.S.C. § 1104(a)(1)(A) (ERISA § 404(a)(1)(A)), a fiduciary must act "solely in the interest of the participants and beneficiaries" and for the exclusive purpose of providing benefits and "defraying reasonable expenses of administering the plan." That is the duty of loyalty.

Under § 1104(a)(1)(B) (ERISA § 404(a)(1)(B)), a fiduciary must act "with the care, skill, prudence, and diligence under the circumstances then prevailing that a prudent man acting in a like capacity and familiar with such matters would use." That is the duty of prudence, and it is the duty Count I of the Rajappan complaint invokes.

A third provision, 29 U.S.C. § 1106 (ERISA § 406), generally bars certain transactions, including a fiduciary dealing with plan assets "in his own interest" or receiving consideration for his own account from a party dealing with the plan. These duties reach both the choice and monitoring of investments and the arrangements with a recordkeeper (the company that keeps account records, processes transactions and sends statements). Those arrangements can include revenue sharing, where a fund pays part of its fee, out of fund assets, to the recordkeeper. The U.S. Department of Labor publishes participant guidance on these duties, though the statute itself is what courts apply.

Excessive Fees: What the Complaint Targets

Since many readers come to a 401(k) lawsuit expecting a fee case, it helps to be precise. The Rajappan complaint targets fund performance, not recordkeeping fees. Fee concepts still matter to anyone reading their own statement, and they can surface in any investment case.

An expense ratio is the annual percentage of a fund's assets taken to cover its operating costs. It comes out of the fund's returns, so it rarely appears as a separate line on a statement.

In fee cases generally, participants often allege that a plan's per-participant recordkeeping cost was out of line with comparable plans of similar size, and that fiduciaries never sought competitive bids or used the plan's size to negotiate. Revenue sharing can make the true price of recordkeeping hard to see, because part of it is paid through fund expenses rather than billed directly. Whether that happened in a given plan is a factual question.

ERISA sets no numeric cap on fees. Courts look at the fiduciaries' process, the services the plan received and the alternatives available. The Second Circuit, which covers the Southern District of New York, has required "meaningful" benchmarks for fee claims, according to the defendants' reply in this case citing Singh v. Deloitte LLP. A plan's actual fees appear in its Form 5500 filing with the Department of Labor; no Bloomberg plan fee figure is stated here because no Form 5500 was read for this page. A general overview of 401(k) plan mismanagement covers the warning signs participants usually notice first.

Investment Menu Claims: Underperforming Funds and the Prudent-Expert Standard

For a participant whose money sat in the Harbor or Parnassus fund, this is the heart of the case. Fiduciaries do not satisfy the duty of prudence by choosing funds once. Courts read § 1104(a)(1)(B) to require ongoing monitoring and removal of options that no longer belong on the menu.

The complaint alleges that the Harbor Fund, added in 2010, underperformed its benchmark, the Russell 1000 Growth Index, and that both challenged funds should have been removed after 2019. It alleges the harm traces to an imprudent process for selecting, monitoring and retaining the plan's options.

The defendants answer that the complaint shows only "modest underperformance" and "cherry-picked alternatives." Their reply argues that removing the Harbor Fund at the start of 2020 would have cost participants a year in which, they say, it returned 54%. That is their argument, not a finding. They also argue the plaintiff lacks standing to challenge the Parnassus Fund because he never invested in it.

Courts ask whether the process was sound, not whether a fund later did well or badly. Many plans also offer a target-date fund, which shifts its mix of investments automatically as a chosen retirement year approaches; the complaint does not challenge one. Comparable investment-menu disputes appear in Becker v. Wells Fargo and Snyder v. UnitedHealth Group.

How ERISA Class Actions Like This One Work

If you never signed anything, you may still be inside this case. That is because 29 U.S.C. § 1132(a)(2) (ERISA § 502(a)(2)) lets a participant sue "for appropriate relief under section 1109," which is relief to the plan itself. The complaint says it seeks to make good "to the Plan all losses" from each alleged breach, plus other plan-wide equitable relief. Under § 1132(a)(3), courts may also grant "other appropriate equitable relief."

A class action is a lawsuit in which named plaintiffs represent a larger group of people in a similar position. The court's order calls this a "putative" class action, meaning no class has been certified. Certification requires the court to find that the claims are common enough to be decided together.

Before that, defendants usually move to dismiss, arguing the complaint fails to state a plausible claim. Here, the court docket shows the first motion to dismiss was denied as moot after the plaintiff chose to amend. Defendants filed a new motion on May 20, 2026. On June 17, 2026, the plaintiff moved for leave to file a Second Amended Complaint. On June 23, 2026, Magistrate Judge Barbara C. Moses stayed discovery pending a decision on the motion, finding it raised "substantial arguments for dismissal." The judge also acknowledged that the plaintiff had raised significant opposition. That order pauses discovery; it does not decide the claims. The docket shows the motion to amend was opposed on July 1, 2026, with a reply on July 8, 2026. As of the docket read on November 14, 2026, whose latest entry is dated August 13, 2026, it shows no ruling on the motion to dismiss or on the motion to amend. Surviving a motion to dismiss would not prove the allegations either.

Some ERISA cases resolve by settlement, which ends a case without a finding of liability unless the court's order says otherwise. The GM company stock case, Pyrka v. General Motors, shows how court approval of one worked.

What This Case Means If You Are a Bloomberg Plan Participant

By the time a participant reads about a suit like this, the practical question is usually about the account. Filing a lawsuit does not, by itself, change the plan's terms. Contributions, withdrawals and rollovers remain governed by the plan's ordinary rules. If a class were certified and money were later recovered, it would go to the plan and reach accounts through a court-supervised distribution.

Your own rights under the plan are measured in plan terms. Vesting is the schedule on which you earn a non-forfeitable right to employer contributions. An accrued benefit is what you have earned under the plan's formula as of a given date. In a 401(k), that is generally your vested account balance.

Timing rules are set by 29 U.S.C. § 1113 (ERISA § 413). A fiduciary-breach claim must be brought by the earlier of six years after the last action that was part of the breach (or, for an omission, the last date it could have been cured), or three years after the plaintiff had actual knowledge of the breach. In cases of fraud or concealment, the limit is six years from discovery. Which period applies depends on the facts. A claim for benefits is different: 29 U.S.C. § 1133 requires the plan to have a claims procedure with written notice and review, and courts, not the statute, generally require using that procedure before suing for benefits.

Frequently Asked Questions

ERISA plans generally must protect account balances from assignment, which shields them from most creditors. That is a separate subject from this case. Rajappan v. Bloomberg challenges how the plan's fiduciaries managed the investment menu; it is brought on the plan's behalf and does not seek anything from participants' own accounts.

Related ERISA Resources

This page provides general information, not legal advice. Laws and regulations change; consult an attorney about your specific situation.

Attorney Contributor: Charles H. Field
Co-Chair, Financial Mismanagement and ERISA Litigation Practice Group | Licensed in California, State Bar No. 189817
Contributor attribution recognises participation in this website's content program. It does not mean that this page was personally authored, reviewed or approved by the contributor. General legal information only; this material does not constitute legal advice or establish an attorney-client relationship.

Sources

Citations link to free, stable, official sources: the United States Code as published by the House Office of the Law Revision Counsel, the Department of Labor's regulations and Form 5500 filings, and the published opinions of the federal courts.

Last reviewed November 13, 2026.

Concerned About Your 401(k) or Retirement Plan?

The case review is free and confidential. Speaking with counsel early may preserve options that are harder to recover later.

Call UsEmail UsCase Review