139 Queen's Road
Central, Hong Kong
Bottom line
In its 23 June 2026 consultation conclusions, the SFC confirmed it will implement the Hong Kong Investor Identification Regime for the derivatives market (HKIDR-DM) substantially as consulted and adopt a new paragraph 5.6A of the SFC Code of Conduct. The regime is directed at licensed corporations (LCs) and registered institutions (RIs) that submit or arrange HKFE orders, conduct HKFE block trades, undertake covered proprietary trading, or provide covered derivatives brokerage. It will require client-specific Broker-to-Client Assigned Numbers (BCANs), client identification data (CID) mapping and order tagging for listed derivatives. (Conclusions, paras. 6, 17, 21–24 and 69; Appendix C, proposed Code para. 5.6A(b)–(c).)
The requirements are not yet in force. The SFC says the Code amendments and implementation date will be Gazette-published and take effect on a date it determines, coordinated with HKEX’s Orion Derivatives Platform (ODP), after system testing and market rehearsals. The current target is Q2 2028, subject to the ODP timetable. An implementation circular, including consent requirements, is due by September 2026. (Conclusions, paras. 11–13 and 58–60, 69–71.)
For asset managers, the immediate question is whether the group or service model carries out a specified activity, submits or arranges HKFE orders, or instead trades through a broker and must provide the right account-level CID and consent. Under the proposed text, for a collective investment scheme or discretionary account, the relevant “client” is the fund, discretionary-account holder or asset management company that opened the trading account, as applicable—not automatically each underlying investor. (Appendix C, proposed Code para. 5.6A(b)(xiv), (m)(iv).)
Do today
Should — assign an accountable implementation owner. Compliance should name a business, Operations and Technology workstream lead; produce a short applicability map covering Hong Kong futures, options and stock options, execution routes, block trades, aggregation and overseas affiliates before the SFC’s September 2026 circular.
Should — inventory every affected account and order path. Operations should identify the legal entity that opens each futures/options account, the first non-regulated person in each broker chain, account type (including joint, fund and discretionary accounts), and whether the firm submits, arranges to submit or merely originates each order. This determines who assigns the BCAN and collects CID. (Appendix C, proposed Code para. 5.6A(c)–(e), (m).)
Should — begin consent and data-gap analysis. Legal and Data Privacy should compare existing HKIDR-S notices and consents against the new derivatives purpose, identify clients needing fresh consent, and retain an audit trail of the analysis. Prior securities-market consent may not cover the derivatives-market transfer; SFC guidance and a tailored template are still to come. (Conclusions, paras. 63–64.)
Should — reserve the technology change. Technology should assess ODP-compatible order interfaces, BCAN validation, automated tagging and mapping-file processes. ODP is expected to reject orders or quotes without a BCAN or with an invalid-format BCAN, so manual exception handling is not a credible primary control. (Conclusions, para. 45; Appendix C, proposed Code para. 5.6A(i).)
Consider — obtain execution-party commitments. Legal and Operations should identify agreements with non-LC/non-RI receiving parties that must transmit a tagged BCAN or aggregate-order code onward, and plan amendments where required. (Appendix C, proposed Code para. 5.6A(g).)
Check
Scope and allocation
Does any group entity submit or arrange HKFE on-exchange orders, carry out block trades, conduct Type 1 stock-options or Type 2 futures/options proprietary trading, or provide derivatives brokerage? If not, which executing broker will be the relevant regulated intermediary (RRI)? (Appendix C, proposed Code para. 5.6A(b)(xiv), (xvi).)
For each broker chain, have we located the last RRI whose direct client is not an RRI? That firm bears the core BCAN, CID and mapping-file responsibility, though submissions may be made through another RRI. (Appendix C, proposed Code para. 5.6A(d).)
Are overseas affiliates separately identifiable? A single BCAN cannot stand for multiple non-RRI overseas affiliates; head office and branches of the same overseas affiliate are, however, treated as the same entity. The SFC may issue cross-border FAQs. (Conclusions, paras. 21–22, 36–37.)
Data and consent
Can the responsible RRI produce the prescribed CID—name, issuing jurisdiction, document type and number—from the prescribed identity-document hierarchy? For corporate clients, an LEI registration document is first in the hierarchy, but the regime does not require annual LEI renewal where CID has not changed. (Appendix C, proposed Code para. 5.6A(n)–(o); Conclusions, paras. 42–43.)
Do onboarding, periodic review and account-event controls promptly update the mapping file for CID changes, new or closed accounts? Is there a contractual or other measure requiring clients to report changes? (Appendix C, proposed Code para. 5.6A(k)–(l).)
Is express consent collected before a natural person’s BCAN-CID mapping is filed and retained for the client relationship plus at least two years? If consent cannot be obtained, the proposed rule permits only position-closing, not new-position, orders for that person. (Appendix C, proposed Code para. 5.6A(p)–(q).)
Orders, aggregation and readiness
Do order-management controls preserve one BCAN for the same account, distinguish where multiple accounts justify separate BCANs, and include both the RRI’s CE number and BCAN (or prescribed aggregate-order code) in the order information? (Appendix C, proposed Code para. 5.6A(c), (f), (i).)
Can the desk report underlying BCANs for an executed aggregated block order within T+3 business days? For cancelled or partially executed orders, is the allocation process capable of reporting only the executed portion? (Conclusions, paras. 50 and 52.)
Does the implementation plan distinguish existing clients—whose CID is to be submitted by T-1—from new clients trading on account-opening day and accounts dormant for at least 24 months, for which same-day submission by an HKEX cut-off is contemplated? Confirm exact cut-offs and migration milestones in the forthcoming circular. (Conclusions, paras. 38–40.)
Keep an eye on
September 2026 implementation circular. Reassess the project when the SFC publishes the circular, especially its consent guidance, key activity dates and any client migration requirements. (Conclusions, paras. 12, 69.)
HKEX technical specifications, testing and training. The SFC and HKEX will provide testing and industry training; ODP uses a unified binary protocol. Reassess system design when HKEX releases final validation rules, formats and rehearsal dates. (Conclusions, paras. 45, 60.)
Timing and FAQs. The Q2 2028 date is conditional on ODP completion; the SFC will update it if ODP slips. The SFC has also established HKIDR-DM-faq@sfc.hk and intends to publish FAQs for common or wider-industry questions. (Conclusions, paras. 59, 70–71.)
Why this matters
HKIDR-DM is designed to give the SFC investor identity information at the trading-activity level, complementing—not replacing—the Large Open Position Reporting Regime, which monitors position concentration once reporting thresholds are exceeded. (Conclusions, paras. 27–28.) The control burden is therefore an execution-data and client-data programme, not simply a reporting overlay.
The implementation runway is comparatively generous, but delivery has hard dependencies: data privacy consent, account taxonomy, broker-chain allocation, counterparties’ onward-transmission arrangements, and ODP-ready tagging. Leaving those decisions to the final technology release is how an 18–24 month migration window becomes surprisingly short. (Conclusions, paras. 40, 45 and 58–60.)
Scope and timing
Regulator/jurisdiction: SFC / Hong Kong.
Document: consultation conclusions, dated 23 June 2026; the SFC has decided to implement the proposals, but the Code amendments remain subject to Gazette publication and a commencement date.
In scope: covered LC and RI proprietary and brokerage activity for futures contracts, options contracts and stock options traded through HKFE’s trading system, including on-exchange and block-trade orders.
Target start: Q2 2028, coordinated with ODP and conditional on testing and market rehearsals.
(Conclusions, paras. 6, 59, 69–71; Appendix C, proposed Code para. 5.6A.)
This guidance note does not constitute legal advice. Enforcement matters described involve allegations only; no findings of wrongdoing have been made by a court unless expressly stated. AI, under human supervision, has been used for research and drafting assistance. All content has been reviewed by a human prior to publication.
