# Real-Time Public Reporting Requirements

> Briefs, arguments, decisions, and more.

URL: https://www.frixlaw.com/law-library/documents/fr%3A2020-04405

## Record

- **Collection:** Federal Register
- **Document type:** Proposed Rule
- **Published:** April 17, 2020
- **Citation:** 85 FR 21516

## Text

COMMODITY FUTURES TRADING COMMISSION
17 CFR Part 43
RIN 3038-AE60
Real-Time Public Reporting Requirements

AGENCY:

Commodity Futures Trading Commission.

ACTION:

Notice of proposed rulemaking.

SUMMARY:

The Commodity Futures Trading Commission (“Commission” or “CFTC”) is proposing revisions to its regulations setting forth the real-time public reporting and dissemination requirements for swap data repositories (“SDRs”), derivatives clearing organizations (“DCOs”), swap execution facilities (“SEFs”), designated contract markets (“DCMs”), swap dealers (“SDs”), major swap participants (“MSPs”), and swap counterparties that are neither SDs nor MSPs. The Commission is also proposing revisions that, among other things, change the “block trade” definition, change the block swap categories, update the block thresholds and cap sizes, and adjust the delay for the public dissemination of block transactions.

DATES:

Comments must be received on or before May 20, 2020.

ADDRESSES:

You may submit comments, identified by RIN number 3038-AE60, by any of the following methods:

•
CFTC Website: https://comments.cftc.gov.
Follow the instructions for submitting comments through the Comments Online process on the website.

•
Mail:
Send to Christopher Kirkpatrick, Secretary of the Commission, Commodity Futures Trading Commission, Three Lafayette Centre, 1155 21st Street NW, Washington, DC 20581.

•
Hand Delivery/Courier:
Same as Mail, above.

Please submit your comments using only one method.

All comments must be submitted in English, or if not, accompanied by an English translation. Comments will be posted as received to
https://www.cftc.gov.
You should submit only information that you wish to make available publicly. If you wish the Commission to consider information that you believe is exempt from disclosure under the Freedom of Information Act (“FOIA”), a petition for confidential treatment of the exempt information may be submitted according to the procedures established in § 145.9 of the Commission's regulations.
1

1
17 CFR 145.9. Commission regulations referred to herein are found at 17 CFR chapter I.

The Commission reserves the right, but shall have no obligation, to review, pre-screen, filter, redact, refuse or remove any or all of your submission from
https://www.cftc.gov
that it may deem to be inappropriate for publication, such as obscene language. All submissions that have been redacted or removed that contain comments on the merits of the rulemaking will be retained in the public comment file and will be considered as required under the Administrative Procedure Act and other applicable laws, and may be accessible under the FOIA.

FOR FURTHER INFORMATION CONTACT:

David E. Aron, Special Counsel, (202) 418-6621,
daron@cftc.gov,
Division of Market Oversight; Meghan Tente, Acting Associate Director, 202-418-5785,
mtente@cftc.gov,
Division of Market Oversight; Owen J. Kopon, Special Counsel, (202) 418-5360,
okopon@cftc.gov,
Division of Swap Dealer and Intermediary Oversight; Matthew Jones, Special Counsel, (202) 418-6710,
majones@cftc.gov,
Division of Market Oversight; John Roberts, Senior Research Analyst, (202) 418-5943,
jroberts@cftc.gov,
Office of the Chief Economist; in each case at the Commodity Futures Trading Commission, Three Lafayette Centre, 1155 21st Street NW, Washington, DC 20581.

SUPPLEMENTARY INFORMATION:

Table of Contents

I. Background and Introduction

A. Reporting Rules Review

B. Statutory and Regulatory Framework for Real-Time Public Reporting

II. Proposed Amendments to Part 43

A. § 43.1—Purpose, Scope, and Rules of Construction

B. § 43.2—Definitions

C. § 43.3—Method and Timing for Real-Time Public Reporting

D. § 43.4—Swap Transaction and Pricing Data To Be Publicly Disseminated in Real-Time

E. § 43.5—Time Delays for Public Dissemination of Swap Transaction and Pricing Data

F. § 43.6—Block Trades

G. § 43.7—Delegation of Authority

III. Swap Transaction and Pricing Data Reported to and Publicly Disseminated by Swap Data Repositories

A. General

B. Swap Transaction and Pricing Data Elements

IV. Compliance Date

V. Related Matters

A. Regulatory Flexibility Act

B. Paperwork Reduction Act

C. Cost-Benefit Considerations

D. Antitrust Considerations

I. Background and Introduction

A. Reporting Rules Review

The Commission's real-time public reporting regulations were adopted in 2012 and are located in part 43 of the Commission's regulations. The 2012 rulemaking set forth regulations that require swap counterparties, SEFs, and DCMs to report publicly reportable swap transactions (“PRST”) to SDRs.
2

In addition, the 2012 RTR Final Rule set forth regulations that require SDRs to publicly disseminate swap transaction and pricing data (“STAPD”) in real-time.
3

In 2013, the Commission adopted a block trade rule
4

to implement the statutory requirements of Commodity Exchange Act (“CEA”) section 2(a)(13)(E)(i)-(iv).
5

2
Real-Time Public Reporting (“RTR”) of Swap Transaction Data, 77 FR 1182 (Jan. 9, 2012) (“2012 RTR Final Rule”); 17 CFR 43.3(a)(1)-(3) and (b)(1).

3

See id.;
17 CFR 43.3(b)(2).

4
Procedures to Establish Appropriate Minimum Block Sizes for Large Notional Off-Facility Swaps and Block Trades, 78 FR 32866 (May 31, 2013) (“Block Trade Rule”).

5
CEA section 2(a)(13)(E)(i)-(iv). These CEA sections contain provisions (
e.g.,
time delays) that the Commission must include in its required rulemakings governing public reporting of STAPD for the categories of swaps set forth in CEA sections 2(a)(13)(C)(i) and (ii), 7 U.S.C. 2(a)(13)(C)(i) and (ii).

Several years ago, the Division of Market Oversight (“DMO”) conducted a review of the Commission's swap reporting rules. After completing that review, on July 10, 2017, DMO announced
6

its Roadmap to Achieve High Quality Swaps Data (“Roadmap”),
7

consisting of a comprehensive review to, among other things: “[(i)] Evaluate real-time reporting regulations in light of goals of liquidity, transparency, and price discovery in the swaps market[; and (ii)] Address ongoing issues of reporting packages, prime brokerage, allocations, risk mitigation services/compressions, EFRPs, and post-priced swaps by clarifying obligations and identifying those distinct types of transactions to increase the utility of the real-time public tape.
8

6

See
CFTC Letter 17-33, DMO Announces Review of Swap Reporting Rules in Parts 43, 45, and 49 of Commission Regulations (July 10, 2017),
available at http://www.cftc.gov/idc/groups/public/@lrlettergeneral/documents/letter/17-33.pdf.

7
The Roadmap is available at
https://www.cftc.gov/sites/default/files/idc/groups/public/@newsroom/documents/file/dmo_swapdataplan071017.pdf.

8
Roadmap at 11.

In April 2019, the Commission adopted its first notice of proposed rulemaking (“NPRM”) as part of the

Roadmap review.
9

The 2019 Part 49 NPRM proposes amendments to streamline and clarify the Commission's SDR regulations in parts 23, 43, 45, and 49. Among other things, the 2019 Part 49 NPRM proposes modifications to the existing requirements on SDRs for confirming the accuracy of swap data with swap counterparties, and proposes requiring reporting counterparties to verify the accuracy of swap data.

9

See generally
Certain Swap Data Repository and Data Reporting Requirements, 84 FR 21044 (May 13, 2019) (“2019 Part 49 NPRM”).

The Commission has received extensive feedback that addressed many swap reporting topics.
10

In connection with the Roadmap review, DMO conducted extensive outreach with commenters. DMO held calls and meetings, and reviewed the comment letters to better understand the challenges facing market participants and their suggestions on how to improve real-time public reporting. Comments raised on specific issues are discussed in the relevant sections throughout this release.

10
Comment letters are available at
https://comments.cftc.gov/PublicComments/CommentList.aspx?id=1824.

After reviewing the Roadmap feedback, the Commission is proposing revisions to the following aspects of the part 43 real-time public reporting regulations: The method and timing of real-time reporting and public dissemination, generally and for specific types of swaps; the delay and anonymization of the public dissemination of block trades or large notional trades; the standardization and validation of real-time reporting fields; the delegation of specific authority to Commission staff; and the clarification of specific real-time reporting questions and common issues.
11

11
At the same time, the Commission is proposing a separate NPRM for publication in the
Federal Register
amending the part 45 swap data reporting regulations (“2020 Part 45 NPRM”).

B. Statutory and Regulatory Framework for Real-Time Public Reporting

Section 2(a)(13)(B) of the CEA authorizes the Commission to make STAPD available to the public in such form and at such times as the Commission determines appropriate to enhance price discovery. Section 2(a)(13)(C) requires that the Commission publish rules for the public availability of STAPD. Section 2(a)(13)(D) permits the Commission to require registered entities to publicly disseminate STAPD.

In 2012, the Commission adopted part 43 to implement rules providing for the public availability of STAPD as directed by section 2(a)(13).
12

Section 2(a)(13)(E) required that the Commission's rules contain provisions for: (i) Ensuring the STAPD publicly disseminated does not identify the swap counterparties; (ii) specifying the criteria for large notional swaps (block trades), for particular markets and contracts; (iii) specifying an appropriate time delay for reporting block trades to the public; and (iv) taking into account whether the public disclosure will materially reduce market liquidity. In 2013, the Commission adopted the Block Trade Rule to further implement the statutory requirements of CEA section 2(a)(13)(E)(i)-(iv).
13

12
2012 RTR Final Rule.

13

See
Block Trade Rule.

Part 43 currently requires reporting parties to report PRSTs to SDRs as soon as technologically practicable (“ASATP”) after execution.
14

Part 43 defines a PRST as: (i) Any executed swap that is an arm's-length transaction between two parties that results in a corresponding change in the market risk position between the two parties; or (ii) any termination, assignment, novation, exchange, transfer, amendment, conveyance, or extinguishing of rights or obligations of a swap that changes the pricing of the swap.
15

14
17 CFR 43.3(a).

15
17 CFR 43.2.

Part 43 currently defines execution as an agreement by the parties (whether orally, in writing, electronically, or otherwise) to the terms of a swap that legally binds the parties to such terms under applicable law.
16

In addition, execution is defined to occur simultaneously with or immediately following the affirmation of the swap.
17

16

Id.

17

Id.

For a PRST executed on or pursuant to the rules of a SEF or DCM, a party to such transaction satisfies its requirement to report the transaction to an SDR by executing it on the SEF or DCM.
18

For off-facility transactions, § 43.3(a)(3) specifies the reporting party for PRSTs and requires the reporting party to report the swap to an SDR ASATP following execution.

18
17 CFR 43.3(a)(2).

SDRs are required to ensure that STAPD is publicly disseminated ASATP after receiving it from a SEF, DCM, or reporting party, unless it is subject to a time delay described in § 43.5, in which case the PRST must be publicly disseminated in the manner described in § 43.5.
19

Regulation 43.3(b)(3), the “embargo rule,” generally prohibits SEFs, DCMs, SDs, and MSPs from disseminating STAPD to their customers and participants prior to the public dissemination of such data to an SDR.

19
17 CFR 43.3(b)(2).

The STAPD to be disseminated in real-time consists of the data elements listed in appendix A to part 43.
20

SDRs are permitted to request additional information from reporting parties, SEFs, and DCMs, but may not publicly disseminate it.
21

SDRs must comply with other regulations concerning how STAPD is disseminated, including ensuring they do not disclose the identities of the counterparties;
22

restrictions on disclosing underlying assets for certain swaps in the other commodity asset class;
23

and rounding and capping notional or principal amounts.
24

20
17 CFR 43.4(b).

21
17 CFR 43.4(c).

22
17 CFR 43.4(d)(1).

23
17 CFR 43.4(d)(4).

24
17 CFR 43.4(g)-(h).

With respect to the delay for block trades, the Commission assigned swap contracts to “swap categories” in the Block Trade Rule for the purpose of applying a common appropriate minimum block size (“AMBS”) to different swap transactions. To create these swap categories, the Commission divided swaps into five asset classes: Interest rates; equity; credit; foreign exchange; and other commodities. The Commission then split these asset classes into the various swap categories.
25

25
17 CFR 43.6(b).

The Commission phased-in the time delays for the public dissemination of block trades based on four factors: (1) Whether the swap is executed on or pursuant to the rules of a SEF or DCM; (2) the swap's asset class; (3) whether the swap is mandatorily cleared; and (4) whether at least one counterparty is an SD or MSP.
26

26
17 CFR 43.5.

The initial time delays were: 30 minutes for blocks executed on a SEF or DCM;
27

30 minutes for large notional off-facility swaps (“LNOFs”)
28

