Last reviewed: 10 October 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
Editorial ink illustration: Two colleagues compare a parcel with records during a warehouse count.
A physical count of fifty-five against a system snapshot of fifty looks like a five-unit difference. If five units were received during the count, the difference may be explained by timing rather than an unexplained gain.
NetSuite Inventory Count compares count information with a snapshot taken when the count starts. Completing the count and approving the resulting adjustment are separate stages. The reviewer needs to understand the snapshot, the observation, and any movements between them.
This lesson is for inventory counters and approvers. It uses a fictional count with one in-count receipt and explains why raw differences need investigation. Confirm the Inventory Count feature, permissions, item details, and snapshot preferences in your account before performing an exercise.
A count needs a boundary: the location, items, units, and relevant inventory details. Without that boundary, two people can count different stock and believe they disagree about the same quantity.
Confirm which bins, lots, serial numbers, or statuses are included where those features apply. Identify any goods physically nearby that belong outside the count, such as another item, another location, or a separately controlled area.
Agree how the team will handle movement during the exercise. Where practical, control receipts, shipments, transfers, and other changes for the count scope. If work must continue, establish how each movement will be documented and reconciled.
The boundary should be understandable to both the counter and the reviewer. “Count item TEST-6 at North in each, including these designated bins” is more useful than “count the shelf.”
Starting an open inventory count takes a snapshot of the on-hand quantities for the selected items and relevant details. That snapshot is the system's comparison point for the count.
It is not a live physical observation. It represents recorded stock at that moment. A later receipt or shipment can make current on-hand quantities differ from the original snapshot while the count is still in progress.
For that reason, note when the count starts and when the physical observation occurs. The time between them is important evidence. A screenshot of today's item balance does not automatically establish what the snapshot contained when the count began.
Counts can be created manually or from scheduled count requirements. A calculated list of items due for counting determines which work is due; it does not replace the physical count.
The counter records observed quantities and required inventory detail. While the count is started, quantities can be reviewed and edited under the supported process, but the set of count items is no longer freely changed.
Completing the count moves it to the review stage. In Completed/Pending Approval, the quantities and results cannot simply be edited as though the count were still open. A reviewer approves or rejects the completed count through the appropriate process.
Approval can create the inventory adjustments needed for the accepted differences. That makes approval consequential: it is more than acknowledging that someone walked through the warehouse.
Rejection means the count needs further work or recounting. Depending on the configured preference, rejecting can also take a new snapshot. The reviewer must understand that change in comparison point before interpreting the next result.
Imagine a fictional count at Pinebridge Distribution. The team is counting one inventory item at one location in each. At the start, the count snapshot shows fifty units.
While counting is in progress, a documented receipt adds five units to the same item and location. In this example, the receipt is recorded in NetSuite and the five units are included in the physical area being counted. No other movement occurs.
The counter observes fifty-five units. The physical observation is consistent with fifty at the start plus five received. The raw difference of five from the original snapshot is explained by the movement under these assumptions.
It would be misleading to call that difference an unexplained surplus without checking the receipt. It would also be unsafe to approve an extra five-unit adjustment simply because fifty-five minus fifty equals five. The receipt has already increased the recorded stock, so another increase could count the same arrival twice.
Keep the actual physical count of fifty-five and the receipt evidence. Record the item, location, unit, receipt identifier, and timing. Do not replace the observation with a guessed number simply to make the variance disappear.
The final values entered into the count process must follow the organization's supported method for accounting for movements. The counter and reviewer need to understand how that method aligns the physical observation with the relevant snapshot.
If the receipt was not recorded, went to another location, or arrived after the physical count, the explanation changes. Those are different cases and must be investigated separately. The example's conclusion depends on the stated timing and matching scope.
NetSuite provides the Recalculate Snapshot on Inventory Count Reject preference. When enabled, rejecting a count can take a new snapshot and update the related adjustment and variance details.
The reviewer should confirm whether that preference applies and follow the supported rejection, recount, and review process when needed. Do not assume the snapshot silently refreshes every time inventory moves.
In the fictional example, a properly aligned snapshot after the recorded receipt can reflect fifty-five units. A corresponding verified physical count of fifty-five would then support no unexplained quantity difference, assuming the same scope and no further movements.
That is an interpretation to verify through the configured process, not a universal instruction to press a button or overwrite a quantity. Preserve both the original evidence and the revised comparison so that another reviewer can follow why the result changed.
A total of fifty-five can still conceal a detail problem. The right total may be assigned to the wrong bin, lot, serial number, or inventory status.
For supported detailed counts, review the count detail against the snapshot detail and physical evidence. Confirm that the unit and component quantities reconcile. A total-level match should not be treated as proof that the traceability data is correct.
Counts of lot-numbered or serialized items require Advanced Bin/Numbered Inventory Management. Confirm the feature and the actual detail requirements before a training exercise or production count.
If detail does not reconcile, identify the exact mismatch. “The total matches, but the two lot quantities are reversed” gives the reviewer a useful question. “Count error” does not explain whether the issue is quantity, identity, or location.
An unexplained count difference can arise from several sources: an omitted receipt, a timing mismatch, the wrong unit, a transfer recorded elsewhere, a counting error, or a genuine physical discrepancy. The number alone cannot select among them.
Start with scope and timing because those checks can explain a difference without changing stock. Then review the relevant transactions and recount when the evidence calls for it.
Do not describe a shortage as theft or loss merely because the count is lower than the snapshot. Those are conclusions that require further evidence and the organization's investigation process.
Likewise, do not approve a positive variance as a convenient correction for a missing purchase receipt. If the arrival belongs to a purchase order, recording the proper transaction may be necessary to preserve purchasing and accounting relationships. Coordinate with the responsible owner before deciding the correction.
The lesson on purchase orders, receipts, and vendor bills explains why an inventory adjustment is not an interchangeable replacement for receipt evidence.
Before approval, inspect the proposed adjustment quantity, snapshot detail, and variance detail. Confirm that movement evidence has been incorporated through the supported method and that the reviewer understands the resulting stock position.
After approval, inspect the inventory adjustments associated with the count and verify their actual quantities and relevant posting information. Do not assume that the count total itself is the posted adjustment amount.
A count can create positive and negative adjustments for different differences. Review the affected records rather than reducing the entire outcome to one net number that may hide offsetting errors.
Then check the updated inventory position and retain the explanation. The evidence should connect the count scope, physical observation, movements, review decision, and resulting adjustments. If no unexplained difference remained, that should be clear as well.
If approval is unavailable or fails, inspect the count state, permissions, snapshot details, and applicable inventory restrictions. Continued movements can affect whether the resulting quantities are valid.
Do not create an unrelated manual adjustment to bypass a count that still needs investigation. That can make the next comparison harder and leave the original issue unresolved.
If the count is already completed, follow the supported rejection and recount process where appropriate rather than looking for another route to alter locked results. Confirm whether rejection recalculates the snapshot in your configuration.
If the team cannot explain the outcome, preserve the records and ask the inventory administrator and finance owner to review the exact error and data. Include the count identifier and affected detail, not only the headline variance.
A count becomes reliable when its quantities describe the same stock at an understood point in time. Use the snapshot as a defined comparison, account for movements, and approve only the result the evidence supports.
For the underlying balance meanings, read on-hand, committed, and available inventory. For help preparing role-specific count exercises, explore CuriousRubik's NetSuite training services.