Hedge Fund Blogs From HedgeCo.Net

Impact of CFTC Registration and Reporting Requirements on Commodity Pool Operators

Recently, the Commodity Futures Trading Commission (CFTC) finalized several amendments to the registration and compliance requirements for commodity pool operators (CPOs), including rescinding the exemption from CFTC registration provided in Rule 4.13, according to hedge fund law firm Rothstein Kass.

The rescission of 4.13 has forced fund managers to reassess their trading in commodity interests as part of an effort to determine whether they can avail themselves of an alternative exemption from CFTC registration.

Although the 4.13 exemption was effectively repealed as of April 24, 2012, managers currently utilizing this exemption for one or more of their pools can continue to rely on it until December 31, 2012. Read more of this article.

About Alex Akesson

Alex has been specializing in hedge fund and alternative investment news since April 2006. Working mainly in research and manager interviews, she has published breaking news on the hedge fund industry on her blog, as well as several industry publications. Her access to hedge fund managers gives her insight into news stories as well, and the ability to track press releases and other breaking news in real time.
This entry was posted in law. Bookmark the permalink.

2 Responses to Impact of CFTC Registration and Reporting Requirements on Commodity Pool Operators

  1. Pj says:

    Great summary – should be read by every CTA and Pool Operator including commodity platform providers.
    Pj *.*

  2. Dave Snow says:

    Great article for Pool Operators. To keep up to date on these issues everyone should come to the West Palm Beach CPO – Certified Pool Operator Class that is available in September.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>