How is the per envelope charge assessed for the DocuSign integration?
This article addresses LTi charges for subscribing to and using the ASPIRE DocuSign integration.
The client must have an active DocuSign subscription, subject to charges from and billed by DocuSign, to use this integration.
The client must have an active DocuSign subscription, subject to charges from and billed by DocuSign, to use this integration.
The ASPIRE DocuSign integration is billed to subscribers in two components:
- Base Module Charge - a recurring charge billed quarterly in advance for periods where the client is licensed for the integration
- Per Envelope Charge - a usage-based charge billed quarterly in arrears based on the number of envelopes created by the subscriber in the most recent prior quarter
The per envelope charge is determined by counting the number of DocuSign envelopes created using the ASPIRE DocuSign integration.
In other words, each time an ASPIRE user successfully submits ("Submit" or "Submit for Revision") from the Sign Documents screen in ASPIRE, a billable event is recorded for later use in billing.
Successful submission is generally reflected to the ASPIRE user in the form of a dialog indicating "success" and the resulting DocuSign Envelope ID.
Successful submission is generally reflected to the ASPIRE user in the form of a dialog indicating "success" and the resulting DocuSign Envelope ID.
Billing is not impacted by any activity that happens with DocuSign after that point, including failure of required signers to sign the documents, envelope expiration, or modification of the envelope from the DocuSign portal.
If a given envelope requires modification from ASPIRE, it is likely that a new envelope will need to be created from ASPIRE and a billable event will be recorded upon successful creation of that envelope from ASPIRE.
If a given envelope requires modification from ASPIRE, it is likely that a new envelope will need to be created from ASPIRE and a billable event will be recorded upon successful creation of that envelope from ASPIRE.
For example, if an envelope for Contract 1000 is created using the integration, and it is later determined that the terms in the agreement are inaccurate, the documents may need to be regenerated or modified in ASPIRE and sent again to DocuSign. In that case, LTi does not differentiate that an envelope had already been created from ASPIRE for the given contract, rather we always record a billable event upon successful envelope creation using the integration.