Finalizing an Agreement
After you complete the negotiation process with the customer, you can send the finalized agreement document for signatures to internal or external signatories. You can send the agreement document for a manual or electronic signature to a third-party application such as Echosign or DocuSign.
You can send documents in all file formats that the Salesforce platform supports including DOC, DOCX, RTF, and PDF using X-Author for Contracts. You can also upload manually signed documents for the agreement. For more information, see.Uploading Signed Documents.
You can send the document in PDF format using Conga for Google Docs. For more information, see Updating and Checking In Contract.
Once you receive the manually signed documents from the customer, you can upload the signed documents to finalize the agreement. Documents in the review are not available to send for signatures or eSignatures.
Before sending the agreement document for signature, you must ensure that a final version of the agreement document is present in the Notes & Attachments related list.
Prerequisites
- The agreement document is reviewed.
- The Status Category for the Agreement is In Authoring.
Limitation
- You cannot send a document with protection for signatures if your organization has set up High-Assurance Session Security at a user profile level. As a result of the security, the sessions cannot be generated in asynchronous calls.
- For information on supported file sizes, see Supported File Sizes in Lightning and Supported File Sizes in Classic.
To send an agreement for manual signatures
After the agreement document is signed, all the clauses are marked as Final in the Agreement Clauses section. In the version aware agreement, the Document Type of the signed document is updated as the Executed Document. An executed document is a finalized version of an agreement that is ready for activation.
To Send an Agreement for Electronic Signature
- You must have sent a generated Agreement document to the customer for review.
- You must ensure that the Status Category for the Agreement record is In Authoring.
From the Agreement detail page, click the eSignature button. This action takes you to the EchoSign, DocuSign, Conga Sign, or OneSpan Sign wizard. For more information on EchoSign, see Adobe Sign Services documentation. For more information on DocuSign, see DocuSign Services documentation. For more information on Conga Sign, see Conga Sign documentation. For more information on OneSpan Sign, see OneSpan Sign documentation. For more information on Conga Sign 2.0, see Sending Transactions with Conga CLM..
The following conditions apply when you send documents in the Version Aware agreement for eSignatures in DocuSign or Conga Sign:
- The Status Category changes to In Signatures and the Status changes to Other Party Signatures for your agreement record.
- The signed agreement documents are stored in the Document Version-related list.
- All the agreement clauses are marked as Final.
- The Document Type is updated to Executed Document.
After an agreement document is signed, all the smart clauses are marked as Final in the Agreement Clauses section.
The following conditions apply when you send documents in the Version Aware agreement for eSignatures in EchoSign:
- You can send generated, regenerated, supporting, imported offline, created offline, or manually uploaded documents.
- You can select any document from Files or Notes and Attachments. You can also select the latest document version from the Document Version-related list.
- The Document Type of the signed document is updated as the Executed Document.
- The intermediate signed documents from EchoSign are available in Contract Management as a major document version with the name Intermediate Signed Document in the Document Version related list. In the version aware agreement, the Document Type of the document is updated to Intermediate Document.