From ICIHelp7.15
Jump to: navigation, search
Line 1: Line 1:
  
 
= Agreement Management =
 
= Agreement Management =
 +
 +
 
  
 
== <font face="Segoe UI">Overview of Agreement Management</font> ==
 
== <font face="Segoe UI">Overview of Agreement Management</font> ==
Line 6: Line 8:
 
<font face="Segoe UI">The Agreement Management Tile enables you to manage all aspects of creating and editing agreements from a single page. From here, you can:</font>
 
<font face="Segoe UI">The Agreement Management Tile enables you to manage all aspects of creating and editing agreements from a single page. From here, you can:</font>
  
*<font face="Segoe UI">search, view and manage all your agreements on the [[Agreements_Page]].</font>  
+
*<font face="Segoe UI">search, view and manage all your agreements on the <a href="Agreements%20Page">Agreements Page</a></font>  
*<font face="Segoe UI">create new agreements on the [[Create_Agreement_Page]].</font>  
+
*<font face="Segoe UI">create new agreements on the <a href="Create%20Agreement%20Page">Create Agreement Page</a></font>  
*<font face="Segoe UI">search, view and manage all your existing requests on the [[Requests_Page]].</font>  
+
*<font face="Segoe UI">search, view and manage all your existing requests on the <a href="Requests%20Page">Requests Page</a></font>  
*<font face="Segoe UI">create new requests on the [[Create_Request_Page]].</font>  
+
*<font face="Segoe UI">create new requests on the <a href="Create%20Request%20Page">Create Request Page</a></font>  
  
 
<font face="Segoe UI">If you are new to the Icertis Contract Management (ICM) application, the following section will help you understand the agreement workflow and give you an overview of agreements in the context of this application. In ICM, the terms Agreement and Contract are used interchangeably and mean the same thing. In this Help System, we will use the word "Agreement" when talking about Agreements. "Contract" will only be used in reference to Contract Types.</font>
 
<font face="Segoe UI">If you are new to the Icertis Contract Management (ICM) application, the following section will help you understand the agreement workflow and give you an overview of agreements in the context of this application. In ICM, the terms Agreement and Contract are used interchangeably and mean the same thing. In this Help System, we will use the word "Agreement" when talking about Agreements. "Contract" will only be used in reference to Contract Types.</font>
Line 25: Line 27:
 
*<font face="Segoe UI">'''Approvers and signatories''' are an integral part of creating an agreement and are rule based. The rules determine who must approve and sign the agreement throughout it's life cycle.</font>  
 
*<font face="Segoe UI">'''Approvers and signatories''' are an integral part of creating an agreement and are rule based. The rules determine who must approve and sign the agreement throughout it's life cycle.</font>  
  
<font face="Segoe UI">This figure shows the above&nbsp;building blocks of an Agreement in ICM:</font>
+
<font face="Segoe UI">This figure shows these building blocks of an Agreement in ICM:</font>
  
 
<font face="Segoe UI"><img src="/ICMHelp4.4/images/8/89/AgreementComponents.JPG" _fck_mw_filename="AgreementComponents.JPG" _fck_mw_origimgwidth="300" _fck_mw_origimgheight="203" alt="RTENOTITLE" title="RTENOTITLE" style="vertical-align:middle;" /></font>
 
<font face="Segoe UI"><img src="/ICMHelp4.4/images/8/89/AgreementComponents.JPG" _fck_mw_filename="AgreementComponents.JPG" _fck_mw_origimgwidth="300" _fck_mw_origimgheight="203" alt="RTENOTITLE" title="RTENOTITLE" style="vertical-align:middle;" /></font>
Line 36: Line 38:
 
*<font face="Segoe UI">make this step completely optional, so it can be skipped by someone who is an expert at contracting and it's process.</font>  
 
*<font face="Segoe UI">make this step completely optional, so it can be skipped by someone who is an expert at contracting and it's process.</font>  
  
<font face="Segoe UI">'''2. Create agreement''': this involves the primary owner (creator of the agreement) defining the contract type, selecting attributes and template, and verifying the details entered. See [[Create_Agreement_Page]] for complete details.</font>
+
<font face="Segoe UI">'''2. Create agreement''': this involves the primary owner (creator of the agreement) defining the contract type, selecting attributes and template, and verifying the details entered. See <a href="Create%20Agreement%20Page">Create Agreement Page</a> for complete details.</font>
  
 
<font face="Segoe UI">'''3. Review and approve agreement''': once the primary owner has created an internal draft of the agreement, it gets published and this published draft can now be sent for reviews and approvals to the team of people that are working on this agreement in various roles.</font>
 
<font face="Segoe UI">'''3. Review and approve agreement''': once the primary owner has created an internal draft of the agreement, it gets published and this published draft can now be sent for reviews and approvals to the team of people that are working on this agreement in various roles.</font>
Line 44: Line 46:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
|  
+
| '''Note''' - In case if the wrong document gets uploaded by any '''signatories''' then in the user who has the privilege can go ahead and upload the correct document even after the agreement gets executed. The document uploaded should be only in '''pdf format'''. This access will not be provided to following roles:  
'''Note''' -&nbsp;User with appropriate privilege can upload a corrected document&nbsp;even after the agreement gets executed, if a wrong document was initially uploaded by a&nbsp;signatory. The new document uploaded can be only be a PDF. This access will not be provided to following roles:
+
 
