'

The 403(b) Prohibited Transaction

 I had posted in an earlier blog some of the technical  differences between 401(k) plans and 403(b) plans. One of the more striking differences I did NOT mention was that of the Prohibited Transaction.

Assume a successful insurance agent sits on the Board of a mid-sized tax exempt organization with 250 employees, a Board which also serves as the Plan Administrator of its ERISA 403(b) plan. The Board has just conducted a review and chosen a new vendor to handle all of the new tax rules while also complying with its fiduciary obligations. The Board selected a 403(b) vendor which is an insurance company that the agent/board member has been appointed to do business with. That agent/board member took all the (often excruciating) steps necessary to make sure that no commissions are paid to her on the purchase of those annuities by the charity's plan.

The agent opens her quarterly bonus statement from the insurance company and finds, to her great dismay, that the insurance company has paid a retention bonus on the charity's 403(b) plan annuities. She immediately calls a fellow Board member, who also happens to be the CPA which will be auditing the charity's plan. She wants to know whether this is a problem, and how should she fix this. The CPA is now concerned, because the audit may need to address this circumstance.

Assuming that the payment of the retention bonus is a prohibited transaction  (there are circumstances in which it may not be), and setting aside the issue of how to correct something like this (that's why people hire lawyers like me), how does the CPA approach this?

The first, and most important, point is a 403(b) plan is NOT a plan defined under IRC Section 4975(e)-which means that 4975 and its related excise taxes does NOT apply to 403(b) plans. There is no "disqualified person;" there is no "non-exempt transaction" that is reportable under Schedule G, Part III of the Form 5500; and no Form 5330 needs to be filed.

This also means that, by virtue of not being covered by 4975, that it is subject to ERISA's Civil Penalties under ERISA Section 502(i), which relate to the Title 1 Prohibited Transactions under ERISA Section 406. The 403(b) plan is NOT exempt from this section. But there is currently no way to report this transaction to the DOL, which "may" asses the civil penalties thereunder.

This may put the CPA in a bit of a quandary, particularly if the potential prohibited transaction penalty is substantial because of the size of the transaction or because of the number of years it went uncorrected. Until the matter is resolved with the DOL, and a decision made whether to asses the penalty, this may be carried as a sort of open liability on the audit report. ... yet another 403(b) regulatory issue to be resolved.

Preview

For a heads up, I thought I'd preview with you a few of the matters I expect to address in the early part of the new year:

  • Part 3 of the Annuity "Fiduciary Concerns." Yes, there is a "Part 3" on the boards. This will cover "Invisibility", which is really a discussion of sales charges, and "Immobility,"which is a discussion on Portability.
  • Annuity Transparency.  How to make disclosures relevant.
  • Complex Prohibited Transactions. There will be a few blogs on how the prohibited transaction rules apply in large, complex financial organizations.
  • A Schedule H and C "walkthrough" for the 403(b) plan
  • ERISA Section 502(a)(9), the Plan Distributed Annuity and 403(b).

And a few other interesting tidbits.  Keep watching.....

A Final Reflection

The year's end always brings the opportunity to reflect again on important matters. I would like to share with you a quote from Learned Hand, eminent jurist of the federal bench in the early 20th century. I came across this quote some 30 years ago, as I was deciding to go to law school, and have carried it with me since. In a corporate world where the staff "common denominator" often seems to be fear, where ideas are much at risk, this takes on particular relevance:

 Our dangers, it seems to me, are not from the outrageous but from the conforming; not from those who rarely and under the lurid glare of obloquy upset our moral complaisance, or shock us with unaccustomed conduct, but from those, the mass of us, who take their virtues and their tastes, like their shirts and their furniture, from the limited patterns which the market offers.

Learned Hand June  2, 1927, commencement address at Brym Mawr College. Bryn Mawr Alumnae Bulletin, Oct, 1927.

To all, wishing a healthy and fulfilling new year.

 

_________________

 

 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.  

 

403(b) devotees often speak of the continuing, and significant, number of technical differences between 403(b) and 401(k) plans. The following lists a few of the differences not given a lot of attention, a sort of holiday stocking stuffer:

Handling 403(b) cash.   Handling cash is much more challenging under a 403(b) plan than under the 401(k) plan as pointed out to me a little while back by David Walters of Bodman LLP. A 401(k) deposit can sit in some sort of cash account (sometimes for lengthy periods of time) in the trust while a variety of administrative issues related to the handling of that cash can be resolved. Not so with 403(b) plans. First,  403(b) cash needs to put in a "custodian account  held"  registered investment company share or into an annuity contract to maintain its 403(b) status. It can't just sit around in some sort of custodian owned cash account for more than a very short time.  Secondly, 403(b) investments are registered products which are subject to strict SEC rules on timing of deposits and the return of funds received "Not In Good Order." 403(b) custodians beware!

Notice of restrictions on distributions.  In an example of the quirkiness of the 403(b) rules, the SEC issued a No-Act letter in 1988 to the ACLI regarding the distribution restrictions on 403(b) annuity contracts. It appears that the 403(b)(11) distribution restrictions could have run afoul of the distribution requirements under the Investment Company Act of 1940 (403(b) investments being registered securities subject to these rules) but for this issuance of this No Act. 

The 403(b) SAR.  ERISA 403(b) plans have always had to file an SAR. They were very silly, not looking at all like a 401(k) SAR, with very little information on them because of the minimal 5500 reporting requirements. Now, those 403(b) SARs will be substantial. Those who have "standard" 403(b) forms will need to modify them to look like the 401(k) standard.

Non-merger.  It was conventional wisdom in the past, as Kurt Lawson  of Hogan and Hartson notes, that 403(b) plans and 401(a) plans could not be merged, though this surely would be a handy planning tool to have today to manage all of these 403(b) issues. The 403(b) regs confirmed this "conventional wisdom" in 1.403(b)-10(b)(1)(i).

Employer Approval.  I find it fascinating that, with all the back and forth going on between employers and vendors on "approving" hardships and loans and the like that, unlike 401(k) plans, the 403(b) regs do not actually require employers to approve such things. The 403(b) "Plan Administrator" is really a much different animal than the 401 (k) Plan Administrator. It really is more like a compliance coordinator.  

A Personal Thought

My friends and colleagues likely do not think of me of being particularly religious or spiritual, even given my 12 years of Catholic schooling and reading more than my fair share of the likes of Lao Tzu, William Stringfellow (lawyer and theologian),  Kahil Gibran,  Eckhart Tolle and others. But this holiday season causes us all to reflect, regardless of one's religious tradition, on the magnitude of personal tragedy we are witnessing today. NPR reported the other day that 1 in 7 U.S. families are struggling putting food on their tables. 

So let us be thankful for what we do have and for those incredible folks who give their hearts-mostly without thanks or recognition- to righting the indignities and inequities of this time. And let us  humbly remember those who are much less fortunate than us, as all of the traditions teach us that-yes-we are all our brother's keeper.

 

 

 ______________

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.  

 

 

Continuing the DB Demise Discussion

I blogged a couple of weeks ago on the DB demise because of what I was seeing my current work on DC annuities, triggered by an interesting e-mail discussion string between fellows of the American College of Employee Benefits Counsel

But then the PBGC held a 35th anniversary forum shortly thereafter, extolling the idea of revitalizing the current DB system.  I thought this made it an opportune time to further the discussion.

The December 7 Forum on DB plans seem to hit it mostly right  in its calling the attention to the fundamental value of employers providing "guaranteed income for life" to employees. The National Institute on Retirement Security also reported on the meeting, noting the  critical role of Defined Benefit Plans, calling them the "Real Deal." The NIRS has also published its vision with which one can hardly argue. Under a high quality retirement system retirement system: 

  • employers can offer affordable, high quality retirement benefits that help them achieve their human resources goals;
  • employees can count on a secure source of retirement income that enables them to maintain a decent living standard after a lifetime of work;
  • the public interest is well-served by retirement systems that are managed in ways that promote fiscal responsibility, economic growth, and responsible stewardship of retirement assets

But here's where the problem lies. Juxtapose those statements with the following quote from "The Black Swan," by Nassim Nicholas Taleb, Random House, 2007:

"Consider the following sobering statistic.Of the five hundred largest U.S, Companies in 1957, only 74 were still part of that select group, the Standard and Poors 500, forty years later. Only a few had disappeared in merger; the rest either shrank or went bust." p.22

This where the PBGC, the NIRS and Pension Rights Center (which also presented at the conference) have it all wrong: the traditional DB plan does not, and will not, meet these laudable goals if you rely upon the private employer for the financial wherewithal to insure that the funding and fund management will be adequate. Plan sponsors can be terribly conflicted, with their own corporate financial needs creating economic pressure to engage in some sort  dangerous "creative accounting" in the management of these plans- which we have all too often seen in the past.  I am tempted to argue that public plans do not have this problem, and that they should get a "bye" on this concern. But think again. Many state and local governments are in serous trouble because of a disturbing lack of financial discipline, as they have not really had to "pay as you go" when promising very expensive benefits. Are not these promises really of the most cruel kind, when we find the money to pay for them really is not, nor ever can be, there?

The current DB system is premised on the notion that a private employer can more cost effectively provide this benefit. Logically, this cannot be true because of the lack of sensible pooling even in the largest employers. Some employers will be able to do so today because of their current demographics, but many cannot-and even those who can may find themselves in a bind in a decade or two. The only potential cost savings is in the profit charge on this guarantee issued by an insurer.

In effect, the system believes that it can do a better job at longevity risk management than regulated insurance companies, and to get that insurance for, in effect, free. When all is said and done, it is likely far from free. We are seeing the effect of the fallacy today, with only 19,000 DB plans now being covered by the PBGC.

So if the system REALLY needs a guaranteed lifetime benefit based upon employer sponsorship, one under which employers have the ability to choose the benefits (and thereby control the cost),  but one under which the employees should not be exposed to the vagaries of foolish business decisions of their  employers' senior management, what IS the answer?

I truly believe the answer lies in a private insurance system which provides Annuity Transparency, in annuities purchased through the employer sponsored system.  I'll talk about this on my next blog. For now, though, its back to the ski slopes of Quebec.... 

A footnote, added 12/21: Gretchen Morgenson reports in the Sunday NY Times  on a multi-billion dollar failure in the Alaska pension system, caused in large part by the alleged error of Mercer.  Again, my point: non-regulated institutions are ill-equipped to manage DB plans, particularly large ones. Had Alaska purchased insurance, the risk of error would have be borne by a well capitalized, highly regulated expert organization.

 

 

 

 

 

The DOL issued FAB 2009-2 back in July, in response to the concerns of employers and investment providers that in many cases they would not be able to obtain the information necessary related  to a number of "old" 403(b) contracts and accounts for the expanded Form 5500 required for 403(b) plans beginning with the 2009 plan year. Moreover, even in cases where some annual reporting with respect to the contracts would be possible, the DOL recognized that compliance efforts involved in including these contracts in the financial statements would be substantial and expensive.

The FAB  was not uniformly well received initially, many expressing the thought that the relief was illusory at best.  Now that we have had some time for the FAB to settle in, and now that parts of the market are beginning to try to identify past contracts and "classify" what to do with them, the usefulness of the FAB becomes more clear. 

The FAB allowed contracts to be excluded from an audit if they met the following 4 conditions:

  1. were issued prior to 1/1/09,
  2. all contributions ceased prior to 1/1/09,
  3. all rights under the contract are"legally enforceable" against the insurer or custodian by the individual owner "without any involvement of the employer," and
  4. the mounts in the contract were fully vested and non-forfeitable.

The real key to making the FAB work for the employer in keeping auditing costs down is in the sensible application of the FAB's 3rd condition.  I would suggest that applying it consists of two parts. First, use a reasonable effort to determine and find contracts that were related to the plan at some time in the past and, secondly, making a reasonable effort to determine whether or not the rights under those contracts are "legally enforceable" by the individual.

Finding contracts

Establish a reasonable (meaning not "perfect") method to use to find what contracts might possibly be part of your plan. Review the employer records to determine (to the best of your ability) which employees made contributions to which vendors over a reasonable period of time (perhaps the ERISA 6 year recordkeping requirement?).  Do the best you can, document it, and convince your CPA that a reasonable effort should do. 

Legally Enforceable 

From a purely legal viewpoint, this should be "easy." Heck, just get a copy of all those contracts issued over the past (6 years?) and read them. Right? Two problems, of course:

  • Go ahead. Try finding them. You won't find them. This is in part because insurance companies don't typically keep actual copies of contracts. Instead, they keep records of the application, plus the "form number" they issued to the individual. Which means when you try to ask for a copy, you'll just get an assembled form-assuming the company would give the employer (who doesn't own the contract) a copy anyway.
  • Then try reading it. I dare you.  Have you ever tried to read an annuity contract?Trying to determine whether or not rights are solely enforceable by the individual will be a difficult task, and one which an answer to this question may never be readily findable.

