Inside Staff Letter 25-42: The §23.23 Control Plane for Cross-Border Swaps

Opening Insight

CFTC Staff Letter No. 25-42 reframes how cross-border swaps status is determined and governed.

The key change: firms can apply the 2020 §23.23 U.S. person and guarantee tests consistently across clearing, execution, Parts 45/46 reporting, and uncleared margin; the conduit‑affiliate shortcut is removed for specified scopes; and reliance on pre‑2020 representations for Group B/C is permitted with validation.

The implication is straightforward: legacy, fragmented logic is now a self‑inflicted tax—collateral drag, audit findings, onboarding delays, and P&L noise—exemplified by a $9 million IM over‑post. Precisely adopting the narrower 2020 definitions converts that tax into liquidity and control gains.

The opportunity is to replace scattered determinations with a governed classification control plane—policy‑as‑code integrated across ETRM, collateral, and reporting via APIs/events. This post lays out the cost of ignoring harmonization, the benefits of a single source of truth, and the operating model to make it real. We sequence implementation, governance, KPIs, risk controls, and the bounded role of explainable AI—anchored in live operator results (e.g., 38% of swaps re‑classified out of scope , 27% IM reduction , 42% fewer exceptions , and reporting breaks down from 31 to 9 ). With the change defined, we turn to Context and Analysis.

Costs of Ignoring Harmonization

Clinging to fragmented cross‑border status logic—when §23.23 offers a single framework—turns caution into cost. Noise compounds across desks and systems, eroding controls while tying up liquidity and people.

• IM/VM over‑posting persists—think the $9 million hit from a stale U.S. person tag—while under‑posting risk hides in misread eligibility.
• Parts 45/46 mis‑matches keep producing audit findings and rework; you forgo outcomes like shrinking monthly breaks from 31 to 9.
• Mis‑classified hedges skew P&L and clearing fees, masking true performance.
• Inconsistent status flags delay onboarding and scheduling; exceptions bounce among marketing, risk, and legal.
• Limits, IM forecasts, and stress ladders drift from reality, degrading liquidity plans.
• Status attributes diverge across ETRM, credit, collateral, and SDR gateways, multiplying reconciliations.
• Dealers dispute classifications and novations stall when your view conflicts with theirs.
• Peers modernizing under 23.23 bank gains—e.g., a 27% IM drop ($12.5 million), 42% fewer exceptions, and two FTEs freed—while you carry that drag.

Near term, this shows up as higher operating cost, slower deal cycles, and exception churn you don’t need.

Benefits of Harmonized Status

Making the 23.23 framework the single source of truth for counterparty status changes daily trading. When status

flows as a governed service into margin, clearing, and reporting, the desk runs faster, safer, and better protected on P&L and liquidity.

• Decision cycles compress as onboarding, clearing determination, and uncleared margin use the same tests, eliminating rework and stalls.
• Risk attribution tightens when status, guarantees, and trade-level obligations reconcile across ledgers and reports, reducing classification drift.
• Liquidity planning improves as exceptions drop and IM/VM forecasts reflect accurate in-scope populations.
• Collateral efficiency rises with right-sized IM/VM and less deadweight collateral tied up in mis-tagged affiliates.
• Compliance steadies with traceable determinations and harmonized Parts 45/46 reporting.

Operator result (from a live rollout): A European power marketer facing two non‑U.S. dealers re‑classified 38% of its cross‑border swaps as out of scope under the 23.23 framework. Exceptions fell 42% , IM dropped by $12.5 million (27%) with no change in VaR, and monthly reporting breaks shrank from 31 to 9 —freeing two FTEs at quarter‑end.

• Integration becomes seamless as a classification engine publishes status via ETRM integration and APIs, removing brittle logic from individual systems.
• P&L clarity grows as hedges, fees, and settlements reference the same counterparty classification engine, cutting variance and disputes.

In practice, a single source of truth under the 23.23 framework releases liquidity, retires exceptions, and gains cycle time across the book.

Unified Classification Control Plane

The strategic answer is a governed control‑plane service: counterparty classification delivered as policy‑as‑code implementing §23.23 U.S. person and guarantee. It becomes the single source of truth, propagating determinations via APIs/events across onboarding, clearing determination, uncleared IM/VM, and Parts 45/46 reporting. This operating model replaces brittle logic and aligns decisions front to back.

