Acumatica Physical Inventory Count: The Complete Tutorial

A physical inventory count comes back with a variance, and the first reaction is almost always “something’s wrong with the system.” Most of the time, nothing’s actually broken — it’s a timing issue between when goods physically move and when Acumatica records that movement. This guide walks through how to run an Acumatica physical inventory count from start to finish, exactly what quantity the system compares against, and the #1 mistake that causes false shortages.

What Is a Physical Inventory Count in Acumatica?

A physical inventory count compares the physical, real-world quantity of an item against the system’s book quantity, and generates an inventory adjustment for any difference. It’s typically performed before closing a financial period, to make sure your books reflect what’s actually on the shelves. A physical count is not the same thing as a cycle count — and picking the wrong one for your operation is where most of the trouble starts.

Full Physical Inventory vs. Cycle Counting

Full Physical Inventory

Counts every item in the warehouse at once. This method freezes the entire warehouse — no inventory transactions can be released for that warehouse until the count is complete. It’s best suited for a planned shutdown window, such as a weekend or a scheduled closing.

Cycle Counting / By Item Class / By Specific Items

Counts a defined subset of inventory — a class of items, specific items, or a rotating cycle. Only the items and locations actually included in the count get frozen; the rest of the warehouse can keep operating normally. This is the more realistic option for a business that can’t fully stop.

Method	Scope	Freeze Impact	Best For
Full Physical Inventory	Entire warehouse	Whole warehouse frozen	Planned shutdown / closing
By Item Class	One or more item classes	Only those items frozen	Category-specific counts
By Specific Items	Selected items	Only those items frozen	Spot checks, high-value items
Cycle Counting	Rotating subset over time	Only the cycle’s items frozen	Continuous accuracy without downtime

What Quantity Does Acumatica Actually Compare? (The Book Qty Formula)

This is the part most teams never dig into — and it changes how you should read every variance you get. The quantity a physical count document compares against isn’t your raw On Hand quantity. It’s calculated as:

Book Qty = Qty on Hand − Qty on SO Shipped

In practice, that’s the same calculation as Available for Issue — a term we broke down in detail in Acumatica Inventory Availability Explained: On Hand vs. Available. Acumatica is already trying to net out anything tied to a confirmed shipment before comparing to your physical count — because comparing against a raw On Hand figure would produce a false variance on any day with shipping activity at all.

The #1 Cause of False Variances: The Book Qty Snapshot Goes Stale

Here’s the catch: that formula is calculated once — the moment you click Generate PI. It is not recalculated as the day goes on. Walk through this example: in the morning, On Hand is 12 and 2 units are already tied to a confirmed shipment, so the Book Qty snapshot locks in at 10. During the day, two more orders for 2 units each get confirmed — and in a lot of warehouse operations, “confirmed” already means the item has a tracking number and has physically left the building. Those 4 units are now genuinely gone. But the count sheet is still comparing against the 10 from the morning. When you count, you correctly find only 8 units on the shelf. The system compares 8 against the frozen 10 and reports a variance of -2 — which looks like a shortage, but is really just same-day shipping activity that the snapshot never saw.

If a shipment is confirmed after Generate PI but before you finish counting, that quantity won’t be reflected in the Book Qty you’re comparing against — even though it’s already physically gone.

The Double-Deduction Trap: When a PI Adjustment and a Pending Shipment Collide

This is where a false variance turns into a real accuracy problem. If that -2 adjustment gets released, and afterward the deferred sales transaction for those same 2 units also releases — for example, because invoicing doesn’t happen until a nightly batch process — On Hand gets reduced a second time for the exact same units. The result compounds: inventory ends up understated by the full amount twice over, not once. This isn’t a hypothetical edge case. A very similar pattern has come up independently in Acumatica’s own user community, involving service orders that consume stock before the service invoice is released: a physical count captured items that were already committed but not yet formally deducted, triggered an adjustment, and the team noted that “inventory would then be incorrect and eventually the problem compounds itself out of control” (Acumatica Community). Same root cause, different transaction type — anything with a delayed release creates the same risk. Warning signs this is happening to you:

