'

Robert Toth

Robert Toth has no picture

Bob Toth has more than 25 years of experience in employee benefits law. His practice focuses on the design, administration and distribution of financial products and services for retirement plans, one which combines elements of ERISA, tax law, insurance law, securities law and investment law for both 401(a) and 403(b) plans. Bob's experience includes implementing 403(b) programs under the new regulations; designing investment products for 401(k) plans; annuitization programs for defined contribution plans; advising on prohibited transactions issues related to retirement plan products and services and their distribution, development of open architecture programs for 403(b) plans; ESOPs and writing and implementing standards for fiduciary and advisory practices. Bob was a partner at Baker and Daniels and spent 17 years in the legal division of Lincoln National Corporation, where he was Associate General Counsel managing the legal affairs of LFG's employer market division. Prior to joining LFG, Bob was a Senior Attorney at Kellogg Company in Battle Creek, Michigan, where he provided in-house counsel for all benefit law issues related to the company. Bob is a Fellow of American College of Employee Benefits Council, and an Adjunct Professor at John Marshall School of Law’s Employee Benefits LLM Program, teaching the 403(b) and 457 plan courses. He graduated from Wayne State University Law School in 1983, and from the University of Michigan in 1978.

Bob is licensed to practice in Indiana and Michigan, and is admitted to the U.S. District Court for the Eastern District of Michigan. His professional associations have included the American Society of Pension Professionals and Actuaries (Member; Board Member of ABC of Northern Indiana; Great Lakes Benefits Conference Executive Committee; Vice Chair, Tax Exempt Plan Committee); EP Program Chair of the IRS Great Lakes TE/GE Council; Co-founder of the Institute for Pension Plan Mgt, Purdue University; Past member of the Advisory Board of the American Benefits Council; Past Chair of the American Council of Life Insurance's Pension Committee; and a member of the American Bar Association. He is licensed to practice in Indiana and Michigan.


Articles By This Author

The DOL continues with its sensitivity to the challenges created for 403(b) plan sponsors in the transition to an employer accountable world. In today's release of the final 408(b)(2) regs, the DOL provided tremendously needed relief for 403(b)plans. The language from the preamble speaks for itself:

The Department was persuaded by commenters on the interim final rule to exclude all or that part of a Code section 403(b) plan (hereafter “403(b) plan”) that consists exclusively of “frozen” contracts or accounts, as described in the Department’s Field Assistance Bulletins addressing the limited application of the annual reporting requirements to such contracts or accounts.  Plan sponsors and fiduciaries likely would be unable to comply with this rule because they often have no dealings with the relevant plan service providers and are unable to obtain information about these contracts and accounts.  Accordingly, paragraph (c)(1)(ii) of the final rule now provides that, in the case of a Code section 403(b) plan subject to Title I of ERISA, the “covered plan” would not include annuity contracts and custodial accounts described in section 403(b) of the Code with respect to which the plan sponsor ceased to have any obligation to make contributions (including employee salary reduction contributions) and in fact ceased making contributions to such contracts or accounts for periods before January 1, 2009.  Further, the contract or account has to have been issued to a current or former employee before January 1, 2009; all the rights and benefits under the contract or account have to be legally enforceable against the insurer or custodian by the individual owner of the contract or account without any involvement by the employer; and such individual owner has to be fully vested in the contract or account. 
As with everything 403(b), there are going to be complications, as it is not a totally carte blanche of pre-2009 "frozen" contracts. There will be odd circumstances, like where  vendors who insist on employer approval on loans and distributions from those contracts (but the price of that insistence will be 408b2 disclosure).
 
The real value of this new DOL position will be as the "flushing" of old 403(b) contracts begins-and we have, indeed, seen it begin.  Plan sponsors will be able to manage vendors effort at these disclosures as long as they take the steps to make it clear that they are not exercising authority over these contracts. It also closes the loop on the past FABs which initially granted reporting relief only. 

The successful chair of a committee serves the committee, the committee does not serve the chair. And so it was with the creation of the just-released "best practices" 403(b) Model Disclosure, which was developed jointly by NEA, ASBO, NTSAA and ASPPA. I was fortunate enough, and honored, to serve as the chair of that group. I have chaired  and served probably more than my fair share of retirement industry related committees over the course of my nearly 30 year career, but this effort was incredibly different: the driving force was not vendor interests, government policy interests, or of those serving our profession. From early on, the focus was instead plan participants,  to get to participants in non-ERISA 403(b) plans (and, in particular, employees of school districts) information that would be useful and inmportant in their purchase of 403(b) retirement products.  Lisa Sotir-Ozkan from NEA Benefits and Melody Douglas from ASBO very much drove the process, and kept us focused on this goal. 

