Fix product, disclosure version and consent purpose; distinguish product consent from authorization to sign the document.
If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.
| Control point | Applicable design |
|---|---|
| Actors | Investor and investment product administrator |
| Trigger | Confirm product, disclosure version and trading authority |
| Source system | CRM / investor records |
| Documents | Product-specific risk disclosures and consent documents |
| Approval control | Confirm product, disclosure version and trading authority |
| Identity and authority | Match the participants, representation authority and document scope before requesting authorization. |
| Signing route | API or Agent connects an agreed VNeID/RS-HUB or Trusted SIC route; fallback requires an approved deployment policy. |
| Business exceptions | Consent withdrawal; new disclosure version; wrong product |
| Downstream system | Investor records / Audit |
Fix product, disclosure version and consent purpose; distinguish product consent from authorization to sign the document.
Investor; product owner; compliance review the document and representation authority before authorizing signing.
Correlate the signing request with risk disclosure and investor consent and its approved version; retain the transaction reference.
The approved provider creates the signature using the applicable certificate and authorization; do not change routes without approval.
Retain disclosure version, review/consent time where available, signer and result correlated to the product.
Consent withdrawal; new disclosure version; wrong product.
The CRM / investor records owner decides whether to amend, cancel or request a new signature. Reconcile delayed callbacks against the original transaction before creating a replacement.
This is a reference implementation workflow. The organization determines business policy, legal requirements and acceptance conditions.
