6.2 Counting Journals, Tag Counting, and Cycle Count Adjustments
Key Takeaways
- Counting journals calculate inventory variances automatically using the formula Quantity = Counted - On hand, where positive variances generate receipts (Inventory profit) and negative variances generate issues (Inventory loss).
- Counting groups automate counting schedule creation via Period, Zero on hand, and Minimum triggers assigned to released products.
- The 'Lock items during count' parameter prevents active warehouse transactions and reservations from skewing stock levels during physical counting.
- Tag counting journals provide double-blind physical audit controls using pre-numbered tags that must be completely reconciled before transferring counts into a standard counting journal.
- Counting discrepancy thresholds enforce segregation of duties by requiring managerial approval workflows when variance quantities or values exceed authorized worker limits.
6.2 Counting Journals, Tag Counting, and Cycle Count Adjustments
Quick Answer: In Dynamics 365 Supply Chain Management, physical inventory verification is managed through Counting journals (for periodic cycle counts and location audits) and Tag counting journals (for formal wall-to-wall annual audits utilizing pre-numbered tags). When a counting journal line is created, the system records an
On handsnapshot; when the user enters theCountedquantity, the system calculates the variance asQuantity = Counted - On hand. Posting the journal automatically creates inventory issue (Deducted) or receipt (Received) transactions and posts offsetting financial adjustments to Inventory profit or Inventory loss accounts configured in the Inventory posting profile.
1. Counting Journal Setup and Line Creation Methods
Counting journals are accessed at Inventory management > Journal entries > Item counting > Counting. Before lines can be populated, a counting journal header must be created referencing a journal name configured with the Counting journal type.
Inventory management
└── Journal entries
└── Item counting
└── Counting
└── Lines > Create (Items, On hand, Counting groups)
Automated Line Generation Options
Instead of entering items manually line by line, warehouse supervisors populate counting journals using three automated generation engines under the Create menu:
- Create > Items: Generates counting lines based on a query filtering released products by Item number, Item group, ABC code, or search name. This method generates lines regardless of whether on-hand stock currently exists.
- Create > On hand: Generates counting lines only for items and storage/tracking dimensions that currently hold physical on-hand inventory. This prevents generating empty lines for inactive inventory.
- Create > Counting groups: Generates lines based on the Counting group parameters assigned to released products (Inventory management > Setup > Inventory > Counting groups).
Counting Group Parameters
Counting groups define automated cycle counting policies:
- Counting code: Governs the triggering rule:
Manual: Lines are generated only when explicitly queried by the user.Period: Generates counting lines at recurring intervals defined by the Counting period in days (e.g., 30 days for Class A items, 90 days for Class B, 360 days for Class C).Zero on hand: Automatically creates a counting line whenever an item's physical inventory drops to zero, verifying that the location is truly empty.Minimum: Generates a counting line when on-hand stock reaches or breaches the safety stock minimum.
The 'Lock Items During Count' Parameter
When generating counting lines, enabling the Lock items during count checkbox places a transactional block on the item at the specified storage dimensions (warehouse and location). While locked:
- Open sales orders, transfer orders, and production picking lists cannot register issues or reserve stock from that location.
- Inbound receipts cannot be registered to that location.
- This locks inventory in place during physical counting, eliminating data skew caused by active picking or putaway during audit sweeps. Once the journal is posted or deleted, the lock is automatically released.
2. Counted Quantity vs. On-hand Quantity and Variance Calculations
Each line in a counting journal presents three core quantity fields that govern inventory variance accounting:
| Field | Description | System Behavior |
|---|---|---|
On hand | System-recorded physical inventory at the exact moment the counting line was generated. | Read-only snapshot of current inventory. |
Counted | Actual physical quantity counted by the warehouse worker or auditor. | Editable. Defaults to the on-hand quantity or blank depending on setup. |
Quantity | Calculated variance (Counted - On hand). | System-calculated. Represents the net adjustment to be posted. |
Variance Posting Mechanics
- Positive Variance (
Counted > On hand): The worker found more stock than recorded. The resultingQuantityis positive.- Inventory Transaction: Status
Received. - Ledger Posting: Debit Inventory physical asset account (
Inventory receipt), CreditInventory profitaccount.
- Inventory Transaction: Status
- Negative Variance (
Counted < On hand): The worker found less stock than recorded (shrinkage or damage). The resultingQuantityis negative.- Inventory Transaction: Status
Deducted. - Ledger Posting: Debit
Inventory lossaccount, Credit Inventory physical asset account (Inventory issue).
- Inventory Transaction: Status
- Zero Variance (
Counted == On hand): Quantity is 0. Posting the journal confirms the count date on the item without posting financial vouchers.
[!IMPORTANT] Exam Tip — Confirming Zero On-Hand: If a location is physically empty, the counter must explicitly enter
0in theCountedfield. If the field is left blank or the line is deleted, the system will not adjust the on-hand inventory, leaving ghost inventory in the system.
3. Tag Counting Journals and Double-Blind Physical Audits
For formal annual or semi-annual wall-to-wall physical inventory audits, enterprises utilize Tag counting journals (Inventory management > Journal entries > Item counting > Tag counting).
Inventory management
└── Journal entries
└── Item counting
└── Tag counting
├── Tag entry (Pre-numbered sequential tags)
├── Reconcile missing/void tags
└── Post Tag Journal (Transfers consolidated data to Counting Journal)
Tag Counting Architecture and Workflow
- Pre-Numbered Physical Tags: Sequential paper or barcode tags are printed and distributed to audit teams. Each tag has a unique identifier tracked by the system.
- Double-Blind Auditing: Two independent count teams count the same warehouse zones without visibility into system on-hand balances or each other's recorded numbers. If counts differ, an audit supervisor recounts the location.
- Tag Entry: Auditors enter the physical counts into the Tag counting journal, recording Tag number, Item ID, Product dimensions (Size, Color), Storage dimensions (Site, Warehouse, Location), Tracking dimensions (Batch, Serial), and the Counted quantity.
- Tag Status Reconciliation: Every issued tag must be accounted for before the audit can be finalized:
Used: Tag contains verified physical count data.Voided / Damaged: Tag was spoiled during the audit and must be explicitly recorded as void.Missing: Any gap in the sequential tag series is flagged by the system, preventing closure until the missing tag is located or formally voided.
- Transfer to Counting Journal: Posting a Tag counting journal does NOT post financial adjustments to the General Ledger. Instead, posting the Tag counting journal consolidates all tag records, computes net variances against current on-hand balances, and automatically generates a standard Counting journal. The accounting manager then reviews the generated counting journal and posts it to commit the financial and inventory adjustments.
4. Counting Reason Codes, Discrepancy Thresholds, and Approval Workflows
To enforce audit governance and prevent fraudulent or erroneous write-offs, D365 SCM provides reason codes and threshold controls.
Counting Reason Codes
- Configured at Inventory management > Setup > Inventory > Counting reason codes.
- Reasons represent operational causes for variances:
Damage,Theft / Shrinkage,Vendor Mispack,Spill / Evaporation,Data Entry Error. - Reason codes can be configured as Mandatory whenever a counting variance exists (
Quantity != 0).
Discrepancy Thresholds and Approval Limits
Enterprises can restrict warehouse workers from posting large inventory adjustments by establishing Counting thresholds:
- Maximum quantity threshold: Maximum number of units a worker can adjust on a single line (e.g., up to 50 units).
- Maximum value threshold: Maximum total financial value a worker can adjust on a single line (e.g., up to $1,000).
- Percentage threshold: Maximum allowable percentage variance relative to on-hand stock (e.g., variance cannot exceed 5%).
Workflow Routing for Approvals
When an inventory worker posts a counting journal where one or more lines breach the configured thresholds, the journal cannot be posted directly. Instead, it triggers an Inventory counting journal approval workflow (Inventory management > Setup > Inventory management workflows). The workflow routes the journal to the Warehouse Manager or Cost Accountant for review, recount verification, and formal approval before General Ledger vouchers can be committed.
5. Core Inventory Counting vs. Warehouse Management (WMS) Cycle Counting
Candidates must distinguish between basic Inventory management counting and advanced WMS mobile cycle counting:
| Capability | Inventory Management Counting Journals | Warehouse Management (WMS) Cycle Counting |
|---|---|---|
| Primary Interface | Web client back-office forms (Item counting > Counting). | Warehouse Management Mobile App (handheld barcode scanners). |
| Execution Mode | Batch line generation, manual paper sheets, or desktop data entry. | Mobile work directed to workers via guided menu items and location sweeps. |
| Warehouse Scope | Non-WMS (basic warehousing) or hybrid warehouses. | Advanced WMS-enabled warehouses (Location profile enabled for warehouse management). |
| Cycle Count Plans | Controlled by Counting groups (Period, Zero, Minimum). | Controlled by Cycle count plans, Work templates, and Location directives. |
| Blind Counting | Enforced via Tag counting journals or hiding on-hand columns. | Configurable parameter directly on mobile device menu items. |
| Discrepancy Handling | Back-office counting approval workflow. | Cycle count thresholds generating 'Cycle count work requiring review' in WMS. |
A medical device distributor must execute an annual wall-to-wall physical inventory audit for regulatory compliance. Internal auditors require that physical counts be conducted using sequentially numbered paper tags, that counters have no access to system on-hand quantities (blind count), and that every missing or damaged tag number be formally reconciled before any inventory adjustments can be posted to the General Ledger. Which Dynamics 365 Supply Chain Management feature meets these audit requirements?
A company wants to automate cycle counting for fast-moving electronic components. The inventory policy requires that these components be physically counted every 30 days. In addition, if the physical inventory of any of these items drops to zero at any point in time, the system must immediately trigger a counting journal line to verify that the warehouse location is truly empty. How should the functional consultant configure Dynamics 365 Supply Chain Management?
A warehouse supervisor reviews a posted counting journal for an industrial motor. The system recorded an on-hand quantity of 50 units, but the physical count revealed only 46 units. The motor uses FIFO valuation, and the item model group has physical and financial ledger integration enabled. What inventory transaction status and General Ledger posting occur upon posting this journal line?