17 C.F.R. §§ 242.901–242.909

9 sections in range

§242.901. Reporting obligations.

17 C.F.R. § 242.901

(a)

Assigning reporting duties. A security-based swap, including a security-based swap that results from the allocation, termination, novation, or assignment of another security-based swap, shall be reported as follows:

(1)

Platform-executed security-based swaps that will be submitted to clearing. If a security-based swap is executed on a platform and will be submitted to clearing, the platform on which the transaction was executed shall report to a registered security-based swap data repository the counterparty ID or the execution agent ID of each direct counterparty, as applicable, and the information set forth in paragraph (c) of this section (except that, with respect to paragraph (c)(5) of this section, the platform need indicate only if both direct counterparties are registered security-based swap dealers) and paragraphs (d)(9) and (10) of this section.

(2)

All other security-based swaps. For all security-based swaps other than platform-executed security-based swaps that will be submitted to clearing, the reporting side shall provide the information required by §§ 242.900 through 242.909 to a registered security-based swap data repository. The reporting side shall be determined as follows:

(i)

Clearing transactions. For a clearing transaction, the reporting side is the registered clearing agency that is a counterparty to the transaction.

(ii)

Security-based swaps other than clearing transactions.

(A)

If both sides of the security-based swap include a registered security-based swap dealer, the sides shall select the reporting side.

(B)

If only one side of the security-based swap includes a registered security-based swap dealer, that side shall be the reporting side.

(C)

If both sides of the security-based swap include a registered major security-based swap participant, the sides shall select the reporting side.

(D)

If one side of the security-based swap includes a registered major security-based swap participant and the other side includes neither a registered security-based swap dealer nor a registered major security-based swap participant, the side including the registered major security-based swap participant shall be the reporting side.

(E)

If neither side of the security-based swap includes a registered security-based swap dealer or registered major security-based swap participant:

(1) If both sides include a U.S. person, the sides shall select the reporting side.

(2) If one side includes a non-U.S. person that falls within § 242.908(b)(5) or a U.S. person and the other side includes a non-U.S. person that falls within § 242.908(b)(5), the sides shall select the reporting side.

(3) If one side includes only non-U.S. persons that do not fall within § 242.908(b)(5) and the other side includes a non-U.S. person that falls within § 242.908(b)(5) or a U.S. person, the side including a non-U.S. person that falls within § 242.908(b)(5) or a U.S. person shall be the reporting side.

(4) If neither side includes a U.S. person and neither side includes a non-U.S. person that falls within § 242.908(b)(5) but the security-based swap is effected by or through a registered broker-dealer (including a registered security-based swap execution facility), the registered broker-dealer (including a registered security-based swap execution facility) shall report the counterparty ID or the execution agent ID of each direct counterparty, as applicable, and the information set forth in paragraph (c) of this section (except that, with respect to paragraph (c)(5) of this section, the registered broker-dealer (including a registered security-based swap execution facility) need indicate only if both direct counterparties are registered security-based swap dealers) and paragraphs (d)(9) and (10) of this section.

(3)

Notification to registered clearing agency. A person who, under paragraph (a)(1) or (a)(2)(ii) of this section, has a duty to report a security-based swap that has been submitted to clearing at a registered clearing agency shall promptly provide that registered clearing agency with the transaction ID of the submitted security-based swap and the identity of the registered security-based swap data repository to which the transaction will be reported or has been reported.

(b)

Alternate recipient of security-based swap information. If there is no registered security-based swap data repository that will accept the report required by § 242.901(a), the person required to make such report shall instead provide the required information to the Commission.

(c)

Primary trade information. The reporting side shall report the following information within the timeframe specified in paragraph (j) of this section:

(1)

The product ID, if available. If the security-based swap has no product ID, or if the product ID does not include the following information, the reporting side shall report:

(i)

Information that identifies the security-based swap, including the asset class of the security-based swap and the specific underlying reference asset(s), reference issuer(s), or reference index;

(ii)

The effective date;

(iii)

The scheduled termination date;

(iv)

The terms of any standardized fixed or floating rate payments, and the frequency of any such payments; and

(v)

If the security-based swap is customized to the extent that the information provided in paragraphs (c)(1)(i) through (iv) of this section does not provide all of the material information necessary to identify such customized security-based swap or does not contain the data elements necessary to calculate the price, a flag to that effect;

