Stock Reconciliation — Count Sheets

Sheet 1 of 3 — Blind count sheet (counter fills this in; system quantities are NOT shown here)

Date:  
Batch / session:  
Counted by:  
#SKU / ItemInventory status / count scopeCounting unit Locations countedCounted qtyCount completed (time)Initials
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

Blind rule: the counter never sees the system quantity. Lock each counted quantity and its completion time before comparing with the system. Inventory status: use one line per SKU per status — e.g. “sellable”, “damaged — held aside”, “returns — awaiting inspection”. Never fold damaged or returned units into the sellable quantity, and never merge different statuses into one counted line to split later. Convert cases/cartons to units first and write the conversion in “Counting unit” (e.g., “case → 3 × 12 = 36 units”).

Stock Reconciliation — Count Sheets

Sheet 2 of 3 — Movement log (documented movements for counted SKUs while counting)

Date:  
Batch / session:  
#TimeSKU / ItemFrom (location / status)To (location / status) Movement typeQty (+ in, − out)ReferenceInitialed by
1
2
3
4
5
6
7
8
9
10
11
12
13
14

What goes in this log — and what does not. Log only documented movements that actually happened during the count window, with from → to and a reference (receipt, sale slip, transfer note) where available. Damage (or any status difference) discovered during the count that predates the snapshot is an observation, not a movement: note it on Sheet 1’s status line and let the variance show — do not enter it here as an automatic outbound, which would hide the variance or count it twice. A status change that actually happened and is documented during the window (e.g. breakage at 9:30) is a movement: log it as two legs — outbound from sellable, inbound to damaged — so each status line stays reconcilable. No double counting: for internal transfers and status changes inside the scope, the two legs cancel in the SKU-total movement; each leg belongs to its own status line. Never add both legs to the total as if they were separate movements.

Stock Reconciliation — Count Sheets

Sheet 3 of 3 — Comparison, review & adjustment (filled in after the blind count, from Sheets 1–2; one row per SKU per status)

Date:  
Reviewed by:  
Formulas — per SKU per status. Net movement = sum of Sheet-2 quantities for this SKU and status between snapshot time and count completion (inbound +, outbound −).   Adjusted counted = Counted qty − Net movement.   Unit variance = Adjusted counted − System qty at snapshot (same status).   Value variance = Unit variance × recorded unit cost (cost, not selling price).
#SKU / ItemInventory status / count scopeSnapshot time System qty @ snapshotCount completedCounted qty Net movement (snap→count)Adjusted counted Unit varianceUnit cost
1
2
3
4
5
6
7
8
9
10
11
12
13
14

Every counted quantity needs a system balance and a net movement for the same status and scope. Compare each quantity against the system balance that covers that status: sellable vs. system sellable; damaged vs. the system’s damaged/write-off bucket (where it exists); returns recorded with their status. If your system has no separate balance for a status, do not treat it as zero: record that status line as N/A, keep the detailed count, and compare only the SKU total against a system balance covering the same scope. Never create a variance or an adjustment for a status the system cannot balance on its own. A return is not automatically unsellable — record its status and compare accordingly.

Stock Reconciliation — Count Sheets

Sheet 3 (continued) — Review & adjustment gate (one row per SKU per status)

Date:  
Approved by:  
#SKU / ItemInventory status / count scopeValue variance Reason codeBalance before → afterAdjusted byNotes (movements checked, documents, subsequent activity)
1
2
3
4
5
6
7
8
9
10
11
12
13
14

Adjustment gate (do not skip). Before any balance change: (1) blind-recount the SKU on any variance, per the shop’s recount policy below; (2) check movements and documents since the last count, plus any subsequent movements, late postings, and prior corrections after the snapshot; (3) record balance before → after, the reason code, who adjusted, and who approved. The computed variance is historical (as of the snapshot) — never set the current balance back to an old snapshot or old counted quantity. Use your system’s inventory-adjustment function with a reason; do not re-enter sales or receipts as new transactions.

Shop policies (owner-set, written here). Recount policy — default (proposed): blind-recount the SKU on any variance. Adopted policy if different: _______________________. Threshold (if any): _______________. Balance-adjustment approval authority (separate policy): _______________________.