# How to Run a Cycle Count in SyteLine > Source: https://netray.co/erp-help/syteline-how-to-cycle-count > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Cycle counting in SyteLine runs through Inventory > Cycle Count: generate a count list by ABC class or location, print or enter tags, key the counted quantities into Cycle Count Entry, then review the variance report before posting the count to update on-hand quantity. ## Kind how-to ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module Inventory / Cycle Counting ## Query How do I do a cycle count in SyteLine? ## Alternate Queries - SyteLine cycle count entry - SyteLine ABC cycle counting setup - how to print cycle count tags SyteLine - CSI cycle count variance posting ## Applies To SyteLine 8.x/9.x, CloudSuite Industrial (CSI) 10.x-11.x, Mongoose and classic UI ## Steps ### Run a cycle count in SyteLine **Items:** - Confirm every item has an ABC class assigned on the Item record, since ABC class drives the default count frequency. - Open Inventory > Cycle Count > Generate Cycle Count and choose a selection method: ABC class, location, or specific items. - Print Cycle Count Tags or a worksheet for the floor count, or export the list for a handheld/RF count tool. - Perform the physical count and record the counted quantity against each tag or location. - Enter counted quantities in Cycle Count Entry, matching tag number to item, lot, and location. - Review the Cycle Count Variance report before posting, and flag any variance beyond tolerance for a recount. - Recount items outside tolerance rather than posting a large, unexplained variance straight to the GL. - Post the cycle count to update on-hand inventory and generate the adjustment transaction against the inventory adjustment account. - Track count accuracy over time to retune ABC frequency for items that consistently miss tolerance. ## Sections ### ABC class drives count frequency **Body:** A items are typically counted most often because they carry the highest dollar value or usage, C items least often, with B items somewhere in between. The classification lives on the item master and can be set manually or generated from a usage/value analysis. This is the same field the Generate Cycle Count selection uses to decide which items are due for a count on a given cycle. Sites that never revisit ABC classification end up counting slow-moving C items on the same schedule as fast-moving A items, which wastes floor time without improving inventory accuracy where it actually matters. ### Tags vs mobile and RF counting **Body:** Many sites have moved from printed paper tags to RF or handheld scanning for the physical count, but both approaches post through the same underlying Cycle Count Entry tables once the counted quantities come back in. Lot- and serial-controlled items add complexity either way, because the count has to reconcile at the lot or serial level, not just the item and location level. ### Variance tolerance and investigation **Body:** Before posting, compare the counted quantity against the system quantity and check it against whatever tolerance the site has set, either as a percentage or a fixed unit threshold. A large variance is usually a symptom of an earlier problem, such as an unissued material transaction, an un-received purchase order still sitting on the dock, or a mis-keyed transaction, not real physical shrinkage. Posting large unexplained variances without investigating first hides those underlying process problems and makes the next count just as unreliable as the last one. ### Posting and its GL impact **Body:** Posting a cycle count generates an inventory adjustment transaction at the item's current cost, moves on-hand quantity to match the counted quantity, and updates the item's last-count date and transaction history. The adjustment shows up on the standard inventory valuation and adjustment reports, so it is visible to Finance the same way any other inventory transaction is. ## Pitfalls - Counting while transactions are still posting against the same item or location produces false variances. - Not freezing picks and put-away on the location during the count window lets the floor keep moving inventory mid-count. - Blank or duplicate lot numbers on lot-controlled items cause the count entry to fail to match against the tag. - Posting a large unexplained variance without investigation hides a real process problem, such as a backflush error, instead of surfacing it. - ABC classification never gets re-evaluated, so fast-moving items are undercounted relative to the risk they carry. - Treating a cycle count miss as a one-off instead of tracking accuracy trends over time misses the chance to fix a root cause. ## Ai Angle Instead of pulling the Cycle Count Variance report and manually eyeballing which locations keep failing tolerance, ERPray can be asked which items have missed cycle count tolerance three counts running and pull that straight from count history - a pattern most planners only catch at year-end physical inventory. ## Faq ### Does cycle counting freeze inventory transactions on the item? **Answer:** SyteLine does not automatically lock the item during a count. Best practice is to pause picks and put-away on the counted location for the physical count window so the count reflects a stable snapshot rather than a moving target. ### Can I cycle count by warehouse location instead of by item? **Answer:** Yes. Generate Cycle Count supports a location-based selection so you can walk a physical area of the warehouse rather than chase individual items scattered across multiple locations one at a time. ### What happens to variance dollars when I post a cycle count? **Answer:** The system posts the quantity difference at the item's current cost to the inventory adjustment account, and the transaction shows up on the standard inventory valuation and adjustment reports for that period. ### How do I handle a count on a lot-controlled item with multiple lots in one location? **Answer:** Count and enter each lot separately in Cycle Count Entry. The system reconciles variance at the lot level, not just the item and location level, so lot quantities need to be broken out individually during entry. ## Search terms syteline cycle count, csi cycle count entry, syteline abc cycle counting, syteline cycle count tags, syteline inventory variance posting, infor syteline cycle count tolerance, syteline rf cycle count, syteline lot cycle count --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json