Sourcing of Stock Option Income for U.S. Tax Purposes

The determination of which portion of stock option compensation is U.S. source income is addressed under the sourcing rules of Code section 861, which is not as neighborhood that I frequent as an employee benefits lawyer.

The general rule is, “The source of multi-year compensation is determined generally on a time basis, as defined in paragraph (b)(2)(iii)(E) of this section over the period to which the compensation is attributable.”  Thus, you would multiply by a fraction, A/B where:

•  A =number of days of performance of labor or personal services in the U.S. and
•  B = total number of days of performance of labor or personal services.

The regulations provide, “In the case of stock options, the facts and circumstances generally will be such that the accountableperiod to which compensation is attributable is the period between the grant of an option and the date on which all employment-related conditions have been satisfied (the vesting of the option).”  (Treas. Regs. section 1.861-4(b)(2)(ii)(F).)

Thus, you’re looking at the period from grant to vesting and not the period from grant to exercise.  This seems like good news because the grant and vesting dates should be somewhat predictable and knowable in advance.

Not all states have adopted this rule, obviously, but there is a lot of logic to this rule.

Transitional Reinsurance Contributions

In a fit of uncharacteristic diligence (hey, things are slow), I read the final regulations issued on March 11, 2013 about the transitional reinsurance contributions.  A few notes that will be most relevant for self-funded plans follows

A.     Reinsurance Contributions

The pie-in-the-sky idea here is that group health plans are going to subsidize the individual market and cushion the shock for three years as the individual market becomes more robust and covers more people.  I do not  know anyone who is willing to bet that the reinsurance contributions will really go away after three years.

B.      Contributing Entities for Purposes of Reinsurance Contributions

A “contributing entity” is generally a group heath plan or a health insurance issuer.  More specifically, a self-funded group health plan is included and is ultimately responsible for payment of reinsurance contributions, although that responsibility can be delegated to a TPA.  Some plans are, predictably, excluded, and they include:

  • Stand-alone vision plans;
  • Stand-alone dental plans;
  • Cancer or other single disease insurance;
  • Expatriate coverage (won’t the multi-national corporations be glad!);
  • Plans limited to prescription drug coverage;
  • Employee assistance programs, wellness programs and disease management programs that do not constitute major medical coverage;
  • Flexible spending arrangements;
  • Health savings accounts;
  • Integrated health reimbursement accounts; and
  • Other coverage excepted from Section 2711 of the Public Health Service Act such as treatment at on-site medical clinics or coverage supplemental to Medicare or TRICARE.

Instructive here is the definition of major medical coverage that is provided in the preamble, “… for purposes of the reinsurance program only, our view is that major medical coverage is health coverage, which may be subject to reasonable reasonable enrollee cost sharing, for a broad range of services and treatments including diagnostic and preventative services, as well as medical and surgical conditions provided in various settings, including inpatient, outpatient and emergency room settings.”  (78 FR at 15456.)

C.     Calculation of the Reinsurance Contributions

Each contributing entity must pay a reinsurance contribution that equals A x B, where

  • A = number of covered lives of reinsurance contribution enrollees during a benefit year, and
  • B = the contribution rate for the applicable year.
    1.        1.     Determining the Number of Covered Lives

The number of covered lives is determined in a manner that is almost the same as the determination used for the Patient Centered Outcomes Research Institute, or “PCORI” fee.  Self-funded group health plans can use one of four methods:

  • “Actual Count Method” – an actual count method for the first nine months of the benefit year;
  • “Snapshot Count Method” – adding covered lives on any corresponding date in the first three quarters of the year and dividing by the applicable number of dates; provided, however that the dates used must fall within the same week of the quarter.
  • “Snapshot Factor Method” – on corresponding dates in the first three quarters of the calendar year, adding participants with self-only coverage on a given date to participants with other than self-only coverage multiplied by a factor of 2.35 and dividing by the total number of dates on which the counts were made
  • “Form 5500 Method” – using the sum of participants at the beginning of the plan year and the end of the plan year as reported on the Form 5500 “for the last applicable time period”.
    • For plans with self-only coverage, this sum can be divided by two.
    • For plans with other than self-only coverage, the sum will be used.
    • According to the preamble, the “last applicable time period” is the last plan year. (See 78 FR at 15463)

For plans that use one of the first three methods, only the first nine months of the year are considered because of administrative requirements to assess fees before the year end.

Note that this version of the snapshot method is slightly looser than the method described in the final PCORI rule, which requires that the dates fall within three days of each other, but if dates satisfy the PCORI rule, then they should work for purposes of this rule as well.)

In determining the number of covered lives, the Medicare secondary rules will apply.  This is most significant for retiree coverage, which is generally subject to reinsurance contributions unless a general exception applies.  (78 FR 15457.)

