ISDA Updates Global OTC Derivatives Compliance Calendar

ISDA’s update comprises one listed document for global OTC derivatives compliance deadlines, with no rule, jurisdiction, proposal date, effective date or compliance deadline stated.

ISDA says it has updated its global calendar of compliance deadlines and regulatory dates for the over-the-counter derivatives space. The linked item carries the same title, while the calendar notice appears both as the lead document and as the first Latest entry.

No calendar table, jurisdiction list or dated entry appears in the material. A desk can confirm that ISDA maintains a calendar, but it cannot determine from this notice whether a reporting obligation, risk limit, vendor workflow or software control changed.

What does the update actually establish?

• Scope: ISDA describes the document as a global calendar covering OTC derivatives compliance deadlines and regulatory dates.
• Document inventory: The page displays a document count of one and repeats the same one-sentence calendar announcement in its Latest section.
• Revision record: The source states neither what changed nor when the calendar posted. It provides no previous version, redline, effective date, transition period, affected counterparty class or jurisdiction.

That boundary is consequential because the announcement does not distinguish a new deadline from a date moved in the prior version. Buy-side and sell-side teams cannot route an obligation to an owner, schedule a control test, estimate implementation work or validate an exception from the excerpt alone.

Which dated ISDA items accompany the calendar notice?

Three latest entries sit alongside the calendar item, but the source presents none as a revision to that calendar.

• SIMM calibration: ISDA says it published ISDA SIMM methodology version 2.9+2606 following the 2026 primary calibration exercise. The version incorporates updates arising from recalibration using historical data up to and including 30 June 2026.

The methodology excerpt supplies no changed parameter, predecessor comparison, publication timestamp, implementation date or affected transaction scope. It establishes a model version and data cut-off, not a quantified impact on any desk workflow.

• Regulatory reporting and AI: Another latest item, Moving Regulatory Reporting up a Gear with AI, says: “The aim of derivatives regulatory reporting is to improve transparency so regulators can monitor market activity and identify emerging risks.”

The item also says reporting rules and subsequent updates have produced improvements without fully consistent outcomes. Its explanation then breaks off mid-sentence. The excerpt names no AI tool, vendor, regulator, reporting rule, pilot, deployment date or consistency metric, so it documents a stated problem rather than a deployable technology change.

The third latest item concerns the ISDA/AFMA Sydney Derivatives Trading Forum on 26 October 2026. The item identifies Scott O’Malia as ISDA chief executive; he opens with: “Good morning, and welcome to the ISDA and AFMA Derivatives Trading Forum.”

The source also shows the start of O’Malia’s thanks to attendees before truncating the remarks. It gives no agenda, additional speakers, venue detail or link between the forum and the compliance calendar.

These dated items supply context, not a calendar comparison. The SIMM item names a 2026 calibration exercise and a 30 June 2026 data cut-off; the forum item carries an 26 October 2026 date. Neither says which compliance deadline moved, and the AI item identifies no reporting deployment that could absorb a calendar change.

What must desks verify next?

Before treating the update as an operational instruction, desks need a dated, rule-level comparison against the previous calendar. Each entry should identify the jurisdiction, legal or regulatory instrument, proposal and effective dates, compliance deadline, affected entities and required action.

That comparison would let legal and compliance owners map each entry to valuation, data and reporting controls, while technology and operations teams could assess software routing, reconciliation, retention and resourcing requirements. Without it, claims about cost, risk or control changes remain unmeasured.

Until ISDA supplies the itemized entries and revision history, the defensible conclusion stays narrow: ISDA has updated one listed calendar document, but the source supports no verified deadline or desk-control change.

The 30 June 2026 SIMM data cut-off and 26 October 2026 forum provide dated context, not proof of a calendar revision. A rule-level comparison tying dates to obligations is the next evidence needed for an implementation assessment.