Daily versus monthly account statements under Hong Kong client rules

Daily and monthly statements are separate controls. The daily rule is transaction-focused: it applies to relevant margin-account activity. The monthly rule is a periodic account summary for a client whose assets are held by the intermediary or its associated entity. Do not treat the daily statement as a universal report of every account asset, or assume a monthly statement is unnecessary merely because nothing traded.

Daily statements are linked to margin transactions

The SFC's client-money FAQ explains that the daily statement obligation concerns margin transactions. The statement should show the relevant margin transaction and collateral information required by the rule. It is not automatically a full inventory of unrelated client assets merely because the client also has another account or position with the firm. Keep the scope of the daily report connected to the qualifying transaction.

Monthly statements look at assets held during the month

The monthly statement duty is tested by whether the intermediary or its associated entity held client assets during the relevant month, including assets received during that month. The SFC FAQ illustrates that timing is based on the period in which assets were held, not simply on the date a report is physically delivered. A statement can therefore be issued shortly after month-end and still relate to the preceding month.

Separate the trigger, period and contents

1. Identify the trigger: a relevant margin transaction points to the daily-statement rule; holding client assets during the month points to the monthly rule.
2. Identify the reporting period and the deadline in the current rule text. Do not substitute an informal calendar assumption for a prescribed deadline.
3. Check which account and asset information the specific rule requires. The daily margin statement is not necessarily the monthly account summary.
4. Check for the applicable rule's exceptions and whether the client has agreed to an electronic delivery method where permitted.

Common exam mistakes

• Assuming every client receives a daily full-account statement.
• Assuming no monthly statement is needed if there was no trade, even though client assets were held.
• Confusing the date assets were received or held with the date the statement was sent.
• Treating the SFC FAQ as a substitute for checking the current Client Money Rules and Code of Conduct provisions.

Key takeaway

For the daily statement, look for the relevant margin transaction. For the monthly statement, look for client assets held during the month. Then apply the precise scope, deadline and exceptions in the current rule.

Statement duties are not all the same

Client statements help customers understand money and securities movements, but the applicable frequency depends on the type of account and the relevant rules. A monthly statement is not automatically required for every client in every circumstance, and a daily statement rule should not be casually generalized to all intermediaries. Identify whether the firm holds client money, client securities or both, which rule applies, and whether a transaction or balance triggers a specific reporting obligation. The firm should maintain internal records even where the customer-facing statement cadence differs.

Reconciliation and exception handling

A reliable statement process begins with accurate ledgers, bank and custodian records, settlement movements and fee calculations. The firm should reconcile relevant client accounts, investigate differences, correct errors promptly and ensure the statement reflects the actual position for the prescribed period. Returned mail, failed electronic delivery, bounced notifications and disputed transactions should enter a tracked exception process. A statement generated from unreconciled or stale data can mislead even if it is sent on time. Access logs and delivery evidence help establish what information was provided and when.

What the client should be able to see

The purpose is meaningful transparency: opening and closing balances, receipts and payments, transactions, positions and charges as required by the governing rule. The statement format should not hide a material debit or make it difficult to identify how securities or money moved. Firms should provide a clear contact path for discrepancies and investigate a customer’s question against source records. If an error is found, the correction should be traceable and the firm should assess whether affected customers or regulators need notification under applicable requirements.

Exam method

Do not answer from the everyday meaning of “daily” or “monthly.” Link the frequency to the specific Client Money Rules or Client Securities Rules and read the facts for the activity and holdings. Distinguish a statement requirement from internal daily reconciliation, which may be a separate control. Also distinguish delivery of a statement from record retention. A common distractor swaps these concepts: a firm may need frequent internal control checks even where a particular customer statement is sent periodically. Check the relevant rule rather than assuming one universal cadence.

Implementation and review

Customers may choose electronic delivery where permitted, but the firm remains responsible for reliable access, security and the applicable delivery timeline. A portal notification is not necessarily proof that the customer could retrieve the statement, so keep delivery and availability logs. Where a customer has multiple capacities or accounts, the firm should make clear which assets are included and avoid presenting a partial statement as a consolidated view. Complaints about missing statements should be investigated as a control issue, especially if the underlying records also show unexplained movements.

A practical review checklist

A sound test is to take a transaction from the ledger and verify that it appears in the correct customer statement for the correct period, with all required charges and balance effects. Then confirm that the statement reached the customer using an approved channel. Reconcile any omitted, duplicated or reversed transactions and document the correction. This simple end-to-end sample tests both data accuracy and delivery, whereas checking only that the monthly batch ran tests neither completely.