redbeam.comhs-fshubfsRedBeam_Logo-1
redbeam.comhs-fshubfsRedBeam_Logo-1

Inventory Audit: Steps, Methods, and Frequency Guide

Summary • 22 minutes read
Inventory audits fail when the method doesn't match the operation and discrepancies get adjusted instead of investigated. This guide covers the six audit methods, a seven-step process, how often to count, what to do when the numbers don't match, and how barcode and RFID cut count time without shutting down operations

Your team finishes the count and compares it to the system. There are mismatches you can't explain. Nobody knows if it's a receiving error, a data-entry mistake, or something that walked out the door. So you adjust the numbers, close the count, and move on. Then the next audit turns up the same gaps. Financial records stay messy, shrinkage keeps climbing, and every count feels like starting over.

That cycle breaks when you match your inventory audit method and schedule to how your operation actually runs. The right method at the right frequency cuts shrinkage and reduces time off the floor. A clear process for investigating discrepancies keeps your records clean year-round. Here's how to choose what fits your operation and what to do when the numbers don't add up.

Main Takeaways

  • Six audit methods exist. The right one depends on inventory size, item value, and how much disruption you can absorb.
  • Audit frequency should follow business type, inventory velocity, and compliance requirements.
  • Cutoff controls must halt or document all receiving, shipping, transfers, and returns during the count window to prevent phantom variances.
  • Every discrepancy needs a documented root cause before you adjust records. Otherwise the same gap will surface next audit.
  • Most operations use internal teams for ongoing cycle counts and external auditors for the annual count that feeds financial statements.

Build an Annual Count That Actually Works

Annual counts go sideways when planning, staffing, and documentation aren't locked in before count day. This guide covers the best practices that keep your process tight and your records clean.

Read the Annual Inventory Guide

Inventory Audit Methods: 6 Types and When to Use Each

Six core audit procedures exist for inventory. Each one balances coverage depth against the time your team spends off the floor. The right choice depends on inventory size, item value, and how much disruption you can absorb. Here's what each method does and where it fits.

Physical Inventory Count

A physical inventory count is a wall-to-wall count of every item in your facility, matched line by line against recorded quantities. It's the most complete method and the most disruptive. Use it for year-end fiscal close and regulatory requirements. Default to it when your records have drifted too far to trust partial counts.

Cycle Counting and ABC Analysis

Cycle counting means counting a rotating subset of inventory on a set schedule so you never shut down for a full count. It spreads the audit workload across the year, and accuracy stays high without cramming the effort into one painful window. Use it in high-velocity warehouses and operations that can't afford multi-day shutdowns.

ABC analysis is a ranking layer on top of cycle counting that assigns count frequency by item value. A items (the small share of SKUs that represent most of your inventory value) get counted most often. C items get counted least. The 80/20 logic is simple: protect the dollars that matter most. Use it alongside cycle counting to build toward continuous accuracy.

Sampling, Spot Checks, and Blind Counts

Sampling means counting a representative subset and estimating accuracy across the full inventory. Use it for very large inventories where counting everything isn't practical, or as a mid-year confidence check between scheduled audits.

Spot checks are unscheduled counts of specific items, triggered by a discrepancy, a customer complaint, or a loss-prevention flag. Use them to investigate suspected shrinkage or verify high-risk items between scheduled counts.

Blind counts hide the expected quantity from the counter, so the count isn't biased by what the system says should be there. Use them any time you need an independent accuracy check, especially when shrinkage or data-entry errors are suspected.

Why the Right Audit Method Matters More Than Auditing More Often

Matching your method to your operation drives better outcomes than sticking with an annual wall-to-wall count. The right approach reflects how your inventory actually moves. It helps keep records accurate and shrinkage under control. It also supports smarter purchasing and cleaner financial reporting.

This is also a resource decision. Inventory management is the most-cited bottleneck in fulfillment and distribution operations, and 73% of companies say they can't find enough labor to staff them, according to the 2024 Warehouse Outlook and Trends report from Kardex and Peerless Research Group. The wrong method wastes floor time you don't have. The right one gives you reliable data without shutting down.

How to Audit Inventory in 7 Steps

A reliable inventory audit follows seven steps. First set the scope and schedule and freeze inventory movement. Then prepare documentation, count, verify, reconcile, and adjust. Each step closes a specific gap where mismatches typically hide.

Step 1: Set the Scope and Schedule

Define what you're counting: full inventory, specific zones, or high-value items. Pick your method and assign ownership for each area. Set the date and share it with every team that touches inventory. That typically includes receiving, shipping, production, and returns. Surprises on count day come from teams that didn't know the count was happening.

