A New Look at an Old Friend

About 10 years ago, they were all the rage for companies that had defined benefit (DB) plans. Lots of DB plans were still in surplus, or at least thought they were, and lots of companies still had ongoing DB plans. Something happened in the interim (OK, a few somethings happened), but that's not the point here. Roughly 10 years ago, lots of companies were looking for an ideal way to fund their DB Supplemental Executive Retirement Plans (SERPs), In my opinion, the most effective way to fund these nonqualified (NQ) benefits was through a qualified plan (QP). This strategy has gone by many names, but the most prevalent in the industry has been the QSERP.

On the surface, the QSERP is simple. An executive has a NQ accrued benefit which is usually composed of a gross benefit offset by a QP accrued benefit. The resultant net benefit is what the executive would get from the SERP. In a QSERP, the QP is amended to increase the QP benefit to include some or all of the SERP benefit, thus (because of the offset feature) decreasing the net SERP benefit by an equal amount.

What does this do for the executive? Here are some of the benefits.

• It generally secures the benefit. Of course, if the plan sponsor goes bankrupt, such security is subject to PBGC limits on guaranteeable benefits.
• It takes the benefit out from under the purview of Code Section 409A.
• While the benefit is still in the plan, it does not fall prey to the doctrine of constructive receipt under Code Section 83.
• If the benefit is payable in a lump sum, it can be rolled over into an IRA further deferring taxation.
• The executive can wait until just before his benefit commencement date to make an election as to the timing and form of benefit distribution.
• The benefit is exempt from FICA taxes.
• The benefit is protected in the event of a change-in-control.

And, for the plan sponsor, here are some of the benefits.

• To the extent that the benefit is funded immediately, the sponsor gets an immediate tax deduction.
• Since the plan is qualified under Code Section 401(a), the trust will be exempt from taxes under Code Section 501(a), meaning that the plan assets grow tax-free.
• Payment of the benefit comes from a trust that holds all of the plan assets, not from the corporate coffers, or a far smaller rabbi trust.
• Qualified plans have better optics than do SERPs.

How about for the shareholder? How does a QSERP affect them?

• In every case that I can think of, implementation of a QSERP has been either income-neutral or income-positive.
• The company is less likely to have sudden cash flow requirements.
• From a risk standpoint, it is far easier to use risk management techniques in a qualified plan than in a SERP.

So, why can companies put in these QSERPs? Generally, from a technical standpoint, it goes to two things in the Internal Revenue Code: 1) the nondiscrimination rules of Code Section 401(a)(4) are highly objective; and 2) the combined limits under Code Section 415(e) were repealed.

Yes, that's highly technical stuff. But, suffice to say that it works. For years, I had the extreme pleasure <cough, cough> of teaching nondiscrimination testing to generally younger and aspiring actuaries. One of the things about the testing that I drilled into their heads was this: if you don't pass, you're not trying hard enough. 

Sometimes benefits actually are discriminatory, and there is nothing that any of us can do to change that. But, I have seen some benefit formulas over time that are extremely discriminatory to the naked eye. So, what do we do? We take the employee data and put it in a big pot. We add in the benefit provisions. We stir a bit with the nondiscrimination rules (remember, they are objective; either you pass or you fail.) and out comes a nondiscriminatory plan.

We're late in 2011 now. The funding rules have changed. There are fewer large defined benefit plans, and of those that remain, many are in one state of freeze or another. 10 years ago, there was no 409A. There was no Dodd-Frank, 

There is still lots of merit to this approach. Consider it. Talk to us.

MAP-21 and SERP Funding, Now May be the Time

If you work with US defined benefit (DB) pensions and you haven't been living under a rock, then you are probably familiar with MAP-21, the law passed this summer whose more formal name is Moving Ahead for Progress in the 21st Century. It was positioned as a highway bill, but you are too smart for all that and know all about positioning. Where building highways costs money, lowering corporate deductions for pension plans raises money (or gets scored that way by the Congressional Budget Office). So, MAP-21 included pension funding relief.

In a nutshell, MAP-21 allows plan sponsors to use significantly above-market discount rates in the determination of funding requirements for their qualified pension plans. The trade-off comes in increases in PBGC premiums. But, while the first of these items is optional, the second is required.

So, where am I going with this? If you read the title of this post, you may be wondering.

Flashback to late 2004. Congress passed and a different president signed into law another act supposedly designed to create jobs. This one had a much more in-your-face title, the American Jobs Creation Act of 2004. With that innocuous name, however, came a new section of the Internal Revenue Code, Section 409A that among other things removed distribution and funding flexibility for DB SERPs. Since that time, many executives have wondered how to get their benefits, or at least portions of them, out from under the dark veil of 409A.