(2)

The date and time, to the second, of execution, expressed using Coordinated Universal Time (UTC);

(3)

The price, including the currency in which the price is expressed and the amount(s) and currenc(ies) of any up-front payments;

(4)

The notional amount(s) and the currenc(ies) in which the notional amount(s) is expressed;

(5)

If both sides of the security-based swap include a registered security-based swap dealer, an indication to that effect;

(6)

Whether the direct counterparties intend that the security-based swap will be submitted to clearing; and

(7)

If applicable, any flags pertaining to the transaction that are specified in the policies and procedures of the registered security-based swap data repository to which the transaction will be reported.

(d)

Secondary trade information. In addition to the information required under paragraph (c) of this section, for each security-based swap for which it is the reporting side, the reporting side shall report the following information within the timeframe specified in paragraph (j) of this section:

(1)

The counterparty ID or the execution agent ID of each counterparty, as applicable;

(2)

As applicable, the branch ID, broker ID, execution agent ID, trader ID, and trading desk ID of the direct counterparty on the reporting side;

(3)

To the extent not provided pursuant to paragraph (c)(1) of this section, the terms of any fixed or floating rate payments, or otherwise customized or non-standard payment streams, including the frequency and contingencies of any such payments;

(4)

For a security-based swap that is not a clearing transaction and that will not be allocated after execution, the title and date of any master agreement, collateral agreement, margin agreement, or any other agreement incorporated by reference into the security-based swap contract;

(5)

To the extent not provided pursuant to paragraph (c) of this section or other provisions of this paragraph (d), any additional data elements included in the agreement between the counterparties that are necessary for a person to determine the market value of the transaction;

(6)

If applicable, and to the extent not provided pursuant to paragraph (c) of this section, the name of the clearing agency to which the security-based swap will be submitted for clearing;

(7)

If the direct counterparties do not intend to submit the security-based swap to clearing, whether they have invoked the exception in Section 3C(g) of the Exchange Act (15 U.S.C. 78c-3(g));

(8)

To the extent not provided pursuant to the other provisions of this paragraph (d), if the direct counterparties do not submit the security-based swap to clearing, a description of the settlement terms, including whether the security-based swap is cash-settled or physically settled, and the method for determining the settlement value;

(9)

The platform ID, if applicable, or if a registered broker-dealer (including a registered security-based swap execution facility) is required to report the security-based swap by § 242.901(a)(2)(ii)(E)(4), the broker ID of that registered broker-dealer (including a registered security-based swap execution facility); and

(10)

If the security-based swap arises from the allocation, termination, novation, or assignment of one or more existing security-based swaps, the transaction ID of the allocated, terminated, assigned, or novated security-based swap(s), except in the case of a clearing transaction that results from the netting or compression of other clearing transactions.

(e)

Reporting of life cycle events.

(1)

(i)

Generally. A life cycle event, and any adjustment due to a life cycle event, that results in a change to information previously reported pursuant to paragraph (c), (d), or (i) of this section shall be reported by the reporting side, except that the reporting side shall not report whether or not a security-based swap has been accepted for clearing.

(ii)

Acceptance for clearing. A registered clearing agency shall report whether or not it has accepted a security-based swap for clearing.

(2)

All reports of life cycle events and adjustments due to life cycle events shall, within the timeframe specified in paragraph (j) of this section, be reported to the entity to which the original security-based swap transaction will be reported or has been reported and shall include the transaction ID of the original transaction.

(f)

Time stamping incoming information. A registered security-based swap data repository shall time stamp, to the second, its receipt of any information submitted to it pursuant to paragraph (c), (d), (e), or (i) of this section.

(g)

Assigning transaction ID. A registered security-based swap data repository shall assign a transaction ID to each security-based swap, or establish or endorse a methodology for transaction IDs to be assigned by third parties.

(h)

Format of reported information. A person having a duty to report shall electronically transmit the information required under this section in a format required by the registered security-based swap data repository to which it reports.

(i)

Reporting of pre-enactment and transitional security-based swaps. With respect to any pre-enactment security-based swap or transitional security-based swap in a particular asset class, and to the extent that information about such transaction is available, the reporting side shall report all of the information required by paragraphs (c) and (d) of this section to a registered security-based swap data repository that accepts security-based swaps in that asset class and indicate whether the security-based swap was open as of the date of such report.