The example in the preamble (78 FR 15456) is helpful.  It explains that a 68-year old employee enrolled in a plan for which Medicare is a secondary payer would be counted, but a 68-year old employee in a plan for which Medicare was primary would not be counted.  (78 FR 15456.)  Similarly, individuals who are Medicare-eligible due to end-stage renal disease may count depending on whether Medicare is the primary or secondary payer.

In reducing the number of covered lives to reflect participants for whom the plan is a secondary payer to Medicare, any reasonable method can be used.  The preamble states, “In order for a contributing entity to determine its enrollment count as required under § 153.405 while taking into account enrollees for which the employer group health coverage is secondary to Medicare under the MSP rules, we clarify that the contributing entity may use any reasonable method of estimated the number of percentage of its enrollees.”  (78 FR 15456)  The preamble continues that the entity may calculate the percentage of participants for whom Medicare is primary on each date used in the snapshot method or may calculate the total enrollment for which coverage is secondary on the last day of the third quarter.  This doesn’t quite sound like “any reasonable method” to me, as actual counting on specific dates is still required.  However, it suggests that there will be a little bit of flexibility regarding which date the MSP counts must be conducted.

For plans that include multiple components – for example a group health plan that is major medical coverage combined with a wellness plan and an employee assistance plan – participants who do not have major medical coverage can be excluded from the count of covered lives.

      2.       National Contribution Rate

The national reinsurance contribution rate is the sum of (1) a reinsurance pool amount of $10 billion for 2014, $6 billion for 2015 and $4 billion for 2016 plus (2) an amount payable to the U.S. Treasury of $2 billion for 2014, $2 billion for 2015 and $1 billion for 2016 plus (3) an administrative cost amount.  This sum is divided by the expected number of covered lives for reinsurance contribution purposes to arrive at a per capita national reinsurance contribution rate.

As a practical matter, this is not something a self-funded plan controls or influences.  The rate is simply handed down from on high, and the rate for 2014 is $5.25 per month.  However, for administrative reasons, it’s paid as an annual rate of $63 per covered life.

D.     Payment of Reinsurance Contributions

Each contributing entity must submit an annual enrollment count to HHS by November 15 of 2014, 2015 and 2016.  The entity will then be required to pay the reinsurance contributions at the national rate plus any applicable state rate. (Note, that I don’t really understand how the state rates apply – does a self-funded plan that is exempt from state insurance law still have to pay an additional state rate?)

HHS will notify covered entities within 30 days of submission of enrollment counts or by December 15, whichever is later.  So a covered entity that submits its count before November 15 could receive its notification before December 15.  (Really, why does HHS have to notify contributing entities?  If people are smart enough to calculate the number of covered lives, then multiplying by $63 is surely something that we could trust them to do without help from HHS?)

As for how the annual enrollment counts and payments will be submitted, stay tuned, “HHS will provide details on the submission of enrollment counts and contributions in future guidance.”  (78 FR 15465.)

The good news is that these fees are permissible plan expenses under Title I of ERISA.  (See 77 FR 73198, fn 56.)  The IRS has also advised in its FAQ for tax guidance under the Affordable Care Act that the fees can be deducted as ordinary and necessary business expenses.  (See www.irs.gov/uac/Newsroom/ACA-Section-1341-Transitional-Reinsurance-Program-FAQs .)

Speaking of PCORI Fees

I was talking to some other ERISA lawyers today (frequently a humbling experience given how smart some folks are and how much they are into the technical issues), and the PCORI fee came up.  I’ve had to go back and read the Final Regulations, issued December 6, 2012 (77 FR 72721) and here are a few thoughts:

There are two fees:  one is imposed on insured plans under Code section 4375, and the other is imposed on self-insured plans under Code section 4376.

CALCULATION OF THE FEE

The fee is equal to the average number of covered lives covered during the plan year (calculated using one of the acceptable methods) multiplied by the applicable fee for the year.

For 2012, the fee is $1 per covered life, and it doubles to $2 per life for 2013.  After 2013, it increases each year by the percentage increase in the projected per capita amount of National Health Care expenditures most recently released by HHS before the beginning of the Federal fiscal year.  (Treas. Regs. section 46.4376-1(c)(3) for self-funded plans and Treas. Regs. section 46.4375-1(c)(4) for insured policies.)

Plans Covered:

  • Both group health policies and self-insured plans, including with respect to COBRA coverage.
  • HRA’s that are integrated with an insured plan are subject to separate PCORI fees, but if they are integrated a self-insured plan with a calendar year, they are not.  (See 77 FR 72724-5.)
  • Retiree only plans are subject to PCORI fees. (77 FR 72723.)
  • Flexible spending arrangements that do not meet the requirements for being excepted benefits under Code section 9832 and Treas. Regs. section 54.9831-1(c)(3)(v) are subject to PCORI fees.  (77 FR 72725.)

