CSA Releases Derivatives Manual v2.0: Point Nine Guide

On 11 August 2026, the Canadian Securities Administrators (CSA) released the second version of the CSA Derivatives Data Technical Manual. Issued also in Ontario as OSC Staff Notice 91-705 (Revised) and through equivalent staff notices across participating CSA jurisdictions, this update marks a major shift in technical trade reporting specifications.

The revised specifications take effect on 11 August 2027. Until that date, Version 1.0 (published 25 July 2024 and effective alongside the amended TR Rules since 25 July 2025) remains the operative technical standard.

This release does not rewrite the core regime: the underlying Trade Reporting Rules (TR Rules) remain unchanged, the required data set stays fixed at 148 fields, and no new reporting populations are introduced. Instead, Version 2.0 focuses on the technical execution layer, updating field definitions, formats, allowable values, and validation conditionality.

Key Technical Changes at a Glance

Detailed Technical Breakdown

1. Prescriptive Schedule Field Reporting

Multi-value schedule fields must now enforce rigorous structural consistency:

• A single, consistent delimiter must be maintained across all files by the Trade Repository (TR).
• Format and validation rules apply to each individual entry inside a delimited field, rather than the field as a whole.
• Related schedule fields must contain an equal number of entries and be ordered chronologically by effective date.
• Public dissemination is limited to the first 10 values.
• A total of 26 fields fall under this multi-value requirement (e.g., Notional schedules, Price schedules, Strike Price schedules, and Other Payments).

2. Clarified Conditionality & Leg 2 Validations

• Explicit Four-State Conditionality: Validations now distinguish between Mandatory(M), Conditional(C), Not Required(NR), and Optional(O). Crucially, worked examples distinguish else (blank) from else (optional), removing prior interpretation ambiguity.
• Leg 2 Validation Carve-Out: Where the Technical Manual does not state leg-specific validations, rules apply to Leg 1 by default. They must not be assumed to apply to Leg 2. Because Trade Repositories may apply custom Leg 2 checks, validation behaviour may legitimately vary between repositories.

3. Standardised Underlier ID (OTHER) Guidance

When an underlying asset or index cannot be derived from a Unique Product Identifier (UPI) and is reported as OTHER, new Appendix tables specify acceptable format patterns:

• Interest Rate / Commodities: ISDA Floating Rate Option (FRO) and Commodity Reference Price (CRP) naming conventions.
• Unlisted Debt / Equities: Official issuer names combined with maturity, coupon rate, or CFI attributes.
• Exchange-Traded Derivatives: Standardized concatenation incorporating MIC, Product Code, Put/Call indicator, Expiry Date, and Strike Price.
• Digital Assets: ISO 24165 Digital Token Identifiers (DTI).

4. Position Reporting & Action Sequences

• Same-day position inclusions must use Action Type POSCwithout an Event Type.
• Position inclusions on subsequent days must use Action Type TERM with Event Type INCP.
• Zero-valuation positions must either be terminated and recreated under a new UTI or kept open while reporting zero values daily.
• Correcting errors in historical valuation or collateral entries must now use Action TypesVALUandMARU, respectively.

The Global Perspective: Strategic Impact Beyond Canada

Canada is leading global implementation as the first regulatory body to adopt CDE Technical Guidance Version 4. Because CDE forms the common baseline for over-the-counter derivatives reporting worldwide, identical baseline updates will be rolled out by authorities across the EU, UK, US, Australia, and Singapore.

Firms that approach OSC 91-705 (Revised) as an isolated, Canada-only requirement risk duplicating data mapping, architecture design, and testing efforts as other global regulators mandate CDE v4. A global CDE v4 strategy allows market participants to execute this work once.

Implementation Roadmap: Preparing for August 2027

Although the formal deadline is 11 August 2027, the practical timeline depends on when Trade Repositories release updated XML schemas and open user acceptance testing (UAT) environments.

Recommended Immediate Actions:

1. Data Population Audit: Identify all internal trades utilizing schedules, custom baskets, OTHER underliers, or the optional position reporting model.
2. Validation Engine Check: Ensure internal systems can handle four-state conditionality (M, C, NR, O) and per-entry schedule validation.
3. Repository Gap Analysis: Review custom Leg 2 validation requirements for each designated trade repository used for Canadian reporting.

How Point Nine Supports Your Compliance

Point Nine provides a cloud-native, multi-regime reporting platform covering CSA, CFTC/SEC, EMIR (EU/UK), MiFIR (EU/UK), SFTR, ASIC, MAS, and FinfraG.

Our single-engine, multi-regime model helps financial institutions adapt to CDE v4 seamlessly:

• Centralised CDE v4 Architecture: We integrate CDE v4 updates once across our unified platform, ensuring that your logic mapping carries over directly as other global authorities adopt the standard.
• Dual-Version Rule Engine: Point Nine supports effective-dated, versioned rule sets. This allows the current 25 July 2025 baseline and the new 11 August 2027 specification to run concurrently during testing without disruptive system hard cutovers.
• Multi-TR Handling: We manage repository-specific validation variations, including custom Leg 2 logic, directly within our platform, protecting your operations from submission rejections.

Frequently Asked Questions (FAQ)

Q1: When do the CSA Technical Manual v2.0 rules become mandatory?
The new specifications take effect on 11 August 2027. Until then, Version 1.0 remains the required operational specification.

Q2: Do the underlying TR Rules change with this release?
No. The core TR Rules, legal definitions, and the 148 reportable field set remain unchanged. Version 2.0 updates the technical layer, including format standards, allowable values, and validation conditionality.

Q3: How are multi-value schedule fields validated under the new manual?
Each individual entry in a delimited schedule field must independently pass the format and validation rules for that data element. Furthermore, related schedule fields must have an equal number of values and be sorted chronologically by effective date.

Q4: What action should Point Nine clients take?
Point Nine manages schema updates, field mapping, and TR testing directly within our architecture. Clients should consult with their Point Nine account representative to review affected trade populations and align on testing schedules ahead of repository UAT windows.