Using DocuSign KBA authentication for eSignature

Starting August 15, 2026, KBA (Knowledge-Based Authentication) works only for eSignature requests that originate from within the tax product (Lacerte, ProSeries, and ProConnect Tax).

After this date, any KBA-authenticated requests submitted directly from the DocuSign website, and those from any other DocuSign integration connected to your eSignature account, will fail. The eSignature workflow within your tax product is unaffected.

What's changing

• KBA works only for signature requests originating in the Lacerte, ProSeries, and ProConnect Tax products. This includes the Continue with DocuSign option when custom documents are attached to the signature request from within the tax product.
• Requests sent directly through the DocuSign website or portal (or another DocuSign integration on the same account that is connected to your eSignature account) cannot use KBA authentication.
• In the DocuSign portal after August 15, 2026, DocuSign KBA no longer appears as an option.
• Intuit KBA still appears as a selectable option in the portal, but new requests using it will fail. This is the key change — the option is still visible, but recipient authentication cannot be completed.
  • When the recipient tries to sign the envelope, they'll see the message:

Something on our end isn't working

What is not changing

• The normal Lacerte, ProSeries, and ProConnect Tax workflows, including Continue with DocuSign for adding your own custom documents. KBA continues to work exactly as it does today.
• Signature requests sent with the Access Code or No Authentication methods from the DocuSign portal are unaffected.
• Requests already sent before August 15, 2026 complete normally, even if signed after that date.

Looking ahead

We're moving to Intuit Sign starting Tax Year 2026. Going forward, we recommend sending all signature requests from within your tax product.