Cycle counting and physical inventory in Business Central

Inventory accuracy is operationally fundamental — a system that says 100 widgets on hand when the warehouse holds 87 produces wrong promises to customers, wrong picking instructions, wrong cost of goods sold. Cycle counting (frequent counting of small subsets) and full physical inventory (counting everything periodically) are the two practices Business Central supports for keeping inventory honest.

Physical inventory journals. The fundamental counting tool. A physical inventory journal:

• Header — date, location, period.
• Lines — one row per item being counted, with the system-recorded quantity and a field for the counted quantity.

The flow:

1. Calculate Inventory action populates the journal with all items in scope (filtered by location, item, item category, bin). The system quantity is filled in.
2. Print Count Sheets — paper or PDF lists for warehouse workers to use during counting.
3. Workers count physical inventory and write counted quantities on the sheets.
4. Enter counted quantities into the journal (manually, via Excel import, or via mobile scanning).
5. Calculate difference — system quantity minus counted quantity per line.
6. Investigate exceptions — large variances get investigated before posting (could be a count error, a posting error, or genuine shrinkage).
7. Post the journal — adjustment entries hit the item ledger and value entries; the GL receives the variance offset to inventory adjustment accounts.

Cycle counting. Instead of counting everything at once (disruptive), cycle counting counts small subsets continuously — a few hundred SKUs every day, every week, rotating through the catalogue so every item is counted N times per year.

Business Central supports cycle counting through item counting periods:

• Each item has a counting period (Daily, Weekly, Monthly, Quarterly, Annually, or custom).
• Items with the same period are counted on the same cycle.
• The Calculate Counting Period routine identifies items due for counting today.
• The user generates a physical inventory journal for those items, counts, and posts.

ABC analysis and counting frequency. Mature operations tier inventory by importance:

• A-class items (high value or high velocity, ~10–20% of SKUs accounting for 70–80% of inventory value) — count weekly or monthly.
• B-class items (medium) — count quarterly.
• C-class items (low value, slow movers) — count annually.

This focuses counting effort where accuracy matters most. The ABC analysis report in Business Central segments items; the counting period on each item card aligns.

Mobile scanning. For larger warehouses, manual paper-based counting is slow and error-prone. Mobile scanning via partner ISVs (Tasklet, Insight Works, Continia WMS):

• Worker scans bin, then scans each item / quantity.
• Data flows directly to the physical inventory journal in BC.
• No paper, no transcription errors, faster cycle times.

Locations and bin counting. Multi-location operations need counting per location; bin-managed locations need counting per bin. The physical inventory journal supports filters for these scopes:

• Bin counting — list every bin and its contents, count each bin separately.
• Stockpile counting — for locations without bins, count items in aggregate.
• Cross-location counting — same item across multiple locations counted together for the analytical view.

Counting and item tracking. Items with lot or serial tracking require tracking-level counting — count by lot or serial, not just total quantity. The journal supports tracking specifications; the counted quantity per lot / serial must match the system's tracking records.

Reconciliation to GL. Posted physical inventory adjustments hit:

• Item ledger (quantity adjustment).
• Value entry (cost adjustment per inventory layer).
• GL: inventory account (debit / credit depending on direction) and inventory adjustment account (offset).

After posting, the Inventory Valuation report should reconcile to the GL inventory balance.

Frequency and discipline.

• Daily cycle counting for high-velocity items.
• Weekly cycle counting for moderate-velocity.
• Monthly cycle counting for slow-movers.
• Annual full physical inventory as the safety net (legal / audit requirement in some jurisdictions).

Without ongoing cycle counting, accuracy drifts; with active cycle counting, full physical inventory becomes a confirmation rather than a surprise.

Common pitfalls.

• Counting without investigating variances — adjustments post without understanding why; root cause never fixed.
• Frozen mid-count discrepancies — if posting / shipping continues during a count, the count is invalid. Pause activity per location.
• Tracking inconsistencies — counted quantity doesn't match the lot / serial breakdown; partial-tracking adjustments are error-prone.

Operational reality. Inventory accuracy is unglamorous and continuous. Cycle counting is a daily discipline; full physical inventory is the annual safety net. Both compound — well-run operations have inventory variances under 1%; poorly-run operations have variances over 5% perpetually.