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.
- Purchase Order System
- Features
- Purchase orders
Purchase orders
Issue an approved order revision and keep later changes connected to the original commitment.
OverviewOrders awaiting approval×
Purchase Order System · Purchase orders
New
Orders awaiting approval
Approval waits for the approver
| PO number | Supplier | Department | Cost center | Total amount | Revision | |
|---|---|---|---|---|---|---|
| PO-59397 | VND-176 | DPR-140 | CC-110 | 590 | 540 | |
| PO-94426 | VND-131 | DPR-110 | CC-140 | 910 | 430 | |
| PO-30614 | VND-163 | DPR-130 | CC-140 | 740 | 50 | |
| PO-63648 | VND-062 | DPR-130 | CC-150 | 340 | 450 | |
| PO-36924 | VND-129 | DPR-130 | CC-120 | 680 | 100 |
6 of 6 records
VND-176Purchase orders · PO-59397
Pending approvalDepartmentDPR-140
Cost centerCC-110
Total amount590
Revision540
Order date11 Oct
What you can do
Know which order the supplier is working to
The Buyer prepares the supplier order with its line quantities, prices and need-by dates. Billing entity, ship-to location, payment terms and freight responsibility make the commercial instruction clear. The order retains its originating request or awarded supplier response so the Approver can follow how the purchase was selected.
Approval, sending and acknowledgment are separate moments. The approved revision establishes the purchasing decision. The sent date records issuance, while the acknowledgment identifies the revision accepted by the supplier. This distinction matters when a supplier confirms an older version after the Buyer has prepared a change.
How the work is organized
- Order preparation. The Buyer checks supplier eligibility, contract pricing and competition type before requesting approval. A sole-source purchase has a justification. A price override has its own reason and recorded decision from the Procurement Manager.
- Revision control. Approved scope retains its amount and authority. An amendment describes the before-and-after values for affected lines and identifies the base revision. Applying an approved amendment creates a traceable change while preserving work already received.
- Delivery follow-up. Open order lines feed expediting work with an owner, severity and outstanding quantity. The original need-by date remains available alongside the supplier’s revised promise. The Buyer can therefore discuss recovery without losing the date against which delivery was originally expected.
What to agree during setup
Define how order numbers, billing entities and receiving locations are used. Confirm the terms Buyers may select and who resolves an exception to a negotiated rate. Decide which order changes require an amendment and explain how cumulative increases affect routing. A price decrease elsewhere on an order should not obscure the line whose increased exposure needs review.
Agree who records supplier acknowledgment and how communication delivery is reconciled. Identify the Buyer responsible for each supplier’s overdue lines. Set the warning window and escalation practice for expediting, then check how the team records a new promise without changing the historical delivery basis.
Check the handoff on an actual case
A Buyer orders packaging supplies for an agreed production date. The Approver approves the prepared scope and the Buyer sends that revision. When the supplier confirms it, record the acknowledged revision and compare it with the current order.
The business later requests a larger quantity on an unreceived line. Prepare an amendment showing the old and new quantity, explain the reason and review the resulting approval exposure. After approval, apply the change and send the revised instruction through the configured supplier connection.
Have the supplier acknowledge the earlier version during the rehearsal. The Buyer should recognize the mismatch and obtain confirmation of the intended revision. Next, record a late promise against an outstanding line. Check that the original need-by date remains visible and that the follow-up owner can explain what is still due.
What your team sees
- Order pipeline — Orders grouped by purchasing state with their current revision and commitment.
- Amendment review — Amendments with base revision and approval exposure ready for review.
- Expediting worklist — Outstanding lines with ownership, original dates and revised supplier promises.
Follow the work through
What it keeps track of
Data model- Purchase orders
- Supplier order with immutable approved revisions.
- PO line items
- Per-item lines on a PO, the level at which receipts and invoice match reconcile.
- PO amendments
- A reviewed change to an issued or approved PO revision.
- PO amendment lines
- Per-line before and after on an amendment.
- Commitment allocations
- Immutable signed effects of a business event on a PO line and its funding authority.
- Procurement events
- Durable once-only business event and migration provenance.
- Expediting
- The expediting worklist: open PO lines past Need By Date or inside the warning window.
- Integration deliveries
- Per-event destination outbox for an explicitly configured connection.
Who uses it
PermissionsSet up Purchase Order System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.