DocuSign Integration - Contract Status Updates

Background

Finance companies generally have multiple credit applications in process at the same time which often means having to prepare documents for signing, getting the documents to the signers, and tracking when the documents come back signed on many credit applications concurrently.

This situation can be a challenge for the documentation team who need to remember which credit applications still need to have docs sent out and which credit applications they are waiting on the signed documents to come back.

ASPIRE Contract Statuses are commonly used to track these phases of the credit application lifecycle.

DocuSign supports the concept of envelope status, used to track where documents are in the signing process.

Because of the situations noted above, the ASPIRE DocuSign integration supports mapping of DocuSign envelope State values to ASPIRE Contract Status values.

ASPIRE Configuration

In ASPIRE - Administration - eSignature - DocuSign, you can configure the mapping of four DocuSign Envelope Statuses to the configured, active ASPIRE Contract Statuses.

If an Envelope Status is not mapped, an occurrence of that status on a relevant DocuSign envelope will not cause a Contract Status change in ASPIRE.

Click "Update Mappings" to confirm/save the changes, which will take effect for any envelope state updates from that point forward for all envelopes created using the ASPIRE DocuSign integration, regardless of whether the envelope was created prior to the configuration mapping change.

Status Updates

When an envelope is created in DocuSign using the ASPIRE DocuSign integration through the "Submit" or "Submit for Revision" processes, the LTi DocuSign service communicates a callback address to DocuSign, so that DocuSign can inform the LTi DocuSign service of relevant envelope status changes.

When the status of an envelope created using the ASPIRE DocuSign integration changes in DocuSign, DocuSign informs the LTi DocuSign service using the noted callback address.
The LTi DocuSign service then translates the envelope status to the relevant ASPIRE contract status and holds it as it waits for the relevant ASPIRE instance to ask for it.

On a recurring scheduled basis, each ASPIRE instance licensed for the DocuSign integration calls out to the LTi DocuSign service to get new status changes and makes any necessary Contract Status changes.

• Related Articles

• DocuSign Integration User Guide

  Please see Attachments to download the guide. This article is the holding place for the most recent version of the ASPIRE v5 - DocuSign User Guide. Throughout the Knowledge Base there are also individual articles on relevant topics related to this ...

• Updating equipment status when calculating a contract payoff

   Please see the attached document to learn how to update equipment status when processing a payoff. When you are calculating a contract payoff, it is easy to update the status of the associated equipment at the same time. The attached PDF outlines ...

• DocuSign - No signers in the Sign Documents screen

  To create an envelope using the ASPIRE DocuSign integration, you must have at least one signer listed in the signer section (outlined in red in the screenshot). Sometimes, no signers will appear in the Sign Documents screen. To uncover the problem ...

• Submitting Documents to DocuSign/Creating a DocuSign envelope

  Use the attached steps for more detail on how to create a DocuSign envelope using the integration in ASPIRE v5. The ASPIRE DocuSign integration uses the DocuSign Remote Signing Ceremony, where DocuSign will send an email to each signer inviting them ...

• 401 error when using DocuSign integration

  401 errors indicate an unauthorized request. Most commonly, this is due to using an invalid service key. Each service key is unique to a subscriber and service address. Please check with the assigned LTi account manager to confirm authorization for ...