The CRM/ERP finalizes buyer, terms and agreement version. An amendment has its own version and reference to the original agreement.
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 | Sales, legal reviewer and customer |
| Trigger | Approve terms, price and representation authority |
| Source system | CRM / ERP |
| Documents | Final quotation, agreement and annexes |
| Approval control | Approve terms, price and representation 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 | Renegotiation; incorrect annex version; customer declines |
| Downstream system | ERP / DMS |
The CRM/ERP finalizes buyer, terms and agreement version. An amendment has its own version and reference to the original agreement.
Sales; legal reviewer; seller/buyer representatives review the document and representation authority before authorizing signing.
Correlate the signing request with sales agreement and amendment 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 agreement and amendments in the customer record; return status to CRM/ERP after version correlation.
Renegotiation; incorrect annex version; customer declines.
The CRM / ERP 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.