Cloning 408(b)(2) or 404a-5 wasn't sufficient, nor was relying on those thick prospectuses that accompany variable 403(b) contracts. As valuable as the DOL disclosure schemes are in the employer-sponsored, institutional context, and as important as prospectuses are in protecting investor interests, they the lack simplicity -or obscure in volumes of other data- that which is particulalry important to the individual 403(b) participant. These plan particpants are not fiduciaires, and often do not have anyone to be able to collect and compare data on their behalf. They are sold investment products directly. So it really becomes a very simple issue for that school teacher or adminstrator: how much sales commissions is my investment generating; what services am I getting in return; is there a way for me to compare it all; and how can I reasonably access comparative data on the investemnts themselves?

There is the practical problem: whatever would be recommended also had to be doable by the 403(b) vendor providing the product, so disclosure was based upon information that was already being collected in some way by providers in the ERISA world. The committee also recognized the value of the comparatve format for investments under 404a-5 (and the significant investment being made in those dsclosures),  and took advantage of the benfits of that work by recommending their use here.

The Committee, with skillful drafting support and guidance from ASPPA's Deb Davis and with Craig Hoffman's ongoing involvement in our work,   put in serious time over the past 6 mohts to balance the useful with the doable. Along with Lisa and Melody, Aaron Friedman, Carol Gransee, Chris Guanciale,  Scott Betts  and Theresa Ward put together what I consider a pretty good piece of "engineering."  Having known engineers from from my days in Michigan, who have told me that successful engineering is really the art of successful compromise (as, they have said, you cannot have the fastest, strongest AND most fuel efficent vehicle in one; its always a balance between them all), this group can lay claim to a pretty good result.

We all recognize that this first effort was not perfiect, and pratcice will be a good teacher for us as we try to bring a new level of transaprency into play.  There is likely to be changes as we find out what we really did here. But its a pretty good start.

Freedom and liberty are not merely themes sounded by politicians in political campaigns, or in rousing marches by military bands (though I am personally  particularly fond of them!), nor are they ideas which you will typically see being discussed in a piece about retirement issues. But they are themes woven into the fabric of our our everyday life, without our often even even being aware of them. They form not only the basis of our own civil society, but (believe it or not) are deeply embedded in the holy texts of the major religions. 

But there is a risk nowadays in even referencing these two grand ideas in today's political environment: instead of being viewed as the firm basis of how the vast majority of us quietly operate, they seem to have been outrageously hijacked by political extremists (such as of the libertarian/Ron Paul/ Tea Party sort-of which I am not so inclined) for some specific end.

In spite of all that, there is something well worth mentioning along these lines about the striking impact of the work we do, something we are not prone to see while working the fine minutiae of our chosen profession.

If we step back for a minute, we can see the extraordinary policy underlying 408(b)(2), the prohibited transaction rules and the exclusive benefit rules (which apply even to non-ERISA plans).  These rules seek to set aside and protect from others the individual wealth of those who accumulate benefits under these plans. It became pretty plain to me while reading Absolute Monarchs, by John Norwich (a history of the Catholic Popes, which really is a brief history of the absolute power of royalty as well as the church over individuals), where, historically, an individual's financial well being was wholly dependent on the whims of powers that be.

We now have something very odd in man's modern history. The value of the funds which are now protected for participants in retirement plans by the Code, ERISA or both approximates 85% of the value of publicly traded securities in the United States.  Though this seemingly huge amount is not yet adequate to establish broad retirement security, it is material enough to take note: these pooled funds are outside of the legal reach of the unaccountable "whims" of those who have something other than the best interests of the participants at heart.  Imagine that. A significant and growing portion of society's wealth is institutionally dedicated in funded pools to the individual's well being, which are difficult to access by an abusive use of power which has so often corrupted society-and jeopardized freedom and liberty-in the past. 

The only way this really works, however, is by things like 408(b)(2); by enforcement of the prohibited transaction rules; and by giving serious attention to the exclusive benefit rules. And all of this is dependent on what appears to be non-sensical minutiae upon which we daily work.

There is a reason I like doing what I do......

 A while back, I did a piece on the manner in which the 408(b)(2) regs applied to the variable investment accounts under a group annuity contract held by a retirement plan, in particular, 401(k)plans; and a "light" piece on its application to general account products. In that I hear more and more rumblings  about the "fixed investment" portion of these accounts under 408(b)(2), it may be helpful to take another, more detailed look at how that reg applies to such accounts.

The first thing that comes to mind when looking at the regs for these purposes is the thing I noted in that previous blog: regardless of what you may think about 408b2 and the requirements now imposed by the rules, this reg has been craftfully drafted. The pieces fit together nicely, and complex issues with regard to investment products have been meaningfully addressed in as simple and direct manner as possible.There may be a few interpretaive issues that need to be resolved (which is to be expected), and 403(b) issues continue to be a serious challenge, but this is a fine piece of technical writing.

