Stock Transfer Form Template for Internal Moves

A transfer can leave one store today and reach another in several arrivals. A signed dispatch note proves neither that every item arrived nor that the destination made it available for use. One “complete” checkbox hides those differences.

This stock transfer form template is complete inline: copy the blocks and tables into a document or spreadsheet. It covers ordinary consumable supplies moving between locations within one organization. The formulas, review targets and approval rules are a proposed operating design, not universal inventory or accounting requirements. There is no download or account requirement.

Use a transfer record for movement between stock locations

Use this resource when both the sending and receiving locations hold stock and someone must reconcile what moved. For a job requesting supplies from stores, use a material requisition form. For an individually assigned laptop or tool changing custodian, use an asset handover form.

The CRS dispatching and receiving goods manual describes comparing physical deliveries with shipment documents and investigating differences using records from both warehouses. That operational principle informs this resource; the template below is an independent general-business design, not the CRS procedure.

Exclude hazardous, temperature-controlled, regulated or safety-critical goods unless the responsible specialist supplies the necessary controls. Intercompany sales, cross-border transfers, stock valuation and tax treatment need separate procedures.

Copy the transfer authorization

Create one transfer ID for one source–destination pair. A different destination needs a separate linked transfer. Use stable text IDs, not spreadsheet row numbers.

Template version: ST-1
Transfer ID: [unique, never reused]
Requested at: [date/time and time zone]
Requester and contact: [name/team/contact]
Source site and store: [approved location code]
Destination site and store: [approved location code]
Reason / linked job: [purpose and reference]
Required arrival by: [date/time and zone]
Transfer coordinator: [person accountable for open work]
Source release approver: [authorized person/role]
Destination receiving lead: [person/role and contact]
Approval: [pending / revise / approved / rejected]
Approved version and evidence: [version, approver, time, reference]
Expected receipt review target: [locally chosen elapsed time]
Exception escalation owner: [named role/person]
Current status: [use rules below]
Next action / owner / due at: [required while open]
Closeout: [reviewer, time, evidence references]

The requester completes the purpose and locations. The coordinator validates contacts and a realistic arrival plan. The source approver confirms release authority and the approved version before dispatch. Approval does not itself reserve stock. Record any reservation separately in the authoritative stock system.

Authorized item lines

Require all fields except lot/serial where genuinely inapplicable and closeout until finished. Dates need a time zone; quantities must be nonnegative, with whole numbers for indivisible units. A rejected line has zero approval plus a reason. Unknown identity, unit or authority blocks dispatch.

Record each dispatch and each arrival separately

One transfer may have multiple dispatches. One dispatch may have multiple arrivals. Keep those identities distinct so a later receipt does not overwrite the first count.

Dispatch event: complete at physical release

Dispatch ID | Transfer ID | Line ID | Approved version
Item / unit / lot | Source bin | Destination receiving point
Actual dispatched quantity D | Actual release time and zone
Released by | Carrier/handler and contact | Shipment/container reference
Condition and count evidence | Expected arrival at
Source stock transaction reference | Recorded by / recorded at

Use one row per line and dispatch, with D greater than zero. The source lead checks cumulative dispatches plus K do not exceed A. Record the actual release count, not the planned pick. Retain dispatch evidence and the source stock transaction reference. A planned shipment is not a completed dispatch.

Receipt event: complete at each physical arrival

Receipt ID | Dispatch ID | Transfer ID | Line ID
Actual arrival time and zone | Receiver | Destination receiving point
Item / unit / lot verified | Counted quantity C
Initially accepted a | Initially held h | Initially rejected r
Condition and count evidence | Accepted / held / rejected locations
Decision reviewer | Decision reference and time
Destination stock transaction reference, or pending exception
Recorded by / recorded at

For each receipt, require C = a + h + r. C includes physically counted goods that are held or rejected. A blank decision is unknown; do not assume all counted stock was accepted. Wrong items need their actual identities and a mismatch exception, not relabeling to fit the transfer.

Later inspection decisions use a linked decision event: Decision ID | Receipt ID | quantity | hold-to-accepted or hold-to-rejected | reason/evidence | reviewer | timestamp | resulting location | stock reference. Reduce the remaining hold by that quantity and increase the chosen outcome equally. Do not record another arrival for goods already present.

Reconcile quantities without hiding the difference

Calculate these balances per dispatch line, using valid linked receipt events. Never offset a shortage on one item, lot or dispatch against a surplus on another.

• Received Ctotal = sum of its receipt counts.
• Not yet received S = max(D − Ctotal, 0).
• Excess E = max(Ctotal − D, 0).
• Held H = initial held quantities minus valid later hold decisions.
• Open to dispatch O = A − sum(D) − K, calculated at the authorized transfer-line level.