Step 2: Freeze Inventory Movement (Cutoff Controls)

Cutoff control means halting or carefully documenting all receiving, shipping, transfers, and returns during the count window. Without it, items that arrive or leave mid-count create phantom variances that look like real problems. Returns are a major variance driver. U.S. retailers expected 16.9% of 2024 sales, or $890 billion in merchandise, to come back as returns, according to NRF. Return-to-stock items that hit the shelf during a count window will throw off your numbers, so document them. Cutoff controls also apply to inter-facility transfers and production-floor movements. Any transaction that changes item location or status during the count must be paused or logged.

Step 3: Prepare Count Documentation

Print or load count sheets. Confirm scanners are charged and synced. Assign zones to counters and set blind-count settings if needed. Pre-count prep is where most teams save or lose time on count day. Skipping it means your counters spend the first hour fixing equipment instead of counting.

Step 4: Count

Count in assigned zones using the method you chose in Step 1. Counters record quantity, location, and condition for every item, and they scan or log each one as they go rather than tallying from memory. Two-person teams work best for high-value zones: one counts, one records. Move through each zone in one direction so nothing gets counted twice or skipped. Don't stop to investigate variances yet. That's Step 5, and mixing the two slows both down.

Step 5: Verify and Recount Exceptions

Compare initial counts against system records. Any item with a variance above your threshold gets a second, independent recount. Flag items with condition issues (think damaged or obsolete stock) separately. Those need valuation review, not just quantity correction.

Step 6: Reconcile Records

Reconciliation means matching your verified physical counts to the quantities and values in your enterprise resource planning (ERP) or inventory management system. Middleware bridges the two by translating raw count data into clean updates. Then you identify every variance. Document each discrepancy with the item and location. Record the expected quantity, actual quantity, and dollar impact before making any adjustments. This documentation separates a useful audit from a number-shuffling exercise.

Step 7: Adjust and Document

Post approved adjustments to your system: write-ups, write-downs, reclassifications, and disposals. Record the reason code for every adjustment so your next audit has a trail to follow. A corrected number without a documented cause is just a guess that happens to match the shelf.

How Often Should You Audit Inventory?

Your audit frequency should follow three factors:

  1. Business type
  2. Inventory velocity
  3. Compliance requirements

A one-size-fits-all calendar wastes time in some operations and leaves gaps in others. Consider high-velocity operations like retail and ecommerce fulfillment. These need monthly or continuous cycle counts on fast-moving SKUs. Quarterly spot checks cover the rest. Manufacturing operations with a stable bill of materials are a different story. They can rely on quarterly cycle counts plus an annual wall-to-wall count.

State, local, and education (SLED) organizations follow a compliance-driven schedule regardless of velocity. Under 2 CFR 200.313, entities that hold federally funded equipment must run a physical inventory and reconcile the results at least once every two years. GASB 34 capital asset reporting adds its own documentation expectations on top of that.

The table below maps recommended audit activities by business type. Use it to build a schedule that fits your operation without over-counting or under-counting.

Factor

Manual (Pen & Paper / Spreadsheet)

Barcode Scanning

RFID Scanning

Speed

Slowest, manual recording takes roughly 70% longer than automated methods*

Moderate, scan one item at a time with line-of-sight necessary

Fastest, read hundreds of tags per second, no line-of-sight required

Accuracy

Lowest, prone to transposition, missed items, illegible entries

High, eliminates transcription errors

Highest, inventory accuracy improves to 98% to 99% with RFID**

Labor required

Highest, needs more counters and more time

Moderate, fewer counters, faster per item

Lowest, one person can scan an entire zone

Operational disruption

Highest, long count windows, more downtime

Moderate, shorter count windows

Lowest, counts can happen during normal operations

Upfront cost

Lowest, no hardware investment

Moderate, scanners + labels

Highest, readers + tags + infrastructure

Best fit

Very small inventories (< 200 items), one-time counts

Mid-size operations, mixed environments, budget-conscious teams

Large-scale, high-velocity, or compliance-heavy operations

 

What to Do When Counts Don't Match

Even with a routine audit schedule, sometimes, counts don't match. The variance itself isn't the problem. The root cause is. You need a step-by-step investigation process before you adjust anything. An unexplained adjustment today becomes an unexplained variance next quarter.

