The workflow reads the vendor and its contact from NetSuite and fills the supplier agreement, which the supplier completes with its legal name and tax ID and signs, and the person who started the workflow countersigns. It then writes the legal name and tax ID back to the vendor and files the signed agreement on the vendor record.
| Data label on the supplier agreement | NetSuite field | Step |
|---|---|---|
Supplier_Name | Vendor / Company Name | 1 |
Supplier_Number | Vendor / Record ID | 1 |
Supplier_Street | Vendor / Default Billing Address 1 and 2 | 1 |
Supplier_City | Vendor / Default Billing City, State and Zip | 1 |
Contact_Name | Contact / Contact Name | 2 |
Contact_Email | Contact / Email | 2 |
Supplier_Phone | Vendor / Phone | 1 |
Payment_Terms | Vendor / Terms Name | 1 |
Written back: Legal Name = Legal_Name, as the supplier entered it; Tax ID = Tax_ID, as the supplier entered it
Filed to: Vendor drive / {Vendor Record ID} / Signed Supplier Agreement - {Company Name} - {Instance ID}.pdf
The highlighted fields are the supplier agreement's data labels, shown here with sample values. The field map lists where each one comes from in NetSuite or the start inputs. Each field sits on a hidden anchor tag, so you can use your own supplier agreement: keep the eight data labels and the workflow keeps working.
Install NetSuite for Docusign IAM from the Docusign App Center and connect it to your NetSuite account. An account admin does this once.
In Docusign, upload the supplier agreement template (.json) under Templates. It carries the document and its fields.
In Agreements, Workflows, Create Workflow, add the steps listed above in order. Use the definition file to check the settings of each step, pick your NetSuite connection, and map the fields as the field map shows.
Run it once on a test record addressed to your own inbox, and check the write-back and the file.
No. It is the definition exported from the tested workflow, kept as a reference. Build the workflow step by step in Docusign Workflow Builder and use the file to check the settings of each step. The account, connection and template ids in it are placeholders.
Procurement, on the NetSuite vendor with Baton Launcher, or anyone with Run Workflow and the vendor's internal ID. Another system can start it through the API with Vendor_ID.
Legal Name and Tax ID, as the supplier entered them on the agreement. The entity type and year established stay on the signed agreement unless you map them to fields of your own.
No. Honeycomb Mfg. is a fictional company and every sample value is invented. Put your own company, terms and template in place before you use the workflow.
We adapt library workflows to your stages, approvals and documents, and build private apps when a system has no app yet.
Fills an order form from the quote, its customer and contact, collects both signatures and files the signed copy on the quote.
Fills a credit application from the customer record, collects the customer and credit manager signatures and updates the customer.
Fills an onboarding packet from the employee record, collects the new hire's details and signature, and writes their phones back.
Docusign is a trademark of Docusign, Inc. NetSuite for Docusign IAM is published by Fluidlabs. To ask us to remove a mark, email hello@fluidlabs.com.
