Hong Kong OTC Derivatives Reporting Deadlines
Under Hong Kong’s OTC derivatives reporting regime, covered transactions generally must be reported to the Hong Kong Trade Repository within two business days of the trading day (T+2).
More key points
- Reportable subsequent events generally follow the same two-business-day deadline.
- Valuation information is reported each business day, and margin and collateral information is reported when calculated or updated under the rules.
- Apply the current rules and any specified grace period or special arrangement.
On this page14 sections
- Core transaction deadline
- Events and other data
- Current technical requirements matter
- Which events are reported
- The two-business-day deadline
- Valuation and collateral can have different timing
- Who must report and how delegated reporting works
- A practical control sequence
- Exam traps
- A simple event timeline
- Data validation and corrections
- Delegation does not erase responsibility
- Use current scope and technical material
- Exam takeaway
The deadline question is easy to mix up with the separate frequency for valuation data. Keep the transaction/event reporting cycle distinct from daily valuation reporting.
Core transaction deadline
The joint SFC and HKMA FAQs explain that covered OTC derivatives transactions are reported within two business days, on a T+2 basis. The reporting and recordkeeping framework applies to the prescribed reporting entities and specified transactions under the Securities and Futures (OTC Derivative Transactions—Reporting and Record Keeping Obligations) Rules. It is not a blanket reporting duty for every company that enters any derivative contract.
Events and other data
Subsequent events affecting a reportable transaction’s terms, conditions, or parties may also need to be reported within two business days under the reporting instructions. Valuation information is a distinct data item reported for every business day. Margin and collateral information is reported when calculated or updated in accordance with relevant margin requirements. The exact reportable fields and technical format are set out in the current Supplementary Reporting Instructions and HKTR materials.
Current technical requirements matter
For new transactions and subsequent events from 29 September 2025, reporting entities submit in ISO 20022 XML format under the current implementation. Reporting procedures may include grace periods or special arrangements, and CCP trades have specific timing details. Use the latest SFC/HKMA FAQs and HKTR instructions rather than applying an older format or an oversimplified deadline to every report type.
Which events are reported
Hong Kong’s OTC derivatives reporting regime covers specified reportable transactions and lifecycle events under the SFO framework and relevant rules. Depending on the transaction and reporting entity, events can include execution, termination, changes to key terms, valuations, and margin or collateral information. Identify the product, counterparties, reporting obligation, and event type before calculating a deadline. A trade report is not a substitute for valuation or collateral reporting where those are separately required.
The two-business-day deadline
For covered transaction details and reportable lifecycle events, the current SFC/HKMA FAQ describes a two-business-day reporting deadline (T+2), subject to the applicable rules and event-specific provisions. The clock is tied to the relevant event and the meaning of business day in the regime, not simply two calendar dates. Reporting entities should use the current HKTR instructions and data standards, including ISO 20022 requirements that took effect in 2025, and maintain evidence of submission and acknowledgments.
Valuation and collateral can have different timing
Valuation information is generally reported on the required schedule, including daily valuation reporting under the current regime. Margin and collateral information is reported when it is calculated or updated as required by the rules. Do not apply the transaction T+2 window mechanically to every data field. The current FAQ and technical instructions distinguish report types and situations; firms should map each event to the corresponding schema and timing requirement.
Who must report and how delegated reporting works
The rules identify reporting entities and allocation of responsibility by counterparty type and status. A party may arrange for another entity or service provider to submit on its behalf where permitted, but delegation does not necessarily remove the underlying party’s responsibility to ensure complete and timely reporting. Contracts should allocate data sourcing, validation, corrections, and outage escalation. A reporting party should monitor rejections and omissions rather than assume a file upload equals a compliant report.
A practical control sequence
On execution or a lifecycle event, capture the event timestamp and required economic terms, determine whether the trade is in scope, identify the reporting entity, map fields to HKTR format, and submit within the applicable time. Validate identifiers and counterparty data, review acknowledgment or rejection messages, correct errors promptly, and reconcile reported trades to internal records. Keep a calendar for daily valuations and collateral updates. During an outage, invoke the contingency process and retain evidence of reasonable steps.
Exam traps
T+2 means business days in the relevant regime, not necessarily calendar days. Event reporting and daily valuation reporting are distinct. Outsourcing submission does not automatically eliminate accountability. A transaction may be subject to reporting even if it is not centrally cleared, depending on scope and the rules. For precise coverage, exclusions, and exceptions, use the current SFO rules, SFC/HKMA FAQs, and HKTR technical materials rather than relying on a broad summary.
A simple event timeline
Assume a reportable trade is executed Monday with no holidays. The reporting entity captures event time and required economics, then submits within the applicable two-business-day window. A later material lifecycle event starts its own analysis; it is not absorbed into the original submission. Daily valuation follows its own cadence. Retain the timestamps used for deadline calculation.
Data validation and corrections
A timely but inaccurate report still undermines the regime. Validate counterparty identifiers, product taxonomy, notional, event type, dates, valuation and collateral fields. Review acknowledgments and rejections, correct promptly, and reconcile HKTR data to internal systems. Investigate omissions rather than assuming upload equals acceptance.
Delegation does not erase responsibility
If a service provider submits on a party’s behalf, define data sourcing, deadlines, escalation and corrections. Monitor completion and keep a contingency for provider outages. Contractual allocation may not change the party treated as responsible under the rules. Maintain evidence that reporting controls work.
Use current scope and technical material
Not every derivative or entity is covered identically. SFO rules define scope, reporting persons and exemptions. Reporting schemas and instructions can change even if the high-level deadline does not. Consult current SFC/HKMA FAQs and HKTR technical material for fields, and the legislation for legal scope.
Exam takeaway
Default memory aid: covered transaction and reportable subsequent event—T+2 business days; valuation—each business day. Confirm the reporting entity, product scope, and any specific exception.
Common questions
Is valuation data also submitted only on T+2?
No. The FAQs state valuation information is reported for every business day; this is distinct from transaction reporting.
Does this apply to every OTC derivative market participant?
No. The rules identify prescribed reporting entities and covered transactions.
What reporting format applies to new trades after September 29, 2025?
The current framework requires ISO 20022 XML for new transactions and subsequent events from that date.