(j)

Interim timeframe for reporting. The reporting timeframe for paragraphs (c) and (d) of this section shall be 24 hours after the time of execution (or acceptance for clearing in the case of a security-based swap that is subject to regulatory reporting and public dissemination solely by operation of § 242.908(a)(1)(ii)), or, if 24 hours after the time of execution or acceptance, as applicable, would fall on a day that is not a business day, by the same time on the next day that is a business day. The reporting timeframe for paragraph (e) of this section shall be 24 hours after the occurrence of the life cycle event or the adjustment due to the life cycle event.

Notes, amendments, and revision history

Amendments

[80 FR 14728, Mar. 19, 2015, as amended at 81 FR 53653, Aug. 12, 2016]

Source

Source: 80 FR 14728, Mar. 19, 2015, unless otherwise noted.

Authority

Authority: 15 U.S.C. 77g, 77q(a), 77s(a), 78b, 78c, 78c-4, 78g(c)(2), 78i(a), 78j, 78k-1(c), 78 l, 78m, 78n, 78 o (b), 78 o (c), 78 o (g), 78q(a), 78q(b), 78q(h), 78w(a), 78dd-1, 78mm, 80a-23, 80a-29, 80a-37, and 8343.

Source

Source: 62 FR 544, Jan. 3, 1997, unless otherwise noted.

Amendments

[80 FR 14728, Mar. 19, 2015, as amended at 81 FR 53653, Aug. 12, 2016]

§242.902. Public dissemination of transaction reports.

17 C.F.R. § 242.902

(a)

General. Except as provided in paragraph (c) of this section, a registered security-based swap data repository shall publicly disseminate a transaction report of a security-based swap, or a life cycle event or adjustment due to a life cycle event, immediately upon receipt of information about the security-based swap, or upon re-opening following a period when the registered security-based swap data repository was closed. The transaction report shall consist of all the information reported pursuant to § 242.901(c), plus any condition flags contemplated by the registered security-based swap data repository's policies and procedures that are required by § 242.907.

(b)

[Reserved].

(c)

Non-disseminated information. A registered security-based swap data repository shall not disseminate:

(1)

The identity of any counterparty to a security-based swap;

(2)

With respect to a security-based swap that is not cleared at a registered clearing agency and that is reported to the registered security-based swap data repository, any information disclosing the business transactions and market positions of any person;

(3)

Any information regarding a security-based swap reported pursuant to § 242.901(i);

(4)

Any non-mandatory report;

(5)

Any information regarding a security-based swap that is required to be reported pursuant to §§ 242.901 and 242.908(a)(1) but is not required to be publicly disseminated pursuant to § 242.908(a)(2);

(6)

Any information regarding a clearing transaction that arises from the acceptance of a security-based swap for clearing by a registered clearing agency or that results from netting other clearing transactions;

(7)

Any information regarding the allocation of a security-based swap; or

(8)

Any information regarding a security-based swap that has been rejected from clearing or rejected by a prime broker if the original transaction report has not yet been publicly disseminated.

(d)

Temporary restriction on other market data sources. No person shall make available to one or more persons (other than a counterparty or a post-trade processor) transaction information relating to a security-based swap before the primary trade information about the security-based swap is sent to a registered security-based swap data repository.

Notes, amendments, and revision history

Amendments

[80 FR 14728, Mar. 19, 2015, as amended at 81 FR 53654, Aug. 12, 2016]

Source

Source: 80 FR 14728, Mar. 19, 2015, unless otherwise noted.

Authority

Source

Source: 62 FR 544, Jan. 3, 1997, unless otherwise noted.

Amendments

[80 FR 14728, Mar. 19, 2015, as amended at 81 FR 53654, Aug. 12, 2016]

§242.903. Coded information.

17 C.F.R. § 242.903

(a)

