Set Up Electronic Signature

After you set up the electronic signature functionality, contracts users can submit contracts that can be signed electronically.

Before you start

Contracts Prerequisites

• When you create contract types, you specify whether an electronic signature is required for contract acceptance and activation.
• An electronic signature contract type is set up with:
  • The Requires signature checkbox set to Yes.
  • The Electronic signature checkbox set to Yes.
  • The Solution Provider is DocuSign or OneSpan.
  • Entry of a meaningful value for the email subject and email message.
• An electronic signature contract terms layout template must be set up with the signature table and with the standard tags in the signature table. This layout template is selected as the default contract terms layout template for the contract type to be used for electronic signatures.
• The contract author who plans to send the contract for signature must have a valid email address and must be set up as a user in the account that's specified in the electronic signature setup.

See Define Contract Types for more information.

Electronic Signature Prerequisites

• Your organization must first register and obtain a license directly from a supported third-party electronic signature service provider. The supported providers are DocuSign and OneSpan.
• After the license is obtained, you must set up an account for your organization on the service provider's website. You must create an administrator account on the site. Note that this is a one-time activity.
• Note down the account key, provider URL, user name, and password from the solution provider's site.

Here's what to do

1. In the Setup and Maintenance work area, search for and select the Manage Contract Electronic Signature task.
2. Select DocuSign or OneSpan as the solution provider.
3. If you're using DocuSign:
   1. Enter the User ID (a 32-digit GUID from DocuSign) that's associated with the user profile that has administrator privileges.
   2. Enter the Account ID, which is the API account ID mentioned on the DocuSign website.
   3. Enter the Endpoint URL, which is the Account Base URL mentioned on the DocuSign website.
   4. Provide the OAuth URL:
      • Development account: https://account-d.docusign.com
      • Production account: https://account.docusign.com
      Note: Developer accounts let you test and develop with DocuSign functionality for free. Developer accounts operate in the DocuSign development (demo) environment, which is similar to production except:

      • Documents sent in this environment aren't legally binding and have test stamps on them.
      • Developer accounts don't expire.
      • Developer accounts have enterprise-level features enabled for development and testing purposes.
   5. Click Validate to provide one-time user consent to use DocuSign integration.
   6. Click ALLOW ACCESS to grant consent.
      You'll receive a confirmation message on the linking of Oracle Enterprise Contracts and DocuSign.
   7. Click Validate, and after the validation status changes to Complete, Save and Close.
4. If you're using OneSpan:
   1. Enter the user ID of the OneSpan account user, the API key, and the appropriate OneSpan endpoint URL.
   2. Save the settings.

What to do next

After you set up the electronic signature process, you must set up your contract types to enable them for electronic signatures. The enabling at the contract type level works with the Enable electronic signature checkbox on individual contracts. So, if enabled for a particular type, by default, any contract you create of that type will also have the Enabled electronic signature box checked. Still, you can decide to deselect it and turn off the electronic signature specifically for that contract. You can edit this checkbox if the contract hasn't yet been signed. However, once the contract reaches Pending acceptance status, you'll need to continue with the electronic signing process. See the topic, Define Contract Types, for more information.

Keep in mind these user requirements to be able to send contracts for signature:

• Users must have a valid electronic signature account.
• Users' electronic signature user names must match their email addresses in Oracle Person Management.
• In the solution provider's account, the users must be defined as members with permission to send contracts for signing.

For more information on Contracts user tasks, see How Capturing Contract Acceptance with Electronic Signatures Works.