ARTICLE
25 September 2013

IRS And DOL Issue Guidance On Windsor Decision And Employee Benefit Plans

In its decision in United States V. Windsor, handed down on June 26, 2013, the U.S. Supreme Court held that Section 3 of the Defense of Marriage Act is unconstitutional because it violates the principles of equal protection.
United States Employment and HR
To print this article, all you need is to be registered or login on Mondaq.com.

In its decision in United States V. Windsor, handed down on June 26, 2013, the U.S. Supreme Court held that Section 3 of the Defense of Marriage Act is unconstitutional because it violates the principles of equal protection.  While this decision was monumental, the Supreme Court did not address Section 2 of DOMA, which provides that no state is required to recognize a same-sex marriage that was (legally) performed and recognized in another state.

Consequently, for the last three months, many same-sex couples and their employers have been left in a quandary.  Consider the same-sex couple who were married legally in one state, but now are domiciled in a state that does not recognize same-sex marriage.  Now, add the complication that at least one of the parties works in the state in which the couple resides, but all benefit programs are administered in a third state, where the employer's home office is located, and that recognizes same-sex marriage.  Which state law controls?

Fortunately, the IRS just resolved these concerns, at least insofar as federal tax matters and ERISA-governed employee benefit plans are concerned, in Revenue Ruling 2013-17 and two sets of Frequently Asked Questions, all of which became effective as of September 16, 2013.  The guidance makes it clear that a same-sex marriage that is valid in the place of celebration (whether that be a state or a foreign jurisdiction having the legal authority to sanction marriage) will be recognized, regardless of the domicile of the parties.  The terms spouse, husband and wife will be defined on a gender-neutral basis, for all federal purposes, to refer to individuals who are lawfully married under state law. 

This guidance further confirms that the term "marriage" does not include registered domestic partnerships, civil unions or other similar formal relationships recognized under state law that are not denominated by that state's law as marriage.  As such, the terms spouse, husband and wife do not include individuals who have entered into such a formal relationship.  This is the case whether the parties are of the same or opposite sex.

The guidance provided by the Revenue Ruling is to be applied prospectively.  However, affected taxpayers are permitted to rely upon it for the purpose of filing original, amended or adjusted returns and/or claims for credit or refund for overpayments of tax resulting from these changes, provided that the applicable statute of limitations has not expired.  The IRS made note in the Revenue Ruling that it expects to issue further guidance, specifically with regard to employee benefits and employee benefit plans, pertaining to potential consequences of retroactive application of the new law and to provide plan sponsors with sufficient time for plan amendments and any necessary corrections.

In addition to the recently issued IRS guidance, the Employee Benefits Security Administration (EBSA) division of the Department of Labor also issued its own guidance on September 18, 2013.  Fortunately, EBSA has adopted an identical position to the IRS that a same-sex marriage that is valid in the state of celebration will be recognized notwithstanding the residence of the parties.  This makes for a clear, consistent policy among the government agencies governing employee benefits.

So, what does all of this mean for employee benefit plans and for the employers that sponsor them?

  1. First and foremost, employers should review their plan documents to identify any nonconforming definitions of marriage, spouse, husband and wife.  That said, it is probably a good idea to defer amending plan documents until the IRS has set clear guidelines for amendment deadlines and effective dates.
  2. Plans should be administered and operated, beginning immediately, to comply with the new law, by extending spousal rights and spousal benefits on a gender-neutral basis, even though plan documents haven't yet been amended.  This applies to all benefits, including group health plans of all types, flexible spending accounts and group insurance programs.  
  3. Keep in mind, that while benefits provided to domestic partners generally remain taxable, health insurance and other benefits provided to spouses (whether of the same or opposite sex) are not, so payroll protocols must be adjusted. 
  4. Qualified retirement plans, in particular, are affected by the new law.  Same-sex spouses now will be automatic death beneficiaries (unless appropriate spousal consent is secured) and will be eligible for spousal rollover of benefits.  The financial needs of same-sex spouses must be taken into account under the 401(k) hardship withdrawal rules, and same-sex spouses or former spouses may obtain rights as alternate payees under qualified domestic relations orders.  Plan participants should be made aware of these changes and should be encouraged to review their beneficiary designations and revise them as appropriate.
  5. Some authorities have suggested that plan administrators should request proof of marriage before accepting a new beneficiary designation or claim for benefits.  While, to a large extent, this is a matter of personal preference and administrative feasibility, we strongly recommend that documentation request policies be developed and administered objectively, consistently and with sensitivity.
  6. Watch for the additional guidance promised by the IRS!

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

See More Popular Content From

Mondaq uses cookies on this website. By using our website you agree to our use of cookies as set out in our Privacy Policy.

Learn More