Saudi sukuk + private-debt operations
Run a Saudi regulated-finance lane across issuer perimeter, investor qualification, subscription-book control, authoritative register confirmation, profit servicing, and reconciled close without drifting into retail-crypto framing.
Overview
Saudi sukuk and private-debt programmes stay control-ready across investor qualification, authoritative register confirmation, and profit-servicing close.
Route coverage
- Issuer perimeter through servicing close
- Sukuk and private-debt programs
- Book-entry first, ledger optional
- Profit events through redemption
Infrastructure
- Issuer and SPV perimeter controls
- Eligibility and appointed roles
- Register confirmation, holder reports, and settlement records
- Profit-servicing notice, payment reports, and reconciliation close
Lifecycle stages
| Stage | Flow steps |
|---|---|
| Program Setup | Verifies the issuer perimeter and binds the appointed-role pack before subscriptions open |
| Qualification Subscription | Verifies qualified-investor evidence, records admitted subscriptions, matches funding references, and locks the investor book before issuance release |
| Issue Allocate Register | Runs issuance release, register confirmation, holder reporting, and settlement linkage while keeping the partner register as the legal source |
| Service Redeem Reconcile | Publishes the profit notice, binds payment instructions and payment reports, and closes the Saudi packet through reconciliation against the authoritative register |
Setup reference
| Field | Explanation | Related terms |
|---|---|---|
| Programme size | Sets the issuance amount carried through qualification, allocation, settlement, and servicing. Determines the values shown across the workflow records. | |
| Instrument structure | Supports more than one instrument structure. Controls the terms and servicing path. | Sukuk, Shariah |
| Investor eligibility | Sets who the programme is intended for. Controls who can be qualified and allocated. | |
| Register model | Supports more than one register model. Controls how holder records are maintained. | |
| Servicing event | Supports more than one servicing path. Controls which downstream event the workflow follows. | |
| Tenor | Fixed for this case. Keeps the workflow on one programme timeline. Determines the servicing and maturity horizon. | |
| Settlement method | Fixed for this case. Keeps the workflow on one issuance settlement method. Determines how settlement is recorded. |