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.
- Procurement
- Features
- Purchase orders
Purchase orders
The purchase order is the document the supplier acts on and accounts payable matches against. Drafts, approvals and amendments retain the commercial version the supplier should fulfil and accounts payable should match.
OverviewApproved Requisitions To Convert×
Procurement · Purchase orders
New
Approved Requisitions To Convert
Purchase requisitions
| Req number | Requester | Department | Total amount | Priority | Approved at | |
|---|---|---|---|---|---|---|
| PR-68266 | Carlos Kim | Customer Support | 1,651.10 | Routine | 24 Oct | |
| PR-77240 | Nora Patel | Customer Support | 42,563.38 | Expedited | 17 Oct | |
| PR-47682 | Omar Silva | Customer Support | 18,820.44 | Emergency | 27 Oct | |
| PR-39283 | Priya Okafor | Customer Support | 34,320.05 | Routine | 24 Oct | |
| PR-55279 | Mei Haddad | Research and Development | 27,277.80 | Expedited | 25 Oct |
6 of 6 records
Customer SupportPurchase requisitions · PR-68266
RoutineRequesterCarlos Kim
Total amount1,651.10
Approved at24 Oct
Conversion pathDirect PO
What you can do
Where orders come from
- Approved requisitions. When the Buyer sets the conversion path to direct order, lines are grouped by supplier and one draft order is created per supplier. The requisition’s GL accounts and project codes are carried onto the lines.
- RFQ awards. The awarded response becomes a draft order priced at the quoted lines.
- Blanket releases. A release against a master agreement generates an order already priced at the agreement.
A Buyer can also raise an order by hand. An eligible configured Buyer-limit policy can authorise an original hand-raised order without requisition, award or release backing. Mandatory competition and pricing controls still apply; other orders follow the applicable matrix.
The order record
| Field group | What it holds |
|---|---|
| Identity and source | PO number, Revision, Supplier, from requisition, from RFQ award, master agreement |
| Competition | Competition type (Competed, single bid, sole source, Blanket, Catalog), sole source justification, clause set |
| Commercial | Order date, expected delivery, payment terms, FOB point, freight terms, total amount |
| Routing and logistics | Department, cost center, ship to location, bill to entity |
| Override | Price override approved, price override reason, off contract reason, price override by |
| Control | Buyer, approved by and approved at, sent at, acknowledged at, acknowledged revision, closed at |
Each line carries its category, item or free-text description, quantity, unit, unit price, need-by date, GL account and project code. It also carries the contract rate it was matched to and the contract price as a snapshot. Each line has its own status from Open through partially received and Received to Closed. Net accepted fulfilment and the open quantity live on each line. Gross arrivals and rejected units remain separate receipt evidence.
Status
Draft → pending approval → Approved → Sent → Acknowledged → partially received → Received → Closed, with Cancelled available before receipt.
- pending approval freezes the submitted revision for authority and pricing checks.
- Approved queues the configured accounts-payable handoff; delivery acknowledgement remains separate evidence.
- Sent is the Buyer’s action: the approved revision goes through the configured PDF or EDI channel to the supplier.
- Acknowledged is the supplier’s action, through the portal or an EDI 855, and stamps the date and the revision acknowledged. Orders still in Sent on the Open Purchase Orders view are the ones the Buyer chases for acknowledgement.
- Closed requires resolved delivery, return and match obligations, with current-revision accounts-payable evidence covering all expected invoices and credits.
Approval
Spend approvals record the prior decision and approved revision; spend approval lines define its scope. Commitment allocations reserves the amount and quantity consumed by each order line. Reuse checks the remaining authority, tolerance, department, cost centre, category and item. Requisition conversion preserves that evidence. An RFQ award supplies the selected offer but grants no spending authority alone.
Without valid reusable authority or an eligible Buyer-limit decision, the order routes on its total through all applicable matrix rules. Every required step retains its assigned person and rule. Submitted commercial fields are frozen; a revised draft invalidates the earlier calculation and requires new routing.
A line that fails the guardrail or sits off contract in a category that requires one holds the order regardless. Procurement Manager records the exception decision and reason. Clearing that hold does not substitute for the required spend approval.
Amendments
Changes after sending are recorded as change orders rather than edits. A change order records the type (quantity revision, price revision, need-by reschedule, line add, line remove, cancellation), the reason, and one line per affected PO line with the old and new values. Routing checks the proposed order total and cumulative gross increases against the original approved baseline. Positive line increases accumulate before netting; another line’s reduction cannot offset them for routing. The routing amount is the greater of the proposed total and original approved total plus cumulative gross increases; the configured threshold adds any required higher tier. Added lines include item or description, category, unit, coding, quantity, price and date. Price changes on partly received lines split the unfulfilled portion, preserving fulfilled value at its original price. On approval the new values are applied to the lines, the order’s revision number increments and is stamped on the amendment, and the supplier is asked to acknowledge the new revision. The same change updates authority consumption and any agreement commitment before it takes effect. Cancellation releases unfulfilled value while retaining fulfilled history.
Supplier acknowledgement
My Open Orders gives Supplier access to its own issued orders and amendments. Acknowledgement identifies the accepted revision. Changed dates require an approved amendment; a supplier message alone cannot alter the issued obligation.
What people see
- Approved Requisitions To Convert as the intake queue.
- POs Pending Approval for the Procurement Manager and approvers, and Pending My Approval for the steps assigned to each person.
- Open Purchase Orders for everything sent and not yet fully received, with sent and acknowledged dates.
- My Open Orders for the supplier.
- Open Commitment Lines for the Controller: every open line with its value and GL account.
What it keeps track of
Data model- Purchase orders
- Supplier order with immutable approved revisions. Spend approvals record its authority separately from lifecycle; an RFQ award is selection evidence only. Prior requisition or agreement authority may be reused only within its approved scope and remaining capacity. Otherwise full matrix approval or the explicitly configured Buyer-limit exception is required before issuance.
- PO line items
- Per-item lines on a PO. The level at which receipts and the invoice match reconcile, and where the contract price check is recorded.
- PO amendments
- A reviewed change to an issued or approved PO revision. All amendments route on the proposed total and cumulative positive increases, including new scope; decreases cannot reset the escalation basis. Applying the approved change atomically updates lines, commitments and the exact order revision once.
- PO amendment lines
- Per-line before and after on an amendment.
- Approval steps
- One row per approval tier a requisition, purchase order or amendment passes through. The audit trail: which matrix row, which person, on whose behalf, when, and what they said.
- Approval matrix
- Effective-dated approval rules for Department × cost center × Category × full-document USD routing amount × tier. All matching specific and wildcard rows apply; required steps are unioned, not replaced by a narrower match. Routing must cover every distinct line scope and amount, or submission blocks.
- Locations
- Ship-to and receiving places: a dock managed by the warehouse system, an office where desk deliveries land, or a site. The PO ships to one and the receipt is taken at one.
- Spend approvals
- Versioned authority request and frozen decision for a complete source revision. Document lifecycle may progress independently. Submitted content and approved decisions cannot be overwritten; invalidation stops future use but does not erase existing commitments. Reused authority and Buyer-limit policy are explicit decision types, never a fabricated new human signature.
- Spend approval lines
- Immutable scope and approved allowance within a spend approvals decision. Separate lines retain routing dimensions and source identities. Parent and line ceilings are both enforced; changing supplier, item, category, quantity, scope or value outside this packet requires a new decision.
- Commitment allocations
- Immutable signed effects of a business event on a PO line and its funding authority. Amount delta measures actual order commitment; authority amount delta separately measures use or release of the linked approval allowance, preventing a new approval packet from duplicating agreement spend. Reversals are compensating Posted rows referencing the original.
Who uses it
Permissions- Buyer
- Drafts, sends and amends.
- Approver
- And Controller approve at their tier.
- Procurement Manager
- Releases overrides.
- Supplier
- Acknowledges.
- Controller
- Reads open commitment.
- Requester
- Sees the status of orders raised from their requisitions.
Set up Procurement your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.