ISDA Seeks Vendors for Derivatives Trade Reporting Eligibility Tool

ISDA has issued a request for proposal (RFP) for a trade reporting eligibility tool to sit alongside its Digital Regulatory Reporting (DRR) solution, with proposals due by 5.00pm EST on December 31, 2026 and a vendor decision expected no later than January 31, 2027.

The tool would standardize one of the least consistent steps in the derivatives reporting workflow: deciding whether a transaction must be reported at all. Today, that determination rests on each firm's individual analysis of the rules, and conclusions can differ from firm to firm. The ISDA tool would base eligibility analysis on a golden-source interpretation of the rules produced by an ISDA working group.

ISDA has pledged to support 14 reporting rule sets across nine major jurisdictions through the DRR, which uses the Common Domain Model (a standardized data and process model for derivatives) to translate an industry-agreed interpretation of reporting rules into machine-executable code. The association has committed to maintaining that code as the underlying rules evolve.

What must the tool determine?

According to the RFP, the eligibility tool should provide analysis on whether a derivatives transaction is required to be reported under various reporting regimes, which counterparty bears the reporting obligation, and under what timeline. At a minimum, the solution must consider:

• counterparty and jurisdictional nexus;
• product and regime scope;
• conditional exemptions;
• allocation of reporting responsibility;
• lifecycle events and timing rules, including events that must not be reported.

The requirements extend across the full range of reporting regimes covered by the ISDA DRR, and the tool must be extensible to new or amended reporting rules in future.

Evidence trail and firm overrides

The RFP specifies an audit requirement that goes beyond a simple yes-or-no output. The tool must provide a full evidence trail for every conclusion, citing specific regulatory provisions and ISDA working group discussions where relevant.

ISDA also draws a firm boundary around the tool's legal standing. It is not intended to make a final legal eligibility determination on whether a transaction should be reported. The solution must support firm-specific configurations and overrides, and those overrides must be clearly distinguishable from the ISDA golden-source position — a design choice that keeps legal accountability with the reporting firm while giving desks a consistent analytical baseline.

What does this change for reporting desks?

For buy-side and sell-side reporting teams, the practical question is whether the tool removes the per-firm interpretation work that currently drives cost and inconsistency. The RFP's evidence-trail requirement points at regulator-driven audit needs: firms could cite provision-level justification for each reporting decision rather than reconstructing internal legal analysis. The override architecture means firms with divergent legal views can retain their own positions without abandoning the shared golden source.

Procurement timeline

Interested vendors can request the detailed RFP requirements document by emailing [email protected]. The fixed procurement calendar — proposals by December 31, 2026, decision by January 31, 2027 — gives technology providers a defined window to scope a solution against the DRR's existing code base and the 14 supported rule sets.

More information on the ISDA DRR is available on the association's solutions infohub. If a vendor is selected on schedule, market participants can expect a defined eligibility layer to enter development alongside the DRR in early 2027, with coverage obligations tied to the rule sets ISDA already supports.