<?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>U.S. Law Watch</title>
	<atom:link href="http://www.uslawwatch.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uslawwatch.com</link>
	<description>U.S. Legal &#38; Regulatory Headlines</description>
	<lastBuildDate>Mon, 29 Apr 2013 10:12:39 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>BNA INSIGHTS: New HIPAA Regulations: What Liability Risks Loom Under the Expanded Business Associate and Breach Notification Provisions?</title>
		<link>http://www.uslawwatch.com/2013/04/09/privacy/bna-insights-hipaa-regulations-liability-risks-loom-expanded-business-associate-breach-notification-provisions/</link>
		<comments>http://www.uslawwatch.com/2013/04/09/privacy/bna-insights-hipaa-regulations-liability-risks-loom-expanded-business-associate-breach-notification-provisions/#comments</comments>
		<pubDate>Tue, 09 Apr 2013 12:10:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Privacy]]></category>
		<category><![CDATA[breach notification]]></category>
		<category><![CDATA[health data privacy]]></category>

		<guid isPermaLink="false">http://www.uslawwatch.com/?p=6159</guid>
		<description><![CDATA[The new HIPAA omnibus rule adopted an expanded definition of “business associate” and tightened the standards for notification of breaches of the security of health information...]]></description>
				<content:encoded><![CDATA[<p><img alt="Nancy Perkins" src="http://privacylaw.bna.com/pvrc/core_adp/get_object/im186555.png" /></p>
<p><em>By <strong>Nancy L. Perkins</strong>, Arnold &amp; Porter LLP.</em></p>
<div>In its new omnibus final rule governing health data privacy, security, and enforcement published Jan. 25,  the Department of Health and Human Services has unilaterally broadened the scope of potential liability under the Health Insurance Portability and Accountability Act of 1996 to a vastly greater range of persons and entities than those Congress apparently contemplated. Confirming its view of its own authority under HIPAA, HHS adopted the expanded definition of “business associate” under HIPAA that it suggested in a proposed rule  in 2010: going forward, subcontractors of covered entities&#8217; business associates will be business associates themselves.</div>
<p>&nbsp;</p>
<div>At the same time, HHS tightened the standards for notification of breaches of the security of health information that it prescribed in an interim final rule in 2009.  No longer may HIPAA covered entities and business associates determine that breach notifications are unwarranted because a data security incident appears to pose no significant risk of harm to individuals whose health information was involved. Instead, notifications are uniformly required unless, following an investigation, it can be determined that there is a “low probability” of any compromise to the security of individually identifiable health information.</div>
<p>&nbsp;</p>
<div>These two moves—even setting aside the numerous other compliance requirements associated with the final rule—substantially raise the stakes for a wide variety of entities that may have access to medical information, particularly in light of the heightened civil and criminal penalties for data protection violations authorized by the 2009 Health Information Technology for Economic and Clinical Health (HITECH) Act.  Under the HITECH Act, violations of the HIPAA Privacy Rule  or Security Rule  are punishable by penalties as much as $50,000 for each violation (up to $1.5 million within a single year). In addition, state attorneys general may sue for injunctive relief, statutory damages, and attorneys&#8217; fees, with damages potentially running as high as $100 per violation or $25,000 for all violations of an identical requirement or prohibition during a single calendar year.</div>
<p>Clearly, the new final rule merits close attention and counsels in favor of proactive—and timely—compliance planning. The final rule takes effect March 26 and compliance with most of its provisions is required by Sept. 23.</p>
<h4>Background on the HITECH Act and the HIPAA Privacy and Security Rules</h4>
<p>In the HITECH Act, Congress prescribed a number of changes to the HIPAA Privacy and Security Rules, which collectively serve to protect the privacy and security of “protected health information” (PHI).  As originally adopted by HHS, consistent with HIPAA, the Privacy and Security Rules directly applied only to HIPAA “covered entities,” which are (1) health plans, (2) health care clearinghouses, and (3) health care providers who perform certain transactions involving health information in electronic form. The original rules affected, but did not directly apply, to business associates of those covered entities (such as billing and claims administrators, accountants, attorneys, and data management companies), by requiring that a business associate may receive an individual&#8217;s PHI from a covered entity only if the covered entity obtains satisfactory assurances from the business associate that it will protect the PHI in a manner consistent with the covered entity&#8217;s obligations under the Privacy Rule. Such satisfactory assurances are to be provided in a business associate agreement (BAA) between the parties that contains specific commitments.</p>
<p>&nbsp;</p>
<div>In the HITECH Act, Congress changed this framework by making business associates directly liable for violation of relevant aspects of the Privacy Rule and the Security Rule. And, in an important step to help protect individuals from the adverse consequences of breaches of the security of their PHI, Congress also required HHS to adopt regulations requiring notification to individuals and HHS (and in certain cases, the media) of such breaches. Under the HITECH Act, covered entities bear the obligation to notify individuals and HHS; business associates must notify the covered entities from or on behalf of whom the business associate received the affected PHI.</div>
<h4>What Has HHS Now Done With the “Business Associate” Definition?</h4>
<p>Despite receiving many objections, HHS adopted in the final rule its proposed expansion of the HIPAA rules&#8217; definition of business associate to include subcontractors of HIPAA business associates. HHS acknowledged that the proposed expansion was viewed by many as “not the intent of Congress and beyond the statutory authority of the Department,” and that commenters believed “creating direct liability for subcontractors will discourage such entities from operating and participating in the health care industry.”  But HHS disagreed, noting that the HITECH Act “does not bar the Department from modifying definitions of terms in the HIPAA Rules to which the Act refers,” and opining that the statute “expressly contemplates that modifications to the terms may be necessary to carry out the provisions of the Act or for other purposes.” <sup><br />
</sup></p>
<p>According to HHS, its expanded business associate definition is necessary to prevent the lapse in protection for PHI once a subcontractor is enlisted to assist a primary business associate. Thus, under the final rule, “covered entities must ensure that they obtain satisfactory assurances required by the [HIPAA] Rules from their business associates, and business associates must do the same with regard to subcontractors, and so on, no matter how far ‘down the chain’ the information flows.”  And, as HHS further explained, the factors that determine whether a first-tier contractor is a business associate also govern the determination of whether a subcontractor is a business associate.</p>
<p>&nbsp;</p>
<h4>Who IS and Who Is NOT a Business Associate?</h4>
<p>HHS received a number of comments objecting to the proposed expanded definition of business associate on the ground that it was confusing and ambiguous. As these comments emphasized, the ability to determine which entities are covered by the definition is critical, particularly in light of the enhanced penalties authorized by the HITECH Act. In response, HHS provided some further clarification and guidance on the scope of the new business associate definition. However, ambiguities remain&#8230;</p>

		<div id="usermessagea" class="cf_info "></div>
		<form enctype="multipart/form-data" action="/feed/#usermessagea" method="post" class="cform contact-form " id="cformsform">
		<ol class="cf-ol">
			<li id="li--1" class="textonly" style="color:red" >Read this entire article for free, simply activate your free 7 day trial access now.</li>
		</ol>
		<fieldset class="cf-fs1">
		<legend>Contact Bloomberg BNA</legend>
		<ol class="cf-ol">
			<li id="li--3" class=""><label for="cf_field_3"><span>Your Name</span></label><input type="text" name="cf_field_3" id="cf_field_3" class="single fldrequired" value="Your Name" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li--4" class=""><label for="cf_field_4"><span>Email</span></label><input type="text" name="cf_field_4" id="cf_field_4" class="single fldemail fldrequired" value=""/><span class="emailreqtxt">(valid email required)</span></li>
			<li id="li--5" class=""><label for="cf_field_5"><span>Message</span></label><textarea cols="30" rows="8" name="cf_field_5" id="cf_field_5" class="area"></textarea></li>
			<li id="li--6" class=""><label for="cforms_captcha" class="seccap"><span>Verification</span></label><input type="text" name="cforms_captcha" id="cforms_captcha" class="secinput" value=""/><img id="cf_captcha_img" class="captcha" src="http://www.uslawwatch.com/wp-content/plugins/cforms/cforms-captcha.php?ts=&amp;c1=4&amp;c2=5&amp;ac=abcdefghijkmnpqrstuvwxyz23456789&amp;i=i&amp;w=115&amp;h=35&amp;c=2B3AFF&amp;l=547FA9&amp;f=font32.ttf&amp;a1=-5&amp;a2=5&amp;f1=17&amp;f2=19&amp;b=16.gif" alt=""/><a title="reset captcha image" href="javascript:reset_captcha('')"><img class="captcha-reset" src="http://www.uslawwatch.com/wp-content/plugins/cforms/images/spacer.gif" alt="Captcha"/></a></li>
		</ol>
		</fieldset>
		<fieldset class="cf_hidden">
			<legend>&nbsp;</legend>
			<input type="hidden" name="cf_working" id="cf_working" value="One%20moment%20please..."/>
			<input type="hidden" name="cf_failure" id="cf_failure" value="Please%20fill%20in%20all%20the%20required%20fields."/>
			<input type="hidden" name="cf_codeerr" id="cf_codeerr" value="Please%20double-check%20your%20verification%20code."/>
			<input type="hidden" name="cf_customerr" id="cf_customerr" value="yyy"/>
			<input type="hidden" name="cf_popup" id="cf_popup" value="nn"/>
		</fieldset>
		<p class="cf-sb"><input type="submit" name="sendbutton" id="sendbutton" class="sendbutton" value="Submit"/></p></form><p class="linklove" id="ll"><a href="http://www.deliciousdays.com/cforms-plugin"><em>cforms</em> contact form by delicious:days</a></p>		<div id="usermessageb" class="cf_info " ></div>


<a href="http://twitter.com/?status=RT%20%40%3A%20BNA%20INSIGHTS%3A%20New%20HIPAA%20Regulations%3A%20What%20Liability%20Risks%20Loom%20Under%20the%20Expanded%20Business%20Associate%20and%20Breach%20Notification%20Provisions%3F%20-%20U.S.%20Law%20Watch%20http%3A%2F%2Ftinyurl.com%2Fccfg2yt" class="tweet-this" ><img src="http://www.uslawwatch.com/wp-content/plugins/simple-tweet/img/tweet.gif" title="Tweet this!" alt="Tweet this!" />Tweet this!</a>]]></content:encoded>
			<wfw:commentRss>http://www.uslawwatch.com/2013/04/09/privacy/bna-insights-hipaa-regulations-liability-risks-loom-expanded-business-associate-breach-notification-provisions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BNA INSIGHTS: Top Ten SEC Enforcement Developments of 2012</title>
		<link>http://www.uslawwatch.com/2013/04/09/finance/bna-insights-top-ten-sec-enforcement-developments-2012/</link>
		<comments>http://www.uslawwatch.com/2013/04/09/finance/bna-insights-top-ten-sec-enforcement-developments-2012/#comments</comments>
		<pubDate>Tue, 09 Apr 2013 12:01:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[accounting fraud]]></category>
		<category><![CDATA[alternative trading systems]]></category>
		<category><![CDATA[bounty program]]></category>
		<category><![CDATA[corporate officers]]></category>
		<category><![CDATA[foreign official bribery]]></category>
		<category><![CDATA[initial public offerings]]></category>
		<category><![CDATA[Insider Trading]]></category>
		<category><![CDATA[securities fraud]]></category>
		<category><![CDATA[Statutes of Limitations]]></category>

		<guid isPermaLink="false">http://www.uslawwatch.com/?p=6157</guid>
		<description><![CDATA[This article highlights significant developments during 2012 in the enforcement program of the U.S. SEC. Developments were selected because they may signal future trends or establish new legal standards...]]></description>
				<content:encoded><![CDATA[<p><img alt="Marc Dorfman" src="http://news.bna.com/srln/core_adp/get_object/im192188.png" width="100" height="110" /> <img alt="Ellen Wheeler" src="http://news.bna.com/srln/core_adp/get_object/im192176.png" width="100" height="110" /></p>
<p><em>By <strong>Marc Dorfman</strong> and <strong>Ellen Wheeler</strong>, Foley &amp; Lardner LLP.</em></p>
<div><span style="color: #808080;"><em>Foley &amp; Lardner LLP represents parties who are the subject of SEC enforcement inquiries and actions, including in cases discussed in this article.</em></span></div>
<p>This article highlights significant developments during 2012 in the enforcement program of the U.S. Securities and Exchange Commission (“SEC”). Developments were selected because they may signal future trends or establish new legal standards.</p>
<p>Last year we highlighted as the Number One enforcement development of 2011 the increasing scrutiny by courts of settlements negotiated between the SEC and defendants. As we noted a year ago,</p>
<div style="padding-left: 30px;">The U.S. Court of Appeals for the Second Circuit is considering an appeal by the SEC from a decision issued by U.S. District Court Judge Jed S. Rakoff rejecting a settlement negotiated by the SEC with Citigroup Capital Markets as “neither reasonable, nor fair, nor adequate, nor in the public interest” because it “asks the Court to impose substantial injunctive relief, enforced by the Court&#8217;s own contempt power, on the basis of allegations unsupported by any proven or acknowledged facts whatsoever….” The SEC has asked the Second Circuit to reject Judge Rakoff&#8217;s approach, but if its appeal is unsuccessful, the SEC will have little choice but to revisit its practices in negotiating settlements.</div>
<p>In some ways, during 2012, SEC Enforcement developments were reminiscent of a Beckett play, but with a new title: “Waiting for Rakoff.” The appeal to the Second Circuit from Judge Rakoff&#8217;s order declining to approve a settlement between the SEC and Citigroup remains sub judice, with the Court having finally heard oral argument on February 8, 2013. The outcome of that appeal is expected to have a significant impact on the SEC&#8217;s practices in negotiating settlements, either in confirming or limiting the use of consents which “neither admit nor deny” the SEC&#8217;s allegations.</p>
<p>In November 2012, the SEC announced that it had filed 734 enforcement actions in the fiscal year ending September 30 (only one fewer than the record number of proceedings instituted in the prior year).  Many of these actions are reflective of much larger societal trends. For example, this year&#8217;s Top Ten reflects the growing significance of social media and the increased globalization of markets, particularly with respect to China.</p>
<p>&nbsp;</p>
<div>The Number One enforcement development of 2012 is the SEC&#8217;s increasing effort to hold individuals (as well as their corporate employers) accountable for violations, with occasionally mixed results. Undoubtedly in response to the clamor of media and congressional complaints that executives at banks and other financial institutions have not been held responsible for the conduct that led to the 2008 financial crisis and market collapse, the SEC heavily touted its actions against bankers and other individuals during 2012. The SEC, however, also suffered a number of setbacks in its efforts to pursue such individuals in 2012. Indeed, the SEC&#8217;s case against a midlevel Citigroup executive resulted in both a defense verdict and a public rebuke by the jury foreman that the SEC had not pursued the top executives.</div>
<p>The SEC and the U.S. Department of Justice are jointly responsible for enforcing the provisions of the Foreign Corrupt Practices Act of 1977 (“FCPA”). The Number Two enforcement development of 2012 is the joint release by the SEC and DOJ in November of “A Resource Guide to the U.S. Foreign Corrupt Practices Act,” a 120-page guide providing a detailed analysis of the SEC&#8217;s and DOJ&#8217;s approaches to FCPA enforcement.</p>
<p>The remaining Top Ten developments illustrate other significant issues and trends in the SEC enforcement program:</p>
<p style="padding-left: 30px;">•  Number Three is the Supreme Court&#8217;s grant of a writ of certiorari in 2012 and decision in February 2013 holding that the five-year clock in the statute of limitations applicable to SEC claims for fraud begins when the fraud occurs, not when it is discovered.</p>
<p style="padding-left: 30px;">•  The Number Four enforcement development of 2012 is the SEC&#8217;s continued aggressive pursuit of insider trading cases.</p>
<p style="padding-left: 30px;">•  Number Five is the easing of the standard for aiding and abetting liability by the Second Circuit.</p>
<p style="padding-left: 30px;">•  Number Six is the opening for business of the SEC&#8217;s whistleblower program.</p>
<p style="padding-left: 30px;">•  Number Seven is the SEC&#8217;s pursuit of cases against officers and directors for overvaluing their firms&#8217; assets.</p>
<p style="padding-left: 30px;">•  Number Eight is the SEC&#8217;s case against a “dark pool” for not being dark enough.</p>
<p style="padding-left: 30px;">•  Number Nine is the SEC&#8217;s pursuit of cases involving pre-IPO trading.</p>
<div style="padding-left: 30px;">
<p>•  Number Ten is the SEC&#8217;s initiation of enforcement proceedings against China-based affiliates of U.S. accounting firms.</p>
</div>
<h4>1. The SEC&#8217;s Increasing Pursuit of Individuals, With Mixed Results</h4>
<p>In its press release describing its enforcement results in 2012, the SEC touted its enforcement actions against individuals accused of wrongdoing related to the financial crisis. <sup>2</sup> The SEC pointed out that it had filed 29 separate actions against 34 individuals, including 24 CEOs, CFOs and other senior corporate officers. Outgoing Chairman Mary L. Schapiro similarly focused on the SEC&#8217;s pursuit of individuals during her speech at the 2012 New England Securities Conference, explaining that the SEC is “determined in our pursuit of those whose actions fueled the Financial Crisis, bringing actions against over 100 individuals and firms – including more than 50 CEOs, CFOs and other senior officers, and obtaining more than $2.2 billion in monetary relief – not to mention dozens of orders barring individuals from the financial industry.”&#8230;</p>

		<div id="usermessage5a" class="cf_info "></div>
		<form enctype="multipart/form-data" action="/feed/#usermessage5a" method="post" class="cform securities-regulation-law-report-free-trial-form " id="cforms5form">
		<ol class="cf-ol">
			<li id="li-5-1" class="textonly" style="color:red" >Read this entire article for free, simply activate your free 7 day trial access to Securities Regulation & Law Report now.</li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf5_field_2" id="cf5_field_2" value="SRLR"/></li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf5_field_3" id="cf5_field_3" value="May 21, 2013"/></li>
			<li id="li-5-4" class=""><label for="cf5_field_4"><span>First Name</span></label><input type="text" name="cf5_field_4" id="cf5_field_4" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-5-5" class=""><label for="cf5_field_5"><span>Last Name</span></label><input type="text" name="cf5_field_5" id="cf5_field_5" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-5-6" class=""><label for="cf5_field_6"><span>Email</span></label><input type="text" name="cf5_field_6" id="cf5_field_6" class="single fldemail fldrequired" value=""/><span class="emailreqtxt">(valid email required)</span></li>
			<li id="li-5-7" class=""><label for="cf5_field_7"><span>Job Title</span></label><input type="text" name="cf5_field_7" id="cf5_field_7" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-8" class=""><label for="cf5_field_8"><span>Organisation</span></label><input type="text" name="cf5_field_8" id="cf5_field_8" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-9" class=""><label for="cf5_field_9"><span>Address</span></label><input type="text" name="cf5_field_9" id="cf5_field_9" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-10" class=""><label for="cf5_field_10"><span>Address 2</span></label><input type="text" name="cf5_field_10" id="cf5_field_10" class="single" value=""/></li>
			<li id="li-5-11" class=""><label for="cf5_field_11"><span>City</span></label><input type="text" name="cf5_field_11" id="cf5_field_11" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-12" class=""><label for="cf5_field_12"><span>ZIP/Postal Code</span></label><input type="text" name="cf5_field_12" id="cf5_field_12" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-13" class=""><label for="cf5_field_13"><span>Country</span></label><input type="text" name="cf5_field_13" id="cf5_field_13" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-14" class=""><label for="cf5_field_14"><span>Phone</span></label><input type="text" name="cf5_field_14" id="cf5_field_14" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-15" class=""><label for="cforms_captcha5" class="seccap"><span>Verification</span></label><input type="text" name="cforms_captcha5" id="cforms_captcha5" class="secinput" value=""/><img id="cf_captcha_img5" class="captcha" src="http://www.uslawwatch.com/wp-content/plugins/cforms/cforms-captcha.php?ts=5&amp;c1=4&amp;c2=5&amp;ac=abcdefghijkmnpqrstuvwxyz23456789&amp;i=i&amp;w=115&amp;h=35&amp;c=2B3AFF&amp;l=547FA9&amp;f=font32.ttf&amp;a1=-5&amp;a2=5&amp;f1=17&amp;f2=19&amp;b=16.gif" alt=""/><a title="reset captcha image" href="javascript:reset_captcha('5')"><img class="captcha-reset" src="http://www.uslawwatch.com/wp-content/plugins/cforms/images/spacer.gif" alt="Captcha"/></a></li>
			<li id="li-5-16" class=""><input type="checkbox" name="cf5_field_16" id="cf5_field_16" class="cf-box-a" checked="checked"/><label for="cf5_field_16" class="cf-after"><span>I would like to receive occasional emails about product updates and special offers</span></label></li>
		</ol>
		<fieldset class="cf_hidden">
			<legend>&nbsp;</legend>
			<input type="hidden" name="cf_working5" id="cf_working5" value="One%20moment%20please..."/>
			<input type="hidden" name="cf_failure5" id="cf_failure5" value="Please%20fill%20in%20all%20the%20required%20fields."/>
			<input type="hidden" name="cf_codeerr5" id="cf_codeerr5" value="Please%20double-check%20your%20verification%20code."/>
			<input type="hidden" name="cf_customerr5" id="cf_customerr5" value="yyy"/>
			<input type="hidden" name="cf_popup5" id="cf_popup5" value="yy"/>
		</fieldset>
		<p class="cf-sb"><input type="submit" name="sendbutton5" id="sendbutton5" class="sendbutton" value="Activate Free Access"/></p></form><p class="linklove" id="ll5"><a href="http://www.deliciousdays.com/cforms-plugin"><em>cforms</em> contact form by delicious:days</a></p>

<a href="http://twitter.com/?status=RT%20%40%3A%20BNA%20INSIGHTS%3A%20Top%20Ten%20SEC%20Enforcement%20Developments%20of%202012%20-%20U.S.%20Law%20Watch%20http%3A%2F%2Ftinyurl.com%2Fbmcver2" class="tweet-this" ><img src="http://www.uslawwatch.com/wp-content/plugins/simple-tweet/img/tweet.gif" title="Tweet this!" alt="Tweet this!" />Tweet this!</a>]]></content:encoded>
			<wfw:commentRss>http://www.uslawwatch.com/2013/04/09/finance/bna-insights-top-ten-sec-enforcement-developments-2012/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>2012 Trends in Patent Case Filings and Venue: Eastern District of Texas Most Popular for Plaintiffs (Again) But 11 Percent Fewer Defendants Named Nationwide</title>
		<link>http://www.uslawwatch.com/2013/02/18/intellectual-property/2012-trends-patent-case-filings-venue-eastern-district-texas-popular-plaintiffs-11-percent-defendants-named-nationwide/</link>
		<comments>http://www.uslawwatch.com/2013/02/18/intellectual-property/2012-trends-patent-case-filings-venue-eastern-district-texas-popular-plaintiffs-11-percent-defendants-named-nationwide/#comments</comments>
		<pubDate>Mon, 18 Feb 2013 17:21:59 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Intellectual Property]]></category>
		<category><![CDATA[consolidation]]></category>
		<category><![CDATA[joinder]]></category>
		<category><![CDATA[Patent Infringement]]></category>

		<guid isPermaLink="false">http://www.uslawwatch.com/?p=6152</guid>
		<description><![CDATA[This article presents the 2012 patent case filing statistics. It then compares those numbers to case filings in 2011 and explores possible reasons for the changes, including how districts and district judges have reacted to continued venue challenges...]]></description>
				<content:encoded><![CDATA[<p><img alt="James C. Pistorino" src="http://iplaw.bna.com/iprc/core_adp/get_object/im193503.png" /></p>
<p><em>By <strong>James C. Pistorino</strong></em></p>
<div><em>James Pistorino is a patent litigation partner in the Palo Alto, Calif., office of Perkins Coie.</p>
<p></em></div>
<h4>I. Introduction</h4>
<p>The year 2011 closed with the U.S. District Court for the District of Delaware becoming the most popular place for plaintiffs to file patent litigation after the effective date of the America Invents Act. <sup>1</sup> From Sept. 16, 2011, when the AIA went into effect, through the end of 2011, more cases by more plaintiffs naming more defendants were filed in the District of Delaware than in any other district in the nation. The Eastern District of Texas dropped to being only the second most popular place for plaintiffs to bring patent infringement suits. Thus, to the extent that the AIA was intended to reduce the volume of cases in the Eastern District of Texas, it appeared to be working.</p>
<div style="padding-left: 30px;"><sup>1</sup> See James Pistorino &amp; Susan Crane, “2011 Trends in Patent Case Filings, Eastern District of Texas Continues to Lead Until America Invents Act Is Signed,” 83 PCTJ 710 (Mar. 17, 2012).</div>
<p><img id="im212512" alt="Figure 1. Jurisdictions with the Most Defendants in Patent Litigation in 2012" src="http://iplaw.bna.com/iprc/core_adp/get_object/im212512.png" width="589" height="248" /></p>
<p>A full calendar year with the AIA in effect has now passed, and the AIA&#8217;s longer term effects on patent litigation have begun to emerge. The 2012 case filing data lead to four important takeaways:</p>
<p style="padding-left: 30px;">•  The districts have returned to their pre-AIA rankings, with the Eastern District of Texas regaining the crown as the most popular place for plaintiffs to file patent suits and the District of Delaware somewhat behind in second place.</p>
<p style="padding-left: 30px;">•  The concentration of patent cases in the Eastern District of Texas and the District of Delaware remains very high, with approximately 40 percent of all patent cases brought and 37 percent of all defendants named in those two districts alone.</p>
<p style="padding-left: 30px;">•  Compared to 2011, there was an 11 percent decrease in the number of defendants named in patent cases nationwide, with over 15 percent fewer defendants named in the Eastern District of Texas and District of Delaware.</p>
<p style="padding-left: 30px;">•  Probably as a result of the joinder provisions of the AIA, patent plaintiffs filed 52 percent more cases in 2012, and the average number of defendants in each case dropped to less than three in nearly all the top 10 districts.</p>
<p>Overall, the AIA does not appear to have substantially reduced patent case concentration in the two small districts that are most popular with plaintiffs. Nevertheless, the AIA has reduced the number of defendants named in each case and may have reduced the total number of defendants somewhat.</p>
<p>This article begins by presenting the 2012 patent case filing statistics. It then compares those numbers to case filings in 2011 and explores possible reasons for the changes, including how districts and district judges have reacted to continued venue challenges.</p>
<h5>A. The Data Sources</h5>
<p>Docket data on patent lawsuit filings across the United States from Jan. 1, 2012, to Dec. 31, 2012, were retrieved from PACER and compiled into a database. Pacer classifies each party in a suit as a plaintiff, defendant, or something else (e.g., intervenor, third-party plaintiff/defendant and counter/cross-claimant). The secondary classifications were filtered out and only the primary plaintiff(s) and defendant(s) were examined. For the year 2012, the dataset included information on 21,541 parties involved in 5,584 cases. Combined with previous analyses of cases between 1999 and 2011, the dataset includes information on 179,638 parties involved in 41,747 cases. <sup>2</sup></p>
<p style="padding-left: 30px;"><sup>2</sup> Some aspects of the Pacer dataset bear noting. First, it includes both information from the original case filing and any later added parties. Thus, the reported numbers are not a perfect reflection of the actions at the time of filing. Second, the data used in this article were retrieved from Pacer on Jan. 20, 2013, and represent a complete retrieval of all data for the year 2012. By contrast, earlier data reported for 2012 were based on data sampled periodically throughout the year. Third, the dataset only classifies parties as plaintiffs or defendants; it does not classify the parties as patentees or accused infringers. Thus, in actions seeking a declaratory judgment of noninfringement or invalidity, the parties bringing seeking declaratory relief, the accused infringers will be classified as the plaintiffs and the patent owners will be classified as the defendants. Fourth, named plaintiffs and defendants are counted each time they appear as a party. Thus, a single party that brings four lawsuits alleging patent infringement is counted as four plaintiffs in the reported data. Fifth, only cases coded as patent cases (code 830) were pulled. Cases that began as, say, copyright, trade secret, or breach of contract actions may not have been coded as patent cases. Finally, neither the Court of Federal Claims nor the International Trade Commission fully participate in Pacer, so patent cases filed there are not included.</p>
<p>Because of the passage of the AIA, no effort was made to identify false marking cases filed in 2012. The AIA effectively limited private false marking cases to those brought by competitors seeking only actual damages and rendered marking with an expired patent number non-actionable. See 35 U.S.C. §292(b) and (c). As a result, false marking cases have been all but eliminated, and they should not materially affect analysis of the larger trends. Slightly more than 1,000 false marking cases were filed in 2010 and 2011 and they have been excluded from the datasets for those years so that trends in traditional patent infringement cases can be analyzed.</p>
<h4>B. 2012 Patent Filing Statistics</h4>
<p>As shown in Table 1, the Eastern District of Texas led the nation in patent infringement case filings in 2012 based on: (a) the number of cases; (b) the number of plaintiffs; and (c) the number of defendants. In 2012, the average case in the Eastern District of Texas involved a single plaintiff suing two defendants (often corporate relatives). By comparison, in 2010, the average non-false-marking case in the Eastern District of Texas involved 13 defendants and the average case for the pre-AIA period in 2011 had 10 defendants.</p>
<p><img id="im212518" alt="Table 1. Top Ten Jurisdictions with the Most Patent Cases in 2012" src="http://iplaw.bna.com/iprc/core_adp/get_object/im212518.png" width="630" height="326" /></p>
<p>Noteworthy in Table 1 is the general decrease in the number of defendants per case across all districts. In 2011 (even including the period after the enactment of the AIA), 8 of the top 10 districts averaged more than 3 defendants per case. In 2012, all but one of the top 10 districts averaged fewer than 3 defendants per case.</p>
<p>Table 2 shows the data of Table 1 as a percentage of the national totals. As an absolute number, nearly 21 percent of all the defendants named in patent cases filed in 2012 were sued in the Eastern District of Texas. By comparison, the District of Delaware accounted for 16 percent, the Central District of California accounted for nearly 12 percent, and no other district accounted for 6 percent or more.</p>
<p><img id="im212519" alt="Table 2. Top Ten Jurisdictions with the Most Patent Cases in 2012" src="http://iplaw.bna.com/iprc/core_adp/get_object/im212519.png" width="630" height="327" /></p>
<p>For ease of comparison, Table 3 shows the 2012 and 2011 data and calculates the percentage change year over year. Compared to 2011, the number of cases non-false-marking cases increased from 3,660 to 5,584 (52 percent), the number of plaintiffs increased from 6,119 to 8,894 (45 percent), while the number of defendants dropped from 14,201 to 12,647 (decrease of 11 percent).</p>
<p><img id="im212520" alt="Table 3. Top Ten Jurisdictions 2012 vs. 2011" src="http://iplaw.bna.com/iprc/core_adp/get_object/im212520.png" width="630" height="325" /></p>
<p>The decrease in the number of defendants named in the Eastern District of Texas and the District of Delaware was significant, with both districts seeing a drop of over 15 percent. The 2012 filings are generally in line with the 2011 filings in that seven of the top 10 districts in 2011 were again in the top 10 in 2012, with the Eastern District of Texas and the District of Delaware occupying the top two spots. Figure 2 depicts the combined Eastern District of Texas and District of Delaware case filings from 2000-2012 as a percentage of the national totals.</p>
<p><img id="im212513" alt="Figure 2. Patent Litigation in E.D. Texas and Delaware as a Percentage of National Totals 2000-2012" src="http://iplaw.bna.com/iprc/core_adp/get_object/im212513.png" width="586" height="242" /></p>
<h4>II. What Explains the 2012 Filings</h4>
<h5>A. AIA Joinder Provision</h5>
<p>One important provision of the AIA that affects case filings relates to joinder. Before passage of the AIA, numerous defendants (including direct competitors) were frequently named in a single case based on the fact that the same patent was allegedly infringed—regardless of differences in the products accused of infringing. This practice was most pronounced in the Eastern District of Texas, where, on average, 13 defendants were named in each non-false-marking patent case filed in 2010. That figure decreased slightly in 2011 to 10 defendants per case through Sept. 16, 2011, when the president signed the AIA and the new joinder statute went into effect.</p>
<p>The AIA generally precludes joining multiple defendants in the same lawsuit unless the same product or process is accused of infringement. Before the AIA, tens of defendants with different accused products could be joined in a single suit alleging infringement of the same patent, and that practice was especially prevalent in the Eastern District of Texas. After the AIA, the same plaintiff wishing to bring suit against the same defendants would need to bring numerous separate suits. Thus, it is not surprising that AIA joinder provisions would result in an increase in the absolute number of cases and plaintiffs, and that is what the data indicate: the number of cases increased by 52 percent, and the number of plaintiffs increased by 45 percent over the 2011 figures.</p>
<p>In 2011, including the period after the AIA went into effect, there were 790 same-day, same-district plaintiffs in non-false-marking cases. That is, 790 times the same plaintiff had already filed a patent infringement case on that same day in that same district. By contrast, in 2012, there were 3,266 same-day, same-district plaintiffs. The difference (2,476) closely matches the increase in the number of plaintiffs between 2012 and 2011 (2,775). Thus, it appears that nearly 90 percent of the increase in plaintiffs can be attributed to multiple, same-day, same-district filings presumably resulting from the AIA&#8217;s stricter joinder provisions.</p>
<p>Conversely, the AIA joinder provisions predictably resulted in a decrease in the number of defendants. In the pre-AIA period, the marginal cost of adding another defendant was low. Post-AIA, however, adding a new defendant requires filing another suit. Moreover, it is more likely (although not certain) that the case will be treated as a separate matter. The data suggest that the plaintiffs found that benefits from suing marginal defendants did not justify the increased burdens. As indicated above, there was a decrease of approximately 11 percent in the number of defendants named in 2012 over 2011. Of course, it is possible that there were simply fewer defendants to name in 2012 than in 2011. That seems unlikely, but 2013 may provide more information.</p>
<p><img id="im212514" alt="Figure 3. Patent Litigation in E.D. Texas 2000-2012" src="http://iplaw.bna.com/iprc/core_adp/get_object/im212514.png" width="586" height="239" /></p>
<p><span style="color: #ffffff;">.</span></p>
<p><img id="im212515" alt="Figure 4. Patent Litigation in E.D. Texas as a Percentage of National Totals 2000-2012" src="http://iplaw.bna.com/iprc/core_adp/get_object/im212515.png" width="585" height="242" /></p>
<h5>B. The Eastern District of Texas</h5>
<p>Figures 3 and 4 depict filings in the Eastern District of Texas from 2000-2012. Figure 3 reports the actual number of cases, plaintiffs and defendants, while Figure 4 reports the parties (combined plaintiffs and defendants) and cases as a percentage of national totals. As the figures show, there has actually been a reduction in both the absolute number and percentage of defendants named in the Eastern District of Texas from the 2010 peak. Nevertheless, the district is still the most popular with plaintiffs, and nearly 21 percent of all defendants were named in this single district in 2012.</p>
<p>Courts in the Eastern District of Texas continue to issue rulings that have the effect of keeping cases in the district even in the face of legislative changes and previous mandamus rulings by the U.S. Court of Appeals for the Federal Circuit.</p>
<h6>(i) Joinder in Pre-AIA Cases.</h6>
<p>In the week between passage of the AIA by Congress and the President&#8217;s signature, more than 1,500 defendants were named in patent cases in an apparent effort to avoid the non-retroactive AIA joinder provisions that would take effect. Indeed, more than 700 defendants were named in the Eastern District of Texas during that week with an average 13 defendants per case. <sup>3</sup> Thus, while the AIA joinder provisions will guide cases going forward, a substantial volume of pre-AIA cases with large numbers of defendants remain and those cases are not governed by the AIA.</p>
<div style="padding-left: 30px;"><sup>3</sup> See 2011 Trends (Table 7, Figure 5).</div>
<p>The Federal Circuit addressed joinder standards in pre-AIA cases in a mandamus decision, In re EMC Corp. <sup>4</sup> The plaintiff, Oasis Research L.L.C., filed suit in August 2010 naming 16 unrelated defendants and asserting that Oasis&#8217;s principal place of business was in Marshall, Texas. In November 2010, several defendants moved to dismiss, sever, and/or transfer to various districts alleging, among other things, that Oasis alleged presence in Marshall was a sham created solely to manufacture venue. In May 2011, Magistrate Judge Amos L. Mazzant issued reports and recommendations denying all the motions to dismiss. Finding that the actions were “not dramatically different,” the magistrate judge recommended denying all the severance motions and, as a result, denying transfer.</p>
<div style="padding-left: 30px;"><sup>4</sup> 677 F.3d 1351, 102 U.S.P.Q.2d 1539 (Fed. Cir. 2012) (84 PTCJ 54, 5/11/12).</div>
<p>In July 2011, District Judge Michael H. Schneider adopted the magistrate&#8217;s recommendations and refused to sever or transfer. The day before Congress passed the AIA, three defendants sought a writ of mandamus, arguing “not dramatically different” was not the appropriate standard for evaluating misjoinder under Fed. R. Civ. P. 20 and that their cases should be severed and transferred to other districts.</p>
<p>On review, the Federal Circuit confirmed that the AIA joinder provisions were not retroactive, but nevertheless held that in pre-AIA cases, independent defendants may be joined in a single case only where the accused products or processes “are the same in respects relevant to the patent” and that merely practicing the same alleged patent is not sufficient. <sup>5</sup> “Unless there is an actual link between the facts underlying each claim of infringement,” the Federal Circuit held, “independently developed products using differently sourced parts are not part of the same transaction, even if they are otherwise coincidentally identical.” <sup>6</sup></p>
<div style="padding-left: 30px;"><sup>5</sup> In re EMC Corp., 677 F.3d at 1359.</div>
<div style="padding-left: 30px;"><sup>6</sup> Id.</div>
<p>Although that standard did not exactly track the AIA&#8217;s requirement that the “same product or process” be accused, it was quite similar and far removed from the “not dramatically different” standard used by the district court. Rather than addressing severance and transfer in the first instance, the Federal Circuit remanded for the district court to reanalyze under the proper standard. <sup>7</sup></p>
<div style="padding-left: 30px;"><sup>7</sup> On remand in EMC, the district court severed the defendants but then consolidated the cases for everything except venue considerations and trial. It also denied the defendants&#8217; motions for transfer on the ground, among others, that judicial economy would not be served because the court had invested so much effort in the case in the nearly two years since the defendants moved to transfer. Several defendants petitioned for writs of mandamus ordering transfer, but the same panel of Federal Circuit judges denied relief in a nonprecedential decision. <em>In re</em> <em>EMC Corp</em>., Misc. No. 142 (Fed. Cir. Jan. 29, 2013) (non-precedential). In the Federal Circuit&#8217;s view, it could not conclude that there was a “clear” abuse of discretion in this situation and stressed the importance of the district court addressing transfer “at the outset of the litigation.” While the Federal Circuit held that it was not proper to rely on later events when considering transfer, it believed that, viewed at the time of the original transfer motion, the district court could have properly looked to the fact that other cases were pending at the time of the original motion in considering judicial economy. Thus, the writ was denied.</div>
<h6>(ii) Non-Rulings.</h6>
<p>In some cases, Eastern District of Texas judges have simply not ruled on transfer motions for extended periods of time. For example, in <em>Software Rights Archive L.L.C. v. Google Inc.</em>, Google filed a motion to transfer in February 2009. <sup>8</sup> Having received no ruling on the motion by July 2010, Google filed a petition for a writ of mandamus with the Federal Circuit seeking an order compelling the district court to rule on the motion. Within days, the district court took up the motion and granted transfer before the Federal Circuit ruled.</p>
<div style="padding-left: 30px;"><sup>8</sup> No. 07-cv-00511-CE (E.D. Tex).</div>
<p>In <em>SimpleAir Inc. v. AWS Convergence Technologies Inc.</em>, the defendants filed a motion to transfer in March 2010. Magistrate Judge Chad Everingham did not rule until June 2011 and then denied the motion. The defendants petitioned for a writ of mandamus, but the Federal Circuit denied relief, noting, among other things, that they “failed to employ any strategy to pressure the district court to act, such as seeking mandamus to direct the district court to rule on the motion” and also waited over three months after the transfer motion to seek writ relief. <sup>9</sup></p>
<div style="padding-left: 30px;"><sup>9</sup> <em>In re Apple Inc.</em>, Misc. No. 103 (Fed. Cir. Jan. 12, 2012).</div>
<p>Of course, defendants may be reluctant to seek mandamus directing district courts to rule on severance and venue issues out of concerns that they might antagonize the district judge who may still need to rule on the merits, and/or that the Federal Circuit may treat a petition as premature if the defendants do not wait long enough for the district court to rule.</p>
<p>On the other hand, defendants may be encouraged by the Federal Circuit&#8217;s recent (albeit nonprecedential) decision in the second EMC mandamus petition in which the Court denied mandamus, but stressed “the importance of addressing motions to transfer at the outset of litigation,” that such motions should have “top priority,” and that “Congress&#8217; intent ’to prevent the waste of time, energy and money and to protect litigants, witnesses and the public against unnecessary inconvenience and expense,’ &#8230; may be thwarted where … defendants must partake in years of litigation prior to a determination on a transfer motion.” <sup>10</sup> It is too early to tell whether that decision will result in more prompt rulings.</p>
<div style="padding-left: 30px;"><sup>10</sup> <em>In re EMC Corp.</em>, Misc. No. 142, slip op. 4 (Fed. Cir. Jan. 29, 2013).</div>
<h6>(iii) Consolidation of Cases for Pre-Trial Purposes and Deferring Transfer Until After Claim Construction.</h6>
<p>One of the most remarkable decisions of 2012 occurred in <em>Norman IP Holdings L.L.C. v. Lexmark International Inc</em>. <sup>11</sup> The day before the AIA was signed into law (Sept. 15, 2011), Norman IP filed one lawsuit in the Eastern District of Texas naming two defendants. Norman then filed a series of amended complaints in that suit naming additional, unrelated defendants so that by January 2012, 18 defendants had been named.</p>
<p>&nbsp;</p>
<div style="padding-left: 30px;"><sup>11</sup> No. 11-cv-00495-LED (E.D. Tex.).</div>
<p>In August 2012, Chief District Judge Leonard E. Davis issued an order addressing numerous motions to dismiss or transfer claims against various defendants for misjoinder and convenience. In light of EMC, the court severed the cases against the various defendants. Nevertheless, the court further ruled that the cases would be consolidated for all pretrial purposes other than venue determination and that any transfer of venue would not take effect until after the court issued its claim constructions. Further the court stated:</p>
<p>This Court has limited resources and constantly strives to employ efficient and cost-saving case-management procedures for the benefit of the parties, counsel, and the Court. In response to the AIA&#8217;s joinder provision, plaintiffs now serially file multiple single-defendant (or defendant group) cases involving the same underlying patents. This presents administrative challenges for the Court and, left unchecked, wastes judicial resources by requiring common issues to be addressed individually for each case. For example, what was once a single motion to substitute parties (or join a plaintiff) becomes multiple motions. These must each be processed by the Court and staff, including review of the underlying motions and docketing individual orders addressing each motion. More substantive motions, particularly where the same arguments are used in each individual case, present even more difficulties. There, the Court is required to waste time digesting duplicate arguments to ensure that new arguments are not hidden among the plethora of common arguments. … Thus, to permit efficient case management, the Court ORDERS these newly severed actions consolidated with the original filed case as to all issues, except venue, through pretrial only.</p>
<div>
<p>Motions to transfer venue under 28 U.S.C. §1404(a) will be considered only as to the defendants in the severed case, not as to all defendants in the pretrial consolidated cases. For instance, the Court&#8217;s analysis of GM&#8217;s Motion to Transfer (Docket No. 195) will only consider GM and Norman in the transfer analysis. However, in the event that transfer is appropriate, the Court shall retain the case through the Markman phase of the proceedings. Once the Markman opinion issues, any pending orders to transfer shall become effective. This serves two important purposes. First, it conserves judicial resources by requiring only one district court to address the underlying disputed claim terms. The claim construction process requires a thorough understanding of the technology at issue, often demanding substantial investment of time and energy. It does not make sense for two courts to plow the same ground. Second, this case management approach ensures that the related patent cases proceed initially on a consistent claim construction, thus avoiding inconsistent rulings.</p>
</div>
<p>However, this case management approach should not be perceived as an invitation to file motions to transfer venue. In recent years, this Court has expended considerable time addressing venue. This Court has many, many, issues before it—both criminal and civil—and it carries one of the heaviest patent dockets in the country; yet, venue in patent cases has increasingly become an extremely expensive and time-consuming matter, not only for the Court but for the parties as well. For instance, in a recent set of serially filed cases involving only seven defendant groups, the parties had already expended over $700,000 on venue-related discovery and briefing before the cases were even ready for status conference (i.e., before all defendants had answered the complaint). This Court currently has approximately forty pending motions to transfer venue. If the average costs of discovery and briefing for each of these transfer motions is only $300,000, then approximately $12 million is being spent by the parties on an issue that does not move the ball down the field, but only seeks a new field upon which to play. Finally, some parties have even called courts in this district to essentially “threaten” mandamus if a venue ruling is not issued within the timeframe desired by the parties. This Court manages a very busy docket—as do all courts in this district—with pending motions of varying levels of priority. Criminal cases take first priority because individuals&#8217; freedom is at stake. In the patent context, trials and Markman hearings are a high priority. Venue motions are important, but not any more important than everything else this court has to do. The court rules on these motions as soon as it can. The Civil Justice Reform Act of 1990 was instituted to provide checks on long-pending motions and cases. Courts in this district take their cases seriously and strive to timely address pending motions in an effort to resolve cases promptly. This Court will address motions to transfer venue as timely as possible, while balancing the many other issues unrelated to venue requiring the court&#8217;s attention. <sup>12</sup></p>
<div style="padding-left: 30px;"><sup>12</sup> No. 11-cv-00495, Dkt. No. 253 at 6-10 (Aug. 10, 2012).</div>
<p>Whether other district judges will follow this lead, and whether the Federal Circuit will endorse this approach, remains to be seen. <sup>13</sup></p>
<div style="padding-left: 30px;"><sup>13</sup> In support of the statement that the Eastern District of Texas strives to timely address pending motions, the Norman IP decision cited to the Civil Justice Reform Act Report of September 2011 showing only 16 motions pending for more than 6 months within the Eastern District of Texas as of Sept. 30, 2011. It is not clear that that report is a reliable indicator of the pendency of motions. For example, the motion to transfer filed in the SimpleAir case did not appear on any of the September 2010, March 2011, September 2011, or March 2012 reports despite the fact that the motion was pending from March 2010 through June 2011 (i.e., more than twice the six month reporting period).</div>
<h6>iv) Denials of Writ Relief by the Federal Circuit.</h6>
<p>Although the Federal Circuit has granted mandamus to force transfers of venue in some cases, it has made clear that such relief will be granted only in extreme cases where it considers a district court&#8217;s ruling to be beyond the pale of reasonableness.</p>
<p>For example, in <em>In re Amazon.com Inc.</em>, the Federal Circuit refused to order transfer to a district (the Western District of Texas) where none of the defendants was headquartered. According to the panel, the fact that none of the defendants was headquartered in the proposed forum made the situation significantly different from other cases where mandamus was granted. <sup>14</sup></p>
<div style="padding-left: 30px;"><sup>14</sup> Misc. No. 115 (Fed. Cir. May 1, 2012).</div>
<p>Mandamus to transfer was also denied in <em>In re Vicor Corp</em>.. There, both the district court and the Federal Circuit focused on the fact that an earlier case that involved the defendants&#8217; products (albeit different defendants) had been litigated in the Eastern District of Texas (albeit before a different judge). The newly assigned judge (Schneider) retained jurisdiction over that case for post-injunction damages and contempt issues. In the Federal Circuit&#8217;s view, the petitioner did not make a compelling showing that there was insufficient overlap between the earlier case and the current one such that judicial economy would not be gained. <sup>15</sup></p>
<div style="padding-left: 30px;"><sup>15</sup> Misc. No. 123 (Fed Cir. July 26, 2012).</div>
<p>Writ relief was also denied in<em> In re Fusion-Io Inc</em>. There, the plaintiff filed suit nine days before the AIA was signed, naming nine unrelated defendants. One of the defendants (Fusion-Io) filed a motion to sever and transfer in January 2012, before answering. In September 2012, Judge James Rodney Gilstrap severed the parties and denied the motions to transfer without prejudice, indicating that the defendants could file new motions to transfer that only addressed their severed case.</p>
<p>Fusion-Io first sought reconsideration of denial of its transfer motion in light of the fact that its original motion filed in January had addressed only the circumstances of its case and re-filing the same motion again would merely lead to delay. After the district court denied reconsideration, Fusion-Io sought a writ. The Federal Circuit denied relief, indicating that it would not weigh the facts on transfer before the district court. Nevertheless, the Federal Circuit suggested that Fusion-Io promptly re-file its motion to transfer with the district court along with a motion to stay and indicated that the district court should take up those motions before proceeding to any motion on the merits of the case. <sup>16</sup></p>
<div style="padding-left: 30px;"><sup>16</sup> Misc. No. 139 (Fed. Cir. Dec. 21, 2012). The district court did stay the case with respect to <em>Fusion-Io</em> and ordered an evidentiary hearing before the magistrate judge on the transfer motion. At the hearing, the Court issued an oral order denying the motion to transfer and lifted the stay. Fusion-Io&#8217;s objections to the magistrate judge&#8217;s decision remain pending.</div>
<p>The Federal Circuit also refused to order transfer in <em>In re HTC Corp</em>. There again, the district court and the Federal Circuit focused on the fact that the proposed transfer district (the Northern District of California) was not the headquarters district of either of the parties (although it did contain the headquarters for a third party, Google, whose relevance to the case was disputed). HTC&#8217;s relatively recent change of incorporation from Texas to Washington and refusal to waive privilege to disclose the reasons for that move were also noted. <sup>17</sup></p>
<div style="padding-left: 30px;"><sup>17</sup> Misc. No. 130 (Fed. Cir. Sept. 20, 2012).</div>
<h6>v) Judge Selections by Plaintiffs.</h6>
<p>As noted in a previous article, the Eastern District of Texas allows plaintiffs to influence which district judge is assigned to their case because case assignments are allocated based on the division where the case was filed. <sup>18</sup> The Eastern District has several divisions, six of which are relevant to civil cases: <em>Beaumont</em> (division 1); <em>Marshall</em> (division 2); <em>Sherma</em>n (division 4); <em>Texarkana</em> (division 5);<em> Tyler</em> (division 6) and <em>Lufkin</em> (division 9). With the confirmation of Judge Gilstrap to replace Judge T. John Ward, case assignment practices were returned to those in place before Ward&#8217;s resignation. After a further general order dated Jan. 17, 2012, cases were assigned as follows:</p>
<p style="padding-left: 30px;">•  <em>Beaumont</em>—100 percent of patent cases to Judge Ron Clark;</p>
<p style="padding-left: 30px;">•  <em>Marshall</em>—75 percent of civil cases to Judge Gilstrap and 25 percent to Judge Schneider;</p>
<p style="padding-left: 30px;">•  <em>Sherman</em>—50 percent of civil cases to Judge Richard A. Schell and 50 percent to Judge Marcia A. Crone;</p>
<p style="padding-left: 30px;">•  <em>Texarkana</em>—90 percent of all cases to Schneider and 10 percent to Gilstrap;</p>
<p style="padding-left: 30px;">•  <em>Tyler</em>—95 percent of patent cases to Chief Judge Davis and 5 percent of patent cases to Schneider; and</p>
<div style="padding-left: 30px;">
<p>•  <em>Lufkin</em>—100 percent of patent cases to Clark.</p>
</div>
<div style="padding-left: 60px;"><sup>18</sup> See 2011 Trends at 7-8 (Table 8 and 9). See, e.g., Eastern District of Texas General Order Nos. 11-17, 12-3, and 13-2.</div>
<p>Table 4 shows the breakdown of cases and parties by division filing. As shown in the table, patent plaintiffs appear to have particular preferences for Davis and Gilstrap.</p>
<p><img id="im212521" alt="Table 4. E.D. Texas Case Filings by Division 2012" src="http://iplaw.bna.com/iprc/core_adp/get_object/im212521.png" width="316" height="197" /></p>
<h5>C. The District of Delaware</h5>
<p>Figures 5 and 6 show patent case filings in the District of Delaware from 2000-2012. Figure 5 reports the actual number of cases, plaintiffs and defendants, while Figure 6 reports the parties (combined plaintiffs and defendants) and cases as a percentage of the national totals. As the figures show, both the absolute number and percentage of defendants named in Delaware declined in 2012 from the 2011 peak. Nevertheless, the district is still the second popular district with plaintiffs, and more than 16 percent of all defendants were named in this single district in 2012.</p>
<p><img id="im212516" alt="Figure 5. Patent Litigation in Delaware 2000-2012" src="http://iplaw.bna.com/iprc/core_adp/get_object/im212516.png" width="585" height="242" /></p>
<p><span style="color: #ffffff;">.</span></p>
<p><img id="im212517" alt="Figure 6. Patent Litigation in Delaware as a Percentage of National Totals 2000-2012" src="http://iplaw.bna.com/iprc/core_adp/get_object/im212517.png" width="584" height="244" /></p>
<p>As in the Eastern District of Texas, courts in Delaware continue to issue rulings that have the affect of keeping cases in the district.</p>
<p>At the close of 2011, in<em> In re Link_A_Media Devices Corp</em>., <sup>19</sup> the Federal Circuit issued a writ of mandamus ordering a case transferred from the District of Delaware. At issue in that case was the focus of District Court Judge Sue L. Robinson on the fact that the defendants were incorporated in Delaware. Although the dispute otherwise had little or no connection with Delaware, the district court denied a motion to transfer holding: “… because all [the] defendants are incorporated in Delaware, they have no reason to complain about being sued in Delaware.”</p>
<div style="padding-left: 30px;"><sup>19</sup> 662 F.3d 1221, 100 U.S.P.Q.2d 1865 (Fed. Cir. 2011) (83 PTCJ 185, 12/9/11).</div>
<p>On the writ of mandamus, the Federal Circuit ordered the case transferred, noting that place of incorporation is not a factor listed for consideration in either 28 U.S.C. §1404 or Third Circuit case law. In the Federal Circuit&#8217;s view, the place of incorporation should not have been given “dispositive” weight, and placing “heavy reliance” on place of incorporation was inappropriate. <sup>20</sup></p>
<div style="padding-left: 30px;"><sup>20</sup> 662 F.3d at 1223-24. In the wake of <em>Link_A_Media</em>, the Federal Circuit denied without prejudice another pending writ petition, directing the petitioner to seek reconsideration in light of <em>Link_A_Media. In re Trend Micro Inc</em>., Misc. No. 119 (Apr. 2, 2012). The defendant did so, through a series of motions, but the district court again denied transfer more than six months later.</div>
<p>If place of incorporation were removed as a consideration in transfer motions, it would be expected that many more cases should be subject to transfer from the District of Delaware because few companies have significant operations in Delaware. Nevertheless, Delaware district courts have distinguished <em>Link_A_Media</em> and the Federal Circuit has since refused to overturn a ruling denying transfer in a case where the district court continued to rely, in part, on the defendants&#8217; Delaware incorporation.</p>
<p>In <em>Intellectual Ventures I L.L.C. v. Altera Corp</em>, all the plaintiffs and the defendants were Delaware corporations with headquarters on the west coast (Washington and California) and none had offices or employees in Delaware. Further, the named inventors, prosecuting attorneys, and a number of potential witnesses resided in California. The defendants sought to transfer the case to the Northern District of California, where most of the defendants&#8217; accused products were developed and where the plaintiff also had an office.</p>
<p>Instead of the “heavy reliance” disapproved of in <em>Link_A_Media</em>, Delaware District Court Judge Leonard P. Stark placed “substantial weight” on place of incorporation and found that the convenience of the parties favored transfer, “but only slightly.” With regard to the convenience for the witnesses, the court first found that the location of party witnesses carried no weight in the “balance of convenience” because parties are required to produce witnesses wherever the case is pending. With regard to non-party witnesses (e,g., the inventors, prosecuting attorneys, or likely third-party witnesses), none of whom resided in Delaware or were within the subpoena power of the Delaware court, the court held that the relevant inquiry was only whether the witnesses were within the subpoena power of the court for trial.</p>
<p>Thereafter, the court held that the fact that the non-party witnesses were beyond the subpoena power of the court in Delaware for trial (but many would be within the subpoena power of the Northern District of California) favored transfer but was entitled to “little weight” because, in the court&#8217;s view, it would be “statistically rare” for a case to go to trial and witnesses could be presented by deposition in any event. The fact that none of the relevant evidence was in Delaware also favored transfer but was given “little weight” because of alleged technological advances. Weighing all the factors, the court found that the defendants had not shown that the factors strongly favored transfer. <sup>21</sup></p>
<div style="padding-left: 30px;"><sup>21</sup> <em>Intellectual Ventures I L.L.C. v. Altera Corp</em>, No. 10-1065-LPS, Dkt. No. 96 (D. Del. Jan. 23, 2012).</div>
<p>On a petition for mandamus, the Federal Circuit agreed that the place of incorporation could be considered and distinguished <em>Link_A_Media</em>, stating:</p>
<p>Although the circumstances here are in certain respects similar to those in the petition we granted in <em>Link_A_Media</em>, that precedent did not go so far as to limit the trial court&#8217;s discretion to deny transfer in this case. The trial court in <em>Link_A_Media</em> disposed of the transfer motion based on the plaintiff&#8217;s forum preference and the fact that the defendant had incorporated in Delaware. In doing so, the court failed to give any consideration to the fact that transfer would significantly minimize the travel and cost to the identified witnesses and move trial to where the accused products were developed. Because the court viewed those considerations as entirely superfluous, its error could not have been more clear. On that view, this case is clearly distinguishable; in its thorough opinion, the district court endeavored to evaluate each of the forum <em>non conveniens</em> factors in light of the same arguments raised in the petition, and there is no clear indication that the court failed to meaningfully consider the merits of the transfer motion. Moreover, … in this case, unlike <em>Link_A_Media</em>, there are rational grounds for denying transfer given that all of the parties (not just a single defendant) had incorporated in Delaware and some witnesses would potentially find Delaware more convenient. <sup>22</sup></p>
<div style="padding-left: 30px;"><sup>22</sup> <em>In re Altera Corp</em>., Misc. No. 121 (Fed. Cir. Jul. 20, 2012).</div>
<p>With this road map, transfer out of Delaware may be difficult in all but extreme cases.</p>
<h4>III. Conclusion</h4>
<p>Although the AIA appears to have had some effect on the absolute number of defendants in traditional patent cases, the effect on patent case concentration has been muted. In 2012, more than 40 percent of all the patent cases in the United States (with nearly an equal percentage of defendants) were filed in just two small districts with small numbers of like minded judges and policies seen as plaintiff-friendly.</p>
<p>Absent a sea change by one of the involved courts (e.g., random assignment of judges in the Eastern District of Texas, according more than “little weight” or “no weight” to the location of witnesses and documents in the convenience inquiry in Delaware), there is no reason to expect a reduction in patent case concentration. The Federal Circuit also appears to be less and less inclined to police refusals to transfer by writs of mandamus. Those desiring significant change in the venue situation may need to look to the Supreme Court or Congress for relief.</p>

		<div id="usermessagea" class="cf_info "></div>
		<form enctype="multipart/form-data" action="/feed/#usermessagea" method="post" class="cform contact-form " id="cformsform">
		<ol class="cf-ol">
			<li id="li--1" class="textonly" style="color:red" >Read this entire article for free, simply activate your free 7 day trial access now.</li>
		</ol>
		<fieldset class="cf-fs1">
		<legend>Contact Bloomberg BNA</legend>
		<ol class="cf-ol">
			<li id="li--3" class=""><label for="cf_field_3"><span>Your Name</span></label><input type="text" name="cf_field_3" id="cf_field_3" class="single fldrequired" value="Your Name" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li--4" class=""><label for="cf_field_4"><span>Email</span></label><input type="text" name="cf_field_4" id="cf_field_4" class="single fldemail fldrequired" value=""/><span class="emailreqtxt">(valid email required)</span></li>
			<li id="li--5" class=""><label for="cf_field_5"><span>Message</span></label><textarea cols="30" rows="8" name="cf_field_5" id="cf_field_5" class="area"></textarea></li>
			<li id="li--6" class=""><label for="cforms_captcha" class="seccap"><span>Verification</span></label><input type="text" name="cforms_captcha" id="cforms_captcha" class="secinput" value=""/><img id="cf_captcha_img" class="captcha" src="http://www.uslawwatch.com/wp-content/plugins/cforms/cforms-captcha.php?ts=&amp;c1=4&amp;c2=5&amp;ac=abcdefghijkmnpqrstuvwxyz23456789&amp;i=i&amp;w=115&amp;h=35&amp;c=2B3AFF&amp;l=547FA9&amp;f=font32.ttf&amp;a1=-5&amp;a2=5&amp;f1=17&amp;f2=19&amp;b=16.gif" alt=""/><a title="reset captcha image" href="javascript:reset_captcha('')"><img class="captcha-reset" src="http://www.uslawwatch.com/wp-content/plugins/cforms/images/spacer.gif" alt="Captcha"/></a></li>
		</ol>
		</fieldset>
		<fieldset class="cf_hidden">
			<legend>&nbsp;</legend>
			<input type="hidden" name="cf_working" id="cf_working" value="One%20moment%20please..."/>
			<input type="hidden" name="cf_failure" id="cf_failure" value="Please%20fill%20in%20all%20the%20required%20fields."/>
			<input type="hidden" name="cf_codeerr" id="cf_codeerr" value="Please%20double-check%20your%20verification%20code."/>
			<input type="hidden" name="cf_customerr" id="cf_customerr" value="yyy"/>
			<input type="hidden" name="cf_popup" id="cf_popup" value="nn"/>
		</fieldset>
		<p class="cf-sb"><input type="submit" name="sendbutton" id="sendbutton" class="sendbutton" value="Submit"/></p></form><p class="linklove" id="ll"><a href="http://www.deliciousdays.com/cforms-plugin"><em>cforms</em> contact form by delicious:days</a></p>		<div id="usermessageb" class="cf_info " ></div>