If an internationally recognized standards-setting system that imposes fees and usage restrictions on persons that obtain UICs for their own usage that are fair and reasonable and not unreasonably discriminatory and that meets the criteria of paragraph (b) of this section is recognized by the Commission and has assigned a UIC to a person, unit of a person, or product (or has endorsed a methodology for assigning transaction IDs), the registered security-based swap data repository shall employ that UIC (or methodology for assigning transaction IDs). If no such system has been recognized by the Commission, or a recognized system has not assigned a UIC to a particular person, unit of a person, or product (or has not endorsed a methodology for assigning transaction IDs), the registered security-based swap data repository shall assign a UIC to that person, unit of person, or product using its own methodology (or endorse a methodology for assigning transaction IDs). If the Commission has recognized such a system that assigns UICs to persons, each participant of a registered security-based swap data repository shall obtain a UIC from or through that system for identifying itself, and each participant that acts as a guarantor of a direct counterparty's performance of any obligation under a security-based swap that is subject to § 242.908(a) shall, if the direct counterparty has not already done so, obtain a UIC for identifying the direct counterparty from or through that system, if that system permits third-party registration without a requirement to obtain prior permission of the direct counterparty.

(b)

A registered security-based swap data repository may permit information to be reported pursuant to § 242.901, and may publicly disseminate that information pursuant to § 242.902, using codes in place of certain data elements, provided that the information necessary to interpret such codes is widely available to users of the information on a non-fee basis.

Notes, amendments, and revision history

Source

Source: 80 FR 14728, Mar. 19, 2015, unless otherwise noted.

Authority

Source

Source: 62 FR 544, Jan. 3, 1997, unless otherwise noted.

§242.904. Operating hours of registered security-based swap data repositories.

17 C.F.R. § 242.904

A registered security-based swap data repository shall have systems in place to continuously receive and disseminate information regarding security-based swaps pursuant to §§ 242.900 through 242.909, subject to the following exceptions:

(a)

A registered security-based swap data repository may establish normal closing hours during periods when, in its estimation, the U.S. market and major foreign markets are inactive. A registered security-based swap data repository shall provide reasonable advance notice to participants and to the public of its normal closing hours.

(b)

A registered security-based swap data repository may declare, on an ad hoc basis, special closing hours to perform system maintenance that cannot wait until normal closing hours. A registered security-based swap data repository shall, to the extent reasonably possible under the circumstances, avoid scheduling special closing hours during periods when, in its estimation, the U.S. market and major foreign markets are most active; and provide reasonable advance notice of its special closing hours to participants and to the public.

(c)

During normal closing hours, and to the extent reasonably practicable during special closing hours, a registered security-based swap data repository shall have the capability to receive and hold in queue information regarding security-based swaps that has been reported pursuant to §§ 242.900 through 242.909.

(d)

When a registered security-based swap data repository re-opens following normal closing hours or special closing hours, it shall disseminate transaction reports of security-based swaps held in queue, in accordance with the requirements of § 242.902.

(e)

If a registered security-based swap data repository could not receive and hold in queue transaction information that was required to be reported pursuant to §§ 242.900 through 242.909, it must immediately upon re-opening send a message to all participants that it has resumed normal operations. Thereafter, any participant that had an obligation to report information to the registered security-based swap data repository pursuant to §§ 242.900 through 242.909, but could not do so because of the registered security-based swap data repository's inability to receive and hold in queue data, must promptly report the information to the registered security-based swap data repository.

Notes, amendments, and revision history

Source

Source: 80 FR 14728, Mar. 19, 2015, unless otherwise noted.

Authority

Source

Source: 62 FR 544, Jan. 3, 1997, unless otherwise noted.

§242.905. Correction of errors in security-based swap information.

17 C.F.R. § 242.905

(a)

Duty to correct. Any counterparty or other person having a duty to report a security-based swap that discovers an error in information previously reported pursuant to §§ 242.900 through 242.909 shall correct such error in accordance with the following procedures:

(1)

If a person that was not the reporting side for a security-based swap transaction discovers an error in the information reported with respect to such security-based swap, that person shall promptly notify the person having the duty to report the security-based swap of the error; and

(2)

If the person having the duty to report a security-based swap transaction discovers an error in the information reported with respect to a security-based swap, or receives notification from a counterparty of an error, such person shall promptly submit to the entity to which the security-based swap was originally reported an amended report pertaining to the original transaction report. If the person having the duty to report reported the initial transaction to a registered security-based swap data repository, such person shall submit an amended report to the registered security-based swap data repository in a manner consistent with the policies and procedures contemplated by § 242.907(a)(3).

(b)

Duty of security-based swap data repository to correct. A registered security-based swap data repository shall:

