CFTC Swap Data Reporting: Parts 43 and 45 Deadlines, Fields and SDRs
CFTC swap data reporting comprises two distinct obligations. Part 43 applies to publicly reportable swap transactions and their transaction and pricing data, while Part 45 governs regulatory swap-data recordkeeping and reporting. Not every swap is publicly reportable under Part 43, and regulation 45.11 provides for direct reporting to the CFTC where no swap data repository (SDR) accepts data for an asset class. Under 17 CFR Part 43, swap transaction and pricing data goes to the SDR as soon as technologically practicable after execution so that it can be published; under 17 CFR Part 45, the full regulatory record follows, and where a swap dealer reports an off-facility swap that record is due by the end of the next business day after the execution date. That pairing is the backbone of CFTC swap data reporting, and its current form dates from the CFTC’s November 2020 amendments, which had a compliance date of 25 May 2022.
The operational stakes sit in three rules. A submission that fails the SDR’s validation has not discharged the obligation to report. An error has to be corrected within seven business days of discovery, and, for an error discovered or discoverable during a required verification run, discovery is deemed to be the start of that run. And the party that owes all of this is chosen by a status hierarchy in which trade size plays no part. The CFTC and the SEC asked in June 2026 whether the framework should be simplified; until a change is adopted, the rule text and the 2023 technical specification govern.
Related reading: EMIR Reporting Explained
Legal basis for CFTC swap data reporting: CEA section 2(a)(13) and Parts 43 and 45
The statutory hook is section 2(a)(13) of the Commodity Exchange Act (CEA), added by section 727 of the Dodd-Frank Act. It requires each swap, cleared or uncleared, to be reported to a registered SDR, and it authorises the CFTC to make swap transaction and pricing data available to the public. The CFTC implemented those two mandates through two rule sets published in January 2012: real-time public reporting in Part 43 (77 FR 1182, 9 January 2012) and swap data recordkeeping and reporting in Part 45 (77 FR 2136, 13 January 2012). Part 46 covers pre-enactment and transition swaps, and Part 49 sets the SDR’s own duties, including the data validation procedures in regulation 49.10 and the verification mechanism in regulation 49.11.
The text in force today comes from three final rules published on 25 November 2020: Real-Time Public Reporting Requirements (85 FR 75422), Swap Data Recordkeeping and Reporting Requirements (85 FR 75503) and Certain Swap Data Repository and Data Reporting Requirements (85 FR 75601). The CFTC’s rulemaking pages give 25 January 2021 as the effective date of the Part 43 and Part 45 rules. The general compliance date was 25 May 2022, and the Part 43 amendments to the block and cap size rules in regulations 43.4(h) and 43.6 carried a later compliance date of 25 May 2023. In their 2026 joint request for comment, the CFTC and SEC describe that round as an effort to reduce the number of data elements and to address the lack of standardisation across SDRs that followed from the discretion SDRs had over what swap data was reported.
Both parts push the field-level detail out of the Code of Federal Regulations. Regulations 43.3(d)(1) and 45.13(a)(1) require the data elements listed in Appendix A to Part 43 and Appendix 1 to Part 45 to be reported in the form and manner set by a technical specification that Commission staff publish under delegated authority (regulations 43.7 and 45.15). Version 3.2 of that specification, dated 1 March 2023, adopted the unique product identifier and carried an implementation deadline of 29 January 2024. The CFTC and SEC used it as their reference point for the CFTC’s data element count in June 2026.
One definition widens the population. Part 45 defines “swap” to include any foreign exchange forward and any foreign exchange swap as defined in CEA sections 1a(24) and 1a(25), so FX forwards and FX swaps sit inside the Part 45 recordkeeping and reporting perimeter by definition.
Who must report under Parts 43 and 45: venues, clearing houses and the regulation 45.8 hierarchy
The duty attaches to the execution venue first and to the counterparties second. For a swap executed on or pursuant to the rules of a swap execution facility (SEF) or designated contract market (DCM), the venue reports the Part 43 swap transaction and pricing data and the Part 45 creation data (regulations 43.3(a)(2) and 45.3(a)). For a clearing swap, the derivatives clearing organization (DCO) that is a counterparty is the reporting counterparty under Part 45 (regulation 45.8(i)). Under Part 43, the DCO has the reporting obligation only where that clearing swap is a publicly reportable swap transaction (regulation 43.3(a)(5)). Everything else runs through the counterparty hierarchy in regulation 45.8, which also decides who reports continuation data for venue-executed swaps.
| Situation | Part 45 reporting counterparty |
|---|---|
| Executed on or pursuant to SEF or DCM rules | Venue files creation data; continuation data goes to the party selected under regulation 45.8 |
| Clearing swap | The DCO that is a party (45.8(i)) |
| Off-facility, only one party is a swap dealer | The swap dealer (45.8(a)) |
| Neither party a swap dealer, only one a major swap participant (MSP) | The MSP (45.8(b)) |
| Both parties outside the SD, MSP and DCO group, only one a U.S. person | The U.S. person, overriding the financial-entity test (45.8(e)) |
| Both outside that group, only one a financial entity under CEA section 2(h)(7)(C) | The financial entity (45.8(c)), unless 45.8(e) applies |
| Both swap dealers; both MSPs where neither is a swap dealer; or both non-SD/MSP/DCO counterparties with the same financial-entity status | The parties agree; for off-facility swaps, as one term of the swap (45.8(d)) |
| Neither party a U.S. person, but executed on a SEF or DCM, otherwise executed in the United States, or cleared by a DCO | The parties agree (45.8(f)) |
The overrides in regulations 45.8(e) and (f) must be applied before the default selections in paragraphs (a) to (d). In particular, regulation 45.8(f) requires the counterparties to agree who reports when neither is a U.S. person and the swap is executed on a SEF or DCM, otherwise executed in the United States, or cleared by a DCO. This override applies even where one counterparty is a swap dealer or major swap participant, subject to the separate clearing-swap rule in regulation 45.8(i). Where a non-U.S. financial entity that is not a swap dealer faces a U.S. commercial end-user, regulation 45.8(e) makes the U.S. end-user the reporting counterparty, even though the financial-entity test in 45.8(c) points the other way. Teams that assume the financial firm always reports will build the wrong onboarding rule for exactly this pairing.
Part 43 carries its own, shorter hierarchy for off-facility swaps in regulation 43.3(a)(3). A lone swap dealer or MSP reports, a swap dealer outranks an MSP, and in every other pairing the parties designate the reporting counterparty before execution. The whole list applies “unless otherwise agreed to by the parties prior to execution”, and it has no financial-entity or U.S.-person tie-breaker. Regulation 45.10 then sends the Part 43 and Part 45 data for one swap to a single SDR. Firms should settle both answers in the same onboarding step, because the two lists can diverge for pairs of end-users.
The non-reporting side has duties of its own. It must tell the reporting counterparty about any error it finds as soon as technologically practicable and no later than three business days after discovery, or tell the SEF or DCM if it does not know who the reporting counterparty is (regulations 43.3(e)(2) and 45.14(a)(2)). On a SEF or DCM, each order must carry the participant’s LEI and yes/no indicators for swap dealer, MSP, financial entity and U.S. person status, plus any clearing exception election and allocation details, so that the venue can identify the reporting counterparty (regulation 45.8(h)).
Reporting duties under Parts 43 and 45 apply whatever the trade size, and size affects only Part 43 public dissemination: block and large notional treatment, notional rounding and cap sizes. Identification runs at legal-entity level through the LEI. The cross-border hooks written into the hierarchy are the U.S.-person tests in regulation 45.8(e) and (f), and the text of Parts 43 and 45 sets no separate rule for branches.
Two Division of Market Oversight no-action letters change the practical answer for specific populations. CFTC Letter No. 25-16 (23 June 2025) extends a position for non-U.S. swap dealers and MSPs established in Australia, Canada, the European Union, Japan, Switzerland or the United Kingdom that are not part of a group whose ultimate parent is a U.S. swap dealer, U.S. MSP, U.S. bank, U.S. financial holding company or U.S. bank holding company. It covers the Part 45 and Part 46 reporting requirements for their swaps with non-U.S. counterparties that are not guaranteed or conduit affiliates of a U.S. person, excludes the recordkeeping requirements in regulations 45.2, 45.6, 46.2 and 46.4 and SEF and DCM reporting of venue-executed swaps, and lasts until the earlier of 30 days after a Commission comparability determination for the relevant jurisdiction and the compliance date of Commission action on those obligations. CFTC Letter No. 25-18 (9 July 2025) covers counterparties clearing through clearing houses that operate under a Commission exemptive order or a Division of Clearing and Risk no-action letter, which are not DCOs for Part 45 purposes: the Division will not recommend enforcement against those counterparties for failing to report continuation data on the original swap once the clearing house accepts it, to report creation and continuation data on the resulting clearing swaps, or to generate UTIs for those swaps, provided they give the clearing house the information its clearing agreement requires. Like the error letters discussed below, each binds only the Division.
What the report contains: Appendix A, Appendix 1 and up to 128 data elements
Appendix A to Part 43 lists the swap transaction and pricing data elements that feed public dissemination. Appendix 1 to Part 45 lists the regulatory swap data elements, reported in two streams: required swap creation data at execution, and required swap continuation data afterwards. Regulation 45.1 defines continuation data as all life-cycle-event data plus all valuation, margin and collateral data for the swap. The CFTC and SEC put the total at up to 128 data elements in their June 2026 joint request for comment.
The technical specification turns the appendices into one table. Each row numbers a data element, marks its source as “CDE” (taken from the CPMI-IOSCO critical data elements guidance) or “CFTC”, and gives its category, definition, format and allowable values. The right-hand columns carry the validation logic: which of the five asset classes (credit, interest rates, FX, equity and commodities) need the element, the Part 45 SDR validation rule, whether the element belongs in end-of-day valuation or collateral reports, whether it is reported for Part 43, and the Part 43 dissemination rule. Appendix F of the specification sets out the valid combinations of action type and event type, with worked examples of how each life-cycle event is reported in transaction and end-of-day reports.
Identifiers: UTI, LEI and UPI
Every swap carries a unique transaction identifier (UTI) of up to 52 characters, built only from upper-case letters A to Z and digits 0 to 9, which starts with the LEI of the entity that generated it (regulations 45.1 and 45.5). The generator follows the reporting route: the SEF or DCM for venue trades, a financial-entity reporting counterparty for its off-facility trades, the DCO for clearing swaps, and, for a reporting counterparty that is neither a financial entity nor an SD, MSP or DCO, either itself or the SDR on request. A third-party service provider that generates UTIs uses its own LEI as the prefix (regulation 45.5(g)).
Counterparties are identified by LEIs issued under ISO 17442 (regulation 45.6). A financial-entity reporting counterparty facing an eligible counterparty that has no LEI must use best efforts to have one assigned before reporting; if that fails, it must promptly give the Commission the counterparty’s identity and contact information. For natural persons acting as private individuals, the specification has the reporting counterparty submit its own LEI followed by a unique identifier that it assigns and maintains for that person, and neither value is publicly disseminated.
Products are identified by the unique product identifier (UPI) issued by the Derivatives Service Bureau. The CFTC’s designation order, published on 24 February 2023 (88 FR 11790), covers the credit, equity, FX and interest rate asset classes and set a compliance date of 29 January 2024. Commodity swaps keep reporting the product-related data elements each SDR specifies until the Commission designates a UPI for that asset class, and the CFTC’s July 2026 Part 20 order describes that extension as forthcoming. The EU treatment of the same identifier for OTC derivatives transparency is covered in our note on the ESMA transparency manual and UPIs for OTC derivatives.
Formats and conventions
The format conventions are mechanical and unforgiving. Timestamps take the form YYYY-MM-DDThh:mm:ssZ and are expressed in Coordinated Universal Time. Amounts in the Num(25,5) format allow up to 25 numeric characters with at most five after the decimal point, and a value with more decimals is rounded half-up. Currencies use ISO 4217 codes, which is why offshore renminbi is reported as CNY with the settlement location element set to HK; CNH is a market convention, and the specification says it should not be reported.
Direction is reported through the Buyer/Seller or the Payer/Receiver elements, chosen by instrument type. The CFTC did not adopt the alternative Direction 1/Direction 2 approach offered in the CDE guidance, and a single report should never carry both pairs. Notional amounts travel with a separate notional currency element, and sign and allowable-value rules are defined element by element in the specification. A multi-leg product reports leg-based elements separately for each leg, for example a leg 1 and a leg 2 notional amount. Where one element has to carry several values, such as the clearing swap UTIs that result from clearing, the specification leaves the delimiter to the SDR, and notional amount schedules follow the SDR’s implementation procedures.
Valuation data covers the daily mark required by CEA section 4s(h)(3)(B)(iii) and, where it applies, regulation 23.431. Collateral data covers money, securities or other property posted or received to margin, guarantee or secure a swap. The specification’s collateral elements cover initial margin posted and collected before and after haircuts, variation margin posted and collected before haircuts, and the initial and variation margin collateral portfolio codes.
What the public sees
The SDR publishes Part 43 data without disclosing the parties or making them identifiable (regulation 43.4(c)). It rounds notional amounts on the sliding scale in regulation 43.4(f), so that, for example, an amount equal to or greater than one million but less than 100 million is rounded to the nearest million, and it caps the published notional at the cap size for the swap category. For interest rate, credit, equity and FX swaps the actual underlying asset is published. For other commodity swaps that are not tied to a contract listed in Appendix B to Part 43 or executed on a SEF or DCM, delivery and pricing points are generalised to the regions in Appendix E.
Deadlines for Part 43 and Part 45 reports: event-driven clocks and daily streams
Every clock in Parts 43 and 45 starts from an event: execution, a life-cycle event, or each business day for valuation and margin, with no reference date and no monthly or quarterly remittance calendar. The first report for a swap therefore falls due from its execution date, and the daily streams continue for as long as the swap stays open.
| Report | Who | Deadline |
|---|---|---|
| Part 43 swap transaction and pricing data | SEF or DCM; off-facility reporting counterparty; DCO for a clearing swap that is a publicly reportable swap transaction (43.3(a)(5)) | As soon as technologically practicable after execution (43.3(a)) |
| Part 43 data for a post-priced off-facility swap | Reporting counterparty | Earlier of price determination and 11:59:59 p.m. Eastern time on the execution date; undetermined items follow once known (43.3(a)(4)) |
| Part 45 creation data, venue swap | SEF or DCM | End of the next business day after the execution date (45.3(a)) |
| Part 45 creation data, off-facility swap | SD, MSP or DCO reporting counterparty | End of the next business day after the execution date (45.3(b)(1)) |
| Part 45 creation data, off-facility swap | Any other reporting counterparty | End of the second business day after the execution date (45.3(b)(2)) |
| Life-cycle-event data | SD, MSP or DCO reporting counterparty | End of the next business day after the event; a corporate event of the non-reporting counterparty by the end of the second business day (45.4(c)(1)(i)) |
| Life-cycle-event data | Any other reporting counterparty | End of the second business day after the event (45.4(c)(1)(ii)) |
| Continuation data for original swaps, including terminations | DCO that accepted the swap for clearing | End of the next business day after the event (45.4(b)) |
| Valuation data | SD, MSP or DCO reporting counterparty | Each business day (45.4(c)(2)(i)) |
| Collateral data | SD or MSP reporting counterparty | Each business day (45.4(c)(2)(ii)) |
Two gaps in that table are deliberate. Reporting counterparties outside the SD, MSP and DCO group have no recurring valuation or collateral stream under regulation 45.4(c)(2), and a DCO reporting counterparty reports daily valuation data but has no collateral line in that paragraph.
“Business day” means any day other than a Saturday, Sunday or legal holiday in the location of the party reporting the data (regulations 43.2 and 45.1). On my reading of that definition, a swap dealer that executes an off-facility swap on a Friday and reports from New York owes Part 45 creation data by the end of the following Monday, unless that Monday is a legal holiday in New York.
Allocated trades add an intermediate clock. The agent must tell the reporting counterparty who the actual counterparties are as soon as technologically practicable and no later than eight business hours after execution. The reporting counterparty then creates a UTI for each post-allocation swap and reports each one to the same SDR as the initial swap between itself and the agent (regulations 45.3(c) and 45.5(e)).
The correction and verification cycle runs on a timetable of its own. Errors must be corrected as soon as technologically practicable and in all cases within seven business days after discovery (regulations 43.3(e)(1)(i) and 45.14(a)(1)(i)). Verification against the SDR’s records is due at least once every thirty calendar days for swap dealers, MSPs and DCOs, and at least once each calendar quarter, with at least two calendar months between checks, for other reporting counterparties (regulation 45.14(b)(4)). An error that a verification run could have caught counts as discovered from the moment that run began, so the seven-day window can open before anyone has looked at the break.
Public dissemination delays for blocks and large notional off-facility swaps
The SDR releases ordinary trades as soon as technologically practicable. Blocks and large notional off-facility swaps are held back for a fixed period that starts at execution, and the SDR must release them precisely when it ends (regulation 43.5):
- Block trades executed on or pursuant to the rules of a SEF or DCM: 15 minutes.
- Large notional off-facility swaps subject to the mandatory clearing requirement: 15 minutes where at least one party is an SD or MSP, one hour where neither is.
- Large notional off-facility swaps outside mandatory clearing with at least one SD or MSP party: 30 minutes in the interest rate, credit and FX classes, two hours for other commodities.
- Large notional off-facility swaps outside mandatory clearing where neither party is an SD or MSP: 24 business hours.
Submission: one SDR per swap, the SDR’s data standards and third-party reporting
The first reporter picks the SDR: the SEF or DCM for venue trades, otherwise the reporting counterparty selected under regulation 45.8 (regulation 45.3(f)). From then on, all Part 43 and Part 45 data for that swap goes to the same SDR (regulation 45.10), and the first reporter must tell the relevant parties which SDR it is using. A SEF or DCM tells both counterparties, and any DCO that will clear the swap, as soon as technologically practicable after execution; a reporting counterparty on an off-facility swap that is not a clearing swap tells the other counterparty and any such DCO on the same timetable; and a DCO tells its counterparty to each clearing swap as soon as technologically practicable after accepting the original swap for clearing, or after executing a clearing swap that does not replace an original swap (regulation 45.10(a)(1), (b)(1) and (c)(1)). The CFTC’s Data Repositories page links to a search tool for registered SDRs.
The CFR leaves the transmission format to the SDR. Regulations 43.3(d)(3) and 45.13(a)(3) require reporters to use the facilities, methods or data standards that the SDR provides or requires, and regulation 45.1 defines electronic reporting as data normalised in data elements under the SDR’s standard, excluding an image of a document or a text file. Regulation 45.15 lets Commission staff permit or require a particular standard and names FIX, FpML and ISO 20022 as examples. File naming, message schemas and resubmission follow each SDR’s own procedures, to which the technical specification repeatedly defers; neither the CFR text nor the specification sets a CFTC-wide convention for them. The December 2023 proposed version 3.3 of the specification would allow lower-case Boolean values alongside the “True” and “False” that version 3.2 specifies, “until the ISO 20022 message standard is adopted by CFTC”, which indicates that no ISO 20022 mandate was in place when it was drafted.
Moving a swap’s reporting to another SDR requires at least five business days’ notice to the other counterparty, the current SDR and the new SDR, quoting the UTI and the switch date. The change is then reported as a life-cycle event to both SDRs on the same day under the same UTI (regulation 45.10(d)).
Delegation leaves liability where it was. A reporting counterparty, SEF, DCM or DCO may contract with a third-party service provider to help it report, while “remaining fully responsible for reporting” (regulations 43.3(a)(7) and 45.9). If no SDR accepts swaps in an asset class, the data goes to the Commission itself, in a format and at times the Commission announces (regulation 45.11). The specification directs questions on format, content and transmission to CFTCSwapsTechSpec@CFTC.gov.
Validation: SDR acceptance messages, rejection triggers and the verification cycle
Each SDR validates every Part 43 and Part 45 submission against its data validation procedures and tells the submitter whether the report passed, as soon as technologically practicable (regulations 43.3(f) and 45.13(b)). The consequence of a failure is written into the rule. A reporter whose submission fails validation “has not satisfied its obligation” until it submits a compliant report, and for Part 45 the compliant report still has to arrive within the deadline in regulation 45.3 or 45.4. Once that deadline passes, a rejected file waiting in a queue is a missed deadline.
The specification assigns every element one of four codes for each report type (transaction, collateral and valuation): M for mandatory, C for conditionally mandatory, O for optional and NR for not required. Its own text names the triggers that lead to rejection:
- A value outside an element’s list of allowable values is to be rejected by the SDR’s validation.
- Where an element calls for an LEI, the SDR must also check that the code is published by GLEIF, so a mistyped code in the right format still fails.
- Conditional elements depend on other fields. “Central counterparty” is required when “Cleared” is Y and must then match “Counterparty 1 (reporting counterparty)”, and “Clearing account origin” (HOUS or CLIE) is required only for cleared swaps.
- “Cleared” takes Y, N or I, where I marks an original swap that is intended to be submitted for clearing.
- For the TERM, PRTO and EROR action types an SDR may accept a reduced set of elements; every other action type requires the full Part 43 and Part 45 set.
One CFTC figure indicates how often reporting entities notify staff that they expect to be unable to correct errors within the prescribed deadline. In July 2025, Division of Market Oversight staff wrote that the Division of Data was receiving approximately 150 notifications a month from SEFs, DCMs and reporting counterparties that anticipated being unable to correct errors within the required period, against an estimate of about 1,729 a year in the 2020 rulemaking (CFTC Letter No. 25-25).
Verification is the reconciliation half of validation. Each reporting counterparty must verify the completeness and accuracy of data for every open swap it reported or was required to report, including swaps omitted from SDR reporting. Under regulation 45.14(b), it must reconcile accessible SDR records with its internal books using the SDR’s verification mechanism, maintain a log of discovered errors and corrections, and follow the SDR’s verification procedures, including where a third party performs the check. The rule defines an error to include incorrect data, data that differs from a party’s books, data never reported, and a swap still shown as open after it has ended, and it presumes an error whenever the data an SDR maintains and disseminates is incomplete or inaccurate (regulation 45.14(c)). Data a reporting counterparty is not permitted to access, for example under regulation 49.17, falls outside the verification duty.
Caveats and interactions: staff relief, cross-border UTIs, exclusions and Part 20
The 2025 no-action letters on errors
Two Division of Market Oversight letters now shape how the error rules are enforced. Neither changes the rule text, and each binds only the issuing division.
CFTC Letter No. 25-25 (31 July 2025) says the division will not recommend enforcement against a reporting counterparty that skips the notification due within 12 hours of deciding it cannot correct an error in time, provided that, when it first discovers and assesses the error, it reasonably determines that the affected trades do not exceed five percent of its open swaps in that asset class for which it is the reporting counterparty. The five percent is measured on the open-swap population used for its regulation 45.14 verification. The letter is written for reporting counterparties, and the position expires on the compliance date of any Commission action on the notification obligations.
CFTC Letter No. 25-43 (10 December 2025), issued at ISDA’s request, establishes a Division of Market Oversight no-action position for reporting counterparties concerning specified error-correction obligations. The relief described below does not extend to SEFs or DCMs:
- Part 45, swaps no longer open: no enforcement recommendation where the swap had ended before the effective date of the latest Part 45 rule change affecting the content or format of the data, or of the latest technical specification for its asset class, or had ended two years before the error was discovered. For other ended swaps, corrections are still expected for LEI, UTI and Part 43 Appendix A elements and, for commodity swaps, for the product data reported in place of a UPI.
- Part 45, open swaps: only the most recently reported data needs correcting.
- Part 43: only Appendix A elements, and only errors that occurred after the later of the latest Part 43 rule or specification change and the date one year before discovery.
Cross-border UTIs, mixed swaps and multi-asset swaps
Where a swap is also reportable in another jurisdiction with an earlier regulatory reporting deadline, regulation 45.5(h) requires the UTI generated under that jurisdiction’s rules to be used in CFTC recordkeeping and reporting as well. For a swap that is also reportable under EMIR, comparing the two deadlines decides whose UTI rules apply; our EMIR reporting guide covers the EU side. A mixed swap, part CFTC swap and part SEC security-based swap, must be reported to an SDR and to an SEC-registered security-based SDR, or to one repository registered with both, under the same UTI. A multi-asset swap goes to a single SDR that accepts its primary asset class (regulation 45.3(d) and (e)).
Swaps that never reach the public tape
Part 43’s definition of a publicly reportable swap transaction keeps some executed swaps off the tape. Swaps between wholly owned subsidiaries of the same parent, portfolio compression exercises, and swaps a DCO enters into while managing a clearing member’s default are given as examples of trades that are not at arm’s length, and a mirror swap in a prime brokerage chain is excluded outright (regulations 43.2 and 43.3(a)(6)). Those carve-outs belong to Part 43. Regulation 45.3 applies its creation-data duty to each swap and the Part 45 text carries no parallel list, so any Part 45 relief for those populations has to come from a staff letter or another rule, and the CFTC staff letter index is the place to check.
Block trades and large notional elections
Block treatment is an election, and the parties have to qualify for it. Parties to a block trade must be eligible contract participants, although a DCM may allow certain commodity trading advisors, investment advisers and comparable foreign persons to transact blocks for customers who are not eligible contract participants, with the customer’s prior written instruction or consent (regulation 43.6(j)).
Orders for different accounts may be aggregated to meet the minimum block size or cap size only by the persons specified in regulation 43.6(i)(6), where the aggregated orders are executed as one swap and reported as a block trade or large notional off-facility swap, as applicable. If the swap is listed for trading on a SEF or DCM, the aggregation must occur on a SEF or DCM. The reporting counterparty notifies the SEF or DCM of a block election, which passes it on to the SDR, and notifies the SDR directly of a large notional off-facility election (regulation 43.6(h)). Equity swaps never qualify (regulation 43.6(e)).
Minimum block sizes and cap sizes are recalculated by Commission staff at least once each calendar year, published on the CFTC website, and effective on the first day of the second month after publication unless the website says otherwise (regulations 43.4(h) and 43.6(g)). The set the Division of Data published on 23 May 2024, built from calendar-2023 data, took effect on 7 October 2024. The CFTC’s real-time reporting page carries each published set.
Part 20 large trader reporting and event contracts
The CFTC’s order sunsetting large trader reporting for physical commodity swaps took effect on 21 July 2026 (91 FR 45638). Clearing organizations, clearing members and swap dealers no longer file the daily and event-based Part 20 position reports, because the Commission found that the SDR framework under Parts 43, 45 and 49 now gives it open-swap position data; Part 20’s recordkeeping and special-call provisions stay in force as a transitional bridge pending the UPI for the other commodity asset class, after which the Commission intends to reassess them. The order shifts surveillance of physical commodity swap positions toward SDR-based data under Part 45.
Fully collateralised binary and variable payout event contracts run on a separate track. CFTC Letter No. 26-14 (13 May 2026), from the Division of Market Oversight and the Division of Clearing and Risk, established a conditional staff no-action position covering the entities identified in its Appendix, including beneficiaries of earlier letters. Additional DCMs and DCOs wishing to rely on equivalent relief must request and obtain a no-action position from the Divisions; listing a qualifying event contract does not automatically confer relief. The position expires on the compliance date of any final Commission action addressing the matter. The CFTC then proposed a futures-style reporting framework for those contracts on 1 July 2026 (91 FR 40102).
Records, retention and the notification address
Swap records must be kept for the life of the swap and at least five years after final termination (regulation 45.2(c)). SEFs, DCMs, DCOs, swap dealers and MSPs must keep them readily accessible through real-time electronic access for the life of the swap and two years after, and retrievable within three business days for the rest of the period; other counterparties must be able to retrieve theirs within five business days. Once the retention period has expired, the error-correction duty no longer applies (regulations 43.3(e)(3) and 45.14(a)(3)).
One drafting wrinkle affects the failure-to-correct notice. Part 43 directs it to the Director of the Division of Data, following a September 2024 amendment (89 FR 71812). The printed Part 45 text still names the Director of the Division of Market Oversight, because the same amendment misidentified the section and, according to the CFR editorial note, could not be incorporated. Letter 25-25 describes both notifications as going to the Division of Data, and the CFTC’s data recordkeeping page carries the swap data error correction notification form.
Changes to Parts 43 and 45: from the 2020 rewrite to the 2026 joint review
| Date | Action | Effect |
|---|---|---|
| 25 November 2020 | Final rules amending Parts 43, 45 and 49 (85 FR 75422, 75503, 75601) | Parts 43 and 45 rules effective 25 January 2021; compliance date 25 May 2022 |
| 24 February 2023 | UPI designation order (88 FR 11790) | DSB UPI for credit, equity, FX and interest rate swaps from 29 January 2024 |
| 1 March 2023 | Technical specification version 3.2 | Adopted UPI; implementation by 29 January 2024 |
| 28 December 2023 | Proposed amendments to Parts 43 and 45 (88 FR 90046), with a proposed specification version 3.3 | Proposal only; comment period reopened to 11 April 2024 |
| 23 May 2024 | Post-initial block and cap sizes from calendar-2023 data | Effective 7 October 2024 |
| 31 July 2025 | CFTC Letter No. 25-25 | Five percent threshold for error notifications |
| 10 December 2025 | CFTC Letter No. 25-43 | Narrower enforcement of error corrections |
| 13 May 2026 | CFTC Letter No. 26-14 | Conditional event contract relief from Parts 43 and 45 |
| 24 June 2026 | Joint CFTC and SEC request for comment on swap and security-based swap data reporting (91 FR 37877) | Comment deadline 24 August 2026 |
| 1 July 2026 | Proposed reporting framework for certain event contracts (91 FR 40102) | Comment deadline 31 July 2026 |
| 21 July 2026 | Order sunsetting Part 20 large trader reporting for physical commodity swaps (91 FR 45638) | Effective 21 July 2026 |
The December 2023 proposal would keep geographic masking for other commodity swaps once a UPI is designated for that class, add 19 data elements drawn from the 2023 CDE guidance and 30 CFTC-specific elements to the appendices, and introduce a “USD equivalent regulatory notional amount” element in Appendix 1 to Part 45. Version 3.3 of the specification was published with it, and its own cover labels the changes as proposed. Check the CFTC’s Part 45 rulemaking page for a final rule before treating any version 3.3 field as required.
The joint request for comment is the broader review. Its questions cover data elements of limited utility relative to their cost, combining or cutting categories such as prices, payments and transaction-related data, a materiality or de minimis threshold for correcting errors, for example in swaps that have ended, the reporting hierarchies, reference data in place of trade-by-trade fields, and the sequencing of any changes across the two agencies. It also notes that the SEC’s 2019 compliance statement, which has kept security-based swap reporting broadly aligned with CFTC practice, is scheduled to expire on 5 November 2029. A request for comment changes no obligation by itself. The EU has its own review running, covered in our note on ESMA’s transaction reporting simplification across EMIR, MiFIR and SFTR.
Frequently Asked Questions
Can a correction to a swap that matured years ago be submitted in the format that applied when it was live?
The rule leaves that to the SDR. In the 2020 rulemaking the Commission declined to require error corrections to use the SDR’s prevailing validations and technical specification, and left each SDR discretion to require them under regulation 49.10(e); Letter 25-43 repeats the point. Regulations 43.3(e)(1)(iii) and 45.14(a)(1)(iii) then require the reporter to follow that SDR’s error-correction procedures.
Does the five percent test in Letter 25-25 give more time to correct the error?
The letter addresses only the notification. The seven-business-day correction deadline in regulations 43.3(e)(1)(i) and 45.14(a)(1)(i) keeps running, and staff wrote that they still welcome a notification below the threshold where an error could significantly affect data quality for the Commission or for users of the public data.
A novation changes the counterparty but leaves the price unchanged. Which stream picks it up?
Part 45 lists a counterparty change resulting from an assignment or novation as a life-cycle event, so continuation data is due on the life-cycle clock, and regulation 45.8(g) selects the reporting counterparty for later continuation data from the two current counterparties. The Part 43 limb that covers terminations, assignments and novations requires a change in the pricing of the swap. Appendix F of the specification shows the action and event type combination to use in each stream.
Does a public holiday in our counterparty’s city move our Part 45 deadline?
Regulations 43.2 and 45.1 determine business days by reference to the location of the entity responsible for reporting the data. For venue-filed creation data, that may be the SEF or DCM; for an off-facility or continuation report, it may be the reporting counterparty. A holiday observed only where the non-reporting counterparty is located does not, by itself, extend the reporting deadline.
An equity swap is far larger than any block size. Can its publication be delayed?
Regulation 43.6(e) keeps equity swaps out of block and large notional off-facility treatment, so no time delay applies and the SDR publishes as soon as technologically practicable. The protection is the cap: regulation 43.4(h)(6) sets the cap size for the equity category at USD 250 million, the most the SDR will show as the notional.
A vendor runs our SDR reconciliation. Whose verification log is it?
The reporting counterparty’s. Regulation 45.14(b)(5) puts the log duty on each reporting counterparty, and regulation 45.14(b)(2) requires it to follow the SDR’s third-party verification procedures and to require the provider to follow them too. The vendor’s output feeds the log; the obligation stays with the reporting counterparty.
Related Articles
- EMIR Reporting Explained: the EU derivatives reporting regime, its counterparties, data fields and trade repository workflow.
- ESMA Transparency Manual: UPIs for OTC Derivatives and Tick-Size Rules: how ESMA’s transparency manual uses UPIs for OTC derivatives.
- ESMA Transaction Reporting Simplification: EMIR, MiFIR and SFTR: the EU review of overlapping transaction reporting regimes.
- Form PF Reporting: Thresholds, Deadlines and the July 2027 Form Switch: SEC private fund adviser reporting, thresholds and filing deadlines.
Key Takeaways
- Determine each counterparty’s swap-dealer and MSP status for the relevant product, together with financial-entity status, U.S.-person status, execution venue and clearing status. Apply the overrides in regulations 45.8(e) and (f), and document the required counterparty agreement wherever regulation 45.8(d) or (f) applies; agreement is not limited to cases where both counterparties share a status.
- Start the seven-business-day correction count at discovery; where the error was discovered or discoverable during a verification run, the count starts when that run began. Size the correction queue to that clock.
- Route SDR rejections into the same deadline monitoring as unreported trades; a Part 45 report counts only once a compliant version is accepted inside the regulation 45.3 or 45.4 window.
- Record the open-swap count per asset class at each verification run if the five percent test in Letter 25-25 is part of the notification policy.
- Build to technical specification version 3.2 and keep version 3.3 fields behind a switch until a final rule adopts them.
- For commodity swaps, keep the SDR-specific product fields mapped and budget for a UPI cut-over once the Commission designates a commodity UPI.
Sources and References
- 17 CFR Part 43, Real-Time Public Reporting (govinfo, most recent annual edition): https://www.govinfo.gov/link/cfr/17/43?year=mostrecent&link-type=pdf
- 17 CFR Part 45, Swap Data Recordkeeping and Reporting Requirements (govinfo, most recent annual edition): https://www.govinfo.gov/link/cfr/17/45?year=mostrecent&link-type=pdf
- CFTC, Data Recordkeeping and Reporting rulemaking page (rules, technical specification versions, error correction notification form): https://www.cftc.gov/LawRegulation/DoddFrankAct/Rulemakings/DF_17_Recordkeeping/index.htm
- CFTC, Real-Time Reporting rulemaking page (block and cap size publications): https://www.cftc.gov/LawRegulation/DoddFrankAct/Rulemakings/DF_18_RealTimeReporting/index.htm
- CFTC, Final Rule, Swap Data Recordkeeping and Reporting Requirements, 85 FR 75503 (25 November 2020): https://www.cftc.gov/LawRegulation/FederalRegister/finalrules/2020-21569.html
- CFTC, Final Rule, Incorporation of Changes in the Commission’s Administrative Structure, Remove Superfluous Verbiage, and Correct Inaccurate Text, 89 FR 71803 (4 September 2024): https://www.cftc.gov/LawRegulation/FederalRegister/finalrules/2024-18445.html
- CFTC Technical Specification, Parts 43 and 45, version 3.2 (1 March 2023): https://www.cftc.gov/media/8261/Part43_45TechnicalSpecification03012023CLEAN/download
- CFTC Technical Specification, Parts 43 and 45, version 3.3 redline (13 December 2023, proposed changes): https://www.cftc.gov/media/9926/Part43_45TechnicalSpecification12132023REDLINE/download
- CFTC, Proposed Rule, Real-Time Public Reporting Requirements and Swap Data Recordkeeping and Reporting Requirements, 88 FR 90046 (28 December 2023): https://www.cftc.gov/LawRegulation/FederalRegister/proposedrules/2023-28350.html
- CFTC Release 8659-23, designation of the DSB unique product identifier (16 February 2023): https://www.cftc.gov/PressRoom/PressReleases/8659-23
- CFTC Release 8913-24, post-initial block and cap sizes (23 May 2024): https://www.cftc.gov/PressRoom/PressReleases/8913-24
- CFTC, Final Rule, Real-Time Public Reporting Requirements, 85 FR 75422 (25 November 2020): https://www.cftc.gov/LawRegulation/FederalRegister/finalrules/2020-21568.html
- CFTC, Final Rule, Certain Swap Data Repository and Data Reporting Requirements, 85 FR 75601 (25 November 2020): https://www.cftc.gov/LawRegulation/FederalRegister/finalrules/2020-21570.html
- CFTC, Order Designating the Unique Product Identifier and Product Classification System To Be Used in Recordkeeping and Swap Data Reporting, 88 FR 11790 (24 February 2023): https://www.cftc.gov/LawRegulation/FederalRegister/final-rules/2023-03661.html
- CFTC Letter No. 25-16, Part 45 and Part 46 no-action position for certain non-U.S. swap dealers and MSPs (23 June 2025): https://www.cftc.gov/csl/25-16/download
- CFTC Letter No. 25-18, Part 45 no-action position for counterparties clearing through relief DCOs (9 July 2025): https://www.cftc.gov/csl/25-18/download
- CFTC Letter No. 25-25, swap data error correction notification (31 July 2025): https://www.cftc.gov/csl/25-25/download
- CFTC Letter No. 25-43, error correction rules (10 December 2025): https://www.cftc.gov/csl/25-43/download
- CFTC Letter No. 26-14, fully collateralized event contracts (13 May 2026): https://www.cftc.gov/csl/26-14/download
- CFTC and SEC, Joint Request for Comment on Swap and Security-Based Swap Data Reporting, 91 FR 37877 (24 June 2026): https://www.govinfo.gov/content/pkg/FR-2026-06-24/pdf/2026-12742.pdf
- CFTC, Proposed Rule, Data Reporting Requirements for Certain Event Contracts, 91 FR 40102 (1 July 2026): https://www.govinfo.gov/content/pkg/FR-2026-07-01/pdf/2026-13239.pdf
- CFTC, Order Sunsetting Certain Large Trader Reporting Requirements for Physical Commodity Swaps, 91 FR 45638 (21 July 2026): https://www.govinfo.gov/content/pkg/FR-2026-07-21/pdf/2026-14710.pdf
- CFTC, Data Repositories (registered SDR search tool): https://www.cftc.gov/IndustryOversight/DataRepositories/index.htm
Where a Parts 43 and 45 reporting control should start
An error first discovered or discoverable during a required verification run is treated as discovered when that run began; an error discovered independently triggers the correction clock upon discovery. The verification process also supplies the open-swap population relevant to the five percent notification test in Letter 25-25, and the reporting counterparty must keep a log of verifications, errors and corrections. The artifact to produce for each cycle is a verification log that pairs every break found against the SDR’s records with its correction date and its count against open swaps in that asset class, completed within thirty calendar days for a swap dealer, MSP or DCO and within the quarter for every other reporting counterparty.
Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.