So it is with the "guaranteed account," "stable value fund" or "fixed account" within these group annuity contracts.  The 408(b)(2) pieces fit well together.

First, it may be helpful to read my piece on general accounts, and how they work. This can go a long way in understanding why 408b2 applies in the way it does. It is one of my favorites, because it includes a Dick Van Dyke clip from "Mary Poppins." That blog only generally addressed the 408b2 issue.

Next, the fiduciary needs to know whether or not the investment account is a contractual obligation of the insurer,  backed by the "general assets" of the insurer, or if it is part of a "separate account" (see my above noted blog on this). Confusion may arise from the variety of marketing names these funds may be called: the general account product will sometimes be called a "stable value fund" (typically because the crediting rate is set by use of an unrelated, third party index), which may be confused by a "stable value" mutual fund or collective trust interest which is offered under the annuity contract's variable investment separate accounts.

Once you know that fund is a fixed obligation of the insurer from its general account, you need to see what kind of Covered Service Provider (CSP) is the insurer.  It will not be considered an "A" type with regard to the fixed account, because it is not a fiduciary with regard to the management of the assets of the general account backing its contractual promise (a book could be written on this point, alone).  It may be a "B" type of CSP if, under the contract, the insurer is a "recordkeeper."  It will not typically be a "C"  type of CSP because, even though it is insurance, the insurer will not usually receive indirect compensation (as that term is defined by 408b2) related to that account (but keep in mind that these contracts may be part of an annuity where separate accounts are used-and thus indirect comp typically received-for which "C" status may occur). 

What needs to be disclosed?

-If the plan will only buy a group annuity contract with a fixed fund from the insurer, and the insurer will not provide any participant level recordkeeping services, then the insurer may not even be a CSP that will need to report under the new 408(b)(2) regs. The only complication will be the reporting of commissions. 

-If the insurer is a "B" CSP, then two things will need to be reported:  (i) a description of any compensation that will be charged directly against the account balance in connection with the acquisition, sale, transfer of, or withdrawal from the product, like surrender charges; and (ii)  description of any ongoing expenses such as mortality and expense charges or contract charges.

What will NOT need to be reported, however, is any "spread" between the crediting rate under the contract and the investment return on the insurers' general account, as the regs specifically exempt "operating expenses" from needing to be reported from a fixed account.

Didn't say it would be easy, but it all does fit together nicely.....

 

__________________

 

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.    

 

Continue Reading...

Retirement plan lawyers, both in house and outside counsel, may well want to take note of Bank of New York Mellon's recently reported troubles related to potentially widespread  and fraudulent use of unfair currency exchange rates in their dealings with unsuspecting state and local pension plans.  If there is a basis for these charges, and f they were as widespread and as sustained as alleged to be, we may have our first prime example of how SOX Section 307 and SEC's "Part 205" Rules (which implement Section 307) can implicate employee benefit lawyers. This is because it would be hard to believe that there wasn't a lawyer somewhere in the organization that shouldn't have been aware of the practice (as these rules apply not only to corporate law staffs, but to lawyers in the business lines as well).

Much of the Sarbanes Oxley Act n 2002 ("SOX") was designed to address many of the corporate abuses arising from the Enron, Tyco and Worldcom fiascoes, and it included enhanced protections for corporate whistleblowers.  Buried within this statute was Section 307, an obscure section which imposed duties upon lawyers who deal with publicly traded companies the duty to "report up" certain corporate malfeasance of which they became aware in their practice.  The challenge with these rules is they seem to clash, in many respects, with the state law rules governing the attorney client privilege. In house counsel have challenging enough circumstances, where their client is the corporation and not the officers who seek their counsel.  This awkward pressure merely increased with the passage of SOX. The stakes became higher, as well: failure to report properly would effectively result in a ban from ever representing a publicly traded client, whether in house or as outside counsel.

I wrote an analysis describing the impact of Part 205 on employee benefit lawyers for ALI-ABA in 2005. In that article, I struggled to describe sensible circumstances where benefit lawyers would be impacted, and where the reporting up obligation would be imposed. This is because the only corporate malfeasance required to be reported under SOX are those which would result in a material impact on the company's financials, and it seemed at the time that it would be one heckuva stretch to reach the materiality standard in our line of work.

BNYMellon really is an eye opener. For manufacturing companies, there really is rare opportunity for the employee benefit lawyer to trip Part 205 obligations, other than issues related to underfunded pension plans and executive stock programs.  BNYMellon, however, demonstrates that this is a very real possibility for attorneys representing financial service companies which do retirement business. Considering the fact the value of retirement plan holdings are some 85% of the value of publicly traded securities in the U.S., and where many companies' financial stake in the retirement business continues to grow, it occurs to me that the potential circumstances where SOX may be implicated will only become greater.

