Inventory Transfer Reconciliation

A central warehouse ships 100 units to a branch, which counts 96. The four-unit difference might be in a second box, damaged, miscounted or lost, and simply changing the branch balance to 100 conceals the question.

Record a transfer ID, shipment ID, item, source, destination, quantity and dates, and follow the physical movement, because one transfer may have multiple shipments. Shopify's transfer-shipment guidance distinguishes in-transit, partially received and received states, and notes that accepted and rejected quantities can affect location availability differently, so system configuration still needs checking.

Oracle NetSuite's transfer-order receiving guidance describes receiving quantities against a transfer order, and a receipt should be supported by physical count and condition, not just the shipment document. An illustrative unit reconciliation is source-dispatched units minus destination-accepted units minus documented in-transit, rejected or damaged units, so if 100 dispatch, 96 accept and 4 are confirmed damaged, the unexplained difference is zero.

Do not use a zero unexplained number to claim no loss, because the four damaged units still have a financial and operational consequence and the reconciliation merely explains their state. Track timing, since a shipment may leave Friday and arrive Monday, and a same-day location comparison needs an in-transit account or status instead of declaring missing stock.

Compare serials or lots when needed, as a total count of 96 can conceal the wrong 96 units arriving, which matters for warranty, expiry or recall. Handle rejected goods, since the destination may reject a box for damage and the source and destination systems should agree whether it is returning, quarantined or written off.

Check partial receipts, because if two trucks carry one transfer, closing the entire order after the first can leave the remaining shipment untracked. Preserve proof such as the packing list, carrier record, receiving scan and photos, since a manual note without source IDs is harder to audit.

Investigate both ends, because a source pick error, carrier issue or destination count mistake are all plausible, and one site should not automatically be charged for every difference. Set an ageing threshold for unresolved transit, since a parcel in transit for weeks after an expected arrival should be escalated even if the accounting bridge still balances, and keep the case open when the carrier has not confirmed the physical location, because an unexplained transit balance is a tracked risk, not a final answer.

Reconcile value as well as units, as different unit costs, currencies or intercompany treatment can create financial differences after the physical count matches, and a shipment crossing an accounting period should reconcile to the in-transit or intercompany records used by finance. Keep customer-available stock accurate so that goods in transit are not promised from both locations, review transfers caused by returns or repair, which may need a different condition status, and check system integrations, because a handheld receipt scan can fail to sync and leave a false gap.

Use patterns to improve packing, since repeated short receipts for one product or route may signal poor carton labelling or handling, and close with a documented outcome such as a corrected count, traced second shipment, carrier claim or write-off, each with an owner. For an owner, transfer reconciliation keeps one company's stock consistent across sites and shows what moved, where it is now and which differences still need investigation.