Plans NOT Covered:

  • Flexible spending arrangements that meet the requirements for being excepted benefits.  Treas. Regs. section 5431-1(c) describes excepted benefits and paragraph (3) provides, “In addition, benefits provided under a flexible spending arrangement are excepted benefits if they satisfy the requirements of paragraph (c)(3)(v) of this section.”  Paragraph (c)(3)(v) provides that FSA’s are excepted benefits if they meet two requirements:
    • Other group health plan coverage is made available for the year to the class of participants by reason of their employment AND
    • The maximum benefit payable for the year can’t exceed two times the participant’s salary reduction or, if greater, the participant’s salary reduction plus $500.
  • Group policies or self-insured plans designed to cover primarily employees working and residing outside of the United States.
    • An issuer or plan sponsor may rely on the most recent address on file for the primary insured and may assume that the primary insured and his or her spouse and dependents all live at the same address.

CALCULATION OF COVERED LIVES

Issuers can choose any of four methods: (1) actual count, (2) snapshot, (3) member months and (4) state form.  Self-funded plans could choose any of three methods: (1) actual count, (2) snapshot or (3) Form 5500.  I am most interested in the three methods available to self-funded plans, and so this post focuses on those.  A few months ago, I didn’t know of anyone who was planning to use any method other than the Form 5500 method.  Today, however, a number of employers expressed interest in the snapshot method.  I have not yet encountered anyone interested in using the actual count method, which seems bizarrely cumbersome.

For the first year, plan sponsors of self-funded plans can use “any reasonable method” for determining participant lives.  In addition, issuers using the snapshot method can start counting only quarters that begin on or after May 14, 2012, which is the date the proposed regulations were published.

Actual Count Method (which no one is using):

  • The actual count method requires adding the total covered lives for each day during the plan year and then dividing by the number of days in the plan year.
  • Why is this even an option?  Are there any employers or plans that can come up with an actual count on a daily basis?

Snapshot Method:

  • The snapshot method requires a count of covered lives on one or more dates during each calendar quarter.  (Although in 2012, using only the last two calendar quarters of the year seems acceptable.)
  • Covered lives on each date are added and then divided by the number of dates to determine average lives covered for the plan year.
  • There are two ways covered lives can be counted:
    • Snapshot factor method – Covered lives for each date equal (1) the number of participants with self-only coverage plus (2) 2.35 times the number of participants with coverage other than self-only.
    • Snapshot count method – Covered lives for each date equal the actual number of lives covered on the designated date.
    • The same number of dates must be used each quarter.
    • Each date must be within 3 days of the comparable date in the other quarters.  Thus, January 2 and April 1 could be paired as two dates in successive quarters, but March 31 and April 1 could not be paired.

Form 5500 Method:

  • The Form 5500 method determines the average number of covered lives based on participants reported on Form 5500.
  • For a plan providing exclusively self-only coverage, the number of covered lives equals the number of participants reported at the beginning plus the participants at the end of the plan year, divided by two.
  • For a plan providing coverage other than self-only coverage, the average number of covered lives for a plan year equals the number of participants reported at the beginning of the plan year plus the number of participants reported at the end of the plan year.

REPORTING AND PAYMENT DEADLINE

The fee must be paid by July 31 of the year following the last day of the plan year.  The deadline for payment is not extended for plan sponsors who are filing their Form 5500 after July under an extension.  This is significant because the final regulations do not provide a way to correct inadvertent errors, “One commenter suggested that the final regulations provide that plan sponsors may correct, without penalty, inadvertent errors if correction is within a specified period or if the error is de minimis.  The final regulations do not adopt this change and, therefore, do not explicitly address corrections.”  So there is no opportunity to file based on an estimated Form 5500 count and then “true-up” at the time the actual Form 5500 is filed.

Payment is on Form 720, “Quarterly Federal Excise Tax Return,” but at this point, the form has not been updated to take the fee into account.

The fee is assessed on a plan sponsor basis.  However, if the group files a consolidated tax return, it is not clear how each plan sponsor would report and pay separately.  One of the other practitioners had heard an employee of the Service state that the fee could be paid by the parent company, and that records of the plans should document that the fee was paid on behalf of other plan sponsors by the parent filer of the consolidated return.  That at least seems rational, which is a definitely not true of lots of things under the Affordable Care Act.

 

Advance Notice of Funding-Based Benefit Restrictions: Examples from the Real World

I keep encountering situations where nervous employees want to know if they will receive advance notice if funding-based benefit restrictions will be imposed.  While I’ve looked at the statute and guidance (see the preceding post) before, today, I’ve had the time to check out some examples from the real world:

