An inter-branch stock transfer does not end when the source branch records a dispatch. The item may have left the source branch while the destination branch has not yet recorded a receipt. If that gap is not reviewed, the destination may request more stock that is already in transit, while the source branch continues to show a reduced balance for a transfer that has not been completed operationally.
OrderTechERP brings sales, orders, inventory, accounting, reporting, and branches into one operating space. By reviewing transfer records alongside their receiving status, teams can move from a vague question such as “Where is the stock?” to a defined next step: what was sent, what was received, and what needs to be verified now? The usefulness of the result depends on data quality, company configuration, and the permissions available to each team member.
Define the transfer gap first
For this review, a transfer gap is a mismatch between the inventory movement and the transfer status. Start with transfers that indicate stock was dispatched or left the source branch but do not show a documented receipt at the destination.
Before building the review list, agree on what each status means in your operating process. The company may use stages such as draft, approved, dispatched, received, or cancelled, and their names and sequence may vary with the organization’s configuration. Do not treat a status as proof of a physical movement unless that meaning is established in the company’s procedures and system setup.
- Set the branches and date range covered by the review.
- Separate cancelled or unapproved transfers from those that were actually dispatched.
- Compare transferred quantities with received quantities when partial receipts are recorded.
- Confirm that each record has a transfer reference, dispatch date, source branch, and destination branch.
Turn the list into a verification priority
Unreceived transfers do not all require the same response. The objective is not simply to work through records in date order, but to prioritize cases according to operational impact and the likelihood of a process or data issue.
| Review signal | What it may indicate | First action |
|---|---|---|
| Dispatched with no receipt | A mismatch between source movement and destination status | Contact both branches and confirm the shipment’s location and record |
| A long time since dispatch | Delayed documentation or a transport issue | Confirm the expected arrival date and whether receipt occurred outside the system |
| Operationally significant quantity | Potential impact on availability, orders, and balances | Place the transfer ahead of lower-impact cases |
| The same pattern between two branches | A possible weakness in the shared process or data entry | Review how responsibilities and statuses are recorded |
An inventory manager can create a daily or periodic review list using the fields available in the company’s setup, then record why each transfer was prioritized. This turns a set of records into an actionable queue that can be assigned and followed up rather than a report that is merely read.
Connect the movement to an operational question
Use the same sequence of questions for every unreceived transfer. Was the quantity deducted from the source branch? Did the shipment physically arrive? Did the destination check the quantity and condition? Is the receipt missing, or is there an actual discrepancy between what was sent and what arrived? Are open orders at the destination relying on this stock?
- Review the transfer record: Confirm the transfer reference, items, quantities, branches, and recorded dispatch status or date.
- Verify with the source branch: Confirm that the stock was prepared and dispatched, and that the physical quantity matched the recorded quantity.
- Verify with the destination branch: Ask whether the shipment arrived, count the items, note any shortage or damage, and confirm how receipt should be recorded.
- Compare with current demand: Review orders, sales, and availability before arranging another replenishment. A second request may simply result from an unclear shipment status.
- Record the next step: Assign an owner and follow-up date, and state whether the case needs a status update, discrepancy handling, or more information.
Do not adjust stock just because a gap appears
A dispatched but unreceived transfer is not, by itself, enough evidence to add stock to the destination balance or return it to the source balance. Adjusting stock before verification can create an artificial quantity or conceal a real shortage. Keep three facts distinct: the stock leaving the source, its physical arrival, and the receipt being recorded in the system.
If the destination confirms arrival, record the receipt according to the company’s process and user permissions. If the quantity differs, document the difference before making any correction. If the shipment has not arrived, follow the responsible transport or internal process without assuming an undocumented cause. If the receipt was handled outside the system, update the record only through a method allowed by the company configuration and capable of preserving an appropriate audit trail.
Give each team a clear role
This review works best when sales, inventory, accounting, reporting, and branch teams use the same operational picture. Inventory explains how the transfer affects availability. The two branches provide evidence about preparation, arrival, and receipt. Sales should consider transfer status carefully when responding to demand. Accounting and reporting teams need consistent movement data before interpreting balances or variances.
OrderTechERP’s AI operational assistant can connect order and data context to a next operational step according to the company’s configuration and team permissions. That guidance does not replace human verification or create permissions that are not available. Its usefulness depends on the information recorded and on how the organization has configured its working process.
A practical conclusion
A sound review of unreceived transfers starts with a reliable list, separates dispatch from receipt, prioritizes cases by age and operational impact, and assigns verification to the two branches involved. Only then should the team decide whether to update a status, handle a discrepancy, or continue replenishment. This structure reduces manual searching, improves shared visibility across branches, and helps prevent duplicate requests and unsupported balance adjustments. The quality of the outcome still depends on accurate input, clear company procedures, and appropriate data access and permissions.

