1. IT Procurement System
  2. Features
  3. Purchase lines
Feature · Purchase lines

Purchase lines

Compare what was requested with what was accepted.

OverviewOrdered requests
IT Procurement System · Purchase lines

Ordered requests

Purchase requests

New
Record numberSubjectOrder referenceCounterpartyRequired byRequested amount USD
PR-35178Ordered pr-762OR-871SPP-920526 Oct890
PR-25896Ordered pr-583OR-616SPP-255007 Oct570
PR-36639Ordered pr-275OR-406SPP-322520 Oct400
PR-32898Ordered pr-215OR-386SPP-883924 Oct200
PR-50009Ordered pr-993OR-955SPP-274711 Oct490
6 of 6 records
Ordered pr-762Purchase requests · PR-35178
Ordered
Order referenceOR-871
CounterpartySPP-9205
Required by26 Oct
Requested amount USD890
Example screen with sample data

What you can do

Purchase lines in daily work

A purchase request for monitors may carry several lines, each with a line number, description, requested quantity and unit price in USD. The same line can later hold accepted quantity, acceptance date and invoice reference. The parent links all lines to the request and its order reference.

Line numbers help the team discuss which item arrived. Accepted quantity and date can differ from the requested quantity and required date on the parent. Read each line with the order reference and attached delivery evidence before calling the request received.

How the work is organized

  • Ownership. Buyer reviews requested lines and accepted quantities. Purchasing Approver and Auditor inspect the parent request.
  • Record context. Use the parent request and its organization when checking a related record, then confirm the selected supplier and owner where relevant.
  • Evidence. Keep the decision, accepted quantities, attachments and operation outcomes with the same purchase context so later review has the facts in order.

What to agree during setup

Agree how the team numbers lines and records partial acceptance. Check unit price and quantity against the requested USD amount before submitting the parent. Decide when an invoice reference is added and who checks it against the accepted goods.

Rehearse a partial monitor delivery. Compare each accepted quantity with its requested quantity and the evidence attached to the parent. Agree who checks the line entries and who decides whether the parent can be marked received.

Check the handoff on an actual case

Open an ordered request and inspect every line. If fewer units arrived than requested, check the accepted quantity and date against delivery evidence. Attach delivery evidence to the parent. Before marking the request received, compare accepted quantities with the order reference and the purchasing decision.

The Purchasing Approver should compare the accepted quantity with the requested quantity on each line. The Auditor should find the attached delivery file and request status. Resolve any shortfall before treating the full request as received.

What your team sees

  • Ordered requests — Find ordered requests whose linked lines need a delivery check.
  • Received requests — Compare received requests with line acceptance evidence.
  • Purchase request worklist — Trace the owner, supplier and required date of each parent request.

Follow the work through

Read request preparation, review and order and receipt reconciliation. The data model shows how the records connect.

What it keeps track of

Data model
Purchase lines
Requested and accepted line items belonging to exactly one purchase request.
Purchase requests
IT purchase requests with lifecycle status, owner, counterparty and requested USD amount.

Who uses it

Permissions
Buyer
Reviews requested lines and accepted quantities.
Purchasing Approver
And Auditor inspect the parent request.
App Administrator
Maintains organization membership and supplier configuration.

Set up IT Procurement System your way.

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

How to get started