• Rules as software and governance: Encode the §23.23 U.S. person and guarantee tests as versioned rules with automated tests and attestation trails.
• Event/API-driven propagation: Publish status changes as events/APIs into ETRM, collateral, and SDR gateways so IM/VM forecasts, clearing flags, and reporting fields update in near real time.
• Conduit affiliate removal and validated reps: Retire the conduit affiliate heuristic and rely on pre‑2020 reps for Group B/C only with freshness validation and evidence.
• Data lineage and decision linkage: Tie each determination to margin, clearing, and reporting actions, with lineage back to documents and rules for audit and reconciliation.
• Measured impact on liquidity and exceptions: In a live rollout, 38% of cross‑border swaps moved out of scope; exceptions fell 42% ; IM dropped

$12.5 million (27%) with no VaR change; reporting breaks fell from 31 to 9—freeing two FTEs.

Arcelian Architecture and Operating Model

Arcelian turns the 23.23 framework into a governed control plane that standardizes counterparty status and drives margin, clearing, and reporting. The approach encodes U.S. person and guarantee tests as policy‑as‑code, integrates with ETRM and collateral, and delivers audit‑ready lineage so leaders can reduce exceptions and collateral drag without disrupting the desk.

Architecture: Control Plane and Services

• Policy‑as‑code implements 17 C.F.R. §23.23 U.S. person/guarantee and conduit affiliate removal as versioned rules with automated tests and attestation trails.
• A counterparty classification engine/API acts as the control plane, writing determinations to a unified counterparty master with full lineage to documents and rules.
• Determinations flow to onboarding, clearing determination, uncleared IM/VM, Parts 45/46 reporting, and finance so every control reads the same truth.

ETRM Integration and Propagation

• Event‑driven integration publishes status changes to ETRM, collateral/credit, SDR gateways, and risk engines, eliminating manual overrides.
• Changes update IM forecasts, clearing flags, and reporting in near real time; outputs route to CCP/SEF/SD communication where applicable.
• ETRM adapters and event brokers ensure determinations propagate consistently across front‑, middle‑, and back‑office workflows.

Governance, Data Model, and KPIs

• System of record : the counterparty master maintained by the classification engine, with lineage and reconciliations against SD/SE views.
• Rule governance : Legal sets policy, Engineering codes rules, Compliance approves exceptions; rules are versioned and test‑backed with attestation.
• KPIs (board‑level language): exceptions rate, IM reduction, and reporting breaks; operator results include 38% re‑classification out of scope, 42% fewer exceptions, $12.5 million (27%) IM reduction , and monthly reporting breaks down from 31 to 9, freeing two FTEs.

Decision Linkages and Sequence

• Link outcomes to actions: clearing determination, uncleared margin eligibility, Parts 45/46 reporting, and SEF execution where MAT rules apply.
• Sequence to implement: (1) Normalize definitions and roles (apply §23.23; retire conduit affiliate logic). (2) Connect to decisions (wire onboarding, clearing, IM/VM, reporting). (3) Industrialize propagation (APIs/events to ETRM, collateral, SDR).
• This quarter: codify policy‑as‑code and make the classification engine the single system of record; field notes—start with a golden counterparty master, remove conduit affiliate heuristics, and dry‑run reclassification scenarios before cutover.

Human and Org Changes

• RACI : Legal sets policy; Engineering codes the rules; Compliance approves exceptions; the engine writes to the counterparty master consumed by all controls.
• Front‑office

• Enablement: traders and schedulers see status, guarantees, and obligations at the point of decision to avoid rework and disputes.
• Change management and audit: retire dual3definition flows; maintain an audit narrative linking determinations to 23.23 logic, Parts 45/46, and validated reliance on pre2020 reps; document owners, assign names and dates.
• Trade3offs and risk controls:
  • The 2020 definitions are narrowermisapplication can under or overcollateralize; scenario controls reforecast margin, limits, and liquidity before switching logic.
  • Conduit affiliate is removed in scope under CFTC Staff Letter No. 2542 ; ensure legacy heuristics are eliminated across systems and reports.
  • Continued reliance on pre2020 reps for Group B/C is permitted with freshness validation and evidence per the staff letter; maintain exception queues and evidence packs before cutover.

Unify Classification Under 23.23

Fragmented crossborder definitions created operational debt, collateral drag, and noisy controls. Staff Letter No. 2542 lets firms apply 23.23 U.S. person and guarantee tests across clearing, uncleared margin, and Parts 45/46, retiring duplicate logic and the conduit affiliate shortcut.