+
 
• Approver<br/> • Internal Signatory<br/> • External Signatory<br/> • Deviation Approver<br/> • External Reviewer<br/> • Reviewer
 
• Approver<br/> • Internal Signatory<br/> • External Signatory<br/> • Deviation Approver<br/> • External Reviewer<br/> • Reviewer
  
Line 57: Line 57:
 
<font face="Segoe UI">This figure shows all the possible states of an agreement with various roles involved in creating it.</font>
 
<font face="Segoe UI">This figure shows all the possible states of an agreement with various roles involved in creating it.</font>
  
[[File:Agreement Workflow Role-Status white.jpg|Agreement Workflow]]
+
<font face="Segoe UI"><img src="/ICMHelp4.4/images/7/70/Agreement_Workflow_Role-Status_white.jpg" _fck_mw_filename="Agreement Workflow Role-Status white.jpg" _fck_mw_origimgwidth="800" _fck_mw_origimgheight="597" alt="RTENOTITLE" title="RTENOTITLE" style="vertical-align:middle;" /></font>
 +
 
 +
&nbsp;
 +
 
 +
&nbsp;
  
 
&nbsp;
 
&nbsp;
Line 69: Line 73:
 
&nbsp;
 
&nbsp;
  
== &nbsp; ==
+
== <font face="Segoe UI">Request Page</font> ==
 +
 
 +
<font face="Segoe UI">These pages enable you to search, view and manage existing and create new requests:</font>
 +
 
 +
<font face="Segoe UI"><a href="Send%20a%20Request%20for%20Review">Send a Request for Review</a><br/> <a href="Review%20a%20Request">Review a Request</a><br/> <a href="Edit%20a%20Request">Edit a Request</a><br/> <a href="Send%20a%20Request%20for%20Approval">Send a Request for Approval</a><br/> <a href="Approve%20a%20Request">Approve a Request</a><br/> <a href="View%20Request%20Status">View Request Status</a><br/> <a href="Put%20Request%20On%20Hold">Put Request On Hold</a><br/> <a href="Cancel%20a%20Request">Cancel a Request</a><br/> <a href="Search%20an%20Existing%20Request">Search an Existing Request</a><br/> <a href="Copy%20an%20Existing%20Request">Copy an Existing Request</a><br/> <a href="Download%20and%20Print%20Request%20Information">Download and Print Request Information</a></font>
  
 
== <font face="Segoe UI">Contract Types</font> ==
 
== <font face="Segoe UI">Contract Types</font> ==

Revision as of 09:18, 3 March 2017

Agreement Management

 

Overview of Agreement Management

The Agreement Management Tile enables you to manage all aspects of creating and editing agreements from a single page. From here, you can:

  • search, view and manage all your agreements on the <a href="Agreements%20Page">Agreements Page</a>
  • create new agreements on the <a href="Create%20Agreement%20Page">Create Agreement Page</a>
  • search, view and manage all your existing requests on the <a href="Requests%20Page">Requests Page</a>
  • create new requests on the <a href="Create%20Request%20Page">Create Request Page</a>

If you are new to the Icertis Contract Management (ICM) application, the following section will help you understand the agreement workflow and give you an overview of agreements in the context of this application. In ICM, the terms Agreement and Contract are used interchangeably and mean the same thing. In this Help System, we will use the word "Agreement" when talking about Agreements. "Contract" will only be used in reference to Contract Types.

An Agreement in ICM is based on these main concepts:

  • Template is a predefined format that gets used for a given agreement. It consists of the text that is relevant to the type of agreement being created. Templates in ICM are used to organize clauses and give a certain structure to all the attributes.
  • Attribute can be defined as a variable or placeholder for the actual data for the agreement. This is data that changes for each agreement. For example, [Company Name] and [Legal Address] can be attributes that will be replaced by the actual name and address of the company the agreement is being signed with.
  • Clauses contain the terms and conditions of the agreement. For example, the payment terms will be 45 days from the date of invoice. Clauses can be rule or attribute based.
  • Rules help automate the workflow and define conditions that must be met for an agreement to get executed and stay in force. They enforce specific roles for certain users and comply with predefined business conditions. For example, if the payment is not received within 45 days of the date of the invoice, a 10% penalty on the outstanding amount will be levied.
  • Approvers and signatories are an integral part of creating an agreement and are rule based. The rules determine who must approve and sign the agreement throughout it's life cycle.

This figure shows these building blocks of an Agreement in ICM:

<img src="/ICMHelp4.4/images/8/89/AgreementComponents.JPG" _fck_mw_filename="AgreementComponents.JPG" _fck_mw_origimgwidth="300" _fck_mw_origimgheight="203" alt="RTENOTITLE" title="RTENOTITLE" style="vertical-align:middle;" />

