The Shipper's Manifest reported this morning on what happens in the gap between goods arriving and the invoice for them arriving, including a general rate increase taking effect today. Its point, in Keep the Receiving Record Before the Invoice Arrives, is that the receiving record is made at the dock, before any invoice exists, and it is the only thing the invoice can later be compared against. Here is what that looks like on one dock.
The operation in this walkthrough is illustrative, built to reflect a typical small or mid-sized distributor: Harlowe Pump & Seal, a 52-person industrial pump and seal distributor with a 31,000 square foot building and about 70 inbound purchase orders a month. The workflow and the arithmetic are real. The company and its vendor, Stratton Creek Bearing, are not.
Two deliveries, one purchase order
The purchase order is for 90 stainless seal housings at $78 a unit, an order total of $7,020. Stratton Creek Bearing ships it in two deliveries.
The first arrives with 50 units and nothing wrong. The receiver records it on the purchase order line: 50 received, 40 outstanding, and that receipt stays in the history.
Nine days later the remaining 40 units arrive. One carton is visibly crushed, and 6 units inside are unsellable.
Two documents, two relationships
Before signing, the receiver writes the exception on the delivery receipt: one carton crushed, contents damaged. That is the carrier's document, and it governs the carrier claim. A clean signature would have foreclosed the claim.
The receiver does not sign against the purchase order. That is the contract with the vendor, and it governs a vendor chargeback.
On the second receipt the receiver records 34 good units and 6 damaged, as a damaged split with a reason, rather than shelving all 40 as good stock. The 34 post to inventory with a bin location (for example B2-A05-SA-R01-L02-P03-BN01) and a reason-coded movement record. The 6 damaged are held.
The invoice arrives, and it is correct
Eleven days after the first delivery, the vendor's invoice arrives for the full $7,020.
- Invoiced: 90 units at $78 = $7,020
- Received: 50 plus 40 = 90 units at $78 = $7,020, so the invoice matches
- Of those 90, 84 posted as available stock ($6,552) and 6 are held as a damaged split
- Held: 6 units at $78 = $468, which is 6.7 percent of the order
The invoice is right and it reconciles clean, because everything ordered did arrive. The vendor shipped all 90 units. The carrier damaged 6 in transit. So the $468 was never an invoice problem. It is the size of a carrier claim, carried by two things: the exception on the delivery receipt before the signature, and the damaged split that keeps those 6 units out of available stock.
Why the reason matters as much as the count
Suppose the receiver had called those 6 units short instead of damaged. The line would read 84 received of 90 ordered, the purchase order would close short at 84, and the reconciliation would then flag the invoice as billing for the 6 units that never arrived. That points an overbilling finding, and a dispute, at a vendor that shipped everything it was asked to ship. At the same moment, with no exception on the delivery receipt, the signature would already have closed the only recovery that actually existed.
One wrong reason code manufactures a false finding against the vendor and destroys the real claim against the carrier. The quantity was right either way. The reason is what made the later check come out right. Nothing here promises the $468 comes back; it shows which path it can even travel.
How the product keeps that record
LanePilot is a TMS and WMS in one system for small and mid-sized manufacturers, distributors and warehouses. This runs in Warehouse Essentials or the 37-day free trial. One purchase order can be received across several deliveries: "Receive remaining" opens a new receipt on the same line rather than rewriting the first. Over, short and damaged each need a reason at check-in.
Invoice reconciliation on the Purchase Orders page compares the vendor's invoice amount against what was received, at each line's own unit cost, and treats a match within plus or minus 5 percent as clean. Here the $7,020 invoice equals the $7,020 received, so it falls inside the rule. It is a total-level comparison, and posting takes a second confirmation stating the amounts.
The vendor chargeback letter, drafted from a receiving discrepancy, is part of LanePilot Warehouse, and is the wrong tool here because the vendor owes nothing. You file any carrier claim. LanePilot prepares the paperwork; it does not contact your carrier or your vendor on your behalf.
Run this on your own dock
One. Ask where a receiver writes an exception. Anywhere but the delivery receipt, before the signature, and the claim is gone.
Two. Pull a recent damaged receipt and check whether the reason code says damaged, not short.
A damaged-unit rate of zero usually means nobody is writing anything down.
Ready to try it? See Warehouse receiving or create a free account, no credit card needed.
The operation described is illustrative. Purchase order and receiving records are demonstration data.