Reconcile inter-warehouse transfers when receipt is partial

The origin confirms a transfer of 120 cartons. The destination accepts 110, holds five damaged cartons and cannot locate five. Closing the transfer at 110 makes ten cartons disappear from the explanation. Receiving all 120 into available stock invents a position the warehouse cannot use.

Build a transfer bridge that accounts for every dispatched unit: accepted at destination, received but held, still in transit or unresolved. The operational record must distinguish physical custody from accounting ownership and commercial responsibility.

Agree the transfer boundary

Record the origin, destination, owner, item, packaging unit, lot where applicable, handling units and transfer line identity. A transfer number can contain several lines and several journeys. Match receipts to the dispatched line or unit, not only the header.

Define what constitutes dispatch: a completed issue transaction, physical gate departure or another agreed event. Keep those events separately when both exist. Similarly, arrival at the destination gate is not the same as counted receipt or approved availability.

The example below uses an operational transit balance beginning at confirmed physical dispatch and ending at recorded destination custody. Finance's ownership and valuation treatment may use different rules and needs its own documented mapping.

Microsoft's external-ERP integration guidance is relevant when warehouse and financial systems consume different receipt or inventory events. Agree one interpretation per interface and reconcile acknowledgements. Microsoft Dynamics 365 — Integrating warehouse management with an external ERP

Account for a partial receipt

The following figures are illustrative, with no other movements affecting this transfer. Origin starts with 200 cartons and dispatches 120. Destination has no opening stock for this item in the example.

Origin custody is 200 − 120 = eighty. Destination custody is 110 + 5 = 115. Five remain unresolved in the transfer bridge. The five damaged cartons are not still in transit because the destination has observed them.

The bridge reconciles quantity, but it does not prove that the missing five are physically in a truck. Label them “unlocated transfer quantity” while the investigation is open. A transit ledger is a record of unresolved movement, not a GPS observation.

Later, three identified cartons arrive from a hub. Destination custody becomes 118 and unresolved quantity falls to two. Keep the late receipt linked to the original transfer line. Do not create a new purchase receipt simply to clear a transfer exception.

Separate a physical finding from a settlement decision

If the damage reviewer releases four of the five held cartons and retains one, availability becomes 117: the original 110, three late arrivals and four releases. Destination custody remains 118, with one held. Releasing stock is a status movement, not another receipt.

The remaining two unlocated cartons may be found, returned to origin or become an approved loss adjustment after investigation. Each outcome needs evidence and its own transaction. A transfer automatically closed after a set number of days would hide the unresolved decision.

If a carrier accepts a claim, that commercial acknowledgement does not change the physical quantity. Finance records the recovery separately. If the origin shipped the wrong item, a quantity bridge by total cartons may still balance while the item-level records fail.

Use the handling units to investigate

Match origin loading records, carrier acknowledgements, hub scans and destination counts. Where the pallet was split, follow child-unit identities and quantities; do not require every destination carton to retain the original pallet label.

GS1 EPCIS supplies artefacts for standardised visibility-event exchange. Partner support and event meaning must be agreed before treating a shared event stream as a complete custody history. GS1 — EPCIS and CBV artefacts

Keep event time and receipt time separate. A late destination message can make a transfer appear open after the physical receipt was completed. Reconciliation should distinguish an operational shortage from an interface delay.

Make duplicate and out-of-order receipts harmless

A destination may send a first receipt of 115 cartons and a later cumulative receipt of 118. Adding both would produce 233. Specify whether messages contain increments, cumulative snapshots or document states.

For incremental messages, use stable event identities and deduplicate committed outcomes. For cumulative messages, compare versions and calculate an approved delta against the previously applied state. A late older snapshot must not restore the earlier balance.

If only part of a multi-line transfer posts successfully, retain line-level outcomes. Replaying the whole transfer without checking destination references can duplicate the successful lines.

Close with an explained bridge

A manual transfer register can work when volumes are small and both sites maintain prompt transactions. Native transfer orders help preserve the relationship; an integration is useful when the sites run different systems. Whichever approach is used, test partial receipt, damage hold, late arrival, duplicate acknowledgement and return to origin.

Measure aged unresolved quantities and their reasons. Separate known transit from unlocated stock and message failures. A transfer-completion percentage can improve artificially if unresolved lines are closed by adjustment, so review the closure reasons and approval evidence.

For a transfer-reconciliation assessment, start with one lane and the exact dispatch and receipt events used by each system. The first useful result is a bridge both sites can explain.

Every dispatched unit needs a current explanation

The transfer is complete when all quantities have a supported destination or authorised resolution. A reconciled bridge lets the operation continue without erasing damage or uncertainty.

Next actions

1. Agree the dispatch, receipt and availability boundaries.
2. Reconcile one partial transfer at line and handling-unit level.
3. Assign owners to held, late and unlocated quantities.
4. Test cumulative updates and partial posting failures before automating closure.