While the actual workflow of an agreement within ICM can be quite complex and involved, it is summarized in these 5 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 all contracts are initiated and drafted only by 1 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: this involves the primary owner (creator of the agreement) defining the contract type, selecting attributes and template, and verifying the details entered. See <a href="Create%20Agreement%20Page">Create Agreement Page</a> for complete details.

3. Review and approve agreement: once the primary owner has created an internal draft of the agreement, it gets published and this published draft can now be sent for reviews and approvals to the team of people that are working on this agreement in various roles.

4. Execute agreement: there can be one or more people that need to approve the agreement before it is ready to be signed. Once all approvals are obtained, the approved agreement can be 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.

Note - In case if the wrong document gets uploaded by any signatories then in the user who has the privilege can go ahead and upload the correct document even after the agreement gets executed. The document uploaded should be only in pdf format. This access will not be provided to following roles:

• Approver
• Internal Signatory
• External Signatory
• Deviation Approver
• External Reviewer
• Reviewer

There will be no change in the “Execute” state of agreement.

5. Add amendment: if, after execution, there needs to be a change in the agreement, for example the payment terms or the scope of work (SOW) changes or terms and conditions (referred to as clauses in ICM) have to be changed because of the introduction of a new regulation, the primary owner can add an amendment. This process will be similar in nature, but a few things like the approvers may change.

This figure shows all the possible states of an agreement with various roles involved in creating it.

<img src="/ICMHelp4.4/images/7/70/Agreement_Workflow_Role-Status_white.jpg" _fck_mw_filename="Agreement Workflow Role-Status white.jpg" _fck_mw_origimgwidth="800" _fck_mw_origimgheight="597" alt="RTENOTITLE" title="RTENOTITLE" style="vertical-align:middle;" />

 

 

 

Agreement Page

These pages enable you to search, view and manage existing and create new agreements:

<a href="Agreements%20Page">Agreements Page</a>
<a href="Agreement%20Details%20Page">Agreement Details Page</a>
<a href="Create%20Agreement%20Page">Create Agreement Page</a>
<a href="Copy%20an%20Existing%20Agreement">Copy an Existing Agreement</a>
<a href="Create%20an%20Agreement%20from%20a%20Contract%20Request">Create an Agreement from a Contract Request</a>
<a href="Search%20Agreements">Search Agreements</a>
<a href="Create%20Smart%20Link%20for%20Agreement">Create Smart Link for Agreement</a>
<a href="Set%20Auto-Expiry%20of%20a%20Contract%2F%20Agreement">Set Auto-Expiry of a Contract/ Agreement</a>
<a href="Edit%20a%20Contract%2FAgreement">Edit a Contract/Agreement</a>
<a href="Put%20Contract%2FAgreement%20On%20Hold">Put Contract/Agreement On Hold</a>
<a href="Cancel%20a%20Contract%2FAgreement">Cancel a Contract/Agreement</a>
<a href="View%20a%20Contract%2FAgreement">View a Contract/Agreement</a>
<a href="Delete%20a%20Contract%2FAgreement">Delete a Contract/Agreement</a>
<a href="Add%20and%20Remove%20Approvers">Add and Remove Approvers</a>
<a href="Enable%20and%20Disable%20Approvers">Enable and Disable Approvers</a>
<a href="Send%20an%20Agreement%20to%20External%2FThird%20Party%20Signature">Send an Agreement to External/Third Party Signature</a>
<a href="Approve%20a%20Contract%2FAgreement">Approve a Contract/Agreement</a>
<a href="Reject%20a%20Contract%2FAgreement">Reject a Contract/Agreement</a>
<a href="Post-execution%20review%20of%20an%20agreement">Post-execution review of an agreement</a>
<a href="Terminate%20an%20agreement">Terminate an agreement</a>
<a href="Add%20amendment%20to%20an%20agreement">Add amendment to an agreement</a>
<a href="Renew%20an%20agreement">Renew an agreement</a>

 

Request Page

These pages enable you to search, view and manage existing and create new requests:

<a href="Send%20a%20Request%20for%20Review">Send a Request for Review</a>
<a href="Review%20a%20Request">Review a Request</a>
<a href="Edit%20a%20Request">Edit a Request</a>
<a href="Send%20a%20Request%20for%20Approval">Send a Request for Approval</a>
<a href="Approve%20a%20Request">Approve a Request</a>
<a href="View%20Request%20Status">View Request Status</a>
<a href="Put%20Request%20On%20Hold">Put Request On Hold</a>
<a href="Cancel%20a%20Request">Cancel a Request</a>
<a href="Search%20an%20Existing%20Request">Search an Existing Request</a>
<a href="Copy%20an%20Existing%20Request">Copy an Existing Request</a>
<a href="Download%20and%20Print%20Request%20Information">Download and Print Request Information</a>

Contract Types

These tasks are crucial for...

 

Associated Documents

==Miscellaneous Topics==