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.
- Vendor Management System
- Features
- Orders and delivery
Orders and delivery
Follow an approved supplier order through acknowledgement, receipt and exceptions.
OverviewOrders Awaiting Approval×
Vendor Management System · Orders and delivery
New
Orders Awaiting Approval
Approval waits for the approver
| PO number | Vendor | Total amount | Department | Cost center | Status | |
|---|---|---|---|---|---|---|
| PO-75796 | VND-050 | 30 | DPR-110 | CC-130 | Pending approval | |
| PO-60538 | VND-129 | 910 | DPR-110 | CC-150 | Pending approval | |
| PO-43896 | VND-132 | 700 | DPR-110 | CC-140 | Pending approval | |
| PO-97786 | VND-214 | 630 | DPR-110 | CC-120 | Pending approval | |
| PO-38941 | VND-185 | 660 | DPR-110 | CC-120 | Pending approval |
6 of 6 records
VND-050Purchase orders · PO-75796
Pending approvalTotal amount30
DepartmentDPR-110
Cost centerCC-130
What you can do
Keep the issued promise traceable
A purchase order holds the supplier, Buyer, ship-to location, terms, revision, amount and approval identity. An order line carries quantity, price, category and need-by date for each item or service. A line’s original need-by date remains available when a later change is reviewed. Approval steps and spend approvals retain the decisions behind the issued scope, while Commitment allocations record signed effects on authority and commitment.
The order status follows Draft, pending approval, Approved, Sent, Acknowledged, partially received, Received and Closed, with Cancelled for stopped work. An amendment record holds a proposed revision and its before-and-after lines. Buyer can review the change to unexecuted scope without rewriting prior receipts. Expediting follows open lines that are late or at risk; it records the original date, supplier promise, severity and owner.
How the work is organized
- Approved issue. Buyer prepares an order from the approved sourcing scope. Approver decides the assigned amount and revision before Buyer sends it.
- Actual arrival. Receiving Clerk records each delivery and accepted or rejected quantity on receipt lines. The receipt links to the exact order revision and receiving location.
- Follow-up. Buyer tracks expediting, returns and invoice match exceptions against the order, line and supplier rather than keeping those issues in an email trail.
What to agree during setup
Define which buyer can prepare orders, who may approve each amount tier and when a price override requires Procurement Manager review. Agree how a supplier acknowledges an issued revision. Map dock and desk locations to the right Receiving Clerk or Requester. Decide how the team handles short shipment, damaged goods and a promised later delivery. Set the connection to accounts payable for invoice matching and completion evidence; the order record remains the purchasing source for its own terms and receipts.
Check the handoff on an actual case
Prepare an order for ten units with a defined need-by date and approved price. After issue, receive six units. Receiving Clerk records six accepted units and checks the order remains partially received. Buyer sees the four outstanding units in Open Expediting and records a revised supplier promise. If the new date becomes a contractual change, prepare an amendment and review it at the correct approval amount. Receive the balance later and compare the final receipt with the original and revised dates.
For a damaged arrival, record rejected quantity and reason on the receipt line. Link a supplier return to that line and inspect the return’s disposition. Controller can then compare order, receipt and match exception evidence without treating the damaged units as accepted fulfilment.
What your team sees
- Order Pipeline Board — Draft through acknowledged orders by current status.
- Orders Awaiting Approval — Order revisions that need a named decision.
- Open Expediting — Outstanding supplier lines with severity, owner and promise date.
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.
- Approval steps
- One row per approval tier a requisition, purchase order or amendment passes through.
- Spend approvals
- Versioned authority request and frozen decision for a complete source revision.
- Commitment allocations
- Immutable signed effects of a business event on a PO line and its funding authority.
- PO amendments
- A reviewed change to an issued or approved PO revision.
- PO amendment lines
- Per-line before and after on an amendment.
- Receipts
- Physical arrival or service acceptance against a PO.
- Receipt line items
- Per-line received quantity against a PO line.
- Vendor returns
- Controlled return of rejected arrivals or previously accepted goods.
- Expediting
- The expediting worklist: open PO lines past Need By Date or inside the warning window.
- Match exceptions
- A mismatch returned by accounts payable when the invoice disagrees with order or receipt.
Who uses it
Permissions- Buyer
- Prepares and follows orders.
- Approver
- Decides assigned approval steps.
- Receiving Clerk
- Records arrivals and returns.
- Controller
- Reviews commitment and match evidence.
Set up Vendor Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.