The purchase order header says closed, but receiving has only part of the material and production is still waiting. Purchase order tracking needs to explain the remaining obligation on each line. A summary status cannot tell you whether the missing quantity was canceled, rejected, delivered elsewhere, or never shipped.
Start with the order line, preserve each receipt and change, and give unresolved quantities an owner. Keep the supplier’s promise separate from the date material becomes usable. Then build the daily follow-up list from those records, so a purchaser can explain both what is missing and the next action.
Stage 1: the buyer establishes the line being tracked
Give each line a stable key using the source system, purchase order number, and line identifier. Retain the supplier, item, ordered unit, destination, and approved quantity. A product description can change, and the same item can appear on several lines with different delivery dates. Joining records only by item name can assign a receipt to the wrong commitment.
Define a receipt as the recorded arrival of goods, then distinguish whether your source records physical arrival or accepted usable stock. Define a cancellation as an approved reduction in the remaining purchase obligation. A rejection requires its own disposition: replacement, credit, return, or another agreed outcome. These definitions determine the open-quantity calculation.
Microsoft’s Business Central purchasing documentation describes partial receipts through line quantities. Its warehouse-handling configuration changes where receipt posting occurs. Map the evidence from the workflow your warehouse uses rather than assuming every purchase order is posted the same way.
Kartik Deshpande prepared this process using official documentation checked October 22, 2026. The worked quantities are hypothetical and are not results from a tested implementation. The ERP inventory management comparison covers the separate decision about which system owns purchasing and stock records.
Stage 2: the buyer records the supplier’s commitment
Store the requested date, the supplier-confirmed promise, and your expected usable date separately. Microsoft’s purchase reporting model distinguishes requested, promised, planned, and expected receipt dates from the invoice payment due date. Use the source field’s meaning instead of choosing whichever date happens to be populated.
When the supplier changes a promise, retain the earlier date and the confirmation behind the revision. Record who accepted the change and when. Otherwise, replacing yesterday’s missed date with next week’s date makes a late line disappear from the report without resolving the shortage.
If goods need inspection or putaway, the arrival date and usable date may differ. Agree who updates each one and which calendar applies. The lead-time article explains how to separate supplier time from the internal steps before material can support production.
Stage 3: receiving records arrival and quality disposition
The receiving owner records the quantity, unit, receipt reference, location, and actual arrival date. Link the packing document or other permitted supporting evidence. If an order is in cases and receiving counts individual units, preserve the conversion and verify it before adding the receipt to the line total.
Zoho Inventory’s purchase-receive instructions document receipt records against purchase orders and their export. Use the equivalent event records in your system. A current balance without the receipt detail cannot explain which delivery caused a discrepancy.
The quality owner determines which arrived goods are accepted, held, or rejected under your process. Held stock should remain visible without becoming an assumed usable receipt. The buyer then records what the supplier owes for rejected goods, including whether an existing line remains open or a separate replacement document is created.
Reconcile a partial receipt, rejection, and cancellation
Assume one line for 100 units, all measured as individual units. Sixty physically arrive. Of those 60, quality accepts 50 and rejects 10; the rejected 10 are returned and the supplier agrees to replace them. No replacement has arrived yet. The original physical-arrival total remains 60 in this example, while accepted usable supply is 50.
Next, the buyer and supplier agree to cancel 20 of the 40 units that never arrived. That cancellation does not apply to the rejected batch or its replacement. The retained requirement is now 80 units: 50 accepted, 20 still due from the original unreceived quantity, and 10 owed as replacement.
| Measure after those events | Quantity | Meaning |
|---|---|---|
| Original ordered quantity | 100 | Before the agreed cancellation |
| Cumulative physical arrival | 60 | Includes the 10 later rejected and returned |
| Accepted usable quantity | 50 | Goods retained as accepted supply |
| Canceled never-received quantity | 20 | Approved reduction of the original obligation |
| Original quantity still due | 20 | 100 minus 60 arrivals minus 20 cancellations |
| Replacement still due | 10 | Rejected units the supplier agreed to replace |
| Total usable supply still owed | 30 | 20 original plus 10 replacement |
A requirement-based check is 100 ordered minus 20 canceled minus 50 accepted = 30 still owed. This works only because every rejected unit remains a replacement obligation. If the agreement instead removes those units from the purchase requirement, change the definition and document that decision. Do not silently treat a credit as a replacement shipment.
Source systems represent returns differently. If your received figure is already net of the rejected return, subtracting the rejected quantity again would overstate the shortfall. Map the event types before applying a formula. Keep replacement links so a replacement purchase order does not cause the same ten units to appear twice in expected supply.
Stage 4: purchasing works a line-level exception list
Create an overdue exception when an unresolved supply obligation has passed its applicable promise date. Treat a missing promise as a separate unconfirmed-date exception. A blank date is not evidence that the line is on time, and an overdue line should retain its remaining quantity rather than repeating the entire original order.
Assign the buyer to supplier follow-up, receiving to missing receipt evidence, and quality to unresolved disposition. Each exception needs the next action, owner, and follow-up date. A buyer can confirm when the supplier will ship the remaining 20 while quality and purchasing resolve the replacement ten; those commitments may have different dates.
Stage 5: close supply obligations and review invoices separately
The buyer closes a supply obligation after the retained requirement is satisfied or the remainder is approved for cancellation. Zoho’s purchase-order instructions restrict selective cancellation to remaining quantities that have not been billed or received. Follow the actual system’s supported correction process rather than editing historical quantities to force closure.
An invoice records a financial claim; a receipt records a goods event. Microsoft’s purchase-posting documentation explains separate receipt and invoice posting and line-level partial quantities. Have accounts payable review billed quantities and discrepancies independently from the buyer’s supply status.
A supplier invoice marked paid does not prove the remaining material arrived. Likewise, a fully received line may still need an invoice or credit review. The inventory reconciliation process covers how to compare those records without treating one status as proof of another.
Check old open orders before moving the tracker
Choose a cutover time and reconcile each open line to receipts, returns, cancellations, and replacement documents. Preserve old line IDs and current supplier promises. In the example, importing 100 as new open supply would ignore the accepted quantity and cancellation. Importing only 20 would omit the replacement obligation.
Test one partial order through its next receipt in the destination. Retry the import to check that stable event IDs prevent duplicates. Keep archived history readable and distinguish an old unresolved order from a stale report that has stopped refreshing. The owner should verify the actual supplier obligation before carrying an old line forward.
Where Permute fits in purchase order tracking
Permute sells connected business data and custom applications. A suitable project could combine permitted purchase-order exports, receiving records, and supplier-confirmation data while preserving their source references. Match the order and line identities before calculating a combined balance.
Define which receipt types count as accepted, how cancellations reduce demand, and where replacement obligations live. A purchaser could then inspect an exception with the source events behind its open quantity. Missing receipt evidence or an unconfirmed promise should remain visible until its owner resolves it.
Explore one open-order reconciliation problem
Start with a permitted order line and the receipts or changes that should explain its balance.
Keep supplier decisions and source updates under control
Permute does not determine whether a supplier credit settles a contractual obligation or choose the accounting treatment. Source access and implementation scope need confirmation. Any external order update requires separate authorization and permissions; a tracking report does not itself cancel a purchase.
Track the obligation on each line and retain the events that change it. Distinguish accepted supply from physical arrivals and financial status. Give missing quantities and dates an owner instead of relying on the header to explain them. Close the line when its remaining obligation is resolved and the evidence supports that conclusion.
Review an unresolved purchase-order balance
Bring the order, receipt history, and supplier commitment your team needs to explain.
Questions about open purchase orders
Should an order without a supplier promise appear overdue?
Classify it as unconfirmed unless your process has another explicit deadline. Keep that exception visible and assign someone to obtain the commitment. Do not invent a date or treat the blank as on time.
Does a supplier credit remove the replacement quantity?
That depends on the agreed commercial outcome. Record whether the requirement was reduced or the supplier still owes replacement goods. The credit document alone should not decide the supply calculation.
Can the same item appear on more than one open line?
Yes, separate lines can carry different destinations or promises. Preserve the line identifier when matching receipts. Aggregating by item alone can hide which commitment remains unresolved.
What should a purchaser do when a closed header has an unresolved balance?
Investigate the supporting receipts, cancellations, and replacements before changing the status. Use the system’s supported correction path and retain the reason. A dashboard adjustment without a source correction can leave other teams using the original misleading record.