Physical inventory orders in Business Central

Even with strict cycle counting and disciplined warehouse processes, physical and system stock balances diverge. The annual or quarterly physical inventory count is the reconciliation event — count what's physically there, compare to system, post adjustments. Business Central supports physical inventory counts through several mechanisms; understanding the choices matters for accuracy and audit defence.

Why physical inventory matters.

• Financial accuracy — balance sheet inventory value must reflect reality.
• Audit compliance — auditors test inventory; large variances trigger findings.
• Operational accuracy — picking and planning rely on correct on-hand.
• Shrinkage detection — theft, damage, mis-counts surface.

The three mechanisms in BC.

• Physical Inventory Journal — basic mechanism; manual entry of counted quantities.
• Counting Period + Cycle Counting — recurring counts on a schedule per item.
• Physical Inventory Orders / Counting (in some warehouse extensions) — more structured workflows.

Physical Inventory Journal. The foundation:

1. Create a Physical Inventory Journal.
2. Calculate Inventory action — populates lines with current system quantity per item.
3. Operator counts physical stock and enters counted quantity.
4. System computes variance.
5. Post Journal — adjusts inventory ledger entries to match counted.

The journal is straightforward; works for small-medium inventory counts.

Counting periods. Items can be assigned a Counting Period code:

• Annual — counted once a year.
• Quarterly — four times a year.
• Monthly — twelve times.
• Custom periods — specific intervals.

The system tracks when each item was last counted; Calculate Counting Period action generates the journal for items due.

Cycle counting. Continuous counting rather than periodic full counts:

• A subset of items counted each day or week.
• Over time, all items get counted.
• Mature operations cycle-count daily.

Cycle counting integrates with item counting period; daily routine becomes the count.

The count process at scale.

For a warehouse with 10,000 SKUs:

1. Plan the count — period, scope, teams.
2. Generate count sheets — items to count, ideally per location/bin.
3. Freeze the warehouse if doing full count (no movement during count) or have controls if not.
4. Count physical — operators count and record.
5. Capture counts — into BC via UI, mobile app, or import.
6. Compare and investigate variances — significant variances require recount.
7. Post adjustments — final variances written to inventory.
8. Unfreeze warehouse if applicable.

Warehouse-mode considerations. In an advanced warehouse:

• Bin-level counts.
• Warehouse Physical Inventory Journal.
• Counts compared at bin level, not just item level.

Lot/serial considerations. For tracked items:

• Each lot/serial counted separately.
• Variances tracked per lot.
• Lost serials investigated.

Variance investigation.

• Material variances — recount; investigate cause.
• Bin location errors — item miscoded; correct master data.
• System lag — recent transactions not yet posted.
• Shrinkage — accept as loss after investigation.

Mature operations have variance thresholds — within 1%, accept; above, investigate.

Mobile counting. Hand-held scanners + mobile app:

• Operator scans item barcode → enters count.
• Faster than paper-based.
• Less error-prone.
• Real-time capture into BC.

Third-party warehouse mobile extensions (Tasklet, Insight Works) provide rich mobile counting.

Inventory close vs physical inventory.

• Inventory close (F&O) — period-end cost adjustment routine; not physical counting.
• Physical inventory — actual count of stock.

Different concepts; both needed periodically.

Common pitfalls.

• No frozen window. Movements during count; variances impossible to investigate.
• Manual data entry slow. 10,000 items × manual keying = days of work; mobile saves.
• Variance tolerance too loose. Material variances accepted without investigation; shrinkage hidden.
• Counting periods stale. Items with periods set 5 years ago; no longer reflect reality.
• Post without review. Adjustments posted without management approval; large hits to P&L.

Approval workflow. For large variances:

• Threshold-based approval routing.
• Operations manager reviews top variances.
• Finance approves before posting if material.

Without controls, posting authority extends too widely.

Audit considerations. Auditors look for:

• Evidence of the count (count sheets, system records).
• Variance investigation documentation.
• Approval of significant adjustments.
• Year-over-year consistency in shrinkage rates.

Document the count process; retain records for at least the audit retention period.

Operational rhythm.

• Daily — cycle count subset.
• Quarterly — review variances and counting periods.
• Annual — full physical (depending on company policy).
• Pre-fiscal-year-end — count and reconcile.

Strategic positioning. Physical inventory is the moment of truth for inventory accounting. Investing in mobile-driven counting, clear process, variance investigation, and audit-quality documentation pays back in audit defence and operational accuracy. Skipping it or doing it poorly leads to balance sheet surprises and audit findings. For most operations, cycle counting daily plus a periodic structured count provides the right balance of effort and accuracy.