A)      It looks like the General Dynamics pension plan was subject to lump sum restrictions in 2011, and they communicated the restrictions in advance to employees with a very thoughtful FAQ, which is available here: http://www.mygdlumpsum.com/Documents/GD%20Ee%20FAQ.pdf  Thus, there is clearly some precedent for well thought-out advance notice of benefit restrictions, and the July 2012 IRS guidance does not expressly prohibit taking this type of approach.  

B)      The Kodak pension plan was also subject to lump sum restrictions as a result of Kodak’s bankruptcy.

  1. Kodak produced a letter to participants stating that the funded status of their plan for 2012 was around 73%, and they were not taking advantage of MAP-21 funding relief to increase their funded status so that they could pay lump sums.  Their web site for former employees is here: http://www.kodak.com/ek/US/en/Kodak_Transforms/Former_Employees.htm
  2. Kodak did not take advantage of funding relief because, if they had, the PBGC would have taken over their pension plan, which they determined would result in more harm to participants than the decision not to take advantage of funding relief.  Thus, this is an instance where the plan fiduciaries made a decision that resulted in lump sum restrictions because they believed that decision was in the best interests of all participants. 
  3. This highlights the fact that under certain circumstances (in this case bankruptcy), negotiations with the PBGC may play a significant role in the decisions made by plan fiduciaries.
  4. Note that Kodak participants do not appear to have received advance notice because the lump sum restrictions were imposed as a result of bankruptcy, and employees typically would not receive advance notice of a corporate bankruptcy filing.

C)      Finally, here is a BP communication that was issued following the Macondo disaster: http://hr.bpglobal.com/LifeBenefits/Assets/Documents/pq/BP-Pension-Plan-FAQ.aspx

  1. BP’s plan was funded at over 100% as of January 1, 2010, and BP therefore communicated that lump sums could be paid through September 1, 2011.
  2. BP did not make any statements about whether advance notice of benefit restrictions would be given to participants, although the existence of this communication leads me to believe that they were receiving all of the questions you would expect.  They (perhaps wisely) have not addressed any questions regarding advance notice or “what happens if…”

These communications are tailored to specific circumstances and suggest that the plan fiduciaries are trying to take actions that make most sense for their participants in light of their specific facts and circumstances. 

In reading these communications, I was struck by how well-crafted the communications are.  The plan administrators seem well-advised and appear to have thought through difficult (even painful) issues with care, and they have then communicated carefully and deliberately.  

I think my conclusions are unchanged, and that the best approach would be an answer to the question of whether employees will receive advance notice that is along the lines of, ”We don’t know currently what facts and circumstances (including subsequent law or guidance) might look like if our plan were ever subject to funding-based benefit restrictions, and therefore we do not know what the plan administrator would decide regarding advance notice of funding-based restrictions.  There is not a single course of action that is appropriate in all cases, but our plan administrator takes [his/her/its] duty to plan participants and beneficiaries very seriously.  If our plan were ever to become subject to funding-based benefit restrictions, our plan administrator would carefully consider all relevant facts and circumstances and then make the decision [he/she/it] believes is in the best interests of participants and beneficiaries.”

Of course, this is not the perfect assurance that the employees want.  Does anyone else have different or better thoughts?  I would love to make my clients really happy with my answers, and that is not happening as much as I would like lately.

Can a plan sponsor provide notice to plan participants in advance of the date when AFTAP-related benefit restrictions on lump sum benefit payments will take effect?

Section 101(j) of ERISA provides:

(j) Notice of funding-based limitation on certain forms of distribution—The plan administrator of a single-employer plan shall provide a written notice to plan participants and beneficiaries within 30 days—

(1)    after the plan has become subject to a restriction described in paragraph (1) or (3) of section 206(g),

[Note: Section 206(g)(1) is the limitation on “unpredictable contingent event benefits where the AFTAP is less than 60% or would be less than 60% when the unpredictable contingent event is taken into account.  Section 206(g)(3) is the limitation on “prohibited payments”(i.e., lump sums)  where the AFTAP is less than 60% or the plan sponsor is in bankruptcy and the 50% limit where the AFTAP is between 60% and 80%.]