(1)

Upon discovery of an error or receipt of a notice of an error, verify the accuracy of the terms of the security-based swap and, following such verification, promptly correct the erroneous information regarding such security-based swap contained in its system; and

(2)

If such erroneous information relates to a security-based swap that the registered security-based swap data repository previously disseminated and falls into any of the categories of information enumerated in § 242.901(c), publicly disseminate a corrected transaction report of the security-based swap promptly following verification of the trade by the counterparties to the security-based swap, with an indication that the report relates to a previously disseminated transaction.

Notes, amendments, and revision history

Amendments

[80 FR 14728, Mar. 19, 2015, as amended at 81 FR 53654, Aug. 12, 2016]

Source

Source: 80 FR 14728, Mar. 19, 2015, unless otherwise noted.

Authority

Source

Source: 62 FR 544, Jan. 3, 1997, unless otherwise noted.

Amendments

[80 FR 14728, Mar. 19, 2015, as amended at 81 FR 53654, Aug. 12, 2016]

§242.906. Other duties of participants.

17 C.F.R. § 242.906

(a)

Identifying missing UIC information. A registered security-based swap data repository shall identify any security-based swap reported to it for which the registered security-based swap data repository does not have the counterparty ID and (if applicable) the broker ID, branch ID, execution agent ID, trading desk ID, and trader ID of each direct counterparty. Once a day, the registered security-based swap data repository shall send a report to each participant of the registered security-based swap data repository or, if applicable, an execution agent, identifying, for each security-based swap to which that participant is a counterparty, the security-based swap(s) for which the registered security-based swap data repository lacks counterparty ID and (if applicable) broker ID, branch ID, execution agent ID, trading desk ID, and trader ID. A participant of a registered security-based swap data repository that receives such a report shall provide the missing information with respect to its side of each security-based swap referenced in the report to the registered security-based swap data repository within 24 hours.

(b)

Duty to provide ultimate parent and affiliate information. Each participant of a registered security-based swap data repository that is not a platform, a registered clearing agency, an externally managed investment vehicle, or a registered broker-dealer (including a registered security-based swap execution facility) that becomes a participant solely as a result of making a report to satisfy an obligation under § 242.901(a)(2)(ii)(E)(4) shall provide to the registered security-based swap data repository information sufficient to identify its ultimate parent(s) and any affiliate(s) of the participant that also are participants of the registered security-based swap data repository, using ultimate parent IDs and counterparty IDs. Any such participant shall promptly notify the registered security-based swap data repository of any changes to that information.

(c)

Policies and procedures to support reporting compliance. Each participant of a registered security-based swap data repository that is a registered security-based swap dealer, registered major security-based swap participant, registered clearing agency, platform, or registered broker-dealer (including a registered security-based swap execution facility) that becomes a participant solely as a result of making a report to satisfy an obligation under § 242.901(a)(2)(ii)(E)(4) shall establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure that it complies with any obligations to report information to a registered security-based swap data repository in a manner consistent with §§ 242.900 through 242.909. Each such participant shall review and update its policies and procedures at least annually.

Notes, amendments, and revision history

Amendments

[81 FR 53654, Aug. 12, 2016]

Source

Source: 80 FR 14728, Mar. 19, 2015, unless otherwise noted.

Authority

Source

Source: 62 FR 544, Jan. 3, 1997, unless otherwise noted.

Amendments

[81 FR 53654, Aug. 12, 2016]

§242.907. Policies and procedures of registered security-based swap data repositories.

17 C.F.R. § 242.907

(a)

General policies and procedures. With respect to the receipt, reporting, and dissemination of data pursuant to §§ 242.900 through 242.909, a registered security-based swap data repository shall establish and maintain written policies and procedures:

(1)

That enumerate the specific data elements of a security-based swap that must be reported, which shall include, at a minimum, the data elements specified in § 242.901(c) and (d);

(2)

That specify one or more acceptable data formats (each of which must be an open-source structured data format that is widely used by participants), connectivity requirements, and other protocols for submitting information;

(3)

For specifying procedures for reporting life cycle events and corrections to previously submitted information, making corresponding updates or corrections to transaction records, and applying an appropriate flag to the transaction report to indicate that the report is an error correction required to be disseminated by § 242.905(b)(2), or is a life cycle event, or any adjustment due to a life cycle event, required to be disseminated by § 242.902(a);

