Store key extractable information to improve how you report on contracts
To ensure information about the contract is extracted for reporting and searching, key terms & metadata should be stored against your contract.
- Counterparties: Select which contacts you want to be associated with this Contract. If the contact does not exist, it can be added to your Contact list.
- Contracting Entity: Select which contacts you want to be associated with this Contract. If the contact does not exist, it can be added to your Contact list.
- Contract ID: Each contract you create is generated with a globally unique ID.
- Internal Reference: The internal reference field is used to store any generic ID that can be used to identity contracts. This field is typically used for integrations or to reference external systems where relevant information is held.
- Currency: There are several currencies that can be stored against your contract including; NZD, AUD, USD, GBP, EUR
Other key fields include Title, Description, Counterparties, Contracting Entity, and Region.
Contract Owner
Each contract can be assigned a contract owner. The contract owner will receive notifications for key events, such as a variation. To be assigned as a contract owner the user must be assigned the contract manager role (see User roles and permission).
Custom Fields
Custom fields will appear at the bottom section and enable input of any additional information the business wishes to add or capture in the repository. Your custom fields are managed in your settings.
Contract Associations
Contracts can be related to one another via either a Parent, Child or Sibling relationship. For example, if you had an MSA and multiple SOWs, they could be linked via a Parent → Child association.