E-signature native to the record, with audit trail and approvals in one place
Send, approve, and countersign contracts, quotes, and orders natively on the record. Compliant, auditable, and built for the full revenue motion.
E-signature native to the record, not bolted on
Sending a contract through a third-party e-sign tool means leaving the CRM, uploading a PDF, chasing the signer, and hoping the countersigned copy lands back in the right place. Sanka E-Signature replaces that round trip with a signature layer that lives on the record — estimate, contract, order, or purchase order — with audit trail, fields, and approval state all in one place.
Send for signature directly from an estimate, contract, or order. No PDF upload, no tab switching, no copy-paste of signer details.
Every view, field change, signer IP, and timestamp is recorded. Compliant with ESIGN, eIDAS, and Japan's Act on Electronic Signatures.
Internal approvers sign off, counterparty signs, and the record moves to closed-won — all without leaving the workspace.
Why e-signature belongs in your back office
DocuSign and Adobe Sign are excellent signature routers. They are bad systems of record. Most teams end up with:
- Signed PDFs in a DocuSign folder nobody looks at
- Field data re-keyed into the CRM by hand
- Approval history in Slack threads that get archived
- No way to report on "time from quote sent to fully countersigned"
Sanka E-Signature keeps signature as a state of the record, not as an attachment. The signed document, the version history, the approval chain, and the data fields are all one object. Your CPQ quote becomes a signed contract becomes a closed-won deal becomes an invoice — same record, same audit trail.
| Pattern | Third-party e-sign | Sanka E-Signature |
|---|---|---|
| Send a contract | Export PDF, upload to tool, fill signer | One-click from the record |
| Track status | Check the e-sign dashboard | Status is the record state |
| Re-sign after change | New envelope, new link, new chase | Version bumped on same record |
| Reporting | CSV export and manual join | Native reports on time-to-sign |
| Countersigned copy | Email to ops, ops files manually | Automatically attached to the record |
Built for the full revenue motion
Sanka E-Signature ships pre-wired into the Sanka objects where signatures actually live:
- Estimates / Quotes — signer sees the same line items, discount logic, and pricing the AE priced
- Contracts — legal approval, redline tracking, counterparty signature, and renewal sequencing
- Orders — customer countersign on delivery terms; vendor countersign on purchase orders
- MSAs and order forms — master + order pattern, where MSA is signed once and order forms reference it
- Change orders — preserves the parent contract lineage with a delta-only signature flow
Because each record carries its own signature state, cross-deal reports like "open contracts older than 30 days" or "POs awaiting vendor counter-sign" are one click, not one spreadsheet.
Approval workflows and counterparty routing
Most deals have more than two signers. Internal legal, finance, CRO, and sometimes the board sit between the AE and the customer.
- Parallel or sequential approvers — by amount, entity, or deal attribute
- Counterparty routing — customer's legal signs first, then procurement, then authorized signatory
- Delegation — approvers can delegate with time-bound limits
- Out-of-office fallback — auto-route to the next approver, with alert to the original
Every step writes to the same audit trail. When the deal desk asks "why did this sit for three days," the answer is visible from the record.
Compliance and security
- Legal frameworks: ESIGN Act (US), eIDAS (EU), Japan's 電子署名法
- Identity verification: email OTP, SMS OTP, enterprise SSO for the signer
- Tamper-evident sealing: hash-signed PDF with certificate of completion
- Long-term archival: signed originals retained 10 years by default, configurable per retention policy
- Data residency: US, EU, Japan regions available
- SOC 2 Type II: covered under Sanka's workspace security controls
Pairs with HubSpot and Salesforce
Like every Sanka module, E-Signature works on top of your existing CRM. Quotes and contracts sync to HubSpot and Salesforce via native integrations, and signature state appears as a field on the CRM record so your reps don't have to switch tools to check status.
- HubSpot: appears as a custom property and activity on the deal timeline
- Salesforce: appears on the opportunity with activity history and files
- Webhook events for downstream billing, RevRec, and accounting