(2)    in the case of a plan to which section 206(g)(4) applies, after the valuation date for the plan year described in section 206(g)(4)(A) for which the plan’s adjusted funding target attainment percentage for the plan year is less than 60 percent (or, if earlier, the date such percentage is deemed to be less than 60 percent under section 206(g)(7), and

[Note: Section 206(g)(4) is the prohibition on future benefit accruals where the AFTAP is less than 60%.  Section 204(g)(7) addresses the presumptions that apply if no actuarial certification is received by the 4th month or the 10th month of the current plan year.]

(3)    at such other time as may be determined by the Secretary of the Treasury.

[Note: See discussion of IRS Notice 2012-46 below for other times that Secretary of Treasury has determined that a notice under Section 101(j) should be provided.]

The notice required to be provided under this subsection shall be in writing, except that such notice may be in electronic or other form to the extent that such form is reasonably accessible to the recipient. The Secretary of the Treasury, in consultation with the Secretary, shall have the authority to prescribe rules applicable to the notices required under this subsection.

Thus, the statute clearly provides that the notice must be provided after the plan has become subject to a benefit restriction.  There is nothing in the statute that addresses whether a notice or other information could be provided before a benefit limitation takes effect. 

The IRS has issued Notice 2012-46, dated July 23, 2012 to provide guidance regarding the notice requirement under ERISA 101(j).   Q&A-1 in the notice basically repeats the statute and provides that a Section 101(j) notice is required to be provided “within 30 days after the date on which the plan has become subject to a limitation” on either unpredictable contingent event benefits or prohibited payments.  Q&A-4 explains that “the date on which a plan becomes subject to a limitation on prohibited payments” is “the first day on which the plan is required to operate in accordance with the benefit limitation”. 

Thus, a notice that is provided before the plan is required to operate in accordance with the benefit limitation does not appear to satisfy the Section 101(j) notice requirement. 

When exactly must the plan be operated in accordance with the benefit limitation?

Q&A-4 refers to the applicable “436 measurement date”.  The term “436 measurement date is defined in Treas. Regs. Section 1.436-1(j)(8), which says, in part, “See paragraphs (h)(1)(i), (h)(2)(iii)(B), (h)(2)(iv)(B) and (h)(3)(i) of this section regarding section 436 measurement dates that result from the application of presumptions under paragraph (h) of this section.” 

Treas. Regs. Section 1.436-1(h)(1)(i) applies where a plan was subject to a limitation on the last day of the preceding plan year.  In that case, the first day of the plan year is a section 436 measurement date, and the presumed AFTAP equals the AFTAP for the prior year until another certification or presumption changes the AFTAP.  The remaining references to the (h) regulations work through the AFTAP presumptions that apply – minus 10% if the actuary does not provide a certification by April 1 and less than 60% if the actuary does not provide a certification by October 1.  Further, the date of any new certification seems to a new “436 measurement date.”  (See, for example, Treas. Regs. Section 1.436-1(h)(1)(iii)(B) stating that the date of a late prior plan year certification delivered in the current plan year “is a new section 436 measurement date for the current year.”)

As a result, benefit restrictions on “prohibited payments” seem to apply based on the date on which the plan’s AFTAP is either certified as being below 80% or 60%, as applicable, or deemed to be certified as being below 80% or 60%, as applicable.  (I think this is right, and that the Morgan Lewis folks were simply being imprecise in their presentation where they used the term “valuation date”.  See slide 17 of their presentation, which is available here:  http://www.morganlewis.com/pubs/EB_Webinar_RestrictionsSingle-EmployerBenefitPlans_21mar2012.pdf )

Can a certification be provided later to delay imposition of benefit restrictions?

There seems to have been a fair amount of anguish in the actuarial community about the ethics of holding off on providing a certification that would cause a plan to be subject to benefit restrictions.  Typical of this is an April 1, 2011 article from the BNA Daily Tax Report, “Treasury, IRS Speakers Discuss Anti-Cutback Relief, Actuaries’ Duties”.  Harlan Weller stated that he would expect actuaries to get their certifications done “as soon as practicable” and that actuaries would not “intentionally delay” issuing a certification.  Carolyn Zimmerman, who is apparently the Chair of the Joint Board for the Enrollment of Actuaries reminded actuaries of their professional responsibilities and expressed concern about situations where a plan could become defunded by continuing to pay lump sums because someone manipulated the timing of the AFTAP certification.

Thus, there seems to be a somewhat fuzzy line here, but the actuary who knows that a plan will be subject to benefit limitations must issue his or her certification promptly, and then the plan must begin to operate in compliance with the limitations.

What are the other times at which a Section 101(j) notice must be provided?

Q&A-6 of Notice 2012-46 provides that a notice with respect to an unpredictable contingent event must be provided “… on or before the latest of” (1) the date a WARN Act notice is provided for the contingent event, (2) 60 days before the actual occurrence of the contingent event and (3) 30 days after the employer makes the decision to cause the contingent event (for example, the decision to shut down a plant).  Thus, for an unpredictable contingent event, it seems that the Section 101(j) notice may need to be provided before the actual event occurs.

Where does this leave an employer as far as providing advance notice of benefit restrictions on lump sum payments?

The ERISA Industry Committee, or “ERIC” specifically requested that employers be allowed to provide the required notice of benefit restrictions before the restrictions become applicable.  Specifically, ERIC’s letter, (available here: http://www.eric.org/forms/uploadFiles/28B7C00000005.filename.ERIC_Response_to_Treasury_Regulatory_Burden_RFI_042911.pdf ) states on page 4, “Many employers know in advance that the restrictions will apply, and wish to provide the § 101(j) notice in advance – when the information is most useful to affected participants.  Regulations under ERISA § 101(j) should allow the notice to be provided at any time during a window that opens a reasonable time (e.g., 90 days) before the restrictions become applicable and closes 30 days after the restrictions become applicable.”

The IRS did not act on this recommendation.  IRS Notice 2012-46 does not provide any comment on providing early warning that benefit limitations are likely to apply or will apply to a plan, but under the terms of Notice 2012-46, an early notice does not appear to satisfy the ERISA Section 101(j) notice requirement.    

In an older Client Action Bulletin, dated March 16, 2009 (available here: http://publications.milliman.com/periodicals/cab/pdfs/CAB03-16-09-Benefit-Restrictions.pdf ), Milliman advises, “Although advance notification is not required, informing participants of possible benefit restrictions prior to the date restrictions will take effect may be prudent.  This is particularly true for participants who have benefit elections in process before the effective date of the restrictions.  Participants who discover that a lump sum option is not available only because their benefit election forms were received by the plan sponsor after benefit restrictions were received are likely to be upset.”

Yes, participants who do not receive lump sums are likely to be upset.  On the other hand, at many employers, the number of participants who terminate and elect lump sums could increase dramatically if participants learn that benefit restrictions will apply in the future.  If that causes the plan’s AFTAP to drop further, participants who then cannot receive a 50% lump sum may be upset as well. 

It is difficult for me to reconcile the statements made by Carolyn Zimmerman with the suggestion made by Milliman.  In either case, one group of participants may be privileged over another.  Unless I am missing something, I think the plan’s fiduciaries would need to weigh making an advance disclosure carefully.  In addition, I think that the advance disclosure would need to be made in a way that all participants were likely to receive it, even though it is not a required disclosure.  The worst possible action seems to be allowing those “in the know” to take their lump sums while others miss the opportunity.  That may weigh in favor of a more general disclosure, but I think there is no clear course of action under current guidance.

The bottom line, for me anyway, seems to be the plan fiduciaries seem to have a duty to all participants, and they will need to decide what sort of notice is in the best interests of participants generally.  Sadly, by failing to provide advance notice, the employer and plan fiduciaries seem highly likely to be sued.  If they provide advance notice, they may be less likely to be sued because the cause of any future harm to an individual participant may be more difficult to tie back to continued lump sum payments in a relatively brief period following the notice period unless the advance notice creates so much demand for lump sums that the funded status of the plan is clearly affected.

Deposit of Employment Tax Related to Stock Options and Restricted Stock

Last week I was asked whether the timing for the deposit of employment tax related to exercise of a non-qualified stock option calculated from the exercise date or the settlement date.  This question pushed me into the details of payroll tax that I’ve tended to try to slide past, and I’m grateful for being forced to look at this more carefully.  Below I’ve also included a discussion of how the treatment of restricted stock may differ.

Timing of Deposit of Employment Tax Related to Nonqualified Stock Option Exercise

Under § 83 of the Internal Revenue Code of 1986, as amended (the “Code”) and Rev. Rul. 67-257, the exercise of a stock option is likely the point in time when the employee is deemed to acquire a “beneficial ownership interest” in the stock, which triggers income tax liability.  (See also Becker v. Comm’r, 378 F. 2d 767 (3d Cir. 1967), which held that the holding period of stock for capital gains purposes began at the time the employee took actions necessary to exercise his options.) 

However, the timing for FICA tax purposes may be slightly different – specifically, Treas. Regs. § 31.3121(a)-2 specifies the time at which wages are received for FICA tax purposes, “In general, wages are received by an employee at the time that they are actually or constructively paid.”  Treas. Regs. § 31.3121(a)-2(b) states, “Wages are constructively paid when they are credited to the account of or set apart for an employee so they may be drawn upon him at any time although not then actually reduced to possession.”  Based on this language, it is arguable that the FICA tax event would be the settlement date, rather than the exercise date.

During the dot-com boom of the late 1990’s and early 2000’s, many IRS examiners (not agents, as a friend of mine who is reading The Pale King by David Foster Wallace has pointed out!) were apparently assessing late deposit penalties on employers in connection with the exercise of stock options.  This is because the agents were claiming that the employers had violated the “next business day rule” under Treas. Regs. § 31.6302-1(c), which requires deposit of employment taxes on or before the Wednesday or Friday next following a payment date within one business day if the employer has accumulated $100,000 in employment taxes.  Employment taxes are defined in Treas. Reg. § 31.6302-1(e) and include the employer and employee portions of FICA, plus income tax amounts withheld from employees’ wages.

In a Field Directive dated March 14, 2003, the IRS instructed examiners not to assess late deposit penalties relating to exercise of stock options if the deposits were made within one business day of the settlement date, and the settlement date was not more than three days after the date of exercise.  This three-day provision for settlement comports with the vesting date plus three days (“T+3”) settlement date that applies to stock option exercises for many (if not most) publicly traded companies, due to the Securities Exchange Commission requirement that broker-dealer trades be settled within three days as a benchmark for a reasonable period between exercise and settlement. 

The Field Directive referred to the timing rule for FICA tax and stated, “…it has been argued that the shares … are not available to the exercise of the options until the settlement date, and therefore no actual or constructive payment of wages takes place until that time.”  As a further practical matter (out in the real world), there may not be anything to withhold from until the trade actually settles.

As discussed above, the compensation realized upon exercise of a stock option is considered paid for income tax purposes on the exercise date, but under the March 14, 2003 Field Directive, employers receive up to a three-day period until the settlement date before the next business day rule for deposit of employment taxes applies.  Unfortunately, there is no provision for processing of employment taxes related to stock option withholding at a later date such as the next payroll date, which is probably what my client was hoping for.

In a May 2012 publication, Ernst & Young notes that for mechanical purposes, the liability date on Form 941 needs to be adjusted to the exercise date plus three days when completing the Form 941. See page 3 of the EY Payroll NewsFlash, Volume 13, Number 77, March 23, 2012 here: https://webforms.ey.com/Publication/vwLUAssets/Noncash_fringes_and_special_wage/$FILE/Vol.13,077%20Year%20end%20adjustments%20may%20be%20taxable%20NOW%203-23-2012.pdf

The IRS position has been criticized for its inflexibility, and the Section of Taxation of the American Bar Association stated in comments dated May 10, 2004, “The approach adopted in the March 14, 2003 Field Directive is unduly restrictive.  In requiring that deposits be made within one day of the settlement date it either assumes that employer is subject to the one-day deposit rule for large employers, and therefore provides no guidance to other employers, or indirectly imposes that requirement on other employers.”  The ABA’s comments were prepared in response to an IRS request for comments because the IRS and Department of Treasury 2003-2004 Priority Guidance Plan included providing guidance on the deposit requirements for employment taxes in connection with exercise of stock options.  However, no guidance appears to have been issued.  (The fact that the recent EY publication is still citing the same 2003 Field Directive confirms the lack of subsequent guidance.)  The ABA comments are available here: http://www.americanbar.org/content/dam/aba/migrated/tax/pubpolicy/2004/040510emt.authcheckdam.pdf.

Timing of Deposit of Employment Tax Related to Restricted Stock Vesting

For restricted stock, the timing for remitting tax is calculated from the vesting date.  For many companies, there appears to be some administrative processing period between the vesting date and the date on which shares can be transferred to or from a brokerage account, but this administrative processing of the shares of company common stock is not a settlement period, and it does not change the date for deposit of employment taxes related to vesting of restricted stock.  (This administrative processing period appears to be related to the practice that some companies have of having their stock plan services record-keeper track hypothetical stock amounts and then transferring actual shares to the grantee’s brokerage accounts on the vesting date.  However, I am not well-versed in all of these stock-transfer mechanics and do not fully understand them.) 

The date that income is received for tax purposes is the vesting date because restricted stock is actually beneficially owned by the grantee on the date of grant.  The shares are issued and outstanding and held by the grantee between the date of grant and the vesting date.  The tax event that occurs on the vesting date is not a transfer of ownership, but the lapse of a restriction on transfer that allows the shares to be sold.

If an employer accumulates $100,000 or more of employment taxes, those taxes must be deposited on the next business day.  Treas. Regs. § 31.6302-1(c)(3); see also page 22 of Circular E, Publication 15 for use in 2012.  The definition of “business day” for this purpose is any day other than a Saturday, Sunday or legal holiday in the District of Columbia under Code § 7503.  For 2012, legal holidays (which are listed on page 22 of Circular E) include September 3, which is Labor Day.  Thus, if the next business day rule is triggered by wages that are paid on August 31, 2012, the employment taxes must be deposited on Tuesday, September 4.

Code Section 415(b) and Aggregating Defined Benefit Plans

I have been thinking about how Code § 415(b) limits apply when a payment is made under more than one defined benefit plan.  This is an issue that I’ve never had to consider before, and I am coming to appreciate the actuaries who work with the plans in question much more than I used to.  Basically, this issue arises because the lump sum discount rate for the plans in question is the old PBGC rate, which is incredibly low, rather than much higher PPA rates. 

In any event, thanks to BenefitsLink, I came across a very good discussion of how Code § 415(b) applies to governmental plans with really helpful examples illustrating several calculations that are applicable across the board.  That is available here:  http://www.gabrielroeder.com/news/pdf_research/RM-415-Final-Regs-Update-2012.pdf.  The examples in this memorandum are incredibly helpful in illustrating how the Code §  415(b) limits work in all defined benefit plans, not simply governmental plans.

Assuming that a participant has a benefit under two separate plans, Treas. Regs. § 1.415(f)-1 explain how the Code § 415(b) limit applies. 

First, all defined benefit plans ever maintained by an employer are treated as a single plan.

Second, if an affiliated group has split, then a formerly affiliated plan is taken into account, but the formerly affiliated plan is treated as if it had terminated immediately prior to cessation of affiliation with sufficient assets to pay benefits and had purchased annuities.

These rules are illustrated by several examples, and the results are somewhat unexpected.  Consider Example 2, where the facts are as follows:

1)      Employees M and O participate in the ABC Corp. defined benefit plan. 

2)      Both Employees M and O go to work for a subsidiary of ABC Corp., which is XYZ Corp.  M is lucky and participates in the XYZ Corp. defined benefit plan in addition to the ABC defined benefit plan, but O is not so fortunate and does not participate in the XYZ Corp. defined benefit plan.

3)      ABC Corp. sells its shares of XYZ Corp. to LMN Corp.  (I’m going to call LMN Corp. “Buyer” because I find it less confusing.)  Buyer has its own defined benefit plan.

4)      O does not participate in Buyer’s defined benefit plan, but again M is lucky and participates in both the Buyer’s defined benefit plan and the XYZ defined benefit plan.

