HK tokenized-deposit treasury
A company moves HKD between banks while bank approval, receiving-bank confirmation, and the final close record stay connected.
Overview
A company moves HKD between banks while the sending bank controls release, the receiving bank confirms receipt, and finance can see the final result.
Use when a bank wants a Hong Kong corporate treasury transfer to stay on one governed operating lane instead of splitting treasury instruction, bank release, destination confirmation, and reconciliation across separate teams.
Route coverage
- One fixed Hong Kong treasury settlement route
- Bank-money controls are matched before release begins
- Governed release, destination confirmation, and finality stay on one operating record
- Ledger reconciliation and close publication complete the route
Infrastructure
- Programme setup and participant controls
- Funding reservation and liability authorization
- Settlement-reference and destination-bank confirmation tracking
- Reconciliation close record and publication state
Lifecycle stages
| Stage | Flow steps |
|---|---|
| Program Perimeter | Register the treasury mandate, route basis, and destination boundary before release can begin; Keep programme scope and wallet boundary aligned on one operating record |
| Participant Controls | Confirm receiving readiness, control-account coverage, and operating-window posture; Keep participant checks and release controls visible before funding and issuance |
| Funding Issuance | Validate source funding and authorize the tokenized-deposit liability record; Keep funding reservation and issuance posting aligned on one operating record |
| Governed Release | Submit the treasury release and record the decision basis before settlement handoff; Keep maker-checker, cutoff, and duplicate-control posture visible on the release queue |
| Settlement Confirmation | Queue the settlement reference, capture receiving confirmation, and match finality before close; Keep settlement state and exception posture visible on one monitor |
| Reconciliation Close | Match ledger rows, publish the close record, and release the final reconciliation export; Keep reconciliation and publication state visible as the close outcome |
Setup reference
| Field | Explanation | Related terms |
|---|---|---|
| Treasury route | Fixed for this case. Keeps the workflow on one tokenized-deposit treasury route rather than switching between bank-money variants. | Tokenized deposit, Bank money |
| Participant perimeter | Fixed for this case. Keeps the route limited to the named treasury and receiving-bank perimeter used in the mounted Hong Kong workflow. | |
| Settlement currency | Fixed for this case. Keeps the route scoped to one HKD settlement workflow. | |
| Settlement path | Fixed for this case. Keeps the workflow on a cross-bank treasury settlement path. | |
| Treasury intent | Fixed for this case. Keeps the route aligned to one treasury liquidity movement posture. | |
| Receiving posture | Fixed for this case. Keeps the route on a pre-cleared receiving-bank posture before release begins. | Receiving institution |
| Release discipline | Fixed for this case. Keeps the treasury route on governed release with a defined return posture. | Release disposition |
| Operating window | Fixed for this case. Keeps the route inside the bank operating window used for settlement confirmation and close. | Operating window |
| Close package | Fixed for this case. Keeps reconciliation and close-pack publication visible before the route is considered complete. | Liability evidence |