Purchase Order Software: Close a Partial Delivery Correctly

Purchase order software should distinguish what your factory ordered, what physically arrived, what inspection released, and what the supplier still owes under the current agreement. A partial receipt must not silently close the balance. Canceling an unreceived quantity must not create a receipt or make held material usable.

Use the worked example below with purchasing, stores, and production when evaluating a system. It focuses on one narrow decision: how to close or reduce an open delivery balance while preserving the original order and its receipt history. The broader follow-up process is covered in our supplier delivery tracking guide.

Give each quantity a clear meaning

A status such as partially received does not tell a planner how much material can be used today. Start with separate quantities and agree on their definitions:

• Original ordered: the quantity on the approved order before later amendments.
• Received: the physically verified quantity recorded against a receipt and order line.
• Released: received material that has passed the required checks and is available under the agreed stock rules.
• Held: received material still awaiting a decision; it is not also part of the unreceived balance.
• Canceled: an explicitly approved reduction of the quantity no longer expected from this order.
• Open to receive: the outstanding delivery quantity after valid receipts and amendments.

Software may use different labels. Ask the vendor to map these meanings to its actual fields and reports. For a named product example, Microsoft's Business Central documentation describes entering a partial receipt quantity and retaining a received quantity below the ordered total. That is evidence of that product's workflow, not a claim about every purchasing system or Ploqy's capabilities.

Work through a 100-piece order

Hypothetical example, not a customer result: a small assembly manufacturer orders 100 brackets on one purchase-order line. All quantities use pieces. There is no opening stock, no issue to production, no return, and no competing reservation in this simplified case. The agreed delivery is split into 60 pieces first and 40 later.

Stores counts and records the first delivery of 60. Inspection releases 52 and places eight on hold. The order now has four useful facts: 100 originally ordered, 60 received, 52 released, and 40 still unreceived. The eight held pieces are already included in the 60 received.

Check the two balances independently: 100 ordered = 60 received + 40 open. Within the receipt, 60 received = 52 released + eight held. Adding the held eight to the open 40 would wrongly report 48 pieces still due from the supplier before any replacement decision.

An inventory system for manufacturers should retain the held status and location. It should not treat a purchase-order receipt alone as proof that all 60 pieces can be issued. Whether a factory uses inspection on every receipt or only selected items is a process decision; this example explicitly requires it.

Cancel part of the remainder without rewriting the receipt

Suppose the production requirement changes. After reviewing the impact and obtaining the necessary internal and supplier agreement, purchasing cancels 15 of the 40 unreceived pieces. The supplier is now expected to deliver 25, not 40. Keep the approval, reason, communication reference, and effective date connected to the affected order line.

The audit view should now explain 100 original pieces = 60 received + 15 canceled + 25 open. A system might display an amended order quantity of 85 alongside a retained original quantity of 100. Another might preserve the original line quantity and separately record canceled delivery remainder. Either approach needs an understandable history and a consistent remaining-supply calculation.

The receipt of 60 has not changed. The released quantity is still 52, and the held quantity is still eight. Do not post a fictitious receipt for the canceled 15, delete the first receipt, or use a stock adjustment merely to clear the buyer's open-order list.

Confirmation behavior can differ by product. Microsoft documents a delivery-remainder cancellation case where the existing confirmation journal is not changed. Ask your vendor what amended document or communication the supplier will actually receive; a changed internal balance does not prove the supplier has seen it.

Show the planner current supply, not an optimistic total

At this stage, only 52 pieces are released in the simplified example. Another 25 are expected on the supplier's confirmed future date. The eight held pieces have an unresolved disposition and should remain a separate exception. Do not present 100 pieces as covered just because that was the original order.

If a job requires 70 released pieces now, the immediate gap is 18 pieces: 70 minus 52. The expected 25 may cover that gap only after arrival and any required release, and only if the timing supports the job. This is a planning illustration, not a recommendation to issue held material or disregard other job priorities.

Make the cancellation visible to the owner of the affected requirement. Reducing future supply can expose a shortage even when purchasing has correctly updated the order. Our material shortage alert guide explains how to connect that exception to the production decision.

Close receiving without losing unresolved work

The remaining 25 arrive, are counted, and pass the required inspection. Total receipts become 85, released pieces become 77, and eight remain held. The receipt balance is now 85 = 77 released + eight held. The original order reconciliation is 100 = 85 received + 15 canceled + zero open.

With no further deliveries expected, receiving can be complete under this example's policy. That does not resolve the eight-piece quality hold or prove that all other purchasing tasks are finished. Keep the inspection record and owner accessible after the line leaves the open-delivery queue. Invoice processing and payment are separate workflows and outside this guide's quantity test.

If the held pieces are later rejected and a replacement is agreed, record that new decision and its linked return or replacement requirement. Do not automatically assume either that the original order must reopen or that a new order must be created. Test the supported workflow and make sure the supplier is not chased twice for the same replacement.

Use this purchase order software acceptance checklist

Ask for the following demonstration using one non-confidential order line. Record the actual transaction references and any unresolved behavior:

1. Partial receipt: receive 60 against 100 and show 40 open, not a completed order.
2. Inspection split: retain 52 released and eight held without treating the hold as another unreceived quantity.
3. Approved reduction: cancel 15 of the unreceived 40; preserve the receipt and show 25 open with a traceable reason.
4. Supply impact: remove the canceled quantity from expected supply and show the affected job owner the change.
5. Final receipt: receive and release 25; reconcile 85 received, 15 canceled, zero open, and the unresolved hold of eight.
6. Controlled correction: demonstrate a mistaken-entry correction and an import retry without duplicating a receipt or cancellation.
7. Readable history: export the original quantity, amendments, receipts, inspection references, outstanding quantity, and responsible users.

These are proposed acceptance conditions, not claims that Ploqy or a named product already implements your exact process. Start with one material family before adding returns, over-deliveries, or multiple units of measure. A useful buying test ends with purchasing, stores, and production explaining the same balance without a separate spreadsheet.