Routing NDAs to suppliers
Reduce manual effort by providing your procurement specialist with a single place to perform all the necessary actions when creating and routing Non-Disclosure Agreements (NDAs) to suppliers and third parties.
Further, procurement specialists can easily route the NDAs to suppliers and third parties for signing via DocuSign integration, review the signed documents, and close the procurement case of type Send NDA for Signature, from a designated playbook in Source-to-Pay Workspace.
- Define your NDA content and update the list of participants for signature. See Define NDA content and update the list of signers.
- Set up DocuSign.
For more information, see Docusign eSignature Spoke.
- Navigate to .
- Select the list icon and select .
- Select New.
- In the Create a new case dialog box, select Send NDA for Signature.
- Select Create Case.Remarque :During a procurement request, when a valid NDA isn’t available for the selected supplier, a procurement case of type Send NDA for Signature is automatically created.
- Open the case in Source-to-Pay Workspace, prepare the NDA, and send it for signing to the suppliers and third parties from a playbook. See Send NDA to suppliers for signature.Remarque :If the Playbook tab isn’t visible in Source-to-Pay Workspace, verify that the Document Template Integration with DocuSign application is installed correctly.
- Sign the NDA.
- For external third-party suppliers, directly sign from the email notification or from Supplier Collaboration Portal. For more information, see Using Supplier Collaboration Portal.
- For internal supplier representatives, from Employee Center. For more information, see Sign a document using DocuSign from Employee Center.
- Review the signatures from the playbook in Source-to-Pay Workspace, notify the user, and close the case. See Send NDA to suppliers for signature.
Additional configurations
You can make changes to the Send NDA for signature playbook, if you must, from Playbooks.
For adding new participants, create a new column on the procurement case and update the logic to populate in Playbooks. For more information, refer to the implementation of the signer_1 column.
You can also update the subflows to incorporate any new logic. Flow details can be found in different steps in Playbooks.