Agreement Management
The Agreement Management Tile enables you to manage all aspects of creating and editing agreements from a single page. From this page, you can do the following tasks:
- View and manage all your agreements on the Agreements Page.
- Create new agreements on the Create Agreement Page.
- Search, view, and manage all your existing requests on the Requests Page.
- Create new requests on the Create Request Page.
If you are new to the Icertis Contract Management (ICM) application, see the ICM Overview to get a better understanding of agreements and its workflow in the context of this application. In ICM, the terms Agreement and Contract are used interchangeably and mean the same thing. In this Help, we will use the word Agreement when talking about Agreements. Contract will be used only in reference to Contract Types.
While the actual workflow of an agreement in ICM can be quite complex and involved, it is summarized in these five steps:
1. Create contract request: When someone in your organization, such as a department manager wants to engage a vendor for certain services over a length of time, the individual can raise that request with the procurement department that can then work on that agreement. Depending on the workflow adopted, your organization may:
- enforce this step so that all contracts are initiated and drafted only by one department, or
- make this step completely optional, so it can be skipped by someone who is an expert at contracting and it's process.
2. Create agreement: In this step, the primary owner or the creator of the agreement selects the contract type, selects attributes and template, and verifies the details that you entered in the agreement. See Create Agreement Page for complete details.
3-4. Review and approve agreement: After the primary owner has created an internal draft of the agreement, it is published. The published draft can be sent for reviews (optional, if decided by the primary owner) and approvals to the team of people that are working on this agreement in various roles.
5. Execute agreement: Several people can review and approve the agreement before it is ready to be signed. After all approvals are obtained, the agreement is sent to be signed by both the parties. With both parties signing (known as internal and external signatories in ICM), the agreement is said to be executed and is now in force.
If an incorrect document was initially uploaded by a signatory, a user with the appropriate privilege can upload the correct document even after the agreement is executed. The uploaded document must be a PDF.' The Executed state of the agreement remains unchanged. Only the following roles have this privilege:
* Primary Owner
* Secondary Owner
* Contributor
If changes are required in the agreement that is in Executed state, the primary owner of the agreement can add an amendment. Changes may be required due to any of the following business reasons:
* The payment terms of the agreement have changed.
* The scope of work (SOW) in the agreement has changed.
* The terms and conditions of the agreement have changed due to the introduction of a new regulation.
6. Support Multi-party agreements: You can use a single system for managing all your contracts. Multiple Other Parties and multiple divisions on an Agreement can be captured. There is no limit on the number of parties that can be added. All parties can sign the Agreements either manually or electronically, based on the defined sequence of signing.
Such Agreements include Non-Disclosure Agreements, Sell Agreements (multiple types and sub types) or business specific Agreements (multiple types and sub types). For example: A healthcare business group needs contract types for managing their contracts, Mergers & Acquisitions department needs their own contract types.
Key capabilities of Multi-party:
- Captures multiple values of attributes and/or Masterdata
- Tags these multiple instances in the template
- Supports the signature workflow with these multiple instances of Customer data
- Supports multiple rules (say for approval workflow) based on the individual values selected (e.g. in an Agreement, if 3 Divisions are selected, the approval process should support approvals from all 3 divisions).
- Supports visibility in such one-to-many environment; e.g. in the multi-division scenario, the Agreement visibility too should be enabled for multiple divisions.
