How to Run a Cycle Count in SyteLine
How do I do a cycle count in SyteLine?
Also searched as
- SyteLine cycle count entry
- SyteLine ABC cycle counting setup
- how to print cycle count tags SyteLine
- CSI cycle count variance posting
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.
Applies to: SyteLine 8.x/9.x, CloudSuite Industrial (CSI) 10.x-11.x, Mongoose and classic UI
Run a cycle count in SyteLine
- 1Confirm every item has an ABC class assigned on the Item record, since ABC class drives the default count frequency.
- 2Open Inventory > Cycle Count > Generate Cycle Count and choose a selection method: ABC class, location, or specific items.
- 3Print Cycle Count Tags or a worksheet for the floor count, or export the list for a handheld/RF count tool.
- 4Perform the physical count and record the counted quantity against each tag or location.
- 5Enter counted quantities in Cycle Count Entry, matching tag number to item, lot, and location.
- 6Review the Cycle Count Variance report before posting, and flag any variance beyond tolerance for a recount.
- 7Recount items outside tolerance rather than posting a large, unexplained variance straight to the GL.
- 8Post the cycle count to update on-hand inventory and generate the adjustment transaction against the inventory adjustment account.
- 9Track count accuracy over time to retune ABC frequency for items that consistently miss tolerance.
ABC class drives count frequency
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
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
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
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.
Common 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.
How an ERP-grounded AI assistant handles this
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.
Frequently asked questions
Does cycle counting freeze inventory transactions on the item?
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?
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?
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?
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.
Related
How to Run a Cost Rollup in SyteLine
Run Item Cost Rollup from Product Definition > Costing > Cost Rollup, select the site and item range, run it in Simulate mode first to review variances, then run it live to post new standard costs to Item records and the Costed Bill of Material.
How-toHow to Close a Job Order in SyteLine
Close a job order from Production > Job Orders once every routing operation is reported complete and the finished quantity has been received, then run Close Jobs to post the remaining WIP balance to variance and lock the job from further transactions.
How-toHow to Run MRP in SyteLine
MRP in SyteLine runs from Planning > MRP Processing as either a full Regenerative run or a Net Change run against demand from customer orders, forecasts, and safety stock; results appear as planned orders and Action Messages in the Planner Workbench.
How-toSyteLine Customer Order to Invoice: Step by Step
A SyteLine customer order flows from Order Entry through pick, pack, and Customer Shipment, then to invoicing, either through the Auto Invoice batch utility or manual Invoice Entry, posting revenue and relieving inventory once the shipment is confirmed.
Error fixFixing SyteLine's 'Object reference not set to an instance of an object' error
This is a generic .NET NullReferenceException surfacing through the SyteLine IDO Runtime, not a SyteLine-specific error code. It almost always means a form, script or IDO method referenced a field, row or object that came back null, usually after a customization, a missing related record, or a view/IDO method call before the form finished loading. Turn on detailed client logging and check the most recent customization or form event first.
Error fixDiagnosing and fixing SyteLine session timeout errors
SyteLine session timeouts come from one of three independent layers: the IDO Data Service session timeout on the app server, the IIS/application pool idle timeout for the web (Mongoose Web) client, or a load balancer/proxy idle timeout in front of a CloudSuite hosted environment. Fixing the wrong layer is the most common mistake - you need to identify which layer is actually expiring the session before changing anything.
AI for ERPAI for Infor SyteLine and CloudSuite Industrial
Add grounded AI to Infor SyteLine or CloudSuite Industrial: natural-language answers, agents over IDOs and ION, on-prem or CloudSuite deployment.
AI for ERPOn-Prem AI for CloudSuite Industrial, Without the Multi-Tenant Cloud Move
Add generative AI to CloudSuite Industrial without moving to Infor's multi-tenant cloud. On-prem private LLM options for CSI, with governance and audit built in.
Stuck on Infor SyteLine (CloudSuite Industrial)?
Talk to engineers who work inside Infor SyteLine (CloudSuite Industrial) every week, and who build private AI that answers these questions from your own ERP data.