<?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>The Harvard Law School Forum on Corporate Governance</title>
	<atom:link href="https://corpgov.law.harvard.edu/2012/04/12/section-13d-reporting-requirements-need-updating/feed/" rel="self" type="application/rss+xml" />
	<link>https://corpgov.law.harvard.edu</link>
	<description>The leading online blog in the fields of corporate governance and financial regulation.</description>
	<lastBuildDate>Wed, 03 Jun 2026 20:58:09 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.8</generator>

<image>
	<url>https://corpgov.law.harvard.edu/wp-content/uploads/2024/02/cropped-photography-4-e1706898544564-1-32x32.png</url>
	<title>Section 13(d) Reporting Requirements Need Updating &#8211; The Harvard Law School Forum on Corporate Governance</title>
	<link>https://corpgov.law.harvard.edu</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Section 13(d) Reporting Requirements Need Updating</title>
		<link>https://corpgov.law.harvard.edu/2012/04/12/section-13d-reporting-requirements-need-updating/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=section-13d-reporting-requirements-need-updating</link>
		<comments>https://corpgov.law.harvard.edu/2012/04/12/section-13d-reporting-requirements-need-updating/#comments</comments>
		<pubDate>Thu, 12 Apr 2012 13:18:12 +0000</pubDate>
<!-- 		<dc:creator><![CDATA[]]></dc:creator> -->
				<category><![CDATA[Accounting & Disclosure]]></category>
		<category><![CDATA[Practitioner Publications]]></category>
		<category><![CDATA[Securities Regulation]]></category>
		<category><![CDATA[Beneficial owners]]></category>
		<category><![CDATA[Reporting regulation]]></category>
		<category><![CDATA[Schedule 13D]]></category>
		<category><![CDATA[SEC]]></category>
		<category><![CDATA[Williams Act]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/corpgov/?p=27383?d=20150113150052EST</guid>
		<description><![CDATA[A year has passed since Wachtell, Lipton, Rosen &#38; Katz submitted a petition to the U.S. Securities and Exchange Commission requesting that it update its Schedule 13D reporting requirements to “clos[e] the Schedule 13D ten-day window between crossing the 5 percent disclosure threshold and the initial filing deadline, and adopt[] a broadened definition of ‘beneficial [&#8230;]]]></description>
				<content:encoded><![CDATA[<hgroup><em>Posted by David A. Katz, Wachtell, Lipton, Rosen & Katz, on Thursday, April 12, 2012 </em><div class='e_n' style='background:#F8F8F8;padding:10px;margin-top:5px;margin-bottom:10px;text-indent:2.5em;'><strong style='margin-left:-2.5em;'>Editor's Note: </strong> <p style="margin:0; display:inline;"><a href="http://www.wlrk.com/dakatz/" target="_blank">David A. Katz</a> is a partner at Wachtell, Lipton, Rosen &amp; Katz specializing in the areas of mergers and acquisitions and complex securities transactions. This post is based on an article by Mr. Katz and Laura A. McIntosh that first appeared in the <em>New York Law Journal</em>. The views expressed are the authors’ and do not necessarily represent the views of the partners of Wachtell, Lipton, Rosen &amp; Katz or the firm as a whole. This post discusses a letter submitted to the SEC by Professor <a href="http://www.law.harvard.edu/faculty/bebchuk/" target="_blank">Lucian Bebchuk</a> and Professor <a href="http://www.law.columbia.edu/fac/Robert_Jackson" target="_blank">Robert J. Jackson Jr.</a> concerning possible changes to Section 13(d) rules, available <a href="http://blogs.law.harvard.edu/corpgov/2011/07/12/how-the-sec-should-consider-possible-changes-in-section-13d-rules/">here</a>.</p>
</div></hgroup><p>A year has passed since Wachtell, Lipton, Rosen &amp; Katz submitted a petition to the U.S. Securities and Exchange Commission requesting that it update its Schedule 13D reporting requirements to “clos[e] the Schedule 13D ten-day window between crossing the 5 percent disclosure threshold and the initial filing deadline, and adopt[] a broadened definition of ‘beneficial ownership’ to fully encompass alternative ownership mechanisms.” As <a name="1b"></a>the petition noted: “Recent maneuvers by activist investors both in the U.S. and abroad have demonstrated the extent to which current reporting gaps may be exploited, to the detriment of issuers, other investors, and the market as a whole.” <a href="http://blogs.law.harvard.edu/corpgov/2012/04/12/section-13d-reporting-requirements-need-updating#1">[1]</a> The SEC is scheduled to issue a concept release later this spring addressing the concerns raised by the petition. Activist hedge funds have responded strongly—opposing changes to the current Schedule 13D rules—complaining that the suggested changes will significantly hurt their business. Regardless of whether the present reporting scheme allows activist investors to profit by keeping their accumulations secret, it is clear that the present reporting regime is outdated and needs to be reconsidered. At a time when the SEC is requiring greater transparency from public companies and their executives, the same policy concerns demand greater transparency with respect to the acquisition of equity securities of public companies by third parties.</p>
<p> <a href="https://corpgov.law.harvard.edu/2012/04/12/section-13d-reporting-requirements-need-updating/#more-27383" class="more-link"><span aria-label="Continue reading Section 13(d) Reporting Requirements Need Updating">(more&hellip;)</span></a></p>
]]></content:encoded>
			<wfw:commentRss>https://corpgov.law.harvard.edu/2012/04/12/section-13d-reporting-requirements-need-updating/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
