Warehouse & Inventory · SOP
Inventory Cycle Counting & ERP Reconciliation
A standardized procedure for performing cycle counts, investigating discrepancies, and reconciling physical inventory quantities with your ERP system to maintain data integrity and inventory accuracy.
Estimated Time
45 min
Difficulty
Intermediate
Regulation
GAAP / IFRS
Version
1.0
Purpose
This SOP establishes a consistent, auditable method for performing daily cycle counts of warehouse inventory, identifying and investigating quantity variances, and reconciling physical stock with ERP system records. The goal is to maintain a systemwide inventory accuracy of ≥98% and ensure that all adjustments are traceable, approved, and properly documented for financial compliance.
Scope
This procedure applies to all raw materials, work-in-progress (WIP), finished goods, and MRO consumables stored in the primary warehouse, satellite storage areas, and overflow staging zones. It covers ABC-classified SKUs on a rotating cycle count schedule, as well as ad-hoc full physical inventories and year-end audit counts. Excluded are hazardous waste, damaged goods held for disposal, and customer-owned consignment stock.
Safety Precautions
- Wear CSA-approved steel-toe boots, hi-vis vest, and safety glasses at all times in warehouse aisles. Gloves required when handling pallets or sharp-edged packaging.
- Before counting in any racking aisle, confirm all powered industrial trucks (forklifts, order pickers) in that zone are locked out or the aisle is barricaded. No truck travel allowed in an active count aisle.
- Use a ladder or elevating platform to reach top-beam stock. Never climb rack uprights or stand on pallet overhangs. Maximum reach height without a ladder is 1.5 m (5 ft).
- If you discover leaking, damaged, or contaminated inventory during counting, stop immediately, isolate the area, and notify the safety supervisor. Do not handle spilled chemicals without proper PPE and spill kit training.
Required Tools & Materials
- Cycle count sheet (ERP-generated) or handheld scanner / tablet with cycle count module
- Clipboard, pen, and marker for manual tally backup
- Ladder — rolling warehouse ladder rated for 150 kg (330 lb)
- Handheld barcode scanner or mobile device with inventory app
- Variance investigation log template (paper or digital)
- Personal protective equipment (PPE) — safety glasses, hi-vis vest, steel-toe boots, gloves
- Red “Do Not Operate” tags and barrier tape for active count aisles
- SupplyGrid inventory tracking dashboard (optional — for live PO generation and Kanban monitoring)
Procedure: Step-by-Step
1
Prepare counting materials and lock down system transactions. Generate a cycle count report from your ERP — include SKU, bin location, expected quantity, and unit of measure. Place a transaction hold on the designated count zone: freeze all receipts, transfers, and picking activities in that area for the duration of the count. Print physical count sheets or load the count batch into your handheld scanner.
2
Perform physical count per bin location. Travel to each bin listed in the count report. Count every unit of each SKU present — do not rely on partial tallies or visual estimates. Record the actual quantity on the count sheet or scan into the handheld. If a SKU is not in its expected location, search adjacent bins and staging areas before marking it as missing. Note any damaged, expired, or mislabelled units in the comments field.
3
Enter actual counts and flag variances. Input physical count quantities into the ERP cycle count module. The system compares actual vs. expected and calculates the variance. Flag every SKU where the variance exceeds ±2 units or ±5% of the expected quantity (whichever is greater). Lock those lines in the ERP so they are not automatically adjusted — they require supervisor investigation and approval.
4
Investigate flagged discrepancies. For each flagged SKU: (a) re-count the physical stock in the bin and any nearby locations, (b) review the last 48–72 hours of transaction history in the ERP — look for mis-picks, unrecorded transfers, receipt errors, or data entry mistakes, (c) verify unit of measure conversions (e.g., pieces vs. boxes vs. pallets), (d) inspect for signs of theft or damage. Document the root cause in the ERP notes field. If a second count confirms the variance, proceed to adjustment.
5
Adjust ERP inventory balances. For confirmed discrepancies, initiate an inventory adjustment transaction in the ERP. Select the appropriate reason code (miscount, system error, damage, mispick, theft). For adjustment values exceeding $250 (standard cost basis), obtain supervisor digital approval before posting. The adjustment must zero out the variance by writing off the shortage or adding the overage to the ERP balance.
6
Reconcile and close the cycle count batch. Run the ERP cycle count reconciliation report. Verify that every SKU in the batch now has a net variance of zero. Confirm that all adjustments have been posted to the general ledger inventory valuation accounts. Close the count batch in the ERP system — this locks the batch from further edits and makes it available for audit review.
7
Document and review process metrics. Log the following KPIs for the completed count: count accuracy % (number of SKUs with zero variance ÷ total counted), total adjustment dollar value, and top three root causes by frequency. Share a summary with the warehouse team during the next shift huddle. Adjust the cycle count frequency for any SKU family that shows a recurring error rate > 10% — that SKU should move to a higher count frequency tier.