Why the Year-End Count Still Matters
A perpetual inventory system records every receipt, issue, completion, and shipment as it happens. In theory, the system quantity is always right. In practice, it drifts: a material issue that was never keyed, a pallet put away in the wrong bin, scrap thrown out without a transaction, a box counted as a single unit.
The year-end physical inventory is when the books meet the shelves. For a manufacturer, it does three jobs at once:
- It supports the audit. When inventory is material, auditing standards such as ISA 501 and AU-C 501 expect the auditor to attend the count and test it, so your count procedures become part of the audit evidence.
- It sets the closing balance. Year-end inventory flows straight into cost of goods sold, so every error in the count is an error in the year's gross margin, and in next year's opening balance.
- It checks condition, not just quantity. The count is the one time every item is seen. Damaged, obsolete, and slow-moving stock found on the floor may need to be written down to net realizable value.
A well-planned count takes a day or two. A poorly planned one can hold up the year-end close for weeks, and the problems it finds usually started months earlier.
Plan the Count Before Year End
Most count problems are decided before anyone picks up a tag. Start planning four to six weeks out, and work through these steps in order:
- Agree the date and approach with your auditorCount on the balance sheet date if you can. If you count earlier, agree how movements between the count and year end will be rolled forward and tested.
- Define the scopeList every location that holds your inventory, including third-party warehouses, outside processors, consignment stock at customer sites, and goods in transit.
- Clean up open transactionsPost outstanding receipts, issues, and completions, close finished work orders, and put away anything sitting in receiving or staging.
- Plan the freezeAgree when receiving, production issues, and shipping stop, and how any urgent movement during the count will be documented.
- Organize teams and tagsAssign every location to one two-person team, and use pre-numbered tags or scan-based count sheets so that every count can be traced.
- Set recount thresholdsDecide in advance which differences, by value and by quantity, trigger a recount by a second team.
- Brief everyoneCover counting instructions, units of measure, partial packs, how to record work in process, and who to ask when something is unclear.
Decide What Belongs in the Count
A count measures what you own, not what happens to be on your floor. The two are often different, and shipping terms and consignment agreements decide which side of the line an item falls on.
Count and Include
- Stock in your warehouses, stores, and on the shop floor
- Work in process on open work orders
- Your goods at third-party warehouses or outside processors
- Your consignment stock held at customer sites
- Goods in transit bought on FOB shipping point terms
- Goods in transit to customers sold on FOB destination terms
Exclude or Count Separately
- Vendor-owned consignment stock on your site
- Customer-owned material held for processing
- Goods sold where control has already passed to the customer
- Goods in transit bought on FOB destination terms
- Supplies and maintenance items expensed when bought
- Items already written off as scrap
Rejected, quarantined, and obsolete items should still be counted, but tagged and recorded separately so they can be reviewed for write-down instead of being mixed in with good stock.
Counting Work in Process
Raw materials and finished goods are counted in units. Work in process is harder, because it is partly converted and its value depends on how far each job has progressed. It is also where most manufacturers find their largest differences.
- Reduce it before the count. Finish and close as many work orders as you can, and avoid starting new ones in the days before the count. Less WIP means less to estimate.
- Count by work order, not by part. Record the work order number on each tag, so that material on the floor can be matched to the job it was issued to.
- Record the last completed operation. WIP is valued by how far each job has progressed, so counters need to note which routing step each job has passed, not just the quantity.
- Tie the floor to the open order list. Every open work order should be found on the floor, and every job on the floor should have an open order. A mismatch usually means a job was finished but never completed in the system, or an order was closed while material was still on the floor.
The costing behind this, including how material, labor, and overhead build up on a work order, is covered in our guide to WIP accounting for manufacturers.
Running the Count
On the day, the goal is a count that you, and your auditor, can trust without counting again. A few controls do most of the work:
- Freeze movements and record cut-off. Stop receiving, issues, and shipping at the agreed time, and record the last receiving and shipping document numbers so that finance can check cut-off later.
- Count blind. Counters record what they find without seeing the system quantity. A counter who knows the expected answer tends to find it.
- Use two-person teams. One person counts and one records, or both count independently and compare before the tag is submitted.
- Control every tag. Each pre-numbered tag is accounted for at the end of the count: used, voided, or unused. A missing tag is a missing count.
- Recount before you release. Differences above the threshold are recounted by a different team before the area goes back to operations.
Investigate Differences Before You Adjust
Once the count is compared with the system, it is tempting to post the net difference and move on. That is usually a mistake. A count difference is a symptom, and many of them are not missing stock at all. Common causes:
- Unrecorded issues: material moved to a work order without a transaction, so raw materials look short and WIP looks long.
- Unrecorded completions: finished jobs still open in the system, so WIP looks short and finished goods look long.
- Location errors: stock in an overflow area or the wrong bin, missed by the count or counted twice.
- Unit-of-measure errors: a box of 50 counted as one, or the reverse.
- Cut-off errors: receipts or shipments recorded on the wrong side of the count.
- Unreported scrap: material spoiled on the shop floor and thrown away without a transaction.
- True shrinkage: theft, damage, and loss that no transaction can explain.
Work through the largest differences first. For each one, look at the transactions posted around the count date before you accept it as shrinkage.
A Worked Example: From $42,000 to $10,000
A manufacturer carries $4.8 million of inventory at year end. The first comparison of count to book shows a net shortage of $42,000: raw materials and WIP short, finished goods over. Here is what the investigation found, and how each correction changed the remaining difference.
Differences are counted value minus book value. Each correction updates the book balance, which changes the difference that remains.
What the Example Shows
Posted blind, the full $42,000 would have gone to cost of goods sold as shrinkage. Raw materials would have been written down for a receipt that was sitting in an overflow bin. The work orders that consumed the missing material and produced the extra finished goods would still carry the wrong cost. And $26,000 of scrap would have looked like theft or loss, not a reporting gap on the shop floor.
Investigated, the picture is different. One finding was a counting error. Two were missed transactions that moved cost between inventory categories with no effect on profit. One was scrap that needs a process fix. Only $10,000 was true shrinkage.
A count difference is a question, not an answer. Post it only once you know what it is.
Booking the Adjustments
Once each difference is explained, book it to the account that matches its cause. Transaction errors are corrected with the transaction that was missed. Only true losses reach the P&L as shrinkage, scrap, or write-downs.
Under standard costing, count differences are valued at standard cost, consistent with how the item moved all year. Under FIFO or weighted average, they are valued at the item's carrying cost. Our guide to inventory valuation methods for manufacturers explains how each method affects the result.
The condition review matters as much as the quantity. Under IAS 2, and under ASC 330 for inventory measured using FIFO or average cost, inventory is carried at the lower of cost and net realizable value. Stock found damaged, obsolete, or far in excess of demand should be reviewed for write-down before the year is closed.
If you counted before year end, roll the count forward: start from the counted balance, add receipts and production, subtract issues and shipments up to the balance sheet date, and check the result against the ledger. The same subledger-to-ledger tie-out used in the month-end close applies here.
Can Cycle Counting Replace the Year-End Count?
For many manufacturers, yes, with conditions. Cycle counting checks part of the inventory every week or month, so that every item is counted during the year without shutting down operations. A common approach is ABC classification: high-value or fast-moving A items are counted most often, typically monthly or quarterly, B items less often, and C items once or twice a year.
Auditors can rely on cycle counts instead of a full year-end count, but only when the program is strong enough to support the year-end balance. That usually means:
- Every item is counted at least once during the year, on a documented schedule
- Record accuracy is measured and stays within agreed tolerances
- Differences are investigated and approved before adjustments are posted
- The process is controlled well enough for the auditor to test it
Agree the approach with your auditor well before year end. Moving from a wall-to-wall count to cycle counting is a decision to make early in the year, not in December.
Common Year-End Count Mistakes
- Counting before cleaning up. Open work orders, unposted receipts, and stock in staging areas turn into count differences that take days to explain.
- Letting counters see the system quantity. A count is only useful as a check if it could have disagreed with the system.
- Forgetting stock at other sites. Inventory at third-party warehouses, outside processors, and customer sites belongs in the count, and is easy to miss.
- Posting the net difference as one entry. It hides transaction errors, misstates category balances, and makes shrinkage look larger than it is.
- Skipping the condition review. Obsolete and damaged stock counted at full cost overstates inventory on the balance sheet.
- Treating the count as a one-day event. The differences show where the process breaks during the year. Fix those causes, or the same differences will be back next year.
A Year-End Count Timeline
Adjust the timing to your size and number of sites. The sequence matters more than the exact weeks.
- Six weeks beforeAgree the count date, scope, and approach with your auditor, and confirm third-party and consignment locations.
- Four weeks beforeIssue count instructions, assign teams and areas, set recount thresholds, and start clearing open work orders and unposted transactions.
- One week beforeRun down WIP where possible, tidy and label locations, separate stock you do not own, and trial count one area.
- Count dayFreeze movements, record cut-off documents, count blind, and recount differences above threshold.
- The week afterInvestigate differences, post corrections, book shrinkage and write-downs, and tie the inventory subledger to the ledger.
How an ERP Should Support the Count
Most of the effort in a year-end count comes from the gap between what happened on the floor and what the system recorded. An ERP cannot count stock for you, but it should make the count shorter and the differences easier to explain:
- Count sheets come from live locations and quantities, not from a spreadsheet export
- Counts are captured by scanning, bin by bin, at the point of count
- Differences are reviewed and approved before stock levels change
- Approved adjustments reach finance as the same transaction, with no re-keying
- Cycle counts run through the year, so the year-end count confirms rather than discovers
Axolt runs inventory, warehouse, production, and finance on one data model inside Salesforce. Teams can run rolling cycle counts or full stocktakes with barcode scanning or the Salesforce mobile app, and review and approve variances in Salesforce before stock levels are updated. Because finance works from the same transactions the warehouse recorded, the year-end count becomes a check on the records, not a rebuild of them.
Frequently Asked Questions
When should a manufacturer do its year-end physical inventory count?
Ideally on the balance sheet date, or as close to it as operations allow. If the count is taken earlier, movements between the count date and year end have to be rolled forward and tested, so agree the date with your auditor in advance.
What is a blind count?
A count in which the counter does not see the quantity the system expects. It stops counters from simply confirming the system figure, which makes the result more reliable.
How do you count work in process?
By work order. For each open order, record the quantity on the floor and the last completed operation, so the job can be valued at the cost accumulated to that point. Reducing WIP before the count makes this much easier.
Can cycle counting replace the annual physical inventory?
Often, yes, if every item is counted during the year, record accuracy is measured and within tolerance, and differences are investigated before posting. Agree the approach with your auditor before you drop the year-end count.
How should inventory count adjustments be recorded?
Correct transaction errors, such as missing issues or completions, with the transaction that was missed. Book only true losses as shrinkage, usually through cost of goods sold, and review damaged or obsolete stock for write-down to net realizable value.
The Bottom Line
The year-end physical inventory is when the ledger is tested against what is really on the shelves and the shop floor. Most of the work happens before count day: a clear scope, clean transactions, and a plan everyone understands.
Investigate before you adjust. Many count differences are transaction errors, not missing stock, and each one points to a process that broke during the year. Fix those, and next year's count has less to find.
Make Your Next Count a Confirmation
Axolt connects warehouse, inventory, production, and finance on Salesforce, so counts, variances, and adjustments run on the same records your teams use every day.
Book a Demo