From ICIHelp7.15
A
Name | Description |
---|---|
Agreement | Type of contract that your organization signs with a third party for a legal or procedural purpose. |
Approver | The user who reviews and approves requests and/or agreements. |
Attributes | Property of an entity. For example, party names, addresses, contract value, dates, and so on. |
Associated Documents | Peripheral documents which can be uploaded as attachments to the agreement. |
Amendment | Changes/updates made to an agreement after it is executed. For example, as market or requirements from one or both the parties change, you amend certain content in the contract. All the stakeholders involved must agree to the changes before it goes into effect. In ICM, amendment follows the similar workflow as that of agreement. |
Contract Request | When you want to propose a new contract, you raise a contract request that contains the necessary information of the contract. |
Contract Type | It is a type of contract. It decides which attributes and associations a contract should contain. For example, MSA contract type will define which attributes and associations MSA contract should contain. |
Clause | Part of a legal document covering a particular subject of the whole document; terms, conditions, and legal bindings. |
Commitment | These are obligations towards an agreement. You fulfil the commitment towards the agreement throughout the contract lifecycle. For example, reminding supplier about the contract expiry and renewal. |
Collaborate | Share your agreement with external users. |
Contract | See agreement. |
Dashboard | Single page displaying the status of important events. |
Delegate | Delegate your approval task to another user. |
Deviation | That which differs from original. In ICM, an agreement goes through reviews and approvals from various stakeholders. They may suggest changes in the content of an agreement such as clauses, attributes, and other content. This change in the text from original is a deviation. |
External Signatory | A third party user who either electronically or manually signs an Agreement/contract. |
ICM | Icertis Contract Management. It is an integrated platform to create, execute, and manage agreements with enhanced efficiency and control. |
Internal Signatory | An ICM user who either electronically or manually signs an agreement/contract. |
Key Performance Indicators (KPI) | The elements based on which performance of a particular activity is measured. |
Lock | After you lock an agreement, other users in the team can not take any action on the agreement. |
Masterdata | One of the contract types you can create using ICM. It has peer-to-peer association with the contract type 'agreement'. |
Metadata | See Attributes. |
Notifications | Notifications that you receive for events or the for tasks that require your action. |
Own Paper | Company owned agreement template that has company specific clause, terms, and language. |
Primary Owner | User who has initiated or created the agreement. |
Publish | After the Contract Type or agreement is approved, you publish it to make it available for use in the system. |
QR Code | It is a machine-readable code that contains the information related to the agreement. It appears on the agreement PDF after it is approved. |
Request | See Contract Request. |
Secondary Owner | Co-owner of the agreement record who has the same set of action privileges as the primary owner but who cannot remove the primary owner from the team. |
Stand Alone Agreement | In ICM, an agreement that is initiated without a contract request. |
Template | Basic layout for an agreement in which you can pre-define the fields you want to include in the agreement that you are creating. |
Third Party | It refers to supplier or an external party. |
Third Party Paper | Agreement document not owned by the company and taken from other party such as supplier. |
Turnaround Time | The duration from the date of creation of an agreement till the date of its execution. |