Non-ERISA 403(b)s Off the Radar

Until regulations passed in 2007, 403(b) plans didn’t fall under the same Employee Retirement Income Security Act (ERISA) regulatory oversight to which 401(k) plans were subjected.

In fact, says Ellie Lowder, tax-exempt and governmental plan consultant at TSA Consulting and Training Services, before the regulations changed, most 403(b) plans were not treated like plans, but simply “arrangements,” in which an employer provided a payroll slot to a provider and then remitted contributions to the provider. Plan sponsors were only required to play a very limited role in plan oversight and administration, she tells PLANSPONSOR.

However, with the 2007 regulations only three types of 403(b)s are exempted from ERISA scrutiny—church plans (which can elect to be ERISA plans), governmental plans and plans with limited employer involvement (those that fell under the ERISA “safe harbor” for 403(b) plans)—a plus or a minus for plan sponsors, depending on your view.

If anyone is harmed by the absence of new regulations for non-ERISA 403(b)s over such a long time frame, says Carol A. Idone, vice president of business development at Strategic Benefit Services, it’s the participants themselves, and fees are the reason. If the plans were subject to ERISA, she tells PLANSPONSOR, “participants might be able to get better pricing, if it’s a true group plan. [There are] more providers in the market willing to [take on] ERISA plans.” 

Church plans that do not elect to be governed by ERISA and governmental plans will never be ERISA plans, but private-sector plans with limited employer involvement risk becoming ERISA plans. Idone contends some non-ERISA 403(b)s are getting very close to edge of becoming ERISA plans. The Department of Labor (DOL) could well point to some practices in these plans and say, “Based on what you’re doing, this plan should fall under ERISA.” She says she has seen plans take action that are in the best interests of the participants, the very thing that will trip them up. 

The lack of clear-cut guidance to clearly mark the difference between 403(b) plans that do or do not fall under ERISA can make life difficult for plan sponsors, who are told it will be decided on a case-by-case basis. “It comes down to facts and circumstances,” Idone says. “It’s based on what the plan sponsor is doing, how much control the employer is exerting—too much, and it’s an ERISA plan.”

While the guidelines may seem unclear, Idone explains, generally they are: plan sponsors cannot monitor investments or be involved in the hardship and loan approval process. They can provide data on loans, but cannot actively approve the loans or hardship withdrawals. Plan sponsors cannot be involved in fee reviews. They can look at the fees but cannot say that fees are too high: “That is a murky area they have to be aware of,” Idone says.

And when it comes to the vendor arrangements for the plans, she says debate is ongoing: if the plan has just one vendor, does that make it an ERISA plan? Or, if it is an open-architecture investment platform, is it a non-ERISA 403(b)? There are equal opinions to support either side.

One particularly thorny situation can arise when a single organization has side-by-side plans: a 403(b) that falls under ERISA and a non-ERISA 403(b). Each plan contains different products—mutual funds in the ERISA-governed plan, and an annuity product in the non-ERISA plan—but both plans use the same recordkeeper.

Since non-ERISA 403(b) plans are prohibited from performing investment reviews, Idone observes, the employer may not exert control over the non-ERISA plan, such as conducting an investment review and deciding to remove an investment. Her firm recommends eliminating the non-ERISA plan, but if the plan sponsor is going to keep it, the firm advises keeping a hands-off approach.

“It’s confusing for everyone,” Idone says, “because they have their eyes closed with the non-ERISA plan and full involvement on the ERISA plan.” During meetings of the plan committee, she says, any discussion of the non-ERISA 403(b) must be held to a strictly general level, lest the plan become subject to ERISA.

When the organization uses the same recordkeeper for both plans, Idone says, nine out of ten participants would be unlikely to know the difference between the two plans, and often participants think of the two plans as one, with the same products.

One reasonable explanation for offering both an ERISA and non-ERISA plan Idone says she’s heard from an organization’s chief financial officer is that side-by-side offerings give employees a choice. “[But] is it a good choice?” she asks. “There’s no fee disclosure, no independent review of investments. On a plan committee with six or seven members, the members often don’t know the difference.”

Idone, whose business is largely nonprofits and 403(b) plans, concedes that many small to medium-size nonprofits benefit by offering a non-ERISA 403(b) without a match. “It’s not uncommon to have 200 employees eligible for a voluntary-only plan, but only 50 employees participating,” she says. ERISA requires organizations with more than 100 eligibles to conduct a plan audit each year at a cost ranging from $5,000 to $15,000—a significant expense for some plan sponsors.

But, in general, Idone believes the current regulations that govern non-ERISA 403(b)s don’t go far enough, and the plans should have been eliminated. “I can’t imagine the government is going to go too much longer with no reporting being done on these non-ERISA plans,” she says.

However, Lowder believes the plans are useful for some nonprofits, especially with an administrative burden eased by industry support. “Generally speaking, public school districts don’t have HR departments or staff members in these plans with plan expertise,” she points out. “When the regulations first changed, it created some angst and some employers tried to terminate their plans, but the industry worked to put together compliance support for these employers to help them.”