Part 205 requires the establishment of written procedures to insure compliance.   Though pure corporate, tax and M&A lawyers have always been well versed in such matters, financial service companies may want to check these procedures to make sure that retirement law staffs (including those in the business lines) are well within the loop.

For those curious on the nuts and bolts of the operations of Part 205 in the employee benefit practice (and there are quite a few), I invite you to read the ALI-ABA paper.

 

 

 

I am, by some serious training and long experience, a corporate lawyer, having been put through the paces by two incredible general counsels: Jack Hunter of Lincoln Financial Group and Scott Campbell of Kellogg Company. Each of these gentleman made quite a study of their attendant Boards and the rules (both formal and informal)  related to their rarefied status. The expectation was that lawyers  dealing with Board matters clearly understood the proper role and culture of "their" Boards.

Every year end I tend to be reminded of this seemingly mundane work (though it is really anything but!) in private practice, as this tends to be the "busy" season when it comes to corporate actions related to plan amendments and other plan activity. Though it may be too late in the year to be useful this year, there are a few thoughts that come to mind which you may hopefully find relevant the next time a plan amendment crosses your desk:

1.  Boards do not manage companies. It is fundamental corporate law that corporate officers run companies, not the Board. Board members have the fiduciary obligation to the shareholders to oversee management; but they do not step into the role of management.  This means that whatever you are looking for the Board to do, it should be generally "big picture,"  such as adopting or terminating the retirement plan. When adopting the plan, try to make sure that a corporate officer has the ability to amend the plan. In larger corporations, this authority will often be subject to certain limits, such as where the benefit is increased.  

2.  Check the minutes.  If you are unsure of who has the authority to amend the plan, check the past Board minutes (if you can find them) to see who has that authority to amend.

3. Rely upon general authority.  If it is not clear who has the authority to amend, you may find guidance in the general authority granted to officers in the bylaws or enabling resolutions as to who may have the authority to amend a plan, absent a specific grant. If you find yourself needing to go in for a Board resolution, take that opportunity to delegate future amendment authority to an officer.

4. Keep details minimal. I recently saw a board resolution that not only adopted a QACA, but also directed the officers to provide required notices. This is patently unacceptable drafting. The officers should be directed, instead,  to take all necessary actions to execute the decision of the board.

5. That fiduciary thing. Make sure that whatever you are asking the Board to do does not constitute a fiduciary action unless you intend it to. One of the worst things you can do to Board members is to inadvertently cause them to have unwanted fiduciary status. Make sure that the authority to act on behalf of the plan is properly delegated to appropriate officers: in the absence of a clear delegation, one would not generally like the DOL or courts to make a de facto finding of inadvertent ERISA fiduciary status of a Bord member.

Related to this are a number of RMD amendments I have been seeing for 403(b) plans, which purport to amend 403(b) plans for the WRERA rule that allowed RMD waivers in 2009.  Some vendors are presenting these amendments to plan sponsors for their signature by year end, as the vendor may have taken it upon itself to generally waive these requirements for those 403(b) customers with individual contracts.

First, it is not clear that such an amendment is needed because, at least for now, you can still incorporate a lot of things by reference-and the inclusion of 401(a)(9) in a 403(b) document should suffice.

Secondly, though, is the bigger problem.  These these carrier provided amendments purport to amend the entire plan. If there are other vendors in the plan  which did NOT offer the RMD waiver, you actually have a plan document problem on your hands if you adopt this broad amendment.

So, be careful; and may your New Year be fruitful, fulfilling and meaningful. 

 

  

Tags:

DC Plans and the Recession Inequities

Many in the industry saw early on, and tried to address, the terrible disruption caused by the change in 403(b) regulations during the recession. In many circumstances, the transition to the new rules made amounts in many 403(b) contracts unavailable at a time when many teachers and employees of not-for-profit organizations (who were among the hardest hit by the collapse) needed them the most-as loans, hardship distributions, or terminating distributions during times of often grievous financial circumstances.

401(k) plans did not suffer that fate, and I really believe that this recession would have been many times worse had it not been for those defined contribution balances (including 403(b) plans) which acted as a reserve  for those who lost their jobs. I have not yet seen anyone research on those numbers, but the anecdotal evidence appears strong.

Much of the literature being published today talks of how the recession, and the related capital losses within  DC account balances,  speak strongly of the need to preserve that accumulation from future shocks by using those balances to purchase  guaranteed income products. I cannot disagree more strongly.  Many of you know from my writings that I am a strong supporter of guaranteed lifetime income but, I think instead, that the recession demonstrated the huge value of the DC account balance plan: it provided an invaluable cushion to many at a time they needed it most, which would have been otherwise unavailable in a DB type of arrangement. These plans had not  been so widely available during economic shocks in the past.

