Approve loan conditions and the repayment schedule in the LOS before presenting the agreement; the borrower reviews the approved version.
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 | Borrower and credit officer |
| Trigger | Approve credit and finalize the loan offer |
| Source system | LOS / Core Banking |
| Documents | Loan agreement, repayment schedule and loan disclosures |
| Approval control | Approve credit and finalize the loan offer |
| 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 | Offer changes after approval; borrower declines; co-borrower signature pending |
| Downstream system | DMS / Core Banking |
Approve loan conditions and the repayment schedule in the LOS before presenting the agreement; the borrower reviews the approved version.
Borrower; credit officer; authorized bank signer review the document and representation authority before authorizing signing.
Correlate the signing request with loan offer and repayment schedule 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.
The DMS retains the signed agreement and loan-offer correlation; disbursement remains a separate bank-system decision.
Offer changes after approval; borrower declines; co-borrower signature pending.
The LOS / Core Banking 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.