For some companies, MAP-21 may have provided an answer.

WARNING: before considering an option such as what I am about to describe, plan sponsors should very carefully consider the underlying risks.

The time may be right to consider a QSERP. Briefly, a QSERP is a means to transfer certain nonqualified benefits to a qualified plan. You can read about them in more detail here.

So, why might now be the right time. MAP-21 has given companies the ability to use higher discount rates in funding their pension plans. This means that any restrictions that might have arisen due to low funded statuses have likely disappeared. So, companies have the opportunity to fund this obligation in a qualified plan without having to fund it all at once.

Risk managers might tell you not to do this and there are good reasons. Paramount among them is that temporary use of above-market discount rates does not change the "true" funded status of a plan.

Other risk managers might tell you that you should do this and you should do it now. Why? Let's consider a simple example. Suppose you have agreed to pay your CEO an additional $100,000 per year (for life starting at age 65) from the SERP. This is over and above what he will get from the qualified DB plan. The present value of that obligation is the same whether that benefit is in the qualified plan or in the SERP. But, in the qualified plan, you get these advantages and many others:

• The benefit will not be subject to 409A
• You could efficiently fund the benefit immediately and generally get an immediate tax deduction for that funding
• That tax deduction may be taken at a higher corporate tax rate than it will be in the future
• When the CEO retires, his benefit can be paid out of a large pool of assets rather than creating a cash flow crunch

This is a complex process and there is much to consider. But, for the right company, now is the time. You'll only know if you are the right company after careful analysis. Ask an expert.

New Pay Limit for Covered Health Insurance Providers and Maybe a Way Around It

Perhaps you like the Patient Protection and Affordable Care Act (PPACA, ACA, or ObamaCare). Perhaps you don't. You are entitled to your opinion. I think we can all agree that it has its good provisions and it has those that perhaps could have been better thought through. One that falls into the latter category is the [relatively] new Code Section 162(m)(6) dealing with the limit on compensation for Covered Health Insurance Providers (I'll refer to them as CHIPs because it's much easier for me to type). In a nutshell, the section and its new proposed regulations limit the deduction for compensation that can be taken by a CHIP to $500,000 annually with respect to any person.

If you want to read the regulation like I did, you can find it here. If you want a good technical overview with the requisite cynicism, I direct you to Mike Melbinger's blog.

If you would like a solution, read on.

In a nutshell, you are a CHIP if 2% of the gross revenues received by your controlled group are from health insurance premiums. Yes, that means that if you happen to be part of a controlled group that contains a health insurer, you are likely a CHIP. Congratulations!

Most of Code Section 162(m) deals with deduction of compensation (as a reasonable business expense). The parts that limit it generally limit it to $1 million, except for CHIPs. And, for CHIPs, and only for CHIPs, the determination of whether an individual's compensation exceeds $500,000 includes deferred compensation earned, nonqualified plan benefits earned, equity compensation awarded, and severance benefits paid. The calculation is not easy, but this post is not about that. If you'd like to know more about the calculation, contact me and I'll be happy to charm you with its details.

I said I have a solution, and for many companies, I think I do. What was left out? Did you notice that qualified plan contributions and accruals were left out? And, for qualified plans, we have an objective set of nondiscrimination rules.

The solution involves a technique often referred to as a QSERP. What this technique does is to take nonqualified deferred compensation amounts and moves them from a nonqualified plan to a qualified plan. In this case, it has lots of advantages:

• Frequently immediate tax deductibility
• Tax-favored buildup
• More security
• Pooling with significant other obligations in a large trust

Most often, QSERPs are utilized in a defined benefit context. But, realizing that many companies no longer have defined benefit plans providing for current accruals, QSERPs can be utilized in a defined contribution context as well. 

Again, the explanation is long and has been covered elsewhere, so I'm not going to bore my readers here, but if you'd like a detailed explanation, contact me directly.

I know the cynics among you will say that this deduction limitation is the right thing to do. For you, I will say that you should have asked Congress to craft the law in a way that doesn't leave creative minds the opportunity to find loopholes.

If you're reading this today (it's a Friday) or even if you're not, have a great weekend whenever that may come for you.

The Big Surprise Gotcha in the Million Dollar Pay Cap

Even those of us who have been hiding under rocks know that late last year, the President signed into law the Tax Cuts and Jobs Act. And, as part of that Act, there was language that amended Code Section 162(m) also known as the million dollar pay cap. After Treasury gave us guidance on those changes in Notice 2018-68, some observers were surprised by a few of the interpretations that the regulators took. One in particular, however, that they didn't quite spell out, meets my criteria for a big surprise gotcha.