But there are, and continue to be, huge inequities related to government policies related to the handling of DC plans throughout the recession.

At a time when it was necessary to provide substantial assistance to large financial institutions in many-and now we found out, often hidden-ways (yes, I am a devotee of Gretchen Morgenson and her weekly column in the New York Times), those who were unemployed continued to pay a 10% penalty tax on their defaulted loans and DC distributions which were taken to keep them afloat. The operation of the 10% was, and is, especially cruel, as it is paid regardless of the application of the marginal rate or deductions. So, even if income was so little as to pay little or no tax, the 10% penalty still applied.

The practical effect is that the unemployed were funding, even if in the smallest part, the assistance to large financial orgs which received substantial government support (and, apparently, paid large bonuses from those funds to many of their still employed executives and traders). Regardless of political persuasion, most should have difficulty with this proposition.

Now, as the economy recovers, and hopefully employment returns, many in Congress speak of reducing the amount that can be put into DC plans. Any reduction will have at least two unintended effects which are little mentioned: it will substantially reduce the ability of re-employed participants to rebuild those depleted balance which helped sustain during the recession; and it will seriously impair the ability of all  to build that so-important-cushion for future financially crises.  I would make the case that the smartest thing Congress could do right now is to increase the DC limit, as least for an interim period, to allow balances to be rebuilt.

We do not hear about this much, as it is being suffered by those without a voice: the unemployed and underemployed; those who are being treated so cruelly by the system in which they had, at one time, been invested. But it is all very real, nonetheless.

 

Keeping it simple and sensible is never an easy task. As a matter of fact, it is extremely difficult to do, particularly when dealing with something as complex as 403(b) regulations. This is why the IRS's recent release of its 8955 FAQ's is so striking: in merely two FAQs,  IRS and Treasury provided answers that not only make regulatory sense and further tax administration, but did it in a way which makes sense for 403(b) plan sponsors. And it surprisingly well co-ordinates with positions the DOL has taken.

TE/GE has spent considerable effort in 403(b) outreach over the past decade, even in face of much cynicism about the enhanced regulatory approach to these plans-developing an unusual amount of knowledge about the marketplace in the process. It clearly tapped into this expertise in developing the FAQs. They could not have been written without a number of highly knowledgeable regulators and auditors recognizing a challenge, and being committed to coming up with a workable solution. I have not, in the past, been shy at commenting on a number of different unfortunate choices staff has made when writing and implementing the 403(b) regulations. This time, however, staff impressed.

The following are the 403(b) questions from the FAQ. Even the most difficult part of them-the part about contracts which cease payments in 2008-arises from the requirements of the 8955 itself, but the IRS found a way to integrate it well. 

Does the Form 8955-SSA filed for 2009 by a 403(b) plan sponsor have to report participants who separated from service prior to 2008 with a deferred vested benefit under the plan?

Generally, no. Form 8955-SSA filed for 2009 generally only has to report participants who separated from service in 2008. Thus, participants with a 403(b) contract or account who separated from service prior to 2008 are not required to be reported on the Form 8955-SSA filed for 2009 (or for any subsequent year).However, a participant should be reported on the Form 8955-SSA filed for 2009 if that participant separated from service in a year before 2008 and began receiving payments under the contract or account, but the payments stopped in 2008 before all of the participant’s benefits were paid. See the Instructions for 2009 Form 8955-SSA. See also Question and Answer 2 for an exception that applies even in the case where payments stopped in 2008. 

 

Does a 403(b) plan sponsor have to report all participants who separated from service after 2007 with a deferred vested benefit under the plan?  

No. A plan sponsor is not required to report a separated participant if the participant’s deferred vested benefits are attributable to an annuity contract or custodial account that is not required to be treated as part of the section 403(b) plan assets for purposes of the reporting requirements of ERISA Title I, as set forth in DOL Field Assistance Bulletin (FAB) 2009-02. 

For this exception  to apply, (1) the contract or account would have to have been issued to a current or former employee before January 1, 2009, (2) the employer would have ceased having any obligation to make contributions (including employee salary reduction contributions), and in fact ceased making contributions to the contract or account before January 1, 2009, (3) all of the rights and benefits under the contract or account would be legally enforceable against the issuer or custodian by the participant without any involvement by the employer, and (4) the participant would have to be fully vested in the contract or account. For further information, please see DOL FAB 2009-02, www.dol.gov/ebsa.

 

There are a couple of important nuances in the application of these rules. I invite you to read Conni's analysis in the Thompson quarterly 403(b)/457newsletter, coming out shortly, where she explains them.

