<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>HRBenefitsAlert.com &#187; Employee Retirement Income Security Act</title>
	<atom:link href="http://www.hrbenefitsalert.com/category/employee-retirement-income-security-act/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hrbenefitsalert.com</link>
	<description>Daily dose of benefits news and know-how</description>
	<lastBuildDate>Wed, 29 Jul 2009 13:18:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Total compensation statements gone bad</title>
		<link>http://www.hrbenefitsalert.com/total-compensation-statements-gone-bad/</link>
		<comments>http://www.hrbenefitsalert.com/total-compensation-statements-gone-bad/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 06:10:43 +0000</pubDate>
		<dc:creator>Bill Meltzer</dc:creator>
				<category><![CDATA[Cafeteria plans]]></category>
		<category><![CDATA[Cobra]]></category>
		<category><![CDATA[Compensation]]></category>
		<category><![CDATA[Employee Assistance Programs (EAPs)]]></category>
		<category><![CDATA[Employee Retirement Income Security Act]]></category>
		<category><![CDATA[Healthcare costs]]></category>
		<category><![CDATA[In this week's e-newsletter]]></category>
		<category><![CDATA[Latest News & Views]]></category>

		<guid isPermaLink="false">http://www.hrbenefitsalert.com/?p=153</guid>
		<description><![CDATA[They&#8217;re a proven way to show employees the firm invests more in them than they may think. But be careful. 
The statements can easily backfire – or contain inaccuracies. Here’s how to find and fix two common trouble spots:
1. Avoiding incorrect info
Accidental math errors are the most common – and damaging – problem with total comp statements.
They’re [...]]]></description>
			<content:encoded><![CDATA[<p>They&#8217;re a proven way to show employees the firm invests more in them than they may think. But be careful. <span id="more-153"></span></p>
<p>The statements can easily backfire – or contain inaccuracies. Here’s how to find and fix two common trouble spots:</p>
<p><strong>1. Avoiding incorrect info</strong></p>
<p>Accidental math errors are the most common – and damaging – problem with total comp statements.<br />
They’re also the toughest for you to spot and correct before the firm sends out the statements, since you aren’t the one who crunches the numbers.</p>
<p>But there are two ways to minimize the risk:</p>
<ul>
<li>Make a list of the data sources you use, such as Payroll, your 401(k) provider and health plan carrier, and</li>
<li>Ask each source to pull and review a few random samples. If they’re OK, chances are the rest will also be fine. But if they contain errors, you can be pretty sure others will have mistakes.</li>
</ul>
<p>A related problem: Some statements are arranged as a single list of costs, one line after another. To cut the risk of putting something on the wrong line, break the statement down into small sections (e.g., salary, healthcare and retirement). Bonus: This helps make statements easier for employees to follow.</p>
<p><strong>2. ‘Just increase my salary’ syndrome</strong></p>
<p>Sometimes, total compensation statements can actually decrease salary satisfaction, rather than boost morale. A handful of employees may gripe, “Why can’t you just increase my salary instead?” That’s especially true for legally required benefits (like workers’ compensation) and low-profile benefits such as term life insurance. Two fixes that work:</p>
<ul>
<li>List “government-required benefits” as a section of the statement. Avoid the term “mandated,” since many employees are unfamiliar with it, and</li>
<li>Consider adding a section that shows employees how much it’d cost them to line up their own coverage instead.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.hrbenefitsalert.com/total-compensation-statements-gone-bad/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identity theft: Benefits records a prime target</title>
		<link>http://www.hrbenefitsalert.com/growing-threat-benefits-identity-theft/</link>
		<comments>http://www.hrbenefitsalert.com/growing-threat-benefits-identity-theft/#comments</comments>
		<pubDate>Thu, 09 Apr 2009 06:00:40 +0000</pubDate>
		<dc:creator>Bill Meltzer</dc:creator>
				<category><![CDATA[Employee Retirement Income Security Act]]></category>
		<category><![CDATA[Employee education]]></category>
		<category><![CDATA[Latest News & Views]]></category>
		<category><![CDATA[Retirement]]></category>

		<guid isPermaLink="false">http://www.hrbenefitsalert.com/growing-threat-benefits-identity-theft/</guid>
		<description><![CDATA[In the last few years, there&#8217;s been a lot of publicity about the fast-growing crime of identity theft. More than half happen in the workplace. Benefits and compensation files are the most vulnerable targets.

The scariest part: Victims of benefits-related ID theft often make out worse than those who fall prey to the more common variety. The bad guys are [...]]]></description>
			<content:encoded><![CDATA[<p>In the last few years, there&#8217;s been a lot of publicity about the fast-growing crime of identity theft. More than half happen in the workplace. Benefits and compensation files are the most vulnerable targets.</p>
<p><span id="more-48"></span></p>
<p>The scariest part: Victims of benefits-related ID theft often make out worse than those who fall prey to the more common variety. The bad guys are ahead of investigators after such thefts occur, and are often very good at covering their tracks.</p>
<p>Also, because benefits ID-theft is a relatively new type of crime, there&#8217;s no well-established system for victims, plan sponsors and vendors to set things straight after the fact.</p>
<p><strong>401(k) accounts a prime target</strong></p>
<p>Not surprisingly, employees&#8217; 401(k) accounts have become the primary target for benefits thieves. An alarming MSNBC news report showed just how easy it can be for thieves to tap into an employee&#8217;s 401(k) accounts: If an online account gets hacked into or account paperwork falls into the wrong hands, it takes only a few mouse clicks to wipe out the victim&#8217;s retirement savings.</p>
<p>With typical credit-card or bank account fraud, victims need only call their card issuer or bank, report the crime and refuse to pay for an item. But 401(k) theft is much, much harder to resolve.</p>
<p>Three huge obstacles:</p>
<ol>
<li>Money in 401(k) accounts is not federally insured, like a bank account.</li>
<li>401(k) accounts rarely &#8212; if ever &#8212; come with automatic identity theft protection from the vendor, like credit cards.</li>
<li>Even if the theft is successfully resolved, the situation becomes an ERISA nightmare for plan sponsors, because your company also has to account for the way the theft affected the growth of the employee&#8217;s account before the money was restored.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.hrbenefitsalert.com/growing-threat-benefits-identity-theft/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A 401(k) documentation horror story</title>
		<link>http://www.hrbenefitsalert.com/401k-documentation-horror-stor/</link>
		<comments>http://www.hrbenefitsalert.com/401k-documentation-horror-stor/#comments</comments>
		<pubDate>Tue, 04 Nov 2008 05:00:43 +0000</pubDate>
		<dc:creator>Bill Meltzer</dc:creator>
				<category><![CDATA[Employee Retirement Income Security Act]]></category>
		<category><![CDATA[In this week's e-newsletter]]></category>
		<category><![CDATA[Latest News & Views]]></category>
		<category><![CDATA[Our best management idea]]></category>
		<category><![CDATA[Retirement]]></category>

		<guid isPermaLink="false">http://www.hrbenefitsalert.com/horror-story-why-it-pays-to-doublecheck-401k-documents/</guid>
		<description><![CDATA[You can’t always trust 401(k) vendors to automatically get all the details right in their plan documents. 
One of our readers shared a horror story from her company &#8212; one that at least had a happy ending &#8212; that underlines the need to be extra careful, especially in light of the recent Supreme Court ruling [...]]]></description>
			<content:encoded><![CDATA[<p>You can’t always trust 401(k) vendors to automatically get all the details right in their plan documents. <span id="more-44"></span></p>
<p>One of our readers shared a horror story from her company &#8212; one that at least had a happy ending &#8212; that underlines the need to be extra careful, especially in light of the recent Supreme Court ruling that makes plan sponsors vulnerable to employee lawsuits.</p>
<p><strong>Mistakes caught after the fact</strong></p>
<p>The company was in the process of changing 401(k) service providers when it discovered the outgoing provider had goofed on the plan documents in the existing plan.</p>
<p>The documents said the normal payout form would be a joint survivor annuity. So if anyone wanted another option – such as an IRA rollover or a cashout – he or she needed documentation with a notarized signature from a spouse or other beneficiary.</p>
<p>Even worse, there were administrative errors made on the election end. Records showed the old provider put through inappropriate elections from both current and ex-employees. A nightmarish paper chase ensued. Senior management had to calculate if the plan and its participants suffered financially from the inappropriate elections that went through. In addition, the company had to contact everyone who may have been affected by the errors and issue corrected documentation.</p>
<p>One saving grace in this whole mess was that the outgoing vendor (a well-known vendor with a good reputation) agreed to pick up the tab to correct the mistakes that&#8217;d been made. It took several months to clean up the mess, but everything was sorted out. Things could&#8217;ve turned out much, much worse.</p>
<p>Ever since then, the company has been muc wiser for the wear. Management is now hyper-vigilant about staying on top of its new 401(k) vendor. The firm has made sure the vendor got all the documentation right up front, and has made a habit of checking to make sure everything&#8217;s adminstered according to the plan documents.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hrbenefitsalert.com/401k-documentation-horror-stor/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Handling benefits information requests: Dos and don’ts</title>
		<link>http://www.hrbenefitsalert.com/handling-benefits-information-requests-dos-and-donts/</link>
		<comments>http://www.hrbenefitsalert.com/handling-benefits-information-requests-dos-and-donts/#comments</comments>
		<pubDate>Tue, 07 Oct 2008 04:55:18 +0000</pubDate>
		<dc:creator>Bill Meltzer</dc:creator>
				<category><![CDATA[Company culture]]></category>
		<category><![CDATA[Employee Retirement Income Security Act]]></category>
		<category><![CDATA[Employee education]]></category>
		<category><![CDATA[Latest News & Views]]></category>
		<category><![CDATA[Wellness]]></category>

		<guid isPermaLink="false">http://www.hrbenefitsalert.com/?p=39</guid>
		<description><![CDATA[Benefits managers are busy people. Sometimes it&#8217;s tempting to deal with more pressing tasks rather than answering routine employee requests for benefits information.
But when the request is for info about a company-sponsored plan affected by ERISA &#8211; including your retirement and health plans &#8211; it pays to answer as soon as possible. By law, you&#8217;re [...]]]></description>
			<content:encoded><![CDATA[<p>Benefits managers are busy people. Sometimes it&#8217;s tempting to deal with more pressing tasks rather than answering routine employee requests for benefits information.<span id="more-39"></span></p>
<p>But when the request is for info about a company-sponsored plan affected by ERISA &#8211; including your retirement and health plans &#8211; it pays to answer as soon as possible. By law, you&#8217;re on the clock to issue a reply. Courts can hold your firm liable if management drags its feet responding to questions about eligibility, account balance discrepancies or instructions for filing claim-related complaints.</p>
<p><strong>Phoned-in or written requests</strong></p>
<p>A landmark case (<em>Minadeo v. ICI Paints</em>) spells out how not to handle such requests. When downsizing forced an employee&#8217;s termination after 15 years with a company, the firm sent her a letter saying that she&#8217;d receive a separate mailing with her pension benefit eligibility info.</p>
<p>The mailing never came. Over the next 11 months, the ex-employee repeatedly called the company to request the info.</p>
<p>When the firm still didn&#8217;t provide the information, she had her attorney file a written request, threatening legal action if the firm didn&#8217;t comply. Finally, 15 months after she was terminated, the employee received the info &#8211; and was told she didn&#8217;t qualify for the benefits. She sued.</p>
<p>The company&#8217;s defense: The only &#8220;formal&#8221; info request came from the woman&#8217;s lawyer. The other requests came via telephone and were &#8220;unofficial.&#8221; The court rejected this argument, saying the company was legally bound to respond to the phoned-in requests.</p>
<p><strong>What ERISA requires</strong></p>
<p>Under ERISA, employers have 30 days to respond to information requests by &#8211; or on behalf of &#8211; a participant. Two ways to comply:</p>
<ul>
<li>provide the info, in writing, directly to the plan participant, or</li>
</ul>
<ul>
<li>inform his or her attorney (or other non-beneficiary filing the request) that the info will be released to him or her upon receipt of a consent form signed by the participant.</li>
</ul>
<p>So what do you do if there&#8217;s a third party administrator (TPA) for the plan, but the eligibility info request comes to you instead?</p>
<p>As plan sponsor, it&#8217;s the company&#8217;s responsibility to direct the request to the TPA, and follow up yourself if you learn there&#8217;s been no response. The one thing you should <em>never</em> do is simply assume someone else will answer the request.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hrbenefitsalert.com/handling-benefits-information-requests-dos-and-donts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
