Delegation in Fund Custody: HKSI Paper 19
A depositary may use sub-custodians and other service providers, but delegation creates risks that require ongoing oversight.
- Evaluate capability, legal and operating environments, account controls, reconciliations, reporting, audit evidence and incident handling.
- Monitor in proportion to risk and investigate exceptions rather than treating appointment as proof of control.
On this page11 sections
- Why custody chains use delegates
- Due diligence and continued review
- Risk-based monitoring
- Worked case: local sub-custodian
- Failure and contingency
- Concentration and interconnected failures
- Incident escalation and remediation
- Non-custodised assets and delegates
- Sub-delegation and visibility
- Testing an exception sample
- Oversight reporting and service levels
Why custody chains use delegates
Funds invest across markets with different settlement systems, registration rules and operating hours. A depositary may appoint sub-custodians or other providers to hold or process assets. The custody chain can include scheme, depositary, delegate, local agent, bank or central securities depository. Each handoff creates legal, operating, data and insolvency exposure.
Maintain an inventory of where assets are held, the legal entity and account title, how rights are evidenced, protections, who can move property and how records are reconciled. Consider whether assets are segregated and how the fund retrieves them if the delegate fails. These are ongoing safeguards, not one-time procurement checks.
Due diligence and continued review
Before appointment, evaluate legal status, expertise, financial resources, systems, staffing, controls, market access and ability to protect assets. Review service terms, reporting, audit access, incident notice, continuity, data security and termination or transfer arrangements. A provider’s reputation does not prove its controls fit this fund.
After appointment, review reconciliations, aged breaks, instruction controls, audit findings, incidents, service changes and concentration. Reassess when a delegate enters a market, changes ownership or systems, or holds a new asset type. The syllabus explicitly covers delegate appointment and oversight.
Risk-based monitoring
Monitoring depth should reflect asset type, jurisdiction, custody model, concentration, volume, incidents and evidence quality. A transparent market with timely independent statements differs from a complex market with local registration and delayed reporting. Risk-based does not mean ignoring a low-probability event with severe consequences.
Assurance reports can help, but examine scope, period, qualifications, exceptions and whether they cover the specific service. A clean report may not cover the account structure used by the fund or a recent system change. Combine assurance with transaction-level reconciliations and exception follow-up when warranted.
Worked case: local sub-custodian
A local provider holds securities in an omnibus account and sends monthly position files. Assess how the fund’s beneficial interest is identified, how records reconcile, what other clients share the account, whether local law protects assets and what records survive insolvency. Monthly files may be too slow to detect a material intervening transfer.
For a missed corporate action, review how the provider receives notices, identifies entitlements and reconciles proceeds. Obtain event evidence and compare the fund ledger with issuer or market information. Escalate repeated failures, enhance review or consider alternate custody, and ensure any transfer plan preserves continuity and rights.
Failure and contingency
Insolvency of a depositary, delegate, bank or central securities depository may delay access, expose the fund to a shortfall or create legal uncertainty. Identify asset location, protections, account structure, record access and transfer options. A fund ledger balance does not alone establish legal recoverability.
A contingency plan identifies decision makers, communications, replacement providers, data access, settlement continuity and reconciliation. Test whether records are portable and current. On failure, safeguard property, establish facts and communicate through appropriate governance channels.
Concentration and interconnected failures
Concentration at one delegate can make a routine service issue material to the entire fund. Consider market, asset class, account, geography and provider concentration. A provider can also depend on local agents, technology vendors, banks or CSDs; assess these connections when mapping custody risk.
Insolvency or operational failure may affect access to both assets and records. Determine whether fund holdings are segregated, how reconciliations evidence them, what local law says and how quickly substitute arrangements can operate. Scenario exercises can reveal gaps in contact details, data exports and authority.
Incident escalation and remediation
A missed reconciliation, cyber incident, settlement outage or unexplained movement should be logged and assessed for scope. Determine whether the issue affects one transaction, one account, several funds or the delegate’s broader control environment. Ask for evidence of containment and a credible root-cause analysis.
The depositary should decide whether to increase monitoring, restrict activity, notify governance parties or consider replacing the provider, consistent with its authority and applicable requirements. Track remediation to closure and review whether investor communication or regulator notification is required. Keep the rationale for continuing or ending the arrangement.
Non-custodised assets and delegates
Some property cannot be held through a conventional sub-custody account. A provider may maintain a register, contract, key or legal record instead. The depositary should understand what establishes the CIS right, who controls transfer, how existence and valuation are checked and whether the evidence can be accessed during insolvency.
The oversight method should match the asset. Reconcile registers or contractual schedules, verify counterparties and key terms, inspect independent confirmations and review changes. Do not conclude that an asset is protected simply because a delegate’s system lists it.
Sub-delegation and visibility
A provider may appoint another party, creating another handoff and jurisdiction. Know whether sub-delegation is permitted, who selected the party, what terms apply, where property is held and what reporting flows back. If the depositary cannot see the underlying location or records, it may not be able to assess exposure.
Review changes in the chain and require prompt notification where appropriate. A previously acceptable arrangement can change through a merger, new local agent or market migration. Update the custody map and test whether reconciliations, legal protections and contingency plans still work.
Testing an exception sample
A risk-based review can select transactions or positions for independent testing. Trace a sample from instruction to external statement and compare quantities, account titles, settlement and subsequent reconciliation. Include exceptions and manual overrides, not only clean items.
Document sample rationale and limitations. A small sample cannot prove every asset is correct, but can test whether the process operates and identify patterns. If a failure is found, broaden testing based on severity and consider whether other funds use the same provider or control.
Oversight reporting and service levels
Set expectations for position reporting, reconciliation frequency, exception aging, incident notice and escalation. Monitor whether reports arrive on time and include all relevant assets and accounts. A complete report received too late may not support oversight when the fund deals daily.
Review service-level breaches and repeated operational errors. Determine whether staffing, systems, market changes or sub-delegation caused the problem. Require a corrective plan and test it. Escalate if the provider cannot meet controls needed to protect fund property.