Once again, there are several choices TE/GE could have made when developing its position. It used its knowledge and experience to make some pretty good ones here.

ERISA Accounts, Part 2

 I’ve had a number of responses to my “Timing and the ERISA Account” blog of last week: this topic seems to be front and center with a number of folks right now. Given the sorts of comments I received, I thought I’d expand a bit from that initial, almost cryptic, blog.

“ERISA Accounts,” or “Fee Recapture Accounts,” or “ERISA Budgets” are growing in popularity, and are becoming a frequent feature in the 401(k) and 403(b) space. They take two forms: a “credit” with the plan vendor, where the vendor pays up to a certain, agreed-upon amount for plan administrative services as part of the vendor ”package;’ or the “funded” sort where the vendor actually makes a cash payment to the plan, usually based on some sort of revenue sharing schedule. These typically include 12b-1 fees generated from mutual funds, but may also include such things as surrender charge reimbursements or other negotiated items.

In 2007, the ERISA Advisory Council’s Working Group on Fiduciary Responsibilities and Revenue Sharing Practices issued a report which did a nice job on lying out a number of key issues related to this practice. It also recommended that the DOL issue guidance regarding the treatment of revenue sharing received by a plan, specifically regarding the allocation of revenue sharing received by a plan. The DOL has had its hands full in the past few years, so it is little wonder that it has yet to act on providing this guidance.

There all sorts of issues which come up related to these accounts, but the most pressing of them appears to be associated with the funded accounts: the structure of these accounts within the plan (are they like forfeiture accounts?); the method of the allocation of those funds to participant accounts once expenses have been paid; and the timing of those allocations. My previous blog just addressed the timing issue.

The structure of these funded accounts is actually interesting: recordkeepers aren’t generally accustomed to establishing an employer level account, and many recordkeeping systems are not well suited for this function.  The employer level accounts that do exist are typically forfeiture accounts, and the rules governing them can differ from the ERISA Account-which also means that there are a number of different reasons you want to somehow account for ERISA Account deposits differently than forfeitures. These Accounts probably need to be adopted by some formal action of the plan’s fiduciary, in accordance with the authority it is (hopefully) granted in the plan document, which also discuss how they will be used and eventually allocated. Absent that, the general fiduciary authority within the document will need to be relied upon.

With regard to how these funds may be allocated to participant accounts (particularly where there is an “excess” left after certain plan expenses have been paid. Remember, at least in the funded accounts, they cannot be used for settlor expenses. There are interesting prohibited transaction issues as well if the unfunded credits are used for settlor functions), there seems to be a growing sense that ERISA requires that there be some sort of “matching up” of these allocations with the assets which generated them. There is little doubt that this could be an acceptable method of allocation, and there is at least one vendor which I know of which, very nicely,  closely tracks this.

What seems to be getting lost in the discussion related to these allocations is the fundamental rule that participants only have a beneficial interest in the plan. They have no right to any asset, and they only have the right to direct the investment of their accounts because the employer has decided to let them do so instead of the fiduciary. Any funds generated by those investments are due to the plan, not necessarily to any particular participant. Whatever allocation method is chosen by the fiduciary need only be prudently made. It is telling that in Field Assistance Bulletin 2006-01, the DOL stated that (in addressing the allocation of class action settlement proceeds):

“…. a fiduciary’s decision must satisfy the “solely in the interest of participants” standard of section 404(a)(1) of ERISA. In this regard, a method of allocation would not fail to be “solely in the interest of participants” merely because the selected method may be seen as disadvantaging some affected participants or groups of participants. In deciding on an allocation method, the plan fiduciary may properly weigh the competing interests of various participants or classes of plan participants (e.g., affected versus current participants) and the effects of the allocation method on those participants provided a rational basis exists for the selected method and such method is reasonable, fair and objective.”

In short, though “tying back” the ERISA Account payment to the participant account which generates them will generally be considered prudent (though I can see circumstances where it would not be, such as if it were expensive to do so), and can be a good "market differentiator" for a vendor, I think it is a mistake to claim that this is the result demanded by ERISA.

For all these Accounts, there are also a number of interesting 408(b)(2), Schedule C and Schedule A issues with which plan sponsors and vendors must cope-and which I will not address here.

 

__________________

 

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.   


Timing and the ERISA Account

It is not often that one gets to hearken back to the very basic law governing 401(a) plans in addressing an issue, but one of the key questions related to the funding of “ERISA Accounts” provides just such an opportunity. One of the most fascinating of the issues related to these accounts (and there are a number of them coming out of the woodwork as their popularity grows, as well as a number of thoughtful papers being written on these accounts) is the question of how long can the funds can remain in the ERISA Account before needing to be allocated to participant accounts.