• Negative adjustments that don’t match any real physical shrinkage.
• On-hand quantities that keep dropping overnight, after the count is already complete.
• Variances that consistently match your same-day order volume.

How the Freeze Actually Works (and Its Limits)

When a count review document has the Counting in Progress status, Acumatica blocks the release of inventory transactions for the warehouse or items involved — that’s the built-in protection against exactly this problem. There’s a setting that changes this behavior: Unfreeze Stock When Counting Is Finished, on the Physical Inventory Types (IN208900) form. If it’s selected, the freeze lifts as soon as the count moves to Data Entering status — even if the physical counting itself isn’t finished yet. That means transactions can start releasing again while your team is still walking the floor. The practical takeaway: don’t move a count to Data Entering until the physical counting is genuinely done. Doing it early — even to “get a head start” on data entry — is what opens the door to the stale-snapshot problem above.

Step-by-Step: How to Run a Physical Inventory Count in Acumatica

1. Configure Inventory Preferences (IN101000). Decide whether you’ll use tags, and whether PI adjustments should release automatically or wait for review.
2. Create a Physical Inventory Type (IN208900). Choose Full, By Item Class, By Specific Items, or a cycle-based type, based on how much of your operation can actually pause.
3. Release or clear all pending transactions for the items you’re about to count, before generating the count.
4. Generate the count on Prepare Physical Count (IN504000). This is the moment the Book Qty snapshot is taken and the freeze begins.
5. Distribute the physical count sheets and complete the actual floor count. You can print it in Physical Count Sheets (IN620500).
6. Click Finish Counting only once the floor count is fully done — not before.
7. Enter counted quantities on Physical Inventory Count (IN305010), or import them from Excel via Physical Inventory Review (IN305000).
8. Review the generated adjustment before completing — confirm every line reflects a genuine physical variance, not same-day order activity.
9. Complete PI and release the adjustment.

Best-Practice Checklist for an Accurate Count

• Don’t generate the count until same-day shipping activity for those items is settled or paused.
• Match your count type to your operational reality — don’t force a Full count on a location that can’t fully stop.
• Never rush from Counting in Progress to Data Entering before the floor count is finished.
• Review every adjustment line before releasing — a variance that lines up with same-day order activity is a timing artifact, not shrinkage.
• Reconcile any deferred or nightly release process against your count calendar, so invoice timing doesn’t overlap with the count window.

Frequently Asked Questions

Can you count inventory while the warehouse is still operating in Acumatica? With a Full Physical Inventory, no — the entire warehouse is frozen until the count completes. With Cycle Counting or a By Item Class/By Specific Items count, yes — only the counted items and locations are frozen, so the rest of the warehouse can keep working. What quantity does Acumatica compare against during a physical count? Book Qty, calculated as Qty on Hand minus Qty on SO Shipped — effectively the same figure as Available for Issue, captured as a snapshot at the moment the count is generated. Why does my physical inventory count show a shortage that isn’t real? This usually happens when orders are confirmed and shipped after the count was generated but before counting finished — those units are physically gone but weren’t included in the frozen Book Qty snapshot, creating a false variance. What happens if I complete a physical inventory adjustment before a pending shipment invoice releases? You risk a double deduction: the PI adjustment reduces On Hand once for the missing units, and the deferred sales transaction reduces it again for the same units once it releases, leaving your inventory understated. What’s the difference between a full physical inventory and a cycle count in Acumatica? A full physical inventory counts and freezes the entire warehouse at once, best for a planned shutdown. Cycle counting rotates through subsets of inventory over time, freezing only the items involved, so normal operations can continue.

Conclusion

Most “the count broke my inventory” problems aren’t data problems — they’re timing problems. Once your team understands that Book Qty is a frozen snapshot, not a live number, most unexplained variances stop being a mystery. Not sure if your Physical Inventory Type or shipment/invoice timing is set up to avoid this? ClandBus can review your configuration and walk your team through a live count. Contact us or read more about our specialized Acumatica support. Related reading: Acumatica Inventory Availability Explained: On Hand vs. Available.