First off, the benefits that M accrues under the ABC and XYZ defined benefit plans are aggregated when XYZ is a subsidiary of ABC.  No surprises there. 

Following the sale of XYZ to Buyer, the way M’s benefit is tested for Code § 415(b) changes.  ABC must take into account M’s full benefit under the ABC plan, and M’s benefit under the XYZ plan that was accrued immediately prior to the stock sale.  (Treas. Regs. § 1.415(f)-1(j), Example 2, paragraph (iii).) 

Following the sale of XYZ to Buyer, the annual benefit provided under all three plans must be aggregated when applying Code § 415(b) limits to XYZ and Buyer plans.  This is because XYZ is still treated as having maintained the ABC Plan because it was a part of the ABC controlled group before the sale, and XYZ and Buyer are now treated as a single employer.  In calculating Employee M’s benefit, her ABC benefit is limited to the amount accrued immediately prior to the stock sale, as if the ABC plan had terminated immediately prior to the stock sale.  (Treas. Regs. § 1.415(f)-1(j), Example 2, paragraph (vi).)  Employee O’s situation is simpler because he has only his ABC plan benefit.  However, if he ever gets into Buyer’s plan, that old ABC plan benefit will count towards the Code § 415(b) limit for O as if the ABC plan had terminated immediately prior to the stock sale.  This seems monstrously unfair to Employee O (and to Employee M as well, for that matter).  Further, the administrative burden is huge.  I don’t know if buyers of subsidiaries typically keep the data about the benefit an employee may have accrued for some time spent at the old corporate parent for purposes of Code § 415(b) limits.

