These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Vendor Scorecard
- Features
- Commitment Review
Commitment Review
Approve the exact submitted demand and retain an order reference only after the supplier handoff persists.
OverviewMy Requests×
SCM with Vendor Scorecard · Commitment Review
New
My Requests
Purchase requests
| Record number | Subject | Counterparty | Required by | Requested amount USD | Revision | |
|---|---|---|---|---|---|---|
| PR-40792 | Draft pr-979 | SPP-5870 | 15 Oct | 490 | 130 | |
| PR-19037 | Submitted pr-816 | SPP-4074 | 12 Oct | 520 | 60 | |
| PR-44476 | Approved pr-365 | SPP-5465 | 08 Oct | 530 | 260 | |
| PR-73406 | Ordered pr-992 | SPP-9078 | 25 Oct | 260 | 840 | |
| PR-58933 | Received pr-696 | SPP-5515 | 11 Oct | 160 | 620 |
6 of 6 records
Draft pr-979Purchase requests · PR-40792
DraftCounterpartySPP-5870
Required by15 Oct
Requested amount USD490
Revision130
What you can do
Separate the approval from the supplier order result
Procurement Reviewer receives the submitted request with its supplier, required date and requested amount. The decision concerns the exact revision prepared for review. A later change to quantity or scope cannot inherit the earlier approval merely because the request number remains the same.
Approval records the approved date and makes the eligible scope ready for the supplier commitment action. The handoff then needs to persist before the request carries the real order reference and Ordered state. This distinction lets the team investigate a request that has been approved but whose external handoff is still unresolved.
The operation receipt preserves the action, expected revision and result. Procurement Specialist follows that receipt when the supplier order response is delayed or disputed. A completed handoff is separate from supplier acknowledgement and the physical arrival of goods; receiving and invoice matching follow their own evidence paths.
How the work is organized
- Independent review. Procurement Reviewer checks the submitted scope and supporting files. The decision records the source revision and reason, keeping preparation and approval with distinct people.
- Commitment issue. Procurement Specialist requests the approved handoff through the guarded action. The request moves to Ordered only after the order effect is persisted and its actual reference is retained.
- Outcome investigation. Pending or failed operation results stay visible through their receipts. Auditor can compare the recorded decision and external evidence without changing the commercial record.
What to agree during setup
Name the independent Procurement Reviewer and agree which supporting information is needed before a decision. Use the request’s amount, budget code and line scope to explain the commitment being authorized. Administrative access must not substitute for that commercial decision.
Identify the supplier-order destination and the person responsible for its connection. Agree what external reference confirms the handoff and how an uncertain response will be investigated. The receiving system’s own acknowledgement and fulfillment process should be understood before the team relies on the Ordered state for follow-up.
Check the handoff on an actual case
Submit the replacement-component request and have a distinct Procurement Reviewer approve the current revision. Inspect the approved date and review record before requesting the supplier handoff. Follow the action to the actual order reference and verify that it describes the same approved scope.
Rehearse a delayed or uncertain handoff response. The team must inspect the original operation receipt before requesting another external effect. A request must not appear Ordered with a made-up reference merely to clear it from the review queue.
Finally, try a stale revision and the preparer’s identity as reviewer. Both should be refused. Repeat a successful guarded request and confirm that the original outcome remains traceable without another supplier order. The receiving team can then follow the real commitment into its accepted-quantity records.
What your team sees
- Request Review Queue — Submitted demand waiting for the independent decision.
- Open Commitments — Approved and Ordered requests with their required date and an order reference when the handoff has persisted.
- Commitment Board — The stored commitment state across the authorized purchasing scope.
Follow the work through
What it keeps track of
Data model- Purchase requests
- Demand records carrying requested amount, lifecycle status and supplier counterparty.
- Purchase lines
- Line items under a purchase request with requested and accepted quantities.
- Review decisions
- Independent approver decisions recorded against a purchase request revision.
- Operation receipts
- Idempotent receipts for guarded operations and their downstream effects.
- Record attachments
- Evidence files attached to a purchase request with visibility scope.
- Suppliers
- Approved supplier parties eligible for purchase commitments.
Who uses it
Permissions- Procurement Reviewer
- Approves eligible revisions.
- Procurement Specialist
- Requests and follows the supplier handoff.
- Receiving Officer
- Reads the commitment context.
- Auditor
- Inspects its decision and effect evidence.
Set up SCM with Vendor Scorecard your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.