Rule · CFTC · 22 Dec 2015 · CFTC Staff Letter 15-68
The Division of Market Oversight grants time-limited no-action relief to swap execution facilities (SEFs) from the requirements under Commission regulation 37.205 to capture post-trade allocation information in their audit trail data and to conduct associated audit trail reviews. This relief applies to SEFs that maintain a rule requiring market participants to provide such information upon request and that obtain and review the data during trade practice surveillance or market surveillance investigations. The relief commences on the date of issuance and expires at 11:59 p.m. (EST) on November 15, 2017, while other audit trail obligations and recordkeeping requirements under regulation 1.35 remain in effect.
U.S. COMMODITY FUTURES TRADING COMMISSION
Three Lafayette Centre
1155 21st Street, NW, Washington, DC 20581
Telephone: (202) 418-5000
Facsimile: (202) 418-5521 www.cftc.gov
CFTC Letter 15-68
No-Action
December 22, 2015
Division of Market Oversight
Re: No-Action Relief for Swap Execution Facilities from Certain Audit Trail Requirements in Commission Regulation 37.205 Related to Post-trade Allocation Information Ladies and Gentlemen:
This letter responds to a request received from multiple parties 1 by the Division of Market Oversight (the “Division”) of the Commodity Futures Trading Commission (the “Commission”) for no-action relief for swap execution facilities (“SEFs”) from certain of the requirements under Commission regulation 37.205 that require SEFs to capture post-trade allocation information in their audit trail data. Background Title VII of the Dodd-Frank Wall Street Reform and Consumer Protection Act (the “Dodd-Frank Act”) 2 amended the Commodity Exchange Act (“CEA”) 3 to establish a comprehensive new regulatory framework for swaps. CEA Section 5h provides that to be registered and maintain registration, a SEF must comply with fifteen enumerated core principles and any requirements that the Commission may impose by rule or regulation. 4 Among the core principle requirements for SEFs, Core Principle 2 5 requires a SEF to have the capacity to detect, investigate and enforce its rules, and to capture information that may be used in establishing whether violations of those rules have occurred.
This letter responds to no-action relief requested in a jointly-submitted letter from Chicago Mercantile Exchange, Inc., Clear Markets, Inc., GTX SEF, LLC, ICE Swap Trade LLC, Javelin SEF, LLC, LatAm SEF, LLC, MarketAxess SEF Corporation, trueEX LLC, and 360 Trading Networks, Inc. These parties herein will be referred to as the “requesting parties.” Each of the requesters is currently operating as a temporarily-registered swap execution facility, pursuant to Commission regulation 37.3(c), and has currently pending before the Commission an application for full registration as a swap execution facility, pursuant to Commodity Exchange Act Section 5h and Commission regulation 37.3(b). Pub. L. 111-203, 124 Stat. 1376 (2010). 7 U.S.C. 1, et seq. (2012). CEA § 5h, as enacted by section 733 of the Dodd-Frank Act; 7 U.S.C. 7b-3 (2012). 5 CEA § 5h(f)(2); 7.U.S.C. 7b-3(f)(2).
No-Action Relief for Certain Audit Trail Requirements in Commission Regulation 37.205 Related to Post-trade Allocation Information On June 4, 2013, the Commission published final regulations governing SEFs. 6 Among the regulations promulgated under Core Principle 2, Commission regulation 37.205(a) requires SEFs to capture and retain all audit trail data necessary to detect, investigate, and prevent customer and market abuses. The audit trail data must be sufficient to reconstruct all indications of interest, requests for quotes, orders, and trades within a reasonable period of time and provide evidence of any violations of the SEF’s rules. In addition, the audit trail should enable the SEF to track an order from the time of receipt through fill, allocation, or other disposition. The requirement to capture allocation information in the audit trail data is also addressed in Commission regulation 37.205(b)(2), which requires a SEF’s electronic transaction history database to include, among other things, “identification of each account to which fills are allocated.” Requested Relief The requesting parties provide a number of reasons why SEFs do not capture post-trade allocation information in their audit trail data, as required by Commission regulations 37.205(a) and (b)(2). The requesting parties explain that trade allocations are made post-trade away from the SEF and typically occur between the clearing firm or the customer and the derivatives clearing organization (“DCO”), or at the middleware provider. Thus, the requesting parties assert that SEFs typically do not have access to post-trade allocation information, and for the most part will be unable to obtain such data from third parties, such as DCOs and swap data repositories (“SDRs”), due to confidentiality concerns. Even if SEFs could obtain the information from DCOs, SDRs or middleware providers, or alternatively, from the counterparties to the swap, the requesting parties note that the infrastructure necessary to securely transmit the post-trade allocation information, such as an application-programming interface (“API”) or secure file transfer protocol (“SFTP”) site, is currently not in place. Discussion The Division acknowledges the practical challenges that SEFs face in obtaining posttrade allocation information, as these allocations occur away from the SEFs, after the trade has been executed. The Division is therefore granting time-limited no-action relief from the requirements for SEFs to capture post-trade allocation information in their audit trail data, as required under Commission regulations 37.205(a) and (b)(2). The Division will continue to work with SEFs and other parties involved in the allocation workflow to identify methods for obtaining post-trade allocation information.
Core Principles and Other Requirements for Swap Execution Facilities, 78 FR 33476 (June 4, 2013) (“SEF Final Rules”).
No-Action Relief for Certain Audit Trail Requirements in Commission Regulation 37.205 Related to Post-trade Allocation Information Time-Limited No-Action Relief for SEFs The Division will grant the above time-limited no-action relief from the requirements for SEFs to capture post-trade allocation information in their audit trail data and to conduct associated audit trail reviews of post trade allocations, and will not recommend that the Division take enforcement action against any SEF that does not capture post-trade allocations in its audit trail data or conduct associated audit trail reviews of post trade allocations, as required by Commission regulations 37.205(a) and (b)(2), subject to the following conditions:
No-Action Relief for Certain Audit Trail Requirements in Commission Regulation 37.205 Related to Post-trade Allocation Information Sincerely, Vincent A. McGonagle Director Division of Market Oversight
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.
A newer document in RegAlert amends this one; it applies as amended.
“The letter provides that, subject to certain conditions, the Division will not recommend enforcement action against a swap execution facility (“SEF”) which does not capture post-execution allocation information in its audit trail or conduc…”
“Title VII of the Dodd-Frank Wall Street Reform and Consumer Protection Act (the “Dodd-Frank Act”) 2 amended the Commodity Exchange Act (“CEA”) 3 to establish a comprehensive new regulatory framework for swaps.”
“Pub. L. 111-203, 124 Stat. 1376 (2010). 7 U.S.C. 1, et seq. (2012).”
Amended 1 time · last 2017-10-31
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