SAPFree worksheetPDF, Excel, Word exportSAP Business OneDiscrete ManufacturingAll SAP Business One tools

SAP Business One Cycle Count Variance Worksheet

Cycle counts only improve accuracy if variances are reviewed before they are posted. This worksheet values each variance, shows the percentage and records what you decided to do.

Free, optional. Reopen it on any device.

Download:

Variance qty	Variance value	Variance
-2	-$25	-0.8%
-40	-$126	-2.7%
0	$0	0%
5	$41	5.2%
-50	-$48	-7.8%

Net variance value

-$157

Largest variance

5.2%

Lines counted

Net adjustment to post

-$157

Set your own tolerance by ABC class, for example tighter for A items. In Business One the posting itself is made from the inventory counting and posting documents; use this sheet to review variances and get approval before posting.

Stock variance analysis

Ask about analysing recurring stock variances from your ERP transaction history.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use the worksheet

Enter the item, warehouse or bin, ABC class, system quantity, counted quantity and unit cost. The sheet calculates variance quantity, value and percent. Choose an action for each line: accept, recount, or investigate. Review the net adjustment before anything is posted, and have a second person approve large values.

The calculations

Variance quantity is counted minus system. Variance value is that quantity times unit cost, so shortages are negative. Variance percent is variance quantity divided by system quantity, shown as zero when the system quantity is zero to avoid a meaningless figure. A system quantity of zero with stock found needs investigation, not just a posting.

Negative means stock missing
Positive means unrecorded stock
Value matters more than percent on expensive items

Using it with Business One

Business One records counts through inventory counting documents and posts differences with an inventory posting document, which creates the stock adjustment and the related journal entry. The count should be taken while the area is frozen or movements are recorded, otherwise transactions between the system snapshot and the count create false variances. Counting by bin and batch where used gives more useful results than totals per item.

Common mistakes

Posting every variance without looking for the cause, counting during receipts and issues, and using one tolerance for all items. A recurring variance on the same item usually points to a process error such as wrong unit of measure at receipt, unrecorded scrap, or issuing to production without a transaction.

Frequently Asked Questions

What tolerance should I use?

It depends on item value and risk. Many sites use a tight tolerance for A items, often near zero for high-value stock, and wider ones for low-value C items. Set it with finance and write it down.

Should I recount before posting?

Yes for variances above tolerance. A second count by a different person removes most errors. Only investigate and post when two counts agree or the cause is understood.

How often should I cycle count?

A common approach counts A items more often than B and C. Frequency should reflect value, movement and error history. The goal is to find process errors early, not only to correct the numbers.

Why does zero system stock matter?

It suggests receipts that were never booked or negative stock that was corrected. The percent cannot be calculated, so the sheet shows zero. Treat any such line as an investigation item.

Netray can surface recurring stock variances and likely causes from your ERP transaction history, with a read-only AI layer.

Talk to an Expert Explore More Free Tools