Common Root Causes of Inventory Discrepancies

  • Receiving errors. Items accepted but never scanned in, or scanned under the wrong SKU. Investigation: Pull receiving logs and purchase order (PO) records for the affected items. Compare timestamps against the count window.
  • Data-entry mistakes. Manual quantity adjustments, transposition errors, or duplicate entries. Investigation: Review adjustment history and user logs for items showing variances.
  • Shrinkage (theft or loss). Items missing with no matching transaction. Investigation: Correlate missing items with time windows, camera footage, and access records. Then coordinate with loss prevention.
  • Damaged or obsolete stock. Items physically present but no longer sellable or usable. Investigation: Inspect flagged items, confirm condition, and reclassify or write off.
  • System sync failures. Failed integrations or delayed updates cause inventory quantities to differ between systems. Investigation: Check integration logs and timestamp gaps. Verify whether transactions posted to the correct location.

How to Investigate Before You Adjust

Never adjust records to match the count without documenting the cause. Start with the largest variances by dollar impact and work down. Set a threshold below which variances are batched for review rather than investigated one by one. This keeps your team focused on the mismatches that actually move the needle.

Record every finding, including the cause, corrective action, and responsible party. That documentation gives internal leadership a clear picture of what went wrong. It also gives external auditors the evidence they need without weeks of back-and-forth.

Internal vs. External Auditor: How to Choose

An inventory auditor is the person or team responsible for planning, executing, and documenting your inventory count. They verify that physical quantities match recorded values and investigate any discrepancies. That role can be filled by internal staff or an outside firm. The right choice depends on cost, independence needs, and regulatory triggers.

Internal audits cost less and cause less disruption. Your team already knows the facility, the system, and the items. But internal teams carry built-in bias: they built the processes they're now evaluating. Internal auditors fit best for routine cycle counts and mid-year spot checks. They also work well for operations without public-company or federal compliance mandates.

External auditors provide independence and documentation that satisfies regulators and stakeholders. Public companies need them under the Sarbanes-Oxley Act (SOX), and auditing standards require the auditor to observe the count whenever inventory is material to the financial statements. SLED entities often need them under GASB 34 or 2 CFR 200. External auditors fit best for year-end financial audits and compliance-driven counts. They also make sense when stakeholders need independently verified numbers.

What an External Auditor Actually Tests

An external auditor doesn't count your inventory for you. They observe your count, run their own test counts on a sample, and then test the records behind it. Expect them to check five things: that the inventory exists, that all of it is recorded, that you own it, that it's valued correctly (including old or damaged stock), and that it's presented properly in the financials. They'll also test your cutoff documents, trace their test counts back to your inventory listing, and, if you rely on cycle counts instead of a full count, ask for evidence that your cycle count results are as reliable as a wall-to-wall count.

That last point is where audits most often fall short. The Public Company Accounting Oversight Board (PCAOB), which inspects the firms that audit public companies, flagged two recurring inventory problems in its March 2025 inspection report: auditors who never tested period-end inventory listings for accuracy and completeness, and auditors who never confirmed that cycle-count procedures were reliable enough to stand in for a full count. If your cycle counts feed your financial statements, your documentation needs to survive that scrutiny. Most operations use both kinds of auditor. Internal teams handle ongoing cycle counts and spot checks. External auditors validate the annual or every-two-year count that feeds financial statements.

Run Cycle Counts Without Shutting Down Operations

Cycle counting keeps records accurate year-round without the disruption of a full wall-to-wall count. See how RedBeam's inventory tracking handles receiving, issuing, adjusting, and audit reporting in one workflow.

Explore Inventory Tracking Software

 

Technology Options: Manual vs. Barcode vs. RFID Counting

Your counting technology shapes every audit outcome: speed, accuracy, labor cost, and disruption. Your inventory volume, budget, and accuracy targets should guide your choice. Your options include manual, barcode, and radio frequency identification (RFID) counting.

The table below compares all three. It covers the factors that matter most during an inventory audit. Use it to find the right fit for your operation instead of defaulting to the method you've always used.

Factor

Manual (Pen & Paper / Spreadsheet)

Barcode Scanning

RFID Scanning

Speed

Slowest, manual recording takes roughly 70% longer than automated methods*

Moderate, scan one item at a time with line-of-sight necessary

Fastest, read hundreds of tags per second, no line-of-sight required

Accuracy

Lowest, prone to transposition, missed items, illegible entries

High, eliminates transcription errors

Highest, inventory accuracy improves to 98% to 99% with RFID**

Labor required

Highest, needs more counters and more time

Moderate, fewer counters, faster per item

Lowest, one person can scan an entire zone

Operational disruption

