High-Level Specification

Functional Overview

This document details the DocuSign integration requirement between Syensqo DocuSign and Icertis Contract Intelligence (ICI). This document provides all necessary information to enable and guide the configurator to effectively integrate ICI with DocuSign.

Scope and Objectives

Scope Includes:

1. Standard OOTB Integration of DocuSign with Icertis for Agreement Signatures by Internal & External signatories (Contract Execution)

Process Flow Diagram

Assumptions

NA

Dependencies

1. Signature workflow rules must be configured in Icertis for Electronic Signature or else DocuSign integration will not work.
2. While configuring the integration at DocuSign end, the user must be an Account Administrator. 
3. While configuring the integration at Icertis end, the user must be assigned ESign Admin role.

Security, Integrity and Controls

As this is a standard integration through an adaptor, all security requirements are followed as per standard.

Configuration Requirements

Following configuration needs to be completed in both Icertis and DocuSign platform:

1. DocuSign: In DocuSign, the configuration is a two step process.

   1. Configure Account 
      1. Log in to the DocuSign account as an Account Administrator.
      2. Go to the Setting tab.
      3. In the left navigation panel, click INTEGRATIONS > Connect.
      4. Click Add Configuration and select Custom from the dropdown list.
      5. In the Add Custom Configuration section, update the following sections:
         • Go to the Listener Settings section.
         • Select Active Connection in the Status dropdown.
         • Add a Name for the connect.
         • Add a URL to Publish as https://syensqo-dev/ESignCallBack/Initiate. (For UAT it will be https://syensqo-uat/ESignCallBack/Initiate, for Prod it will be https://syensqo/ESignCallBack/Initiate).
         • Go to the Event Settings section.
         • Select REST v2.1 in the Date Format dropdown.
         • Select Send Individual Messages (SIM) in the Event Message Delivery Mode dropdown.
         • Go to the Trigger Events section.
         • From the Envelope Events list, select Envelope Sent, Envelope Declined, and Envelope Voided.
         • From the Recipient Events list, select Recipient Signed/Completed, Recipient Declined, Recipient, and Reassign.
         • Go to the Include Data section.
         • Select Custom Fields, Extensions, Recipients, and Tabs from the list.
      6. Go to the Integration and Security Settings section. Select Enable Manual TLS.
      7. Click Save Configuration. You can see the configuration you created.
   2. Add App in Account created above
      1. Log in to DocuSign account as an Account Administrator.
      2. Go to Setting > Connect.
      3. Select the configuration which was created as above.
      4. Go to Setting > Apps and Key
      5. Capture the following information.
         • The User ID.
         • The API Account ID.
         • The Account Base URI.
      6. Click Add App and Integration key.
      7. Add a Name for the app and click Add.
      8. The app is automatically assigned an integration key (GUID) value that cannot be changed. Note the Integration key value.
      9. Click Generate RSA to create a new, automatically generated GUID value that represents the ID for the private and public key pair.
      10. Note down the Private key. Click Close.
      11. Click Save.

2. Icertis Side Configuration - Post configuring the above steps, the following configuration needs to be performed in Icertis.

   1. In Icertis, navigate to Configurations > System Configurations > ESign Configurations.

   2. Click Create>DocuSign Account.
   3. Configure the following fields:

Special Requirements

Not Applicable

Design Rationale

Streamline the contract execution process by embedding DocuSign’s eSignature capabilities within the Icertis Contract Intelligence (ICI) platform. This enables faster agreement turnaround, reduces manual effort, and ensures compliance with electronic signature standards.

Processing within Source (Icertis)

• Trigger Point: When clicked on Send for Signature button, Icertis initiates the e-signature process.
• Envelope Creation: Icertis prepares the document and metadata (signatories, roles, signing order) and sends it to DocuSign via standard adaptor.
• Configuration: Admins configure DocuSign account details (Client ID, Secret, RSA Key, API Key) in Icertis UI.
• Callback Setup: A callback URL (https://syensqo-dev/ESignCallBack/Initiate) is configured to receive status updates from DocuSign.

Processing within Middleware

Not Applicable

Processing within Target (DocuSign)

• Envelope Handling: DocuSign receives the envelope, routes it to signatories, and manages the signing workflow.
• Status Updates: DocuSign sends real-time updates to Icertis via the callback URL.
• Signed Document Return: Once signed, the document is returned to Icertis and attached to the agreement record. Agreement status is changed to Executed.

Interface Dependency

• Signature provider selection is rule-based and depends on attributes entered by the user in the agreement.

Interface Constraints

• File Size Limit: DocuSign supports documents up to 4069MB per envelope.
• Signing Order: Sequential or parallel signing must be defined in Icertis.

Delivery Requirements

• Integration between Icertis and DocuSign is through standard adaptor. 

Delta or Full Load Requirements

Not Applicable

Interface Alert & Monitoring

• Audit Trail
  • Available within Icertis for each signature transaction.
  • Available within DocuSign.
  • Certification of Completion is also captured as logs within the agreement document as proof of consent for audit & verification. This is an optional.

Interface Reporting

Not Applicable

Language Requirements

Not Applicable

User Interface Requirements

• Embedded Experience: Users initiate and track signatures within Icertis UI.
• Status Visibility: Real-time status updates shown in agreement summary.
• Admin Configuration UI: Self-service configuration for DocuSign setup.

Volumetrics

• Initial Load Volumes: No bulk initial load; integration is triggered per agreement.
• Expected Frequency: Real-time per agreement; multiple agreements may be processed concurrently. 

Performance Consideration

Not Applicable

Error Handling

• Send for Signature: If DocuSign is down when clicked on Send for Signature, user has an option to retry from the UI.
• Status/Document Sync: If DocuSign fails to sync the status/document, then the retry mechanism in place will try to sync the status/documents back to Icertis. If retry fails, then raise a support ticket to DocuSign to resolve the issue.

Testing

How to Test

• Positive Test Cases:
  • Agreement sent successfully to DocuSign.
  • All signatories complete signing.
  • Signed document returned and attached in Icertis.
• Negative Test Cases:
  • Invalid DocuSign credentials.
  • Callback URL unreachable.
  • Signatory declines to sign.

Test Conditions and Expected Results

Test Considerations/Dependencies

Not Applicable

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log