We know that the IRS has taken a clear position on the timing of the “spend down” of a forfeiture account, and that funds in the forfeiture account must generally be allocated within the plan year that forfeiture is made (this rule, by the way, would not apply to 403(b) plans). But this is based on 401(a)(8) and the required treatment of forfeitures of contributions under 1.401-7(a)- and the ERISA Account deposit is not a forfeiture. We also know that the DOL has, at least on one occasion, deferred to the prudence standard (see, for example, FAB 2006-1) in managing these accounts.

We do know that a plan document needs to contain language outlining the management of the ERISA Account (and that the Account should be accounted for separately from the forfeiture account), unless the fiduciary is otherwise able to establish procedures under its general fiduciary authority. But what should be the standard under the Code that the plan should adopt?

I think the answer goes back to the “exempt purpose” rules which govern tax-exempt organizations. If I recall my research as a first year associate in Detroit with the good Rasul Raheem, Dr. Willard Holt, Richard Smart and Roland Bessette, under the tutelage of the fine Stan Kirk, the trust of a 401(a) plan is, after all, an exempt organization under 501(a), and the assets of a tax exempt organization are to be used in the fulfillment of the organization’s exempt purpose.  The exempt purpose of a 401(a) trust is, of course, to provide a pension or profit sharing benefit exclusively for employees or their beneficiaries. So, hanging on to the funds in this ERISA Account for too long and not using them for providing this benefit or supporting the operation of the plan would be a failure to use the assets of the "exempt organization" in furtherance of the trust’s exempt purpose. This, ultimately, really leaves you with that “reasonable” period that the DOL suggests to be the standard.

This may also mean that there may not be a standard for a non-ERISA 403(b) plans (as they are neither not subject to 401(a) or the fiduciary standards of ERISA). Any effort to impose a standard would have to be related somehow to the failure to purchase an annuity for an employee. But that may not even matter, for the tax exempt organization would not be otherwise taxed on that amount anyway, and it is not an event which would disqualify the plan.

With 403(b) plans in mind, by the way, make sure the 403(b) ERISA Account is invested in mutual funds or in an annuity account, not just to some holding account at a financial institution. See my blog on “The Trouble With 403(b) Cash.”

I knew that research I first did years ago when trying to figure out how a pension fund worked would eventually turn out to be useful sometime…….

 

 

__________________

 

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.   

 

 

Older Entries

November 8, 2011 — Dodd-Frank and the Annuity Fiduciary Standard

October 28, 2011 — 403(b) Plan Documents: "Planning to Amend," by Linda Segal Blinn

September 23, 2011 — The Uncommon MEP

July 10, 2011 — Zen and The Art of Annuity Regulation, Part 1

June 23, 2011 — Testing of the MEP Waters

June 21, 2011 — IRS Extends 8955-SSA Deadline

June 18, 2011 — 403(b), 8955-SSA and 408(b)2

May 31, 2011 — Healthcare's 403(b) Aggregation Hangover

May 9, 2011 — Securities Rules for Retirement Plans

May 6, 2011 — ERISA and Mom

April 30, 2011 — New IRS Review of Higher Ed's 403(b) Plans: An Expensive and Serious Matter

April 28, 2011 — The Flushing Effect of the 403(b) Connection Between 408(b)(2), Participant Disclosures and Plan Audits

April 20, 2011 — 408(b)(2)/ERISA Compliance and the Security Compliance Professional

April 7, 2011 — 401(k) Distribution Annuities: Its Just Not About "GMWB"

March 18, 2011 — Guidelines For Keeping It Simple Under 408(b)(2)

March 7, 2011 — ERISA Metaphysics, Mysticism and Alchemy: Sales Compensation

February 22, 2011 — 403(b) Terminations Under Revenue Ruling 2011-7: Establishing the Base

February 19, 2011 — Annuity Investment Accounts and 408(b)2

December 27, 2010 — The 403(b) 81-100 Trust Under Rev Rul 2011-1: It Ain't What It Seems

December 8, 2010 — Opportunity Missed: Obscure IRS Shift Provides Contradiction Instead of Clarity for DC Annuities

November 22, 2010 — Participant fee disclosure, 408(b)(2) and the new Schedule C: The 403(b) Impact of DOL's Three-Pronged Approach to Transparency

November 3, 2010 — The REAL Problem With the New 12b-1 Rule: SEC's Treatment of 401(k) Participants as 403(b) Participants

October 1, 2010 — Prudence, not Prescience: A Suggestion for a Fiduciary Standard for DC Annuity Purchases

September 25, 2010 — The 403(b) Unfair Labor Practice

August 7, 2010 — DC Annuity Portability and Asimov's "M.N.C.": What Is Old Is New Again

August 3, 2010 — Insurance Company General Account DC Investments and the 408(b)(2) Conundrum: Balancing Capital, Liquidity and Transparency