subject to mandatory clearing with a SD/MSP counterparty;
29

4 hours for LNOFs subject to mandatory clearing with no SD/MSP counterparty;
30

1 hour for

LNOFs not subject to mandatory clearing in the interest rate, credit, foreign exchange, or equity asset classes with at least one SD/MSP counterparty;
31

4 hours for LNOFs in the other commodity asset class not subject to mandatory clearing with at least one SD/MSP counterparty;
32

and 48 business hours for LNOFs in all asset classes not subject to mandatory clearing for which neither counterparty is an SD/MSP.
33

The Commission has not established post-initial AMBS under § 43.6(f)(1).

27
17 CFR 43.5(c)(2) and (d)(1). After the first year, the delay reduced to 15 minutes. 17 CFR 43.5(d)(2).

28
Large notional off-facility swaps are off-facility swaps with notional or principal amounts at or above the AMBS applicable to such PRST and that are not a block trade as defined in § 43.2. 17 CFR 43.2 (definition of “large notional off-facility swap”).

29
17 CFR 43.5(c)(3) and (e)(2)(i). After the first year, the delay reduced to 15 minutes. 17 CFR 43.5(e)(2)(ii).

30
17 CFR 43.5(c)(3) and (e)(3)(i). During year 2, the time delay reduced to 2 hours. 17 CFR

43.5(e)(3)(ii). After year 2, the time delay reduced to 1 hour. 17 CFR 43.5(e)(3)(iii).

31
17 CFR 43.5(c)(4) and (f)(1). After the first year, the time delay reduced to 30 minutes. 17 CFR 43.5(f)(2).

32
17 CFR 43.5(c)(5) and (g)(1). After the first year, the time delay reduced to 2 hours. 17 CFR 43.5(g)(2) and (g)(3).

33
17 CFR 43.5(c)(6) and (h)(1). During year 2, the time delay reduced to 36 business hours. 17 CFR 43.5(h)(2). After year 2, the time delay reduced to 24 business hours. 17 CFR 43.5(h)(3).

II. Proposed Amendments to Part 43

A. § 43.1—Purpose, Scope, and Rules of Construction

The Commission is proposing several non-substantive changes to § 43.1. The Commission is proposing to remove § 43.1(b). Regulation 43.1(b)(1), titled “Scope,” states that part 43 applies to all swaps, as defined in CEA § 1a(47),
34

and lists certain categories of swaps as examples. Regulation 43.1(b)(2) states that part 43 applies to registered entities and parties to a swap and lists certain categories of swap parties. The Commission preliminarily believes that these provisions are superfluous, given that the scope of what part 43 covers is clear from various CEA sections and the operative provisions of part 43.

34
7 U.S.C. 1a(47).

The Commission also proposes to redesignate current § 43.1(c), entitled “Rules of construction,” as § 43.1(b). The first sentence of § 43.1(c) currently reads as follows: The examples in this part and in appendix A to this part are not exclusive. The Commission proposes to delete the reference to “appendix A” to reflect that the Commission proposes to replace appendix A with new appendix C.
35

The Commission is not proposing to remove this full requirement, however, in case there are other places within part 43 in which market participants would rely on examples.

35
As discussed in section II.E.3., the Commission is proposing to delete appendix C in connection with changes to the block delays. In its place, the Commission is proposing to update the list of STAPD elements in current appendix A and move them to appendix C. At the same time, DMO is publishing draft technical specifications on
https://www.cftc.gov
for comment.

The Commission also proposes to delete § 43.1(d), entitled “Severability.” Regulation 43.1(d) currently provides that if any provision of this part, or the application thereof to any person or circumstance, is held invalid, such invalidity shall not affect other provisions or application of such provision to other persons or circumstances which can be given effect without the invalid provision or application. The Commission believes that a severability provision is not appropriate because, without knowing which provision a future court might hold invalid, it is unclear that the Commission would interpret all related remaining provisions of part 43 as continuing to be effective without the invalid provision(s), and the Commission wishes to maintain the flexibility to make that determination at the time of any such holding.

B. § 43.2—Definitions

The Commission is proposing several changes to § 43.2. The Commission is proposing to add a number of new definitions, amend certain existing definitions, and remove certain definitions. Within each of those categories, because § 43.2 is arranged alphabetically, the Commission discusses its proposed changes to § 43.2 in that order as well, except as otherwise noted.

Currently, § 43.2 does not have lettered paragraphs. The Commission is proposing to add new paragraphs (a) and (b) to § 43.2. Proposed new paragraph (a) would contain all of the definitions in current § 43.2, as the Commission proposes to modify them. Proposed new paragraph (b) would provide that terms not defined in part 43 have the meanings assigned to those terms in § 1.3 of the Commission's regulations.

1. Proposed New Definitions

The Commission is proposing to add a definition of “execution date” to § 43.2. As proposed, “execution date” would mean the date, determined by reference to eastern time, on which swap execution has occurred. This proposed new definition is used in a discussion of proposed changes to the reporting deadline for post-priced swaps (“PPSs”) in section II.C.2. below.

The Commission is proposing to add a definition of “post-priced swap” to § 43.2. As proposed, a “post-priced swap” would mean an off-facility swap for which the price has not been determined at the time of execution. This proposed new definition is used in a discussion of proposed changes to reporting deadlines for PPSs in section II.C.2. below.

The Commission is proposing to add a definition of “reporting counterparty.” The Commission notes that the definition itself would be the same as the current definition of “reporting party” in § 43.2. This proposed new definition is used in a discussion of proposed changes to the § 43.3 regulations for the method and timing of real-time public reporting in section II.C.1. below.

The term “swap execution facility” is used throughout parts 43 and 45. While part 45 provides a definition of “swap execution facility,” no such definition exists in part 43. Therefore, in order to harmonize parts 43 and 45, the Commission is proposing to add a definition of “swap execution facility” in part 43. As proposed, “swap execution facility” means a trading system or platform that is a swap execution facility as defined in CEA section 1a(50) and in § 1.3 of this chapter and that is registered with the Commission pursuant to CEA section 5h and § 37 of this chapter. The proposed definition reflects the proposed non-substantive minor technical changes that are proposed to the definition of “swap execution facility” in the concurrent part 45 proposal.

The Commission is proposing to add a definition of “swap transaction and pricing data” to § 43.2. As proposed, “swap transaction and pricing data” means all data for a swap in appendix C to part 43 required to be reported or publicly disseminated pursuant to part 43. The Commission believes that providing a definition for the type of data addressed in part 43 should help distinguish between the different types of data reported pursuant to the different reporting regulations.

The Commission is also proposing to add the following six definitions to § 43.2: “Mirror swap;” “pricing event;” “prime broker;” “prime brokerage agency arrangement;” “prime brokerage agent;” and “trigger swap.” These proposed definitions are all related to swaps entered into by prime brokers. Because all of these six proposed definitions are used in the text of proposed § 43.3(a)(6) or are used in one or more of the proposed definitions that are in turn used in proposed § 43.3(a)(6), all of the six proposed definitions are set forth and discussed in section II.C.4. below.

2. Proposed Amendments to Existing Definitions

The Commission is proposing non-substantive ministerial changes to the

following definitions in § 43.2: “As soon as technologically practicable;” “asset class;” “novation;” “other commodity;” and “reference price.”

The Commission is also proposing to amend the definition of “appropriate minimum block size” in § 43.2. Currently, § 43.2 defines “appropriate minimum block size” to mean the minimum notional or principal amount for a category of swaps that qualifies a swap within such category as a block trade or large notional off-facility swap. This proposed amended definition is used in a discussion of proposed changes to the § 43.5(a) regulations for the time delays for the public dissemination of STAPD in section II.E.1. below.

The Commission is proposing to amend the definition of “block trade” in § 43.2. Currently, § 43.2 defines “block trade” to mean a PRST that: (1) Involves a swap that is listed on a registered SEF or DCM; (2) occurs away from the registered SEF's or DCM's trading system or platform and is executed pursuant to the registered SEF's or DCM's rules and procedures; (3) has a notional or principal amount at or above the AMBS applicable to such swap; and (4) is reported subject to the rules and procedures of the registered SEF or DCM and the rules described in part 43, including the appropriate time delay requirements set forth in § 43.5.

In November 2018, the Commission issued a comprehensive proposal to amend the SEF regulatory framework.
36

Among other things, the 2018 SEF NPRM proposed to amend the definition of “block trade” as part of the proposal's holistic approach to amending the SEF regulatory framework. Given the complex, expansive, and comprehensive nature of the 2018 SEF Proposal, however, the Commission continues to evaluate it.

36

See
Swap Execution Facilities and Trade Execution Requirement, 83 FR 61946 (Nov. 30, 2018) (“2018 SEF NPRM”).

In the interim, in order to provide regulatory and legal certainty to SEFs and market participants, the Commission recently proposed to address certain outstanding no-action relief, including relief related to block trades that SEFs and market participants have operated under for several years.
37

In particular, in the 2020 SEF NPRM, the Commission proposed an amendment to condition (2) of the block trade definition that would read as follows: (2) Is executed on the trading system or platform, that is not an order book as defined in § 37.3(a)(3), of a registered SEF or occurs away from a registered SEF's or DCM's trading system or platform and is executed pursuant to the registered SEF's or DCM's rules and procedures.
38

While the Commission is proposing additional amendments to the “block trade” definition in this NPRM, this NPRM is consistent with the proposed amendments to the definition of “block trade” under the 2020 SEF NPRM.

37

See
Swap Execution Facility Requirements and Real-Time Reporting Requirements, 85 FR 9407 (Feb. 19, 2020) (“2020 SEF NPRM”).

38
In the 2020 SEF NPRM, the Commission explained that (1) “permitting execution of block trades on a SEF's non-[o]rder [b]ook trading systems or platforms promotes the statutory SEF goal of promoting the trading of swaps on SEFs” and (2) “for swap block trades that are [intended to be cleared] and executed on a SEF's non-[o]rder [b]ook trading system or platform, the Commission believes that the proposed revised definition would (i) allow [futures commission merchants (“FCMs”)] to conduct pre-execution credit screenings in accordance with § 1.73; and (ii) allow SEFs to facilitate those screenings in accordance with the Commission's proposed requirement under § 37.702(b).” 2020 SEF NPRM at 9419.

The Commission is proposing to create a two part definition of “block trade” in § 43.2. Paragraph (3) of the current definition of “block trade”
39

would be incorporated into paragraph (1) of the “block trade” definition, which would apply to “off-facility swaps.”
40

The proposed “block trade” definition from the 2020 SEF NPRM, which would apply to swaps that are not “off-facility swaps” and that have specified connections to a SEF or a DCM, would become paragraph (2) of the proposed “block trade” definition in this NPRM.
41

Moreover, the Commission believes these proposed changes would eliminate the need for separate definitions of block trades and large notional off-facility swaps.
42

Therefore, as discussed below in section II.B.3., the Commission is removing the definition of large notional off-facility swaps from its regulations.

39
This paragraph currently reads: Has a notional or principal amount at or above the appropriate minimum block size applicable to such swap.

40
As proposed, paragraph (1) of the “block trade” definition would read: (1) With respect to an off-facility swap, a publicly reportable swap that has a notional or principal amount at or above the appropriate minimum block size applicable to such swap. The Commission is also proposing to make minor changes to the term “off-facility swap,” as discussed below in this section.

41
As proposed, paragraph (2) of the “block trade” definition would read: (2) With respect to a swap that is not an off-facility swap, a publicly reportable swap that: (a) Involves a swap that is listed on a swap execution facility or designated contract market; (b) Is executed on the trading system or platform, that is not an order book as defined in § 37.3(a)(3), of a swap execution facility or occurs away from a swap execution facility's or designated contract market's trading system or platform and is executed pursuant to the swap execution facility's or designated contract market's rules and procedures; (c) Has a notional or principal amount at or above the appropriate minimum block size applicable to such swap; and (d) Is reported subject to the rules and procedures of the swap execution facility or designated contract market and the rules described in this part, including the appropriate time delay requirements set forth in § 43.5.

42

