Warehouse Receiving Discrepancy Closure Lag

Start the clock when a warehouse worker confirms a mismatch between goods received and the expected shipment, not when purchasing first sees a later invoice difference, and keep that earlier physical discovery timestamp even if the system case opens later. Use one clock rule for all cases, such as calendar hours from physical discovery to approved warehouse disposition, and if supplier response time is excluded, disclose the paused interval and publish gross elapsed time as a companion figure.

Tie the finding to a receipt, supplier, order line and handling unit, since a short shipment, overage, wrong item and damaged carton need different corrective paths, even if all appeared at the same dock. Define closure as a documented disposition and any required inventory correction, not merely a changed ticket status, and show a case with a pending supplier credit or unresolved quarantine separately if financial closure is outside this metric.

Microsoft's warehouse guidance distinguishes receiving-complete status from later product-receipt processing and lets configured workflows accept or reject quantity exceptions, so check the local configuration before treating a system milestone as final closure. Oracle's receive-by-ASN flow shows how planned shipment data can drive the receipt, but an ASN helps identify an expected line without replacing scanning or inspecting the actual cartons on the floor.

Compare the recorded received quantity with both the purchase order and the supplier's packing document, which can disagree with one another, since the physical count cannot be inferred from either planned number. Confirm units of measure, because a purchase order for cases and a receipt entered in eaches may create a large apparent variance without any missing physical stock.

For a short receipt, confirm that the missing units were not unloaded to another dock or posted under a second load, then record whether the supplier will reship, issue credit or dispute the count. For an overage, establish whether it belongs to the same order and whether accepting it is permitted under the commercial terms, and do not make surplus goods available for sale merely by entering a convenient receipt quantity.

Keep quality status independent from quantity reconciliation, since a damaged case can be physically received but held from use while the discrepancy investigation decides which party bears the cost. Retain photographs, seal condition and carrier handover notes when damage or shortage could have occurred in transit, preserving the original files and discovery time instead of replacing them with a cleaned-up case narrative.

If the supplier disputes the difference, record both observations and the evidence still needed, because a denial is not automatically a warehouse closure and a supplier's acceptance is not proof inventory was corrected. Close a shortage only after the stock balance reflects what arrived and the outstanding demand is addressed, while an expected reshipment can remain open as a separate follow-up without overstating today's inventory.

When the correction changes financial value, route the accounting entry through its own authorisation, since the warehouse disposition tells finance what happened without silently granting approval to change a payable. Sample closed cases against the original scan, disposition approval, final bin or return proof and case timestamps.

This tests whether the clock and closure evidence agree rather than trusting a dashboard flag.