Keep intersite transfers visible while material is in transit
Compare approaches
TL;DR — what you’ll learn
- Record dispatch and destination receipt as separate events linked by one transfer reference.
- Keep dispatched material visible in transit until the destination confirms its quantity and condition.
- Reconcile shortages, overages and damage explicitly instead of forcing the destination receipt to match dispatch.
- Apply finance and tax treatment according to the entity and transaction facts; this article's example assumes an internal transfer within one entity.
Twelve tonnes leave Site A on 30 September. Site B receives 11.8 tonnes on 2 October. At month-end, the material is neither physically at the source nor yet acknowledged at the destination. After receipt, another 0.2 tonnes still needs explanation.
An intersite transfer process should preserve both facts. If dispatch immediately increases destination stock, Site B appears to hold material it has not received. If the source simply removes the quantity with no transit record, the material disappears from operational visibility during the journey.
- 0130 September dispatch
- 12.0 t in transit
- Source stock reduces; destination has not acknowledged arrival.
- 02Month-end cutoff
- 12.0 t still in transit
- Preserve dispatch evidence and expected arrival.
- 032 October receipt
- 11.8 t received
- Record actual quantity and separate condition status.
- 04Residual
- 0.2 t unresolved
- Investigate measurement, partial delivery or loss evidence.
Illustrative internal movement within one entity. Quantity positions do not prescribe accounting or tax treatment.
Read the visual as text
30 September dispatch: 12.0 t in transit. Source stock reduces; destination has not acknowledged arrival.. Month-end cutoff: 12.0 t still in transit. Preserve dispatch evidence and expected arrival.. 2 October receipt: 11.8 t received. Record actual quantity and separate condition status.. Residual: 0.2 t unresolved. Investigate measurement, partial delivery or loss evidence..
Original explanatory visual: NextEdge Labs. Illustrative records, not client results.
- STEP 01Authorise and identify movement
Owner: Source + receiving site
Confirm entity boundary, need and item identity.
- STEP 02Dispatch into transit
Owner: Source stores + logistics
Record actual quantity and transport evidence.
- STEP 03Acknowledge actual receipt
Owner: Destination stores
Record date, quantity, condition and discrepancies.
- STEP 04Resolve the remaining balance
Owner: Logistics + finance
Approve corrections or other supported outcomes.
Close the transfer with both-end evidence.
Keep the residual assigned and visible; do not force receipt to match dispatch.
Return path: Return to transport and measurement review, then post the supported resolution.
Read the workflow as text
1. Authorise and identify movement (Source + receiving site) → 2. Dispatch into transit (Source stores + logistics) → 3. Acknowledge actual receipt (Destination stores) → 4. Resolve the remaining balance (Logistics + finance). After step 3, ask: Does receipt plus authorised discrepancy treatment reconcile to dispatch? Yes: Close the transfer with both-end evidence. No: Keep the residual assigned and visible; do not force receipt to match dispatch. Return: Return to transport and measurement review, then post the supported resolution.
Workflow: NextEdge Labs. Apply the project’s actual authority and procedures.
Establish the transfer boundary
Identify the sending and receiving sites, legal entity, item, specification, unit of measure, quantity and reason for transfer. Confirm that the receiving site needs the material and can accept it. Link the request or allocation decision so the source does not release stock still required for its own work.
This article uses an internal movement within one legal entity, with unchanged ownership assumed for the example. Intercompany movements, sales, tax documentation and movements across jurisdictions require the relevant finance and tax review. A stock transfer reference alone does not settle those questions.
For controlled or tagged items, carry the serial, batch, certificate or asset identity into the transfer. The receiving site should not have to rebuild traceability from a delivery note that lists only a generic description.
Use two acknowledgements and one connecting reference
The source confirms what was dispatched, when it left and which transport evidence supports the movement. The destination confirms what actually arrived, when it arrived and its condition. Both records should point to the same transfer reference and line identities.
ERPNext documents a transit warehouse approach in which one entry moves stock into transit and a subsequent entry completes the destination transfer. That is one implementation pattern; the important control is preserving an open balance between the two events.
Record the expected arrival date and follow-up owner. Transit should be a monitored location or status, not a permanent parking area for unresolved stock. The logistics team needs a list of overdue transfers with shipment evidence and the last confirmed update.
Follow the twelve-tonne movement across month-end
For the worked transfer, Site A dispatches an illustrative 12.0 tonnes on 30 September. No receipt is confirmed by the reporting cutoff. The operational position is a 12.0-tonne reduction at Site A and 12.0 tonnes in transit. Site B has not yet received an available-stock increase.
On 2 October, Site B measures 11.8 tonnes. The receipt records that actual quantity, subject to its inspection status. A residual 0.2 tonnes remains associated with the transfer while the discrepancy is investigated.
Scroll horizontally to see all columns.
| Event | Source movement | Transit position | Destination receipt |
|---|---|---|---|
| Dispatch on 30 September | −12.0 t | 12.0 t | 0.0 t |
| Month-end before receipt | No further movement | 12.0 t | 0.0 t |
| Receipt on 2 October | No further movement | 0.2 t unresolved | 11.8 t |
The table shows quantity movement, not a prescribed accounting journal. Finance should determine valuation and period treatment under the applicable policy. The operational evidence gives finance a defensible basis for that decision.
Investigate the residual before clearing it
The 0.2-tonne difference could reflect measurement methods, a partial delivery, handling loss, an incorrect dispatch quantity or another cause. Compare weighbridge records, units, tare treatment, vehicle details and any intermediate handling evidence before concluding what happened.
If part of the shipment is still travelling, keep that portion open with its expected arrival. If the dispatch record was wrong, correct it through an authorised process. If a loss is confirmed, record the approved disposition and any separate recovery or claim action. Do not clear the residual by increasing the receipt to the expected quantity.
Set a practical tolerance policy with the responsible technical, commercial and finance owners where measurement uncertainty is relevant. A tolerance may determine review or approval requirements; it should not erase the measured difference or imply that every difference within the limit is physically explained.
Keep condition separate from arrival
All 11.8 tonnes may arrive physically while some portion remains held for inspection or damage review. Record the destination receipt and the condition split separately. A transit balance should not remain open merely because material has arrived but is awaiting local acceptance, unless the system's clearly defined status model requires that representation.
The receiving team should preserve photographs, packaging condition and carrier observations when damage is found. Link the resulting inspection or nonconformance record to the transfer. Logistics closure and quality closure may happen at different times.
Return movements need their own evidence. If Site B sends material back, do not silently reverse the original dispatch and pretend the outward journey never happened. Record the return transfer and retain the relationship between the two movements.
Reconcile the reporting cutoff from both ends
At month-end, compare source dispatch records with destination receipts and the transit register. Identify receipts entered after cutoff for material that physically arrived before it, and dispatch entries posted late. Preserve physical event dates and entry dates so finance can assess the correct period.
Ask both sites to confirm open transfers. A source-only review may miss a receipt that the destination recorded under the wrong reference. A destination-only review may miss a shipment still in transit. Reconciliation should also catch duplicate receipts and transfers cancelled before dispatch.
For valuation, use the agreed policy and consistent item units. Do not combine quantity reconciliation with an unexplained change in transfer value. Price or cost adjustments should have their own reason and approval trail.
Test partial deliveries and failed journeys
A useful acceptance test dispatches ten units and receives six, then four on a later date. The transfer should remain open for four after the first receipt and close only after the second, without duplicating the source reduction.
Also test a shipment returned to the source before reaching the destination, a destination change during transit and a damaged partial receipt. The records should explain where the material is at each stage and who owns the next action.
Make transit a visible stock position
The transfer is complete when the dispatched quantity is reconciled to destination receipts and authorised discrepancy outcomes. Until then, someone should be able to locate the evidence and the unresolved balance.
- Confirm the transfer scope, entity boundary and receiving need.
- Link dispatch and receipt through one stable reference.
- Monitor open transit quantities and expected arrival dates.
- Investigate residuals using actual transport and measurement evidence.
- Reconcile both sites and transit at the reporting cutoff.
Compare this workflow with your current setup
Share the step that takes the most manual work, the systems involved and the exceptions your team handles. That gives us a concrete starting point for comparing approaches.
References and further reading
Sources checked 15 October 2026. The worked examples and diagrams are original editorial explanations, not client results.
- ERPNext documentation — Stock EntryStock Entry purposes and Add to Transit subsection
Product movement examples.
Visual credits
Original explanatory visuals and workflow diagrams by NextEdge Labs. Labels and text equivalents are included in the page. Numerical scenarios are illustrative; diagrams preserve the project owner’s approval and exception decisions.