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

Purchase lines

A request has two supplier lines with different unit prices.

OverviewPurchase line acceptance
SCM with Landed Cost Calculation · Purchase lines

Purchase line acceptance

Purchase lines

New
ParentLine numberItem descriptionRequested quantityAccepted quantityAccepted at
PR-95583890Line 116058003 Oct
PR-81546170Line 2405007 Oct
PR-10695350Line 341027011 Oct
PR-2740050Line 44003011 Oct
PR-93282900Line 55402008 Oct
6 of 6 records
Line 1Purchase lines · PL-54175
ParentPR-95583
Line number890
Requested quantity160
Accepted quantity580
Accepted at03 Oct
Example screen with sample data

What you can do

Keep the operating record clear

A request has two supplier lines with different unit prices. Requested quantity records demand; accepted quantity records what actually arrived. The receiving colleague enters the acceptance date and invoice reference on each line. That preserves a difference when a supplier delivers only part of the request. The parent request and operation evidence give reviewers the context for that line.

Each line retains the requested quantity and unit price alongside the quantity actually accepted. The acceptance date and invoice reference belong to that line. The parent request gives the receiving colleague the supplier and order context for the delivery.

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 who records physical acceptance and what document supports it. Decide how partial arrivals will be handled before the parent is marked Received. Over-receipt needs authorization rather than a silent increase. An invoice reference should be matched to unused accepted scope so the same arrival cannot be matched twice.

Rehearse a delivery that covers only part of a requested line. The Receiving Clerk records the accepted quantity and date without changing the requested quantity. Compare the invoice reference with the accepted scope before another match is attempted.

Check the handoff on an actual case

Take one line with a partial acceptance. Compare requested and accepted quantities, unit price and invoice reference. Follow the parent request to its supplier and order reference. Have the receiving colleague explain the quantity difference; have the reviewer confirm that the recorded action uses the expected revision.

Have the Receiving Clerk point to the line quantity actually received and the invoice reference used for that scope. If the delivered quantity exceeds the authorized amount, route it for authorization before recording acceptance.

When only part of a line arrives, keep the original requested quantity visible. The Receiving Clerk records the actual accepted quantity and date, while the Purchasing Approver checks any excess before it is accepted or matched to an invoice.

What your team sees

  • Purchase line acceptance — Lines with accepted quantities, dates and invoice references.
  • Requests due soon — Parent requests whose required date has arrived.

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
Purchase lines
Requested and accepted quantities and prices per purchase request.
Purchase requests
Purchase requests with lifecycle, counterparty and requested amount.
Operation receipts
Durable operation receipts for guarded workflow executions.

Who uses it

Permissions
Buyer
Owns requested line scope; Receiving Clerk records accepted quantities; Purchasing Approver reviews exceptions.

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