Saudi fund-unit servicing
Run a Saudi fund-unit servicing lane across fund perimeter, qualified-investor controls, official unit-register continuity, NAV or redemption servicing, and reconciled close.
Overview
Saudi fund-unit servicing kept control-ready across offer basis, investor qualification, official unit records, and post-issue servicing.
CMA-side fund-unit lane. StableNexus orchestrates perimeter controls, investor qualification, dealing instructions, official unit-register continuity, and servicing while fund administration, transfer-agent, custody, and closeout execution remain partner-led.
Route coverage
- Perimeter, distribution basis, and role pack
- Investor classification, suitability, and subscription acceptance
- Unit allotment with official unit-register continuity
- NAV, distribution, redemption, and reconciliation evidence on one spine
Infrastructure
- CMA fund perimeter, offer basis, and role controls
- Investor classification, suitability, and subscription capture
- Official unit-register, transfer-agent, custody, and nominee continuity
- NAV, distribution, redemption, and reconciliation pack
Lifecycle stages
| Stage | Flow steps | Notes |
|---|---|---|
| Program Setup | Record the fund perimeter, unit class, and dealing calendar; Bind the Saudi offer/distribution basis and appointed-role pack; Confirm the custody and official-record model before launch; Open the fund window only after all setup controls clear | CMA-facing setup step; no public crypto/VASP route is implied. |
| Qualification Subscription | Classify the investor and apply the suitability policy; Capture signed subscription acceptance against current fund terms; Confirm cleared cash before the dealing cut-off closes; Admit the order to the allotment queue | Keep the cash leg conventional; show matched funding, not wallet funding. |
| Issue Allocate Register | Apply the issue price or NAV point to admitted cash; Allot fund units and update the official transfer-agent register; Confirm custody/nominee entitlements and issue the holder statement; Publish the register snapshot and variance check | Official ownership remains anchored to the partner-administered register/custody model. |
| Service Redeem Reconcile | Import NAV, distribution, or redemption events from the fund administrator; Reconcile cash, units, and investor-position states; Publish the servicing notice and close pack; Stop the cycle if a NAV variance or reconciliation break remains unresolved | Exception handling is part of the lane, not an afterthought. |
Setup reference
| Field | Explanation | Related terms |
|---|---|---|
| Fund amount | Sets the value carried through the selected fund action. Determines the amounts shown in acceptance, register, and close records. | |
| Suitability scope | Sets who can enter this fund action. Controls which suitability checks apply. | |
| Unit register model | Supports more than one register model. Controls how unit ownership is recorded. | Public fund, NAV basis |
| Fund action | Supports more than one fund action. Controls which branch the workflow follows. | Public fund, NAV servicing |
| Fund product | Fixed for this case. Scoped to one fund product. | |
| Dealing currency | Fixed for this case. Scoped to one dealing currency. | |
| Dealing settlement mode | Fixed for this case. Scoped to one dealing settlement mode. Determines how acceptance and close are recorded. |