Further, there are weird situations that seem likely to arise – for example joint ventures where a partner is not necessarily in the same controlled group as the venture but may still count joint venture compensation under its plan.  (Questionable, I realize, but these crazy things sometimes happen in that messy place called the real world!)

In that case, I would think that the joint venture plan and the partner companies plan would be aggregated for Code § 415(b) purposes.  But which plan’s benefit is reduced if a limit is hit?  Which plan’s benefit counts towards the limit first?  I am assuming that it must be the former employer’s plan because the employee is gone, and might even have commenced his benefit there.  The practical implications of attempting to reduce a benefit post-commencement are indeed mind-boggling, so the only choice seems to be to reduce the benefit the employee is accruing in his current employer’s plan.

Again, that is monstrously unfair to the employee, but I do not see a tax law problem or an ERISA problem with that answer because the only employees who are going to have a Code § 415(b) problem are likely those with compensation at the Code § 401(a)(17) limit and a whole lot of service.  (That’s why I think this would come up for joint ventures where the venture seems reasonably likely to count partner service as an inducement for high-performing employees to join the venture.)  There is nothing wrong with cutting the benefit of a very highly compensated employee.  There is also nothing else the plan can do given that Code § 415(b) limits are qualification requirements.  But why do we have a law that limits the benefit that can be paid from qualified plans that otherwise pass non-discrimination testing?  What is the public good achieved here?

Follow

Get every new post delivered to your Inbox.