Court Dismisses One Lawsuit Against ADP Multiple Employer Plan

A court found a participating employer was not a fiduciary with respect to alleged actions in the lawsuit, and therefore was not under threat of being sued for those actions.

A plan sponsor participant in the ADP TotalSource Retirement Savings Plan, a multiple employer plan, has lost its effort to sue ADP, ADP TotalSource Group and the plan’s administrative committee over allegedly excessive fees.

The defendants filed a motion to dismiss the complaint, arguing, among other things, that McCaffree Financial Corp. does not have constitutional or statutory standing to sue. McCaffree responded that it has constitutional standing because it might be sued as a co-fiduciary for the defendants’ alleged breach of fiduciary duties, and that it has statutory standing as a fiduciary. Judge Esther Salas of the U.S. District Court for the District of New Jersey agreed with the defendants and granted their motion to dismiss.

Get more!  Sign up for PLANSPONSOR newsletters.

Salas noted that constitutional standing consists of three elements: The plaintiff must have suffered an injury in fact that is both fairly traceable to the challenged conduct of the defendant and likely to be redressed by a favorable judicial decision. The defendants argue that the complaint fails to allege injury in fact, while McCaffree says it has suffered an injury in fact because, as a co-fiduciary, it is at risk of being sued under the Employee Retirement Income Security Act for the defendants’ alleged unlawful conduct.

Salas found that the plaintiff does not plead any facts suggesting that it could actually be held liable as a co-fiduciary. For example, her opinion states, McCaffree does not allege how a future plaintiff could reasonably plead that it was a co-fiduciary “with respect to” the unlawful conduct allegedly committed by the defendants.

Regarding statutory standing, Salas noted that under ERISA, a “participant, beneficiary or fiduciary” may bring a civil action for appropriate relief against a plan fiduciary for breach of fiduciary duty. However, McCaffree is not the “named fiduciary” per the plan document, which identifies the administrative committee as the named fiduciary.

As for being a functional fiduciary, Salas cited prior case law in saying a court must ask “whether [the person] is a fiduciary with respect to the particular activity in question.” She found that the complaint does not identify any authority or control, discretionary or otherwise, that McCaffree has with respect to management or administration of the plan or plan assets. The lawsuit also doesn’t identify any investment advice that McCaffree offers or demonstrate that it has the authority to render such advice. “Much less does the complaint suggest that the plaintiff is a co-fiduciary ‘with respect to’ the defendants’ alleged conduct giving rise to [McCaffree’s] claims,” Salas wrote.

Salas also pointed out that the lawsuit alleges that the defendants breached their fiduciary duties by subjecting the plan to excessive total plan costs and excessive recordkeeping/administrative costs, by failing to oversee the plan recordkeeper and engaging a recordkeeper with a conflict of interest, and by permitting objectively imprudent investment options. It does not identify what authority or control McCaffree had with respect to those actions. “Indeed, the complaint does not suggest, and plaintiff does not argue in its opposition brief, that plaintiff has any authority, control, or oversight duties with respect to setting or negotiating total plan costs or recordkeeping/administrative costs, appointing or terminating the recordkeeper or trustee, or advising or setting investment options,” Salas wrote in her opinion. “Moreover, the court cannot glean any such responsibilities pursuant to the terms of the plan.”

Since McCaffree fails to plausibly plead that it is a fiduciary to the plan, it follows that it has neither constitutional nor statutory standing to sue, Salas concluded.

The week after McCaffree filed its lawsuit, another lawsuit with similar allegations was filed on behalf of participants in the ADP TotalSource Retirement Savings Plan. Salas gave the parties in that case until April 15 to assess the impact of her decision in the McCaffree lawsuit on the proceedings of their lawsuit.

Proposed RMD Rules for 403(b)s Could Mean Big Changes

A change to how required minimum distributions are taken from 403(b) contracts might call for changing recordkeeping systems and dusting off information sharing agreements.

A change to required minimum distribution rules for 403(b) retirement plans proposed by the IRS is causing industry chatter.

Currently, the RMD rules applicable to individual retirement accounts apply to section 403(b) contracts. As David Levine, principal at Groom Law Group, Chartered, explains to PLANSPONSOR, that means a participant doesn’t have to take his RMD amount from each 403(b) contract he has, but can take calculated amounts from any one plan account.

Never miss a story — sign up for PLANSPONSOR newsletters to keep up on the latest retirement plan benefits news.

Also, although IRA trustees are required to report to the IRS and provide to IRA owners certain information regarding RMDs, such as whether an RMD is due for a year and the account balance on which it will be based, the IRS requires no reporting with respect to RMDs from 403(b) contracts. “Accordingly, a section 403(b) plan is neither required to automatically make a required minimum distribution for a participant nor required to inform the IRS or the participant that a required minimum distribution is due or the account balance on which the distribution is based,” the IRS explains in its proposed rules.

However, the agency says it is “considering additional changes to the required minimum distribution rules for section 403(b) plans so that they more closely follow the required minimum distribution rules for qualified plans.” Levine says the IRS is proposing to make 403(b)s like 401(k)s under RMD rules. An RMD would have to be taken from each 403(b) contract, rather than a participant being able to request his total RMD amount from one 403(b) account.

Levine says this is a big deal because recordkeepers don’t hold individual annuity contracts for participants and do not have systems in place to force out an RMD from a 403(b) annuity contract. He adds that recordkeepers would have to make updates to their systems and 403(b) plans with individual annuity contracts would have to coordinate RMDs across accounts. Plan sponsors, dust off your information sharing agreements.

Asked whether he thinks this proposed change will be finalized, Levine says there’s a chance, but he believes there will be many comments about it. The comment period for the proposed RMD rules ends May 25.

«