The stakes are real: misclassification can over or undercollateralize exposures and escalate audit findings; precision now protects P&L, liquidity, and compliance.

The upside is concrete: one rollout reclassified 38% of crossborder swaps as out of scope, cut exceptions 42% , and reduced IM by $12.5 million (27%) ; reporting breaks fell from 31 to 9 , and a separate case saw $9 million overposting under legacy conduit heuristics.

Strategic takeaway: Make 23.23 the only source of counterparty status, retire conduitaffiliate logic, and deliver policyascode through a counterparty classification engine that propagates determinations via API to ETRM, clearing determination, uncleared IM/VM, and Parts 45/46 reporting.

Operationalize 23.23 With Arcelian

Arcelian operationalizes 23.23 by linking policy, controls, and systems so counterparty status drives onboarding, clearing, margin, and reportingwithout desk disruption.

• Counterparty status engine: policyascode for 17 C.F.R. 23.23 U.S. person/guarantee with conduit affiliate removalreplaces brittle logic and fragmented definitions; APIs feed onboarding, ETRM, collateral, and SDR reporting.
• Document and rep refresh: validates pre2020 reps, extracts guarantees, and maintains evidence/freshnesscutting exceptions and reducing Parts 45/46 reporting breaks.
• Integration and workflow redesign: push determinations to IM/VM and clearing in near real timeshrinking collateral drag and cycle time in crossborder swaps.
• Controls and model governance: provide versioned rules, automated tests, and lineagestrengthening reconciliations with SD/SE views and tightening compliance.
• Finance and risk calibration: frame portfoliolevel IM, liquidity, P&L, and limits impacts from reclassificationbuilt into BAU planning.

Schedule Arcelian’s short, structured workshop now to turn 23.23 policy into a delivery roadmap your desk can execute.

Risk, Credit & Compliance Modernization: RegTech for Cross‑Border Swaps under CFTC §23.23

With Staff Letter 25-42 clarifying cross‑border swaps harmonization under §23.23, risk leaders have an opportunity to retire fragmented U.S. person/guarantee determinations and the conduit‑affiliate heuristic. The modernization strategy is to stand up a policy‑as‑code classification engine and control plane as the single source of truth across onboarding, clearing determination, uncleared margin (IM/VM), and Parts 45/46 reporting automation.

In practice, this means codifying §23.23 U.S. person definitions, substituted compliance logic, and booking models in versioned rules with evidence, lineage, and KPIs, then exposing determinations to ETRM architecture, SDR/SEF, and collateral systems via APIs and events.

Integration choices should be framed by latency, explainability, and governance requirements.

• Event‑driven ingestion from onboarding/KYC and trade capture.
• Synchronous evaluation for pre‑trade clearing determination alignment.
• Asynchronous fan‑out to margin and reporting pipelines.

AI can assist, but must be bound to controls: Agentic AI can triage reference‑data gaps, propose rule changes from Staff Letters and no‑action relief, and simulate IM impacts—yet all actions should be explainable, policy‑linked, and subject to approvals.

Sequence the integration roadmap to de‑risk change:

• (1) Discover data and author the §23.23 ontology.
• (2) Implement rules and evidence templates.
• (3) Wire orchestration hooks in front/middle/back office.
• (4) Parallel‑run with backtesting against historical filings.
• (5) Decommission legacy heuristics and manual workarounds.

This reinforces our thesis that modernization succeeds when control and data models are unified across the trade lifecycle.

Expected outcomes should be measurable and owned:

• IM reduction through accurate status and substituted compliance application; fewer margin disputes and calls.
• Fewer exceptions and reporting breaks via consistent classifications driving Parts 45/46 data elements and UTI/UPI consistency.
• Lower operational risk with audit‑ready lineage, clear override policies, and KPI tracking (misclassification rate, exception aging, clearing rejections).
• Faster change velocity—new rule effective dates promoted through controlled releases rather than spreadsheet rewrites—supporting sustainable uncleared margin requirements optimization in energy/commodity trading.

Frequently Asked Questions

What changes under CFTC Staff Letter No. 25-42 for cross-border swaps status?

You may apply the 2020 §23.23 U.S. person and guarantee tests consistently across clearing/execution, Parts 45/46 reporting, and uncleared margin. The conduit‑affiliate shortcut is removed for the specified scopes, and you can continue to rely on pre‑2020 representations for Group B/C if you

validate freshness and keep evidence. Because the 2020 definitions are narrower, determinations must be precise to avoid under‑ or over‑collateralizing and missing clearing/reporting triggers.

