Title BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
Multilateral Instrument 96-101 Trade Repositories and Derivatives Data Reporting
Section 1 (5) (a) BEFORE amended by BC Reg 45/2020, effective March 27, 2020.
(a) in British Columbia, Newfoundland and Labrador, Northwest Territories, Nunavut, Prince Edward Island and Yukon, a quotation and trade reporting system for derivatives, and
Section 1 (1) definitions of "collateral and margin data", "commodity derivative", "Derivatives Service Bureau", "facility for trading derivatives", "notional amount threshold derivatives dealer", "position level data", "qualified reporting counterparty", "UTI" and "validation procedure" were added by BC Reg 139/2025, effective July 25, 2025.
Section 1 (1) definitions of "creation data", "derivatives dealer", "Global LEI System", "interim period", "life-cycle event", "life-cycle event data", "local counterparty" (part) and "valuation data" BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
"creation data" means data resulting from a transaction which is within the classes of data described in the fields listed in Appendix A, other than valuation data;
"derivatives dealer" means a person or company engaging in or holding himself, herself or itself out as engaging in the business of trading in derivatives as principal or agent;
"Global LEI System" means the system for unique identification of parties to financial transactions developed by the Legal Entity Identifier Regulatory Oversight Committee;
"interim period" means an interim period as defined in National Instrument 51-102 Continuous Disclosure Obligations;
"life-cycle event" means an event that results in a change to derivatives data reported to a recognized trade repository in respect of a derivative;
"life-cycle event data" means data reflecting changes to derivatives data resulting from a life-cycle event;
"local counterparty" means a counterparty to a derivative if, at the time of the transaction, one or more of the following apply:
"valuation data" means data within the classes of data described in the fields listed in Appendix A under Item E — "Valuation Data".
Section 1 (3) (c) and (d) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(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.
Section 1 (6) and (7) were added by BC Reg 139/2025, effective July 25, 2025.
Section 3 (3) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(3) For a change to a matter set out in Form 96-101F1 other than a change referred to in subsection (1) or (2), a recognized trade repository must file an amendment to the information provided in Form 96-101F1 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, or
(b) the time the recognized trade repository discloses the change.
Section 7 (1) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(1) A recognized trade repository must establish, implement and maintain clear and transparent written rules, policies and procedures that are not contrary to the public interest and that are reasonably designed to ensure that
(a) each material aspect of its activities complies with applicable laws,
(b) its rules, policies, procedures and contractual arrangements applicable to its users are consistent with applicable laws,
(c) the rights and obligations of its users and owners with respect to the use of derivatives data reported to the trade repository are clear and transparent, and
(d) where a reasonable person would conclude that it is appropriate to do so, an agreement that it enters into clearly states service levels, rights of access, protection of confidential information, who possesses intellectual property rights and levels of operational reliability of the recognized trade repository's systems, as applicable.
Section 7 (3) was added by BC Reg 139/2025, effective July 25, 2025.
Section 8 (0.1) was added by BC Reg 139/2025, effective July 25, 2025.
Section 8 (1) (part) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(1) A recognized trade repository must establish, implement and maintain clear and transparent written governance arrangements that set out a clear organizational structure with direct lines of responsibility and are reasonably designed to do each of the following:
Section 8 (1) (b.1) was added by BC Reg 139/2025, effective July 25, 2025.
Section 18 (1) and (2) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(1) A recognized trade repository must have recordkeeping procedures reasonably designed 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 relating to a derivative required to be reported under this Instrument for 7 years after the date on which the derivative expires or terminates.
Section 21 (3) (c) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(c) promptly notify the regulator or securities regulatory 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.
Section 23 BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
Confirmation of data and information
23 (1) A recognized trade repository must establish, implement and maintain written rules, policies and procedures reasonably designed to allow for confirmation by each counterparty to a derivative that has been reported under this Instrument that the derivatives data reported in relation to the derivative is accurate.
(2) Despite subsection (1), a recognized trade repository is not required to establish, implement and maintain written rules, policies or procedures referred to in that subsection in respect of a counterparty that is not a participant of the recognized trade repository.
Section 25 (1) (c) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(c) if paragraphs (a) and (b) do not apply and the counterparties to the derivative have, at the time of the transaction, agreed in writing that one of them will be the reporting counterparty, the counterparty determined to be the reporting counterparty under the terms of that agreement, and
Section 26 (1) and (8) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(1) A reporting counterparty to a derivative involving a local counterparty must report, or cause to be reported, the data required to be reported under this Part to a recognized trade repository.
(8) If a local counterparty to a derivative that is required to be reported under this Instrument and is cleared through a reporting clearing agency has specified a recognized trade repository to which derivatives data in relation to the derivative is to be reported, the reporting clearing agency must report the derivatives data to that recognized trade repository.
Section 26 (3) (b) (i), (ii) and (iii) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(i) Multilateral Instrument 96-101 Trade Repositories and Derivatives Data Reporting, as amended from time to time, if reported under the requirements of a jurisdiction other than the local jurisdiction;
(ii) Manitoba Securities Commission Rule 91-507 Trade Repositories and Derivatives Data Reporting, as amended from time to time;
(iii) Ontario Securities Commission Rule 91-507 Trade Repositories and Derivatives Data Reporting, as amended from time to time;
Section 26 (5), (6) and (7) BEFORE repealed by BC Reg 139/2025, effective July 25, 2025.
(5) A reporting counterparty must not submit derivatives data that is false or misleading to a recognized trade repository.
(6) A reporting counterparty must report an error or omission in the derivatives data it has reported as soon as practicable after discovery of the error or omission and, in any event, no later than the end of the business day following the day of discovery of the error or omission.
(7) 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 derivative to which it is a counterparty as soon as practicable after discovery of the error or omission and, in any event, no later than the end of the business day following the day of discovery of the error or omission.
Section 26 (9) was added by BC Reg 139/2025, effective July 25, 2025.
Section 27 (2) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(2) In a report of life-cycle data or valuation data required under this Part, a reporting counterparty must include the unique transaction identifier for the transaction relating to the derivative as set out in section 29.
Section 28 (1) and (3) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(1) A recognized trade repository must identify each counterparty to a derivative that is required to be reported under this Instrument in all recordkeeping and all reporting required under this Instrument by means of a single legal entity identifier that is a unique identification code assigned to the counterparty in accordance with the standards set by the Global LEI System.
(3) If a local counterparty to a derivative required to be reported under this Instrument is an individual, or is not eligible to receive a legal entity identifier as determined by the Global LEI System, the reporting counterparty must identify the counterparty by a single alternate identifier.
Section 28 (4) BEFORE repealed by BC Reg 139/2025, effective July 25, 2025.
(4) Despite subsection (1), if subsection (3) applies to a counterparty to a derivative, the recognized trade repository to which a report has been made in relation to the derivative must identify the counterparty with the alternate identifier supplied by the reporting counterparty.
Section 29 BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
Unique transaction identifiers
29 (1) A recognized trade repository must identify each transaction relating to a derivative that is required to be reported under this Instrument in all recordkeeping and all reporting required under this Instrument 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.
Section 30 (1) and (2) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(1) In this section, "unique product identifier" means a code that uniquely identifies a sub-type of derivative and is assigned in accordance with international or industry standards.
(2) For each derivative that is required to be reported under this Instrument, the reporting counterparty must assign a unique product identifier that identifies the sub-type of the derivative.
Section 30 (3) and (4) BEFORE repealed by BC Reg 139/2025, effective July 25, 2025.
(3) A reporting counterparty must not assign more than one unique product identifier to a derivative.
(4) If international or industry standards for a unique product identifier are not reasonably available for a particular sub-type of derivative at the time a report is made under this Instrument, a reporting counterparty must assign a unique product identifier to the derivative using its own methodology or incorporating a unique product identifier previously assigned to the derivative.
Section 31 (1) and (2) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(1) A reporting counterparty must report creation data relating to a derivative that is required to be reported under this Instrument to a recognized trade repository immediately following the transaction.
(2) Despite subsection (1), if it is not practicable to immediately report the creation data, a reporting counterparty must report creation data as soon as practicable and in no event later than the end of the business day following the day on which the data would otherwise be required to be reported.
Section 31 (3) was added by BC Reg 139/2025, effective July 25, 2025.
Section 32 (1) and (2) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(1) A reporting counterparty must report all life-cycle event data relating to a derivative that is required to be reported under this Instrument to a recognized trade repository by the end of the business day on which the life-cycle event occurs.
(2) Despite subsection (1), if it is not practicable to report life-cycle event data by the end of the business day on which the life-cycle event occurs, the reporting counterparty must report life-cycle event data no later than the end of the business day following the day on which the life-cycle event occurs.
Section 32 (3) and (4) were added by BC Reg 139/2025, effective July 25, 2025.
Section 33 BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
Valuation data
33 (1) A reporting counterparty must report valuation data relating to a derivative that is required to be reported under this Instrument to a recognized trade repository in accordance with industry accepted valuation standards
(a) daily, based on relevant closing market data from the previous business day, if the reporting counterparty is a reporting clearing agency or a derivatives dealer, or
(b) quarterly, as of the last day of each calendar quarter, if the reporting counterparty is not a reporting clearing agency or a derivatives dealer.
(2) Despite subsection (1), valuation data required to be reported under paragraph (1) (b) must be reported to the recognized trade repository no later than the 30th day after the end of the calendar quarter.
Section 35 BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
Timing requirements for reporting data to another recognized trade repository
35 Despite subsection 26 (4) and sections 31 to 34, if a recognized trade repository ceases operations or stops accepting derivatives data for an asset class of derivatives, a reporting counterparty may fulfill its reporting obligations under this Instrument by reporting the derivatives data to another recognized trade repository or, if there is not an available recognized trade repository, the regulator or securities regulatory authority.
Section 38 (1), (2) and (3) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(1) A recognized trade repository must provide all counterparties to a derivative with timely access to all derivatives data relating to that derivative 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 a non-reporting counterparty or a delegate of a non-reporting counterparty.
(3) Each counterparty to a derivative must permit the release of all derivatives data required to be reported or disclosed under this Instrument.
Section 39 (1), (2), (3) and (5) BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
(1) Unless otherwise governed by the requirements or conditions of a decision of the securities regulatory authority, a recognized trade repository must, on a reasonably frequent basis, create and make available on its website, in a manner that is easily accessible to the public, at no cost, aggregate data on open positions, volume, number and, if applicable, price, relating to the derivatives reported to it under this Instrument.
(2) The data made available under subsection (1) must include, at a minimum, breakdowns, if applicable, by currency of denomination, geographic location of reference entity or asset, asset class, contract type, maturity and whether the derivative is cleared.
(3) A recognized trade repository must make transaction-level reports available to the public, at no cost, in accordance with Appendix C.
(5) A recognized trade repository must make the data referred to in this section available to the public on its website or through a similar medium, in a usable form and in a manner that is easily accessible to the public at no cost.
Section 40 BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
Commodity derivative
40 Despite Part 3, a local counterparty is not required to report derivatives data relating to a derivative the asset class of which is a commodity, other than currency, if
(a) none of the counterparties to the derivative are any of the following:
(iii) an affiliated entity of a person or company referred to in subparagraph (i) or (ii), and
(b) the aggregate month-end gross notional amount under all outstanding derivatives the asset class of which is a commodity, other than currency, of the local counterparty and of each affiliated entity of the local counterparty that is a local counterparty in a jurisdiction of Canada, excluding derivatives with an affiliated entity, did not, in any calendar month in the preceding 12 calendar months, exceed $250 000 000.
Section 41.1 BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
Derivative between affiliated entities
41.1 Despite Part 3, a counterparty is not required to report derivatives data relating to a derivative if, at the time of the transaction,
(a) the counterparties to the derivative are affiliated entities, and
(b) none of the counterparties to the derivative are any of the following:
(iii) an affiliated entity of a person or company referred to in subparagraph (i) or (ii).
Section 42 BEFORE renumbered and amended by BC Reg 139/2025, effective July 25, 2025.
Derivative between a non-resident derivatives dealer and a non-local counterparty
42 Despite Part 3, a counterparty is not required to report derivatives data relating to a derivative if the derivative is required to be reported solely because one or both counterparties is a local counterparty under paragraph (b) of the definition of "local counterparty".
Section 42.1 BEFORE repealed by BC Reg 139/2025, effective July 25, 2025.
Reporting by a local counterparty that ceases to qualify for an exclusion
42.1 (1) Despite section 40, and subject to section 44, a local counterparty must report creation data in relation to a derivative if all of the following apply:
(a) the derivative was not previously reported as a result of the operation of section 40;
(b) a condition in section 40 is no longer satisfied;
(c) the derivative was entered into after May 1, 2016 but before the date on which the condition in section 40 is no longer satisfied;
(d) there are outstanding contractual obligations with respect to the derivative on the earlier of
(i) the date that the derivative is reported, and
(ii) the date that is 180 days following the date on which the condition in section 40 is no longer satisfied.
(2) Despite subsection (1), and subject to subsection 44 (3), a local counterparty is not required to report derivatives data in relation to a derivative to which subsection (1) applies, or any other derivative required to be reported under this Instrument, until the date that is 180 days following the date on which a condition referred to in paragraph (1) (b) is no longer satisfied.
(3) Subsection (2) does not apply to a local counterparty that has previously acted as a reporting counterparty under any of the following:
(a) Multilateral Instrument 96-101 Trade Repositories and Derivatives Data Reporting, as amended from time to time, as it applies in any jurisdiction;
(b) Manitoba Securities Commission Rule 91-507 Trade Repositories and Derivatives Data Reporting, as amended from time to time;
(c) Ontario Securities Commission Rule 91-507 Trade Repositories and Derivatives Data Reporting, as amended from time to time;
(d) Québec Regulation 91-507 respecting trade repositories and derivatives data reporting, as amended from time to time.
(4) Despite section 31, a reporting counterparty to a derivative to which subsection (1) applies is required to report, in relation to the transaction resulting in the derivative, only the creation data indicated in the column in Appendix A entitled "Required for Pre-existing Derivatives".
(5) Despite section 32, a reporting counterparty is not required to report life-cycle event data relating to a derivative to which subsection (1) applies until the reporting counterparty has reported creation data in accordance with subsections (1) and (2).
(6) Despite section 33, a reporting counterparty is not required to report valuation data relating to a derivative to which subsection (1) applies until the reporting counterparty has reported creation data in accordance with subsections (1) and (2).
Appendix A BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
to Multilateral Instrument 96-101
Trade Repositories and Derivatives Data Reporting
Minimum Data Fields Required to be Reported to a
Recognized Trade Repository
Instructions
The reporting counterparty is required to provide a response for each of the fields unless the field is not applicable to the derivative.
| Data Field | Description | Required for Pre-existing Derivatives |
| Transaction identifier | The unique transaction identifier as provided by the recognized trade repository or the identifier as identified by the two counterparties, electronic trading venue of execution or clearing agency. | Y |
| Master agreement type | The type of master agreement, if used for the reported derivative. | N |
| Master agreement version | Date of the master agreement version (e.g., 2002, 2006). | N |
| Cleared | State whether the derivative has been cleared by a clearing agency. | Y |
| Intent to clear | State whether the derivative will be cleared by a clearing agency. | N |
| Clearing agency | LEI of the clearing agency where the derivative is or will be cleared. | Y (If available) |
| Clearing member | LEI of the clearing member, if the clearing member is not a counterparty. | N |
| Clearing exemption | State whether one or more of the counterparties to the derivative are exempted from a mandatory clearing requirement. | N |
| 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 | State whether the derivative is between two affiliated entities. | Y (If available) |
| Collateralization | State whether the derivative 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 case of an individual, its client code. | Y |
| Identifier of non-reporting counterparty | LEI of the non-reporting counterparty or, in case of an individual, its client code. | Y |
| Counterparty side | State 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 |
| Identifier of agent reporting the derivative | LEI of the agent reporting the derivative if reporting of the derivative has been delegated by the reporting counterparty. | N |
| Jurisdiction of reporting counterparty | If the reporting counterparty is a local counterparty under the derivatives data reporting rules of Manitoba, Ontario or Québec, or is a local counterparty under paragraph (a) or (c) of the definition of location counterparty in the derivatives data reporting rules of any other jurisdiction of Canada, state all such jurisdictions. | Y (If available) |
| Jurisdiction of non-reporting counterparty | If the non-reporting counterparty is a local counterparty under the derivatives data reporting rules of Manitoba, Ontario or Québec, or is a local counterparty under paragraph (a) or (c) of the definition of location counterparty in the derivatives data reporting rules of any other jurisdiction of Canada, state all such jurisdictions. | Y (If available) |
| A. Common Data | These fields are required to be reported for all derivatives even if the information may be entered in an Additional Asset Information field below. A field is not required to be reported if the unique product identifier | |
| 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, forward, option, basis swap, index swap, basket swap). | Y |
| Underlying asset identifier 1 | The unique identifier of the asset referenced in the derivative. | Y |
| Underlying asset identifier 2 | The unique identifier of the second asset referenced in the derivative, if more than one. If more than two assets identified in the derivative, 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). | Y (If available) |
| Effective date or start date | The date the derivative becomes effective or starts. | Y |
| Maturity, termination or end date | The date the derivative expires. | Y |
| Payment frequency or dates | The dates or frequency the derivative 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 | State whether derivative is settled physically or in cash. | Y |
| Price 1 | The price, rate, yield, spread, coupon or similar characteristic of the derivative. This must not include any premiums such as commissions, collateral premiums or accrued interest. | Y |
| Price 2 | The price, rate, yield, spread, coupon or similar characteristic of the derivative. This must not include any premiums such as commissions, collateral premiums or accrued interest. | Y |
| Price notation type 1 | The manner in which the price is expressed (e.g., percentage, basis points). | Y |
| Price notation type 2 | The manner in which the price is expressed (e.g., percentage, basis points). | Y |
| Price multiplier | The number of units of the underlying reference entity represented by 1 unit of the derivative. | Y (If available) |
| Notional amount leg 1 | Total notional amount(s) of leg 1 of the derivative. | Y |
| Notional amount leg 2 | Total notional amount(s) of leg 2 of the derivative. | Y |
| Currency leg 1 | Currency of leg 1. | Y |
| Currency leg 2 | Currency 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 or currencies in which any up-front payment is made by one counterparty to another. | N |
| Embedded option | State whether the option is an embedded option. | Y (If available) |
| B. Additional Asset Information | These fields are required to be reported for the respective types of derivatives set out below, even if the information is entered in a Common Data field above. | |
| i) Interest rate derivatives | ||
| Fixed rate leg 1 | The rate used to determine the payment amount for leg 1 of the derivative. | Y |
| Fixed rate leg 2 | The rate used to determine the payment amount for leg 2 of the derivative. | Y |
| Floating rate leg 1 | The floating rate used to determine the payment amount for leg 1 of the derivative. | Y |
| Floating rate leg 2 | The floating rate used to determine the payment amount for leg 2 of the derivative. | 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 derivative (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 derivative (e.g., quarterly, semi-annually, annually). | Y |
| Floating rate reset frequency or dates | The dates or frequency at which the floating leg of the derivative 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 | ||
| 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 derivative (e.g., barrels, bushels). | 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 fields are required to be reported for options derivatives, 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 | State whether the option can be exercised on a fixed date or anytime during the life of the derivative (e.g., American, European, Bermudan, Asian). | Y |
| Option type | Put, call. | Y |
| D. Event Data | ||
| Action | Describes the type of event to the derivative (e.g., new transaction, modification or cancellation of existing derivative). | N |
| Execution timestamp | The time and date of execution of a transaction, including a novation, expressed using Coordinated Universal Time (UTC). | Y (If available) |
| Post-transaction events | State whether the report results from a post-transaction service (e.g., compression, reconciliation) or from a life-cycle event (e.g., amendment). | N |
| Reporting timestamp | The time and date the derivative was submitted to the trade repository, expressed using UTC. | N |
| E. Valuation Data | These fields are required to be reported on a continuing basis for all reported derivatives, including reported pre-existing derivatives. | |
| Value of derivative calculated by the reporting counterparty | Mark-to-market valuation or mark-to-model valuation of the derivative. | N |
| Valuation currency | State the currency used when reporting the value of the derivative. | N |
| Valuation date | Date of the latest mark-to-market or mark-to-model valuation. | N |
| F. Other Details | ||
| Other details | Where the terms of the derivative cannot be effectively reported in the above prescribed fields, provide any additional information that may be necessary. | Y (If applicable) |
Appendix B BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
to Multilateral Instrument 96-101
Trade Repositories and Derivatives Data Reporting
Trade Reporting Laws of Foreign Jurisdictions
| Jurisdiction | Law, Regulation and/or Instrument |
| European Union | Regulation (EU) No 648/2012 of the European Parliament and Council of 4 July 2012 on OTC derivatives, central counterparties and trade repositories, as amended from time to time. Commission Delegated Regulation (EU) No 148/2013 of 19 December 2012 supplementing Regulation (EU) No 648/2012 of the European Parliament and of the Council on OTC derivatives, central counterparties and trade repositories with regard to regulatory technical standards on the minimum details of the data to be reported to trade repositories, as amended from time to time. Commission Delegated Regulation (EU) No 151/2013 of 19 December 2012 supplementing Regulation (EU) No 648/2012 of the European Parliament and of the Council on OTC derivatives, central counterparties and trade repositories, with regard to regulatory technical standards specifying the data to be published and made available by trade repositories and operational standards for aggregating, comparing and accessing the data, as amended from time to time. Commission Implementing Regulation (EU) No 1247/2012 of 19 December 2012 laying down implementing technical standards with regard to the format and frequency of trade reports to trade repositories according to Regulation (EU) No 648/2012 of the European Parliament and of the Council on OTC derivatives, central counterparties and trade repositories, as amended from time to time. |
| United States of America | CFTC Real-Time Public Reporting of Swap Transaction Data, 17 C.F.R. pt. 43 (2013), as amended from time to time. CFTC Swap Data Recordkeeping and Reporting Requirements, 17 C.F.R. pt. 45 (2013), as amended from time to time. CFTC Swap Data Recordkeeping and Reporting Requirements: Pre-Enactment and Transition Swaps, 17 C.F.R. pt. 46 (2013), as amended from time to time. |
Appendix C title BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
to Multilateral Instrument 96-101
Trade Repositories and Derivatives Data Reporting
Appendix C "Instructions" was deleted by BC Reg 139/2025, effective July 25, 2025.
Appendix C, section 1 BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
1 Subject to items 2 through 6, a recognized trade repository must make available to the public, at no cost, the information contained in Table 1 for a derivative in any of the asset classes and underlying asset identifiers listed in Table 2 for all of the following:
(a) a derivative reported to the recognized trade repository under this Instrument;
(b) a life-cycle event that changes the pricing of an existing derivative reported to the recognized trade repository under this Instrument;
(c) a cancellation of a reported transaction or a correction of data relating to a transaction that was previously made available to the public, in each case resulting in a derivative referred to in paragraph (a) or a life-cycle event referred to in paragraph (b).
Appendix C, table 1 BEFORE re-enacted by BC Reg 139/2025, effective July 25, 2025.
| Data Field | Description |
| Cleared | State whether the derivative has been cleared by a clearing agency. |
| Electronic trading venue identifier | State whether the transaction was executed on an electronic trading venue. |
| Collateralization | State whether the derivative 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, forward, option, basis swap, index swap, basket swap). |
| Underlying asset identifier 1 | The unique identifier of the asset referenced in the derivative. |
| Underlying asset identifier 2 | The unique identifier of the second asset referenced in the derivative, if more than one. If more than two assets identified in the derivative, state 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). |
| Effective date or start date | The date the derivative becomes effective or starts. |
| Maturity, termination or end date | The date the derivative expires. |
| Payment frequency or dates | The dates or frequency the derivative 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, rate, yield, spread, coupon or similar characteristic of the derivative. This should not include any premiums such as commissions, collateral premiums or accrued interest. |
| Price 2 | The price, rate, yield, spread, coupon or similar characteristic of the derivative. This should not include any premiums such as commissions, collateral premiums or accrued interest. |
| Price notation type 1 | The manner in which the price is expressed (e.g., percentage, basis points). |
| Price notation type 2 | The manner in which the price is expressed (e.g., percentage, basis points). |
| Notional amount leg 1 | Total notional amount(s) of leg 1 of the derivative. |
| Notional amount leg 2 | Total notional amount(s) of leg 2 of the derivative. |
| Currency leg 1 | Currency of leg 1. |
| Currency leg 2 | Currency of leg 2. |
| Settlement currency | The currency used to determine the cash settlement amount. |
| Embedded option | State 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 | State whether the option can be exercised on a fixed date or anytime during the life of the derivative (e.g., American, European, Bermudan, Asian). |
| Option type | Put, call. |
| Action | Describe the type of event to the derivative (e.g., new transaction, modification or cancellation of existing derivative). |
| Execution timestamp | The time and date of execution of a derivative, including a novation, expressed using Coordinated Universal Time (UTC). |
Appendix C, section 4 BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
Capping of notional amount
4 If the rounded notional amount, as determined under item 3, of a derivative referred to in item 1 exceeds the capped rounded notional amount, in Canadian dollars, according to the asset class and maturity date less execution time stamp date set out in Table 4 for that derivative, a recognized trade repository must make available to the public the capped rounded notional amount for the derivative in place of the rounded notional amount.
Appendix C, section 6 BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
6 For each derivative referred to in item 1 for which the capped rounded notional amount is made available to the public, if the data to be made available to the public includes an option premium, the recognized trade repository must adjust the option premium in a manner that is consistent with and proportionate to the capping and rounding of the reported notional amount of the transaction.
Appendix C, table 4 heading BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
| Asset Class | Maturity Date less Execution Time Stamp Date | Capped Rounded Notional Amount in Canadian Dollars |
Appendix C, section 7 BEFORE amended by BC Reg 139/2025, effective July 25, 2025.
Timing
7 Subject to items 2 through 6, a recognized trade repository must make the information contained in Table 1 available to the public 48 hours after the time reported in the execution timestamp field for the derivative.
Appendix C, section 8 was enacted by BC Reg 139/2025, effective July 25, 2025.