The count lifecycle
A count moves through three statuses in order. Posting is atomic, so a count is never left half-applied.Creating a count
Every count is scoped to one location. From there you can narrow it two ways, both optional: A full count covers an entire location. A cycle count covers selected bins or one item type. Scope determines which lines Alforse generates; both use the same count document and lifecycle. When you generate the lines, Alforse aggregates on-hand from the item ledger into one line per item, storage unit, and lot. It excludes Rejected and Consumed lots — a count never lists stock that has already been scrapped or used up. Each line records the frozen system quantity; that snapshot is what the variance is measured against later, not live on-hand.Counting
A counter walks the lines and enters what they find. Two rules matter: Counted quantities are non-negative, so a count can never drive on-hand below zero.What posting does
Posting reconciles against the frozen snapshot, not live on-hand. For each counted line Alforse computes the variance ascounted − systemQuantity and posts a single adjustment for it:
- A shortfall books a “Negative Adjmt.”, an overage a “Positive Adjmt.”, written to the with the document type “Inventory Count”.
- Cost layers are maintained on every variance. When accounting is turned on, one journal is written for the whole post, debiting or crediting inventory against the inventory adjustment account, valued at the item’s approved cost. A count that raises a line above its snapshot needs an approved valuation for that line.
- For a tracked lot, the same variance is applied to the entity’s quantity — the delta is added, not set — so any receipt or shipment that posted between the snapshot and the post survives the count rather than being clobbered.