OTC derivative transaction-record retention
Under Hong Kong's OTC Derivative Transactions (Reporting and Record Keeping Obligations) Rules, records of a reportable transaction must generally be kept while the transaction is outstanding and for five years after it matures or is terminated.
More key points
- This reporting-rule period is distinct from other record-retention duties that may apply to a licensed corporation, trade repository or different transaction record.
On this page16 sections
- The basic retention timeline
- What kinds of records
- Do not mix up retention rules
- Operational control
- The retention clock follows the transaction lifecycle
- Records must explain and support reporting
- Accessibility and retrieval
- Storage location and outsourcing
- Maturity versus termination
- Legal holds and investigations
- Do not confuse other retention periods
- Exam method
- Records after a merger or system migration
- Regulatory request readiness
- Retention and secure deletion
- Exam takeaway
Reporting a transaction to the Hong Kong Trade Repository does not eliminate the obligation to retain supporting records. Retention gives regulators and firms a way to reconstruct the reportable transaction and demonstrate what was submitted.
The basic retention timeline
The SFC and HKMA FAQ on the Reporting Rules states that records of a reportable transaction are kept for the life of the transaction and for a further five years after maturity or termination. The retention clock therefore does not simply start on the trade date; an open transaction remains within the period until it ends.
What kinds of records
Schedule 2 to the Reporting Rules specifies records to keep in relation to the reporting obligation. Depending on the entity and activity, these can support transaction details, lifecycle events, reporting submissions and corrections. Consult the rule schedule and current SFC/HKMA instructions for the exact record set rather than assuming a single confirmation is enough.
Do not mix up retention rules
Licensed corporations may have separate general books-and-records obligations, and other OTC derivative rules may prescribe different records or periods. Identify the regulated entity, record type and legal source before calculating retention. The five-years-after-maturity-or-termination rule discussed here concerns reportable transaction records under the Reporting Rules.
Operational control
- Link the record to the transaction identifier and repository submission.
- Preserve corrections, lifecycle events and evidence of reporting.
- Prevent premature deletion while the transaction remains outstanding.
- Apply a legal hold or longer retention period if another rule, investigation or litigation requires it.
- Document secure deletion only after all applicable periods expire.
The retention clock follows the transaction lifecycle
For a reportable OTC derivative transaction, the reporting rules generally require records to be retained while the transaction remains outstanding and for at least five years after it matures or is terminated. The post-termination period is not measured from trade date. Long-dated trades can therefore require a much longer total retention period than five years from execution. Check the current rule text for the precise scope and any person-specific obligation.
Records must explain and support reporting
The records should allow the transaction and its lifecycle to be reconstructed, including terms, counterparties, events, valuations, collateral or margin information where applicable, and submitted reports. Keep supporting contracts, confirmations, amendments, records of calculations, source data and corrections. A report receipt alone may not explain how the data was derived or whether it was accurate.
Accessibility and retrieval
Retention is useful only if records remain readable, searchable and retrievable for the regulator or internal review. Index by transaction identifier, counterparty, date and event. Maintain the ability to connect the reported record with source systems even after platforms are replaced. Data migrations should preserve metadata, audit trails and evidence that no fields were lost.
Storage location and outsourcing
Firms may use electronic archives or service providers, subject to the applicable rules and access requirements. Outsourcing storage does not remove the reporting person’s duty to ensure the records can be produced. Contracts should provide data access, continuity, security, export on exit and support for regulatory requests. Test retrieval instead of relying on the provider’s promise that files are backed up.
Maturity versus termination
A transaction may terminate early, mature on its scheduled date, or be partially amended or novated. Determine the event that legally ends the relevant transaction and document the date used to start the retention tail. For a portfolio of trades under a master agreement, one trade’s termination does not necessarily end another trade. Track each transaction or legally relevant record set separately.
Legal holds and investigations
If an investigation, dispute, audit or regulatory request is open, preserve relevant records beyond the ordinary destruction date where required. Suspend automated deletion for affected data and document the hold scope. A retention schedule should distinguish a routine expiry from an active legal or regulatory preservation duty. Never destroy records to avoid disclosure or scrutiny.
Do not confuse other retention periods
Licensed corporations may have separate recordkeeping duties under the SFO, Code of Conduct, AML/CFT rules or other regimes. Those periods can use different trigger dates and apply to different records. The five-year-after-maturity/termination rule in the OTC reporting framework should not be generalized to all securities records or used to shorten a longer obligation.
Exam method
Name the OTC reporting rule, state retention during the life of the transaction plus at least five years after maturity or termination, and identify records that support the report and lifecycle. Then distinguish this period from broader intermediary recordkeeping rules. If facts involve an amended or novated trade, identify the relevant transaction end date rather than using original execution.
Records after a merger or system migration
A reporting entity that merges, changes vendors or retires a system must preserve the complete audit trail through the remaining retention period. Map old transaction identifiers to current records, retain the underlying source data and test sample retrieval after migration. A vendor exit plan should include export format, metadata and secure access—not just a PDF archive.
Regulatory request readiness
Assign an owner to respond to SFC or HKMA record requests and know where each data set resides. A retrieval drill can test that a transaction can be produced with its lifecycle, report acknowledgments and supporting calculations. Keep an index and escalation route so a request is not delayed by staff turnover or obsolete systems.
Retention and secure deletion
At the end of the statutory period, apply the firm’s retention schedule and any legal hold before secure deletion. Prevent unauthorized access during retention and document destruction approvals. Indefinite retention is not automatically safer; preserve what the regime requires, protect it appropriately and delete it only when no applicable duty or hold remains.
Exam takeaway
For reportable OTC transaction records, keep them while the transaction is outstanding plus five years after maturity or termination. Check the specific record and entity because separate rules may require longer retention.
Common questions
Does the five-year period begin on trade date?
No. The cited FAQ says records are kept while the transaction is outstanding and for five years after it matures or terminates.
Does this period cover every record a securities firm has?
No. It applies to reportable transaction records under the Reporting Rules; other duties may differ.
Can an entity destroy a record after five years if another law requires longer retention?
No. Apply the longest relevant legal, regulatory, preservation or litigation requirement.