See also
n. 38,
supra
(noting the Commission's belief that the 2020 SEF NPRM would promote the statutory goal of promoting trading on SEFs and help to facilitate the pre-execution credit screening by SEFs and FCMs for swap block trades intended to be cleared).

The Commission is proposing to amend the definition of “embedded option” in § 43.2 by removing the reference to “confirmation” at the end of the current definition.
43

As proposed, “embedded option” would mean any right, but not an obligation, provided to one party of a swap by the other party to the swap that provides the party holding the option with the ability to change any one or more of the economic terms of the swap. As discussed below in section II.B.3., the Commission is proposing to remove references to confirmations in part 43.

43
Embedded option is currently defined as any right, but not an obligation, provided to one party of a swap by the other party to the swap that provides the party holding the option with the ability to change any one or more of the economic terms of the swap as those terms previously were established at confirmation (or were in effect on the start date). 17 CFR 43.2.

The Commission is proposing to amend the definition of “execution” in § 43.2 by replacing the reference to execution occurring “orally, in writing, electronically, or otherwise” with “by any method” to shorten the definition without substantively altering it.
44

In addition, the Commission is proposing to remove the phrase that execution occurs simultaneous with or immediately following the affirmation of the swap.
45

As proposed, “execution” would mean an agreement by the parties, by any method, to the terms of a swap that legally binds the parties to such swap terms under applicable law.

44
Execution is currently defined as an agreement by the parties (whether orally, in writing, electronically, or otherwise) to the terms of a swap that legally binds the parties to such swap terms under applicable law. Execution occurs simultaneous with or immediately following the affirmation of the swap. 17 CFR 43.2.

45
As explained in the following section II.B.3., the Commission is proposing to remove references to “affirmation” in § 43.2 because affirmation is not currently used in any of the part 43 regulations.

The Commission is proposing to amend the definition of “off-facility swap” in § 43.2 by removing the reference to “publicly reportable” and “registered.”
46

The Commission is proposing to remove the requirement that the swap be publicly reportable because determining whether a swap transaction is an off-facility swap depends only on where a swap was executed; whether it is also a PRST is

irrelevant. The Commission is proposing to remove the reference to “registered” for the reasons discussed below in section II.C.1.a.

46
Off-facility swap is currently defined as any PRST that is not executed on or pursuant to the rules of a registered swap execution facility or designated contract market. 17 CFR 43.2.

The Commission is proposing to amend the definition of “public dissemination and publicly disseminate” in § 43.2. Currently, § 43.2 defines “public dissemination and publicly disseminate” as to publish and make available STAPD in a non-discriminatory manner, through the internet or other electronic data feed that is widely published and in machine-readable electronic format. Separately, current § 43.3(d)(1) requires that SDRs “publicly disseminate” STAPD in a consistent, usable, and machine-readable electronic format that allows the data to be downloaded, saved, and analyzed.

The Commission is concerned that the definition of “public dissemination and publicly disseminate” currently varies enough from § 43.3(d)(1) to create ambiguity for SDRs as to the format they must use in publicly disseminating STAPD. For instance, the definition of “publicly disseminate” requires that access be non-discriminatory, but the requirement for SDRs to “publicly disseminate” STAPD in § 43.3(d)(1) does not explicitly require that access be non-discriminatory.

Therefore, the Commission is proposing to re-locate the qualification in current § 43.3(d)(1) that SDRs publicly disseminate STAPD in a consistent, usable, and machine-readable electronic format that allows the data to be downloaded, saved, and analyzed to the definition of “public dissemination and publicly disseminate” in § 43.2.
47

As revised, the definition of “public dissemination and publicly disseminate” would mean to make freely available and readily accessible to the public [STAPD] in a non-discriminatory manner, through the internet or other electronic data feed that is widely published. Such public dissemination shall be made in a consistent, usable, and machine-readable electronic format that allows the data to be downloaded, saved, and analyzed.
48

47
As discussed below in section II.C.8., the Commission is proposing to remove current § 43.3(d)(1) in conjunction with moving the substance of the requirement to the definition of “publicly disseminate.”

48
The revised definition of “public dissemination and publicly disseminate” is also discussed below in section II.C.7. with respect to the responsibilities of SDRs to make publicly disseminated STAPD available to the public.

The Commission is proposing to amend the definition of “trimmed data set” in § 43.2 by changing the standard deviation used in the calculation of the trimmed data set from four to two for the “other commodity” asset class, and from four to three for all other asset classes.
49

This proposed amended definition is used in a discussion of proposed changes to the § 43.6(c) regulations for determining AMBSs and cap sizes discussed in section II.F.2. below.

49
Trimmed data set is currently defined as a data set that has had extraordinarily large notional transactions removed by transforming the data into a logarithm with a base of 10, computing the mean, and excluding transactions that are beyond four standard deviations above the mean. 17 CFR 43.2.

3. Proposed Removal of Definitions

The Commission is proposing to remove the definition of “Act” from § 43.2 because the Commission preliminarily believes the definition of “Act” is unnecessary in part 43 because the term is defined in § 1.3.

The Commission is proposing to remove the definition of “business day” from § 43.2 because the Commission preliminarily believes that the definition of “business day” is unnecessary in part 43 because it is defined in § 1.3. Further, the Commission is proposing to remove the definition of “business hours” because it believes the definition of “business hours” would no longer be necessary as a result of the Commission's proposal to remove references to “business hours” in the § 43.5 regulations for the timing delays for block trades. Those proposed changes are discussed below in section II.E.

The Commission is proposing to remove from § 43.2 the “confirmation” definition and the following related definitions: “Affirmation” and “confirmation by affirmation.” The Commission believes these definitions are unnecessary in part 43, and have created confusion as the terms are not used in any of the regulations in part 43.

The Commission is proposing to remove from § 43.2 the definition of “executed.” The Commission believes the current definition is vague. In addition, the Commission believes the proposed definition for “execution date,” discussed above in section II.B.1. would provide the specificity that the current “executed” definition lacks.

The Commission is proposing to remove from § 43.2 the definition of “real-time public reporting.” Currently, § 43.2 defines “real-time public reporting” as the reporting of data relating to a swap transaction, including price and volume, ASATP after the time at which the swap transaction has been executed. The CEA currently already defines “real-time public reporting” as to report data relating to a swap transaction, including price and volume, ASATP after the time at which the swap transaction has been executed.”
50

Therefore, to avoid creating confusion, the Commission is proposing to remove the definition in part 43 because it would be redundant.

50
7 U.S.C. 2(a)(13)(A).

The Commission is proposing to remove the definition of “reporting party” because it is proposing to add a definition of “reporting counterparty” to § 43.2 that would be the same as the current definition of “reporting party” in § 43.2, as discussed above in section II.B.1.

The Commission is proposing to remove the following definitions from § 43.2 as a result of proposed changes to §§ 43.5 and 43.6 for block trades and large notional off-facility swaps: “Futures related swap,” “large notional off-facility swap,” “major currencies,” “non-major currencies,” and “super-major currencies.” Those proposed changes are discussed below in sections II.E. and II.F.

The Commission is proposing to remove the following definitions from § 43.2 as a result of proposed changes to simplify the definition of “novation:” “Remaining party,” “transferee,” and “transferor.”

The Commission is proposing to remove the “unique product identifier” (“UPI”) definition from § 43.2. “Unique product identifier” is currently only used in § 43.4(e). The Commission is proposing to delete current § 43.4(e), which is discussed below in section II.D.1. Therefore, the Commission believes the definition of UPI in § 43.2 is no longer necessary.

The Commission is proposing to remove the definition of “widely published” from § 43.2. “Widely published” means to publish and make available through electronic means in a manner that is freely available and readily accessible to the public. “Widely published” is currently referenced in the definition for “public dissemination and publicly disseminate” as the standard by which SDRs must publish data.
51

The Commission believes that the term “widely published” has a clear meaning and that the definition therefore is unnecessary and may cause confusion.

51
The term “widely published” is also used in current § 43.6(g)(4) for currency conversions.

Request for Comment

The Commission requests comment on all aspects of the proposed changes to § 43.2. The Commission requests specific comment on the following:

(1) Does the Commission's proposed definition of “execution date” present problems for SEFs, DCMs, SDRs, or reporting counterparties? Should the Commission instead adopt a definition that aligns with other regulations, including, for instance, the definition of “day of execution” in § 23.501(a)(5)(i)?
52

52
For the purposes of § 23.501, “day of execution” means the calendar day of the party to the swap transaction that ends latest, provided that if a swap transaction is—(a) entered into after 4:00 p.m. in the place of a party; or (b) entered into on a day that is not a business day in the place of a party, then such swap transaction shall be deemed to have been entered into by that party on the immediately succeeding business day of that party, and the day of execution shall be determined with reference to such business day. 17 CFR 23.501(a)(5)(i). For the purposes of § 23.501, “business day” means any day other than a Saturday, Sunday, or legal holiday. 17 CFR 23.501(a)(5)(ii).

C. § 43.3—Method and Timing for Real-Time Public Reporting

1. § 43.3(a)(1)-(3)—Method and Timing for Reporting Off-Facility Swaps and Swaps Executed on or Pursuant to the Rules of a SEF or a DCM

a. § 43.3(a)(1)—General Rule

The Commission is proposing a number of clarifying and substantive changes to § 43.3(a)(1). As background, § 43.3(a)(1) currently: (i) Requires reporting parties to report PRSTs to SDRs ASATP after execution; and (ii) states that for purposes of part 43, a registered SDR includes any SDR provisionally registered with the Commission pursuant to part 49 of this chapter.

The Commission proposes to make a non-substantive amendment to § 43.3(a)(1) by changing the reference to the person required to report a PRST to an SDR ASATP after execution. The current term “reporting party” is defined in § 43.2 as the party to a swap with the duty to report a PRST in accordance with this part and section 2(a)(13)(F) of the Act. The Commission proposes to replace the reference to the catchall term “reporting party” with more specific references to the persons that, depending on the circumstances, have the reporting obligation for a PRST, namely: A reporting counterparty; a SEF; or a DCM.
53

The Commission is also proposing to slightly reword § 43.3(a)(1) for brevity and to add a cross-reference to proposed §§ 43.3(a)(2)-(6), which address matters such as who must report PRSTs and the timing thereof. Proposed §§ 43.3(a)(2)-(6) would provide additional detail about how (and, in the case of proposed § 43.3(a)(6), whether) the ASATP requirement would apply to real-time public reporting of certain swap transactions and by certain reporting parties. Consequently, the Commission is also proposing to add language to § 43.3(a)(1) stating that it would be “subject to” proposed §§ 43.3(a)(2)-(6) to reflect that, with respect to the transactions and persons covered by proposed §§ 43.3(a)(2)-(6), the provisions thereof apply instead of the general ASATP requirement of proposed § 43.3(a)(1).

53
To limit repetition, this change will not be discussed in each section throughout this release. The circumstances dictating which of these specific persons has the PRST reporting obligation are specified in existing and proposed §§ 43.3(a)(2) and (3). Although the Commission is not proposing to change these circumstances, the Commission is proposing other changes to §§ 43.3(a)(2) and (3), which are discussed below in this section II.C.1.

The Commission also is proposing to add a requirement that the PRST reporting required pursuant to proposed §§ 43.3(a)(1)-(6) be done in the manner set forth in proposed § 43.3(d), discussed below in section II.C.8.

Finally, the Commission proposes to delete the sentence in § 43.3(a)(1) stating that for purposes of this part, a registered SDR includes any SDR provisionally registered with the Commission pursuant to part 49 of this chapter and proposes to replace references to registered SDRs with references to SDRs in proposed § 43.3(a) specifically and throughout part 43.
54

The Commission has also proposed to remove the term “registered swap data repository” from part 49.
55

The term “registered swap data repository” is not needed in part 49 because a definition of “swap data repository” already exists in § 1.3,
56

and the definition is identical to the definition contained in section 1a(48) of the CEA.
57

Because the definitions in § 43.2 have the meanings assigned to them in § 1.3 unless the context otherwise requires, the definition of “swap data repository” already applies to part 43, and would continue to apply to part 43, including proposed § 43.3(a), thus removing the need for a separate defined term for “registered swap data repository.” Furthermore, the word “registered” in the term “registered swap data repository” creates unnecessary confusion as to whether part 43 applies to entities that are in the process of registering as SDRs or are provisionally registered pursuant to § 49.3(b); part 43 applies to SDRs whether they are registered or provisionally registered. The Commission emphasizes that removing the defined term “registered swap data repository” is a technical amendment that does not in any way modify the requirements applicable to current or future SDRs.

54
To limit repetition, this change will not be discussed in each section throughout this release.

55

See
Certain Swap Data Repository and Data Reporting Requirements, 84 FR 21044, 21101.

56

See
17 CFR 1.3 (definition of “swap data repository”) (This term means any person that collects and maintains information or records with respect to transactions or positions in, or the terms and conditions of, swaps entered into by third parties for the purpose of providing a centralized recordkeeping facility for swaps).

57
7 U.S.C. 1a(48) (The term `SDR' means any person that collects and maintains information or records with respect to transactions or positions in, or the terms and conditions of, swaps entered into by third parties for the purpose of providing a centralized recordkeeping facility for swaps).

Therefore, revised § 43.3(a)(1) would require reporting counterparties, SEFs, or DCMs to report any PRST to an SDR ASATP after execution subject to § 43.3(a)(2)-(6) and in the manner set forth in § 43.3(d).

b. § 43.3(a)(2)—Swaps Executed on or Pursuant to the Rules of a SEF or a DCM

The Commission is proposing several amendments to § 43.3(a)(2). As background, current § 43.3(a)(2) states that a party to a PRST can satisfy its part 43 real-time public reporting obligations by executing PRSTs on or pursuant to the rules of a SEF or DCM.

The Commission is proposing to replace the language in § 43.3(a)(2) with the current requirement in § 43.3(b)(1). Current § 43.3(b)(1) states that SEFs and DCMs satisfy their real-time public reporting obligations by transmitting STAPD to SDRs ASATP after the PRST was executed on or pursuant to the rules of the trading platform or facility. Revised § 43.3(a)(2) would therefore state that that SEFs or DCMs must report PRSTs executed on or pursuant to the rules of a SEF or DCM ASATP after execution. As a result, § 43.3(a)(2) would contain SEFs' and DCMs' part 43 reporting obligations instead of § 43.3(b)(1). In revising § 43.3(a)(2), the Commission would also replace the reference to a “registered [SEF]” with a reference to SEFs because, similar to the reasoning discussed above in section II.C.1.a. with respect to “registered” SDRs, the term “registered” is unnecessary and could create confusion.
58

The Commission considers the above amendments to be non-substantive.

58
The Commission is proposing this change elsewhere in part 43. To limit repetition in this release, the change will not be discussed repeatedly in this preamble.

c. § 43.3(a)(3)—Off-Facility Swaps

The Commission proposes to amend § 43.3(a)(3) in two respects. As background, current § 43.3(a)(3) requires reporting parties to report all off-facility swaps to an SDR for the appropriate

asset class in accordance with the rules set forth in part 43 ASATP following execution, and sets out the reporting hierarchy for these PRSTs.
59

59
The Commission is not proposing substantive amendments to the reporting hierarchy.

The Commission proposes to clarify in §§ 43.3(a)(3)(iii)-(v) that, in situations where the parties to an off-facility PRST must designate which of them is the reporting counterparty, they must make such designation prior to the execution of the off-facility PRST so that there is no delay in reporting the off-facility PRST pursuant to part 43, as there could be if the parties do not make such designation until after the off-facility PRST is executed or cannot agree on such designation.

Because the Commission is proposing to add part 43 reporting requirements specific to PPSs, clearing swaps, and mirror swaps, respectively, in proposed new §§ 43.3(a)(4)-(6), the Commission proposes to introduce proposed § 43.3(a)(3) with except as otherwise provided in paragraphs (a)(4)-(6) of this section. The proposed part 43 reporting requirements applicable to PPSs, clearing swaps and mirror swaps are discussed below in sections II.C.2.-4., respectively.

2. § 43.3(a)(4)—Post-Priced Swaps

The Commission is proposing new § 43.3(a)(4) to address issues market participants face in reporting PPSs. As background, the purpose of CEA § 2(a)(13), the primary source of the Commission's authority to promulgate real-time public reporting rules, is to authorize the Commission to make [STAPD] available to the public in such form and
at such times as the Commission determines appropriate to enhance price discovery.
60

Congress also directed the Commission to include provisions in its real-time reporting rules that take into account whether the public disclosure will materially reduce market liquidity.
61

Swap counterparties must report STAPD to the appropriate registered entity
in a timely manner as may be prescribed by the Commission.
62

The Commission, therefore, has some discretion in determining when STAPD should be reported and publicly disseminated.

60
7 U.S.C. 2(a)(13)(B) (emphasis added).

61
7 U.S.C. 2(a)(13)(E)(iv).

62
7 U.S.C. 2(a)(13)(F) (emphasis added).

Regulation 43.3(a) generally requires the reporting party for each PRST to report it to an SDR ASATP after execution of the transaction. Market participants have raised concerns with complying with the ASATP requirement for a category of swaps with respect to which one or more terms are unknown at the time the swap is executed. One Roadmap commenter suggested that such swaps should only be reported when all of the final primary economic terms of the transaction are determined, rather than at execution.
63

63
Letter from The International Swaps and Derivatives Association (“ISDA”) and The Securities Industry and Financial Markets Association (“SIFMA”) (“Joint ISDA-SIFMA Letter”) (Aug. 21, 2017) at 10.

The Commission understands that these swaps are generally characterized by the price, size and/or other terms of the transaction being contingent upon the outcome of SD hedging, market results during an observation period (a point in time or a longer period), or the occurrence of certain events—such as the price for a swap underlier being determined at the close of trading on a trading platform—that occur after an SD accepts a client request (collectively, “Variable Terms”). Although the parties may know the non-Variable Terms at the time of execution,
64

the Variable Terms generally are not known until the subsequent dealer hedging or other market activity has taken place because the Variable Terms are, wholly or partly, contingent on the occurrence of such triggers and determined, wholly or in part, by some aspect of such contingencies.

64
“Execution” is defined in § 43.2, in relevant part, as an agreement by the parties to the terms of a swap that legally binds the parties to such swap terms under applicable law.

The Commission understands that some market participants do not report swaps with Variable Terms to SDRs until hours, or even days, after the execution thereof.
65

Reporting parties have contended that they report these swaps to SDRs only after the Variable Terms are set because (i) they want to foreclose the possibility of market participants “front running” reporting parties' customers'/counterparties' swaps; and (ii) neither reporting parties nor SDRs have the technological processes in place to support reporting prior to the determination of a numerical price, volume or other Variable Terms.

65
However, this approach is not followed universally: Other market participants report PPSs differently. For example, some market participants report to an SDR PPSs with a price of zero at the time of execution and amend the price reported to the SDR once the price is known.

Currently, PPSs and other swaps with Variable Terms not determined at execution (“Variable Terms Swaps”) account for a significant but unknown percentage of swaps that are not reported to SDRs in a timely manner.
66

However, through Roadmap outreach, the Commission has learned that these PPSs and other Variable Terms Swaps may constitute a large percentage of certain market participants' equity derivatives business subject to CFTC jurisdiction.
67

The Commission preliminarily believes that the reporting of PPSs and other Variable Terms Swaps is not consistent across SDs, with some reporting swaps shortly after execution and others not reporting until the Variable Terms are known.

66
The percentage is unknown because there is no SDR data field to indicate that a swap is a PPS. Although, as noted above, some reporting parties may report PPSs with zero or blank prices or other Variable Terms and later amend such reports once the Variable Terms are known, there are other reasons a zero price may be reported or that blanks may be reported for the Variable Terms, so there currently is no definitive method of quantifying the scope of the PPS reporting issue.

67
One market participant estimated that PPSs are a bigger percentage of equity swaps than of any other asset class and constitute approximately 80-90% of CFTC-reportable equity swaps.

The Commission also preliminarily believes that the reporting of PPSs ASATP after execution but before the price is determined does not serve a significant price discovery function and that the omission of a price, or the use of a placeholder price, by reporting parties who report PPSs before the price is determined may confuse market participants or constitute unhelpful “noise” on the public tape. The Commission understands that requiring public reporting of PPSs before their prices are determined could allow market participants to transact in swaps ahead of any necessary hedging by SDs, potentially disadvantaging the SDs' counterparties driving the PPS transactions by increasing the cost of the hedges. This could, in turn, lead such counterparties to forego the use of swaps to achieve their investment or other goals, thereby reducing swap market liquidity.

However, the Commission seeks to balance permitting the delayed reporting of swaps that appear to lack a significant price discovery benefit with encouraging or permitting indefinitely delayed reporting of PPSs. The latter possibility could encourage swap counterparties to structure some of their swaps as PPSs to take advantage of the longer proposed reporting deadline for PPSs.
68

68
However, to the extent the Commission's proposal raises concerns in this regard, § 23.402(a)(1) does require SDs to have written policies and procedures reasonably designed to prevent a swap dealer from evading or participating in or facilitating an evasion of any provision of the CEA or any regulation promulgated thereunder.

In light of the foregoing, the Commission is proposing a longer deadline for reporting STAPD for certain PPSs than for PRSTs generally. To effectuate such longer deadline, the

Commission proposes to add new § 43.3(a)(4) to its regulations. Proposed § 43.3(a)(4)(i) would permit the reporting counterparty to delay reporting a PPS to an SDR until the earlier of the price being determined and 11:59:59 p.m. eastern time on the execution date.
69

Proposed § 43.3(a)(4)(i) would further provide that, if the price of a PRST that is a PPS is not determined by 11:59:59 p.m. eastern time on the execution date, the reporting counterparty shall report to an SDR by 11:59:59 p.m. eastern time on the execution date all STAPD for such PPS other than the price and any other then-undetermined Variable Terms and shall report each such item of previously undetermined STAPD ASATP after such item is determined.
70

Proposed § 43.3(a)(4)(ii) would provide that the more lenient proposed reporting deadline in § 43.3(a)(4)(i) would not apply to PRSTs with respect to which the price
is
known at execution but one or more other Variable Terms are not yet known at the time of execution.
71

69
By “11:59:59 p.m. eastern time on the execution date,” the Commission means 11:59:59 p.m. in the eastern time zone of the United States on the date the relevant swap is executed, irrespective of where either counterparty's headquarters or personnel or office involved in executing the swap are located and irrespective of any other factors. This could result in the reporting counterparty having more or less time to report a swap depending on how close it is to 11:59:59 p.m. eastern time at execution in any time zones relevant to the reporting counterparty reporting the STAPD.

70
While the proposed definition of “post-priced swap” would be a swap for which the price has not been determined at the time of execution, such a swap with
additional
terms that are also not determined at the time of execution would also fall within the proposed “post-priced swap” definition. Consequently, if a PPS also has non-price terms that are not determined at the time of execution, a value for such non-price terms must be reported ASATP after it is determined. If a placeholder value that satisfies the allowable values parameters for an unknown Variable Term was previously reported for such undetermined STAPD, then such STAPD must be corrected ASATP after it is determined.

71
The Commission notes that when the price is known at execution but one or more Variable Terms are not yet known, the reporting counterparty must report the swap ASATP and then amend the swap later to report the Variable Terms.

3. § 43.3(a)(5)—Clearing Swaps

The Commission proposes to amend § 43.3(a) to add DCOs to the reporting counterparty hierarchy for clearing swaps that are PRSTs. As background, in 2016, the Commission adopted rules that, among other things, added DCOs to the hierarchy for determining the reporting counterparty for clearing swaps in § 45.8.
72

Although the Cleared Swap Final Rule added DCOs to the reporting counterparty hierarchy in § 45.8, it did not add DCOs to the reporting hierarchy in part 43.

72
Amendments to Swap Data Recordkeeping and Reporting Requirements for Cleared Swaps, 81 FR 41736 (June 27, 2016) (“Cleared Swap Final Rule”). Specifically, § 45.8(i) now states, in relevant part, if the swap is a clearing swap, the DCO that is a counterparty to such swap shall be the reporting counterparty and shall fulfill all reporting counterparty obligations for such swap.

Most clearing swaps are the result of an original swap being accepted for clearing by a DCO. In these cases, there is no part 43 real-time public reporting for the clearing swaps. For most clearing swaps, there is no conflict between the part 43 and part 45 reporting hierarchies.

However, there are limited circumstances in which DCOs create clearing swaps for which there is no original swap, and the clearing swaps may meet the definition of a PRST in part 43, while also being required to be reported pursuant to part 45. In these circumstances, the part 43 and part 45 reporting hierarchies may conflict. For example, if a DCO enters into PRSTs to manage the default of a clearing member, the DCO would be the reporting counterparty under § 45.8(i) but not under current § 43.3(a)(3).

To avoid this conflict, the Commission proposes to add DCOs to the hierarchy in § 43.3 for clearing swaps. Proposed § 43.3(a)(5) would state that notwithstanding the provisions of paragraphs (a)(1)-(3) of this section, if a clearing swap, as defined in § 45.1 of this chapter, is a PRST, the DCO that is a party to such swap shall be the reporting counterparty and shall fulfill all reporting counterparty obligations for such swap as soon as technologically practicable after execution.

4. § 43.3(a)(6)—Mirror Swaps

As explained above, the CEA authorizes the Commission to make STAPD available to the public in such form and
at such times as the Commission determines appropriate to enhance price discovery.
73

In 2017, DMO announced its intention to review the reporting regulations to address ongoing issues of reporting prime brokerage transactions.
74

As a result of this review, and as discussed below in this section, the Commission is proposing new regulations in § 43.3(a)(6) to help ensure that the STAPD associated with mirror swaps, which some market participants view as duplicative, non-price-forming data, does not distort the volume of trading activity or unnecessarily impede price discovery for market participants and others who rely on the real-time public tape for those purposes. The Commission notes that the swap data associated with all mirror swaps would be required to be reported to SDRs pursuant to part 45 so the Commission can fulfill its risk monitoring, compliance, and market manipulation responsibilities.

73
7 U.S.C. 2(a)(13)(B) (emphasis added).

74
Roadmap at 11. DMO has previously provided no-action relief from the real-time public reporting requirements for swaps executed pursuant to prime brokerage arrangements in response to concerns that reporting both legs of prime brokerage transactions would incorrectly suggest the presence of more trading activity and price discovery in the market than actually exists.
See
CFTC Letter No. 12-53, Time-Limited No-Action Relief from (i) Parts 43 and 45 Reporting for Prime Brokerage Transactions, and (ii) Reporting Unique Swap Identifiers in Related Trades under Part 45 by Prime Brokers (Dec. 17, 2012),
available at https://www.cftc.gov/sites/default/files/idc/groups/public/@lrlettergeneral/documents/letter/12-53.pdf.
The Financial Markets Lawyers Group (“FMLG”) and the International Swaps and Derivatives Association (“ISDA”), which requested the relief that DMO provided in CFTC Letter No 12-53, also sought and received relief from certain reporting requirements of part 45 of the Commission's rules, but this proposal discusses only the part 43 reporting aspects of the relief.

The Commission understands that prime brokerage swaps begin with a counterparty opening an account with a prime broker (“PB”) that grants limited agency powers to the counterparty. These limited powers enable the counterparty, as an agent for the PB, to enter into swaps with approved executing dealers (“ED”), subject to specific limits and parameters, such as credit limits and collateral requirements. The PB also enters into “give-up” arrangements with approved EDs in which the EDs agree to negotiate swaps with the counterparty, acting as an agent for the PB, within the specified parameters and to face the PB as counterparty for the resulting ED-PB swap (“ED-PB Swap”).

The Commission understands that in a prime brokerage swap, the counterparty seeks bids for the desired swap from one or more of the approved EDs, within the parameters established by the PB. Once the counterparty and ED agree on the terms, the Commission believes that both the counterparty and ED provide a notice of the terms to the PB, and those terms constitute the ED-PB Swap, which the PB must accept if: The swap is with an approved ED; the counterparty and ED have committed to the material terms; and the terms are within the parameters established by the PB. Once the ED-PB Swap is accepted by the PB, the PB enters into a mirror swap (“Mirror Swap”) with the counterparty with identical economic terms and pricing, subject to adjustment, as a result of the prime brokerage servicing fee.

In 2012, DMO granted no-action relief, subject to conditions described below, where: (i) An ED reports an ED-

PB Swap under part 43, including any required post-trade event reporting; and (ii) the related Mirror Swap is not reported for part 43 purposes by the ED, PB or any other party, unless there is a modification to the economic terms of the ED-PB swap.
75

The relief was conditioned on: The allocation of part 43 reporting responsibilities being agreed upon by the parties; the ED and the PB each being a registered SD; and the ED-PB Swap and Mirror Swap having identical economic terms and pricing, subject to adjustment in the case of the Mirror Swap as a result of a prime brokerage servicing fee.
76

75

See id.
at 5.

76

Id.

CFTC Letter No. 12-53 expired on June 30, 2013, but the Commission believes that concerns about the impact on price discovery of mirror swap STAPD on the public tape are still concerns today. To address these concerns, the Commission is proposing new § 43.3(a)(6), and related definitions in § 43.2(a). The Commission believes the proposed regulations would address issues raised by swaps executed pursuant to prime brokerage arrangements and related mirror swaps.
77

77
The Commission notes that the Securities and Exchange Commission (“SEC”) has adopted a different approach with respect to security-based swaps, with the result that mirror security-based swaps would be PRSTs and thus reported.
See
Regulation SBSR—Reporting and Dissemination of Security-Based Swap Information, 81 FR 53546, at 53583-86 (Aug. 12, 2016) (declining to exempt from public dissemination certain prime brokerage SBSs discussed therein).

a. Proposed New Definitions

The Commission is proposing to add the term “prime brokerage agency arrangement” to § 43.2(a). “Prime brokerage agency arrangement” would mean an arrangement pursuant to which a prime broker authorizes one of its clients, acting as agent for such prime broker, to cause the execution of a trigger swap. The Commission proposes to use the term “prime brokerage agency arrangement” in the new proposed definitions of “prime brokerage agent” and “trigger swap” in § 43.2(a) to establish the parameters of the proposed new definition of a “mirror swap,” also in § 43.2(a), which would not be reportable under part 43 if it satisfied the terms of proposed § 43.3(a)(6)(i). The Commission's goal in proposing the “prime brokerage agency arrangement” definition and using it in other definitions in § 43.2(a) is to help ensure that the scope of unreported mirror swaps is limited to swaps that are, among other things, integrally related to trigger swaps and their related pricing events.

The Commission is proposing to add the term “prime brokerage agent” to § 43.2(a) as a new definition that would mean a client of a prime broker who causes the execution of a trigger swap acting pursuant to a prime brokerage agency arrangement.

The Commission is also proposing to add the term “prime broker” to § 43.2(a). “Prime broker” would mean with respect to a mirror swap and its related trigger swap, a swap dealer acting in the capacity of a prime broker with respect to such swaps. The Commission proposes to use the term “prime broker” in the proposed definitions of “prime brokerage agency arrangement,” “prime brokerage agent,” and “trigger swap” in § 43.2(a), and in proposed § 43.3(a)(6), to establish the parameters of when a “mirror swap” would not be reportable under part 43 if it satisfied the terms of proposed § 43.3(a)(6)(i).

The Commission is proposing to add the term “trigger swap” to § 43.2(a) as a new definition that would mean a swap: (1) That is executed pursuant to one or more prime brokerage agency arrangements;
78

(2) to which a prime broker is a counterparty or both counterparties are prime brokers; (3) that serves as the contingency for, or triggers, the execution of one or more corresponding mirror swaps; and (4) that is a PRST that is required to be reported to a swap data repository pursuant to this part and part 45 of this chapter. The Commission proposes to use the term “trigger swap” as an element of a “mirror swap,” which the Commission proposes to make not reportable.
79

78
The Commission understands that some pricing events (as proposed to be defined in § 43.2(a) and as discussed in the paragraph following the paragraph in the body of the preamble with which this footnote is associated) that result in trigger swaps and related mirror swaps (
e.g.,
in the context of a reverse give-up, which is discussed below in section II.C.4.b.) are negotiated by persons that are acting pursuant to a prime brokerage agency arrangement with more than one prime broker. The Commission understands that some pricing events that lead to related trigger swaps and related mirror swaps (
e.g.,
in the context of a double give-up, which is discussed below in section II.C.4.b.) are negotiated by two persons that are each acting pursuant to a prime brokerage agency arrangement with its respective prime broker.

79

See
proposed § 43.6(a)(6)(i), discussed below in section II.C.4.b.

The Commission is proposing to add the term “pricing event” to § 43.2(a) as a new definition that would mean the completion of the negotiation of the material economic terms and pricing of a trigger swap. The Commission is proposing to use the term “pricing event” in proposed § 43.3(a)(6)(i) to make it clear when execution of a trigger swap, which would be required to be reported under proposed § 43.3(a)(6)(iv) (discussed below in section II.C.4.b.), occurs.

The Commission is proposing to add the term “mirror swap” to § 43.2(a) to mean a swap: (1) To which a prime broker is a counterparty or both counterparties are prime brokers; (2) that is executed contemporaneously with a corresponding trigger swap; (3) that has identical terms and pricing as the contemporaneously executed trigger swap (except that a mirror swap, but not the corresponding trigger swap, may include any associated prime brokerage service fees agreed to by the parties and except as provided in the final sentence of this “mirror swap” definition); (4) with respect to which the sole price forming event is the occurrence of the contemporaneously executed trigger swap; and (5) the execution of which is contingent on, or is triggered by, the execution of the contemporaneously executed trigger swap. The notional amount of a mirror swap may differ from the notional amount of the corresponding trigger swap, including, but not limited to, in the case of a mirror swap that is part of a partial reverse give-up;
80

provided, however,
that in such cases, (i) the aggregate notional amount of all such mirror swaps to which the prime broker that is a counterparty to the trigger swap is also a counterparty shall be equal to the notional amount of the corresponding trigger swap and (ii) the market risk and contractual cash flows of all such mirror swaps to which a prime broker that is not a counterparty to the corresponding trigger swap is a party will offset each other (and the aggregate notional amount of all such mirror swaps on one side of the market and with cash flows in one direction shall be equal to the aggregate notional amount of all such mirror swaps on the other side of the market and with cash flows in the opposite direction), resulting in each prime broker having a flat market risk position.

80
A “partial reverse give-up” is described below in section II.C.4.b.

The Commission is proposing to define the term “mirror swap” to delineate a group of swaps that do not have to be reported under part 43 if the related conditions set forth in proposed § 43.3(a)(6) are satisfied. The Commission preliminarily believes that because the terms and pricing of a trigger swap and its related mirror swaps are the same, part 43 reporting of both a trigger swap and the related

mirror swaps could falsely indicate the occurrence of two or more (depending on how many mirror swaps there are for a given trigger swap) pricing events and incorrectly suggest the presence of more trading activity and price discovery in the market than actually exist.

The Commission preliminarily believes the STAPD of trigger swaps should be reported pursuant to part 43 ASATP after the occurrence of the related pricing event for the following reasons: (1) All the terms of a trigger swap are determined at the time of its related pricing event, so execution of the trigger swap occurs at that time (as stated expressly in proposed § 43.3(a)(6)(i)), so the ASATP clock should “start ticking” at that time; (2) any delay in the mirror swap counterparties learning of the related trigger swap terms should not delay part 43 reporting of the trigger swap given that the mirror swaps would not be reported under proposed § 43.3(a)(6);
81

(3) one or both of the parties to a pricing event often are the reporting counterparties in other swaps so have the infrastructure in place to report the related trigger swap ASATP after the execution of the pricing event; and (4) to the extent that (3) is untrue, one or more of the prime brokers involved in the related mirror swaps (all of whom currently are SDs, the Commission understands) can amend the terms of their prime brokerage arrangements (as proposed to be defined in § 43.2) to require the parties thereto who are also parties to pricing events to ensure that their prime brokers learn of the terms of the pricing events in a manner that is sufficiently timely to permit their prime brokers to report trigger swaps ASATP after the execution of the related pricing events.

81
To the extent a trigger swap is outside the permitted scope of a prime brokerage arrangement, as proposed to be defined in § 43.2(a), the relevant party can cancel it. The Commission understands that this happens today but preliminarily believes that the potential for a trigger swap to be cancelled as a result of its being outside the scope of the relevant prime brokerage arrangement, as proposed to be defined in § 43.2(a), should not delay reporting STAPD.

The Commission is proposing to use the word “contemporaneously” in clause (2) of the “mirror swap” definition (
i.e.,
a swap “that is executed contemporaneously with a corresponding trigger swap”) rather than “simultaneously” to reflect the fact that it may take some time for potential parties to a mirror swap to receive the terms of such mirror swap from the parties to the related trigger swap and to verify that the terms of the potential mirror swap are within the parameters established by the governing prime brokerage arrangement, as proposed to be defined in § 43.2(a). However, the Commission expects the parties to a trigger swap to promptly convey those terms to the relevant prime broker(s) that would be a party or parties to related mirror swaps; any delay in conveying such terms should not be used as an opportunity to find additional counterparties to take part in unreported mirror swaps.
82

The Commission may construe any purported mirror swaps resulting from such activity as not executed contemporaneously with the related trigger swap, and thus not within the scope of the proposed mirror swap definition or, as a result, proposed § 43.3(a)(6), and therefore reportable under §§ 43.3(a)(1)-(3), as applicable, depending on the facts and circumstances.

82
This could include, but would not be limited to, a potential party to a mirror swap receiving the terms of a related trigger swap from one party to the trigger swap and seeking additional counterparties to a mirror swap while waiting to receive the matching terms of the trigger swap from the other party thereto.

The Commission is proposing the language regarding associated prime brokerage service fees in clause (3) of the proposed “mirror swap” definition (
i.e.,
as is relevant here, a swap that has identical terms and pricing as the contemporaneously executed trigger swap (except that a mirror swap, but not the corresponding trigger swap, may include any associated prime brokerage service fees agreed to by the parties)) to reflect that a mirror swap may contain fees that a prime broker that is a counterparty to a mirror swap may charge its counterparty to that mirror swap as a fee for serving as a prime broker in such swap. The Commission understands that prime brokers typically charge their clients a service fee for the swap intermediation service that prime brokers provide (
i.e.,
serving as swap counterparties in lieu of counterparties that prime brokers' clients would prefer not to face as swap counterparties for credit reasons). The prime broker service fee is meant to reflect prime brokers' credit intermediation costs as well as prime brokers' back-office and middle-office administrative services costs related to trigger swaps and mirror swaps (
e.g.,
booking, reconciling, settling and maintaining such trigger swaps and mirror swaps). The prime broker service fee is typically agreed upon by a prime broker and its client before a pricing event. To be considered prime brokerage service fees for purposes of clause (3) of the proposed “mirror swap” definition, such fees must be limited to the foregoing purpose and cannot contain any other elements.
83

83
For example, the Commission would not consider a purported prime brokerage service fee providing the prime broker or its counterparty exposure to a commodity to be a prime brokerage service fee within the meaning of clause (3) of the proposed “mirror swap” definition, as a result of which the related “mirror swap” would not be a mirror swap, and thus would not be within the scope of proposed § 43.3(a)(6) (discussed below in section II.C.4.b.), and therefore would be reportable under §§ 43.3(a)(1)-(3), as applicable, depending on the facts and circumstances.

b. Other Proposed Regulations

Proposed new § 43.3(a)(6)(i) would provide that a mirror swap, which the Commission is proposing to define in § 43.2(a), as discussed above in section II.B.1., is not a PRST. Proposed new § 43.3(a)(6)(i) would also state that, for purposes of determining when execution occurs under §§ 43.3(a)(1)-(3), execution of a trigger swap shall be deemed to occur at the time of the pricing event for such trigger swap.

Proposed new § 43.3(a)(6)(ii) would provide parameters for determining which counterparty is the reporting counterparty for a given trigger swap in situations where it is unclear, with respect to a given set of swaps, which are mirror swaps and which is the related trigger swap. More specifically, proposed new § 43.3(a)(6)(ii) would state that if, with respect to a given set of swaps, it is unclear which are mirror swaps and which is the related trigger swap (including, but not limited to, situations where there is more than one prime broker counterparty within such set of swaps and situations where the pricing event for each set of swaps occurs between prime brokerage agents of a common prime broker), the PBs would be required to determine which swap is the trigger swap and which are mirror swaps. Proposed new § 43.3(a)(6)(ii) would also specify that, with respect to the trigger swap to which a PB is a party, the counterparty that falls within the highest level of the reporting counterparty determination hierarchy set forth in § 43.3(a)(3) is the reporting counterparty; proposed new § 43.3(a)(6)(ii) would further specify that, if both counterparties fall within the same level of that hierarchy, they must determine who is the reporting counterparty for such trigger swap pursuant to §§ 43.3(a)(3)(iii), (iv), or (v), as applicable. Proposed new § 43.3(a)(6)(ii) would add that, notwithstanding the foregoing, if the counterparty to a trigger swap that is not a PB is an SD, then that counterparty will be the reporting counterparty for the trigger swap.

Proposed new § 43.3(a)(6)(iii) would provide that, if, with respect to a given set of swaps, it is clear which are mirror swaps and which is the related trigger swap, the reporting counterparty for the trigger swap shall be determined pursuant to § 43.3(a)(3).

Proposed new § 43.3(a)(6)(iv) would provide that trigger swaps described in proposed § 43.3(a)(6)(ii) (situations in which it is unclear which of a set of swaps are mirror swaps and which is the related trigger swap) and (iii) (situations in which it is clear which of a set of swaps are mirror swaps and which is the related trigger swap) shall be reported pursuant to the requirements set out in §§ 43.3(a)(2) or (a)(3), as applicable, except that the provisions of proposed § 43.3(a)(6)(ii), rather than of proposed § 43.3(a)(3), shall govern the determination of the reporting counterparty for purposes of the trigger swaps described in proposed § 43.3(a)(6)(ii).

CFTC Letter No. 12-53 provided relief for what it termed a “Typical Prime Brokerage Transaction” in which an ED that is an SD agrees with its counterparty to the terms of matching swaps entered into between the ED and the counterparty's PB and between the PB and the counterparty. The Commission understands that the scope of proposed § 43.3(a)(6) would expand the scope of CFTC Letter No. 12-53 in that it would encompass both the “typical prime brokerage transactions” covered by CFTC Letter No. 12-53 and at least three other forms of PB transactions: reverse give-up PB swaps; partial reverse give-up PB swaps; and double give-up PB swaps. The Commission understands that other forms of prime brokerage swap transactions also may be covered by proposed § 43.3(a)(6) and does not intend, by describing herein reverse give-up PB swaps, partial reverse give-up PB swaps, and double give-up PB swaps, to limit the scope of proposed § 43.3(a)(6) to such forms of prime brokerage swap transactions.

In a reverse give-up PB swap structure, the executing broker (“EB”)
84

and one or more clients of a PB, or of both PBs involved in the structure,
85

negotiate swap terms forming the basis of a trigger swap entered into between the EB and a PB
86

and related mirror swaps entered into between the PB and one or more other PBs, the other PB(s) and one or more clients and, in some reverse give-up prime brokerage swap structures, the client and the EB-facing PB.
87

In a double give-up prime brokerage swap structure, a client of one PB and a client of a different PB negotiate with each other swap terms forming the basis of a trigger swap entered into between the two PBs
88

and of the related mirror swaps entered into between each of the PBs and its respective client.

84
The Commission understands that EBs are always SDs today, but proposed § 43.3(a)(6) does not require EBs to be SDs. EBs play the same role in the prime brokerage swap transactions discussed in today's proposal that EDs did in CFTC Letter No. 12-53. Thus, other than when it is discussing CFTC Letter No. 12-53, which used the term “ED,” the Commission is using the term EB rather than ED in the preamble to reflect the fact that proposed § 43.3(a)(6) does not require EBs to be SDs.

85
As noted above, the Commission understands that some pricing events (as proposed to be defined in § 43.2(a) and as discussed in the paragraph following the paragraph in the body of the preamble with which this footnote is associated) that result in trigger swaps and related mirror swaps (
e.g.,
in the context of a reverse give-up, which is discussed below in section II.C.4.b.) are negotiated by persons that are acting pursuant to a prime brokerage agency arrangement with more than one prime broker.

86
The EB and the PB client are said to “give up” the swap that otherwise would have been entered into between the EB and the PB client to the EB and PB. That “given up” swap becomes the trigger swap.

87
The mirror swaps between the PBs, pursuant to instructions from a client, are said to be “reverse give-ups” from the EB-facing PB to the other PB(s). If the reverse give-up is for 100% of the notional of the trigger swap, then the PB that is a swap counterparty to the EB in the trigger swap will not also be a swap counterparty to a client in a mirror swap. If the reverse give-up is for less than 100% of the notional of the trigger swap (
i.e.,
a partial reverse give-up), then there will be a mirror swap between: the EB-facing PB and at least one client participating in the partial reverse give-up; the EB-facing PB and each of the other PBs participating in the partial reverse give-up; and each of such other PBs and at least one of the clients participating in the partial reverse give-up.

88
The two clients are said to “give up” to their respective PBs the swap that otherwise would be entered into between the two clients. That “given up” swap becomes the trigger swap.

CFTC Letter No. 12-53 permitted the ED to be the reporting party for the ED-PB Swap, subject to the conditions that the ED and PB allocated reporting responsibility between them and both parties were SDs. Proposed § 43.3(a)(6)(ii) would differ from the reporting structure in CFTC Letter No. 12-53 in that proposed § 43.3(a)(6)(ii) would instead incorporate the reporting counterparty hierarchy of § 43.3(a)(3). The goal of proposed § 43.3(a)(6)(ii) is to have each trigger swap be reported ASATP after its pricing event. The Commission understands that one counterparty to a trigger swap often will have participated in negotiating the related pricing event, so should be well-placed to report the trigger swap pursuant to part 43 in such circumstances, particularly if that counterparty is an SD, given that SDs are experienced with part 43 reporting. If the PB is an SD, but its counterparty is not, the PB would be the reporting counterparty for the trigger swap even though the PB may not learn of the pricing event for some time, although, pursuant to proposed § 43.3(a)(7), discussed below in section II.C.5., it could contract with a third-party service provider (which could include a party to the pricing event (
e.g.,
an EB)) to handle such reporting if it believes reporting such PRST in a timely manner (
i.e.,
ASATP after the pricing event, per proposed § 43.3(a)(6)(i)) would be problematic for it, while remaining fully responsible for such reporting. Similarly, even in circumstances in which neither counterparty to a trigger swap participated in negotiating the related pricing event (
e.g.,
a double give-up prime brokerage swap structure), such counterparties can contract with a third-party service provider to handle such reporting if they believe that reporting such trigger swap in a timely manner (
i.e.,
ASATP after the pricing event, per proposed § 43.3(a)(6)(i)) would be problematic for them, while remaining fully responsible for such reporting.

5. § 43.3(a)(7)—Third-Party Facilitation of Data Reporting

The Commission proposes to add § 43.3(a)(7) to provide for the third-party facilitation of data reporting. As background, in the 2012 RTR NPRM, Real-Time Public Reporting of Swap Transaction Data, 75 FR 76140 (Dec. 7, 2010), the Commission noted that SEFs, DCMs, and SDRs may enter into contractual relationships with third party service providers to facilitate reporting, while remaining responsible for the reporting requirement under part 43.
89

Regulation 45.9 contains a parallel provision for part 45 reporting. Regulation 45.9 provides for third-party facilitation of data reporting, and specifies that registered entities and swap counterparties that contract with third-party service providers remain fully responsible for the reporting requirement under part 45. Proposed § 43.3(a)(7) would codify the Commission's previously-stated position with respect to third party facilitation of part 43 reporting in a manner consistent with § 45.9 and expressly expand it to reporting parties for off-facility swaps. Therefore, proposed § 43.3(a)(7) would state that any person required by part 43 to report STAPD, while remaining fully responsible for reporting as required by part 43, may contract with a third-party service provider to facilitate reporting.

89
Real-Time Public Reporting of Swap Transaction Data, 77 FR 1182, 1201.

6. § 43.3(b)—Public Dissemination of Swap Transaction and Pricing Data

The Commission is proposing several revisions to the rules for SEFs, DCMs, SDs, MSPs, and SDRs in disseminating STAPD. First, as discussed above in section II.C.1.b., the Commission is proposing to move the substance of current § 43.3(b)(1) to revised § 43.3(a)(2).
90

90
Moving current § 43.3(b)(1) to § 43.3(a)(2) would consolidate the requirements for SEFs and DCMs to report STAPD in § 43.3(a)(2).

Second, the Commission is proposing to relocate current § 43.3(b)(2) to § 43.3(b)(1) and revise the regulation. As background, current § 43.3(b)(2) states that registered SDRs shall ensure that STAPD is publicly disseminated ASATP after such data is received from a SEF, DCM, or reporting party, unless such PRST is subject to a time delay described in § 43.5, in which case the PRST shall be publicly disseminated in the manner described in § 43.5.

The Commission is also proposing to replace the language in current § 43.3(b)(2) stating that SDRs shall “ensure” STAPD is publicly disseminated with an SDR shall publicly disseminate STAPD ASATP to clarify that SDRs must disseminate the data, rather than ensure it is done. The Commission believes that this revision should not result in any changes in current practice for SDRs. Finally, the Commission is proposing to replace the two references to “publicly reportable swap transaction” with references to “swap transaction and pricing data” for consistency both within proposed § 43.3(b)(1) and with § 43.5, which is cross-referenced by current § 43.3(b)(2) and would continue to be cross-referenced by proposed § 43.3(b)(1). Therefore, proposed § 43.3(b)(1) would state that an SDR shall publicly disseminate STAPD ASATP after receiving it from a SEF, DCM, or reporting counterparty, unless the STAPD is subject to a time delay described in § 43.5, in which case the SDR must publicly disseminate the STAPD pursuant to § 43.5.

Third, the Commission is proposing to relocate § 43.3(c)(1) to § 43.3(b)(2) in conjunction with the above relocation of § 43.3(b)(2) to § 43.3(b)(1). As background, current § 43.3(c)(1) states that any SDR that accepts and publicly disseminates STAPD in real-time shall comply with part 49 and shall publicly disseminate STAPD in accordance with part 43 ASATP upon receipt of such data, except as otherwise provided in part 43.

The Commission is proposing to locate the regulations for SDRs to follow in disseminating STAPD in § 43.3(b). Because current § 43.3(c)(1) is an SDR obligation regarding the public dissemination of STAPD, the Commission believes it should be located in revised § 43.3(b). The Commission is also proposing to remove the last phrase of § 43.3(c)(1), which states that SDRs must publicly disseminate STAPD in accordance with part 43 ASATP upon receipt of such data, except as otherwise provided in part 43. The Commission believes this language unnecessary given the similar, but more precise, reference to § 43.5 in current § 43.3(b)(2) and in proposed § 43.3(b)(1), discussed above in this section II.C.6.
91

Therefore, proposed § 43.3(b)(2) would state that any SDR that accepts and publicly disseminates STAPD in real-time shall comply with part 49.

91
The reference in § 43.3(c)(1) to “except as otherwise provided in part 43” rather than solely to § 43.5 is unnecessarily broad, given that § 43.5 currently is the only regulation in part 43 containing a delay to public dissemination.

The Commission is proposing to redesignate current §§ 43.3(c)(2) and (3) as §§ 43.3(b)(4) and (5), respectively.

7. § 43.3(c)—Availability of Swap Transaction and Pricing Data to the Public

The Commission is proposing to relocate the requirements to make STAPD available to the public from § 43.3(d)(2) to §§ 43.3(c)(1) and (2).
92

As background, current § 43.3(d)(2) specifies that SDRs must make “publicly disseminated” STAPD “freely available and readily accessible” to the public. Currently, publicly disseminated is defined to mean to publish and make available STAPD in a non-discriminatory manner, through the internet or other electronic data feed that is widely published and in machine readable electronic format.

92
As discussed above in section II.C.6., the Commission is proposing to relocate the text of current § 43.3(c)(1), as the Commission proposes to modify it, to § 43.3(b)(2), and current §§ 43.3(c)(2) and (3) as §§ 43.3(b)(4) and (5), respectively.

The requirement in § 43.3(d)(2) supports the fairness and efficiency of markets and increases transparency, which in turn improves price discovery and decreases risk (
e.g.,
liquidity risk).
93

Most SDRs currently make historical STAPD spanning multiple years available on their websites for market participants to download, save, and analyze.
94

However, without clear requirements on how long SDRs must make this data available, or to make instructions available, a situation could arise where STAPD is reported, publicly disseminated, and then quickly or unreasonably made unavailable to the public. Removing STAPD in this fashion would deny the public a sufficient opportunity to review such data and ultimately impede the goals of increasing market transparency, improving price discovery, and mitigating risk.

93

See
Real-Time Public Reporting of Swap Transaction Data, 77 FR 1182, 1183.

94
DTCC-SDR's historical STAPD is available at
https://rtdata.dtcc.com/gtr/;
CME SDR's historical STAPD is available at
https://www.cmegroup.com/market-data/repository/data.html;
and ICE Trade Vault's historical STAPD is available at
https://www.icetradevault.com/tvus-ticker/#.

Therefore, the Commission is proposing to move the requirement in current § 43.3(d)(2) to new §§ 43.3(c)(1) and (2), along with revising the definition of “publicly disseminate” in § 43.2,
95

to establish requirements for SDRs to make STAPD available to the public on their websites. First, the Commission is proposing to specify that SDRs must make STAPD available on their websites for a period of a least one year after the initial “public dissemination” of such data. Second, the Commission is proposing to move the format requirements for SDRs in making this STAPD available to the revised definition of “public dissemination.”
96

95
The revisions to the definition of “publicly disseminate” are discussed above in section II.B.2.

96

Id.

Therefore, proposed § 43.3(c) would state that SDRs shall make: STAPD available on their websites for a period of time that is at least one year after the initial public dissemination thereof; instructions freely available on their websites on how to download, save, and search such STAPD; and STAPD that is publicly disseminated pursuant to part 43 available free of charge.

8. § 43.3(d)—Data Reported to SDRs

a. § 43.3(d)(1)—Standards for Reporting STAPD to SDRs

As discussed above in section II.B.2., the Commission is proposing to relocate the current requirement for SDRs to use a specific format in making STAPD available to the public from § 43.3(d)(1) to the definition of “public dissemination and publicly disseminate” in § 43.2.

Currently, § 45.13(b) requires reporting entities or counterparties to use the facilities, methods, or data standards provided or required by the SDR to which the entity or counterparty reports the data. An SDR may permit reporting entities and counterparties to use various facilities, methods, or data standards, provided that its requirements in this regard enable it to

report the data to the Commission in a format acceptable to the Commission, and transmit all swap data requested by the Commission to the Commission in an electronic file in a format acceptable to the Commission pursuant to § 45.13(a).

As explained in section III. below, the Commission had intended that part 43 data would be a subset of part 45 data reported to SDRs. As a result, § 45.13(b) indirectly required reporting entities or counterparties to use the data standards of their SDRs, as long as the standards enabled the SDR to report the data to the Commission in the format acceptable to the Commission. The Commission believes reporting counterparties would benefit from having a distinct regulatory requirement in part 43 for real-time public reporting. Therefore, the Commission is proposing § 43.3(d)(1), which would require reporting counterparties, SEFs, and DCMs to report the STAPD elements in appendix C in the form and manner provided in the technical specifications published by the Commission. The Commission is proposing a parallel requirement in § 45.13(a) in a separate part 45 NPRM.

b. § 43.3(d)(2)—Data Validations

As discussed above in section II.C.7., the Commission is proposing to relocate the current requirement for SDRs to make STAPD available to the public from § 43.3(d)(2) to §§ 43.3(c)(1) and (2).

Proposed § 43.3(d)(2) would require reporting counterparties, SEFs, and DCMs to satisfy SDR validation procedures when reporting STAPD to SDRs. Currently, the Commission's regulations do not require that SDRs validate STAPD. In a related NPRM, the Commission is proposing to require that SDRs implement validations, including on STAPD reported to SDRs.
97

As explained below in section II.C.9., the Commission is proposing to add related regulations for SDRs for STAPD validations in § 43.3(f). In general, § 43.3(f) would require SDRs to notify SEFs, DCMs, and reporting counterparties if the reported STAPD satisfied the SDR's validation procedures. The rule would further specify that SEFs, DCMs, and reporting counterparties have not fulfilled their reporting obligations until the STAPD passes an SDR's validation procedures.

97
2019 Part 49 NPRM.

The Commission believes that the SDR validation procedures in proposed § 43.3(f) would help improve the timeliness and accuracy of STAPD SDRs disseminate to the public. However, the Commission also believes that a companion requirement for reporting counterparties, SEFs, and DCMs to satisfy SDR validation procedures is necessary. Without such a requirement, the Commission is concerned about ambiguity as to the responsibilities of reporting counterparties, SEFs, and DCMs to respond to and satisfy the validation requirements specified in proposed § 43.3(f).

c. § 43.3(d)(3)—SDR Facilities, Methods, and Data Standards

The Commission is proposing to delete current § 43.3(d)(3). Currently, § 43.3(d)(3) requires SDRs to provide to the Commission a hyperlink to the internet website where publicly disseminated STAPD can be accessed by the public. This requirement is unnecessary, as SDRs have this information on their websites in a manner that is simple for the Commission and market participants to locate.

Proposed § 43.3(d)(3) would require reporting counterparties, SEFs, and DCMs to use the facilities, methods, or data standards provided or required by the SDR to which the reporting counterparty, SEF, or DCM, reports the data. The Commission understands that reporting counterparties, SEFs, and DCMs are currently using the facilities, methods, or data standards provided or required by the SDRs to which they are reporting data. Otherwise, reporting counterparties, SEFs, and DCMs would be unable to send STAPD to SDRs. However, as discussed throughout this section II.C.8., specifying this requirement for market participants would provide regulatory certainty.

9. § 43.3(f)—Data Validation Acceptance Message

The Commission is proposing new regulations for SDRs in validating STAPD in § 43.3(f). The Commission's regulations do not currently require that SDRs validate STAPD. The Commission understands, however, that SDRs have implemented validations as a best practice. As a result, each SDR runs a number of checks, or validations, on each STAPD message prior to publicly disseminating it. A failed validation can cause an SDR to reject the message without disseminating it to the public.

The Commission is concerned that the lack of validation requirements has resulted in reporting counterparties, SEFs, and DCMs being unaware of, or unfamiliar with, the existence of such validations. The Commission is concerned that the lack of awareness may be resulting in reporting counterparties, SEFs, and DCMs being unclear about their responsibilities to monitor their submissions to SDRs for errors that may result in validation failures that ultimately result in non-dissemination. As a result, the Commission is proposing in § 43.3(d)(2) to require reporting counterparties, SEFs, and DCMs to satisfy SDR validation procedures when reporting STAPD to SDRs. The Commission is also proposing § 43.3(f) to make clear the requirement for each SDR to notify submitting parties of their failure to meet the SDR's validation procedures and that an entity's reporting obligation is not satisfied until the SDR's validation procedures have been satisfied.

Therefore, proposed § 43.3(f)(1) would require that for an SDR to validate each STAPD report submitted it, the SDR shall notify the reporting counterparty, SEF, or DCM submitting the report whether the report satisfied the data validation procedures of the SDR. The SDR would have to provide such notice ASATP after accepting the STAPD report. Proposed § 43.3(f)(1) would provide that an SDR may satisfy the validation requirements by transmitting data validation acceptance messages as required by proposed § 49.10.
98

98
The Commission is proposing new regulations for SDRs to validate STAPD in a separate Roadmap proposal amending parts 45, 46, and 49.

Proposed § 43.3(f)(2) would provide that if a STAPD report submitted to an SDR does not satisfy the data validation procedures of the SDR, the reporting counterparty, SEF, or DCM required to submit the report has not satisfied its obligation to report STAPD in the manner provided by § 43.3(d). The reporting counterparty, SEF, or DCM would not have satisfied its obligation until it submits the STAPD report in the manner provided by § 43.3(d), which includes the requirement to satisfy the data validation procedures of the SDR.

10. § 43.3(h)—Timestamp Requirements

The Commission is proposing to delete the current timestamp requirements in § 43.3(h).
99

Regulation 43.3(h) sets forth timestamp requirements for registered entities, SDs, and MSPs with respect to STAPD for all PRSTs.
100

Pursuant to § 43.3(h)(1), SEFs

and DCMs must timestamp STAPD relating to a PRST with the date and time, to the nearest second, of when such SEF or DCM receives data from a swap counterparty (if applicable), and transmits such data to an SDR for public dissemination. Pursuant to § 43.3(h)(2), SDRs must timestamp STAPD relating to a PRST with the date and time, to the nearest second when such SDR receives data from a SEF, DCM, or reporting party, and publicly disseminates such data. Pursuant to § 43.3(h)(3), SDs or MSPs must timestamp STAPD for off-facility swaps with the date and time, to the nearest second when such SD or MSP transmits such data to an SDR for public dissemination. Regulation 43.3(h)(4) requires that records of all timestamps required by § 43.3(h) must be maintained for a period of at least five years from the execution of the PRST.

99
The Commission notes that it has proposed to remove and reserve current § 43.3(g), and move the substance of the current requirements in § 43.3(g) regarding SDR hours of operation to § 49.28.
See
2019 Part 49 NPRM at 20164. In this release, the Commission is proposing to relocate current § 43.3(i) to § 43.3(g), in conjunction with the proposed removal of current § 43.3(h) discussed above, as well as make conforming changes to the wording.

100
In addition to allowing the Commission to monitor compliance with the timing requirements, timestamps also confirm for market participants that publicly reported STAPD is in fact being

reported ASATP after transactions have been executed.

As discussed in section III. below, the Commission is proposing an updated list of STAPD elements in appendix C where the timestamps described in § 43.3(h) would be covered. Therefore, the Commission proposes to remove the requirements in §§ 43.3(h)(1)-(3) for SEFs, DCMs, SDs, MSPs, and SDRs to timestamp STAPD.

In addition, the Commission believes that the separate recordkeeping requirement for timestamps is duplicative of other recordkeeping requirements for SEFs, DCMs, SDs, MSPs, and SDRs. For instance, SDRs must already keep swap data for five years following the final termination of the swap and for an additional ten years in archival storage.
101

In the 2019 Part 49 NPRM, the Commission is proposing to more clearly include part 43 STAPD in the recordkeeping requirement in § 49.12(b)(1).
102

SEFs, DCMs, SDs, and MSPs have similar recordkeeping requirements for swaps.
103

As a result, when timestamps are reported or disseminated, SEFs, DCMs, SDs, MSPs, and SDRs subject to Commission jurisdiction have to maintain them as part of recordkeeping requirements separate from § 43.3(h)(4). Therefore, the Commission is also proposing to remove the requirement in § 43.3(h)(4) for these entities to keep records of the timestamps for at least five years from execution.

101

See
§§ 45.2(f) and (g) (containing recordkeeping requirements for SDRs);
see also
§ 49.12(a) (referencing part 45 recordkeeping requirements). In the 2019 Part 49 NPRM, the Commission is proposing to move the requirements in §§ 45.2(f) and (g) to § 49.12.
See
Certain Swap Data Repository and Data Reporting Requirements, 84 FR 21044, 21103-04.

102
The Commission is doing so by replacing the term “swap data” with “SDR data,” which the Commission proposes to define as data required to be reported pursuant to two or more of parts 43, 45, 46, or 49 of the Commission's regulations.
See
Certain Swap Data Repository and Data Reporting Requirements, 84 FR 21044, 21103-04.

103
17 CFR 45.2(c) requires SDs, MSPs, SEFs, and DCMs subject to Commission jurisdiction to maintain records for each swap throughout the life of the swap for a period of at least five years following the final termination of the swap.

Request for Comment

The Commission requests comment on all aspects of the proposed changes to § 43.3. In addition, the Commission requests specific comment on the following:

(2) Instead of permitting a delay for PPS, should reporting counterparties be required to submit PPSs ASATP after execution using the Post-priced swap indicator (59), leaving the price empty and then be required to update that entry after the price is determined?

(3) Should the Commission permit an indefinite delay for reporting STAPD for PPSs? In other words, should reporting such data be required only once the price and/or other Variable Terms is/are known regardless of how long that takes? The Commission notes that such swaps could be flagged on the public tape as PPSs once reported. Alternatively, should the Commission set a shorter deadline for reporting STAPD for PPS?

(4) Should the Commission exclude from the PPS definition and/or from the reporting delay in proposed § 43.3(a)(4) swaps for which a price is not known at execution because it is contingent upon the outcome of SD hedging? Would permitting such swaps to receive the reporting delay in proposed § 43.3(a)(4) cause market participants to intentionally delay reporting in reliance on the need to hedge a swap where such market participants do not delay their reporting under current Commission reporting regulations?

(5) Should market participants be required to rely on the Commission's block trade reporting delays and capping and rounding rules, rather than proposed § 43.3(a)(4), to avoid the front-running concerns discussed above in section II.C.2.? Conversely, are the CEA's provisions and the Commission's regulations sufficient to deter market participants from intentionally altering their behavior to delay their reporting of swaps for which a price is not known at execution because it is contingent upon the outcome of SD hedging?

(6) Should the Commission modify its PPS indicator in appendix C, or add another indicator, to require market participants to indicate whether a swap is a PPS because it is contingent upon the outcome of SD hedging?

(7) Should the Commission modify its PPS indicator, or add another indicator, to require market participants to indicate whether a swap is a PPS based on other common reasons, such as the price being determined based on the volume-weighted average price (also known as “VWAP”) of an index level at market close?

(8) The Commission understands that trade at settlement (“TAS”) futures orders
104

are displayed to the market when entered, in contrast to PPS executions under proposed § 43.3(a)(4). Do the similarities between PPSs and TAS futures orders warrant reporting PPSs when executed, rather than by the deadline specified in proposed § 43.3(a)(4)? Conversely, do PPSs' relative illiquidity vis-a-vis TAS futures orders warrant the reporting delay in proposed § 43.3(a)(4)?
105

104

See, e.g., Trading at Settlement (TAS),
CME Group Inc.,
available at https://www.cmegroup.com/trading/trading-at-settlement.html
(explaining that “Trading at Settlement (TAS) order types . . . allow you to buy or sell a contract at the settlement price”).

105

See
Paul Peterson, Trading at Settlement for Agricultural Futures: Results from the First Month, farmdocdaily,
available at https://farmdocdaily.illinois.edu/2015/07/trading-at-settlement-for-agricultural-futures.html
(Jul. 29, 2015) (noting that “[t]o prevent [“banging the close” and other forms of manipulation] . . . from happening in the ag markets, TAS is available only in the most liquid commodities, and only in the most liquid contract months” and “[s]ome energy market participants claim that . . . price discovery is reduced because TAS trades are simply assigned a price without having to compete (like a limit or `price' order would) for a price in the open market”).

(9) Did the Commission accurately describe the prime brokerage swap transaction structures discussed above? Should the real-time public tape reflect the number of mirror swaps related to a given trigger swap to provide information to the public on the number of prime brokerage swap transaction structures with multiple mirror swaps? Would such an indicator provide useful information to market participants?

(10) Should the Commission scale back the scope of the exclusion of mirror swaps from the PRST definition in proposed § 43.3(a)(6)(i) such that each of the following swaps would be PRSTs: (a) Swaps executed as part of partial reverse give-up arrangements and/or (b) swaps executed as part of other prime brokerage transaction structures in which the notional amount of a mirror swap may differ from the notional amount of the corresponding trigger swap? Should the Commission scale back the scope of the exclusion of mirror swaps from the PRST definition in proposed § 43.3(a)(6)(i) such that the exclusion would be limited to “plain vanilla” mirror swaps?

(11) If a SD executed one or more swaps to hedge a swap that the SD had executed with a counterparty, and the hedging swap(s) was/were executed at the same price as the swap being hedged, the hedging swap(s) generally would be a PRST or PRSTs and, thus, subject to part 43 reporting.
106

Given the similarity of such transaction structures to trigger swap-mirror swap transactions structures, is it appropriate to treat mirror swaps as non-PRSTs pursuant to proposed § 43.3(a)(6)?

106

But see
paragraph (2) of the “Publicly reportable swap transaction” definition in § 43.2, which states that examples of executed swaps that do not fall within the definition of publicly reportable swap transaction may include internal swaps between one-hundred percent owned subsidiaries of the same parent entity.

(12) Should the Commission modify proposed § 43.2(a) to include a carve out for prime brokerage service fees to reflect that such fees might not be included in all such mirror swaps?

(13) Is the proposed definition of “prime broker” sufficient and clear enough to accurately describe the term as understood in common industry practice? Is it sufficiently narrow to limit the non-reporting of mirror swaps to transactions involving “prime brokers,” as that term is understood in the market? If the Commission should propose a different definition of “prime broker,” what should that definition be?

(14) In order to ensure data quality, should the Commission mandate a certain standard for reporting to the SDRs? If so, what standard should the Commission mandate and what would be the benefits of mandating this standard? If not, why should the Commission not mandate a standard?

D. § 43.4—Swap Transaction and Pricing Data To Be Publicly Disseminated in Real-Time

1. § 43.4(a)-(e)—Public Dissemination, Additional Swap Information, Anonymity, and Unique Product Identifiers

The Commission proposes to make several primarily non-substantive changes to current §§ 43.4(a)-(e), (g) and (h). As background, § 43.4(a) generally requires that STAPD must be reported to an SDR so that the SDR can publicly disseminate it in real-time, including according to the manner described in § 43.4 and appendix A. The Commission proposes to delete current § 43.4(a). The Commission believes that current § 43.4(a) is overly general. As a result of removing current § 43.4(a), the Commission proposes to re-designate §§ 43.4(b)-(d) as §§ 43.4(a)-(c).

Current § 43.4(b) requires that any SDR that accepts and publicly disseminates STAPD in real-time shall publicly disseminate the information described in appendix A, as applicable, for any PRST. The Commission proposes to re-designate § 43.4(b) as § 43.4(a), and make conforming changes. As proposed, § 43.4(a) would require that any SDR that accepts and publicly disseminates STAPD in real-time shall publicly disseminate the information for the STAPD elements in appendix C to part 43 in the form and manner provided in the technical specifications published by the Commission.

Current § 43.4(c) states that SDRs that accept and publicly disseminate STAPD in real-time may require reporting parties, SEFs, and DCMs to report to the SDR information necessary to compare the STAPD that was publicly disseminated in real-time to the data reported to an SDR pursuant to section 2(a)(13)(G) of the CEA or to confirm that parties to a swap have reported in a timely manner pursuant to § 43.3. The Commission proposes to re-designate § 43.4(c) as § 43.4(b) and make minor non-substantive changes.

Current § 43.4(d) contains regulations for maintaining the anonymity of the parties to a PRST. The Commission is proposing to re-designate § 43.4(d) as § 43.4(c) and make minor non-substantive changes. Among these changes, the Commission is proposing to remove current § 43.4(d)(4)(i)-(iii); re-designate § 43.4(d)(4) as § 43.4(c)(4); and consolidate the substance of §§ 43.4(d)(4)(i) and (iii) in proposed § 43.4(c)(4). These actions would remove the requirement in current § 43.4(d)(4)(ii) that registered SDRs publicly disseminate the actual assets underlying other commodity swaps that either reference one of the contracts described in appendix B to part 43
107

or that are economically related to such contracts.
108

107

See
current § 43.3(d)(4)(ii)(A).

108

See
current § 43.3(d)(4)(ii)(B).

Currently, depending on the assets underlying other commodity swaps, such assets are either disseminated as reported or are disseminated as described in § 43.4(d)(4)(iii). Current § 43.4(d)(4)(iii) states that the underlying assets of swaps in the “other commodity” asset class that are not described in § 43.4(d)(4)(ii) shall be publicly disseminated by limiting the detail of the underlying assets. Current § 43.4(d)(4)(iii) also states that the identification of any specific delivery point or pricing point associated with the underlying asset of such “other commodity” swap shall be publicly disseminated pursuant to appendix E to part 43.

As proposed to be amended, § 43.4(c)(4) would provide the same geographic masking treatment for all assets underlying “other commodity” swaps, namely the geographic masking described in current § 43.4(d)(4)(iii). The Commission believed when adopting part 43 that other commodity swaps referencing or economically related to one of the contracts described in appendix B to part 43 were sufficiently liquid that publicly disseminating such information would not identify the swap counterparties
109

or materially reduce swap market liquidity.
110

However, the Commission preliminarily believes that other commodity swaps referencing, or economically related to, the contracts in appendix B may still be sufficiently bespoke to warrant additional masking. Consequently, the Commission proposes to remove the requirement in current § 43.4(d)(4)(ii) that registered SDRs publicly disseminate the actual assets underlying other commodity swaps that either reference one of the contracts described in appendix B to part 43 or that are economically related to such contracts. Because the Commission proposes to remove that requirement from current § 43.4(d)(4)(ii), the Commission also proposes to remove appendix B to part 43 from its regulations. The Commission also proposes to redesignate current appendix E as appendix B.

109

See
Real-Time Public Reporting of Swap Transaction Data, 77 FR 1182, 1211. CEA section 2(a)(13)(E)(i) requires the Commission to ensure that information disseminated pursuant to its real-time reporting rules does not identify swap “participants.” 7 U.S.C. 2(a)(13)(E)(i).

110
CEA section 2(a)(13)(E)(iv) requires the Commission to take into account whether public disclosure pursuant to its real-time reporting rules will materially reduce market liquidity. 7 U.S.C. 2(a)(13)(E)(iv).

Finally, current § 43.4(e) permits SDRs to disseminate UPIs for certain data fields once a UPI is available. The Commission proposes to delete current § 43.4(e), which gives SDRs discretion regarding what fields to publicly disseminate after a UPI exists.
111

As discussed below in section III., the UPI will be addressed in the STAPD elements in appendix C.

111
The Commission has not yet designated a UPI and product classification system to be used in recordkeeping and swap data reporting pursuant to § 45.7.

2. § 43.4(f)-(g)—Process To Determine Appropriate Rounded Notional or Principal Amounts

Current § 43.4(f) requires that reporting parties, SEFs, and DCMs report the actual notional or principal amount of any swap, including block

trades, to an SDR that accepts and publicly disseminates such data pursuant to part 43.
112

112
17 CFR 43.4(f)(1)-(2).

As discussed above, the Commission is proposing to remove §§ 43.4(a) and (e), and re-designate § 43.4(b)-(d) as § 43.4(a)-(c). As a result of these changes, the Commission proposes to re-designate § 43.4(f) as § 43.4(d) and make minor non-substantive changes.

3. § 43.4(g)—Public Dissemination of Rounded Notional or Principal Amounts

As discussed above, the Commission is proposing to redesignate current § 43.4(f) as § 43.4(d). As a result of these changes, the Commission is proposing to re-designate current § 43.4(g) as § 43.4(e) and make minor non-substantive edits.

One of these non-substantive edits is a structural change in the regulations. Current § 43.4(g), titled “Public dissemination of rounded notional or principal amounts,” states that the notional or principal amount of a PRST, as described in appendix A to this part, shall be rounded and publicly disseminated by a registered SDR, and then sets out the rules for rounding.

The Commission is proposing to rephrase § 43.4(g), which would be re-designated as § 43.4(e), to state that the notional or principal amount of a PRST shall be publicly disseminated by an SDR subject to rounding as set forth in § 43.4(f) and a cap size as set forth in § 43.4(g).

Then, the rounding rules in current § 43.4(g) would be in a new section § 43.4(f) titled “Process to determine appropriate rounded notional or principal amounts.” Section § 43.4(f) would then contain the rounding rules for SDRs, subject to two substantive changes explained below, among other non-substantive changes.

The Commission proposes amending §§ 43.4(g)(8) and (9), which would be re-designated as §§ 43.4(f)(8) and (9). Current § 43.4(g)(8) requires a registered SDR to round the notional or principal amount of a PRST to the nearest one billion if it is less than 100 billion but equal to or greater than one billion. The Commission proposes to amend proposed § 43.4(f)(8) to require rounding to the nearest 100 million instead of one billion. Current § 43.4(g)(9) requires a registered SDR to round the notional or principal amount of a PRST to the nearest 50 billion if it is greater than 100 billion. The Commission proposes to amend § 43.4(f)(9) to require rounding to the nearest 10 billion and to add the words “equal to or” before “greater than 100 billion” to include swaps with notional or principal amounts that are exactly 100 billion, the omission of which from the 2012 RTR Final Rule appears to have been an oversight.
113

113
The omission of swaps with notional or principal amounts of exactly 100 billion did not change the rounding result. Although such swaps are not presently subject to rounding due to their omission from § 43.4(g)(9), even if they were included therein, because their notional or principal amount is a round number already, they would not have been rounded, and would not be rounded as a result of proposed § 43.4(f)(9). However, because all swaps with notional or principal amounts of greater than 100 billion will be rounded to the nearest 10 billion if § 43.4(f)(9) is adopted as proposed, such swaps wou

[Text truncated at 120,000 characters. The full text is on the page linked above.]

---

Source: Frix Law Library, https://www.frixlaw.com/law-library/documents/fr%3A2020-04405. Public record. Not legal advice.