<a href="http://twitter.com/?status=RT%20%40%3A%202012%20Trends%20in%20Patent%20Case%20Filings%20and%20Venue%3A%20Eastern%20District%20of%20Texas%20Most%20Popular%20for%20Plaintiffs%20%28Again%29%20But%2011%20Percent%20Fewer%20Defendants%20Named%20Nationwide%20-%20U.S.%20Law%20Watch%20http%3A%2F%2Ftinyurl.com%2Fattb77u" class="tweet-this" ><img src="http://www.uslawwatch.com/wp-content/plugins/simple-tweet/img/tweet.gif" title="Tweet this!" alt="Tweet this!" />Tweet this!</a>]]></content:encoded>
			<wfw:commentRss>http://www.uslawwatch.com/2013/02/18/intellectual-property/2012-trends-patent-case-filings-venue-eastern-district-texas-popular-plaintiffs-11-percent-defendants-named-nationwide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Long-Awaited Foreign Account Tax Compliance Act Final Rules Issued by Government</title>
		<link>http://www.uslawwatch.com/2013/01/22/finance/longawaited-foreign-account-tax-compliance-act-final-rules-issued-government/</link>
		<comments>http://www.uslawwatch.com/2013/01/22/finance/longawaited-foreign-account-tax-compliance-act-final-rules-issued-government/#comments</comments>
		<pubDate>Tue, 22 Jan 2013 11:13:14 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[exchange of information]]></category>
		<category><![CDATA[federal tax]]></category>
		<category><![CDATA[foreign bank account reporting]]></category>
		<category><![CDATA[International Banking]]></category>
		<category><![CDATA[Tax Evasion]]></category>
		<category><![CDATA[Tax Havens]]></category>
		<category><![CDATA[withholding of tax]]></category>

		<guid isPermaLink="false">http://www.uslawwatch.com/?p=6149</guid>
		<description><![CDATA[The Treasury Department and the IRS issued long-awaited final rules, with changes intended to harmonize agreements negotiated with other countries. The 2010 law is intended to stop cross-border tax evasion...]]></description>
				<content:encoded><![CDATA[<p><em>By <strong>Alison Bennett.</strong></em></p>
<p>The Treasury Department and the Internal Revenue Service issued long-awaited final rules T.D. 9610 on the Foreign Account Tax Compliance Act Jan. 17, with changes intended to harmonize the rules with FATCA agreements negotiated with other countries.</p>
<p>The 2010 law is intended to stop cross-border tax evasion. It requires foreign financial institutions to tell the Internal Revenue Service about their U.S.-owned accounts. If the banks do not comply, they could face a 30 percent withholding tax on the accounts.</p>
<blockquote><p>“The final rules mark a critical milestone in international cooperation on these issues, and they provide important clarity for foreign and U.S. financial institutions.”<br />
<em>Treasury Deputy Secretary Neal Wolin</em></p></blockquote>
<p>“These regulations give the administration a powerful set of tools to combat tax evasion and efficiently,” Treasury Deputy Secretary Neal Wolin said in a news release. “The final rules mark a critical milestone in international cooperation on these issues, and they provide important clarity for foreign and U.S. financial institutions.”</p>
<p>Treasury said the rules are intended to finalize a step-by-step process for U.S. account identification, information reporting, and withholding requirements for foreign financial institutions (FFIs), other foreign entities, and U.S. withholding agents.</p>
<h4>Rules Intended to Build On IGAs</h4>
<p>The rules also are intended to build on intergovernmental information sharing agreements (IGAs) that allow financial institutions to report information on U.S.-owned accounts directly to their own governments, which then would share the data with the United States.</p>
<p>Treasury said it has signed or initialed such agreements with the United Kingdom, Mexico, Denmark, Ireland, Switzerland, and Spain, and announced for the first time Jan. 17 that Norway has joined this group.</p>
<p>A Treasury official said in a news conference that such IGA harmonization is a key goal of the final rules. She stressed that the general approach and intent of the Jan. 17 guidance remains the same as the proposed rules (REG-121647- 10) the government unveiled in February 2012.</p>
<p>The official said the refinements to the rules came in response to the hundreds of comments Treasury and IRS received on the proposed guidance.</p>
<h4>Timelines Phased In</h4>
<p>According to the news release, the final rules phase in the timelines for due diligence, reporting, and withholding in order to give financial institutions time to build systems to comply. Another goal for the government was to align these time frames with those for the IGAs. The Treasury official said this phase-in is consistent with Announcement 2012-42.</p>
<p>Treasury also said the rules expand and clarify the scope of payments not subject to withholding with respect to certain grandfathered obligations and certain payments made by nonfinancial entities. This is to “limit market disruption, reduce administrative burdens and establish certainty,” the government said.</p>
<p>In another major development, the rules are intended to “better align the obligations under FATCA with the risks posed by certain entities,” Treasury said. The guidance allows more flexible treatment of certain categories of low-risk institutions, such as governmental entities and retirement funds.</p>
<h4>Changes to Reporting for Investment Entities</h4>
<p>The final rules also provide that some investment entities may be subject to being reported on by FFIs with which they hold accounts, rather than being required to register as FFIs and report to IRS, Treasury said. The final rules also clarify the types of passive entities that must be identified and reported by financial institutions&#8230;</p>

		<div id="usermessage7a" class="cf_info "></div>
		<form enctype="multipart/form-data" action="/feed/#usermessage7a" method="post" class="cform bnas-banking-report-free-trial-form " id="cforms7form">
		<ol class="cf-ol">
			<li id="li-7-1" class="textonly" style="color:red" >Read this entire article for free, activate your free 7 day trial access to <b>BNA's Banking Report</b> now.</li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf7_field_2" id="cf7_field_2" value="BNKR"/></li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf7_field_3" id="cf7_field_3" value="May 21, 2013"/></li>
			<li id="li-7-4" class=""><label for="cf7_field_4"><span>First Name</span></label><input type="text" name="cf7_field_4" id="cf7_field_4" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-7-5" class=""><label for="cf7_field_5"><span>Last Name</span></label><input type="text" name="cf7_field_5" id="cf7_field_5" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-7-6" class=""><label for="cf7_field_6"><span>Email</span></label><input type="text" name="cf7_field_6" id="cf7_field_6" class="single fldemail fldrequired" value=""/><span class="emailreqtxt">(valid email required)</span></li>
			<li id="li-7-7" class=""><label for="cf7_field_7"><span>Job Title</span></label><input type="text" name="cf7_field_7" id="cf7_field_7" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-8" class=""><label for="cf7_field_8"><span>Organisation</span></label><input type="text" name="cf7_field_8" id="cf7_field_8" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-9" class=""><label for="cf7_field_9"><span>Address</span></label><input type="text" name="cf7_field_9" id="cf7_field_9" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-10" class=""><label for="cf7_field_10"><span>Address 2</span></label><input type="text" name="cf7_field_10" id="cf7_field_10" class="single" value=""/></li>
			<li id="li-7-11" class=""><label for="cf7_field_11"><span>City</span></label><input type="text" name="cf7_field_11" id="cf7_field_11" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-12" class=""><label for="cf7_field_12"><span>ZIP/Postal Code</span></label><input type="text" name="cf7_field_12" id="cf7_field_12" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-13" class=""><label for="cf7_field_13"><span>Country</span></label><input type="text" name="cf7_field_13" id="cf7_field_13" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-14" class=""><label for="cf7_field_14"><span>Phone</span></label><input type="text" name="cf7_field_14" id="cf7_field_14" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-15" class=""><label for="cforms_captcha7" class="seccap"><span>Verification</span></label><input type="text" name="cforms_captcha7" id="cforms_captcha7" class="secinput" value=""/><img id="cf_captcha_img7" class="captcha" src="http://www.uslawwatch.com/wp-content/plugins/cforms/cforms-captcha.php?ts=7&amp;c1=4&amp;c2=5&amp;ac=abcdefghijkmnpqrstuvwxyz23456789&amp;i=i&amp;w=115&amp;h=35&amp;c=2B3AFF&amp;l=547FA9&amp;f=font32.ttf&amp;a1=-5&amp;a2=5&amp;f1=17&amp;f2=19&amp;b=16.gif" alt=""/><a title="reset captcha image" href="javascript:reset_captcha('7')"><img class="captcha-reset" src="http://www.uslawwatch.com/wp-content/plugins/cforms/images/spacer.gif" alt="Captcha"/></a></li>
			<li id="li-7-16" class=""><input type="checkbox" name="cf7_field_16" id="cf7_field_16" class="cf-box-a" checked="checked"/><label for="cf7_field_16" class="cf-after"><span>I would like to receive occasional emails about product updates and special offers</span></label></li>
		</ol>
		<fieldset class="cf_hidden">
			<legend>&nbsp;</legend>
			<input type="hidden" name="cf_working7" id="cf_working7" value="One%20moment%20please..."/>
			<input type="hidden" name="cf_failure7" id="cf_failure7" value="Please%20fill%20in%20all%20the%20required%20fields."/>
			<input type="hidden" name="cf_codeerr7" id="cf_codeerr7" value="Please%20double-check%20your%20verification%20code."/>
			<input type="hidden" name="cf_customerr7" id="cf_customerr7" value="yyy"/>
			<input type="hidden" name="cf_popup7" id="cf_popup7" value="yy"/>
		</fieldset>
		<p class="cf-sb"><input type="submit" name="sendbutton7" id="sendbutton7" class="sendbutton" value="Activate Free Access"/></p></form><p class="linklove" id="ll7"><a href="http://www.deliciousdays.com/cforms-plugin"><em>cforms</em> contact form by delicious:days</a></p>

<a href="http://twitter.com/?status=RT%20%40%3A%20Long-Awaited%20Foreign%20Account%20Tax%20Compliance%20Act%20Final%20Rules%20Issued%20by%20Government%20-%20U.S.%20Law%20Watch%20http%3A%2F%2Ftinyurl.com%2Fb3ofvym" class="tweet-this" ><img src="http://www.uslawwatch.com/wp-content/plugins/simple-tweet/img/tweet.gif" title="Tweet this!" alt="Tweet this!" />Tweet this!</a>]]></content:encoded>
			<wfw:commentRss>http://www.uslawwatch.com/2013/01/22/finance/longawaited-foreign-account-tax-compliance-act-final-rules-issued-government/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BNA INSIGHTS: 2012: Annus Horribilis for the Banking Industry</title>
		<link>http://www.uslawwatch.com/2013/01/22/finance/bna-insights-2012-annus-horribilis-banking-industry/</link>
		<comments>http://www.uslawwatch.com/2013/01/22/finance/bna-insights-2012-annus-horribilis-banking-industry/#comments</comments>
		<pubDate>Tue, 22 Jan 2013 11:00:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[bank fraud]]></category>
		<category><![CDATA[Bank Supervision]]></category>
		<category><![CDATA[banking litigation]]></category>
		<category><![CDATA[Corporate Governance]]></category>
		<category><![CDATA[financial system reform]]></category>
		<category><![CDATA[interest rates]]></category>
		<category><![CDATA[International Banking]]></category>
		<category><![CDATA[Money Laundering]]></category>
		<category><![CDATA[mortgage fraud mortgage-backed securities]]></category>
		<category><![CDATA[Systemic Risk]]></category>
		<category><![CDATA[systemically important financial institutions]]></category>
		<category><![CDATA[Tax Fraud]]></category>

		<guid isPermaLink="false">http://www.uslawwatch.com/?p=6146</guid>
		<description><![CDATA[The year 2012 proved to be an annus horribilis for the banking industry.. This essay analyzes the most significant enforcement developments in 2012 and assesses the prospects for heightened scrutiny and increased enforcement action against the banking industry in 2013...]]></description>
				<content:encoded><![CDATA[<p><img alt="Paul L. Lee" src="http://news.bna.com/bnln/core_adp/get_object/im207014.png" /></p>
<p><em>By <strong>Paul L. Lee</strong>, Debevoise &amp; Plimpton LLP.</em></p>
<p>The year 2012 proved to be an annus horribilis for the banking industry at least from the perspective of regulatory and enforcement risk. Some might counter with the observation that 2012 was simply another annus horribilis in a series of such years for the banking industry. But by virtually any measure the horrors of 2012 exceed those of prior years. The regulatory and enforcement developments in 2012 prompt the question whether a permanently heightened regulatory and enforcement risk profile is now the new baseline for large banking institutions. This essay analyzes the most significant enforcement developments in 2012 and assesses the prospects for heightened scrutiny and increased enforcement action against the banking industry in 2013.</p>
<h4>Unprecedented Enforcement Action</h4>
<p>There is no precedent for the heightened regulatory and enforcement action seen in 2012. A faint precedent at best can be glimpsed from experience in the years following the dotcom crash and the Enron-like scandals. Under the title “Wall Street Fine Tracker,” Forbes tracked the fines paid by Wall Street firms from 2001 through 2003. It calculated the amount paid in total fines and settlements of class actions by Wall Street firms at almost $3 billion in 2002 and in excess of $4.2 billion in 2003. By contrast, the fines alone paid by UBS, HSBC and Standard Chartered Bank in the month of December 2012 exceeded $3.7 billion, including in the case of HSBC and UBS the two largest individual fines in U.S. banking history. Together with the fines paid earlier in 2012 by Standard Chartered Bank, Barclays and ING, the total for these five institutions exceeded $5.1 billion. Surveying the new enforcement scene, Adair Turner, chairman of the U.K. Financial Services Authority, is reported to have observed — in a private setting — that there is now an “arms race” among the regulators in pursuit of larger fines.</p>
<h4>The Banking Industry as Public Enemy</h4>
<p>The individual fines do not begin to tell the full story. They do not take account of the significant potential liability to private litigants, for example, in the LIBOR and other matters. Nor do they take account of the substantial reputational damage done to the institutions involved and the banking industry as a whole. In any event, fines do not appear to satisfy the public demand for retribution. The editorial pages of leading publications have for several years called for criminal prosecutions following the perceived misdeeds that led to the financial crisis. As the details of the LIBOR scandal emerged in June and July of 2012, such estimable publications as Bloomberg andThe New York Times encouraged the law enforcement authorities to seize the opportunity presented by these investigations to indict institutions and individuals at last. The announcement in December 2012 of the deferred prosecution agreement with HSBC for anti-money laundering and sanctions law violations resulted in press criticism of the fact that neither the institution nor any individuals were indicted. It also confirmed the suspicion in the mind of many observers that the regulators and law enforcement authorities view large financial institutions as “too big to indict.”</p>
<p>These criticisms may have been anticipated by the authorities because only a week after announcing the HSBC deferred prosecution agreement, the Department of Justice announced a settlement of LIBOR bid-rigging charges with UBS involving an agreement by a Japanese subsidiary of UBS to plea to a felony count as well as the criminal indictment of two former UBS traders. If the Department of Justice officials thought that the additional criminal action against the UBS subsidiary and former traders would go any distance to satisfy the critics, they were mistaken. The New York Times for one concluded that the settlement was structured so as to permit the plea by the subsidiary to shield the parent company and the indictment of the two traders to shield the management of the parent company. In some respects the Department of Justice may have become a victim of its own rhetoric. In announcing the settlement and the plea by the subsidiary, the Department described the UBS bid-rigging as an “epic” scandal. The New York Times editorial wanly concluded that there was nothing “epic” in the Department of Justice response. The equally esteemed Financial Times opined in words borrowed from the Department of Justice that the scale of UBS&#8217;s involvement in the bid-rigging was “astonishing” and in its own words that the bank&#8217;s “cavalier” attitude to compliance “simply beggars belief.”</p>
<div>
<blockquote><p>There is no precedent for the heightened regulatory and enforcement action seen in 2012.</p></blockquote>
</div>
<p>The public discourse over the banking industry has acquired a poisonous tone. It has admittedly been many decades since an observer would have presumed to suggest that it might be a wonderful life to be a banker — at least in the popular estimation. The opprobrium currently attached to Wall Street and the banking industry exceeds anything encountered since the time of the Great Depression. One does not require polling results to gauge the public distemper. A casual reading of reportage by the press and declamations by legislators in the U.S. and the U.K. indicates the anger and disdain directed at the financial sector. This anger was on prominent display during the U.S. Senate subcommittee hearing on HSBC and U.K. Parliamentary committee hearings on Barclays in July of 2012. These hearings can be seen in the most generous light as designed to seek truth, but certainly not reconciliation. A Parliamentary Commission has continued the quest in the New Year with hearings on the UBS involvement in the LIBOR bid-rigging scandal.</p>
<p>One may also question whether the press in its reporting and the legislators in their pronouncements simply reflect the public anger or actually amplify it. It is likely a bit of both. In any event it seems clear that the public outcry has influenced the approach of law enforcement and regulatory authorities to their LIBOR and other enforcement actions. When the New York Department of Financial Services pronounced Standard Chartered Bank a “rogue institution” in its August 2012 enforcement action, it merely borrowed a phrase used by a member of Parliament to describe Barclays during the Parliamentary committee hearings on the LIBOR scandal. The public anger from the financial collapse and the government financial assistance to the banking sector (to banks both large and small) is still strong and, if anything, will metastasize with each new hint of scandal in the banking sector. The Wall Street Journal editorial writers in fact suggest that the LIBOR scandal has become the regulators&#8217; surrogate for all that supposedly went wrong in finance before the panic of 2008. It seems that through the inadvertence of some and the malfeasance of others, the banking sector has constituted itself a public enemy. All the current signs suggest that notwithstanding the doubts of The New York Times, this will bean epic period of regulatory and law enforcement action against the banking sector in terms of penalties and remediation requirements.</p>
<h4>Governance Challenges in the New Enforcement Era</h4>
<p>This new era of regulatory and law enforcement action in the banking sector presents significant new challenges for governance in the sector. There are several different perspectives that may be brought to bear on the problem of governance. The first and most obvious perspective is how more robust governance might reduce regulatory and enforcement risk at least for future activities. A related perspective is how more robust governance might help as well to manage the risks of legacy activities, as these risks are actualized through existing investigations and enforcement actions. The banking sector is already experiencing an explosion of liability, some actualized from regulatory fines and settlements of civil litigation, other still potential from pending regulatory and law enforcement investigations and civil litigation, from a wide range of historical business practices and activities. Many of the practices and activities have been changed or terminated, but the prospect of regulatory, law enforcement and civil litigation action against institutions for past practices and activities is substantial and a matter of concern to the market since the ultimate size of any actualized liability is difficult to project.</p>
<p>One additional perspective on governance may come from the analysis of how improved governance might have helped the institutions to identify the risks in their legacy practices and mitigate those risks at an earlier stage. The recent enforcement actions provide useful insights for this historical analysis. In some cases they indicate that an institution&#8217;s governance and control structure had simply not identified the risk. In other cases they indicate that the risk had been identified by a control function such as compliance but was not addressed because the business function overrode the control function. In still other cases they indicate that the business and control functions identified the risk and the need to change practices but lacked the resources or a sense of urgency to correct the practices. In the most extreme cases there is even the suggestion that senior business and control functions may have simply decided as a business matter that they would run the risk of liability. Regulators have long known that control functions in many institutions do not have a strong enough voice and can be easily overridden by the business managers. The regulators will find confirmation of this belief in virtually all of the recent enforcement actions and may find further reason to be concerned that in some cases senior management and control functions were complicit in, or turned a blind eye to, the activity.</p>
<p>The recent law enforcement actions suggest that there is still another perspective to be brought to governance of regulatory and compliance risks. The law enforcement and regulatory actions themselves have had a profound effect on governance, in the short-term leading to the replacement of senior management and board members and in the long-term leading to changes in governance structure and board responsibility. This analysis here partakes of an oscillating nature, alternating between the effects of governance on these risks and the effects of these risks (or more precisely, their actualization from enforcement and litigation actions) on governance. To put this idea in a more pointed way, one might contrast the aspirational effect that sound governance might have on mitigating regulatory and enforcement risk with the demonstrable effect that recent regulatory and enforcement actions have had on governance from the perspective of management and the board. As even a cursory review of the recent regulatory and law enforcement actions indicates, the enforcement process itself has fundamentally affected governance. In announcing its settlement agreements with HSBC and UBS, the Department of Justice specifically noted that each institution had changed its senior leadership and restructured its compliance structure and taken numerous steps to enhance compliance and other control functions. In the case of Barclays, the effects of the law enforcement and regulatory actions on management and board were even more dramatic, playing out virtually in real-time as the Parliamentary committee hearings were in progress. Both the chairman of the board and the chief executive officer were forced to resign. Corporate accountability, as guided not so very gently by the regulators, was particularly swift in its exactions for Barclays&#8230;</p>

		<div id="usermessage7a" class="cf_info "></div>
		<form enctype="multipart/form-data" action="/feed/#usermessage7a" method="post" class="cform bnas-banking-report-free-trial-form " id="cforms7form">
		<ol class="cf-ol">
			<li id="li-7-1" class="textonly" style="color:red" >Read this entire article for free, activate your free 7 day trial access to <b>BNA's Banking Report</b> now.</li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf7_field_2" id="cf7_field_2" value="BNKR"/></li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf7_field_3" id="cf7_field_3" value="May 21, 2013"/></li>
			<li id="li-7-4" class=""><label for="cf7_field_4"><span>First Name</span></label><input type="text" name="cf7_field_4" id="cf7_field_4" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-7-5" class=""><label for="cf7_field_5"><span>Last Name</span></label><input type="text" name="cf7_field_5" id="cf7_field_5" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-7-6" class=""><label for="cf7_field_6"><span>Email</span></label><input type="text" name="cf7_field_6" id="cf7_field_6" class="single fldemail fldrequired" value=""/><span class="emailreqtxt">(valid email required)</span></li>
			<li id="li-7-7" class=""><label for="cf7_field_7"><span>Job Title</span></label><input type="text" name="cf7_field_7" id="cf7_field_7" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-8" class=""><label for="cf7_field_8"><span>Organisation</span></label><input type="text" name="cf7_field_8" id="cf7_field_8" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-9" class=""><label for="cf7_field_9"><span>Address</span></label><input type="text" name="cf7_field_9" id="cf7_field_9" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-10" class=""><label for="cf7_field_10"><span>Address 2</span></label><input type="text" name="cf7_field_10" id="cf7_field_10" class="single" value=""/></li>
			<li id="li-7-11" class=""><label for="cf7_field_11"><span>City</span></label><input type="text" name="cf7_field_11" id="cf7_field_11" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-12" class=""><label for="cf7_field_12"><span>ZIP/Postal Code</span></label><input type="text" name="cf7_field_12" id="cf7_field_12" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-13" class=""><label for="cf7_field_13"><span>Country</span></label><input type="text" name="cf7_field_13" id="cf7_field_13" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-14" class=""><label for="cf7_field_14"><span>Phone</span></label><input type="text" name="cf7_field_14" id="cf7_field_14" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-15" class=""><label for="cforms_captcha7" class="seccap"><span>Verification</span></label><input type="text" name="cforms_captcha7" id="cforms_captcha7" class="secinput" value=""/><img id="cf_captcha_img7" class="captcha" src="http://www.uslawwatch.com/wp-content/plugins/cforms/cforms-captcha.php?ts=7&amp;c1=4&amp;c2=5&amp;ac=abcdefghijkmnpqrstuvwxyz23456789&amp;i=i&amp;w=115&amp;h=35&amp;c=2B3AFF&amp;l=547FA9&amp;f=font32.ttf&amp;a1=-5&amp;a2=5&amp;f1=17&amp;f2=19&amp;b=16.gif" alt=""/><a title="reset captcha image" href="javascript:reset_captcha('7')"><img class="captcha-reset" src="http://www.uslawwatch.com/wp-content/plugins/cforms/images/spacer.gif" alt="Captcha"/></a></li>
			<li id="li-7-16" class=""><input type="checkbox" name="cf7_field_16" id="cf7_field_16" class="cf-box-a" checked="checked"/><label for="cf7_field_16" class="cf-after"><span>I would like to receive occasional emails about product updates and special offers</span></label></li>
		</ol>
		<fieldset class="cf_hidden">
			<legend>&nbsp;</legend>
			<input type="hidden" name="cf_working7" id="cf_working7" value="One%20moment%20please..."/>
			<input type="hidden" name="cf_failure7" id="cf_failure7" value="Please%20fill%20in%20all%20the%20required%20fields."/>
			<input type="hidden" name="cf_codeerr7" id="cf_codeerr7" value="Please%20double-check%20your%20verification%20code."/>
			<input type="hidden" name="cf_customerr7" id="cf_customerr7" value="yyy"/>
			<input type="hidden" name="cf_popup7" id="cf_popup7" value="yy"/>
		</fieldset>
		<p class="cf-sb"><input type="submit" name="sendbutton7" id="sendbutton7" class="sendbutton" value="Activate Free Access"/></p></form><p class="linklove" id="ll7"><a href="http://www.deliciousdays.com/cforms-plugin"><em>cforms</em> contact form by delicious:days</a></p>

<a href="http://twitter.com/?status=RT%20%40%3A%20BNA%20INSIGHTS%3A%202012%3A%20Annus%20Horribilis%20for%20the%20Banking%20Industry%20-%20U.S.%20Law%20Watch%20http%3A%2F%2Ftinyurl.com%2Falxytrj" class="tweet-this" ><img src="http://www.uslawwatch.com/wp-content/plugins/simple-tweet/img/tweet.gif" title="Tweet this!" alt="Tweet this!" />Tweet this!</a>]]></content:encoded>
			<wfw:commentRss>http://www.uslawwatch.com/2013/01/22/finance/bna-insights-2012-annus-horribilis-banking-industry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HSBC Agrees to Pay U.S.$1.9 Billion to Resolve Money Laundering Case</title>
		<link>http://www.uslawwatch.com/2012/12/19/finance/hsbc-agrees-pay-us19-billion-resolve-money-laundering-case/</link>
		<comments>http://www.uslawwatch.com/2012/12/19/finance/hsbc-agrees-pay-us19-billion-resolve-money-laundering-case/#comments</comments>
		<pubDate>Wed, 19 Dec 2012 11:16:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[Bank Supervision]]></category>
		<category><![CDATA[banking litigation]]></category>
		<category><![CDATA[International Banking]]></category>
		<category><![CDATA[Money Laundering]]></category>

		<guid isPermaLink="false">http://www.uslawwatch.com/?p=6139</guid>
		<description><![CDATA[The London-based HSBC Group and HSBC Bank USA have agreed to pay $1.9 billion and enter into a deferred prosecution agreement (DPA) to resolve charges of money laundering and doing business with countries subject to U.S. sanctions...]]></description>
				<content:encoded><![CDATA[<p><em>By <strong>John Herzfeld</strong></em></p>
<p>NEW YORK—The London-based HSBC Group and HSBC Bank USA have agreed to pay $1.9 billion and enter into a deferred prosecution agreement (DPA) to resolve charges of money laundering and doing business with countries subject to U.S. sanctions, the Justice Department and banking regulators announced Dec. 11 (<em>United States v. HSBC</em>, E.D.N.Y., No. 12-cr-763, deferred prosecution agreement 12/11/12).</p>
<p>Charged in the U.S. District Court for the Eastern District of New York with helping narcotics traffickers and others to launder their criminal proceeds and illegally handling transactions for customers in Cuba, Iran, Libya, Sudan, and Burma, HSBC has agreed to forfeit $1.256 billion and pay $665 million in civil penalties—including $500 million to the Office of the Comptroller of the Currency and $165 million to the Federal Reserve.</p>
<p>The U.K. Financial Services Authority is pursuing a separate action, DOJ said.</p>
<p>The U.S. case charged violations of the Bank Secrecy Act (BSA), the International Emergency Economic Powers Act (IEEPA), and the Trading With the Enemy Act (TWEA).</p>
<p>In the five-year corporate monitoring agreement, HSBC consented to submit to an enhanced compliance regimen and oversight by an independent monitor.</p>
<p>HSBC Bank USA, based in McLean, Va., was charged with violating the BSA by failing to maintain an effective anti-money laundering program and to conduct appropriate due diligence on its foreign correspondent account holders. The HSBC Group violated IEEPA and TWEA by illegally conducting transactions barred by sanctions enforced by the Office of Foreign Assets Control (OFAC) at the time of the transactions, DOJ said.</p>
<p>HSBC has waived federal indictment, agreed to the filing of a criminal information containing the charges, and has accepted responsibility for its criminal conduct and that of its employees, DOJ said.</p>
<h4>Breuer: ‘Stunning’ Oversight Failures</h4>
<p>In announcing the resolution, Assistant Attorney General Lanny Breuer said that HSBC was “being held accountable for stunning failures of oversight—and worse—that led the bank to permit narcotics traffickers and others to launder hundreds of millions of dollars through HSBC subsidiaries, and to facilitate hundreds of millions more in transactions with sanctioned countries.”</p>
<p>Calling HSBC “one of the largest financial institutions in the world,” U.S. Attorney Loretta Lynch said that the bank&#8217;s “blatant failure to implement proper anti-money laundering controls” aided in the laundering of at least $881 million in drug proceeds through the U.S. financial system and that its “willful flouting of U.S. sanctions laws and regulations” allowed “hundreds of millions of dollars in OFAC-prohibited transactions” to be processed.</p>
<p>She added, “Today&#8217;s historic agreement, which imposes the largest penalty in any BSA prosecution to date, makes it clear that all corporate citizens, no matter how large, must be held accountable for their actions.”</p>
<p>HSBC has replaced almost all of its senior management, clawed back deferred compensation bonuses given to its most senior anti-money laundering and compliance officers, and has agreed to partially defer bonus compensation for its most senior executives during the five-year DPA, prosecutors said.</p>
<p>New York prosecutors also joined in the HSBC probes and settlements. Manhattan District Attorney Cyrus R. Vance Jr. noted that his office had entered into DPAs with six banks over the past four years&#8230;</p>
<p>&nbsp;</p>

<a href="http://twitter.com/?status=RT%20%40%3A%20HSBC%20Agrees%20to%20Pay%20U.S.%241.9%20Billion%20to%20Resolve%20Money%20Laundering%20Case%20-%20U.S.%20Law%20Watch%20http%3A%2F%2Ftinyurl.com%2Fc94tjn3" class="tweet-this" ><img src="http://www.uslawwatch.com/wp-content/plugins/simple-tweet/img/tweet.gif" title="Tweet this!" alt="Tweet this!" />Tweet this!</a>]]></content:encoded>
			<wfw:commentRss>http://www.uslawwatch.com/2012/12/19/finance/hsbc-agrees-pay-us19-billion-resolve-money-laundering-case/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Federal Reserve Proposes Guidelines for Foreign Banks in Keeping with U.S. Bank Capital Standards</title>
		<link>http://www.uslawwatch.com/2012/12/19/finance/federal-reserve-proposes-guidelines-foreign-banks-keeping-bank-capital-standards/</link>
		<comments>http://www.uslawwatch.com/2012/12/19/finance/federal-reserve-proposes-guidelines-foreign-banks-keeping-bank-capital-standards/#comments</comments>
		<pubDate>Wed, 19 Dec 2012 11:12:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[Bank Supervision]]></category>
		<category><![CDATA[capital requirement]]></category>
		<category><![CDATA[International Banking]]></category>
		<category><![CDATA[lending]]></category>
		<category><![CDATA[Multinational Corporations]]></category>
		<category><![CDATA[Systemic Risk]]></category>

		<guid isPermaLink="false">http://www.uslawwatch.com/?p=6137</guid>
		<description><![CDATA[Big foreign banks would face capital standards applied to their U.S. counterparts and be required to maintain a 30-day buffer of highly liquid assets under a proposal Dec. 14 by the Federal Reserve that makes significant change in its regulation of overseas lenders...]]></description>
				<content:encoded><![CDATA[<p><em>By<strong> Jeff Bater</strong></em></p>
<p>Big foreign banks would face capital standards applied to their U.S. counterparts and be required to maintain a 30-day buffer of highly liquid assets under a proposal Dec. 14 by the Federal Reserve that makes significant change in its regulation of overseas lenders.</p>
<p>The Fed proposal would have a foreign bank organize its U.S. subsidiaries under a single U.S. intermediate holding company subject to the same risk-based capital and leverage standards applied to U.S. bank holding companies. The proposal would apply to foreign banks with total global consolidated assets of $50 billion or more and U.S. assets of at least $10 billion; the Fed estimates about 107 firms would be affected.</p>
<p>The $10-billion threshold excludes assets held by a U.S. branch or agency. While the intermediate holding company would be subject to enhanced prudential standards on a consolidated basis, U.S. branches and agencies of a foreign banking organization can continue to operate outside of the intermediate holding company.</p>
<p>A reduced set of requirements would apply to 84 foreign banks that each have total global assets of $50 billion or more, but have less than $50 billion in combined U.S. assets, reflecting “the limited risk to U.S. financial stability posed by these firms,” according to a staff memo on the proposal. The 23 banks with more than $50 billion in combined U.S. assets would face more stringent standards.</p>
<p>The proposal would also apply to foreign nonbank financial companies. The Financial Stability Oversight Council, made up of U.S. financial regulators, is expected to designate certain nonbanks as systemically important but hasn&#8217;t done so yet.</p>
<h4>Financial Crisis Revelations</h4>
<p>The financial crisis revealed limitations on the ability of foreign banks to act as a source of support to their U.S. operations under stressed conditions. Congress directed the Fed, in the Dodd-Frank Wall Street Reform and Consumer Protection Act, to impose enhanced prudential standards on foreign banks.</p>
<p>The Fed will accept comments on the proposal through March. The regulator is giving foreign banks considerable time to implement the requirements. Organizations with global consolidated assets of $50 billion or more on July 1, 2014, would be required to meet the new standards on July 1, 2015, according to the Fed.</p>
<p>“What does all this mean for covered foreign and non-bank banks? Of course, an FRB proposal is not a final rule,” Federal Financial Analytics said in a comment. “But, if the FRB proceeds as planned, covered firms will be governed by the Federal Reserve and, thus, an array of increasingly stringent standards, in ways their home-country regulators or non-bank business plans never anticipated.”</p>
<p>Jaret Seiberg, an analyst at Washington Research Group, a unit of Guggenheim Securities, called the proposal a negative for the large foreign banks that operate extensive broker-dealer and banking activities in the United States.</p>
<p>“An example of a foreign bank at risk from this approach would be Deutsche Bank,” he said. “For the domestic mega banks, this is a mixed development. It should give them a competitive advantage over their foreign bank rivals for lending and investment banking activities. Yet it also runs the risk of triggering a trade war that could result in domestic banks facing costly requirements in foreign countries. The mega banks include JP Morgan, Citigroup, Bank of America, Goldman Sachs, and Morgan Stanley. For the large regional banks, this should be all upside. These banks operate only domestically, which means foreign country retaliation will not impact them.”&#8230;</p>

		<div id="usermessage7a" class="cf_info "></div>
		<form enctype="multipart/form-data" action="/feed/#usermessage7a" method="post" class="cform bnas-banking-report-free-trial-form " id="cforms7form">
		<ol class="cf-ol">
			<li id="li-7-1" class="textonly" style="color:red" >Read this entire article for free, activate your free 7 day trial access to <b>BNA's Banking Report</b> now.</li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf7_field_2" id="cf7_field_2" value="BNKR"/></li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf7_field_3" id="cf7_field_3" value="May 21, 2013"/></li>
			<li id="li-7-4" class=""><label for="cf7_field_4"><span>First Name</span></label><input type="text" name="cf7_field_4" id="cf7_field_4" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-7-5" class=""><label for="cf7_field_5"><span>Last Name</span></label><input type="text" name="cf7_field_5" id="cf7_field_5" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-7-6" class=""><label for="cf7_field_6"><span>Email</span></label><input type="text" name="cf7_field_6" id="cf7_field_6" class="single fldemail fldrequired" value=""/><span class="emailreqtxt">(valid email required)</span></li>
			<li id="li-7-7" class=""><label for="cf7_field_7"><span>Job Title</span></label><input type="text" name="cf7_field_7" id="cf7_field_7" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-8" class=""><label for="cf7_field_8"><span>Organisation</span></label><input type="text" name="cf7_field_8" id="cf7_field_8" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-9" class=""><label for="cf7_field_9"><span>Address</span></label><input type="text" name="cf7_field_9" id="cf7_field_9" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-10" class=""><label for="cf7_field_10"><span>Address 2</span></label><input type="text" name="cf7_field_10" id="cf7_field_10" class="single" value=""/></li>
			<li id="li-7-11" class=""><label for="cf7_field_11"><span>City</span></label><input type="text" name="cf7_field_11" id="cf7_field_11" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-12" class=""><label for="cf7_field_12"><span>ZIP/Postal Code</span></label><input type="text" name="cf7_field_12" id="cf7_field_12" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-13" class=""><label for="cf7_field_13"><span>Country</span></label><input type="text" name="cf7_field_13" id="cf7_field_13" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-14" class=""><label for="cf7_field_14"><span>Phone</span></label><input type="text" name="cf7_field_14" id="cf7_field_14" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-15" class=""><label for="cforms_captcha7" class="seccap"><span>Verification</span></label><input type="text" name="cforms_captcha7" id="cforms_captcha7" class="secinput" value=""/><img id="cf_captcha_img7" class="captcha" src="http://www.uslawwatch.com/wp-content/plugins/cforms/cforms-captcha.php?ts=7&amp;c1=4&amp;c2=5&amp;ac=abcdefghijkmnpqrstuvwxyz23456789&amp;i=i&amp;w=115&amp;h=35&amp;c=2B3AFF&amp;l=547FA9&amp;f=font32.ttf&amp;a1=-5&amp;a2=5&amp;f1=17&amp;f2=19&amp;b=16.gif" alt=""/><a title="reset captcha image" href="javascript:reset_captcha('7')"><img class="captcha-reset" src="http://www.uslawwatch.com/wp-content/plugins/cforms/images/spacer.gif" alt="Captcha"/></a></li>
			<li id="li-7-16" class=""><input type="checkbox" name="cf7_field_16" id="cf7_field_16" class="cf-box-a" checked="checked"/><label for="cf7_field_16" class="cf-after"><span>I would like to receive occasional emails about product updates and special offers</span></label></li>
		</ol>
		<fieldset class="cf_hidden">
			<legend>&nbsp;</legend>
			<input type="hidden" name="cf_working7" id="cf_working7" value="One%20moment%20please..."/>
			<input type="hidden" name="cf_failure7" id="cf_failure7" value="Please%20fill%20in%20all%20the%20required%20fields."/>
			<input type="hidden" name="cf_codeerr7" id="cf_codeerr7" value="Please%20double-check%20your%20verification%20code."/>
			<input type="hidden" name="cf_customerr7" id="cf_customerr7" value="yyy"/>
			<input type="hidden" name="cf_popup7" id="cf_popup7" value="yy"/>
		</fieldset>
		<p class="cf-sb"><input type="submit" name="sendbutton7" id="sendbutton7" class="sendbutton" value="Activate Free Access"/></p></form><p class="linklove" id="ll7"><a href="http://www.deliciousdays.com/cforms-plugin"><em>cforms</em> contact form by delicious:days</a></p>

<a href="http://twitter.com/?status=RT%20%40%3A%20Federal%20Reserve%20Proposes%20Guidelines%20for%20Foreign%20Banks%20in%20Keeping%20with%20U.S.%20Bank%20Capital%20Standards%20-%20U.S.%20Law%20Watch%20http%3A%2F%2Ftinyurl.com%2Fckulsso" class="tweet-this" ><img src="http://www.uslawwatch.com/wp-content/plugins/simple-tweet/img/tweet.gif" title="Tweet this!" alt="Tweet this!" />Tweet this!</a>]]></content:encoded>
			<wfw:commentRss>http://www.uslawwatch.com/2012/12/19/finance/federal-reserve-proposes-guidelines-foreign-banks-keeping-bank-capital-standards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Schapiro to Leave SEC in Mid-December; White House Taps Walter as Replacement</title>
		<link>http://www.uslawwatch.com/2012/12/04/finance/schapiro-leave-sec-middecember-white-house-taps-walter-replacement/</link>
		<comments>http://www.uslawwatch.com/2012/12/04/finance/schapiro-leave-sec-middecember-white-house-taps-walter-replacement/#comments</comments>
		<pubDate>Tue, 04 Dec 2012 09:50:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[appointments and personnel changes (securities)]]></category>

		<guid isPermaLink="false">http://www.uslawwatch.com/?p=4636</guid>
		<description><![CDATA[Ending weeks of speculation, SEC Chairman Mary Schapiro Nov. 26 announced that she will step down on Dec. 14.  On the same day, the White House announced that it intends to designate SEC Commissioner Elisse Walter to the chairmanship after Schapiro departs...]]></description>
				<content:encoded><![CDATA[<p><em>By <strong>Yin Wilczek</strong> and <strong>Cheryl Bolen</strong></em></p>
<p>Ending weeks of speculation, Securities and Exchange Commission Chairman Mary Schapiro Nov. 26 announced that she will step down on Dec. 14.</p>
<p>Schapiro—who was appointed by President Obama in January 2009—is the first woman to serve as a permanent SEC chair, and one of the longest serving chairmen at the financial services regulator. She also tirelessly advocated for a strong SEC, even as critics called for its dismantling following one of the worst economic periods in U.S. history.</p>
<p>On the same day, the White House announced that it intends to designate SEC Commissioner Elisse Walter to the chairmanship after Schapiro departs. However, a White House official later told BNA that while Walter will be designated as the new chairman, President Obama intends to nominate someone for a full term in the near future.</p>
<h4>Busy Tenure</h4>
<p>Under Schapiro&#8217;s leadership, the SEC revitalized its enforcement program in the wake of its high profile failure to uncover Bernard Madoff&#8217;s massive Ponzi scheme, even as it embarked on the busiest rulemaking agenda in its history. On the other hand, the SEC also has suffered some significant embarrassments, including loss of a legal challenge over its proxy access rule, and a controversy over conflicts of interest regarding former general counsel David Becker&#8217;s participation in Madoff-related commission decisions.</p>
<p>In a statement, Schapiro called her time at the SEC “incredibly rewarding.” “Over the past four years, we have brought a record number of enforcement actions, engaged in one of the busiest rulemaking periods, and gained greater authority from Congress to better fulfill our mission,” she said.</p>
<p>Schapiro and SEC officials did not offer reasons for her departure. Her term would have expired June 5, 2014. However, other sources suggested that the heavy workload has taken its toll.</p>
<p>Meanwhile, President Obama expressed his “deep gratitude” to Schapiro for taking on the job shortly after the 2008 financial crisis. “When Mary agreed to serve nearly four years ago, she was fully aware of the difficulties facing the SEC and our economy as a whole,” he said in a statement. “But she accepted the challenge, and today, the SEC is stronger and our financial system is safer and better able to serve the American people—thanks in large part to Mary&#8217;s hard work.”</p>
<h4>Speculation</h4>
<p>In the weeks leading up to Schapiro&#8217;s announcement, rumors had circulated widely about her possible departure and replacement. Media reports and other sources suggested that likely candidates for the chairmanship included Treasury official Mary John Miller, Walter, former banking executive Sallie Krawcheck, and Mellody Hobson, president of Chicago-based investment firm Ariel Investments LLC and a member of the SEC&#8217;s Investor Advisory Committee (44 SRLR 760, 4/16/12)&#8230;</p>

		<div id="usermessage5a" class="cf_info "></div>
		<form enctype="multipart/form-data" action="/feed/#usermessage5a" method="post" class="cform securities-regulation-law-report-free-trial-form " id="cforms5form">
		<ol class="cf-ol">
			<li id="li-5-1" class="textonly" style="color:red" >Read this entire article for free, simply activate your free 7 day trial access to Securities Regulation & Law Report now.</li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf5_field_2" id="cf5_field_2" value="SRLR"/></li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf5_field_3" id="cf5_field_3" value="May 21, 2013"/></li>
			<li id="li-5-4" class=""><label for="cf5_field_4"><span>First Name</span></label><input type="text" name="cf5_field_4" id="cf5_field_4" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-5-5" class=""><label for="cf5_field_5"><span>Last Name</span></label><input type="text" name="cf5_field_5" id="cf5_field_5" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-5-6" class=""><label for="cf5_field_6"><span>Email</span></label><input type="text" name="cf5_field_6" id="cf5_field_6" class="single fldemail fldrequired" value=""/><span class="emailreqtxt">(valid email required)</span></li>
			<li id="li-5-7" class=""><label for="cf5_field_7"><span>Job Title</span></label><input type="text" name="cf5_field_7" id="cf5_field_7" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-8" class=""><label for="cf5_field_8"><span>Organisation</span></label><input type="text" name="cf5_field_8" id="cf5_field_8" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-9" class=""><label for="cf5_field_9"><span>Address</span></label><input type="text" name="cf5_field_9" id="cf5_field_9" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-10" class=""><label for="cf5_field_10"><span>Address 2</span></label><input type="text" name="cf5_field_10" id="cf5_field_10" class="single" value=""/></li>
			<li id="li-5-11" class=""><label for="cf5_field_11"><span>City</span></label><input type="text" name="cf5_field_11" id="cf5_field_11" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-12" class=""><label for="cf5_field_12"><span>ZIP/Postal Code</span></label><input type="text" name="cf5_field_12" id="cf5_field_12" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-13" class=""><label for="cf5_field_13"><span>Country</span></label><input type="text" name="cf5_field_13" id="cf5_field_13" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-14" class=""><label for="cf5_field_14"><span>Phone</span></label><input type="text" name="cf5_field_14" id="cf5_field_14" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-5-15" class=""><label for="cforms_captcha5" class="seccap"><span>Verification</span></label><input type="text" name="cforms_captcha5" id="cforms_captcha5" class="secinput" value=""/><img id="cf_captcha_img5" class="captcha" src="http://www.uslawwatch.com/wp-content/plugins/cforms/cforms-captcha.php?ts=5&amp;c1=4&amp;c2=5&amp;ac=abcdefghijkmnpqrstuvwxyz23456789&amp;i=i&amp;w=115&amp;h=35&amp;c=2B3AFF&amp;l=547FA9&amp;f=font32.ttf&amp;a1=-5&amp;a2=5&amp;f1=17&amp;f2=19&amp;b=16.gif" alt=""/><a title="reset captcha image" href="javascript:reset_captcha('5')"><img class="captcha-reset" src="http://www.uslawwatch.com/wp-content/plugins/cforms/images/spacer.gif" alt="Captcha"/></a></li>
			<li id="li-5-16" class=""><input type="checkbox" name="cf5_field_16" id="cf5_field_16" class="cf-box-a" checked="checked"/><label for="cf5_field_16" class="cf-after"><span>I would like to receive occasional emails about product updates and special offers</span></label></li>
		</ol>
		<fieldset class="cf_hidden">
			<legend>&nbsp;</legend>
			<input type="hidden" name="cf_working5" id="cf_working5" value="One%20moment%20please..."/>
			<input type="hidden" name="cf_failure5" id="cf_failure5" value="Please%20fill%20in%20all%20the%20required%20fields."/>
			<input type="hidden" name="cf_codeerr5" id="cf_codeerr5" value="Please%20double-check%20your%20verification%20code."/>
			<input type="hidden" name="cf_customerr5" id="cf_customerr5" value="yyy"/>
			<input type="hidden" name="cf_popup5" id="cf_popup5" value="yy"/>
		</fieldset>
		<p class="cf-sb"><input type="submit" name="sendbutton5" id="sendbutton5" class="sendbutton" value="Activate Free Access"/></p></form><p class="linklove" id="ll5"><a href="http://www.deliciousdays.com/cforms-plugin"><em>cforms</em> contact form by delicious:days</a></p>

<a href="http://twitter.com/?status=RT%20%40%3A%20Schapiro%20to%20Leave%20SEC%20in%20Mid-December%3B%20White%20House%20Taps%20Walter%20as%20Replacement%20-%20U.S.%20Law%20Watch%20http%3A%2F%2Ftinyurl.com%2Fcd6z372" class="tweet-this" ><img src="http://www.uslawwatch.com/wp-content/plugins/simple-tweet/img/tweet.gif" title="Tweet this!" alt="Tweet this!" />Tweet this!</a>]]></content:encoded>
			<wfw:commentRss>http://www.uslawwatch.com/2012/12/04/finance/schapiro-leave-sec-middecember-white-house-taps-walter-replacement/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fed to Overhaul Regulation of Foreign Banks, Eyeing Three-Part Framework</title>
		<link>http://www.uslawwatch.com/2012/12/04/finance/fed-overhaul-regulation-foreign-banks-eyeing-threepart-framework/</link>
		<comments>http://www.uslawwatch.com/2012/12/04/finance/fed-overhaul-regulation-foreign-banks-eyeing-threepart-framework/#comments</comments>
		<pubDate>Tue, 04 Dec 2012 09:45:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[bank holding companies]]></category>
		<category><![CDATA[bank liquidity]]></category>
		<category><![CDATA[Bank Supervision]]></category>
		<category><![CDATA[capital requirement]]></category>
		<category><![CDATA[enterprise risk management]]></category>
		<category><![CDATA[Foreign Corporations]]></category>
		<category><![CDATA[International Banking]]></category>

		<guid isPermaLink="false">http://www.uslawwatch.com/?p=4633</guid>
		<description><![CDATA[The Federal Reserve Board plans to overhaul how it regulates the U.S. operations of large foreign banks, outlining a three-part framework based on a new holding company structure, uniform capital and stress-testing requirements, and liquidity standards...]]></description>
				<content:encoded><![CDATA[<p><em>By <strong>Chris Bruce</strong></em></p>
<p>The Federal Reserve Board plans to overhaul how it regulates the U.S. operations of large foreign banks, Fed Governor Daniel K. Tarullo said Nov. 28, outlining a three-part framework based on a new holding company structure, uniform capital and stress-testing requirements, and liquidity standards.</p>
<p>Tarullo, who said he expects a proposal “in the coming weeks,” said regulatory requirements have changed little over the past decade, despite an increase in the concentration and complexity of foreign bank assets in the United States and new limits on the ability of home-country regulators and foreign parent firms to support their institutions here.</p>
<p>Those concerns, as well as recent changes by Congress, call for a new recognition that “while internationally active banks live globally, they may well die locally,” he said.</p>
<p>“By imposing a more standardized regulatory structure on the U.S. operations of foreign banks, we can ensure that enhanced prudential standards are applied consistently across foreign banks and in comparable ways between U.S. banking organizations and foreign banking organizations,” Tarullo told the Yale School of Management Leaders Forum in New Haven, Conn.</p>
<h4>Tarullo Cites Three Changes</h4>
<p>Although discussions are still ongoing at the Fed on how to address challenges posed by foreign banks, Tarullo offered a glimpse, saying three basic changes “are desirable.”</p>
<p>First would be a requirement for large foreign institutions to establish a U.S. intermediate holding company (IHC) over their U.S. bank and nonbank subsidiaries. Tarullo said the IHC would promote more consistent and uniform regulation.</p>
<p>In addition, U.S. IHCs would have to comply with the same capital rules that apply to U.S. bank holding companies, and large foreign banks would have to comply with liquidity standards designed to reduce the chance of bank runs during periods of financial stress.</p>
<p>Not all U.S. operations would be affected, or affected in the same way. For example, branches of foreign banks and agency offices generally would not be part of an IHC, because they are part of the foreign parent company.</p>
<h4>Some Revisions Already In Play</h4>
<p>The approach laid out by Tarullo is not entirely new. The Fed already plans to propose capital, stress testing, and other requirements for large foreign banks as required under Section 165 of the Dodd-Frank Wall Street Reform and Consumer Protection Act&#8230;</p>

		<div id="usermessage7a" class="cf_info "></div>
		<form enctype="multipart/form-data" action="/feed/#usermessage7a" method="post" class="cform bnas-banking-report-free-trial-form " id="cforms7form">
		<ol class="cf-ol">
			<li id="li-7-1" class="textonly" style="color:red" >Read this entire article for free, activate your free 7 day trial access to <b>BNA's Banking Report</b> now.</li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf7_field_2" id="cf7_field_2" value="BNKR"/></li>
			<li class="cf_hidden"><input type="hidden" class="cfhidden" name="cf7_field_3" id="cf7_field_3" value="May 21, 2013"/></li>
			<li id="li-7-4" class=""><label for="cf7_field_4"><span>First Name</span></label><input type="text" name="cf7_field_4" id="cf7_field_4" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-7-5" class=""><label for="cf7_field_5"><span>Last Name</span></label><input type="text" name="cf7_field_5" id="cf7_field_5" class="single fldrequired" value="" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-7-6" class=""><label for="cf7_field_6"><span>Email</span></label><input type="text" name="cf7_field_6" id="cf7_field_6" class="single fldemail fldrequired" value=""/><span class="emailreqtxt">(valid email required)</span></li>
			<li id="li-7-7" class=""><label for="cf7_field_7"><span>Job Title</span></label><input type="text" name="cf7_field_7" id="cf7_field_7" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-8" class=""><label for="cf7_field_8"><span>Organisation</span></label><input type="text" name="cf7_field_8" id="cf7_field_8" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-9" class=""><label for="cf7_field_9"><span>Address</span></label><input type="text" name="cf7_field_9" id="cf7_field_9" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-10" class=""><label for="cf7_field_10"><span>Address 2</span></label><input type="text" name="cf7_field_10" id="cf7_field_10" class="single" value=""/></li>
			<li id="li-7-11" class=""><label for="cf7_field_11"><span>City</span></label><input type="text" name="cf7_field_11" id="cf7_field_11" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-12" class=""><label for="cf7_field_12"><span>ZIP/Postal Code</span></label><input type="text" name="cf7_field_12" id="cf7_field_12" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-13" class=""><label for="cf7_field_13"><span>Country</span></label><input type="text" name="cf7_field_13" id="cf7_field_13" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-14" class=""><label for="cf7_field_14"><span>Phone</span></label><input type="text" name="cf7_field_14" id="cf7_field_14" class="single fldrequired" value=""/><span class="reqtxt">(required)</span></li>
			<li id="li-7-15" class=""><label for="cforms_captcha7" class="seccap"><span>Verification</span></label><input type="text" name="cforms_captcha7" id="cforms_captcha7" class="secinput" value=""/><img id="cf_captcha_img7" class="captcha" src="http://www.uslawwatch.com/wp-content/plugins/cforms/cforms-captcha.php?ts=7&amp;c1=4&amp;c2=5&amp;ac=abcdefghijkmnpqrstuvwxyz23456789&amp;i=i&amp;w=115&amp;h=35&amp;c=2B3AFF&amp;l=547FA9&amp;f=font32.ttf&amp;a1=-5&amp;a2=5&amp;f1=17&amp;f2=19&amp;b=16.gif" alt=""/><a title="reset captcha image" href="javascript:reset_captcha('7')"><img class="captcha-reset" src="http://www.uslawwatch.com/wp-content/plugins/cforms/images/spacer.gif" alt="Captcha"/></a></li>
			<li id="li-7-16" class=""><input type="checkbox" name="cf7_field_16" id="cf7_field_16" class="cf-box-a" checked="checked"/><label for="cf7_field_16" class="cf-after"><span>I would like to receive occasional emails about product updates and special offers</span></label></li>
		</ol>
		<fieldset class="cf_hidden">
			<legend>&nbsp;</legend>
			<input type="hidden" name="cf_working7" id="cf_working7" value="One%20moment%20please..."/>
			<input type="hidden" name="cf_failure7" id="cf_failure7" value="Please%20fill%20in%20all%20the%20required%20fields."/>
			<input type="hidden" name="cf_codeerr7" id="cf_codeerr7" value="Please%20double-check%20your%20verification%20code."/>
			<input type="hidden" name="cf_customerr7" id="cf_customerr7" value="yyy"/>
			<input type="hidden" name="cf_popup7" id="cf_popup7" value="yy"/>
		</fieldset>
		<p class="cf-sb"><input type="submit" name="sendbutton7" id="sendbutton7" class="sendbutton" value="Activate Free Access"/></p></form><p class="linklove" id="ll7"><a href="http://www.deliciousdays.com/cforms-plugin"><em>cforms</em> contact form by delicious:days</a></p>

<a href="http://twitter.com/?status=RT%20%40%3A%20Fed%20to%20Overhaul%20Regulation%20of%20Foreign%20Banks%2C%20Eyeing%20Three-Part%20Framework%20-%20U.S.%20Law%20Watch%20http%3A%2F%2Ftinyurl.com%2Fc3uj2n4" class="tweet-this" ><img src="http://www.uslawwatch.com/wp-content/plugins/simple-tweet/img/tweet.gif" title="Tweet this!" alt="Tweet this!" />Tweet this!</a>]]></content:encoded>
			<wfw:commentRss>http://www.uslawwatch.com/2012/12/04/finance/fed-overhaul-regulation-foreign-banks-eyeing-threepart-framework/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BNA INSIGHTS: Patents Become the New Currency Among Competing Tech Companies</title>
		<link>http://www.uslawwatch.com/2012/12/04/intellectual-property/bna-insights-patents-currency-competing-tech-companies/</link>
		<comments>http://www.uslawwatch.com/2012/12/04/intellectual-property/bna-insights-patents-currency-competing-tech-companies/#comments</comments>
		<pubDate>Tue, 04 Dec 2012 09:34:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Intellectual Property]]></category>
		<category><![CDATA[patent assignment]]></category>
		<category><![CDATA[patent ownership]]></category>
		<category><![CDATA[Prior Art]]></category>

		<guid isPermaLink="false">http://www.uslawwatch.com/?p=4629</guid>
		<description><![CDATA[With patents emerging as valued currency, the author offers tips for determining their value...]]></description>
				<content:encoded><![CDATA[<p><img src="http://news.bna.com/ptln/core_adp/get_object/im209512.png" alt="Daniel R. Foster" /></p>
<p><em>By<strong> Daniel R. Foster</strong>, McDermott Will &amp; Emery, Irvine, Calif.</em></p>
<p>Patents are emerging as a valued currency. This is creating significant opportunities for businesses to generate revenue. Banks are finding new business opportunities advising companies on patent sales, a turf typically dominated by lawyers. 2012 also marks the launch of Intellectual Property Exchange International, which is self-described as “the world&#8217;s first financial exchange focused on Intellectual Property.” Whether done as a private or public sale, the science—and often art—of pricing patents is maturing as an asset valuation.</p>
<p>Despite the maturing market for patents, pricing patents can still be tricky and highly subjective, and can depend on many factors. Eastman Kodak Co. recently failed to generate sufficient bids to “auction” off its digital imaging patents. By comparison, Nortel Networks successfully auctioned off its patent portfolio in 2011 for a $4.5 billion haul received from a consortium of Apple Inc., EMC Corp., Ericsson, Microsoft Corp., Research in Motion Ltd., and Sony Corp. Consortiums, as contrasted with a single entity, were rumored to be among the bidders in the Kodak auction as well.</p>
<p>These auctions, as well as other recent high-profile transactions, illustrate how patents are more than ever a central determinant of a company&#8217;s success and its failure. However, it remains somewhat of a mystery as to how these patents are actually valued. The valuation of patents, using both objective and subjective factors, is critically important whether an individual or company is looking to buy or sell a large portfolio, such as Nortel or Kodak, or just a single patent. The value of each invention will generally depend on some common factors, which are discussed below.</p>
<h4>The importance of the patent.</h4>
<p>This is an obvious consideration, but one that is often not given its full due. Some questions to ask: Do the claims cover a fundamental technology or an incremental improvement over the prior art? How often is this patent cited in other patents or patent applications? Has there been a business plan developed for the patent? Has it been involved in litigation and, if so, how has the patent fared? Has the patent been subject to reexamination (and what were the results)? What does the prosecution history reveal, such as disclaimers of subject matter of the patent claims? Has this patent been licensed and, if so, for how much? Are there foreign counterparts? If there is a portfolio of patents, how do they relate to each other, and what is the scope of their collective coverage? &#8230;</p>

		<div id="usermessagea" class="cf_info "></div>
		<form enctype="multipart/form-data" action="/feed/#usermessagea" method="post" class="cform contact-form " id="cformsform">
		<ol class="cf-ol">
			<li id="li--1" class="textonly" style="color:red" >Read this entire article for free, simply activate your free 7 day trial access now.</li>
		</ol>
		<fieldset class="cf-fs1">
		<legend>Contact Bloomberg BNA</legend>
		<ol class="cf-ol">
			<li id="li--3" class=""><label for="cf_field_3"><span>Your Name</span></label><input type="text" name="cf_field_3" id="cf_field_3" class="single fldrequired" value="Your Name" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li--4" class=""><label for="cf_field_4"><span>Email</span></label><input type="text" name="cf_field_4" id="cf_field_4" class="single fldemail fldrequired" value=""/><span class="emailreqtxt">(valid email required)</span></li>
			<li id="li--5" class=""><label for="cf_field_5"><span>Message</span></label><textarea cols="30" rows="8" name="cf_field_5" id="cf_field_5" class="area"></textarea></li>
			<li id="li--6" class=""><label for="cforms_captcha" class="seccap"><span>Verification</span></label><input type="text" name="cforms_captcha" id="cforms_captcha" class="secinput" value=""/><img id="cf_captcha_img" class="captcha" src="http://www.uslawwatch.com/wp-content/plugins/cforms/cforms-captcha.php?ts=&amp;c1=4&amp;c2=5&amp;ac=abcdefghijkmnpqrstuvwxyz23456789&amp;i=i&amp;w=115&amp;h=35&amp;c=2B3AFF&amp;l=547FA9&amp;f=font32.ttf&amp;a1=-5&amp;a2=5&amp;f1=17&amp;f2=19&amp;b=16.gif" alt=""/><a title="reset captcha image" href="javascript:reset_captcha('')"><img class="captcha-reset" src="http://www.uslawwatch.com/wp-content/plugins/cforms/images/spacer.gif" alt="Captcha"/></a></li>
		</ol>
		</fieldset>
		<fieldset class="cf_hidden">
			<legend>&nbsp;</legend>
			<input type="hidden" name="cf_working" id="cf_working" value="One%20moment%20please..."/>
			<input type="hidden" name="cf_failure" id="cf_failure" value="Please%20fill%20in%20all%20the%20required%20fields."/>
			<input type="hidden" name="cf_codeerr" id="cf_codeerr" value="Please%20double-check%20your%20verification%20code."/>
			<input type="hidden" name="cf_customerr" id="cf_customerr" value="yyy"/>
			<input type="hidden" name="cf_popup" id="cf_popup" value="nn"/>
		</fieldset>
		<p class="cf-sb"><input type="submit" name="sendbutton" id="sendbutton" class="sendbutton" value="Submit"/></p></form><p class="linklove" id="ll"><a href="http://www.deliciousdays.com/cforms-plugin"><em>cforms</em> contact form by delicious:days</a></p>		<div id="usermessageb" class="cf_info " ></div>


<a href="http://twitter.com/?status=RT%20%40%3A%20BNA%20INSIGHTS%3A%20Patents%20Become%20the%20New%20Currency%20Among%20Competing%20Tech%20Companies%20-%20U.S.%20Law%20Watch%20http%3A%2F%2Ftinyurl.com%2Fdx8vzk3" class="tweet-this" ><img src="http://www.uslawwatch.com/wp-content/plugins/simple-tweet/img/tweet.gif" title="Tweet this!" alt="Tweet this!" />Tweet this!</a>]]></content:encoded>
			<wfw:commentRss>http://www.uslawwatch.com/2012/12/04/intellectual-property/bna-insights-patents-currency-competing-tech-companies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
