The cycle count team finishes the December run and reports a 99.1% inventory accuracy figure to the executive sponsor. The number gets included in the year-end pack, the controller signs off, and the operation moves on to planning for the next quarter. Three months later, the external audit team arrives and asks not for the accuracy number but for a list of every inventory adjustment made during the year. The list runs to four thousand entries. The auditor flags it as a control deficiency because the volume of adjustments suggests that the underlying records are being corrected so frequently that the accuracy claim is not credible. The 99.1% number was true at a single point in time, but the work required to produce that number tells a different story than the headline does.
This is the gap that catches most operations teams off guard. The inventory accuracy metric they publish is the snapshot, the percentage of locations or items that match the count on a given day. The metric the auditor weights is the adjustment frequency, the volume and pattern of corrections required to keep the records aligned with reality. The two metrics tell different stories about the same operation. The snapshot can be flattering and the adjustment frequency can be alarming, both at the same time, in the same period, against the same data. Knowing which metric to publish and which to investigate is the difference between an audit that confirms the operation is in control and one that questions whether it ever was.
The Snapshot Metric and Its Limits
The standard inventory accuracy formula is the percentage of items or locations where the system count matches the physical count on the day of the cycle count or annual inventory. A 99% accuracy rate sounds impressive and is usually what gets reported to leadership and external stakeholders. The metric is real, but it is also incomplete. It tells you the state of the records on the day they were checked. It does not tell you what work was required to get them into that state, how often they fall out of that state between checks, or what the average time to detection of an error actually is.
This is why the snapshot metric is best understood as a hygiene check rather than a comprehensive measure of inventory integrity. A team that runs cycle counts weekly and corrects every variance immediately can publish a high accuracy number without ever having a clean underlying process. The metric reflects the work, not the underlying control. A team that runs cycle counts quarterly and corrects only when variance exceeds a threshold can publish the same number while running a cleaner process underneath. The two operations look identical on the dashboard and feel completely different to the auditor.
The other limitation of the snapshot metric is that it is unit-blind. An operation with 99% accuracy across ten thousand items might have small variances on common items and large variances on the few items that drive most of the financial exposure. The headline number does not distinguish between a one-unit miss on a low-value SKU and a thousand-unit miss on the most expensive raw material in the inventory. Auditors learn to ignore this number because it cannot tell them what they need to know.
Why Auditors Weight Adjustment Frequency
The metric auditors care about is the adjustment frequency, sometimes expressed as the ratio of adjustment movements to total movements over a period. This is what gets called the accuracy vs adjustment ratio in audit shorthand. The logic is simple. Adjustments are what teams do when the records and the physical reality diverge. The more adjustments, the more divergence. A high adjustment frequency tells the auditor that the underlying process is producing errors at a high rate, regardless of whether the snapshot accuracy figure is high at any given moment.
Adjustment frequency also distinguishes between two operations that produce the same accuracy number. The team that adjusts often to maintain the appearance of accuracy is masking a process problem. The team that adjusts rarely, with each adjustment supported by a specific investigation, is showing that the process is genuinely under control. The auditor can tell the difference because the adjustment frequency is a property of the ledger, not the dashboard, and the ledger does not lie about how often the records had to be corrected.
The adjustment ratio is also more informative for operational decision-making. When the ratio rises, it is a leading indicator that something in the process is failing. Maybe a receiving station is mis-keying quantities. Maybe a transfer is being booked twice. Maybe a production run is consuming more or less than the BOM predicts and the variance is being absorbed into adjustments rather than investigated. The ratio surfaces these patterns before they accumulate into a single embarrassing audit finding.
Adjustment Frequency at the Location Level
Aggregate adjustment frequency is useful, but the more diagnostic view is location-level accuracy. Multi-site manufacturers will find that adjustment volume is rarely distributed evenly across the network. One location will show three times the adjustment rate of the others. Sometimes this is because the location is busier. More often it is because the location has a process gap, a training deficit, or a system access pattern that produces more errors. The location view exposes the gap. The aggregate hides it.
A platform that scopes accuracy data by location, with the full ledger of movements and adjustments retained per site, gives the audit team something useful to work with. The audit-ready inventory operation can produce a per-location adjustment ratio for the period, then drill into the specific adjustments at the highest-rate locations to investigate cause. This converts the audit from an interrogation of management's claim into a structured review of the underlying records, which is exactly what auditors prefer.
The same data also gives the operations team a direct lever for improvement. If three sites are under one percent adjustment ratio and one is at five percent, the management attention should go to the outlier rather than to a generalized accuracy initiative across the network. The location view also exposes whether adjustment rates are improving or worsening over time, which is the trend signal that matters more than any single snapshot.
Role-Based Authority for Adjustments
The other property auditors look for is the authority structure around adjustments. An adjustment is a controlled action because it changes the record without a corresponding physical event in the normal flow of business. Controls require that adjustments be made by users with appropriate authority, that the reason for each adjustment be captured, and that the trail be preserved against later modification. A platform that allows any user to adjust any stock record at any location with no required justification is a control failure waiting to be flagged.
The right model is role-scoped authority for adjustments. Warehouse operators can record receipts and dispatches in the normal flow, but adjustments require a manager role and a reason code. Adjustments above a threshold require a second approver. Cross-location adjustments require explicit access to both locations. The point is not to make adjustments hard but to make them traceable to a specific person, a specific reason, and a specific approval path. When the auditor reviews the adjustment ledger, every entry should have a name, a timestamp, a reason, and where applicable an approver attached to it.
This is also where the immutable nature of the underlying ledger pays off. Adjustments themselves are events that get recorded forever, not edits to the original record. The original receipt, the production run, or the transfer remains as it was logged, and the adjustment becomes a separate event with its own context. Auditors can replay the entire history without ambiguity about what was originally recorded and what was changed later. This is the core of an audit-ready inventory architecture, and it removes most of the friction from the audit process because the data the auditor wants is the data the system has been keeping all along.
Alert Thresholds on Adjustment Frequency
The most useful operational application of the adjustment ratio is to alert when it crosses a threshold. A platform that watches the rate of adjustments per location, per item category, or per user can fire a signal when the rate moves outside its normal range. This catches problems early, before they become structural. A receiving station that suddenly produces three times its usual adjustment rate has a process problem that should be investigated this week, not at the next audit.
The alert thresholds for adjustment frequency are best set as rolling baselines rather than static numbers. Each location and category has its own normal rate, driven by volume, item type, and operational complexity. An anomaly is a deviation from that baseline, not an absolute number. A platform that learns the baseline and surfaces deviations gives the operations team a leading indicator that no static threshold could provide.
Alert design also matters here. An alert that fires every day for the same elevated rate becomes noise within a week. The alert should fire when the elevation is detected, then suppress until the rate returns to baseline or until the elevation worsens. This is the same alert design discipline that applies to any production-grade alerting system, and it determines whether the team treats the signal as actionable or as background.
Publishing the Right Metric
The discipline of audit inventory accuracy reporting is to publish two numbers, not one. The first is the snapshot accuracy, computed from the most recent cycle count or full inventory, broken down by location and item category. The second is the adjustment ratio for the period, also broken down by location and category, with the trend over time. The combination tells a complete story. The snapshot tells you where you are now. The ratio tells you what work was required to get there and whether the underlying process is stable.
A team that publishes both numbers earns a different audit conversation. The snapshot accuracy is the headline, but the adjustment ratio is the evidence the headline is honest. When the auditor asks how the team achieved 99% accuracy, the answer is supported by an adjustment ratio that is low and stable. The accuracy benchmark is more meaningful when published alongside the metric that explains it.
The other reason to publish both is internal. Operations leaders make different decisions when they see both numbers. A 99% snapshot combined with a one percent adjustment ratio suggests a controlled process. A 99% snapshot combined with a five percent adjustment ratio suggests a process held together by manual correction. The decisions to invest in process improvement become legible when the two metrics are reported together. For more on the architecture, see the available-to-promise piece and the mrp planning horizons explainer in our archive.
The Audit That Confirms Control
An inventory accuracy metric that survives an external audit is one that the team can defend with primary records, not just dashboard claims. The defense rests on three pillars. The records of every movement are immutable, so the auditor can see what was originally entered without the risk that the entry has been edited. The adjustments are infrequent, scoped to authorized users, and supported by reasons that make sense in context. The trends in adjustment frequency are stable or improving, with any anomalies investigated and resolved within a documented timeframe.
A team that operates this way will find that the audit becomes a verification exercise rather than a discovery exercise. The auditor asks for the same data the team has been watching all year, and the answers are ready. The operations team spends less time preparing for audits because the audit-ready posture is the same as the operational posture. That is the actual goal of inventory accuracy work, and it is reachable for any operation willing to publish the two metrics that matter rather than the one that flatters.
FalOrb helps manufacturers track inventory accuracy and adjustment frequency against an immutable ledger of stock movements with role-scoped authority and configurable alert thresholds. Visit falorb.com, book a 30-minute walkthrough, or email us at [email protected] to see how it applies to your operation.