June 18, 2010 — ERISA Plans' Ultimate-and Criminal-"Prohibited Transaction" Rule of 18 USC 1954

June 1, 2010 — Plan Distributed Annuities, 403(b) Contracts and the Mandatory Cash-Out Rules: The Saga of Relevant Minutiae Continues....

May 2, 2010 — The 403(b) Church Plan Labyrinth

March 24, 2010 — Advisors Guide to Helping 403(b) Clients Manage Their ERISA Challenges

March 23, 2010 — BNA's "Insurance Guarantees In Defined Contribution Plans" Published

March 8, 2010 — The Rubber Finally Hits the Road: The AICPA 403(b) FAQ Confirms Our Fears

February 20, 2010 — Gems, Quirks, and Quirky Gems in the DOL's Third 403(b) FAB

February 6, 2010 — EPCRS Issues Arising from 403(b) "Disqualification"

February 1, 2010 — The K-12 403(b) Non-ERISA Fiduciary Question: The Growing Turner/Toth Consensus

February 1, 2010 — The Annuity RFI: A Rare, Inter-Agency Treat

January 20, 2010 — The Curious Matter of 403(b) Plan Disqualifiction

January 14, 2010 — CORRECTION BLOG: Annuity PLR Reference Incorrect!

January 6, 2010 — IRS PLR Helps Pave the Way for DC Annuities

December 30, 2009 — The 403(b) Prohibited Transaction

December 23, 2009 — The Trouble with 403(b) Cash; the 403(b) SAR; and Other 403(b) Stocking Stuffers

December 14, 2009 — Continuing the DB Demise Discussion

December 6, 2009 — Using the Third Condition of DOL's FAB 2009-2 to Manage 403(b) Audit Expense

November 29, 2009 — DOL Considering 403(b) FAQ

November 21, 2009 — Private Employer DB Demise Was Inevitable, and Should Not Be Revitalized in Current Form.

November 19, 2009 — Managing the ERISA 403(b) Transition

October 23, 2009 — SEC Chair Warns of Increased Focus On Retirement Market

October 11, 2009 — Addressing Fiduciary Concerns in the Purchase of 401(k) Distributed Annuities: Dealing With The Five "I's"- Part 2, Inflexibility and Inaccessability

September 17, 2009 — DOL Shows Its Swagger; Annuities Pick Up Steam

September 9, 2009 — Pang/Warshawsky vs. GAO: Recent Study Challenges Traditional Thinking About DC Annuities

August 24, 2009 — CPA Group Struggles With 403(b) Rules

July 30, 2009 — Can DC Annuities Reduce Risk of Poverty?

July 24, 2009 — 403(b) Form 5500 Changes May Be Permanent

July 20, 2009 — DOL Avoids A 403(b) Train Wreck With FAB 2009-2. A Learning Opportunity For the IRS?

July 17, 2009 — Addressing Fiduciary Concerns in the Purchase of 401(k) Distributed Annuities: Dealing With The Five "I's"- Part 1, Irrevocability

June 21, 2009 — 403(b) Fiduciary Challenges Demand Applying ERISA in Unique Way

June 3, 2009 — The SEC's and DOL's Cross Agency Retirement Plan "Compliance Waltz"

May 31, 2009 — Do 403(b) Distributed Custodial Accounts Currently Exist?

May 26, 2009 — The Case For "Distributed Custodial Accounts" From Terminated 403(b) Plans

May 12, 2009 — Green Book Further Outlines Automatic IRA Similarity to 403(b)

May 10, 2009 — ERISA and Mom

April 28, 2009 — Annuity Advocate Appointed to Senior Treasury Post

April 26, 2009 — ERISA Section 404(a)(1)(b) Lost in the Shuffle: Whatever Happened to Minimizing Risk?

April 15, 2009 — IRS Announcement 2009-34: The 403(b) Prototype Program Takes Shape In a Well Written Way

April 13, 2009 — The DC Annuity Fog

March 21, 2009 — The Lost Souls of 403(b): 2009 Form 5500, Participant Counts and the DOL

March 17, 2009 — In Defense of Our Colleagues

March 13, 2009 — The 403(b) Regs Unintended Consequence: The Freezing of Loans and Hardships in a Time of Crisis

March 8, 2009 — The 403(b) Regs Experience Exposes "401(x)" Weakness

March 4, 2009 — Marketplace Lessons for Workplace Pensions

March 1, 2009 — Obama's Automatic Workplace Pensions: 403(b) Redux?

February 28, 2009 — The New Generation of Annuities: Balancing Flexibility, Stability and the Pooling of Interests

February 23, 2009 — 403(b) Advisor Checklist

February 20, 2009 — 401(k) Annuities: "Defined Benefit" Guarantees Using a 401(k) Account