PO Header
Unique PO number, issue date, and buyer contact details to ensure traceability and match-back to invoices and receiving records.
A Special Purchase Order creates a clear, auditable record of a nonstandard procurement, reducing ambiguity about scope, price, and approvals. Electronically executed SPOs are enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA statutes where adopted; New York follows its ESRA framework. Exceptions such as certain court filings or testamentary instruments remain ineligible for e-signature under prevailing law.
Procurement, finance, and project teams commonly create and route Special Purchase Orders when standard POs won’t cover the purchase specifics.
A clear role split and documented approval chain reduces disputes and speeds receiving, invoicing, and payment reconciliation.
Unique PO number, issue date, and buyer contact details to ensure traceability and match-back to invoices and receiving records.
Vendor legal name, remit address, Taxpayer Identification Number (TIN), and vendor contact to support tax reporting and vendor verification.
Detailed descriptions, SKU or part numbers, quantities, unit prices, and total amounts so receiving can inspect and match items on delivery.
Expected delivery date, ship-to address, incoterms or delivery method, inspection criteria, and acceptance process to prevent disputes.
Payment schedule, discounts, freight allocation, and who bears taxes; clear terms reduce invoice discrepancies and late payments.
Authorized signatories, approval chain, and any referenced contracts or SOWs; include e-signature evidence and approval timestamps for audit trails.
| Field | Configuration |
|---|---|
| Approval Workflow | Two-tier approvals, sequential routing, and escalation rules |
| Conditional Fields | Show extra fields for high-dollar purchases or capital items |
| Auto PO Numbering | Enable system-generated unique PO numbers |
| Notifications | Email or SMS alerts on pending approvals and signed completion |
Choose file formats, integrations, and authentication that match your enterprise systems and security posture.
Ensure the chosen platform logs an audit trail, uses TLS and AES-256 encryption, and supports the retention policy required by your compliance rules.
Internal approval within 3 business days is typical.
Request vendor acknowledgement within 5 business days.
Vendor to confirm shipping date within agreed lead time.
Invoice must reference PO number for timely AP processing.
Follow agreed payment terms (e.g., Net 30) after invoice approval.
Procurement or department creates and submits SPO request for review.
Required management approvals are collected and recorded.
Signed SPO is issued to the vendor and logged in the system.
Goods or services are received, inspected, and matched to PO.
| 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 free trial | Yes | Yes | Yes | Yes |
| Bulk Send | Yes (Premium) | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
A regional property manager needed remote approvals for maintenance contracts across multiple sites.
An IT distributor required exception POs for bespoke equipment orders for enterprise clients.