SG institutional OTC workspace
Run a Singapore institutional OTC workspace where asset classification fixes the SG legal lane before custody confirmation, bilateral execution, settlement affirmation, booking, and reconciled close.
Overview
Institutional OTC workspace fixes SG classification first, then keeps custody scope, bilateral RFQ execution, settlement affirmation, and reconciled close on one desk view.
Institutional-only SG OTC workspace. StableNexus fixes the classification lane, custody scope, RFQ state, settlement posting, and reconciled close while counterparties, custodians, and settlement rails stay explicit.
Route coverage
- 4-stage SG institutional workspace
- Classification-gated custody scope, RFQ commit, settlement booking, and reconciliation
- Custody, booking, and exception ownership stay linked
- Workspace packet and closeout evidence for operations, treasury, and finance
Infrastructure
- Custody, RFQ blotter, settlement, and reconciliation workspaces
- Classification badge, statute lane, and approval-chain continuity
- Exception triage with archive continuity
- Workspace packet and closeout evidence across operations, treasury, and finance
Lifecycle stages
| Stage | Flow steps |
|---|---|
| Counterparty Custody | Fix the SG classification lane before the bilateral RFQ desk opens; Bind counterparty type, custody scope, trade side, and starting balance to the workspace; Carry the same applicable statute, notional, and custody context into execution and settlement; Keep the classification decision visible all the way into post-trade booking and close |
| Quote Execute | Request bilateral route quotes on the approved OTC desk; Lock the selected quote, approval chain, and trade reference; Commit the trade only while the quote window, statute lane, and controls remain live; Pass the matched execution record into a DvP booking handoff rather than a treasury-close shortcut |
| Settle Book | Publish the settlement instruction and consume the matched affirmation callback; Post allocations, booking references, and settlement state against the committed trade; Keep settlement, booking, and exception state visible on one desk; Release the reconciliation run only after booking is complete |
| Reconcile Evidence | Match settlement, booking, and custody records on the shared reconciliation rail; Resolve exceptions before the OTC workspace packet and closeout evidence are published; Release export sets, archive manifests, and closeout evidence from the same close cycle; Keep the SG OTC workspace intact for operations, treasury, and finance after the trade is complete |
Setup reference
| Field | Explanation |
|---|---|
| Trade notional | Sets the notional carried through affirmation, booking, settlement, and reconciliation. Determines the values shown across the workflow records. |
| Execution path | Supports more than one execution path. Controls how the trade is sourced before settlement. |
| Traded product | Fixed for this case. Scoped to one traded product or pair. |
| Trade direction | Fixed for this case. Determines how settlement and booking are read. |
| Custody model | Fixed for this case. Scoped to one custody model. Determines how custody confirmation is handled. |
| Settlement pattern | Fixed for this case. Scoped to one settlement pattern. Determines how affirmation and settlement are recorded. |
| Counterparty class | Fixed for this case. Scoped to one counterparty class. Determines which counterparty context appears in the workflow. |