Reconcile an inventory transfer by linking the source shipment, the quantity still in transit, and each destination receipt to the same transfer line. At a common cutoff, shipped quantity should be explained by recorded receipts, outstanding transit, and supported corrections. Keep units unavailable at the destination until the receiving and release rules say they can be used.
A truck can arrive with only part of a shipment while both warehouses show records that look complete. The useful question is which units moved, where they were recorded, and what remains unresolved (including goods held at the receiving site). A transfer total without those states cannot tell purchasing whether another order is needed.
Choose a transfer method that preserves the journey
Microsoft’s Business Central transfer documentation distinguishes transfer orders from direct reclassification. Transfer orders can separate shipment and receipt using an in-transit location. Its direct-transfer settings have different partial-posting behavior, so verify the selected method before using one procedure for every movement.
Use the operating system’s supported workflow for your route. If shipment and receipt occur at different times, preserve a state for that interval. Do not make a moving pallet available in both warehouses merely because the reporting system has received two extracts with different refresh times.
Set the report’s scope too. A movement between bins within one warehouse may use a different document from a transfer between warehouses. Transfers between legal entities can introduce ownership, tax, or intercompany requirements that a physical stock reconciliation does not settle. Have the responsible owners choose that treatment before combining the records.
Match the dispatch to its source stock
Carry the transfer ID and line, item, base unit, source and destination, shipped quantity, and shipment event. Retain lot or serial identity where the item requires it. A transfer of ten cases is ambiguous until the case size is known; preserve both the entered quantity and the conversion used for the base-unit balance.
Confirm what the status means before aggregating it. A requested transfer quantity is planned work, while a posted shipment records departure under the system’s rules. If a report counts both, one physical movement can appear twice. Keep order quantity, shipped quantity, and canceled quantity in separate fields with their original references.
Microsoft’s Dynamics 365 inventory posting documentation shows source, transit, and destination inventory transactions for a transfer order. That example illustrates why several ledger rows can describe one shipment. Count the business movement once while preserving the rows needed to reconcile each location.
Reconcile a partial delivery without inventing a loss
Assume a hypothetical item starts with 200 units at warehouse A and 50 at warehouse B. A ships 60 units to B. At the cutoff, B has received 54, including four placed on a damage hold. B’s starting 50 units are released and unreserved. No other receipts, issues, losses, or corrections have occurred, and all quantities use the same base unit.
| Location or state | Calculation | Closing quantity |
|---|---|---|
| Warehouse A | 200 minus 60 shipped | 140 |
| Warehouse B, total received stock | 50 plus 54 received | 104 |
| In transit, still unresolved | 60 shipped minus 54 received | 6 |
| All included locations | 140 plus 104 plus 6 | 250 |
The included stock still totals 250 units. B’s 104 units contain four held units, leaving 100 usable under this example’s release policy. The six-unit transit balance is unresolved movement, not proof of a loss. Investigate whether the balance reflects another package, an unposted receipt, a counting error, or a supported correction.
Retain the four held units in B’s physical stock while showing their blocked status. If a return or write-off is later approved, link the resulting transaction to the original receipt. Removing held units from the location balance before that decision would mix condition with ownership and make the reconciliation fail.
Posted departure
Shipped, not yet received
Received and release status
Investigate the unmatched side before correcting stock
Compare the transfer line’s event history with carrier and warehouse records. A physical arrival without a posted receipt belongs with receiving; a shipment posted twice belongs with the authorized transaction owner. Capture the cause and evidence before applying a correction, then rerun the same cutoff so a repair does not conceal another difference.
Check both dates when sources support backdated posting. A movement can have a physical date and an entry timestamp, and yesterday’s location balance may change after a late receipt is entered. Preserve the original extract and label any restated view. Use inventory reconciliation when the recorded movements no longer explain the shelf count.
Keep transfer availability separate from customer commitments. Received stock may still be held, reserved, or in an unusable location. The inventory allocation process handles which demand receives eligible stock; transfer completion alone does not authorize a second allocation.
How Permute joins the two warehouses’ records
Permute sells connected business data, custom applications, and governed analysis. We can connect permitted NetSuite transactions and Excel receiving logs, then match transfer lines under declared item, location, and document mappings. Records without a reliable match remain exceptions for review.
We apply your definitions of shipped, received, held, and outstanding to the same reporting cutoff. An inventory manager can inspect the source references behind a residual transit quantity and see which destination receipts support it. Keep the approved correction trail available alongside the result so a later rerun can explain a changed balance.
Match one transfer across its records
Connect a permitted transfer extract and receiving log to inspect their shared document references.
Keep transfer posting and disposition with authorized owners
We do not verify truck contents, choose accounting treatments, or decide whether unresolved stock is lost. Warehouse and finance owners approve physical and financial corrections in the relevant operating systems. Confirm the source fields, permissions, and refresh schedule before relying on a cross-warehouse view for active fulfillment.
Close the movement when each quantity has an explanation
An inventory transfer needs a linked shipment and receipt history at a common cutoff. Keep the residual in transit until another supported event explains it. Preserve held quantities within the destination balance while separating their availability. Correct the underlying records through an authorized workflow and retain the evidence that changed the result.
Review unresolved transfers between warehouses
Bring source shipments and destination receipts to discuss a recurring view of unmatched quantities.
Questions about transfers between warehouses
Can company-wide net stock hide a transfer problem?
Yes. Equal and opposite errors can leave a total unchanged while putting stock in the wrong locations. Reconcile each transfer line and location as well as the combined total; usable stock still depends on its recorded location and status.
Can a shipped transfer be undone?
Use the supported correction process for the configured system. Microsoft documents undoing a Business Central transfer shipment before receipt, with corrective lines. Once the destination has received stock, verify the applicable reversal or return procedure instead of reusing an earlier-stage action.
Does this method cover intercompany accounting?
It explains physical stock movements within a declared scope. Transfers between legal entities may require separate documents, valuation, or tax treatment chosen by the responsible finance owners. A quantity reconciliation cannot establish those treatments or replace statutory consolidation.