Scope of Services
Define accepted use cases, supported platforms and APIs, permitted data flows, and integration boundaries so both parties know which transactions the connector will process and which are out of scope.
A clear Purchase Connector Agreement aligns commercial expectations, limits technical and legal risk, and ensures that data flows and payment or order processes operate reliably. It creates an auditable record of obligations, fees, and service levels for both parties.
Teams that prepare or sign these agreements are usually procurement, IT/integration, legal counsel, and vendor account teams working together to manage technical and commercial requirements.
In small organizations a single operations manager may cover multiple roles; in larger organizations role separation and explicit approval routing are standard practice.
Define accepted use cases, supported platforms and APIs, permitted data flows, and integration boundaries so both parties know which transactions the connector will process and which are out of scope.
Specify one-time setup fees, recurring license or transaction fees, billing intervals, invoicing procedures, prorations, taxes, and the consequences of late payment to avoid billing disputes.
Include uptime targets, maintenance windows, response and resolution times for incidents, escalation paths, credits or remedies for downtime, and measurement methodology.
Require secure transmission and storage, encryption standards, data retention and deletion procedures, breach notification timelines, and obligations to execute a BAA where HIPAA applies.
Clarify ownership of connector code, integrations, and any customizations, plus licensing rights, restrictions, and reserved rights for each party.
Limit exposure through liability caps, carve-outs for gross negligence or willful misconduct, and mutual indemnities for third-party claims arising from a party's breach.
| Field | Configuration |
|---|---|
| Signer Order | Require sequential signing when approvals must follow business hierarchy. |
| Authentication Method | Use email + SMS code or KBA for higher assurance; require SSO for internal signers. |
| Conditional Fields | Show or hide clauses based on selected options to reduce errors. |
| Retention and Export | Enable PDF/A export and store certificate of completion for audit purposes. |
Verify platform capabilities for secure signing, audit trails, and document export before launching the workflow.
Allow 7–14 business days for internal review and approvals.
Begin integration within agreed SLA days after final signature.
Bill from the Effective Date or the Implementation Completion Date.
Provide nonrenewal notice 30–90 days before term end as specified.
Schedule deletion or archival according to retention policy.
Provide measurable uptime targets, scheduled maintenance windows, incident response steps, and remedies or credits applicable for missed service levels.
Include a field-level data mapping that identifies each data element exchanged, retention times, permitted uses, and masking requirements.
List set-up, recurring, and per-transaction fees, billing cadence, invoicing instructions, and any volume discounts or tiered pricing.
Attach a project schedule with milestones, acceptance tests, responsible parties, and post-implementation support responsibilities.
Optica Ventures integrated a payment connector to automate investor contributions
Xerox used a connector for NetSuite integrations across billing and document exchange
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes (premium tier) | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year limit | Varies | Varies | Varies |