Preserve the original agreement while recording amendments, extensions, value changes, and other approved contract changes.
Choose the correct change method
Use a file version when users revise the same draft. Record a formal amendment separately and link it to the original contract. A field update records the current structured value but may not explain the legal change on its own.
| Capability | Classification | How it is provided |
| Draft revision | File version | Upload a new version of the same draft during review. |
| Executed amendment | Separate document and record | Retain the signed amendment and relate it to the original contract. |
| Current value | Field update | Update the current contract value after approval while retaining amendment evidence. |
| Audit evidence | History and approval records | Use field history, approval history, and system audit information as configured. |
Record an amendment
1. Open the original contract and confirm that it is the correct agreement.
2. Create the configured amendment record or change request.
3. Enter the amendment number, effective date, description, and financial effect.
4. Attach the draft and route it through required approvals.
5. After execution, upload the signed amendment and record its approval and signature status.
6. Update the contract's current dates, value, status, or terms according to the approved amendment.
7. Confirm that reports and GoldFinch financial relationships reflect the approved change.
Controls
- Do not delete or overwrite the executed original agreement.
- Restrict direct changes to controlled fields after activation when appropriate.
- Require a reason and approval for material changes.
- Test how amendments affect open orders, subscriptions, revenue schedules, budgets, and commitments.
Comments
0 comments
Please sign in to leave a comment.