Auditors want count evidence, variance records and clean cut-off. Your 200 field locations have none. Yet.
The audit nobody can walk
An inventory audit is a manageable event when everything you own sits in one warehouse. The auditors arrive, receiving and shipping stop, teams walk the aisles with count sheets, and by Friday the inventory number on the balance sheet has evidence behind it. Now run that same audit when your stock sits in 200 or more field locations: engineer vans, hospital cupboards, consignment shelves inside customer buildings, forward stock rooms three time zones away. Nobody can walk those aisles, because there are no aisles. The operations that pass cleanly are the ones that count continuously through the year with instant cycle counting, not the ones that start scrambling in the last week of the fiscal year.
This post is written for the operations leader who owns that scramble. It covers what an inventory audit actually verifies, the three audit types and how each behaves when stock is distributed, what auditors need to see from you, why field stock fails audits so reliably, and how continuous scan-based counting turns the annual crunch into a report you print.
What an inventory audit is, and what it is not
An inventory audit is a periodic, formal verification that the inventory value on your balance sheet is real: that the stock exists, that all of it is recorded, that it is valued correctly, and that it actually belongs to you. It is driven by finance and compliance, usually on a fixed calendar, and often performed or observed by external auditors whose signature your annual accounts depend on.
That makes it a different thing from counting. Cycle counting is a method your own team runs week in, week out, to keep records honest. An audit is a verification event that someone outside your team relies on. The distinction matters because an audit does not produce counting evidence; it consumes it. If the evidence does not exist by the time the auditors ask, no amount of audit-week effort creates it retroactively.
The three inventory audit types, and how each handles distributed stock
In practice, inventory verification comes in three shapes, and the right question for a distributed operation is not which one is best but which one survives contact with 200 locations.
What auditors actually need from you
Strip away the checklists and auditors are testing a handful of things. Standard audit procedure guidance, such as the inventory audit procedures published by AccountingTools, is remarkably consistent on what those are:
- Count evidence. Proof of who counted what, where, and when. Timestamped records beat spreadsheets, because a spreadsheet edited after the fact proves nothing.
- Variance records. Every discrepancy logged, investigated, explained, and adjusted. When auditors rely on cycle counts instead of a full physical count, what they test is precisely the frequency of those counts and the quality of the investigations behind each variance.
- Cut-off discipline. Transactions recorded in the right period. Goods received before the count date belong in this year's inventory; goods shipped before it do not. Sloppy cut-off is one of the fastest routes to a misstated inventory balance.
- Location-level reconciliation. Per-location balances that tie back to the general ledger, not one blended number nobody can decompose.
- Ownership records. Clear evidence of whose stock sits on whose shelf, which becomes genuinely hard the moment consignment enters the picture.
Why distributed field stock fails the audit
Measure a typical field operation against that list and the problem is obvious: the evidence simply does not exist at the edge. Most ERPs expense stock the moment it leaves the warehouse, so the van, the trunk, and the field stock room hold real value with no count trail at all. We have written before about why multi-location inventory management breaks the single-warehouse playbook; the audit is where that break gets expensive. Field inventory that no system counts during the year cannot suddenly produce twelve months of count evidence in December.
Consignment makes it worse. Consigned stock sits inside a customer's building, still on your balance sheet, counted by nobody. Ownership is exactly what the auditor must verify and exactly what neither your ERP nor the customer's can demonstrate at line level. And cut-off discipline collapses entirely when field engineers consume parts days before anyone records it: the transaction lands in whatever period the paperwork catches up in, not the period the stock actually moved.
This is not a paperwork technicality. Records that disagree with reality carry a real price long before the auditor finds them. According to IHL Group research published in September 2025, inventory distortion, the combined cost of out-of-stocks and overstocks, drains $1.73 trillion a year from global retail alone. The audit does not create that cost; it is merely the one week of the year when someone independent measures how far your records have drifted from your shelves.
From audit crunch to a report you print
The fix is not a heroic annual count. It is making the count trail a by-product of daily work. In a continuous scan-based model, every van, consignment point, and stock room becomes a tracked stocking location. Every movement is a timestamped scan on a phone, offline if the site has no signal. Counting happens in small, scheduled slices across the whole network instead of one impossible freeze, and every variance triggers an investigation workflow the moment it appears, not eleven months later when nobody remembers the job.
Run that way, the audit changes character. Count evidence is the scan log. Variance records are the built-in investigation history. Cut-off holds because consumption is recorded at the moment it happens, in the period it happens. When the auditors ask for proof, you filter by location and date range and export. One national ambulance service runs its stations and vehicles exactly this way and holds a rolling inventory accuracy of 99.76%, measured continuously rather than estimated once a year. That is the quiet difference between audit-week heroics and audit readiness: the number the auditor samples is the number the shelf shows.
Field notes
- If your auditors still insist on a year-end wall-to-wall count, ask what evidence would let them rely on cycle counts instead. The answer is a documented counting program, and it is buildable in one fiscal year.
- Consignment locations deserve the same count cadence as your own warehouse. Your balance sheet does not care whose building the shelf is in.
- A variance you adjust without investigating is not a correction, it is a confession that you do not know what happened.
- Watch cut-off in the two weeks around the count date. That is where most audit adjustments are born.
Facing an audit with stock in places nobody can walk through? Book a demo and see how scan-based counting across vans, consignment points and field locations turns audit week into an export.
Frequently asked questions
What is an inventory audit?
An inventory audit is a periodic, formal verification that the inventory value on a company's balance sheet is accurate: that the stock exists, is completely recorded, is valued correctly, and is owned by the company. It is driven by finance and compliance requirements and is often performed or observed by external auditors as part of the annual accounts.
What is the difference between an inventory audit and cycle counting?
Cycle counting is an internal method: your team counts a rotating slice of stock on a regular schedule to keep records accurate. An inventory audit is a verification event: someone outside the team, usually finance or external auditors, checks that the records are trustworthy. A strong cycle counting program is the best evidence an audit can rely on, but the audit itself is the check, not the counting.
Can auditors rely on cycle counts instead of a full physical count?
Yes. Standard audit guidance allows auditors to rely on a cycle counting program in place of a period-end physical count, provided they can test the frequency of the counts and the quality of the investigations into any variances found. For operations with stock in hundreds of locations, this is usually the only audit model that works without shutting the business down.
How to improve inventory accuracy across distributed locations
Make every location a tracked stocking point, record every movement with a timestamped scan at the moment it happens, and count continuously in small scheduled slices instead of one annual event. Investigate every variance when it appears. Operations that work this way can hold inventory accuracy above 99% across field locations, because the record and the shelf never get more than a few days apart.
About Ventory
Ventory is the field inventory layer for regulated, high-stakes industries. We give MedTech, 3PL, Aerospace, Energy and FMCG leaders real-time visibility and control over inventory outside the four walls, in hospitals, ambulances, trunk stock, consignment locations, and field service vans. Ventory is ERP-agnostic (SAP, Oracle, Dynamics, Sage, NetSuite) and trusted by a global medtech manufacturer, a national ambulance service, global logistics and consumer-goods operators. See how it works →
Ten questions. You get a field readiness score, a gap tier and the three fixes worth doing first.
Ventory is the field inventory layer between your ERP or WMS and the teams working outside the warehouse: engineer vans, forward stocking locations, consigned stock and loaner kits.
About Ventory
