'

Testing of the MEP Waters

In blogging, I don't typically write about informal conversations I have had with anyone, including government staff, friends or colleagues, without first discussing it with them.  I fear that otherwise I would indeed lead a lonely life, as who would ever talk with me if there was a chance that conversation would end up on the internet the next day? 

In spite of this, I've chosen to write  about a discussion with DOL staff today only because I really think it would be helpful to add a bit more color  to Ilene Ferenczy's newsletter on "Clues From the Ivory Tower," a well written piece on on the ASPPA meetings with the DOL where issues on multiple employer plans were raised, among others.
 
Ilene appropriately and accurately describes the conversation with the DOL on MEPS in her newsletter, but reactions on the social networks to her newsletter has lead me to think that a little more context may be useful to more fully understanding the conversation. 
 
I was at the same meeting as Ilene. The question arose as to whether a non-association MEP would qualify as a single plan under ERISA, so to enable a single Form 5500, single audit, and a host of other things. DOL staff's reaction was that they believed that a non-benefit related commonality is needed, but they also expressed a willingness to discuss the idea. We explored several different points.
 
To be fair to the DOL staff, they were presented with the question almost as an afterthought, and staff had not been put on notice that we were looking for a thoughtful response. Likewise, we did not intend to prepare a case for why the answer should be one way or another. It was truly an initial response, to a sort of testing the waters on our part, with DOL staff asking follow up questions exploring why they should rule differently than with the MEWAs.
 
There is little doubt that any 413(c) MEP, including the non-association MEP, has substantial commonality. My ASPPA webcast next week will outline those, but includes vesting, participation, exclusive benefit and a few other things-413(c) even has the DOL drafting special break-in-service rules for 413c, which- I think-never have been written.
 
What it boils down to is actually a narrow question: should ERISA 3(5) be read to require a non-benefits based commonality. That is the concern raised by DOL staff. In my view, the language of ERISA does not require this, nor is there any regulation that does it.  What seems to be the genesis of  this narrow construction was based upon sound public policy: it  was necessary to stop those abusive healthcare MEWAs from continuing to harm participants who were purchasing non-existent health care coverage.  That narrow construction worked well to "plug the dike" until Congress stepped in to change the MEWA rules without requiring the DOL to engage in contortions.
 
The DOL has not ruled (either by Advisory Opinion or informal guidance) on what should be required under ERISA for a 413c plan to be recognized as a single ERISA plan, using the definition of employer under ERISA 3(5).  413c, unlike the MEWA rules, requires substantial commonality to qualify under the Code section as a single plan, but it is a benefits based commonality-one which the DOL position argues against.
 
From a purely policy perspective, as long as the ERISA rules are followed properly, a MEP can actually enhance the compliance that MEWAs were attempting to avoid. Think about it. It really is about professionals now willing to serve as the 3(16) Administrator-after years of TPAs and other professionals (acting on advice of us lawyers) making sure they WEREN'T serving in this role. Now, there appears to be a real market need for it.
 

So, the DOL's initial, and informal, position is that a non-benefits commonality is required for a 413c MEP-I believe in large part because of the long line of of well established MEWA rulings saying so. I think the answer should be otherwise, as supported by the IRS regulatory structure under 413c of what constitutes a single plan, which is substantially different than the MEWA rules (or lack thereof) upon which the DOL position seems to be based. I suspect there will be some parties making this case to the DOL, in a much better prepared manner, and I would expect, over time, a thoughtful response from the DOL once they have reviewed things. But this means before one sets up a new MEP, one should do it with knowledge that the DOL may eventually not agree with this position. But there are a number of very large plans n the market already, so even the DOL's nonacquiesence may not be the end of it. Even the GAO has taken an interest, and is doing initial research on whether these MEPS are a good tool to deepen retirement plan penetration in the small end of the marketplace.

Stay tuned, and step cautiously.  

 

 

Any discussion on any tax issue addressed in this blog (including any attachments or links) is not intended to be used, and cannot be used, for purposes of avoiding penalties imposed under the United States Internal Revenue Code or promoting, marketing or recommending to another person any transaction or tax-related position addressed therein. Further, nothing contained herein is intended to provide legal advice, nor to create an attorney client relationship with any party.   

 

IRS Extends 8955-SSA Deadline

 Important Update to last blog posting. On June 21, IRS announced the extension of the 8955-SSA deadline to January 17, 2011, for which no Form 58 extension will need to be filed. The announcement is here.

Tags:

403(b), 8955-SSA and 408(b)2

Important Update. On June 21, IRS announced the extension of the 8955-SSA deadline to January 17, 2011, for which no Form 58 extension will need to be filed. The announcement is here

 

The challenges continue for 403(b) plans, as the IRS and DOL continue to implement their plan level rules in the 403(b) space. The most recent: the IRS's Form 8955-SSA  and instructions for the 2009 plan year, released on June 18th. You will need Adobe X to open them.  It is due to be filed by August 1, with a 2 1/2 month extension permitted if you file a separate Form 5558.

