Rule · AMF · 13 Sep 2023
An applicant for recognition must file a completed Form 91-507F1 and audited financial statements for its most recently completed financial year. A recognized trade repository must not implement a significant change to Form 91-507F1 matters without filing an amendment at least 45 days beforehand, and must file other amendments by the 10th day after month-end. It must file annual audited financial statements within 90 days of financial year-end, notify the Authority within 5 working days of appointing or replacing its chief compliance officer, chief executive officer or chief risk officer, and file Form 91-507F3 at least 180 days before ceasing business.
Administrative version in force on September 13, 2023 This document has official status
chapter, I-14.01, r. 1.1
Derivatives Act
(chapter I-14.01, s. 175, 1st par., subpars. 2, 3, 9, 12, 26, 27 and 29)
M.O. 2013-21, c. 1; I.N. 2014-01-01.
1. (1) In this Regulation
“asset class” means the asset category underlying a derivative and includes interest rate, foreign exchange, credit, equity and commodity;
“board of directors” means, in the case of a recognized trade repository that does not have a board of directors, a group of individuals that acts in a capacity similar to a board of directors;
“creation data” means the data in the fields listed in Appendix A;
“derivatives data” means all data related to a transaction that is required to be reported pursuant to Chapter 3;
“Global Legal Entity Identifier System” means the system for unique identification of parties to financial transactions developed by the Legal Entity Identifier System Regulatory Oversight Committee;
“Legal Entity Identifier System Regulatory Oversight Committee” means the international working group established by the Finance Ministers and the Central Bank Governors of the Group of Twenty nations and the Financial Stability Board, under the Charter of the Regulatory Oversight Committee for the Global Legal Entity Identifier System dated November 5, 2012;
“life-cycle event” means an event that results in a change to derivatives data previously reported to a recognized trade repository in respect of a transaction;
“life-cycle event data” means changes to creation data resulting from a life-cycle event;
“local counterparty” means a counterparty to a transaction if, at the time of the transaction, one or more of the following apply:
(a) the counterparty is a person organized or incorporated under the laws of Québec or that has its head office or principal place of business in Québec;
(b) the counterparty is registered as a dealer under the Derivatives Act (chapter I-14.01) or in an alternative category as a consequence of trading in derivatives;
(c) the counterparty is an affiliate of a person described in paragraph (a), and such person is responsible for the liabilities of that affiliated person;
“participant” means a person that has entered into an agreement with a recognized trade repository to access the services of the recognized trade repository;
“reporting clearing house” means
(a) a person recognized, or exempted from the recognition requirement, as a clearing house by the Authority under the Act; or
(b) a clearing house that submitted an undertaking accepted by the Authority to act as the reporting counterparty for the purposes of fulfilling the reporting obligation under this Regulation;
“reporting counterparty” means the counterparty to a transaction as determined under section 25 that is required to report derivatives data under section 26;
“Schedule III bank” means an authorized foreign bank named in Schedule III of the Bank Act (S.C., 1991, c. 46);
“transaction” means entering into, assigning, selling or otherwise acquiring or disposing of a derivative or the novation of a derivative;
“user” means, in respect of a recognized trade repository, a counterparty (or delegate of a counterparty) to a transaction reported to that recognized trade repository pursuant to this Regulation; and
“valuation data” means data that reflects the current value of the transaction and includes the data in the applicable fields listed in Appendix A under the heading “Valuation Data”.
(2) In this Regulation, each of the following terms has the same meaning as in Regulation 52-107 respecting Acceptable Accounting Principles and Auditing Standards (chapter V-1.1, r. 25): “accounting principles”; “auditing standards”; “publicly accountable enterprise”; “U.S. AICPA GAAS”; “U.S. GAAP”; and “U.S. PCAOB GAAS”.
(3) In this Regulation, a person is considered to be an affiliate of another person if one of them controls the other, or if each of them is controlled by the same person.
(4) In this Regulation, a person (the first party) is considered to control another person (the second party) if any of the following apply:
(a) the first party beneficially owns or directly or indirectly exercises control or direction over securities of the second party carrying votes which, if exercised, would entitle the first party to elect a majority of the directors of the second party unless the first party holds the voting securities only to secure an obligation;
(b) the second party is a partnership, other than a limited partnership, and the first party holds more than 50% of the interests of the partnership;
(c) the second party is a limited partnership and the general partner of the limited partnership is the first party;
(d) the second party is a trust and a trustee of the trust is the first party.”;
(5) (paragraph repealed).
(6) In this Regulation, “associate” has the same meaning as in section 5 of the Securities Act (chapter V-1.1).
(7) In this Regulation, “interim period” has the same meaning as in section 1.1 of Regulation 51-102 respecting Continuous Disclosure Obligations (chapter V.1.1, r. 24).
M.O. 2013-21, s. 1; M.O. 2014-08, s. 1; M.O. 2016-10, s. 1 ; M.O. 2023-16, a. 1.
1.1. (Repealed).
M.O. 2013-21, s. 1.1; M.O. 2016-10, s. 2.
M.O. 2013-21, c. 2; I.N. 2014-01-01.
2. (1) An applicant for recognition under sections 12 and 14 of the Act must file a completed Form 91-507F1.
(2) In addition to the requirement set out in subsection (1), an applicant for recognition under sections 12 and 14 of the Act whose head office or principal place of business is located outside of Québec must
(a) certify on Form 91-507F1 that it will provide the Authority with access to its books and records and will submit to onsite inspection and examination by the Authority,
(b) certify on Form 91-507F1 that it will provide the Authority with an opinion of legal counsel that
(i) the applicant has the power and authority to provide the Authority with access to its books and records, and
(ii) the applicant has the power and authority to submit to onsite inspection and examination by the Authority.
(3) In addition to the requirements set out in subsections (1) and (2), an applicant for recognition under sections 12 and 14 of the Act whose head office or principal place of business is located in a foreign jurisdiction must file a completed Form 91-507F2.
(4) Within 7 days of becoming aware of an inaccuracy in or making a change to the information provided in Form 91-507F1, an applicant must file an amendment to Form 91-507F1 in the manner set out in that Form.
M.O. 2013-21, s. 2.
3. (1) Subject to subsection (2), a recognized trade repository must not implement a significant change to a matter set out in Form 91-507F1 unless it has filed an amendment to Form 91-507F1 in the manner set out in that Form at least 45 days before implementing the change.
(2) A recognized trade repository must file an amendment to the information provided in Exhibit I (Fees) of Form 91-507F1 in the manner set out in the Form at least 15 days before implementing a change to the information provided in the Exhibit.
(3) For a change to a matter set out in Form 91-507F1 other than a change referred to in subsection (1) or (2), a recognized trade repository must file an amendment to Form 91-507F1 in the manner set out in that Form by the earlier of
(a) the close of business of the recognized trade repository on the 10th day after the end of the month in which the change was made, and
(b) the time the recognized trade repository publicly discloses the change.
M.O. 2013-21, s. 3.
4. (1) An applicant must file audited financial statements for its most recently completed financial year with the Authority as part of its application for recognition under sections 12 and 14 of the Act.
(2) The financial statements referred to in subsection (1) must
(a) be prepared in accordance with one of the following
(i) Canadian GAAP applicable to a publicly accountable enterprise,
(ii) IFRS, or
(iii) U.S. GAAP, if the person is incorporated or organized under the laws of the United States of America or under the laws of a jurisdiction of the United States of America,
(b) identify in the notes to the financial statements the accounting principles used to prepare the financial statements,
(c) disclose the presentation currency, and
(d) be audited in accordance with
(i) Canadian GAAS,
(ii) International Standards on Auditing, or
(iii) U.S. AICPA GAAS or U.S. PCAOB GAAS if the person is incorporated or organized under the laws of the United States of America or under the laws of a jurisdiction of the United States of America.
(3) The financial statements referred to in subsection (1) must be accompanied by an auditor’s report that
(a) expresses an unmodified opinion if the financial statements are audited in accordance with Canadian GAAS or International Standards on Auditing,
(b) expresses an unqualified opinion if the financial statements are audited in accordance with U.S. AICPA GAAS or U.S. PCAOB GAAS,
(c) identifies all financial periods presented for which the auditor’s report applies,
(d) identifies the auditing standards used to conduct the audit,
(e) identifies the accounting principles used to prepare the financial statements,
(f) is prepared in accordance with the same auditing standards used to conduct the audit, and
(g) is prepared and signed by a person that is authorized to sign an auditor’s report under the laws of a jurisdiction of Canada or a foreign jurisdiction, and that meets the professional standards of that jurisdiction.
M.O. 2013-21, s. 4; M.O. 2016-10, s. 4.
5. (1) A recognized trade repository must file annual audited financial statements that comply with the requirements in subsections 4(2) and 4(3) with the Authority no later than the 90th day after the end of its financial year.
(2) A recognized trade repository must file interim financial statements with the Authority no later than the 45th day after the end of each interim period.
(3) The interim financial statements referred to in subsection (2) must
(a) be prepared in accordance with one of the following:
(i) Canadian GAAP applicable to a publicly accountable enterprise;
(ii) IFRS;
(iii) U.S. GAAP, if the person is incorporated under the laws of the United States of America or under the laws of a jurisdiction of the United States of America;
(b) identify in the notes to the financial statements the accounting principles used to prepare the financial statements.
M.O. 2013-21, s. 5; M.O. 2016-10, s. 5.
6. (1) A recognized trade repository that intends to cease carrying on business in Québec as a trade repository must make an application and file a report on Form 91-507F3 – Cessation of Operations Report For Trade Repository at least 180 days before the date on which it intends to cease carrying on that business.
(2) A recognized trade repository that involuntarily ceases to carry on business in Québec as a trade repository must file a report on Form 91-507F3 as soon as practicable after it ceases to carry on that business.
M.O. 2013-21, s. 6.
7. (1) A recognized trade repository must establish, implement, maintain and enforce written rules, policies and procedures reasonably designed to ensure a well-founded, clear, transparent, and enforceable legal basis for each material aspect of its activities.
(2) Without limiting the generality of subsection (1), a recognized trade repository must establish, implement, maintain and enforce written rules, policies and procedures that are not contrary to the public interest and that are reasonably designed to ensure that
(a) such rules, policies and procedures and the contractual arrangements are supported by the laws applicable to those rules, policies, procedures and contractual arrangements,
(b) the rights and obligations of a user, owner and regulator with respect to the use of the recognized trade repository’s information are clear and transparent,
(c) the contractual arrangements that it enters into and supporting documentation clearly state service levels, rights of access, protection of confidential information, intellectual property rights and operational reliability, and
(d) the status of records of contracts in its repository and whether those records of contracts are the legal contracts of record are clearly established.
M.O. 2013-21, s. 7.
8. (1) A recognized trade repository must establish, implement and maintain written governance arrangements that
(a) set out a clear organizational structure with consistent lines of responsibility,
(b) provide for effective internal controls,
(c) promote the safety and efficiency of the recognized trade repository,
(d) ensure effective oversight of the recognized trade repository, and
(e) support the stability of the broader financial system and other relevant public interest considerations.
(2) A recognized trade repository must establish, implement, maintain and enforce written rules, policies and procedures reasonably designed to identify and manage existing and potential conflicts of interest.
(3) A recognized trade repository must publicly disclose on its website
(a) the governance arrangements established in accordance with subsection (1), and
(b) the rules, policies and procedures established in accordance with subsection (2).
M.O. 2013-21, s. 8.
9. (1) A recognized trade repository must have a board of directors.
(2) The board of directors of a recognized trade repository must include
(a) individuals who have an appropriate level of skill and experience to effectively and efficiently oversee the management of its operations in accordance with all relevant laws, and
(b) appropriate representation by individuals who are independent of the recognized trade repository.
(3) The board of directors of a recognized trade repository must, in consultation with the chief compliance officer of the recognized trade repository, resolve conflicts of interest identified by the chief compliance officer.
(4) The board of directors of a recognized trade repository must meet with the chief compliance officer of the recognized trade repository on a regular basis.
M.O. 2013-21, s. 9.
10. (1) A recognized trade repository must establish, implement, maintain and enforce written rules, policies and procedures that
(a) specify the roles and responsibilities of management, and
(b) ensure that management has the experience, competencies, integrity as well as the skills necessary to discharge its roles and responsibilities.
(2) A recognized trade repository must notify the Authority no later than the 5th working day after appointing or replacing its chief compliance officer, chief executive officer or chief risk officer.
M.O. 2013-21, s. 10; I.N. 2016-01-01 (NCCP).
11. (1) The board of directors of a recognized trade repository must appoint a chief compliance officer with the appropriate experience, competencies, integrity as well as the skills necessary to serve in that capacity.
(2) The chief compliance officer of a recognized trade repository must report directly to the board of directors of the recognized trade repository or, if so directed by the board of directors, to the chief executive officer of the recognized trade repository.
(3) The chief compliance officer of a recognized trade repository must
(a) establish, implement, maintain and enforce written rules, policies and procedures to identify and resolve conflicts of interest,
(b) establish, implement, maintain and enforce written rules, policies and procedures to ensure that the recognized trade repository complies with securities legislation,
(c) monitor compliance with the rules, policies and procedures required under paragraphs (a) and (b) on an ongoing basis,
(d) report to the board of directors of the recognized trade repository as soon as practicable upon becoming aware of a circumstance indicating that the recognized trade repository, or an individual acting on its behalf, is not in compliance with the securities laws of a jurisdiction in which it operates and one or more of the following apply:
(i) the non-compliance creates a risk of harm to a user;
(ii) the non-compliance creates a risk of harm to the capital markets;
(iii) the non-compliance is part of a pattern of non-compliance;
(iv) the non-compliance may have an impact on the ability of the recognized trade repository to carry on business as a trade repository in compliance with securities legislation,
(e) report to the recognized trade repository’s board of directors as soon as practicable upon becoming aware of a conflict of interest that creates a risk of harm to a user or to the capital markets, and
(f) prepare and certify an annual report assessing compliance by the recognized trade repository, and individuals acting on its behalf, with securities legislation and submit the report to the board of directors.
(4) Concurrently with submitting a report under paragraph (3)(d), (3)(e) or (3)(f), the chief compliance officer must file a copy of the report with the Authority.
M.O. 2013-21, s. 11.
12. All fees and other material costs imposed by a recognized trade repository on its participants must be
(a) fairly and equitably allocated among participants, and
(b) publicly disclosed on its website for each service it offers with respect to the collection and maintenance of derivatives data.
M.O. 2013-21, s. 12.
13. (1) A recognized trade repository must establish, implement, maintain and enforce written rules, policies and procedures that establish objective, risk-based criteria for participation that permit fair and open access to the services it provides.
(2) A recognized trade repository must publicly disclose on its website the rules, policies and procedures referred to in subsection (1).
(3) A recognized trade repository must not do any of the following:
(a) unreasonably prohibit, condition or limit access by a person to the services offered by the recognized trade repository;
(b) permit unreasonable discrimination among the participants of the recognized trade repository;
(c) impose a burden on competition that is not reasonably necessary and appropriate;
(c) require the use or purchase of another service for a person to utilize the trade reporting service offered by the recognized trade repository.
M.O. 2013-21, s. 13.
14. A recognized trade repository must accept derivatives data from a participant for a transaction in a derivative of the asset class or classes set out in the recognized trade repository’s recognition order.
M.O. 2013-21, s. 14.
15. A recognized trade repository must use or accommodate relevant internationally accepted communication procedures and standards in order to facilitate the efficient exchange of data between its systems and those of
(a) the participants,
(b) other trade repositories,
(c) exchanges, clearing houses, alternative trading systems, and other marketplaces, and
(d) other service providers.
M.O. 2013-21, s. 15.
16. For a decision made by a recognized trade repository that directly adversely affects a participant or an applicant that applies to become a participant, the recognized trade repository must ensure that
(a) the participant or applicant is given an opportunity to be heard or make representations, and
(b) it keeps records of, gives reasons for, and provides for reviews of its decisions, including, for each applicant or participant, the reasons for granting, denying or limiting access.
M.O. 2013-21, s. 16.
17. (1) The rules, policies and procedures of a recognized trade repository must
(a) provide sufficient information to enable a participant to have an accurate understanding of its rights and obligations in accessing the services of the recognized trade repository and the risks, fees, and other material costs they incur by using the services of the recognized trade repository,
(b) be reasonably designed to govern all aspects of the services offered by the recognized trade repository with respect to the collection and maintenance of derivatives data and other information on a completed transaction, and
(c) not be inconsistent with securities legislation.
(2) A recognized trade repository must monitor compliance with its rules, policies and procedures on an ongoing basis.
(3) A recognized trade repository must establish, implement, maintain and enforce written rules, policies and procedures for sanctioning non-compliance with its rules, policies and procedures.
(4) A recognized trade repository must publicly disclose on its website
(a) its rules, policies and procedures referred to in this section, and
(b) its procedures for adopting new rules, policies and procedures or amending existing rules, policies and procedures.
M.O. 2013-21, s. 17.
18. (1) A recognized trade repository must design its recordkeeping procedures to ensure that it records derivatives data accurately, completely and on a timely basis.
(2) A recognized trade repository must keep, in a safe location and in a durable form, records of derivatives data in relation to a transaction for the life of the transaction and for a further 7 years after the date on which the transaction expires or terminates.
(3) Throughout the period described in subsection (2), a recognized trade repository must create and maintain at least one copy of each record of derivatives data required to be kept under subsection (2), in a safe location and in a durable form, separate from the location of the original record.
M.O. 2013-21, s. 18.
19. A recognized trade repository must establish, implement and maintain a written risk-management framework for comprehensively managing risks including business, legal, and operational risks.
M.O. 2013-21, s. 19.
20. (1) A recognized trade repository must establish, implement and maintain appropriate systems, controls and procedures to identify, monitor, and manage its general business risk.
(2) Without limiting the generality of subsection (1), a recognized trade repository must hold sufficient insurance coverage and liquid net assets funded by equity to cover potential general business losses in order that it can continue operations and services as a going concern in order to achieve a recovery or an orderly wind down if those losses materialize.
(3) For the purposes of subsection (2), a recognized trade repository must hold, at a minimum, liquid net assets funded by equity equal to 6 months of current operating expenses.
(4) A recognized trade repository must identify scenarios that may potentially prevent it from being able to provide its critical operations and services as a going concern and assess the effectiveness of a full range of options for an orderly wind-down.
(5) A recognized trade repository must establish, implement, maintain and enforce written rules, policies and procedures reasonably designed to facilitate its orderly wind-down based on the results of the assessment required by subsection (4).
(6) A recognized trade repository must establish, implement, maintain and enforce written rules, policies and procedures to ensure that it or a successor entity, insolvency administrator or other legal representative, will continue to comply with the requirements of subsection 6(2) and section 37 in the event of the bankruptcy or insolvency of the recognized trade repository or the wind-down of the recognized trade repository’s operations.
M.O. 2013-21, s. 20.
21. (1) A recognized trade repository must establish, implement, maintain and enforce appropriate systems, controls and procedures to identify and minimize the impact of all plausible sources of operational risk, both internal and external, including risks to data integrity, data security, business continuity and capacity and performance management.
(2) The systems, controls and procedures established pursuant to subsection (1) must be approved by the board of directors of the recognized trade repository.
(3) Without limiting the generality of subsection (1), a recognized trade repository must
(a) develop and maintain
(i) an adequate system of internal controls over its systems, and
(ii) adequate information technology general controls, including without limitation, controls relating to information systems operations, information security and integrity, change management, problem management, network support and system software support,
(b) in accordance with prudent business practice, on a reasonably frequent basis and, in any event, at least annually
(i) make reasonable current and future capacity estimates, and
(ii) conduct capacity stress tests to determine the ability of those systems to process transactions in an accurate, timely and efficient manner, and
(c) promptly notify the Authority of a material systems failure, malfunction, delay or other disruptive incident, or a breach of data security, integrity or confidentiality, and provide a post-incident report that includes a root-cause analysis as soon as practicable.
(4) Without limiting the generality of subsection (1), a recognized trade repository must establish, implement, maintain and enforce business continuity plans, including disaster recovery plans reasonably designed to
(a) achieve prompt recovery of its operations following a disruption,
(b) allow for the timely recovery of information, including derivatives data, in the event of a disruption, and
(c) provide for the exercise of authority in the event of an emergency.
(5) A recognized trade repository must test its business continuity plans, including disaster recovery plans, at least annually.
(6) For each of its systems for collecting and maintaining reports of derivatives data, a recognized trade repository must annually engage a qualified party to conduct an independent review and prepare a report in accordance with established audit standards to ensure that it is in compliance with paragraphs (3)(a) and (b) and subsections (4) and (5).
(7) A recognized trade repository must provide the report prepared in accordance with subsection (6) to
(a) its board of directors or audit committee promptly upon the completion of the report, and
(b) the Authority not later than the 30th day after providing the report to its board of directors or audit committee.
(8) A recognized trade repository must publicly disclose on its website all technology requirements regarding interfacing with or accessing the services provided by the recognized trade repository,
(a) if operations have not begun, sufficiently in advance of operations to allow a reasonable period for testing and system modification by participants, and
(b) if operations have begun, sufficiently in advance of implementing a material change to technology requirements to allow a reasonable period for testing and system modification by participants.
(9) A recognized trade repository must make available testing facilities for interfacing with or accessing the services provided by the recognized trade repository,
(a) if operations have not begun, sufficiently in advance of operations to allow a reasonable period for testing and system modification by participants, and
(b) if operations have begun, sufficiently in advance of implementing a material change to technology requirements to allow a reasonable period for testing and system modification by participants.
(10) A recognized trade repository must not begin operations in Québec unless it has complied with paragraphs (8)(a) and (9)(a).
(11) Paragraphs (8)(b) and (9)(b) do not apply to a recognized trade repository if
(a) the change to its technology requirements must be made immediately to address a failure, malfunction or material delay of its systems or equipment,
(b) the recognized trade repository immediately notifies the Authority of its intention to make the change to its technology requirements, and
(c) the recognized trade repository publicly discloses on its website the changed technology requirements as soon as practicable.
M.O. 2013-21, s. 21.
22. (1) A recognized trade repository must establish, implement, maintain and enforce written rules, policies and procedures reasonably designed to ensure the safety, privacy and confidentiality of the derivatives data.
(2) A recognized trade repository must not release derivatives data for commercial or business purposes unless
(a) the derivatives data has otherwise been disclosed pursuant to section 39, or
(b) the counterparties to the transaction have provided the recognized trade repository with their express written consent to use or release the derivatives data.
M.O. 2013-21, s. 22.
23. (1) A recognized trade repository must establish, implement, maintain and enforce written rules, policies and procedures to confirm with each counterparty to a transaction, or agent acting on behalf of such counterparty, that the derivatives data that the recognized trade repository receives from a reporting counterparty, or from a party to whom a reporting counterparty has delegated its reporting obligation under this Regulation, is accurate.
(2) Despite subsection (1), a recognized trade repository need only confirm the accuracy of the derivatives data it receives with those counterparties that are participants of the recognized trade repository.
M.O. 2013-21, s. 23; M.O. 2016-10, s. 7.
24. If a recognized trade repository outsources a material service or system to a service provider, including to an associate or affiliate of the recognized trade repository, the recognized trade repository must
(a) establish, implement, maintain and enforce written rules, policies and procedures for the selection of a service provider to which a material service or system may be outsourced and for the evaluation and approval of such an outsourcing arrangement,
(b) identify any conflicts of interest between the recognized trade repository and a service provider to which a material service or system is outsourced, and establish, implement, maintain and enforce written rules, policies and procedures to mitigate and manage those conflicts of interest,
(c) enter into a written contract with the service provider that is appropriate for the materiality and nature of the outsourced activity and that provides for adequate termination procedures,
(d) maintain access to the books and records of the service provider relating to the outsourced activity,
(e) ensure that the Authority has the same access to all data, information and systems maintained by the service provider on behalf of the recognized trade repository that it would have absent the outsourcing arrangement,
(f) ensure that all persons conducting audits or independent reviews of the recognized trade repository under this Regulation have appropriate access to all data, information and systems maintained by the service provider on behalf of the recognized trade repository that such persons would have absent the outsourcing arrangement,
(g) take appropriate measures to determine that a service provider to which a material service or system is outsourced establishes, maintains and periodically tests an appropriate business continuity plan, including a disaster recovery plan in accordance with the requirements under section 21,
(h) take appropriate measures to ensure that the service provider protects the safety, privacy and confidentiality of derivatives data and of users’ confidential information in accordance with the requirements under section 22, and
(i) establish, implement, maintain and enforce written rules, policies and procedures to regularly review the performance of the service provider under the outsourcing arrangement.
M.O. 2013-21, s. 24.
M.O. 2013-21, c. 3; I.N. 2014-01-01.
25. (1) If a transaction involving a local counterparty is cleared through a reporting clearing house, the reporting counterparty with respect to that transaction is the reporting clearing house.
(2) If a transaction involving a local counterparty is not cleared through a reporting clearing house, the reporting counterparty with respect to that transaction is
(a) if only one counterparty to the transaction is a person subject to the registration requirement as a dealer under the Act, the person subject to such registration requirement,
(b) if neither counterparty to the transaction is a person subject to the registration requirement as a dealer under the Act, and only one counterparty to the transaction is a Canadian financial institution or a Schedule III bank, the Canadian financial institution of the Schedule III bank.
(3) If neither subsection (1) nor (2) apply to a transaction involving a local counterparty the reporting counterparty with respect to that transaction is, where both counterparties have, at the time the transaction occurs, entered into a written agreement whereby one of the counterparties undertakes to act as the reporting counterparty for the purposes of fulfilling the reporting obligation under this Regulation, the counterparty determined to be the reporting counterparty under the terms of that agreement.
(4) If none of subsections (1) to (3) apply to a transaction involving a local counterparty, the reporting counterparty with respect to that transaction is each local counterparty to the transaction.
M.O. 2013-21, s. 25; I.N. 2014-01-01; M.O. 2014-08, s. 2.
26. (1) A reporting counterparty to a transaction involving a local counterparty must report, or cause to be reported, the data required to be reported under this Chapter to a recognized trade repository.
(2) A reporting counterparty in respect of a transaction is responsible for ensuring that all reporting obligations in respect of that transaction have been fulfilled.
(3) A reporting counterparty may delegate its reporting obligations under this Regulation, but remains responsible for ensuring the timely and accurate reporting of derivatives data required by this Regulation.
(4) Despite subsection (1), if no recognized trade repository accepts the data required to be reported by this Chapter, the reporting counterparty must electronically report the data required to be reported by this Chapter to the Authority.
(5) A reporting counterparty satisfies the reporting obligation in respect of a transaction required to be reported under subsection (1) if
(a) the transaction is required to be reported solely because a counterparty to the transaction is a local counterparty pursuant to paragraph (b) or (c) of the definition of “local counterparty”,
(b) the transaction is reported to a recognized trade repository pursuant to
(i) the securities legislation of a province of Canada other than Québec, or
(ii) the laws of a foreign jurisdiction appearing on a list determined by the Authority; and
(c) the reporting counterparty instructs the recognized trade repository referred to in paragraph (b) to provide the Authority with access to the data that is reported pursuant to paragraph (b) and otherwise uses its best efforts to provide the Authority with access to such data.
(6) A reporting counterparty must ensure that all reported derivatives data relating to a transaction
(a) is reported to the same recognized trade repository or, if reported to the Authority under subsection (4), to the Authority, and
(b) is accurate and contains no misrepresentation.
(7) A reporting counterparty must report an error or omission in the derivatives data as soon as technologically practicable upon discovery of the error or omission, and in no event later than the end of the working day following the day of discovery of the error or omission.
(8) A local counterparty, other than the reporting counterparty, must notify the reporting counterparty of an error or omission with respect to derivatives data relating to a transaction to which it is a counterparty as soon as technologically practicable upon discovery of the error or omission, and in no event later than the end of the working day following the day of discovery of the error or omission.
(9) A reporting clearing house must report derivatives data to the recognized trade repository specified by a local counterparty and may not report derivatives data to another trade repository without the consent of the local counterparty where
(a) the reporting counterparty to a transaction is a reporting clearing house, and
(b) the local counterparty to the transaction that is not a reporting clearing house has specified a recognized trade repository to which derivatives data in respect of that transaction is to be reported.
M.O. 2013-21, s. 26; M.O. 2014-08, s. 3; I.N. 2016-01-01 (NCCP); M.O 2016-10, s. 8.
27. A reporting counterparty must include the following in every report required by this Chapter:
(a) the legal entity identifier of each counterparty to the transaction as set out in section 28;
(b) the unique transaction identifier for the transaction as set out in section 29;
(c) the unique product identifier for the transaction as set out in section 30.
M.O. 2013-21, s. 27.
28. (1) A recognized trade repository must identify each counterparty to a transaction that is required to be reported under this Regulation in all recordkeeping and all reporting required under this Regulation by means of a single legal entity identifier.
(2) Each of the following rules apply to legal entity identifiers
(a) a legal entity identifier must be a unique identification code assigned to a counterparty in accordance with the standards set by the Global Legal Entity Identifier System, and
(b) a local counterparty must comply with all applicable requirements imposed by the Global Legal Entity Identifier System.
(3) Despite subsection (2), if the Global Legal Entity Identifier System is unavailable to a counterparty to a transaction at the time when a report under this Regulation is required to be made, all of the following rules apply
(a) each counterparty to the transaction must obtain a substitute legal entity identifier which complies with the standards established March 8, 2013 by the Legal Entity Identifier Regulatory Oversight Committee for pre-legal entity identifiers,
(b) a local counterparty must use the substitute legal entity identifier until a legal entity identifier is assigned to the counterparty in accordance with the standards set by the Global Legal Entity Identifier System as required under paragraph (2)(a), and
(c) after the holder of a substitute legal entity identifier is assigned a legal entity identifier in accordance with the standards set by the Global Legal Entity Identifier System as required under paragraph (2)(a), the local counterparty must ensure that it is identified only by the assigned legal entity identifier in all derivatives data reported pursuant to this Regulation in respect of transactions to which it is a counterparty.
(4) If a counterparty to a transaction is an individual or is not eligible to receive a legal entity identifier as determined by the Global Legal Entity Identifier System, the reporting counterparty must identify such a counterparty with an alternate identifier.
(5) If paragraph (4) applies, then despite paragraph (1), the recognized trade repository must identify such a counterparty with the alternate identifier supplied by the reporting counterparty.
[M.O] 2013-21, s. 28; M.O. 2016-10, s. 9.
28.1. Each local counterparty to a transaction required to be reported under this Regulation that is eligible to receive a legal entity identifier as determined by the Global Legal Entity Identifier System, other than an individual, must obtain, maintain and renew a legal identity identifier assigned to the counterparty in accordance with the standards set by the Global Legal Entity Identifier System.
[M.O] 2016-10, s. 10.
29. (1) A recognized trade repository must identify each transaction that is required to be reported under this Regulation in all recordkeeping and all reporting required under this Regulation by means of a unique transaction identifier.
(2) A recognized trade repository must assign a unique transaction identifier to a transaction, using its own methodology or incorporating a unique transaction identifier previously assigned to the transaction.
(3) A recognized trade repository must not assign more than one unique transaction identifier to a transaction.
M.O. 2013-21, s. 29.
30. (1) For the purposes of this section, a unique product identifier means a code that uniquely identifies a derivative and is assigned in accordance with international or industry standards.
(2) A reporting counterparty must identify each transaction that is required to be reported under this Regulation in all recordkeeping and all reporting required under this Regulation by means of a unique product identifier.
(3) A reporting counterparty must not assign more than one unique product identifier to a transaction.
(4) If international or industry standards for a unique product identifier are unavailable for a particular derivative when a report is required to be made to a recognized trade repository under this Regulation, a reporting counterparty must assign a unique product identifier to the transaction using its own methodology.
M.O. 2013-21, s. 30.
31. (1) Upon execution of a transaction that is required to be reported under this Regulation, a reporting counterparty must report the creation data relating to that transaction to a recognized trade repository.
(2) A reporting counterparty in respect of a transaction must report creation data in real time.
(3) If it is not technologically practicable to report creation data in real time, a reporting counterparty must report creation data as soon as technologically practicable and in no event later than the end of the working day following the day on which the data would otherwise be required to be reported.
(4) (Paragraph revoked).
M.O. 2013-21, s. 31; M.O. 2014-08, s. 4; I.N. 2016-01-01 (NCCP).
32. (1) For a transaction that is required to be reported under this Regulation, the reporting counterparty must report all life-cycle event data to a recognized trade repository by the end of the working day on which the life-cycle event occurs.
(2) If it is not technologically practicable to report life-cycle event data by the end of the working day on which the life-cycle event occurs, the reporting counterparty must report life-cycle event data no later than the end of the working day following the day on which the life-cycle event occurs.
M.O. 2013-21, s. 32; I.N. 2016-01-01 (NCCP).
33. (1) For a transaction that is required to be reported under this Regulation, a reporting counterparty must report valuation data, based on industry accepted valuation standards, to a recognized trade repository
(a) daily, based on relevant closing market data from the previous business day, if the reporting counterparty is either a reporting clearing house or a person subject to the registration requirement as a dealer under the Act, or a Canadian financial institution or a Schedule III bank, or
(b) quarterly, as of the last day of each calendar quarter, if the reporting counterparty is neither a reporting clearing house, nor a person subject to the registration requirement as a dealer under the Act, nor a Canadian financial institution, nor a Schedule III bank.
(2) Valuation data required to be reported pursuant to paragraph 1(b) must be reported to the recognized trade repository no later than 30 days after the end of the calendar quarter.
M.O. 2013-21, s. 33; I.N. 2016-01-01 (NCCP); M.O. 2016-10, s. 11; M.O. 2023-16, s. 3.
34. (1) Despite section 31 and subject to subsection 42(4), a reporting counterparty is required to report only the creation data indicated in the column in Appendix A entitled “Required for Pre-existing Transactions” on or before April 30, 2015 if
(a) the reporting counterparty is a reporting clearing house, a person subject to the registration requirement as a dealer under the Act or a Canadian financial institution,
(b) the transaction was entered into before October 31, 2014, and
(c) there were outstanding contractual obligations with respect to that transaction on October 31, 2014.
(1.1) Despite section 31 and subject to subsection 42(5), a reporting counterparty is required to report only the creation data indicated in the column in Appendix A entitled “Required for Pre-existing Transactions” on or before December 31, 2015 if
(a) the reporting counterparty is neither a reporting clearing house, nor a person subject to the registration requirement as a dealer under the Act, nor a Canadian financial institution,
(b) the transaction was entered into before June 30, 2015, and
(c) there were outstanding contractual obligations with respect to the transaction on June 30, 2015.
(2) Despite section 32, for a transaction to which subsection (1) or (1.1) applies, a reporting counterparty’s obligation to report life-cycle event data under section 32 commences only after it has reported creation data in accordance with subsection (1) or (1.1).
(3) Despite section 33, for a transaction to which subsection (1) or (1.1) applies, a reporting counterparty’s obligation to report valuation data under section 33 commences only after it has reported creation data in accordance with subsection (1) or (1.1).
M.O. 2013-21, s. 34; I.N. 2014-04-01; M.O. 2014-08, s. 5.
35. Despite the data reporting timing requirements in sections 31, 32, 33 and 34, where a recognized trade repository ceases operations or stops accepting derivatives data for a certain asset class of derivatives, the reporting counterparty may fulfill its reporting obligations under this Regulation by reporting the derivatives data to another recognized trade repository or the Authority, if there are no available recognized trade repository, within a reasonable period of time.
M.O. 2013-21, s. 35.
36. (1) A reporting counterparty must keep transaction records for the life of each transaction and for a further 7 years after the date on which the transaction expires or terminates.
(2) A reporting counterparty must keep records referred to in subsection (1) in a safe location and in a durable form.
M.O. 2013-21, s. 36.
M.O. 2013-21, c. 4; I.N. 2014-01-01.
37. (1) A recognized trade repository must, at no cost
(a) provide to the Authority direct, continuous and timely electronic access to such data in the recognized trade repository’s possession as is required by the Authority in order to carry out the Authority’s mandate,
(b) create and make available to the Authority aggregate data derived from data in the recognized trade repository’s possession as required by the Authority in order to carry out the Authority’s mandate, and
(c) disclose to the Authority the manner in which the derivatives data provided under paragraph (c) has been aggregated.
(2) A recognized trade repository must conform to internationally accepted regulatory access standards applicable to trade repositories.
(3) A reporting counterparty must use its best efforts to provide the Authority with access to all derivatives data that it is required to report pursuant to this Regulation, including instructing a trade repository to provide the Authority with access to such data.
M.O. 2013-21, s. 37.
38. (1) A recognized trade repository must provide counterparties to a transaction with timely access to all derivatives data relevant to that transaction which is submitted to the recognized trade repository.
(2) A recognized trade repository must have appropriate verification and authorization procedures in place to deal with access pursuant to subsection (1) by non-reporting counterparties or a party acting on behalf of a non-reporting counterparty.
(3) Each counterparty to a transaction is deemed to have consented to the release of all derivatives data required to be reported or disclosed under this Regulation.
(4) Subsection (3) applies despite any agreement to the contrary between the counterparties to a transaction.
M.O. 2013-21, s. 38.
39. (1) A recognized trade repository must, on a periodic basis, create and make available to the public, at no cost, aggregate data on open positions, volume, number and where applicable, price, relating to the transactions reported to it pursuant to this Regulation.
(2) The periodic aggregate data made available to the public pursuant to subsection (1) must be complemented at a minimum by breakdowns, where applicable, by currency of denomination, geographic location of reference entity or asset, asset class, contract type, maturity and whether the transaction is cleared.
(3) For each transaction reported pursuant to this Regulation, a recognized trade repository must make transaction level reports available to the public at no cost, in accordance with the requirements in Appendix C.
(4) In disclosing transaction level reports required by subsection (3), a recognized trade repository must not disclose the identity of either counterparty to the transaction.
(5) A recognized trade repository must make the data required to be made available to the public under this section available in a usable form through a publicly accessible website or other publicly accessible technology or medium.
(6) Despite subsections (1) to (5), a recognized trade repository is not required to make public any derivatives data for transactions entered into between affiliated persons.
M.O. 2013-21, s. 39; M.O. 2016-10, s. 13.
M.O. 2013-21, c. 5; I.N. 2014-01-01.
40. Despite any other section of this Regulation, a local counterparty is under no obligation to report derivatives data for a transaction if,
(a) the transaction relates to a derivative the asset class of which is a commodity other than cash or currency,
(b) the local counterparty is neither a reporting clearing house, nor a person subject to the registration requirement as a dealer under the Act, nor a Canadian financial institution, nor a Schedule III bank, and
(c) the local counterparty has less than $500,000 aggregate notional value, without netting, under all its outstanding transactions at the time of the transaction including the additional notional value related to that transaction.
M.O. 2013-21, s. 40; M.O. 2016-10, s. 14 ; M.O. 2023-16, s. 4.
41. The following counterparties are excluded from the application of this Regulation:
(a) the Gouvernement du Québec;
(b) a body referred to in paragraph 2 of section 77 of the Financial Administration Act (chapter A-6.001);
(c) a municipality, a metropolitan community, a school board or the Comité de gestion de la taxe scolaire de l'île de Montréal;
(d) a transit authority established under an Act of Québec;
(e) a public institution or regional council within the meaning of the Act respecting health services and social services for Cree Native persons (chapter S-5), a public institution or a health and social services agency referred to in the Act respecting health services and social services (chapter S-4.2), or the Corporation d’hébergement du Québec;
(f) a Québec university;
(g) a general and vocational college;
(h) an intermunicipal management board.
M.O. 2013-21, s. 41.
M.O. 2013-21, c. 6; I.N. 2014-01-01.
42. (1) This Regulation comes into force on December 31, 2013, except for Chapters 3 and 5 which come into force on October 31, 2014.
(2) Despite subsection (1), subsection 39(3) does not apply until January 16, 2017.
(3) A reporting counterparty that is neither a reporting clearing house, nor a person subject to the registration requirement as a dealer under the Act, nor a Canadian financial institution is not required to make any reports under Chapter 3 until June 30, 2015.
(4) Chapter 3 does not apply to a transaction entered into before October 31, 2014 that expires or terminates on or before April 30, 2015 if the reporting counterparty is a reporting clearing house, a person subject to the registration requirement as a dealer under the Act or a Canadian financial institution.
(5) Chapter 3 does not apply to a transaction entered into before June 30, 2015 that expires or terminates on or before December 31, 2015 if the reporting counterparty is neither a reporting clearing house, nor a person subject to the registration requirement as a dealer under the Act, nor a Canadian financial institution.
[*] M.O. 2013-21, s. 42; M.O. 2014-08, s. 6; M.O. 2016-10, s. 15.
Instructions: The reporting counterparty is required to provide a response for each of the fields unless the field is not applicable to the transaction.
| Data field | Description | Required for Pre-existing Transactions |
|---|---|---|
| Transaction identifier | The unique transaction identifier as provided by the recognized trade repository or the identifier as identified by the 2 counterparties, electronic trading venue of execution or clearing house. | Y |
| Master agreement type | The type of master agreement, if used for the reported transaction. | N |
| Master agreement version | Date of the master agreement version (e.g. 2002, 2006). | N |
| Cleared | Indicate whether the transaction has been cleared by a clearing house. | Y |
| Intent to clear | Indicate whether the transaction will be cleared by a clearing house. | N |
| Clearing house | LEI of the clearing house where the transaction is or will be cleared. | Y |
| Clearing member | LEI of the clearing member, if the clearing member is not a counterparty. | N |
| Clearing exemption | Indicate whether one or more of the counterparties to the transaction are exempted from a mandatory clearing requirement. | N |
| Data field | Description | Required for Pre-existing Transactions |
|---|---|---|
| Broker/Clearing intermediary | LEI of the broker acting as an intermediary for the reporting counterparty without becoming a counterparty. | N |
| Electronic trading venue identifier | LEI of the electronic trading venue where the transaction was executed. | Y |
| Inter-affiliate | Indicate whether the transaction is between 2 affiliated persons. (This field is only required to be reported as of April 30, 2015.) | N |
| Collateralization | Indicate whether the transaction is collateralized. Field Values: ● Fully (initial and variation margin required to be posted by both parties), ● Partially (variation only required to be posted by both parties), ● One way (one party will be required to post some form of collateral), ● Uncollateralized. | N |
| Identifier of reporting counterparty | LEI of the reporting counterparty or, in the case of an individual or a counterparty that is not eligible to receive an LEI, an alternate identifier. | Y |
| Identifier of non-reporting counterparty | LEI of the non-reporting counterparty or, in the case of an individual or a counterparty that is not eligible to receive an LEI, an alternate identifier. | Y |
| Counterparty side | Indicate whether the reporting counterparty was the buyer or seller. In the case of swaps, other than credit default, the buyer will represent the payer of leg 1 and the seller will be the payer of leg 2. | Y |
| Data field | Description | Required for Pre-existing Transactions |
|---|---|---|
| Identifier of agent reporting the transaction | LEI of the agent reporting the transaction if reporting of the transaction has been delegated by the reporting counterparty. | N |
| Jurisdiction of reporting counterparty | If the reporting counterparty is a local counterparty under this Regulation or the derivatives data reporting rules of Ontario or Manitoba, or is a local counterparty under paragraph (a) or (c) of the definition of local counterparty in the derivatives data reporting rules of any other jurisdiction of Canada, indicate all such jurisdictions. | N |
| Jurisdiction of non-reporting counterparty | If the non-reporting counterparty is a local counterparty under this Regulation or the derivatives data reporting rules of Ontario or Manitoba, or is a local counterparty under paragraph (a) or (c) of the definition of local counterparty in the derivatives data reporting rules of any other jurisdiction of Canada, indicate all such jurisdictions. | N |
| A. Common Data | • These fields are required to be reported for all derivative transactions even if the information may be entered in an Asset field below. • Fields do not have to be reported if the unique product identifier adequately describes those fields. | |
| Unique product identifier | Unique product identification code based on the taxonomy of the product. | N |
| Contract or instrument type | The name of the contract or instrument type (e.g., swap, swaption, forwards, options, basis swap, index swap, basket swap, other). | Y |
| Underlying asset identifier 1 | The unique identifier of the asset referenced in the transaction. | Y |
| Data field | Description | Required for Pre-existing Transactions |
|---|---|---|
| Underlying asset identifier 2 | The unique identifier of the second asset referenced in the transaction, if more than one. If more than two assets identified in the transaction, report the unique identifiers for those additional underlying assets. | Y |
| Asset class | Major asset class of the product (e.g., interest rate, credit, commodity, foreign exchange, equity, etc.). | N |
| Effective date or start date | The date the transaction becomes effective or starts. | Y |
| Maturity, termination or end date | The date the transaction expires. | Y |
| Payment frequency or dates | The dates or frequency the transaction requires payments to be made (e.g., quarterly, monthly). | Y |
| Reset frequency or dates | The dates or frequency at which the price resets (e.g., quarterly, semi-annually, annually). | Y |
| Day count convention | Factor used to calculate the payments (e.g., 30/360, actual/360). | Y |
| Delivery type | Indicate whether transaction is settled physically or in cash. | Y |
| Price 1 | The price, yield, spread, coupon, etc., of the derivative. The price/rate should not include any premiums such as commissions, collateral premiums, accrued interest, etc. | Y |
| Price 2 | The price, yield, spread, coupon, etc., of the derivative. The price/rate should not include any premiums such as commissions, collateral premiums, accrued interest, etc. | Y |
| Data field | Description | Required for Pre-existing Transactions |
|---|---|---|
| Price notation type 1 | The manner in which the price is expressed (e.g., percent, basis points, etc.). | Y |
| Price notation type 2 | The manner in which the price is expressed (e.g., percent, basis points, etc.). | Y |
| Price multiplier | The number of units of the underlying reference entity represented by 1 unit of the transaction. | N |
| Notional amount leg 1 | Total notional amount(s) of leg 1 of the transaction. | Y |
| Notional amount leg 2 | Total notional amount(s) of leg 2 of the transaction. | Y |
| Currency leg 1 | Currency(ies) of leg 1. | Y |
| Currency leg 2 | Currency(ies) of leg 2. | Y |
| Settlement currency | The currency used to determine the cash settlement amount. | Y |
| Up-front payment | Amount of any up-front payment. | N |
| Currency or currencies of up-front payment | The currency in which any up-front payment is made by one counterparty to another. | N |
| Embedded option | Indicate whether the option is an embedded option. | N |
| B. Additional Asset Information | These additional fields are required to be reported for transactions in the respective types of derivatives set out below, even if the information is entered in a Common Data field above. | |
| i) Interest rate derivatives |
| Data field | Description | Required for Pre-existing Transactions |
|---|---|---|
| Fixed rate leg 1 | The rate used to determine the payment amount for leg 1 of the transaction. | Y |
| Fixed rate leg 2 | The rate used to determine the payment amount for leg 2 of the transaction. | Y |
| Floating rate leg 1 | The floating rate used to determine the payment amount for leg 1 of the transaction. | Y |
| Floating rate leg 2 | The floating rate used to determine the payment amount for leg 2 of the transaction. | Y |
| Fixed rate day count convention | Factor used to calculate the fixed payer payments (e.g., 30/360, actual/360). | Y |
| Fixed leg payment frequency or dates | Frequency or dates of payments for the fixed rate leg of the transaction (e.g., quarterly, semi-annually, annually). | Y |
| Floating leg payment frequency or dates | Frequency or dates of payments for the floating rate leg of the transaction (e.g., quarterly, semi-annually, annually). | Y |
| Floating rate reset frequency or dates | The dates or frequency at which the floating leg of the transaction resets (e.g., quarterly, semi-annually, annually). | Y |
| ii) Currency derivatives | ||
| Exchange rate | Contractual rate(s) of exchange of the currencies. | Y |
| iii) Commodity derivatives |
| Data field | Description | Required for Pre-existing Transactions |
|---|---|---|
| Sub-asset class | Specific information to identify the type of commodity derivative (e.g., Agriculture, Power, Oil, Natural Gas, Freights, Metals, Index, Environmental, Exotic). | Y |
| Quantity | Total quantity in the unit of measure of an underlying commodity. | Y |
| Unit of measure | Unit of measure for the quantity of each side of the transaction (e.g., barrels, bushels, etc.). | Y |
| Grade | Grade of product being delivered (e.g., grade of oil). | Y |
| Delivery point | The delivery location. | N |
| Load type | For power, load profile for the delivery. | Y |
| Transmission days | For power, the delivery days of the week. | Y |
| Transmission duration | For power, the hours of day transmission starts and ends. | Y |
| C. Options | These additional fields are required to be reported for options transactions set out below, even if the information is entered in a Common Data field above. | |
| Option exercise date | The date(s) on which the option may be exercised. | Y |
| Option premium | Fixed premium paid by the buyer to the seller. | Y |
| Strike price (cap/floor rate) | The strike price of the option. | Y |
| Option style | Indicate whether the option can be exercised on a fixed date or anytime during the life of the transaction (e.g., American, European, Bermudan, Asian). | Y |
| Data field | Description | Required for Pre-existing Transactions |
|---|---|---|
| Option type | Put/call. | Y |
| D. Event Data | ||
| Action | Describes the type of event to the transaction (e.g., new transaction, modification or cancellation of existing transaction, etc.). | N |
| Execution timestamp | The time and date of execution or novation of a transaction, expressed using Coordinated Universal Time (UTC). | Y (If available) |
| Post-transaction events | Indicate whether the transaction resulted from a post-transaction service (e.g. compression, reconciliation, etc.) or from a lifecycle event (e.g. novation, amendment, etc.). | N |
| Reporting timestamp | The time and date the transaction was submitted to the trade repository, expressed using UTC. | N |
| E. Valuation data | These additional fields are required to be reported on a continuing basis for all reported derivative transactions, including reported pre-existing transactions. | |
| Value of transaction calculated by the reporting counterparty | Mark-to-market valuation of the transaction, or mark-to-model valuation. | N |
| Valuation currency | Indicate the currency used when reporting the value of the transaction. | N |
| Valuation date | Date of the latest mark-to-market or mark-to-model valuation. | N |
| F. Other details |
| Data field | Description | Required for Pre-existing Transactions |
|---|---|---|
| Where the terms of the transaction cannot be effectively reported in the above prescribed fields, provide any additional information that may be necessary. | Y |
M.O. 2013-21, Sch. A; M.O. 2014-08, s. 7; M.O. 2016-10, s. 16.
M.O. 2013-21, Sch. B; M.O. 2014-08, s. 8.
1. A recognized trade repository is required to disseminate to the public at no cost the information contained in Table 1 for each of the asset classes and underlying asset identifiers listed in Table 2 for:
(a) a transaction reported to the recognized trade repository pursuant to this Regulation;
(b) a life-cycle event that changes the pricing of an existing derivative reported to the recognized trade repository pursuant to this Regulation;
(c) a cancellation or correction of previously disseminated data relating to a transaction referred to in paragraph (a) or a life-cycle event referred to in paragraph (b).
Table 1
| Data field | Description |
|---|---|
| Cleared | Indicate whether the transaction has been cleared by a clearing house. |
| Electronic trading venue identifier | Indicate whether the transaction was executed on an electronic trading venue. |
| Collateralization | Indicate whether the transaction is collateralized. |
| Unique product identifier | Unique product identification code based on the taxonomy of the product. |
| Contract or instrument type | The name of the contract or instrument type (e.g., swap, swaption, forwards, options, basis swap, index swap, basket swap, other). |
| Data field | Description |
|---|---|
| Underlying asset identifier 1 | The unique identifier of the asset referenced in the transaction. |
| Underlying asset identifier 2 | The unique identifier of the second asset referenced in the transaction, if more than one. If more than 2 assets identified in the transaction, report the unique identifiers for those additional underlying assets. |
| Asset class | Major asset class of the product (e.g., interest rate, credit, commodity, foreign exchange, equity, etc.). |
| Effective date or start date | The date the transaction becomes effective or starts. |
| Maturity, termination or end date | The date the transaction expires. |
| Payment frequency or dates | The dates or frequency the transaction requires payments to be made (e.g., quarterly, monthly). |
| Reset frequency or dates | The dates or frequency at which the price resets (e.g., quarterly, semi-annually, annually). |
| Day count convention | Factor used to calculate the payments (e.g., 30/360, actual/360). |
| Price 1 | The price, yield, spread, coupon, etc., of the transaction. The price/rate should not include any premiums such as commissions, collateral premiums, accrued interest, etc. |
| Price 2 | The price, yield, spread, coupon, etc., of the transaction. The price/rate should not include any premiums such as commissions, collateral premiums, accrued interest, etc. |
| Data field | Description |
|---|---|
| Price notation type 1 | The manner in which the price is expressed (e.g., percent, basis points, etc.). |
| Price notation type 2 | The manner in which the price is expressed (e.g., percent, basis points, etc.). |
| Notional amount leg 1 | Total notional amount(s) of leg 1 of the transaction. |
| Notional amount leg 2 | Total notional amount(s) of leg 2 of the transaction. |
| Currency leg 1 | Currency(ies) of leg 1. |
| Currency leg 2 | Currency(ies) of leg 2. |
| Settlement currency | The currency used to determine the cash settlement amount. |
| Embedded option | Indicate whether the option is an embedded option. |
| Option exercise date | The date(s) on which the option may be exercised. |
| Option premium | Fixed premium paid by the buyer to the seller. |
| Strike price (cap/floor rate) | The strike price of the option. |
| Option style | Indicate whether the option can be exercised on a fixed date or anytime during the life of the transaction (e.g., American, European, Bermudan, Asian). |
| Data field | Description |
|---|---|
| Option type | Put, call. |
| Action | Describes the type of event to the transaction (e.g., new transaction, modification or cancellation of existing transaction, etc.). |
| Execution timestamp | The time and date of execution or novation of a transaction, expressed using Coordinated Universal Time (UTC). |
Table 2
| Asset class | Underlying asset identifier |
|---|---|
| Interest rate | CAD-BA-CDOR |
| USD-LIBOR-BBA | |
| EUR-EURIBOR-Reuters | |
| GBP-LIBOR-BBA | |
| Credit | All indexes |
| Equity | All indexes |
2. Notwithstanding item 1, each of the following is exempt from the requirement to be publicly disseminated:
(a) a transaction in a derivative that requires the exchange of more than one currency;
(b) a transaction resulting from a bilateral or multilateral portfolio compression exercise;
(c) a transaction resulting from novation by a reporting clearing house.
3. A recognized trade repository must round the notional amount of a transaction for which it disseminates transaction level data pursuant to this Regulation and this Appendix in accordance with the rounding conventions contained in Table 3.
Table 3
| Reported notional amount leg 1 or 2 | Rounded notional amount |
|---|---|
| < 1,000 | Round to nearest 5 |
| ≥1,000, <10,000 | Round to nearest 100 |
| ≥10,000, <100,000 | Round to nearest 1,000 |
| ≥100,000 <1 million | Round to nearest 10,000 |
| ≥1 million, <10 million | Round to nearest 100,000 |
| ≥10 million, <50 million | Round to nearest 1 million |
| ≥50 million, <100 million | Round to nearest 10 million |
| ≥100 million, <500 million | Round to nearest 50 million |
| ≥500 million, <1 billion | Round to nearest 100 million |
| ≥1 billion, <100 billion | Round to nearest 500 million |
| >100 billion | Round to nearest 50 billion |
4. Where the rounded notional amount of a transaction, as set out in Table 3, would exceed the capped rounded notional amount in CAD of that transaction as set out in Table 4, a recognized trade repository must disseminate the capped rounded notional amount for the transaction in place of the rounded notional amount.
5. When disseminating transaction level data pursuant to this Regulation and this Appendix for a transaction to which item 4 applies, a recognized trade repository must indicate that the notional amount for a transaction has been capped.
6. For each transaction for which the capped rounded notional amount is disseminated, if the information to be disseminated includes an option premium, a recognized trade repository must adjust the option premium in a manner that is consistent and proportionate relative to the capping and rounding of the reported notional amount of the transaction.
Table 4
| Asset class | Maturity date less effective date | Capped rounded notional amount in CAD |
|---|---|---|
| Interest rate | Less than or equal to 2 years | 250 million |
| Interest rate | Greater than 2 years and less than or equal to 10 years | 100 million |
| Interest rate | Greater than 10 years | 50 million |
| Credit | All dates | 50 million |
| Equity | All dates | 50 million |
7. A recognized trade repository must disseminate the information contained in Table 1, 48 hours after the time and date represented by the execution timestamp field of the transaction.
M.O. 2016-10, s. 17.
Filer:
TRADER REPOSITORY
Type of Filing:
INITIAL
AMENDMENT
1. Full name of trade repository:
2. Name(s) under which business is conducted, if different from item 1:
3. If this filing makes a name change on behalf of the trade repository in respect of the name set out in item 1 or item 2, enter the previous name and the new name.
Previous name:
New name:
4. Head office
Address:
Telephone:
Facsimile:
5. Mailing address (if different):
6. Other offices
Address:
Telephone:
Facsimile:
7. Website address:
8. Contact employee
Name and title:
Telephone number:
Facsimile:
E-mail address:
9. Counsel
Firm name:
Contact name:
Telephone number:
Facsimile:
E-mail address:
10. Canadian counsel (if applicable)
Firm name:
Contact name:
Telephone number:
Facsimile:
E-mail address:
File all Exhibits with the Filing. For each Exhibit, include the name of the trade repository, the date of filing of the Exhibit and the date as of which the information is accurate (if different from the date of the filing). If any Exhibit required is inapplicable, a statement to that effect shall be furnished instead of such Exhibit.
Except as provided below, if the filer files an amendment to the information provided in its Filing and the information relates to an Exhibit filed with the Filing or a subsequent amendment, the filer must, in order to comply with section 3 of this Regulation, provide a description of the change, the expected date of the implementation of the change, and file a complete and updated Exhibit. The filer must provide a clean and blacklined version showing changes from the previous filing.
If the filer has otherwise filed the information required by the previous paragraph pursuant to section 17 of this Regulation, it is not required to file the information again as an amendment to an Exhibit. However, if supplementary material relating to a filed rule is contained in an Exhibit, an amendment to the Exhibit must also be filed.
1. Legal status:
Corporation Partnership
Other (specify):
2. Indicate the following:
1. Date (DD/MM/YYYY) of formation.
2. Place of formation.
3. Statute under which trade repository was organized.
4. Regulatory status in other jurisdictions.
3. Provide a copy of the constating documents (including corporate by-laws), shareholder agreements, partnership agreements and other similar documents, and all subsequent amendments.
4. Provide the policies and procedures to address potential conflicts of interest arising from the operation of the trade repository or the services it provides, including those related to the commercial interest of the trade repository, the interests of its owners and its operators, the responsibilities and sound functioning of the trade repository, and those between the operations of the trade repository and its regulatory responsibilities.
5. An applicant that is located outside of Québec that is applying for recognition as a trade repository in accordance with sections 12 and 14 of the Act must additionally provide the following:
1. An opinion of legal counsel that, as a matter of law the applicant has the power and authority to provide the Authority with prompt access to the applicant’s books and records and submit to onsite inspection and examination by the Authority, and
2. A completed Form 91-507F2, Submission to Jurisdiction and Appointment of Agent for Service.
A list of the registered or beneficial holders of securities of, partnership interests in, or other ownership interests in, the trade repository. For each of the persons listed in the Exhibit, please provide the following:
1. Name.
2. Principal business or occupation and title.
3. Ownership interest.
4. Nature of the ownership interest, including a description of the type of security, partnership interest or other ownership interest.
In the case of a trade repository that is publicly traded, if the trade repository is a corporation, please only provide a list of each shareholder that directly owns 5% or more of a class of a security with voting rights.
1. A list of partners, officers, governors, and members of the board of directors and any standing committees of the board, or persons performing similar functions, who presently hold or have held their offices or positions during the previous year, indicating the following for each:
1. Name.
2. Principal business or occupation and title.
3. Dates of commencement and expiry of present term of office or position.
4. Type of business in which each is primarily engaged and current employer.
5. Type of business in which each was primarily engaged in the preceding 5 years, if different from that set out in item 4.
6. Whether the person is considered to be an independent director.
2. A list of the committees of the board, including their mandates.
3. The name of the trade repository’s Chief Compliance Officer.
1. For each affiliate of the trade repository provide the name and head office address and describe the principal business of the affiliate.
2. For each affiliate of the trade repository
(i) to which the trade repository has outsourced any of its key services or systems described in Exhibit E , including business recordkeeping, recordkeeping of trade data, trade data reporting, trade data comparison, data feed, or
(ii) with which the trade repository has any other material business relationship, including loans, cross-guarantees, etc.,
provide the following information:
1. Name and address of the affiliate.
2. The name and title of the directors and officers, or persons performing similar functions, of the affiliate.
3. A description of the nature and extent of the contractual and other agreements with the trade repository, and the roles and responsibilities of the affiliate under the arrangement.
4. A copy of each material contract relating to any outsourced functions or other material relationship.
5. Copies of constating documents (including corporate by-laws), shareholder agreements, partnership agreements and other similar documents.
6. For the latest financial year of any affiliate that has any outstanding loans or cross-guarantee arrangements with the trade repository, financial statements, which may be unaudited, prepared in accordance with:
a. Canadian GAAP applicable to publicly accountable enterprises;
b. IFRS; or
c. U.S. GAAP where the affiliate is incorporated or organized under the laws of the United States of America or under the laws of a jurisdiction of the United States of America.
Describe in detail the manner of operation of the trade repository and its associated functions. This should include, but not be limited to, a description of the following:
1. The structure of the trade repository.
2. Means of access by the trade repository’s participants and, if applicable, their clients to the trade repository’s facilities and services.
3. The hours of operation.
4. A description of the facilities and services offered by the trade repository including, but not limited to, collection and maintenance of derivatives data.
5. A list of the types of derivatives instruments for which data recordkeeping is offered, including, but not limited to, a description of the features and characteristics of the instruments.
6. Procedures regarding the entry, display and reporting of derivatives data.
7. Description of recordkeeping procedures that ensure derivatives data is recorded accurately, completely and on a timely basis.
8. The safeguards and procedures to protect derivatives data of the trade repository’s participants, including required policies and procedures reasonably designed to protect the privacy and confidentiality of the data.
9. Training provided to participants and a copy of any materials provided with respect to systems and rules and other requirements of the trade repository.
10. Steps taken to ensure that the trade repository’s participants have knowledge of and comply with the requirements of the trade repository.
11. A description of the trade repository’s risk management framework for comprehensively managing risks including business, legal, and operational risks.
The filer must provide all policies, procedures and manuals related to the operation of the trade repository.
Where the trade repository has outsourced the operation of key services or systems described in Exhibit E to an arms-length third party, including any function associated with the collection and maintenance of derivatives data, provide the following information:
1. Name and address of person (including any affiliates of the trade repository) to which the function has been outsourced.
2. A description of the nature and extent of the contractual or other agreement with the trade repository and the roles and responsibilities of the arms-length party under the arrangement.
3. A copy of each material contract relating to any outsourced function.
For each of the systems for collecting and maintaining reports of derivatives data, describe:
1. Current and future capacity estimates.
2. Procedures for reviewing system capacity.
3. Procedures for reviewing system security.
4. Procedures to conduct stress tests.
5. A description of the filer’s business continuity and disaster recovery plans, including any relevant documentation.
6. Procedures to test business continuity and disaster recovery plans.
7. The list of data to be reported by all types of participants.
8. A description of the data format or formats that will be available to the Authority and other persons receiving trade reporting data.
1. A complete set of all forms, agreements or other materials pertaining to access to the services of the trade repository described in Exhibit E.4.
2. Describe the types of trade repository participants.
3. Describe the trade repository’s criteria for access to the services of the trade repository.
4. Describe any differences in access to the services offered by the trade repository to different groups or types of participants.
5. Describe conditions under which the trade repository’s participants may be subject to suspension or termination with regard to access to the services of the trade repository.
6. Describe any procedures that will be involved in the suspension or termination of a participant.
7. Describe the trade repository’s arrangements for permitting clients of participants to have access to the trade repository. Provide a copy of any agreements or documentation relating to these arrangements.
A description of the fee model and all fees charged by the trade repository, or by a party to which services have been directly or indirectly outsourced, including, but not limited to, fees relating to access and the collection and maintenance of derivatives data, how such fees are set, and any fee rebates or discounts and how the rebates and discounts are set.
The undersigned certifies that the information given in this report is true and correct.
DATED at ____________ this ________ day of _____________, 20 ________________________________________________________ (Name of trade repository) ________________________________________________________ (Name of director, officer or partner – please type or print)
________________________________________________________ (Signature of director, officer or partner) ________________________________________________________ (Official capacity – please type or print)
The undersigned certifies that
(a) it will provide the Authority with access to its books and records and will submit to onsite inspection and examination by the Authority;
(b) as a matter of law, it has the power and authority to
i. provide the Authority with access to its books and records, and
ii. submit to onsite inspection and examination by the Authority.
DATED at ____________ this ________ day of _____________, 20
________________________________________________________ (Name of trade repository) ________________________________________________________ (Name of director, officer or partner – please type or print) ________________________________________________________ (Signature of director, officer or partner) ________________________________________________________ (Official capacity – please type or print)
M.O. 2013-21, Sch. 91-507F1; M.O. 2016-10, s. 18.
1. Name of trade repository (the “Trade Repository”): ________________________________________________________________
2. Jurisdiction of incorporation, or equivalent, of Trade Repository: ________________________________________________________________
3. Address of principal place of business of Trade Repository: ________________________________________________________________
4. Name of the agent for service of process for the Trade Repository (the “Agent”): ________________________________________________________________
5. Address of Agent for service of process in Québec: ________________________________________________________________
6. The Trade Repository designates and appoints the Agent as its agent upon whom may be served a notice, pleading, subpoena, summons or other process in any action, investigation or administrative, criminal, quasi-criminal, penal or other proceeding arising out of or relating to or concerning the activities of the Trade Repository in Québec. The Trade Repository hereby irrevocably waives any right to challenge service upon its Agent as not binding upon the Trade Repository.
7. The Trade Repository agrees to unconditionally and irrevocably attorn to the non-exclusive jurisdiction of (i) the courts and administrative tribunals of Québec and (ii) any proceeding in any province or territory arising out of, related to, concerning or in any other manner connected with the regulation and oversight of the activities of the Trade Repository in Québec.
8. The Trade Repository shall file a new submission to jurisdiction and appointment of agent for service of process in this form at least 30 days before the Trade Repository ceases to be recognized or exempted by the Authority, to be in effect for 6 years from the date it ceases to be recognized or exempted unless otherwise amended in accordance with section 9.
9. Until 6 years after it has ceased to be a recognized or exempted by the Authority from the recognition requirement under section 12 of the Act, the Trade Repository shall file an amended submission to jurisdiction and appointment of agent for service of process at least 30 days before any change in the name or above address of the Agent.
10. This submission to jurisdiction and appointment of agent for service of process shall be governed by and construed in accordance with the laws of Québec.
Dated: _________________________________
Signature of the Trade Repository
Print name and title of signing officer of the Trade Repository
I, ______________________________________ (name of Agent in full; if Corporation, full Corporate name) of __________________________________________(business address), hereby accept the appointment as agent for service of process of ______________________________________(insert name of Trade Repository) and hereby consent to act as agent for service pursuant to the terms of the appointment executed by ______________________________________ (insert name of Trade Repository) on ______________________________________ (insert date).
Dated: ________________________________
Signature of Agent
Print name of person signing and, if
Agent is not an individual, the title of the person
M.O. 2013-21, Sch. 91-507F2.
1. Identification:
A. Full name of the recognized trade repository:
B. Name(s) under which business is conducted, if different from item 1A:
2. Date recognized trade repository proposes to cease carrying on business as a trade repository:
3. If cessation of business was involuntary, date trade repository has ceased to carry on business as a trade repository:
File all Exhibits with the Cessation of Operations Report. For each exhibit, include the name of the trade repository, the date of filing of the exhibit and the date as of which the information is accurate (if different from the date of the filing). If any Exhibit required is inapplicable, a statement to that effect shall be furnished instead of such Exhibit.
The reasons for the recognized trade repository ceasing to carry on business as a trade repository.
A list of all derivatives instruments for which data recordkeeping is offered during the last 30 days prior to ceasing business as a trade repository.
A list of all participants who are counterparties to a transaction whose derivatives data is required to be reported pursuant to this Regulation and for whom the trade repository provided services during the last 30 days prior to ceasing business as a trade repository.
The undersigned certifies that the information given in this report is true and correct.
DATED at ____________ this ____________ day of ___________________ 20 _____ _________________________ (Name of trade repository)
(Name of director, officer or partner – please type or print) _________________________ (Signature of director, officer or partner) _________________________ (Official capacity – please type or print)
M.O. 2013-21, Sch. 91-507F3.
Decision 2013-PDG-0192, 2013-11-13
Bulletin de l’Autorité: 2013-12-19, Vol. 10, n° 50 M.O. 2013-21, 2013 G.O. 2, 3631
Decision 2014-PDG-0113, 2014-09-25
Bulletin de l’Autorité: 2014-10-30, Vol. 11, n° 43 M.O. 2014-08, 2014 G.O. 2, 2451
Decision 2016-PDG-0072, 2016-05-18
Bulletin de l’Autorité : Vol. 13, no 25
M.O. 2016-10, 2016 G.O. 2, 2316
Decision 2023-PDG-0039, 2023-08-09
Bulletin de l’Autorité : 2023-09-14, Vol. 20, n° 36 M.O. 2023-16, 2023 G.O. 2, 2149A
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.
“section 5 of the Securities Act (chapter V-1.1)”
“M.O. 2013-21, c. 1”
“Regulation 91-507 on trade repositories and derivative data reporting, CQLR, c. I-14.01, r. 1.1 (the "Regulation 91-507")”
“Regulation 51-102 respecting Continuous Disclosure Obligations (chapter V.1.1, r. 24)”
“The Regulation excludes certain contracts from the application of Regulation 91-507 respecting Trade Repositories and Derivatives Data Reporting”
“In the Regulation reference to “trade reporting rules” refers to the following instruments... Ontario Securities Commission Rule 91-507 Trade Repositories and Derivatives Data Reporting”
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