S is an unresolved physical difference, not automatically a loss. Expected arrival determines when it becomes late. E is a discrepancy, not permission to increase destination available stock. H is physically present but awaiting a decision; do not include it again in S.

Copy the exception and closeout record

Exception ID | Transfer / line / dispatch / receipt references
Type: [short / excess / damaged / wrong item / late / missing evidence / correction]
Observed quantity and unit | Facts and supporting evidence
Current physical location or last confirmed handler
Action owner | Next action | Due timestamp and zone
Resolution: [additional arrival / approved loss / verified correction /
             approved excess disposition / hold decision / return / other explained]
Authorization | Completion evidence | Stock-record references
Resolved by / resolved at | Coordinator verification

The coordinator assigns an owner immediately when an exception is recorded. Set the due time from your local response policy, arrival plan and any applicable notice deadline. At that time, unresolved work is overdue and escalates to the named escalation owner; it never becomes accepted by age alone.

For a genuine missing quantity, record an authorized loss disposition with quantity and stock-system evidence. S remains the historical not-received amount; show the approved settled quantity separately. For excess, verify the source count and dispatch association, then document the authorized physical disposition and both locations’ stock-record treatment. Do not invent an arrival or silently edit D to force agreement.

A correction needs the original event ID, old and corrected values, reason, evidence, approver and time. Retain the original record and recalculate from the approved corrected event set. A physical return is a new linked reverse movement with its own dispatch and receipt evidence, not deletion of the first arrival.

Worked example: two dispatches, three arrivals and a hold

This fictional example uses 24 identical filter packs, all in units of packs. Transfer ST-024 moves them from Central store to North store. A is 24 and K is zero. Maya coordinates; Sam releases stock; Lee receives it; Jo reviews condition.

Maya closes only after checking both dispatches, all receipt/decision records and source/destination transaction references. Until DC-1, the first dispatch is not ready for closeout even though all 20 packs are physically present.

Two separate edge tests: if DS-1 instead received 21 packs, E would be 1 and closeout would require an excess resolution. If the final four packs had never left Central, an approved cancellation K=4 would make O=0; it could not cancel two packs missing after dispatch.

Use statuses that show the remaining work

1. Needs correction: identity, authority, counts or references are unresolved. Coordinator returns the record to the responsible owner.
2. Approved, awaiting dispatch: release is authorized and O is positive; source lead owns the next dispatch or approved cancellation.
3. In transit / partial receipt: a dispatch has S greater than zero with no completed settlement. Coordinator follows the expected arrival.
4. Exception open: a hold, excess, rejected-goods disposition, late arrival or evidence gap needs action. Show all applicable flags, not only one status.
5. Ready to reconcile: O=0; every physical difference is resolved or explicitly settled; H=0; rejected goods have completed disposition.
6. Closed: coordinator verifies all linked events, decisions, physical dispositions and both stock-record references, then records closeout evidence.

A missing field or exception takes priority over a calculated “ready” result. Approval, a carrier signature or a destination acknowledgment alone cannot close the transfer. Keep review ownership and the next due timestamp visible while open.

Where Workhint fits in the transfer handoff

A shared document can run this process initially. Workhint’s Workflow Engine describes routing approvals by role and requiring details or files before work advances. Its workflow automation software page describes structured forms and tracking stages, owners and next actions. Those capabilities are relevant to coordinating source release, destination review and exception ownership.

Keep the inventory system authoritative. These descriptions do not establish stock reservation, barcode scanning, automatic quantity reconciliation, inventory costing or stock-ledger posting. The record and formulas here are a proposed process design, not a claim that Workhint provides a prebuilt warehouse-transfer module. Confirm any integration separately.

Frequently asked questions

Is this a goods received note?

No. This record links an internal source dispatch to destination arrivals. A supplier receiving note normally references purchasing documents. Keep those purposes separate even when they share count and condition fields.

Can one dispatch have several receipts?

Yes. Give every actual arrival a unique receipt ID linked to the same dispatch line. Sum the counts, but retain each arrival’s time, receiver and condition decisions.

Does receiving stock mean it is available to use?

Not necessarily. Held and rejected goods are physically present but not accepted. Record their locations and decision owners separately, and follow your stock system’s own availability rules.

Can I use the template without spreadsheet formulas?

Yes. Copy the fields into a shared document and calculate the stated balances manually. Before live use, walk through a split arrival, a hold release, an excess and a canceled unshipped remainder. Confirm every case has an owner and a valid closeout path.