Inventory Audit Checklist Template

Standard Operating Procedure: Inventory Audit Protocol (IAP-009)

1. Document Control Block

• Document ID: TR-OPS-IA-2024-009
• Effective Date: October 26, 2024
• Version: 2.1.0
• Review Cadence: Quarterly (Q1-Q4)
• Target Audience: Operations Managers, Warehouse Supervisors, Audit Personnel, Finance Department

---

2. Executive Summary & Scope

This SOP defines the standardized methodology for conducting institutional-grade physical inventory audits at Template Registry facilities. The objective is to achieve a >99.8% inventory accuracy rate by reconciling physical stock against the Enterprise Resource Planning (ERP) ledger. This protocol applies to all raw materials, Work-in-Progress (WIP), and finished goods. It adheres to GAAP (Generally Accepted Accounting Principles) requirements for internal inventory valuation and audit trail transparency.

---

3. Prerequisites & Tool Requirements

• Digital Access: Read/Write credentials for the Corporate ERP/WMS (Warehouse Management System).
• Hardware: Handheld RFID/Barcode scanner (calibrated), tablet/mobile terminal, thermal label printer.
• PPE: Steel-toed boots, high-visibility vest, and hard hat (if in automated storage/retrieval zones).
• Documentation: Current snapshot of the Perpetual Inventory Record (PIR).
• Safety Clearance: Site-specific Lock-Out/Tag-Out (LOTO) training certification.

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Operational Procedure

Phase I: Preparation & Reconciliation Lock

• Freeze all inbound/outbound logistics activity for the designated zone.
• Export the ERP system stock snapshot to generate the "Control Sheet."
• Verify battery levels and network connectivity for all scanning hardware.
• Assign discrete audit zones to personnel to prevent overlapping counts.

Phase II: Physical Verification (Cycle Count)

• Perform Blind Count: Auditor performs physical tally without viewing ERP expected values.
• Verify UOM (Unit of Measure) parity (e.g., eaches vs. cases vs. pallets).
• Inspect physical condition/shelf-life status of items (Flag expired or damaged units).
• Scan and tag items confirmed as "Unallocated" or "Orphaned" inventory.

Phase III: Data Consolidation & Variance Analysis

• Upload scan data to the centralized registry.
• Execute automated reconciliation script to identify variances >0.
• Perform secondary "Recount" on all items showing a variance exceeding the threshold.
• Generate Variance Report for reconciliation with Finance.

---

6. Quality Assurance & Verification Criteria

• Accuracy Threshold: >99.8% (Units scanned vs. Units in ERP).
• Variance Tolerance: +/- 0% for high-value assets (Class A); +/- 0.5% for consumables (Class C).
• Audit Acceptance: Completion of the "Variance Resolution Log" signed by both the Auditor and the Warehouse Supervisor.
• Reporting Frequency: Variance reports must be submitted within 24 hours of audit completion.

---

7. Practical Troubleshooting Scenarios

Scenario A: Ghost Inventory (ERP shows stock; physical shelf empty)

• Protocol:
  1. Check "Pending Transactions" in the WMS to see if items were moved but not confirmed.
  2. Check adjacent bins for mis-shelved items.
  3. If not found within 1 hour, trigger an "Immediate Adjustment Request" to remove the item from the system and initiate a loss-investigation file.

Scenario B: Data Sync Failure (Handheld scanner loses connectivity)

• Protocol:
  1. Cease current counting operation immediately.
  2. Switch to offline/batch mode if the hardware supports it, or utilize paper-based backup logs.
  3. Do not resume system entry until the IT Infrastructure lead provides a "Connection Restored" confirmation and validates that the last 50 scans were successfully cached.

Scenario C: Unlabeled/Damaged Goods

• Protocol:
  1. Quarantine all unidentified items in a dedicated "Pending Identification" zone.
  2. Take digital photograph of the item and label/packaging.
  3. Cross-reference the item against the "Damaged Stock Report" to see if it was previously processed.
  4. Re-label only after Procurement validates the SKU via serial number/batch code.

---

Approved by: Julian Vance, Chief Operations Architect, Template Registry.