(4)

For—

(i)

Identifying characteristic(s) of a security-based swap, or circumstances associated with the execution or reporting of the security-based swap, that could, in the fair and reasonable estimation of the registered security-based swap data repository, cause a person without knowledge of these characteristic(s) or circumstance(s), to receive a distorted view of the market;

(ii)

Establishing flags to denote such characteristic(s) or circumstance(s);

(iii)

Directing participants that report security-based swaps to apply such flags, as appropriate, in their reports to the registered security-based swap data repository; and

(iv)

Applying such flags—

(A)

To disseminated reports to help to prevent a distorted view of the market; or

(B)

In the case of a transaction referenced in § 242.902(c), to suppress the report from public dissemination entirely, as appropriate;

(5)

For assigning UICs in a manner consistent with § 242.903; and

(6)

For periodically obtaining from each participant other than a platform, registered clearing agency, externally managed investment vehicle, or registered broker-dealer (including a registered security-based swap execution facility) that becomes a participant solely as a result of making a report to satisfy an obligation under § 242.901(a)(2)(ii)(E)(4) information that identifies the participant's ultimate parent(s) and any participant(s) with which the participant is affiliated, using ultimate parent IDs and counterparty IDs.

(b)

[Reserved].

(c)

Public availability of policies and procedures. A registered security-based swap data repository shall make the policies and procedures required by §§ 242.900 through 242.909 publicly available on its Web site.

(d)

Updating of policies and procedures. A registered security-based swap data repository shall review, and update as necessary, the policies and procedures required by §§ 242.900 through 242.909 at least annually. Such policies and procedures shall indicate the date on which they were last reviewed.

(e)

A registered security-based swap data repository shall provide to the Commission, upon request, information or reports related to the timeliness, accuracy, and completeness of data reported to it pursuant to §§ 242.900 through 242.909 and the registered security-based swap data repository's policies and procedures thereunder.

Notes, amendments, and revision history

Amendments

[80 FR 14728, Mar. 19, 2015, as amended at 81 FR 53655, Aug. 12, 2016]

Source

Source: 80 FR 14728, Mar. 19, 2015, unless otherwise noted.

Authority

Source

Source: 62 FR 544, Jan. 3, 1997, unless otherwise noted.

Amendments

[80 FR 14728, Mar. 19, 2015, as amended at 81 FR 53655, Aug. 12, 2016]

§242.908. Cross-border matters.

17 C.F.R. § 242.908

(a)

Application of Regulation SBSR to cross-border transactions.

(1)

A security-based swap shall be subject to regulatory reporting and public dissemination if:

(i)

There is a direct or indirect counterparty that is a U.S. person on either or both sides of the transaction;

(ii)

The security-based swap is accepted for clearing by a clearing agency having its principal place of business in the United States;

(iii)

The security-based swap is executed on a platform having its principal place of business in the United States;

(iv)

The security-based swap is effected by or through a registered broker-dealer (including a registered security-based swap execution facility); or

(v)

The transaction is connected with a non-U.S. person's security-based swap dealing activity and is arranged, negotiated, or executed by personnel of such non-U.S. person located in a U.S. branch or office, or by personnel of an agent of such non-U.S. person located in a U.S. branch or office.

(2)

A security-based swap that is not included within paragraph (a)(1) of this section shall be subject to regulatory reporting but not public dissemination if there is a direct or indirect counterparty on either or both sides of the transaction that is a registered security-based swap dealer or a registered major security-based swap participant.

(b)

Limitation on obligations. Notwithstanding any other provision of §§ 242.900 through 242.909, a person shall not incur any obligation under §§ 242.900 through 242.909 unless it is:

(1)

A U.S. person;

(2)

A registered security-based swap dealer or registered major security-based swap participant;

(3)

A platform;

(4)

A registered clearing agency; or

(5)

A non-U.S. person that, in connection with such person's security-based swap dealing activity, arranged, negotiated, or executed the security-based swap using its personnel located in a U.S. branch or office, or using personnel of an agent located in a U.S. branch or office.

(c)

Substituted compliance—

(1)