The Form 8955-SSA replaces the old Schedule SSA to the Form 5500, where former employees with vested account balances remaining in the plan are reported.

Prior to 2009, ERISA 403(b) plans (the only 403(b) plans required to file a Form 5500) never had to file a Schedule SSA because the Form 5500 instructions never required them to do so. Curiously enough, it appears that the DOL may never really have had the authority under ERISA Section 110 to waive its filing in prior years because it is required under Code Section 6057(a), not under ERISA. Here's the language, by the way, from the 2008 5500 instructions:

"403(b) Arrangements: A pension plan or arrangement using a tax deferred annuity arrangement under Code section 403(b)(1) and/or a custodial account for regulated investment company stock under Code section 403(b)(7) as the sole funding vehicle for providing pension benefits need complete only Form 5500, Part I and Part II, lines 1 through 5, and 8 (enter pension feature code 2L, 2M, or both). Note: The administrator of an arrangement described above is not required to engage an independent qualified public accountant, attach an accountant’s opinion to the Form 5500, or attach any schedules to the Form 5500."

Now to the tough part.  For ERISA 403(b) plans for which no SSA has ever been filed, how far back does a 403(b) plan sponsor need to go in reporting past participants? Conni did quite a piece on this for our Thompson Publishing newsletter. She strongly makes the case, with which I concur (but, please, check with your own counsel), that Rev Proc 2007-71 is actually determinative here. Oversimplifyng it, under 2007-71, 403(b) contracts which were issued prior to 1/1/2005, and to which no contributions have been made after 12/31/2004 (but loans, 90-24 transfers and other such things may also come into play), are not considered part of the 403(b) plan.

If you use this as a starting point, it would appear that the plan sponsor may need to go back to the 2005, 2006, 2007, 2008 and 2009 plan years, list all terminating participants from those years, and provide that to their current and deselected vendors. Then they will need to find which of those former employees have a current account balance (as of plan year end 2009)-but only if they had made a deposit to those contracts after 2004. And only for those years in which the plan was an ERISA plan. There is a bit more to it as well, as you are really trying to see who you can exclude for 2007-71 purposes.

A caution: the IRS has not taken this positiion on this. What really would be helpful is if the IRS issued relief telling us we only need to report those who left employment after January 1, 2009. 

408(b)(2) also comes into play here.  I had blogged on the "Flushing Effect" of 408(b)(2), where deselected ERISA 403(b) vendors will be required to make disclosures to plan sponsors in order to keep the comp on these contracts. I suspect that a number of employers will be surprised by these disclosures, and be receiving notices on contracts they may not realize exist.  This, in turn, is likely to cause consternation about the data on the 5500 filings in the past-and the new 8955- which then may need to be amended.

Its not getting any easier.  

 

 

__________________

 

Any discussion on any tax issue addressed in this blog (including any attachments or links) is not intended to be used, and cannot be used, for purposes of avoiding penalties imposed under the United States Internal Revenue Code or promoting, marketing or recommending to another person any transaction or tax-related position addressed therein. Further, nothing contained herein is intended to provide legal advice, nor to create an attorney client relationship with any party.   

 

 

 

 

 

Let’s face it. The appeal of a show like “Jeopardy” is that, every once and awhile, you are able to shout out the answer before the reigning champion buzzes in. I experienced the same sensation after reading that an attorney as distinguished as Eugene Scalia – the former Solicitor of the U.S. Department of Labor – came to the same conclusion as I had in a prior piece published on this blog. (See “The DOL’s Proposal to Update ERISA’s Fiduciary Definition: Right Thought, Wrong Approach,” posted on May 16, 2011.)

While my article was not nearly as erudite and well-researched as Mr. Scalia’s, the legal reasoning was founded on the same premise – namely, that administrative agencies should not be permitted to change existing law through the regulatory process.  Our Constitution specifically granted lawmaking authority to the legislative branch – and for good reason. While subjecting a proposed piece of legislation to the whims of a body comprised of 535 politicians certainly slows the process of change, it also helps to ensure that all potential ramifications of such a change are thoroughly vetted.

As I noted in my blog,

(T)he Department has attempted to pound a square peg into a round hole by using over 1,100 words to redefine the meaning of the phrase “investment advice” – as used within the statute – to significantly broaden the definition of a plan “fiduciary.” Needless to say, by straying so far from the common usage of the phrase, the DOL opened itself up for criticism stemming from the (presumably) unintended consequences of its proposed rule. For example, federal securities laws – namely, the Investment Advisers Act of 1940 – already regulate those who provide investment advice for compensation, and those rules apply whether the client is an 85-year old widow or a multi-billion pension fund.

As a result, I share in Mr. Scalia’s opinion that the Department lacks the authority to adopt the proposed regulation. However, I respectfully disagree to the extent he argues that no change in the current status quo is needed.

Continue Reading...