Start with reviewed source data
Imports are staged for review before they become active work. Buyers can confirm supplier identity, order number, currency, lines, quantities, prices, and requested dates. This checkpoint prevents an extraction or mapping error from becoming a supplier-facing instruction and records who accepted the source.
Separate external response from internal disposition
Suppliers may accept, decline, or propose changes. Those actions create evidence and buyer tasks; they do not grant internal authority. A buyer can accept, reject, or supersede a proposal with a reason. The current commitment updates only through that explicit disposition path.
Apply roles where they reduce risk
Workspace roles separate ownership, administration, and ordinary buyer work. External supplier links are scoped to a specific order and expire. Sensitive configuration such as SSO, SCIM, billing, templates, reminder policy, and membership remains restricted while operational users can process the queue they own.
Close with exports and history
Commitment and audit exports support reconciliation with downstream systems. Every send, view, response, proposal, decision, reminder, and configuration change carries an actor and timestamp where applicable. The resulting record can explain both the current answer and the path that produced it.
Validate the workflow with one real purchase order
Before buying or replacing software, run one representative multi-line PO from reviewed source through supplier response and buyer resolution. Include at least one accepted line, one proposed date or quantity change, and one delivery or reminder edge case. Confirm that every participant can identify the current owner and next action, that the original order remains unchanged, and that the final commitment can be exported and traced to its response and decision. Also verify the supplier experience on a normal phone and desktop browser, revoke and reissue a response link, inspect a failed delivery, and test the role boundary with a non-owner buyer. This evidence is more useful than a feature checklist because it exposes adoption friction, hidden authority, and incomplete system boundaries before the workflow reaches production volume.
Keep source, proposal, decision, and commitment distinct
Pacteva records supplier responses and authorized buyer decisions. It does not silently alter the reviewed purchase order or claim an ERP changed unless a configured write-back is verified. Requisitions, budgets, receipts, invoices, payments, inventory, and shipping remain in their systems of record.
What buyers usually ask
Can we customize the workflow?
Teams can configure templates, reminders, roles, and integration behavior. The source/proposal/decision/commitment separation remains fixed because it protects record integrity.
Does a supplier need a workflow account?
No. Suppliers use order-scoped links; buyers and administrators use authenticated workspaces.
Can users delete audit events?
The operational design is append-only. Corrections create new attributable events rather than rewriting history.