Value a stock count: 3 layers to check against books

Key takeaways

Match counted quantities to purchase records.
Keep quantities and unit costs visible for each layer.
Reconcile using your applicable valuation method.
Investigate differences before recording adjustments.

Why one total hides the layers

That figure goes on the books, and it has to be checked against what the records say should be there. The problem is that the single total is the result of several smaller steps. If you only look at the final number, you cannot tell which step caused a difference.

If a shop buys the same product more than once, prices may change between deliveries. Stock bought early may have cost one amount, and stock bought later may have cost another. When you walk the shelves, the units look identical. Underneath, they can belong to several cost layers, and each layer carries its own unit cost.

This post walks through a method that keeps those layers visible. You split the count into layers, value each layer, add the layers together, and compare the result with your books. The steps are the same whether you use a spreadsheet, a paper record, or inventory software. The worked example comes from an accounting textbook, but the logic applies to a small shop as much as to a large one.

What the count does and does not tell you

The count answers one question: what is physically there? ERPNext's documentation on stock reconciliation puts it plainly: "In this process, the actual physical stocks are checked and recorded in the system." ( ERPNext, Stock Reconciliation)

That sentence describes quantities. It does not describe cost. A count tells you that a certain product is on the shelf, but not whether it came from the spring delivery or the autumn one. The cost has to come from your purchase records, which is why the count and the books need to be read together.

Treat the count as the physical side of the reconciliation and your purchase and sales records as the cost side. Neither is complete alone. When they agree, the total is credible. When they disagree, the gap tells you where to look.

Good preparation makes the rest easier. Before the count, stop or pause movements as far as you can, so nothing is sold or received while people are counting. Give each counter a printed list with product codes, not only product names, so the same item is not recorded under two labels. Write units of measure clearly, because a case and a single unit are easy to mix up on a rushed sheet. For the physical count, follow the stock reconciliation steps.

Who does what on count day

A full count goes better when each person has one job. One person should own the list and the final totals. Counters should work from that list and record what they see, without guessing at anything they cannot read. A second person, ideally not on the counting team, should spot-check a sample of bins against the list.

Keep the roles simple:

Coordinator: prepares the lists, decides the cut-off time for movements, and collects the sheets.
Counters: count each location, mark anything damaged or unlabeled, and note any item they cannot identify.
Checker: recounts a sample from each area and reports any mismatch before the sheets are closed.
Records keeper: matches the counted quantities to the purchase and sales records and prepares the cost layers.

When a counter finds something that does not fit the list, such as an unfamiliar item or a bin with two products, they should flag it rather than force it into a line. Those flags identify items needing investigation.

Why one product can have several costs

When you buy the same item at different prices, you end up with stock at different costs sitting side by side. OpenStax's specific-identification example assigns costs to three groups of ending inventory. Keep the method visible and apply it the same way every time.

In that example, specific identification gives an ending inventory value of $8,895. For a shop with bins of similar goods, keeping cost groups visible can help with checking. You can track cost in lots or batches. For this worked example, each group contains units valued at the same unit cost.

Zoho's inventory guide describes a FIFO Cost Lot Tracking report. It explains that an inventory adjustment "will be reflected in the respective items' details page and in the FIFO Cost Lot Tracking report." ( Zoho Inventory, Inventory Adjustments) In plain terms, the adjustment appears in both places.

Whatever tool you use, the principle is the same. Keep each layer's quantity and unit cost on its own line until the very end.

A worked example with three layers

The clearest example of three layers comes from OpenStax's accounting text, which values ending inventory using specific identification. The ending inventory in that example is made up of three groups: 10 units at $21 each, 65 units at $27 each, and 210 units at $33 each. The text gives the total as $8,895 ( OpenStax, Principles of Financial Accounting, section 10.2).

Build the total one layer at a time. Multiply the units by the unit cost for each layer, write down each layer's value, then add the results.

Work each layer on paper or in a spreadsheet cell so that every figure can be checked. A reader who follows the three multiplications and the addition will arrive at the same total the textbook reports.

Notice what the layers reveal. The third layer has the most units and the highest unit cost, so it carries a large share of the value. A single average cost would hide that concentration, and that is exactly the kind of detail you need when a count does not match the books.

The layer method also protects you from a common shortcut: multiplying the total quantity by one average price. An arbitrary average can give a different total; the quantity-weighted average of these ending-inventory layers reproduces their total exactly but omits the breakdown.

