The ERP checks supplier, value and purchasing authority; acceptance is signed at a separate handover step.
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 | Buyer, supplier and approver |
| Trigger | Review budget, supplier and purchasing authority |
| Source system | ERP / procurement system |
| Documents | Purchase order, supply agreement and acceptance record |
| Approval control | Review budget, supplier and purchasing 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 | Limit exceeded; supplier changes; delivery terms mismatch |
| Downstream system | ERP / supplier management |
The ERP checks supplier, value and purchasing authority; acceptance is signed at a separate handover step.
Procurement; budget owner; supplier; acceptance officer review the document and representation authority before authorizing signing.
Correlate the signing request with purchase order, supply agreement and acceptance record 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.
Link order, agreement, acceptance and signing result by document for payment and audit support.
Limit exceeded; supplier changes; delivery terms mismatch.
The ERP / procurement system 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.
