The month-end risk: A pallet can be on the move while your records say it is somewhere else. A disciplined transfer process keeps warehouse counts, inventory value, and financial records aligned.
A transfer request is not the same as a posted transfer
In conversation, teams sometimes use “transfer request” and “transfer order” interchangeably. That can blur an important distinction. In SAP Business One, the key operational difference is between the Inventory Transfer Request and the Inventory Transfer.
- Inventory Transfer Request: Records the planned movement. It can help coordinate the request and availability between warehouses, but it does not by itself move on-hand stock or create the completed inventory movement.
- Inventory Transfer: Records the actual movement between warehouses. When posted, it updates inventory quantities. In a perpetual inventory setup, it also creates the related accounting posting.
A request is intent. A posted transfer is the record of action.
That distinction matters when someone checks a report and assumes a request means goods have already moved. The request may be open, waiting for fulfillment, or only partly completed. The physical movement and the system record need to meet in the posted transfer.
For more on warehouse processes in SAP Business One, see SAP’s warehouse management learning material.

Why an unposted transfer makes the stock report a lie
A report is only useful when the underlying transactions match the warehouse reality.
Suppose goods physically leave Warehouse A, but the Inventory Transfer is not posted. Depending on how the team tracks the movement, SAP Business One may continue to show the stock at the source location, while Warehouse B’s available quantity remains unchanged. Operations may plan against stock that is no longer there, or purchasing may replenish stock the business already owns.
If your team has a designated in-transit warehouse, the risk shifts rather than disappears. The goods may be recorded as having left the source, but if the receipt into the destination is never posted, the in-transit balance can remain open long after the shipment arrived.
Either way, the report stops describing the whole journey. It describes only the last completed transaction.
A practical process needs one owner for each handoff: dispatch confirms the departure, and receiving confirms arrival. If nobody owns the second step, “in transit” becomes a parking lot for unresolved inventory.

Give in-transit stock a clear home
If your operation needs to track goods between locations, a common approach is to use a designated in-transit warehouse and record the movement in two posted legs:
- Transfer the goods from the source warehouse to the in-transit warehouse when they leave.
- Transfer the goods from the in-transit warehouse to the destination warehouse when they arrive.
This gives the goods a recorded location during the journey and creates a clear receiving step. It also gives the team a place to investigate when the expected arrival date passes.
The setup and accounting treatment should be reviewed with your SAP Business One partner and finance team. In a perpetual inventory environment, confirm that the appropriate inventory accounts are configured and that the resulting journal entries match your accounting policy. The SAP perpetual inventory guide explains inventory accounting considerations, including goods movements.
The operational rule is straightforward: do not let “it shipped” stand in for “it arrived and was recorded.”
The three-check discipline for month-end
Before closing the period, run the same three checks for transfers that are open, recently completed, or past their expected arrival.
1. Check the in-transit date
For every in-transit balance, ask: When did it leave, and when was it expected to arrive?
Use a defined expected-arrival date and review exceptions. A transfer that has been in transit longer than planned should trigger a follow-up with the shipping or receiving team, not a quiet roll-forward into next month.
2. Confirm the receiving document is posted
A delivery confirmation, email, or verbal update is useful evidence. It is not a substitute for the receiving transaction in the system.
Check whether the transfer from in-transit to destination has been created and posted. If it has not, identify who will complete it and what evidence they need. If the goods arrived in partial shipments, make sure the recorded quantities reflect what was actually received.
3. Verify the journal reflects both legs
Where perpetual inventory applies, compare the inventory movement and its accounting effect. With a two-leg in-transit process, confirm the source-to-transit and transit-to-destination movements are both represented, using the accounts approved for your setup.
A warehouse quantity can look right while an accounting entry is missing, misdirected, or sitting in the wrong period. Finance and operations should be able to trace the movement together.
Date. Document. Journal. These checks turn a vague month-end discrepancy into a specific follow-up.
Protect cycle counts from transfer noise
An open transfer can make a cycle count look like a counting problem when the real issue is timing.
If the source warehouse has picked the goods but the system still lists them there, a counter may report a shortage. If receiving has put the goods away but the receipt has not been posted, the destination may report an overage. Then the team spends time researching adjustments that a properly completed transfer would have prevented.
Before a count, agree on a simple cutoff:
- Pause or tightly control transfers in the count area.
- Record goods that have physically moved but are awaiting a system transaction.
- Confirm which warehouse owns the count at the cutoff time.
- Complete or clearly flag transfers before posting count adjustments.
That is especially important for high-volume distributors and manufacturers moving components, finished goods, or stock between facilities. A count is a snapshot. Transfers are motion. The process must account for both.
Make the handoff boring, in the best way
The strongest transfer process is not complicated. It makes the next action unmistakable.
The requester initiates the move. Dispatch records what actually leaves. Receiving records what actually arrives. Finance verifies the value follows the movement. Each handoff has a person responsible, a document to complete, and a date to review.
At month-end, that discipline pays off in fewer surprises and more dependable reports. We help manufacturing and distribution teams examine where their processes break down and how SAP Business One can support clearer operations. Explore Quaint’s SAP Business One resources or book a conversation with David.
A transfer is not complete when the truck leaves. It is complete when the records tell the same story as the warehouse.
Frequently asked questions
Does an Inventory Transfer Request move stock in SAP Business One?
No. A request records planned movement and can affect committed or ordered quantities, but it does not by itself post the physical inventory movement. The Inventory Transfer is the document used to record the movement.
How do we track stock while it is traveling between warehouses?
A common approach is to use a designated in-transit warehouse, then post one transfer when goods leave and another when they arrive. Review the design and accounting treatment with your SAP Business One partner and finance team.
What should we check when an in-transit balance is still open at month-end?
Check the departure and expected-arrival dates, confirm whether the receiving document has been posted, and verify that the related journal entries reflect the movement according to your setup.
Can a transfer create a cycle-count variance?
Yes. If goods move physically before the system records the transfer, or the receiving step is left open, source and destination counts may not match the recorded quantities. Clear transfer cutoffs and timely posting help reduce that mismatch.





