Individual decision · CFTC · 18 Dec 2009 · CFTC Staff Letter 10-03
The Division of Clearing and Intermediary Oversight provides no-action relief to entities A, B, and C from registering as commodity pool operators under Section 4m(1) of the Commodity Exchange Act. This relief applies specifically to their roles as managing partners, general partners, or voting shareholders of Funds 1 through 7, provided that entity D registers and serves as the CPO for all Funds. The Division will not recommend enforcement against A, B, or C for failure to register, subject to the condition that D remains registered and assumes all management authority. The relief does not exempt these entities from other statutory obligations, including antifraud provisions and reporting requirements.
U.S. COMMODITY FUTURES TRADING COMMISSION
Three Lafayette Centre
1155 21st Street, NW, Washington, DC 20581
Telephone: (202) 418-5430
Facsimile: (202) 418-5547 aradhakrishnan@cftc.gov Division of Clearing and Intermediary Oversight Ananda Radhakrishnan Director CFTC Letter No. 10-03 No-Action December 18, 2009 Division of Clearing and Intermediary Oversight Re: Section 4m(l) Dear :
This is in response to your letter dated June 9, 2009, to the Division of Clearing and Intermediary Oversight (the “Division”) of the Commodity Futures Trading Commission (the “Commission”), as supplemented by your letters dated August 14, 2009, August 26, 2009 and December 1, 2009, your facsimile transmission dated July 1, 2009, and your email dated December 7, 2009 (collectively, the “correspondence”). By the correspondence, you seek relief from the requirement to register with the Commission as a commodity pool operator (“CPO”) under Section 4m(1) of the Commodity Exchange Act (the “Act”)1 on behalf of: (i) “A”, a registered CPO, in connection with serving as the managing partner of (“Fund 1”); (ii) “B” in connection with operating (“Fund 2”), (“Fund 3”), (“Fund 5”), and (“Fund 6”); and (iii) “C” in connection with serving as the general partner of (“Fund 4”) and (“Fund 7”), such that “D” may register and serve as the CPO of Funds 1 through 7 (each, a “Fund,” and collectively, the “Funds”) instead, while “A” would withdraw his registration as a CPO.2
Based upon the representations made in the correspondence, as supplemented by information provided to Division staff by Joseph Picone, Compliance Manager, National Futures Association (“NFA”),3 we understand the relevant facts to be as follows. Fund 1 was formed in 1992, with “A” serving as the managing member and registered CPO thereof. Subsequently,
7 U.S.C. §6m(l) (2006). The Act may be accessed through the Commission’s website, at Uhttp://www.cftc.gov/lawandregulationlindex.htmU. With your August 26 letter you submitted an organizational chart showing the relationships of “A”, “B”, “C”, “D”, and the Funds. This information was provided in a telephone conversation between Picone and Division staff held on November 2, 2009.
from June 2003 to February 2008, Funds 2 through 7 were formed, with various entities wholly owned by “A” serving as either the managing member or general partner or owning 100% of the voting shares of a Fund. These structures are intended to facilitate the favorable tax treatment of performance allocations to “A”, “B” and “C”. Upon review, NFA concluded that “B” and “C”, in addition to “A”, should be registered as a CPO by virtue of their relationship to a Fund. However, in order to avoid unnecessary duplicative registration burdens, NFA further suggested that “A” make the instant request.4
In support of the request you represent that:
position is, however, subject to the conditions that “D”: (1) will serve as the CPO of the Funds; and (2) will register as a CPO and remain registered as such. The relief issued by this letter does not excuse “A”, “B” or “C” from compliance with any other applicable requirements contained in the Act or in the Commission’s regulations issued thereunder. For example, they remain subject to all antifraud provisions of the Act8 and the Commission’s regulations, as well as to the reporting requirements for traders set forth in Parts 15, 18 and 19 of the Commission’s regulations and all applicable provisions of Part 4, including Regulations 4.20 and 4.41. Also, the no-action position taken in this letter is applicable to “A”, “B” and “C” solely in connection with the operation of the Funds. This letter, and the position taken herein, are based upon the representations made to us and are subject to compliance with the conditions stated above. Any different, changed or omitted material facts or circumstances might render this letter void. You must notify the Division immediately in the event that the operations or activities of “A”, “B”, “C”, “D” or the Funds change in any material respect from those as represented to us. Further, this letter and the position taken herein represent the views of this Division only, and do not necessarily represent the views of the Commission or of any other office or division of the Commission. If you have any questions concerning this correspondence, please contact me or Peter B. Sanchez, Special Counsel, at (202) 418-5237. Very truly yours, Ananda Radhakrishnan Director cc: Joseph Picone Compliance Manager National Futures Association See, e.g., 7 U.S.C. §§6b and 6o.
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
The documents this one cites, and the documents that cite it.
“See, e.g. CFTC Staff Letter 09-03 [Current Transfer Binder] Comm. Fut. L. Rep. (CCH) ¶31,378 (May 21, 2009).”
“See, e.g., CFTC Staff Letter 10-03 (Dec. 18, 2009), which may be accessed on the Commission's website at”
More like this from CFTC
CFTC published 1 document in the last 30 days. We email you each new one the day it's published.
Source: Commodity Futures Trading Commission — original document · Summary generated with machine assistance and reviewed before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added · updated