Retail purchase orders: close partial receipts without losing the balance

The buyer orders 240 lamps. The delivery contains 210. Receiving rejects eight of those because they are damaged. The supplier agrees to cancel 20 of the undelivered units.

A clerk sees a partially received order and wants to close it so it stops appearing on the open-order report. That action could hide ten lamps still expected and a separate decision about the eight rejected lamps.

Close the delivery obligation only after it is fulfilled, amended or cancelled. Keep the receipt, supplier remedy and finance records linked across their separate screens.

Reconstruct the first delivery

At this point in the example, the original 240 ordered units can be described as follows:

Check both balances: 202 + 8 + 20 + 10 = 240 ordered; 202 + 8 = 210 physically received. After cancellation, 240 − 210 − 20 = 10 remain undelivered.

The eight rejected units have not disappeared. They need an authorised remedy, such as replacement, supplier credit or another agreed outcome. That remedy is separate from the ten units not yet delivered.

This snapshot explains the original order. Record later returns and replacements separately so a replacement cannot also consume the original undelivered balance.

Record the receiving observation before deciding the remedy

The receiver needs the PO line and version, item identity, ordered unit, destination, actual count, accepted count and rejected count. Keep the supplier's delivery reference and any advance shipment notice as supporting evidence. Retain who recorded the observation and when the goods arrived.

A missing quantity and a damaged quantity are different observations. Do not record goods as physically received merely because the supplier's document says they were shipped. Where the software uses “rejected” for several kinds of discrepancy, retain a reason and actual received quantity that keep the distinction recoverable.

The buying team resolves commercial questions: whether the balance will arrive, whether a substitution is acceptable and whether a cancellation has been agreed. Receiving should not have to infer those answers while unloading.

Current Shopify documentation, for example, separates the purchase order's commercial record from a linked inventory transfer that tracks movement and receiving. Check whether a status belongs to the commercial PO or the receiving record. Shopify purchase orders.

Handle a replacement without receiving the same lamps twice

Assume the supplier agrees to replace the eight rejected lamps. The retailer returns those eight under a documented supplier-return reference. A later shipment delivers eight replacements and all are accepted.

Accepted units now total 202 + 8 = 210. Ten original units remain undelivered. If those ten later arrive and are accepted, the order reconciles to 220 accepted + 20 cancelled = 240. The replacement case can close once its return and receipt evidence agree.

Keep the original receipt, rejection, return and replacement receipt linked. Do not edit the first receipt from 210 to 218 to conceal the second delivery. The two shipments occurred at different times and have different evidence.

The replacement receipt also needs a stable event identity. If a scanner uploads it twice after losing connectivity, the second submission must not add another eight units. Check that a repeated identity carries the same item, quantity and destination; a changed quantity is a correction requiring its own recorded treatment.

If the supplier instead grants a credit for the rejected lamps, keep that credit decision separate from physical custody. A credit does not prove the damaged lamps have been returned, disposed of or released for sale. Those require their own authorised outcomes.

Decide whether to receive, amend or cancel

Several situations can look like “partial receipt” on an open-order screen.

A planned substitution also affects the catalogue and stock ledger. A different colour or pack should not be received against the original item because its price is similar. Use the SKU-mapping guide to examine the identity and unit before posting.

Give the buyer an exception view grouped by supplier, expected date and decision needed. Missing acknowledgement, confirmed delay and disputed rejection require different conversations.

Let accounts payable see the accepted evidence

Suppose the illustrative unit price is ₹100, excluding tax and other charges. An invoice for all 240 lamps is ₹24,000. At the first-receipt snapshot, the accepted quantity is 202, representing ₹20,200 on that simplified basis.

The remaining 38 invoiced units comprise eight rejected, 20 cancelled and ten not yet received. They have different reasons and may require different resolutions. Split the 38-unit variance by those reasons.

Microsoft's invoice-matching documentation describes matching invoice quantities to selected product receipts and prices to purchase-order information. The merchant still needs approved receipt semantics, tolerances and exception authority. A product receipt that includes restricted goods must not be assumed to mean all those goods are accepted for every payment decision. Microsoft invoice matching.

The example does not prescribe an automatic ₹20,200 payment. Finance must apply the approved commercial and accounting policy, including how partial invoices, disputes and supporting documents are handled. Automation can assemble the evidence and route the difference.

If the receipt is corrected after finance has used it, notify the affected workflow and preserve the earlier version. Silently changing a quantity beneath an approved invoice makes a later reconciliation harder.

Configure the state model before adding scanning

A first implementation can use the existing ERP if it preserves the quantities, revisions and unresolved cases. Repair closure rules and exception ownership before introducing another system.

Scanning is useful when item selection or repeated manual entry causes errors. It still needs correct units, stable event identities and a recovery process. An integration becomes justified when receiving, purchasing and AP cannot reliably share the relevant evidence.

Scope the pilot around one supplier group and representative partial deliveries. Include a damaged receipt, a cancelled balance, a replacement, a correction and a repeated upload. Keep automated posting permissions bounded to the approved workflow.

Ask the team to demonstrate these acceptance conditions:

1. The original example reconciles to 202 accepted, eight rejected, 20 cancelled and ten still expected.
2. The original ten-unit balance has a named owner and remains visible.
3. The eight-unit remedy retains its physical and commercial evidence.
4. Replaying either receipt produces no additional accepted stock.
5. A substitute item requires an authorised identity decision.
6. A closure action cannot erase unresolved delivery or claim work.
7. AP can reconstruct the receipt version used for its decision.

Measure the age and reason of unresolved balances, unexplained quantity differences and time spent reconstructing receipts. Close obligations before clearing them from the open-order report.

Close an obligation with an explanation

A partial purchase order is ready for closure when the relevant supply obligation has a supported outcome. Receiving, supplier remedies and financial documents may reach that point at different times.

1. Reconcile one partial delivery using actual received, accepted, rejected and cancelled quantities.
2. Separate the undelivered balance from the rejected-goods remedy.
3. Assign owners and evidence requirements for both.
4. Test replacement, correction and duplicate-receipt handling.
5. Agree how document closure preserves any remaining linked case.