Guidance · AMF · 21 Jan 2026
A reporting counterparty must notify the regulator of a significant error or omission as soon as practicable after discovery, but need not notify errors fully remedied, or derivatives terminated or expired, before July 25, 2025. Only clearing agencies and derivatives dealers must verify data accuracy on an ongoing basis; other reporting counterparties must ensure accuracy but not verify. Each Ontario reporting counterparty must submit a separate webform; elsewhere a single pdf may cover a corporate group.
CSA Staff Notice 96-307 (Revised)
Frequently Asked Questions about Derivatives Trade Reporting
CSA/ACVM Canadian Securities Administrateurs Autorités canadiennes en valeurs mobilières
First published May 1, 2025; revised January 21, 2026
January 21, 2026
Staff of the member jurisdictions of the Canadian Securities Administrators (CSA Staff or we) have compiled a list of frequently asked questions (FAQs) that we have received about the CSA derivatives trade reporting rules, as amended by amendments that were published on July 25, 2024 and came into force on July 25, 2025 (collectively, the TR Rules).1
The purpose of the FAQs is to provide clarity about how certain requirements under the TR Rules should be implemented, while preserving flexibility to the extent possible for reporting counterparties and trade repositories to operationalize these requirements in the context of their particular business frameworks.
The list of FAQs below is not exhaustive but includes key issues and questions that market participants have posed to us since publication of the amendments, along with our current views. CSA Staff may update these FAQs from time to time as necessary. CSA Staff welcome comments and questions from market participants on an ongoing basis. The FAQs will be posted on the websites of the local regulators or securities regulatory authorities. 2
CSA Staff also refer market participants to the CSA Summary of Comments and Responses3 that was published together with the amendments to the TR Rules, and which also include responses to questions that were raised in 2022 during our consultation on the draft amendments.
The responses to the FAQs represent the views of CSA Staff and do not constitute legal advice.
This Notice updates and replaces a prior version of this Notice that was published on May 1, 2025 and reflects additional questions that CSA Staff received from market participants. A redline showing the changes is provided.
[1] Manitoba Securities Commission Rule 91-507 Derivatives: Trade Reporting (MSC 91-507), Ontario Securities Commission Rule 91-507 Derivatives: Trade Reporting (OSC 91-507), Regulation 91-507 respecting Trade Repositories and Derivatives Data Reporting (Québec) (AMF 91-507) and, in the remaining provinces and territories, Multilateral Instrument 96-101 Derivatives: Trade Reporting (MI 96-101).
[2] Referred to in this Notice as “regulator”.
[3] See here.
Contents
A. Reporting Counterparty Hierarchy ............................................................................................................................................. 2
B. Verification........................................................................................................................................................................................... 4
C. Reporting of an Error or Omission by the Non-reporting Counterparty..................................................................... 4
D. Notice of a Significant Error or Omission – General ............................................................................................................ 6
E. Notice of a Significant Error or Omission – Scope ............................................................................................................... 7
F. Notice of a Significant Error or Omission – Type .................................................................................................................. 9
G. Notice of a Significant Error or Omission – Duration....................................................................................................... 10
H. Notice of a Significant Error or Omission – Other Circumstances............................................................................... 10
I. Notice of a Significant Error or Omission – Application before Amendments come into Force..................... 12
J. Notice of a Significant Error or Omission – Updates to Submitted Notices and New Notices........................ 14
K. Transferring a Derivative to a Different Trade Repository............................................................................................... 16
L. Unique Transaction Identifiers................................................................................................................................................... 17
M. Valuation Data ................................................................................................................................................................................. 18
N. Position Level Data ........................................................................................................................................................................ 19
O. Anonymous Derivatives ............................................................................................................................................................... 19
P. Unallocated Derivatives ............................................................................................................................................................... 20
Q. Effect of Amendments on Open Derivatives........................................................................................................................ 21
R. Data Elements.................................................................................................................................................................................. 23
S. Reportable Derivatives ................................................................................................................................................................. 26
T. Jurisdiction........................................................................................................................................................................................ 27
U. Public Dissemination..................................................................................................................................................................... 28
| # | Section | Question | Response |
|---|---|---|---|
| 1. | OSC 91-507 s. 25 | The definition of “ISDA methodology” in paragraph 25(3)(a) of OSC 91-507 refers to the Canadian Transaction | Market participants should refer to the most current version of the Canadian Transaction Reporting Party Requirements. |
| Reporting Party Requirements dated April 4, 2014 and amended as of March 20, 2015. If the Canadian Transaction Reporting Party Requirements are subsequently further amended, how should the term “ISDA methodology” be interpreted? | Staff of the Ontario Securities Commission intend to consider potential updates to the definition of “ISDA methodology” in OSC 91-507 at a convenient time following any further amendment to the Canadian Transaction Reporting Party Requirements. | ||
| 2. | OSC 91-507 s. 25 | Is the definition of “financial entity” in OSC 91-507 intended to capture commodity dealers? Is the definition intended to capture all derivatives dealers that are exempt from registration in a jurisdiction of Canada or a foreign jurisdiction? | The definition of “financial entity” is not intended to capture commodity dealers in Canada or a foreign jurisdiction that are not affiliated with another “financial entity.” We also note that the Companion Policy to Paragraph 25(1)(f) of OSC 91-507 indicates that a commodity dealer is an example of a non-financial entity. The definition of “financial entity” is also not intended to capture an entity solely because of a requirement to register or reliance on an exemption from registration under the securities legislation or commodities futures legislation of any jurisdiction of Canada or under the laws of a foreign jurisdiction. Staff of the Ontario Securities Commission intend to consider potential updates to the definition to provide further clarity in subsequent amendments to OSC 91-507. |
| 3. | General | Is it possible that more than one of the TR Rules could apply to a derivative? | Yes. For example, if a derivative involves a local counterparty in Manitoba and Ontario, then both MSC 91-507 and OSC 91-507 apply. A Manitoba derivatives dealer could have a reporting obligation under OSC 91-507 and an Ontario derivatives dealer could have a reporting obligation under MSC 91-507. Foreign counterparties may also have reporting requirements under any of the TR Rules where the derivative involves a local counterparty. The TR Rules are generally aligned and capable of compliance in a consistent manner, so we do not |
| expect there to be conflicts in compliance between the TR Rules. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 26.1(b) and (c) | Could you please clarify if an end-user is required to verify derivatives data? | The data verification requirements under these paragraphs do not apply to a reporting counterparty4 that is not a clearing agency5 or derivatives dealer.6 While all reporting counterparties (including reporting counterparties that are not clearing agencies or derivatives dealers) must, under paragraph 26.1(a) of the TR Rules, ensure the accuracy of the data that they report, only clearing agencies and derivatives dealers must verify the accuracy of that data on an ongoing basis. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 26.3(1) | A local counterparty, other than the reporting counterparty, must notify the reporting counterparty of an error or omission with respect to derivatives data. Does this mean that the non-reporting counterparty must review the accuracy of the reporting counterparty’s reports? | This requirement was already present in the pre-amended TR Rules but in a different section. It does not require a local counterparty, other than the reporting counterparty, to review the accuracy of the reporting counterparty’s derivatives data. However, if a local counterparty that is not the reporting counterparty does discover an error, it is required to notify the reporting counterparty. While not a requirement under the TR Rules, larger market participants may wish to consider, where feasible, reviewing reported data for which they are the |
[4] References in this Notice to “reporting counterparty” should be read as referring to, where section 36.1 of the TR Rules applies, a derivatives trading facility or facility for trading derivatives.
[5] References in this Notice to “clearing agency” should be read as referring to the reporting clearing agency, reporting clearing house, or recognized or exempt clearing agency, as defined in the relevant TR Rule.
[6] References in this Notice to “derivatives dealer” should be read as referring to, with respect to AMF 91-507, a person subject to the registration requirement as a dealer under the Derivatives Act, which includes a person that is registered or exempt from registration.
| # | Section | Question | Response |
|---|---|---|---|
| non-reporting counterparty. Inaccurate data reported by a reporting counterparty may impact regulatory requirements that apply to the non-reporting counterparty. For example, if the notional amount of a derivative is erroneously reported as being exaggerated, it could cause a regulator to view certain thresholds (for example, under Regulation 93-101 respecting Derivatives: Business Conduct or Regulation 94-101 respecting Mandatory Central Counterparty Clearing of Derivatives) to have been triggered where, in fact, they may not have been triggered. Also, where a derivatives participation fee may be payable by the non-reporting counterparty in certain jurisdictions, an error by the reporting counterparty could cause an error in the non-reporting counterparty’s fee calculation based on the erroneous reported data. In these circumstances, while the actual notional amount is what is relevant, the erroneous reported notional amount may nevertheless result in errors in the application of these thresholds and fees if there is reliance on the reported data. Also, as noted in the Companion Policy7 under subsection 32(4), reporting counterparties of the original derivative and clearing agencies should ensure accurate data reporting so that original derivatives that have cleared can be reported as terminated by the clearing agency. Original derivatives that have cleared but have not been reported as terminated are a significant concern for CSA Staff, and we expect reporting counterparties to be diligent in monitoring this issue. |
[7] For CSA jurisdictions that publish a Policy Statement rather than a Companion Policy, references in this Notice to “Companion Policy” should be read as referring to the Policy Statement.
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 26.3(2) | In interpreting the guidance in the Companion Policy under subsection 26.3(2), which of the following two approaches should reporting counterparties take: (1) review each of the four enumerated factors, but only consider those factors to be relevant to the extent they impair the ability of the regulator to fulfill its mandate, or (2) consider that where one of the four enumerated factors applies, this indicates that the error or omission impairs the ability of the regulator to fulfill its mandate, and that the error or omission is therefore significant? | The second interpretation is correct. Where one of the four factors applies, our view is that the error or omission impairs the ability of the regulator to fulfill its mandate, and the error or omission is therefore significant. For example, an error or omission in the notional amount of a derivative that has been outstanding for 7 business days is significant under the “type” factor. It is not necessary to consider, as a second step to the analysis, whether it may impair the ability of the regulator to fulfill its mandate. In other words, because this factor applies, we consider that this error or omission impairs the ability of the regulator to fulfill its mandate, and therefore is significant. |
| 2. | 26.3(2) | Is the “late reporting” box in Question 6 of CSA Staff Notice 96-308 Notice of Significant Error or Omission only relevant to the “Scope” factor? | No. In relation to the “Scope” factor, late reporting is only significant if reporting is delayed beyond 24 hours after the reporting deadline and exceeds the 10% threshold. Late reporting may be relevant for the “Type” factor if reporting is delayed beyond 7 business days and includes the data elements enumerated in the Companion Policy for this factor. Late reporting may be relevant for the “Duration” factor if reporting is delayed beyond 3 months. Late reporting may be relevant for the “Other Circumstances” factor if late reporting has occurred (irrespective of duration) while the circumstances described in this factor are present. |
| 3. | 26.3(2) | Are derivatives that have expired or terminated relevant to determining each of the factors in the Companion Policy under subsection 26.3(2)? | Scope, Type, Duration These factors are intended to apply only with respect to derivatives that have not expired or terminated. Other Circumstances This factor is intended to apply regardless of whether the derivative has expired or terminated (unless, as noted in the Companion Policy, the error or omission occurred more than three years before it is discovered). |
| 4. | 26.3(2) | Could an error or omission in only one derivative be significant if it meets the criteria under the “Type”, “Duration” or “Other Circumstances” factors in the Companion Policy under subsection 26.3(2)? | Yes. |
| 5. | 26.3(2) | Does this subsection require a reporting counterparty to search reported derivatives data for errors and omissions? | No. Subsection 26.3(2) only applies if a reporting counterparty discovers a significant error or omission, but does not require the reporting counterparty to search for errors and omissions. The requirement to review derivatives data for errors and omissions is limited to paragraphs 26.1(b) or (c), if applicable. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 26.3(2) | Is the “Scope” factor in the Companion Policy under subsection 26.3(2) intended to apply separately to each province or territory in Canada? | One purpose of the amendments to the TR Rules is to increase harmonization within CSA jurisdictions to support a harmonized operational implementation of the amendments. This purpose informs CSA Staff’s view that, in interpreting this factor in the Companion Policy, reporting counterparties may consider it to apply with respect to all reporting under the TR Rules, and it is not necessary to consider the 10% threshold separately for each province or territory. However, the threshold should not be calculated on a global basis, but rather should include only derivatives that are required to be reported under the TR Rules. |
| 2. | 26.3(2) | How often should a reporting counterparty assess whether the | In order to facilitate operationalizing this factor, it should be assessed at the time the reporting |
| “Scope” factor in the Companion Policy under subsection 26.3(2) applies while an error or omission persists? | counterparty is determining whether the error or omission is significant. CSA Staff only expect a reporting counterparty to assess this factor again while the error or omission persists if the reporting counterparty subsequently becomes aware that the error or omission affects more derivatives than it had originally considered in first assessing this factor. For example, if the reporting counterparty determines that the error or omission only affects interest rate swaps and determines that the error or omission is not significant, but if it subsequently discovers that the error or omission also affects commodity derivatives, we expect the reporting counterparty to reassess this factor. However, if a reporting counterparty determines that the error or omission is not significant under the “scope” factor solely on the basis that reporting is not delayed beyond 24 hours after the reporting deadline (if the scope would otherwise be above the threshold), we expect the reporting counterparty to reassess the scope if the non-reporting persists beyond 24 hours after the reporting deadline. For example, if a reporting counterparty discovers that it failed to report 11% of its derivatives within 24 hours, and if it still has not reported these derivatives after this time, it should reassess the scope and notify the applicable regulators if the scope of the omission still exceeds 10%. | ||
| 3. | 26.3(2) | If an error or omission occurs with respect to collateral that is reported at portfolio level, and the error or omission has affected all derivatives in the portfolio, which are more than 10% of the reporting counterparty’s derivatives, for which it is the reporting counterparty, and that are required to be reported under the Rule, does the “Scope” factor in the | Yes. In this circumstance, the “Scope” factor applies because this factor refers to the number of derivatives in respect of which an error or omission has occurred, regardless of whether the cause of the error may have been a single issue in calculating or reporting collateral for the portfolio. |
| Companion Policy under subsection 26.3(2) apply? | |||
| 4. | 26.3(2) | Is the 10% threshold specific to each asset class, or to the reporting counterparty’s derivatives, for which it is the reporting counterparty, across all asset classes? | The 10% threshold includes all asset classes. For example, if an error or omission affects 20% of a reporting counterparty’s derivatives, for which it is the reporting counterparty, across all asset classes, but only 1% of its commodity derivatives, the error or omission is significant. The affected commodity derivatives should be reflected, together with derivatives in any other asset classes, in the reporting counterparty’s Notice of Significant Error or Omission. |
| 5. | 26.3(2) | Can a single Notice of Significant Error or Omission be submitted on behalf of multiple reporting counterparties within a corporate group? | For Ontario, no. Each reporting counterparty should submit a separate webform to report a significant error or omission. For the other CSA jurisdictions, a single pdf form may be submitted on behalf of multiple reporting counterparties, provided that any information that is different for each reporting counterparty (for example in Questions 3, 4 and 18) is provided separately in respect of each reporting counterparty. A separate document may be attached for this purpose. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 26.3(2) | When does the 7-business day period indicated in the “Type” factor in the Companion Policy under subsection 26.3(2) begin? | The 7-business day period begins on the date of the error or omission. It does not begin on the date of discovery (unless the error or omission was discovered on the same day that it occurred). For example, if an error in notional quantity occurred on April 1 and is discovered on April 4, the error would not be significant on April 4 under the “type” factor because it had not persisted for longer than 7 business days. However, on April 10, the error has persisted for longer than 7 business days and it then becomes significant under the “type” factor. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 26.3(2) | When does the 3-month period indicated in the “Duration” factor in the Companion Policy under subsection 26.3(2) begin? | The 3-month period begins on the date of the error or omission. It does not begin on the date of discovery (unless the error or omission was discovered on the same day that it occurred). For example, if an error occurred on April 1 and was discovered on May 1, the error would not be significant on May 1 under the “duration” factor because it had not persisted for longer than 3 months. On July 1, the error has persisted for longer than 3 months and therefore is significant under the “duration” factor. We appreciate that the effect will be that any error or omission that has been outstanding in derivatives data for greater than three months would generally be considered significant. This is intentional. We expect validation to reduce the number of errors and omissions in derivatives data, and we expect verification, where applicable, to reduce the duration of any outstanding errors or omissions. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 26.3(2) | The “Other Circumstances” factor in the Companion Policy under subsection 26.3(2) refers to “at the time of the error or omission”. What does this mean? | This factor is not intended to be limited to the time when the error or omission first occurs. It applies to any time the error or omission is outstanding. For example, if an error or omission first occurs on August 1, 2025 which results in non-reporting of creation data that is not remedied, and an event of default occurs the following day, the default occurs at the time of the error or omission. On the other hand, if the error or omission is fully remedied on August 1, 2025 before the default, the default does not occur at the time of the error or omission. |
| A reporting counterparty might consider operationalizing this factor by developing a list of bankruptcies and credit events as they arise and then reviewing any subsequently discovered errors or omissions against this list. Another approach might be for a reporting counterparty to wait until it discovers an error or omission before checking for bankruptcies and credit events with respect to the affected derivatives. Alternatively, a reporting counterparty could, once a bankruptcy or credit event has occurred, review any reported derivatives with the counterparty or underlier to determine whether there are outstanding errors or omissions. | |||
| 2. | 26.3(2) | Does the “Other Circumstances” factor in the Companion Policy under subsection 26.3(2) apply to all events that might trigger a default? | No. We only consider this factor to be relevant if the counterparty is in bankruptcy or the reporting counterparty is notified by a regulator. A regulator may notify reporting counterparties if they consider “Other Circumstances” to apply in relation to a particular entity, but a reporting counterparty should not wait for this notice if the counterparty is bankrupt. This factor is typically relevant in the context of large-scale bankruptcies or credit events that are reported in the media, and where CSA Staff may be analyzing derivatives data to assess potential risk to the market. In that circumstance, the mandate of the regulator may be impaired if an error or omission in derivatives data either masks or exaggerates this risk and thereby frustrates CSA Staff’s ability to accurately assess it. Errors in respect of material economic terms and non-reporting are likely to be most relevant. |
| 3. | 26.3(2) | Does the reference to “credit event” under the “Other Circumstances” factor in the Companion Policy under subsection 26.3(2) apply only to instances where a credit event has been determined by a Credit | In order to facilitate operationalizing this factor, we would only consider a credit event to be relevant that is either pending, accepted, ongoing or has determined to have occurred by a Credit Derivatives Determination Committee or where the reporting counterparty is notified by a regulator. |
Derivatives Determinations
Committee?
Market participants may consult publicly available information from the Credit Derivatives Determinations Committee website.
8
A regulator may also notify reporting counterparties if they consider “Other Circumstances” to apply in relation to a particular entity, but a reporting counterparty should not wait for this notice if the credit event is either pending, accepted, ongoing or has determined to have occurred at a Credit Derivatives Determinations Committee.
CSA Staff note that there is no time period under this factor because risk arising from a credit event may spread quickly and the regulator may require accurate derivatives data to analyze this risk.
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 26.3(2) | A reporting counterparty must notify the regulator of a significant error or omission that has occurred as soon as practicable after discovery of the error or omission. How does this requirement apply to errors and omissions that occurred before July 25, 2025? | A reporting counterparty is not required under this subsection to provide notice of a significant error or omission that is fully remedied before July 25, 2025, or in respect of a derivative that is terminated or expired before July 25, 2025. The notice requirement under this subsection may apply to an error or omission that occurs before July 25, 2025 but is not fully remedied by that date. In this situation, the following factors (as specified in the Companion Policy) should be interpreted as applying beginning on July 25, 2025, as outlined more specifically below: Scope |
[8] Available at https://www.cdsdeterminationscommittees.org As of the date of this FAQ, the “All DC Requests” section of the website “identifies, in a summary table, all questions submitted to the DC for resolution.” Upon clicking “All DC Requests” the classification of event categories appears on this “Requests to the Determinations Committee” page in the upper right-hand corner drop down box “Show All Event Categories.”
| # | Section | Question | Response |
|---|---|---|---|
| This factor applies to an error or omission that occurs before July 25, 2025 if, at any time on or after July 25, 2025, both the error or omission persists and it affects more than 10% of the reporting counterparty’s reportable derivatives for which it is the reporting counterparty. For example, if the error or omission occurs on March 1, 2025 and, at that time, it affects more than 10% of the reporting counterparty’s reportable derivatives for which it is the reporting counterparty, but if the error or omission is partially remedied by July 25, 2025 such that it affects less than 10% of the reporting counterparty’s reportable derivatives for which it is the reporting counterparty on and after July 25, 2025, this factor does not apply. Type This factor applies to an error or omission that occurs before July 25, 2025 if it relates to any of the data elements identified in the Companion Policy for this factor, and if it persists for longer than 7 business days beginning on July 25, 2025. Duration This factor applies to an error or omission that occurs before July 25, 2025 if it persists for longer than three months beginning on July 25, 2025. Other Circumstances This factor applies to an error or omission that occurs before July 25, 2025 if the error and omission persists on or after July 25, 2025 and if any of the circumstances described in the Companion Policy for this factor also occur or persist on or after July 25, 2025. For example, if an error or omission occurs on March 1, 2025 and persists on July 25, 2025 and if the counterparty is in default on July 25, 2025, this factor applies. However, if either the error or omission or the default is remedied before July 25, 2025, this factor does not apply. Also, if the counterparty is in default before July | |||
| 25, 2025 and the derivative is terminated or expires before July 25, 2025, this factor does not apply even if the error or omission persists on or after July 25, 2025. Correction of Errors and Omissions Generally It is important to note that reporting counterparties have an ongoing requirement to report accurately and to remedy any error or omission as soon as possible regardless of when the error or omission occurred or whether the factors outlined in the Companion Policy apply. There is no “significant” threshold to correcting an error or omission, whether the error or omission occurs before or after July 25, 2025. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 26.3(2) | Where a reporting counterparty notifies a regulator under subsection 26.3(2) regarding errors or omissions in derivatives data in relation to a particular issue, should the reporting counterparty notify the regulator regarding new errors or omissions (in respect of any new derivatives that it enters into) that are related to the same issue? | No, if the errors and omissions are related to the same issue. For example, if a reporting counterparty notifies the regulator in relation to a technology error that has resulted in incorrect reporting of notional amounts, and this error is being replicated in new derivatives and/or new valuation data each day, the reporting counterparty is not required to submit additional notices each day in respect of each such new error or omission, as these errors or omissions are reasonably related and the issue was discovered at approximately the same time. However, a new notice is required if a new unrelated issue is discovered that results in a significant error or omission. |
| 2. | 26.3(2) | Where a reporting counterparty notifies a regulator under subsection 26.3(2), is the reporting counterparty required to update the notice to reflect any changes to information | As noted in the Companion Policy, we recognize that when a reporting counterparty provides a notice, it may not yet have a complete understanding of the error or omission. Therefore, the notice represents an initial “snapshot” of the error or omission based on the |
| provided in the notice, or any new information that the reporting counterparty identifies regarding the error or omission? | reporting counterparty’s understanding at the time of completing the Notice. However, we only expect a notice to be updated in the following circumstances: • The reporting counterparty determines that one or more asset classes that were not identified on the first notice are relevant to the error or omission. • No remediation date or approximate remediation date was provided on the first notice, and the reporting counterparty subsequently determines a remediation date or approximate remediation date. • The reporting counterparty provided an expected remediation date (or approximate date) on the first notice, but the actual or revised expected remediation date is more than 6 months after the date indicated on the first notice. Whether or not a reporting counterparty updates a notice, regulators may follow up with reporting counterparties to request additional updates or if they have questions regarding an error or omission. | ||
| 3. | 26.3(2) | What should a reporting counterparty do if, after sending a notice to the regulator of a jurisdiction it subsequently discovers that a notice should also be sent to the regulator of another jurisdiction? | If a reporting counterparty determines that a significant error or omission affected derivatives that were required to be reported under the TR Rule of a jurisdiction, it should submit the notice to the regulator of that jurisdiction. If it subsequently determines that the error or omission affected derivatives that were required to be reported under the TR Rule in another jurisdiction, the reporting counterparty should submit a notice at that time to the regulator of that other jurisdiction. In this situation, it is not necessary to resend or update the notice that was originally provided to the regulator that previously received it, except in any of the three circumstances described above. |
| For example, if a derivatives dealer sends a notice to the Ontario Securities Commission, but subsequently discovers that the error or omission also affected derivatives involving a Saskatchewan local counterparty, it should send a notice to the Financial and Consumer Affairs Authority of Saskatchewan; however, it is not necessary to resend or update the notice that it previously sent to the Ontario Securities Commission, except in any of the three circumstances described above. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 26.4 | Could a reporting counterparty change the designated or recognized trade repository to which derivatives data is reported for derivatives that have not expired or been terminated? | Yes. This section applies to each derivative. Accordingly, a reporting counterparty may change the designated or recognized trade repository to which derivatives data is reported for one, some or all of its derivatives that have not expired or terminated. |
| 2. | 26.4 | Could a reporting counterparty change the designated or recognized trade repository to which derivatives data is reported for derivatives that have expired or terminated? If a reporting counterparty is transferring all open derivatives to a different trade repository, is it required to also transfer all of its expired or terminated derivatives? | Transferring a reporting counterparty’s expired or terminated derivatives is not required when transferring open derivatives. Section 3.5 of the CSA Derivatives Data Technical Manual provides that “any live or dead (terminated or expired) transactions can be transferred out except for the transactions that are previously reported as an error” (as provided under section 26.2 of the TR Rules). However, market participants should confirm with both the designated or recognized trade repositories involved in the transfer to confirm any operational limitations regarding transferring expired or terminated derivatives. For instance, it is possible that records relating to derivatives that have expired or terminated more than 7 years ago may no longer be held by a trade repository as provided under subsection 18(2) of the TR Rules. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 29 | Subsection 29(6) provides that a market participant that is required to assign a UTI must do so as soon as practicable after execution and in no event later than the time that the derivative is required to be reported. Subsection 29(8) provides that a counterparty that is required to assign the UTI must provide it to the persons indicated in that subsection as soon as practicable. What is meant by “as soon as practicable” in the context of subsection 29(8)? Are the timeframes under subsection 29(6) and subsection 29(8) the same? Could a derivatives dealer that is required to “promptly deliver a written confirmation of the transaction” under subsection 28(1) of Regulation 93-101 respecting Derivatives: Business Conduct provide the UTI at the same time as the confirmation? | Timeframes for assigning and providing a UTI The timeframes under subsection 29(6), on the one hand, and subsections 29(7), (8) and (9), on the other hand, do not run concurrently because it is impossible to provide a UTI that has not yet been assigned. Once a UTI is assigned within the timeframe under subsection 29(6), it must then be provided within the timeframes specified under subsections 29(7), (8) or (9). What is meant by “as soon as practicable”? The reference to “as soon as practicable” means within a reasonably prompt time in the circumstances. For instance, the circumstances for a large bank may differ from those of a smaller commodity dealer or money services business. The Companion Policies indicate that the timeframes for reporting obligations under the TR Rules are based on UTIs being assigned and provided expediently. The purpose of providing a UTI to others is to enable them to use it in any required reporting, whether under the TR Rules or a foreign derivatives data reporting requirement. The timeframes under section 29 should be interpreted with a view to accomplishing this purpose. Could a derivatives dealer deliver a confirmation of the transaction at the same time as the UTI? Yes, provided it does not result in a delay in fulfilling the requirement to promptly deliver a written confirmation of the transaction or the requirement to provide the UTI as soon as practicable to enable the counterparty to use it in any required reporting. |
| 2. | 29 | If a reporting counterparty that is a bank doesn’t know whether its counterparty is a dealer (or under OSC | CSA Staff recognize that in certain instances under OSC 91-507, where one or both counterparties are not party to the ISDA Multilateral (as defined under section 25 of |
| 91-507, a dealer that is a financial entity), how would it determine which entity should assign a UTI? | OSC 91-507), a financial entity (for example, a bank) may not be aware of whether its counterparty is a derivatives dealer, and if so whether it is a financial entity. For a derivative involving a local counterparty that is uncleared and not executed anonymously on a derivatives trading facility, the bank would have a reporting obligation under OSC 91-507 in this situation regardless of whether its counterparty is a derivatives dealer or a derivatives dealer that is a financial entity. As a result, the bank would have to assign a UTI when it reports the derivative. If the bank’s counterparty is either not a derivatives dealer or a derivatives dealer that is not a financial entity, the bank’s counterparty does not have a reporting obligation under OSC 91-507 and, as a result, there should be no duplication of either reporting or a UTI under OSC 91-507. However, if the bank’s counterparty is a derivatives dealer that is also a financial entity, the bank’s counterparty would also have a reporting obligation under OSC 91-507. The two counterparties may not be able to follow the UTI hierarchy under section 29 because they are unaware that there are, in fact, two reporting counterparties. CSA Staff recognize that this may result in duplicate UTIs. CSA Staff also recognize that duplicate UTIs may occur in other situations, such as where there is a single reporting counterparty under one of the TR Rules but two reporting counterparties (or a different reporting counterparty) under another of the TR Rules. CSA Staff intend to monitor this issue during implementation and work with industry participants to explore further potential refinements to the UTI hierarchy. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 33 | From whose perspective is the valuation amount reported under | The valuation amount is reported from the perspective of the reporting counterparty, such that a positive number indicates that the valuation amount would be |
| Appendix A to the TR Rules – Data Element Number 101? | paid to Counterparty 1 and a negative number indicates that the valuation amount would be paid to Counterparty 2. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 33.1 | Is a designated or recognized trade repository required to accept position level data? | No, the TR Rules do not require a designated or recognized trade repository to accept position level data. A reporting counterparty that would like to report lifecycle event data, valuation data, and/or collateral and margin data as position level data in the circumstances permitted under the TR Rules should consult with its designated or recognized trade repository as to whether it will support this. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 36.1 | Could you please clarify what is an anonymous derivative? | Section 36.1 applies to anonymous derivatives that are executed on a derivatives trading facility9 and are intended to be cleared, where a counterparty does not know the identity of the other counterparty. We understand this may occur on swap execution facilities with central limit order books (CLOB) that facilitate trades on an anonymous basis. The concept of “anonymous” in section 36.1 is intended to align with that concept under CFTC regulatory requirements, including the Post-Trade Name Give-Up on Swap Execution Facilities Rule and proposed CFTC Data Element 147 SEF or DCM anonymous execution indicator. It is also intended to align with section 22.1 of the TR Rules and with CSA Data Element 23 Platform anonymous execution indicator. |
[9] References in this Notice to “derivatives trading facility” should be read as referring to, with respect to MI 96-101, a “facility for trading derivatives”.
| # | Section | Question | Response |
|---|---|---|---|
| A derivatives trading facility does not have the reporting requirement unless the derivative is anonymous. If the derivative is not anonymous, it is required to be reported by the reporting counterparty under section 25. | |||
| 2. | 36.1 | Is an unallocated derivative always anonymous, simply because a derivatives dealer does not know the identity of the funds to which the derivative will be allocated? | No. An unallocated derivative is only anonymous if the pre-allocation parties to the “block” or “bunched” transaction (for example, the fund manager and dealer) are unknown to each other. It is not anonymous simply because the dealer does not know the identity of the post-allocation counterparties (for example, the funds) at the time of execution. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 25 and 36.1 | Could you please clarify reporting in relation to unallocated derivatives on a derivatives trading facility between a derivatives dealer and a fund manager, as agent? | Not Anonymous CSA Staff’s position is that the dealer should report the unallocated transaction with the person acting as agent on behalf of the parties to the transaction, typically a fund manager, based on the local counterparty jurisdiction of the dealer and the agent (and with respect to the agent, only to the extent practicable if the dealer has made a local counterparty determination with respect to the agent). For allocations that occur before clearing, the dealer should report allocations (as provided in the CSA Derivatives Data Technical Manual at Example 4.4) only to the extent it receives them. We understand that this may arise for pre-trade allocations before a bunched order is executed. For allocations that occur at the clearing agency, we expect the clearing agency to report the resulting cleared derivatives as allocated (using the “CLAL” value in the CSA Derivatives Data Technical Manual). |
Anonymous
The derivatives trading facility reports the pre- allocation anonymous derivative with the agent, as provided under paragraph 36.1(4)(a). CSA Staff’s position is that the derivatives trading facility should consider the “local counterparty” jurisdiction of the agent and the dealer for reporting purposes. We understand that allocation occurs at the clearing agency and would therefore be reported by the clearing agency (using the “CLAL” value in the CSA Derivatives Data Technical Manual).
CSA Staff intend to review the TR Rules in this area and may recommend draft amendments regarding unallocated and anonymous derivatives.
Notwithstanding which entity reports the original derivative, the clearing agency is required to report the termination of the original derivative as provided in
section 32(4) of the TR Rules.
| # | Section | Question | Response |
|---|---|---|---|
| 1. | General | Section 1.3 Historical Derivatives of the CSA Derivatives Data Technical Manual states: "All existing derivatives should eventually be updated with the new data requirements and reported using the action field Modify MODI and event type Upgrade UPDT." Is this intended to indicate that reporting counterparties should upgrade existing reporting? | No. We refer market participants to the detailed guidance that we provided on this subject in the CSA Summary of Comments and Responses10 that was published together with the amendments to the TR Rules. For clarity, we have reproduced this response here: "For open derivatives on the date the amendments to the TR Rules take effect, any reporting that is required on or after this date must be reported as required under the amended TR Rules, but the amendments do not require any prior reporting to be upgraded. This means that: |
[10] See here.
| # | Section | Question | Response |
|---|---|---|---|
| • Creation data that is reported on or after the effective date of the amendments must be reported as required under the amended TR Rules. The technical specifications for this data should be consistent with the Technical Manual. However, creation data that was reported before the effective date of the amendments is not required to be upgraded even if the derivative remains outstanding on the effective date of the amendments (subject to trade repository requirements as discussed below). • Margin, valuation, and lifecycle event data that is reported on or after the effective date of the amendments must be reported as required under the amended TR Rules, even if the transaction was executed before the effective date of the amendments. The technical specifications for this data should be consistent with the Technical Manual. However, any valuation and lifecycle event data for the derivative that were required to be reported before the effective date of the amendments are not required to be upgraded. • Position reporting is available, subject to the conditions in the TR Rules, in respect of any positions that are outstanding on or after the effective date of the amendments, even if the relevant transactions were executed before the effective date of the amendments. We note that the CFTC required creation data on existing derivatives to be reported according to their updated specifications. Because of this, we expect that reporting counterparties will already have updated the creation data for the majority of derivatives reportable in Canada at the time our amendments take effect. Therefore, we have not explicitly required this under the amendments. However, we recognize that trade repositories may find it inefficient and potentially costly to maintain separate creation data for existing derivatives according to the former rules and may require their participants to upgrade this creation data.” In the event that a reporting counterparty does upgrade derivatives data, it should follow the guidance | |||
| in section 1.3 of the CSA Derivatives Data Technical Manual. The reference to “should eventually be updated” was not intended to suggest a different position from what we indicated in the CSA Summary of Comments and Responses. Eventually, all open derivatives will expire or terminate, and all new derivatives booked after the amendments take effect will be reported under the updated data elements or will be upgraded in order to submit lifecycle events. In addition, we note that trade repositories may have required their participants to upgrade creation data on existing derivatives, for example, to report collateral and valuation data as required under the TR Rules. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | App. A | Certain data elements under Section 2 of the CSA Derivatives Data Technical Manual are indicated as “O” (for “Optional”) under the “Validations” column. Does “Optional” mean that the reporting counterparty may decide not to report the data element, even if it is applicable to the derivative? | No. We refer reporting counterparties to the provisions at the beginning of Appendix A to the TR Rules: “the reporting counterparty is required to provide a response for each data element unless the data element is not applicable to the derivative.” Similarly, the CSA Derivatives Data Technical Manual provides at Section 1.2.5 under the heading “Values”, for “Optional”: “The data element should be included in the transaction if applicable.” “Optional” in the context of validations means that the trade repository should not require the data element to be populated under its validation procedure. This is designed so that a derivative for which the data element is not applicable does not fail the validation procedure. For instance, not all data elements apply to all types of derivatives. However, if the data element is applicable to the derivative, it is mandatory for the |
| reporting counterparty to report the data element even though it is labelled optional for the purpose of the validation procedure. A reporting counterparty must also not rely on the specifications of its trade repository in determining mandatory and optional data elements. Instead, a reporting counterparty should review the data elements in the context of the requirements of the TR Rules to ensure that it reports all data elements that are applicable to each derivative that it reports. | |||
| 2. | Data Element # 22 | Data Element # 22 Platform identifier refers to the identifier of the trading facility on which the transaction was executed. What should reporting counterparties consider when reporting this data element? Why is this information required by the CSA? | When reporting Data Element #22, the identifier should correspond to the exact trading facility on which the transaction was executed, and not the parent, affiliate or other affiliated trading facility. Also, this data element should not be used to report the name of a bank. A bank would be a counterparty to a derivative, rather than a platform. The concept of “platform” in Data Element #22 is intended to align with the definition of “facility for trading derivatives” as defined in MI 96-101 and “derivatives trading facility” as set out in the Companion Policy in the other TR Rules. If a derivatives trading facility provides access to a participant in a Canadian jurisdiction, it may be carrying on business in that jurisdiction and may be subject to requirements of applicable legislation that mandate recognition as an exchange or registration as an alternative trading system, depending on Canadian requirements relating to the services they provide to Canadian participants. CSA Staff intend to monitor this data element with a view to ensuring that derivatives trading facilities that provide access to Canadian participants are operating in accordance with Canadian requirements. |
| CSA Staff also note that certain counterparties may also be subject to requirements of their prudential regulator to manage third party risk, which may include risk associated with trading on platforms that are not operating in compliance with securities legislation. | |||
| 3. | Data Element #106 | What is Data Element # 106 Last floating reference value? | The CSA Derivatives Data Technical Manual describes this data element as the most recent sampling of the value of the floating reference for the purposes of determining cash flow. The floating price reference is used to calculate the most recent settlement under a transaction. For example, if the transaction is a monthly settled AECO fixed for float swap and the AECO price used to calculate the prior month’s settlement was $2.50, the last floating reference value would be $2.50. |
| 4. | Data Element #95 | Can reporting counterparties populate Data Element #95 Event timestamp with a value within 15 minutes of submission, consistent with CFTC specifications, and use Data Element # 12 Effective date to populate the future date on which the event takes effect, if applicable? Reporting a future date under Data Element #95 would conflict with current trade repository validations that are designed to reject values that are greater than 15 minutes after submission. | Yes. Reporting counterparties may report format and values in respect of future events using an approach that aligns with CFTC reporting until the CFTC implements updated specifications to align with revised CDE Technical Guidance. We anticipate updating the CSA Derivatives Data Technical Manual to provide further guidance. |
| 5. | Data Element #136 | Under Data Element #136 Other payment amount, what should be reported in the context of an early termination of the derivative (“UWIN” as noted in the values column of the CSA Derivatives Data Technical Manual for Data Element # 141)? Should this include realized profits or losses arising from the derivative? | No. In the context of an early termination, this data element is generally intended to cover only payments associated with the early termination. This would not include the profit or loss of the derivative. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | n/a | Are package foreign exchange spot transactions required to be reported under the TR Rules? | We understand a package foreign exchange spot transaction to have the following features: • two separate contracts are entered into as a package, in the sense that execution of one contract is contingent on execution of the other, and the component contracts are quoted or priced together as one economic transaction with (nearly) simultaneous execution of both contracts; • the two separate contracts are each executed, confirmed and settled separately, where performance of one is not contingent on performance of the other (in contrast to two legs of a single derivative such as a foreign exchange swap); • each contract settles via an actual delivery of the relevant currencies within two business days. MI 91-101 Derivatives: Product Determination, MSC Rule 91-506 Derivatives: Product Determination, OSC Rule 91-506 Derivatives: Product Determination, and Regulation 91-506 respecting Derivatives Determination (Québec) (collectively, the “Scope Rules”) provide for an exclusion in respect of a contract or instrument for the purchase and sale of a currency that (subject to certain conditions) settles within two business days. CSA Staff’s view is that, based on a plain language interpretation, this exclusion under the Scope Rules applies separately to each such separate contract within a package foreign exchange spot transaction, subject to the conditions of the exclusion. As a result, CSA Staff’s view is that they are excluded from the TR Rules, consistent with Part II of CFTC Letter 25-10. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | 1(1) | Is it possible for an entity to be a “local counterparty” for certain derivatives, but not for other derivatives (for example, depending on asset class)? | No. Either an entity is a local counterparty or it is not. |
| 2. | 1(1) | If the jurisdiction of a “local counterparty” changes before a derivative has expired or terminated, is the change in jurisdiction required to be reported? | Yes. A change in jurisdiction of a local counterparty is a lifecycle event because it is a change in creation data (Data Element # 10 or # 11). These data elements enable the appropriate regulator to access relevant data from the trade repository and exercise its mandate. We intend to provide more detailed guidance in the CSA Derivatives Data Technical Manual on how to report changes to Data Elements # 10 or #11. |
| 3. | 41.2(2) of AMF 91-507, MSC 91-507, OSC 91-507 42(2) of MI 96-101 | How should market participants determine where an individual is a “resident”? An individual may have multiple residences. | The term “resident” in these provisions was deliberately not defined to avoid increasing regulatory burden for reporting counterparties by necessitating a specific outreach to determine residence. Reporting counterparties may use residential address information collected through existing AML/KYC documentation. Also, where reporting counterparties ascertain an individual’s province or territory to determine the applicable registration and/or prospectus exemptions that may apply in the individual’s province or territory (e.g. accredited counterparty, accredited investor, qualified party), the relevant province or territory for reporting purposes may be in accordance with that determination. |
| 4. | Section 1(1) | What is the “local counterparty” jurisdiction of a branch of a bank? | A branch is not a legal entity. We expect the counterparty to a derivative to be the bank itself, rather than a branch of the bank. While branches are relevant to reporting frameworks in some other jurisdictions, they are not relevant to the TR Rules. Care should be taken in reporting the LEI of the bank itself under the TR Rules, rather than that of a branch of the bank. |
| 5. | Section 1(1) | Is a Canadian province, territory, or municipality a local counterparty? | Yes. His Majesty the King in right of Canada is a local counterparty in Ontario. A province or territory (including His Majesty the King in right of the province |
| or territory) is a local counterparty in the province or territory. A municipal government is a local counterparty in the province or territory of its location. A government agency is a local counterparty typically in the jurisdiction of its government. Section 41 of the TR Rules provide different exemptions for certain governments and government agencies from reporting requirements, but these do not exempt derivatives dealers from their own reporting requirements in respect of derivatives that they enter into with a counterparty that is a government or government agency. For example, if a foreign derivatives dealer enters into a derivative with His Majesty the King in right of Canada, the derivatives dealer is required to report the derivative under OSC 91-507. Similarly, if a derivatives dealer that is a local counterparty in Ontario enters into a derivative with the Province of Québec, the derivatives dealer is required to report the derivative under AMF 91-507 and OSC 91-507. The purpose of reporting derivatives entered into with governments and government agencies is to ensure that regulators have appropriate oversight of derivatives dealers and a complete and accurate assessment of potential risks (including market risk, counterparty risk, and systemic risk) in all relevant jurisdictions, consistent with our mandates. |
| # | Section | Question | Response |
|---|---|---|---|
| 1. | App. C, Table 2 | Table 2 of Appendix C refers to “EUR-EURIBOR-Reuters”. Is it sufficient that only “EUR-EURIBOR-Reuters” be disseminated or do other indexes starting with "EUR-EURIBOR" or "EUR- | All indexes starting with “EUR-EURIBOR” should be disseminated. CSA Staff anticipate proposing further amendments to the TR Rules relating to public dissemination. |
| EURIBOR-Telerate" all need be disseminated? | |||
| 2. | 39(3) | Under the Securities Act (Ontario), derivatives with certain government entities are excluded from public dissemination of transaction level data. What are the excluded entities and how does this affect transaction level public dissemination under the other TR Rules? | Under subsection 142(3) of the Securities Act, subsection 39(3) of OSC Rule 91-507 does not apply to derivatives traded by certain government entities. This means that derivatives with these entities are not required to be publicly disseminated for transaction level public dissemination under OSC 91-507. This exclusion has existed since public dissemination commenced in 2016. Staff note that this exclusion does not apply to reporting under subsection 26(1) or to aggregate level public dissemination under subsection 39(1). For convenience, OSC Staff have listed the following entities that we believe to be covered by this exclusion and that have LEIs: His Majesty the King in right of Canada 4BFD7AQU0A75QLAHK410 His Majesty the King in Right of the Province of British Columbia 54930058TO7MEKUHWL16 His Majesty in right of Alberta LQPXMHHNJKIPJYE53543 Province of Saskatchewan 549300FKDIB7OJMBSP83 Province of Manitoba 5493003QILFOB3JRKE30 His Majesty the King in right of Ontario C7PVKCRGLG18EBQGZV36 Province of Québec 549300WN65YFEQH74Y36 |
| # | Section | Question | Response |
|---|---|---|---|
| Province of New Brunswick 549300POZA55ZTGSOU44 His Majesty the King in Right of the Province of Nova Scotia 5493002W033HJBDP3481 Government of the Province of Prince Edward Island, Department of Finance 549300L826JG01X2QH35 Government of Newfoundland and Labrador 549300CLWWW48GTPOJ49 Government of the Northwest Territories 549300MHKRYWVMMSH566 Metrolinx 549300IS34S901EOZB45 Ontario Electricity Financial Corporation 549300SI5D7OIEG4Y641 CSA Staff are not aware of comparable exclusions in other CSA jurisdictions. As a result, we note that transaction level public dissemination may be required under another TR Rule even where it is not required in Ontario. For example, if a derivatives dealer that is a local counterparty in Québec enters into a derivative with His Majesty the King in right of Ontario, the derivative remains subject to transaction level public dissemination under subsection 39(3) of AMF 91-507. Similarly, if a derivatives dealer that is a local counterparty in Ontario enters into a derivative with the Province of Saskatchewan, the derivative remains subject to transaction level public dissemination under subsection 39(3) of MI 96-101 in Saskatchewan. | |||
| Each trade repository has a single transaction level public dissemination for Canada, rather than separate dissemination for each province or territory. Therefore, even where transaction level public dissemination is not required under OSC 91-507, CSA Staff expect it to occur where required under any of the other TR Rules. To this end, OSC Staff’s view is that subsection 142(3) of the Securities Act (Ontario) does not prohibit transaction level public dissemination; rather, it operates as an exclusion from the requirement in Ontario. CSA Staff note that only certain derivatives are subject to transaction level public dissemination under the TR Rules, and that these remain subject to various protections, including masking, rounding, capping and a 48-hour delay. |
If you have questions about this CSA Staff Notice, please contact any of the following:
Dominique Martin
Senior Director,
Market Activities and Derivatives
Autorité des marchés financiers
514-395-0337, ext. 4351 dominique.martin@lautorite.qc.ca
Michael Brady
Deputy Director, Capital Markets Regulation
British Columbia Securities Commission
604-899-6561 mbrady@bcsc.bc.ca
Janice Cherniak
Senior Legal Counsel, Market Regulation
Alberta Securities Commission
403-355-4864 janice.cherniak@asc.ca
Sonne Udemgba
Director, Legal
Securities Division
Financial and Consumer Affairs Authority of
Saskatchewan
306-787-5879 sonne.udemgba@gov.sk.ca
Greg Toczylowski
Associate Vice President
Trading & Markets – Derivatives
Ontario Securities Commission
416-593-8215 gtoczylowski@osc.gov.on.ca
Leigh-Anne Mercier
General Counsel
Manitoba Securities Commission
204-945-0362 leigh-Anne.Mercier@gov.mb.ca
Abel Lazarus
Director, Corporate Finance
Nova Scotia Securities Commission
902-424-6859 abel.lazarus@novascotia.ca
Michael Melvin
Senior Securities Analyst
Financial and Consumer Services Commission of
New Brunswick
506-643-7690 michael.melvin@fcnb.ca
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
RegAlert holds no document that amends or replaces this one. This is not a check that it is in force: confirm with the regulator.
“CSA Staff Notice 96-308 Notice of Significant Error or Omission”
“Regulation 93-101 respecting Derivatives: Business Conduct”
“Regulation 94-101 respecting Mandatory Central Counterparty Clearing of Derivatives”
More like this from AMF
AMF published 2 documents in the last 30 days. We email you each new one the day it's published.
Source: Autorite des marches financiers Quebec — original document · Summary generated with machine assistance and checked by an AI reviewer before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added