An open purchase order report is a worklist for checking what still needs attention on each PO. First establish whether “open” refers to receiving, billing or a system status. Review each line against receipts, cancellations and invoices, then assign an action, owner and follow-up date. An old order is not necessarily overdue, and zero remaining delivery quantity does not authorize financial closure.
1. Define what the report calls “open”
The field team wants to know which materials still need to arrive. Purchasing wants to know which vendor commitments remain active. Finance wants to know which invoices or supporting documents are missing. These questions are connected, but one order list may not answer all three. Put the cutoff date and status definition at the top of the report.
For example, Oracle NetSuite defines its Open Purchase Orders report around an open billing status. Microsoft Business Central documents separate measures for outstanding orders and orders received but not invoiced. These are examples from other systems. Check the definition of your own report rather than assuming it uses the same one.
Further reading: Oracle NetSuite: Open Purchase Orders report definition · Microsoft: outstanding orders and received-not-invoiced measures
2. Build a line that supports a decision
Start at PO line level, particularly when different items have different delivery dates. Record the project, vendor, PO and line number, item description and unit of measure. Add the approved quantity, approved cancellations, net receipts, billed quantity, agreed delivery date and the documents supporting those figures.
For this worklist, remaining delivery quantity equals the original approved quantity minus approved cancellations minus net receipts. Net receipts are verified received quantities less documented returns. If your system has already reduced the order quantity for a cancellation, do not subtract it again. Compare matching units and investigate a negative remainder rather than hiding it as zero.
Give each line a reason for remaining open, an owner, a next action and a follow-up date. A manual spreadsheet with document references is a workable starting point. Keep missing information, such as an unknown delivery date, explicitly marked so it is not accidentally classified as on time.
3. Three open orders, three different decisions
This fictional example covers three orders for panels on a construction project, using the same unit and no returns. Billed quantities refer only to panels received in this example, with no advance billing. The table is neither a customer record nor a representation of an automated product report.
- 2101: the delivery remainder is 40. If the agreed date has not arrived, the line is open but not necessarily late.
- 2102: delivery is complete, but documentation for 20 still needs review. This does not establish a particular payable amount or authorize payment.
- 2103: the calculation is 50 − 30 − 20 = 0. The remainder is zero because the cancellation was approved and recorded; closing the line does not erase its history.
| Order | Reviewed record | Delivery remaining | Decision and owner |
|---|---|---|---|
| 2101 | Ordered 100; received 60; billed 60; no cancellation | 40 panels | Purchasing: confirm the date for the remaining 40 and check the effect on site work. |
| 2102 | Ordered 80; received 80; billed 60; no cancellation | 0 panels; 20 received without a recorded bill | Finance: check whether the invoice for 20 arrived but was not linked. Do not request another delivery. |
| 2103 | Ordered 50; received and billed 20; approved cancellation of 30 | 0 panels after cancellation | Purchasing and finance: verify cancellation approval and all documents before closure under company procedure. |
4. Prioritize by due date and project impact
Separate order age from delivery lateness. In an illustrative report cut off on September 18, a remainder promised for September 16 is two calendar days late. An order placed a month earlier but promised for September 25 is not yet late. Retain both the original date and any agreed revised date so a reschedule does not hide earlier performance.
First flag remaining quantities needed for an upcoming work stage or already past their agreed date. Then review receipts without billing documents and remainders awaiting cancellation approval. If the date is missing, first confirm it with the responsible person. A large amount or an old order may merit attention, but neither alone proves urgency.
At the next review, return to the same record: what changed, which document arrived, who approved it and when to check again. Keep closure reasons in the weekly worklist. Fewer open orders do not represent improvement if they were closed without resolving the underlying questions.
5. Gather the evidence before closing a PO
Ask the field owner to confirm that no required remainder is undocumented, and purchasing to verify cancellations and changes against the approved order. For returned materials, separately establish whether replacement or cancellation is required and what is happening with any credit. A system closure does not resolve a need for materials the project still requires.
Finance separately reviews invoices, credits and disputed charges under the company’s process. “Fully billed” is different from “paid,” and a closed PO does not prove that no financial obligation remains. Record the closure decision, owner and references, and keep the documents after the line leaves the active report.
6. Connect the worklist to project documents
A useful report lets the team trace a remainder back to its order and supporting document. For a partial delivery, use the delivery-tracking guide. For an invoice quantity mismatch, review the invoice discrepancy. For the vendor’s overall account balance, use supplier statement reconciliation. Links to those guides appear below.
Novapro brings purchase orders and documents into the project context and supports checking how they match. The worklist in this guide is a suggested manual process; it does not promise a built-in aging report, automatic closure or an existing accounting-system integration. Bring a sample order without sensitive data to a demo and review how the available workflow fits your team.
Practical checklist
- A cutoff date and clear definition of “open”; identified project, vendor and PO line.
- Quantity, unit, net receipts and approved cancellations checked without double subtraction.
- Delivery date and the jobsite’s required remainder checked separately from billing status.
- Every remainder or missing document has an action, owner and follow-up date.
- Closure is supported by approval and documents; billing, payment and credits follow the appropriate process.
In a personalized demo, explore how Novapro connects orders, deliveries and invoices in your project context.
Request a purchasing workflow demoFrequently asked questions
Why does a delivered PO still appear on an open-order report?
The report may use billing status, an invoice may not yet be recorded, or the closure status may not be updated. Check the report definition and PO lines before concluding that a delivery is missing.
Is every open purchase order overdue?
No. An order may remain open until a future delivery date, or because a billing document is missing after the goods have arrived. Assess delivery lateness against the agreed date and the quantity still to be received.
Is zero remaining delivery quantity enough to close a PO?
It explains only the receiving side based on the reviewed data. Cancellations, returns, invoices and credits still need review, and the authorized owner must make the closure decision under company procedure.
Keep reading
How to Track Partial Deliveries and Delivery Tickets →
Invoice vs. Purchase Order Discrepancies: How to Review and Resolve Them →