There may be a way a reasonable method or two to try to divine this answer.  For current vendors, for example, the task is a simple one (of course, nothing is turning out to be simple nowadays in this world): have your vendors give you a list of all the contracts to which they seek your approval for something like loans or distributions.

For past vendors, this is where the gold mine should be. See if you have heard from any of those past vendors for which you have compiled a list (see "Finding Vendors"). It may well be reasonable to assume that, had you not heard from them on your former or current employees, that those employees rights are being enforced without your involvement.

Tougher questions arise when, under 2007-71, you have excluded contracts from your plan.  Can these contracts be excluded for Title 1 reporting purposes? Vendors have taken a hard line on these contracts, and are submitting all sorts of decisions to employers for approval, even where the employer has advised them those contracts are not part of the plan-and many times these approvals are demanded in spite of contract language NOT requiring employer approval.  

A number of employers have decided that they were subject to ERISA just this year, because of the press of the tax regulations. One needs to consider (after consulting a lawyer or accountant) whether any of the old, past contracts under such circumstances would need to be counted.

Finally, this business really is only the tip of one of those melting Antarctica icebergs. Ultimately, the lawyer, accountant and employer need to sit down and review the employer's situation, and make a case amongst themselves for the most reasonable approach. Remember, the DOL's approach right now is accommodative. It is not trying to bankrupt charities through the crushing cost of unreasonable audit requirements.

 

 

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.