General. Compliance with the regulatory reporting and public dissemination requirements in sections 13(m) and 13A of the Act (15 U.S.C. 78m(m) and 78m-1), and the rules and regulations thereunder, may be satisfied by compliance with the rules of a foreign jurisdiction that is the subject of a Commission order described in paragraph (c)(2) of this section, provided that at least one of the direct counterparties to the security-based swap is either a non-U.S. person or a foreign branch.

(2)

Procedure.

(i)

The Commission may, conditionally or unconditionally, by order, make a substituted compliance determination regarding regulatory reporting and public dissemination of security-based swaps with respect to a foreign jurisdiction if that jurisdiction's requirements for the regulatory reporting and public dissemination of security-based swaps are comparable to otherwise applicable requirements. The Commission may, conditionally or unconditionally, by order, make a substituted compliance determination regarding regulatory reporting of security-based swaps that are subject to § 242.908(a)(2) with respect to a foreign jurisdiction if that jurisdiction's requirements for the regulatory reporting of security-based swaps are comparable to otherwise applicable requirements.

(ii)

A party that potentially would comply with requirements under §§ 242.900 through 242.909 pursuant to a substituted compliance order or any foreign financial regulatory authority or authorities supervising such a person's security-based swap activities may file an application, pursuant to the procedures set forth in § 240.0-13 of this chapter, requesting that the Commission make a substituted compliance determination regarding regulatory reporting and public dissemination with respect to a foreign jurisdiction the rules of which also would require reporting and public dissemination of those security-based swaps.

(iii)

In making such a substituted compliance determination, the Commission shall take into account such factors as the Commission determines are appropriate, such as the scope and objectives of the relevant foreign regulatory requirements, as well as the effectiveness of the supervisory compliance program administered, and the enforcement authority exercised, by the foreign financial regulatory authority to support oversight of its regulatory reporting and public dissemination system for security-based swaps. The Commission shall not make such a substituted compliance determination unless it finds that:

(A)

The data elements that are required to be reported pursuant to the rules of the foreign jurisdiction are comparable to those required to be reported pursuant to § 242.901;

(B)

The rules of the foreign jurisdiction require the security-based swap to be reported and publicly disseminated in a manner and a timeframe comparable to those required by §§ 242.900 through 242.909 (or, in the case of transactions that are subject to § 242.908(a)(2) but not to § 242.908(a)(1), the rules of the foreign jurisdiction require the security-based swap to be reported in a manner and a timeframe comparable to those required by §§ 242.900 through 242.909);

(C)

The Commission has direct electronic access to the security-based swap data held by a trade repository or foreign regulatory authority to which security-based swaps are reported pursuant to the rules of that foreign jurisdiction; and

(D)

Any trade repository or foreign regulatory authority in the foreign jurisdiction that receives and maintains required transaction reports of security-based swaps pursuant to the laws of that foreign jurisdiction is subject to requirements regarding data collection and maintenance; systems capacity, integrity, resiliency, availability, and security; and recordkeeping that are comparable to the requirements imposed on security-based swap data repositories by the Commission's rules and regulations.

(iv)

Before issuing a substituted compliance order pursuant to this section, the Commission shall have entered into memoranda of understanding and/or other arrangements with the relevant foreign financial regulatory authority or authorities under such foreign financial regulatory system addressing supervisory and enforcement cooperation and other matters arising under the substituted compliance determination.

(v)

The Commission may, on its own initiative, modify or withdraw such order at any time, after appropriate notice and opportunity for comment.

Notes, amendments, and revision history

Amendments

[80 FR 14728, Mar. 19, 2015, as amended at 81 FR 53655, Aug. 12, 2016]

Source

Source: 80 FR 14728, Mar. 19, 2015, unless otherwise noted.

Authority

Source

Source: 62 FR 544, Jan. 3, 1997, unless otherwise noted.

Amendments

[80 FR 14728, Mar. 19, 2015, as amended at 81 FR 53655, Aug. 12, 2016]

§242.909. Registration of security-based swap data repository as a securities information processor.

17 C.F.R. § 242.909

A registered security-based swap data repository shall also register with the Commission as a securities information processor on Form SDR (§ 249.1500 of this chapter).

Notes, amendments, and revision history

Source

Source: 80 FR 14728, Mar. 19, 2015, unless otherwise noted.

Authority

Source

Source: 62 FR 544, Jan. 3, 1997, unless otherwise noted.