Highest, long count windows, more downtime

Moderate, shorter count windows

Lowest, counts can happen during normal operations

Upfront cost

Lowest, no hardware investment

Moderate, scanners + labels

Highest, readers + tags + infrastructure

Best fit

Very small inventories (< 200 items), one-time counts

Mid-size operations, mixed environments, budget-conscious teams

Large-scale, high-velocity, or compliance-heavy operations

* Automated audit speed based on our customer data. ** RFID accuracy based on Murata ID Solutions use cases.

For cycle counts and audits, enterprise handhelds such as the Zebra MC3300 RFID series, or RFID sleds like the Zebra RFD40 and RFD90, let one person scan a full zone in minutes without touching a single item.

Signs point to heightened use of sensors and auto-ID technology. In the 2025 MHI Annual Industry Report, 88% of supply chain leaders said they expect to be using sensors and automatic identification within five years, up sharply from the prior year's report. Another 55% increased their supply chain technology budgets. Barcode and RFID aren't new. They're the direction most operations are heading. As an enterprise RFID solution provider, our middleware runs Zebra-first and supports both barcode and RFID workflows on one platform. We bridge Zebra hardware and your backend systems by filtering and normalizing raw tag data at the edge, so your team can start with barcode scanning and scale to RFID as volume or accuracy needs grow, without switching systems.

What an Inventory Audit Report Should Include

Your inventory audit report turns a physical count into an actionable record. It should document what you counted and what you found. It should also show what you adjusted and what still needs attention. A complete report includes:

  • Audit scope (locations, item categories, method used)
  • Date range of the count
  • Count team and responsibilities
  • Variance summary by item, location, and dollar impact
  • Discrepancy findings with root causes
  • Adjustments made, with reason codes and approval
  • Unresolved issues flagged for follow-up
  • Recommended next actions (process changes, schedule adjustments, technology upgrades)

Multiple teams need this report. Finance uses it for journal entries and financial statements. Operations uses it to fix broken processes. Compliance uses it as audit trail documentation. Leadership uses it for strategic decisions about inventory investment.

The report isn't a formality. It's the evidence your next audit starts from. Without documentation, next year's team inherits the same blind spots. They have to investigate the same problems all over again. Not to mention, a well-structured report also satisfies external auditor evidence requirements. That cuts weeks of back-and-forth during financial audits.

Inventory Auditing by Industry: Retail, Manufacturing, Logistics, and SLED

The audit process stays the same across industries. But the priorities, risk areas, and compliance requirements shift. Here's what to emphasize based on your operation.

Retail

Primary audit risks include shrinkage from theft, damage, and administrative error. High return volumes create receiving variances. Seasonal inventory spikes strain count accuracy. Ecommerce retailers face the same risks plus split shipments that create phantom availability across channels. Use blind counts for high-shrink categories. Tighten cutoff controls during peak return periods. Apply ABC-ranked cycle counts for high-value merchandise, fixtures, and store assets.

Manufacturing

Primary audit risks center on work-in-progress (WIP) tracking gaps and raw material consumption variances. Multi-stage production flows add complexity when items change form or location between counts. Only 16% of manufacturers have real-time visibility into production, according to Zebra's 2024 Manufacturing Vision Study. For everyone else, the audit is where those gaps surface. Use stage-gate counts at production transitions. Tighten cutoff controls around WIP. Place fixed RFID readers at key movement points, paired with enterprise middleware that filters the high-volume tag reads, to close visibility gaps between counts.

Transportation and Logistics

Primary audit risks include inventory in transit between nodes, multi-location sync failures, and high return-to-stock volume. Goods that left one facility but haven't been received at the next can get counted twice or not at all. Run continuous cycle counts synced across logistics locations. Include in-transit inventory in the count with transfer documentation. Reconcile shipped versus received quantities at every handoff, and add dedicated return-processing audits.

SLED (State, Local, and Education)

Primary audit risks include compliance failures under GASB 34 for capital asset reporting. Federal grant property management under 2 CFR 200 creates another compliance risk. Incomplete property records can also cause problems. So can assets that move between buildings without documentation. Together, these gaps make it harder to maintain an accurate record of public assets.

The 2024 Uniform Guidance raised the federal equipment threshold to $10,000. It kept the requirement for physical inventory and reconciliation at least every two years. Maintain auditable property records with all required fields. These include asset ID, serial number, location, condition, and funding source. Run physical counts every two years and document reconciliation to meet grant compliance.

 

Common Inventory Audit Challenges and How to Solve Them

