Inventory Audit Procedures

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

1. Document Control Block

• Document ID: TR-OPS-IA-009
• Effective Date: October 24, 2023
• Version: 4.2.0
• Review Cadence: Quarterly (or upon major WMS architecture updates)
• Target Audience: Warehouse Operations, Inventory Control Specialists, Finance Audit Committee, Logistics Leads

2. Executive Summary & Scope

This SOP establishes the mandatory methodology for conducting physical inventory audits within Template Registry facilities. The scope covers all high-value assets, raw materials, and finished goods tracked within the Enterprise Resource Planning (ERP) environment. The objective is to achieve a >99.8% inventory accuracy rate while maintaining compliance with Sarbanes-Oxley (SOX) reporting standards and internal fiscal governance protocols.

3. Prerequisites & Tool Requirements

• Software Access: ERP/WMS Read-Write access with elevated "Audit" permissions.
• Hardware: Handheld RFID scanners (Class-1 Gen-2 compliant), tablet-based audit interface, label thermal printers.
• Safety PPE: ANSI-rated steel-toe footwear, high-visibility vest, and hard hat (if auditing high-bay racking).
• Certifications: Completion of "Inventory Control Compliance Training" (Module 102).

4. Roles & Responsibilities (RACI Matrix)

5. Step-by-Step Operational Procedure

Phase I: Preparation & Lockdown

• Freeze all inventory movements (Inbound/Outbound) for the specified zone.
• Perform a full system sync between WMS and ERP to ensure data parity.
• Distribute unique electronic Audit ID packets to the floor team.

Phase II: Execution (The Count)

• Initiate "Blind Count" mode in the WMS software.
• Scan location barcodes followed by SKU-level item tags sequentially.
• Flag "Variance Items" (where physical count ≠ system record) for secondary verification.
• Document damaged, expired, or non-conforming items using the "Condition Flag" digital form.

Phase III: Reconciliation

• Review system-calculated variances vs. physical audit data.
• Conduct a recount for all items exceeding a 0.5% variance threshold.
• Submit final variance reports to the Operations Manager for digital signature.

6. Quality Assurance & Verification Criteria

• Audit Threshold: Zero variance tolerance for Class-A items (High value/critical demand).
• Acceptance Benchmark: 99.8% unit-level accuracy; 100% location accuracy.
• Verification Check: The Finance Controller must perform a "Spot-Check" on 5% of audited locations post-completion to validate the audit team's integrity.
• Sign-off: All reports must be digitally archived with time-stamped validation.

7. Practical Troubleshooting Scenarios

Scenario 1: System/Scanner Connectivity Drop

• Problem: Handheld scanner loses connection to the WMS, halting data entry.
• Corrective Action: Switch to "Offline Batch Mode" on the device. Resume scanning. Once connection is restored, initiate "Sync Pending Data" via the WMS dashboard. Report the uptime interruption to the IT/SysAdmin desk for log review.

Scenario 2: Unidentified Inventory (Ghost Stock)

• Problem: Item found on shelf with no corresponding SKU in the WMS.
• Corrective Action: Place item in the "Quarantine Zone." Assign a temporary "Pending Identification" (PI) tag. Notify the Procurement Lead to trace the ASN (Advanced Shipping Notice) and resolve the source of the unrecorded asset.

Scenario 3: Significant Variance (>5%)

• Problem: Large discrepancy between physical count and WMS data for a specific location.
• Corrective Action: Immediately trigger a "Root Cause Investigation" (RCI) ticket. Audit the last 72 hours of transaction history for that specific SKU. If the discrepancy persists after investigation, initiate an "Inventory Adjustment" in the ERP requiring secondary authorization from the Controller.

Authorized By: Julian Vance Chief Operations Architect, Template Registry