1. SCM with Landed Cost Calculation
  2. Features
  3. Approvals
Feature · Approvals

Approvals

A buyer submits a request for a supplier order.

OverviewDecision history
SCM with Landed Cost Calculation · Approvals

Decision history

Review decisions

New
ParentSource revisionDecisionDecided atReasonReviewer
PR-18153740Approve04 OctApprove rd-628
PR-4222470Return13 OctReject rd-255
PR-57323700Approve04 OctReturn rd-808
PR-54625720Return10 OctApprove rd-652
PR-54482950Approve15 OctReject rd-890
6 of 6 records
Approve rd-628Review decisions · RD-44541
Approve
ParentPR-18153
Source revision740
Decided at04 Oct
Example screen with sample data

What you can do

Keep the operating record clear

A buyer submits a request for a supplier order. The approver reads its current revision and requested amount, then records Approve, Reject or Return with a reason and decision time. The decision points to the parent request and reviewer. It should correspond to exactly the revision the approver saw, not a later edit.

The request and its decision remain separate records. A reviewer can compare the decision’s source revision, reviewer and reason with the purchase request before anyone treats the commitment as authorized. The operation receipt records the outcome of the guarded action.

How the work is organized

  • Prepare. Put the owner, supplier and operating entity on the record before review.
  • Decide. Check the submitted scope and leave a decision with a reason when human approval is required.
  • Verify. Compare the stored effect with the intended action before treating the work as complete.

What to agree during setup

Agree which approver can decide for each organization and amount. Keep requester and approver separate. Define what evidence must be available before approval and when a returned request needs a new revision. The team should know how to handle an attempted order handoff whose receipt remains Pending or needs review.

Rehearse a submitted request whose amount changes before approval. The Purchasing Approver should decide only on the revision in front of them. If an order handoff is uncertain, compare its operation key and external reference before issuing another order.

Check the handoff on an actual case

Select a submitted request and compare its revision to the decision source revision. Confirm reviewer, reason and decision. Follow the operation key into the receipt and check whether the expected effect is present. A changed revision requires another review; a failed effect needs reconciliation.

Have the Purchasing Approver explain which request revision they approved and why. If the buyer changed the amount afterward, return the request for a new decision. Check the operation receipt before treating the supplier order as placed.

Before the first approval, test a request returned for changed amount. The Buyer should see the reason, revise the request, and submit it again. The Purchasing Approver must decide on that new revision rather than extending the old decision.

What your team sees

  • Requests awaiting approval — Submitted requests with their revision, amount and owner ready for a decision.
  • Decision history — Recorded decisions with reviewer, reason and source revision.

Follow the work through

Follow request to commitment, receipt and invoice match, and landed cost review for the related decisions.

What it keeps track of

Data model
Review decisions
Independent approver decisions for a source revision.
Purchase requests
Purchase requests with lifecycle, counterparty and requested amount.
Team members
Membership roster linking authenticated users to organizations and role scope.
Operation receipts
Durable operation receipts for guarded workflow executions.

Who uses it

Permissions
Purchasing Approver
Makes the independent decision; Buyer owns the submitted request; Auditor reads the decision trail.

Set up SCM with Landed Cost Calculation your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started