Illustrative example: value a layer

Suppose a counted layer contains 10 units at an illustrative unit cost of $2. Multiply 10 by $2 to get an illustrative layer value of $20. Keep the quantity, unit cost, and value together so the calculation can be checked.

Connect the count to the cost of sales

The same example shows how the ending figure links to cost of goods sold. The text states: "Subtracting this ending inventory from the $16,155 total of goods available for sale leaves $7,260 in cost of goods sold this period." ( OpenStax, Principles of Financial Accounting, section 10.2)

Goods available for sale is the starting balance plus what was bought. In the example, the purchases recorded for the period total $13,005, and that is the credit entry that balances the adjustment ( OpenStax).

That chain is a useful check. Compare the calculated cost of goods sold with an independently recorded cost-of-goods-sold balance when available; sales revenue or quantities alone are not comparable cost figures. You do not need to be an accountant to run this check. You need the three totals and one subtraction.

The example uses the periodic method.

Check the total against the books

Once the layers are valued, compare the total with the balance in your records. In the OpenStax example, the ending inventory should be $8,895. The text says the adjustment required "an entry to increase merchandise inventory by $5,745" ( OpenStax).

The $5,745 is the routine increase from the $3,150 beginning inventory balance to $8,895 ending inventory, rather than an unexplained stock discrepancy. For an unexplained difference, do not simply post it. Ask what it is made of. Only then should the adjustment be recorded.

Use this order each time:

First, total the counted units for each product, layer by layer.
Next, value each layer with its unit cost from the purchase record.
Then add the layers to get the counted value of each product.
Add the products together to get the shop total.
Compare the shop total with the book balance and write down the difference.
Investigate the difference before recording any change.

When the numbers do not agree

If a gap exists between the count and the books, investigate it. The useful question is where it came from. Common causes include:

Counting errors: a unit was counted twice, or a case was counted as single units.
Missing deliveries: stock arrived but the purchase was not entered, or was entered at the wrong quantity.
Unit cost errors: a supplier price changed and the record was not updated, or a cost was mistyped.
Unrecorded sales or transfers: stock left the shop or moved between locations without a record.
Damage or loss: breakage or theft that nobody wrote down.

Work through these using the layer view. A keying error in cost often shows up as a layer whose value looks wrong for its unit cost. A counting error often shows up as a quantity that does not fit the normal sales pattern. Not every gap can be traced, and that is acceptable, as long as you record why an adjustment was made and who approved it.

Set a limit for how long you spend on a gap. If the cause is still unclear after a reasonable search, record the adjustment with a note that says so. A clear note is far more useful later than a guess dressed up as a fact.

Recording the adjustment

Once the difference is explained, record it so the reason stays visible. Use the adjustment entry for that purpose, and keep the reason in the note.

Keep a separate sheet for adjustments with the product, layer, quantity, unit cost, value, date, and reason. Before posting, use the inventory adjustment checks.

Have someone other than the person who did the count review each adjustment before it is posted. This is a simple control, and it provides an opportunity to identify keying errors before they reach the books.

Keep the method the same next time

Layers only help if you use the same method every time. Changing the cost approach between counts makes the totals hard to compare. If you do change the method, note the date and the reason, and keep the old figures for reference.

Keep a short record for each count:

the date, and who counted and checked,
the total counted value,
the book balance before adjustment,
the difference and its explanation,
the adjustment that was recorded and who approved it.

Over several counts, these notes show patterns. If the same product shows gaps every time, investigate receiving, recording, and recurring counting errors. That is where a small change in routine usually pays off.

Today, choose one product and match its counted quantities to its purchase costs before checking its value against your books.

Common questions from owners

Do I need cost layers if my prices never change? If prices stay the same, the layers will have the same unit cost, and the work is simpler. Keep the layer habit anyway. Prices do change, often without much notice, and a shop that already tracks lots will adjust without a scramble.

Is one average cost good enough? Yes, if average cost is your applicable inventory valuation method. An average alone hides the breakdown you may need to explain a difference. Reconcile using that method and retain supporting detail.

Who should approve the final total? The owner or a manager who was not involved in the counting should approve it. The person who counted should not also approve the adjustment, because that removes the check.

What if the count takes longer than planned? Keep the cut-off clear, and record any movements that happen during the count separately. Do not let the count drift without notes, because the longer it runs, the harder it becomes to match the sheets to the records.

Summary

The finished total is only as good as the layers behind it.