Malaysia regulated broking + custody
Malaysia institutional broker-control workflow across CMSL policy admission, cash-upfront DAX route lock, DAC segregation, liquidation proceeds confirmation, and named-beneficiary bank-release close.
Overview
Malaysia broker-control lane covering CMSL admission, DAX route lock, DAC segregation, liquidation proceeds, and named-beneficiary bank release.
Treasury broker-control lane. StableNexus keeps CMSL admission, route lock, DAC segregation, liquidation proceeds, and bank-release evidence aligned while DAX, DAC, and bank rails stay partner-led.
Route coverage
- 4-stage Malaysia broker-control lane
- CMSL policy dossier, client classification, and dealing readiness
- Cash-upfront DAX route lock with operator-only contingency governance
- Execution settlement, DAC segregation, and beneficial-owner posting
- Liquidation proceeds, named-beneficiary bank release, and close pack
Infrastructure
- CMSL gate, asset-concurrence, and trader-approval controls
- Registered DAX route lock with expiry, approval, and contingency policy
- DAC custody segregation, client-asset receipt, and beneficial-owner evidence
- Bank release authority, beneficiary verification, proceeds advice, and reconciliation pack
Lifecycle stages
| Stage | Flow steps | Notes |
|---|---|---|
| Broker Policy Gate | Capture the institution, client class, trader mandate, target asset, DAC destination, and exit intent before dealing approval opens; Hold the run until KYB, UBO, board mandate, asset concurrence, and broker-notification controls all clear; Keep CMSL dealing readiness and DAC custody path on the same dossier; End the step on a cleared policy pack, not a generic approved request | |
| Funding And Route Lock | Confirm cash-upfront MYR availability before route lock can be approved; Lock the registered-DAX route, expiry window, and execution approval on one desk; Keep any foreign regulated contingency as operator-only fallback with due-diligence evidence, not as an equal public route; Preserve funding, lock, and contingency policy before the order is released | The foreign regulated counterparty path stays contingency-only and should not render like a peer public route. |
| Execution And Dac Custody | Carry the locked route into venue order, trade confirmation, and settlement posting; Book the filled position into the named DAC account with client-asset segregation evidence; Keep beneficial-owner continuity and DAC acknowledgement visible before any liquidation intent opens; Publish a custody-posted position rather than a generic executed trade | |
| Withdrawal And Close | Confirm liquidation intent, net proceeds, beneficiary-bank verification, and release authority as separate controls; Hold bank release on any entitlement, proceeds, or beneficiary mismatch; Record bank reference, credit advice, and reconciliation close on the same release desk; Publish the close pack only after proceeds and bank outcome are both final | Final state must read like a Malaysia bank-release desk with proceeds advice and published evidence, not a generic payout queue. |
Setup reference
| Field | Explanation |
|---|---|
| Trade size | Sets the MYR amount carried through funding, execution, custody, and payout. Determines the values shown across the workflow records. |
| Traded asset | Sets what treasury is buying into custody. Determines the execution, custody, and release path. |
| Custody destination | Identifies where purchased assets are held. Determines the custody destination used after execution. |
| Payout beneficiary | Identifies who receives the payout. Determines who is checked and named in the payout records. |
| Payout destination | Identifies where MYR is paid out. Determines the bank route used at release and close. |
| Execution channel | Supports more than one execution channel. Controls how the trade is sourced before custody. |
| Funding currency | Fixed for this case. Scoped to MYR funding. |