Every audit program hits the same friction points. Each one has a specific fix rooted in the methods, steps, and tools covered throughout this guide.

  • Time burden. Audits pull staff off revenue-generating work. Fix: Use cycle counting to spread the workload across the year. Barcode or RFID scanning cuts count time per item.
  • Inconsistent counting. Different people count differently, producing unreliable data. Fix: Standardize count procedures with written instructions. Use blind counts to remove bias. Require two-person verification for high-value zones.
  • Weak internal controls. No segregation of duties, no approval workflow for adjustments. Fix: Separate the person who counts from the person who adjusts records. Require documented approval for every write-off or reclassification.
  • Obsolete or damaged stock. Items sit on shelves but aren't sellable or usable, inflating inventory value. Fix: Build condition assessment into every count. Flag items for write-down or disposal during the audit, not after.
  • Operational disruption. Wall-to-wall counts shut down receiving, shipping, or production. Fix: Shift to rolling cycle counts with targeted spot checks. Use technology that allows counting during normal operations.

Start Running Cleaner Inventory Audits

The right audit process makes accurate counts easier to maintain. Start with a method and schedule that fit your operation. Then investigate discrepancies instead of simply adjusting the numbers. That's how your team fixes the problems behind repeat errors. Over time, audits become a routine way to keep records clean and shrinkage under control.

We built our platform to turn the seven-step process into a repeatable workflow your team can run without pulling people off the floor for days. You get faster, more accurate counts with barcode or RFID. Documented audit trails satisfy internal leadership and external auditors alike. Cycle-count workflows keep records clean year-round without shutting down operations. That's Tracking Made Easy™.

See how our barcode and RFID inventory tracking cuts audit time and ends the manual scramble.

Cut Count Time with Barcode and RFID Workflows

Manual counts drain floor time. Even worse, they leave room for transcription errors that compound audit after audit. RedBeam gives your team faster, more accurate counts with a documented trail. Satisfy both internal leadership and external auditors.

Schedule a Demo

 

FAQs About Inventory Audits

Is an inventory audit required?

For public companies, yes, when inventory is material to the financial statements. An independent auditor must observe the physical count as part of the annual financial statement audit. Private companies usually face the requirement through a lender, investors, or a GAAP-basis financial statement audit, since an accounting firm won't sign off on a balance sheet without observing inventory. SLED entities holding federally funded equipment must run a physical inventory at least every two years under 2 CFR 200. Even without a mandate, a verified annual count is the baseline most auditors and lenders expect.

What's the difference between an inventory audit and a physical inventory count?

An inventory audit is the complete process of verifying inventory accuracy. It covers planning, counting, reconciling, investigating discrepancies, and documenting adjustments. A physical inventory count is just the counting step. Physical counts generate the raw data. Audits turn that data into verified, actionable records. They add pre-count controls and post-count investigation.

How do I know if cycle counting or a wall-to-wall count is right for my operation?

Choose cycle counting if you can't afford multi-day shutdowns. Also use it if your inventory turns often. Choose a wall-to-wall count if your inventory is stable or your records have drifted too far to trust partial counts. A compliance deadline may also require a full count. High-velocity operations need continuous accuracy without disruption. Wall-to-wall counts work when you can pause operations and need a clean reset. If you want cycle counts to replace the year-end full count entirely, the party requesting your audit has to accept that, and you'll need to show sustained record accuracy over time to earn it.

What should I do if my team finds the same discrepancies every audit?

Recurring discrepancies signal a process failure, not a counting problem. Adjusting the number each time doesn't fix the root issue. Document the pattern by item, location, or transaction type to isolate the breakdown. Common causes include weak receiving controls and missing cutoff procedures. Poor training and system sync failures are also frequent culprits. Fix the process before running another count.

Can I run an inventory audit without disrupting daily operations?

Yes. Use cycle counting to audit inventory in rotating zones without shutting down. RFID scanning lets you count during normal operations. It doesn't require line-of-sight or item-by-item handling. Cycle counts spread the workload across the year instead of packing it into one shutdown window. RFID reads hundreds of tags per second, and purpose-built middleware processes that high-volume data in the background while your team keeps working.

Can I start with barcode scanning and move to RFID later without changing systems?

Yes. We support both barcode and RFID workflows on one platform. You can start with barcode scanning and scale to RFID as volume or accuracy needs grow without switching systems. Both workflows feed the same audit trail and reporting structure, so your process stays consistent regardless of which technology you're using.

See RedBeam in Action

Book a no-pressure demo, tailored for your needs.