How does unifying on the §23.23 tests reduce collateral drag and exceptions?

A single, governed status service that feeds onboarding, clearing determination, IM/VM, and reporting eliminates duplicate logic and drift. In one rollout, 38% of cross‑border swaps were re‑classified out of scope, IM fell by $12.5 million (27%) with no VaR change, exceptions dropped 42%, and monthly reporting breaks fell from 31 to 9—freeing two FTEs. By contrast, legacy conduit heuristics led to a $9 million IM over‑post at another firm.

What’s the recommended path to implement a policy‑as‑code classification engine?

Encode §23.23 U.S. person and guarantee rules as versioned policy‑as‑code with tests and attestation; make the engine the system of record; and publish status via APIs/events into ETRM, collateral, SDR, and risk. Sequence the change: normalize definitions and retire conduit‑affiliate logic; connect status to clearing, margin, and Parts 45/46; industrialize propagation; parallel‑run with backtesting; validate and evidence any reliance on pre‑2020 reps (Group B/C); and maintain auditable lineage, approvals, and KPIs.

Trend Watch RegTech adoption is entering its operate-at-scale phase. With CFTC Staff Letter 25-42 accelerating cross-border swaps harmonization under 17 C.F.R. §23.23, the competitive edge now comes from how fast a policy-as-code counterparty classification engine can drive clearing determination, uncleared margin requirements (IM/VM), and Parts 45 and 46 reporting—while enforcing conduit affiliate elimination and auditable data lineage.

What’s changing on the desk: classification becomes regulated reference data with SLAs. Firms are setting T+0 propagation targets from onboarding through ETRM integration, collateral, and SDR reporting; pre-trade checks align with §23.23 so clearing and margin decisions are consistent at point of execution.

Substituted compliance is codified, tested, and versioned—no more spreadsheet-era drift.

Execution playbook for energy and commodity marketers:

• Treat status as a control-plane service with board-level KPIs (exception rate, IM drag, Parts 45/46 breaks). Tie releases to a change calendar aligned to Staff Letters and dealer notices.
• Build bidirectional reconciliations with SD/SE views to preempt disputes; document reliance on pre‑2020 reps where permitted and expire them automatically.
• Use explainable AI in ETRM to extract guarantees, flag stale representations, and simulate IM/VM impacts—always policy-linked and approval-gated.

Outcome to target: faster onboarding and fewer breaks, plus measurable liquidity lift as right-sized IM/VM frees cash.

In a market where financing

Costs and audit scrutiny are rising; unified §23.23 determinations are a direct lever on P&L , risk analytics quality, and energy trading modernization.

Closing Insight: Operationalizing §23.23 as Governed Reference Data

Leaders that treat §23.23 status as regulated reference data and enforce it through a governed control plane will convert rule clarity into balance‑sheet results.

Execute the following controls to harden the lifecycle:

• Make policy‑as‑code the contract linking Legal, Risk, and Engineering.
• Push determinations T+0 into ETRM, collateral, and SDR.
• Retire conduit‑affiliate heuristics.
• Instrument KPIs (IM drag, exception aging, Parts 45/46 breaks).

With explainable AI bound to approvals—extracting guarantees, validating pre‑2020 reps, and simulating IM/VM—you compress decision cycles without compromising control.

As financing costs and audit scrutiny rise, harmonized classification becomes a liquidity lever and dispute shield—shrinking in‑scope populations, reducing collateral drag, and stabilizing P&L.

Now is the time to operationalize:

• Stand up the classification engine.
• Run parallel backtests.
• Schedule change‑controlled cutover—so volatility flows through resilient, modernized controls rather than your cash.

Partner with Arcelian: Unifying §23.23 Status as a Single Source of Truth

Staff Letter 25‑42 creates the opening to make §23.23 the single source of truth; Arcelian helps leaders turn that clarity into a governed control plane—policy‑as‑code status, API/event propagation into ETRM, collateral, and Parts 45/46—without disrupting the desk.

In live rollouts, firms have realized measurable outcomes:

• Re‑classified 38% of cross‑border swaps out of scope.
• Reduced IM by $12.5 million (27%) with no VaR change.
• Cut exceptions 42% .
• Retired conduit‑affiliate heuristics with audit‑ready lineage.

If you’re weighing how to unify status as a service and de‑risk adoption, connect with our team to pressure‑test your logic, quantify liquidity and P&L lift, and shape a change‑controlled delivery roadmap.