I'll come back to that and consider how an employer might get around it, but first some background. Under the old 162(m), deductions for reasonable compensation under Section 162 were limited to $1,000,000 per year for the CEO and the four other highest compensated employees of, generally speaking, publicly traded companies. However, most performance-based compensation was exempt from that calculation and was deductible as it would have been before the cap came into being.

Under the new 162(m), the definition of covered employee has been changed to be the CEO, CFO, and the three other highest paid employees. But, once you become a covered employee, you remain a covered employee. So, by 2030, for example, a company could easily have 25 covered employees. [Hats off to the cynics who know this is a silly example because no law stays in place unchanged for 13 years anymore.] Further, performance-based compensation is no longer exempt.

Like most law changes that affect compensation and benefits, this one, too, has a grandfather provision. Here, the new rules are not to apply to remuneration paid pursuant to a binding contract that was in effect on November 2, 2017, and which has not been materially modified after that date. The keys then relate to what is compensation for these purposes, what sort of modifications might be material, and what constitutes a binding contract.

Compensation is essentially any compensation that would be deductible were it not for the million dollar pay cap. Whether a modification is material remains a bit subjective, but the guidance does specify that cost-of-living increases in compensation are not material, but that those that meaningfully exceed cost-of-living are.

The binding contract issue is the really sneaky one. Your read and your counsel's read may be different, but my read is that if the employer has the ability to unilaterally change the contract, it's not binding. That is problematic.

Consider a nonqualified retirement plan be it a defined benefit (DB) SERP or a traditional nonqualified deferred compensation (NQDC) plan. In my experience, it's fairly common (completely undefined term) to see language that gives an employer the unilateral right to amend said plan, subject to any employment agreements that may overrule. Well, if the company can amend the plan, there would seem to be no binding agreement. And, that means that when that nonqualified plan is paid out to the employee, perhaps none of a large payout will be deductible for the employer. I'm aware of some payouts well into nine figures.

When it's a nine-figure payout, there really aren't great solutions. But, for the typical nonqualified plan, whether it's DB or DC, qualifying some of the benefits changes the treatment. If the benefits can be qualified in a DB plan using a QSERP device, employer funding will be deductible if it is deductible under Section 404. That's far more forgiving and, in fact, it is not at all unlikely that the deductions will already have been taken before the covered employee retires.

Yes, it's still a big surprise gotcha, but don't you prefer a surprise gotcha when it has a surprise solution.

IRS Withdraws Troubling Provision of Proposed Nondiscrimination Regulations

Yesterday, the IRS released Announcement 2016-16 withdrawing parts of the nondiscrimination regulations it proposed at the end of January. Those proposed regulations had troubled many in the defined benefit industry since their proposal for a number of reasons (more below). From the standpoint of the IRS, the troubling part of the proposal addressed some serious abuses by practitioners and the sponsors they consult to. From the standpoint of practitioners, the proposed regulations took an objective test that has been around for quite a while and essentially changed the rules of the game.

I'm going to have to get a little bit technical here before I bring you back to reality. What the proposed regulations would have done was to make retirement plans with multiple formulas show that each formula applied to reasonable business classifications of employees or to pass a more difficult test.

Under regulations that were finalized in 1993 and then amended for cross-tested plans in the late 90s, a rate group in the testing population must have a coverage ratio at least equal to either

• 70% if the plan uses the Ratio Percentage Test to pass minimum coverage tests or
• The midpoint of the safe harbor and unsafe harbor (the midpoint is typically in the 25% to 40% range, but is determined through a somewhat convoluted formula) if the plan uses the Average Benefit Test to satisfy minimum coverage

It is far easier for a rate group to satisfy a lower minimum coverage ratio than a higher one. And, many plans had been designed around satisfying the lower threshold. While the preamble to the proposed regulation said that it was targeting QSERPs, practitioners found that they also were potentially problematic for many plans of small businesses and plans of professional service firms. 

Why would this be troubling? Certainly, among larger corporations, the prevalence of ongoing defined benefit plans has dropped precipitously, but many small businesses and professional service firms have adopted new defined benefit plans (DB) over the last 15 years or so and many of these plans would have found it more difficult or perhaps impossible to pass these proposed rules.

This doesn't mean that DB plans of this sort are out of the woods yet, so to speak. Clearly, the current Treasury Department views that plans of this sort may be abusive in their application of the nondiscrimination regulations, so we could see another effort from the IRS to make the regulations a bit less QSERP-friendly. 

In the meantime, there are some great DB designs that exist for companies that wish to provide meaningful retirement benefits to their rank and file employees. You can learn more about them here.