You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page:
Return to 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:
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 discussing Agreements, whereas Contracts will be discussed with 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:
2. Create Agreement: In this step, the primary owner or the creator of the agreement select 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. Review 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 of the Agreement) .
4. Approve Agreement: Once the Agreement is reviewed, it can be sent for 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.
Notes:
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 an 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 Statement 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: ICM offers full platform support for multi-party Agreements. You can now use a single system for managing all your Agreements and capture multiple other parties and divisions on an Agreement seamlessly. It allows you to search only metadata instead of searching multiple attributes, thus making it user-friendly. 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 signing sequence set in ICM. It also supports parallel signatures independent of the status of either party.
Such Agreements include Non-Disclosure Agreements, Sell Agreements or business-specific Agreements. For example, A healthcare business group needs Contract Types for managing their contracts, but the Mergers and Acquisitions department needs their own Contract Types.
Key capabilities of Multi-Party:
For organizations looking to optimize their contract lifecycle management processes and digital transformation, this release includes capabilities to manage the bulk upload of larger volumes of legacy contracts, and Artificial Intelligence (AI) driven enhancements to improve discovery, identification, and digitization of third-party, legacy and federal contracts.
Using ICM, you have the:
You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in one of the groups: Users, User.
You can view and copy the source of this page:
Return to Agreement Management.