Inventory Valuation: Why Your ERP is a Liability

Executive Summary

---

The familiar problem of month-end write-offs

It’s the third day of the month-end close. The Financial Controller walks into your office, looking less than thrilled. The numbers from the warehouse don’t match the ledger, again. There’s a multi-million-pound discrepancy between the value of stock the WMS says is on hand and the value the ERP is carrying on the balance sheet.

The result is a painful, unplanned inventory write-off. It’s a direct hit to your net margin and leads to awkward questions from the board. You’ve invested in a modern data stack, you have smart engineers, and you have expensive ERP and WMS systems. It can feel like you've just found a way to automate the same old problem, generating incorrect data more quickly than before.

This isn't a simple reporting error, it's a problem with how the systems work together. The issue lies with the process, not the people.

Why warehouse and finance records rarely match

This is a common problem I see in most scaling manufacturing or consumer goods businesses. It’s not because your teams are doing a bad job, it’s because your systems are speaking two different languages without a translator. The problem isn't usually the tools themselves, it's that the business logic is vague and lives in spreadsheets and people's heads, instead of being written down and automated.

In my experience, the disagreement comes from three areas:

Timing and delays: Your WMS records a pallet as 'received' the moment it's scanned at the loading bay. Your ERP, however, might only recognise that stock when an invoice is processed by accounts payable, which could be days or even weeks later. In that gap, the stock exists physically but not financially, creating a blind spot in your Operational Visibility.

Different units of measure: The warehouse thinks in 'eaches', 'inner cases', and 'pallets'. Finance thinks in pounds sterling. The conversion logic, how many 'eaches' are in a 'case' and the standard cost of that 'case', is often managed in a sprawling master spreadsheet. When that logic changes, it rarely gets updated in both systems at the same time. This can lead to small rounding errors that become significant when they compound over millions of units.

Systems being out of sync: A forklift driver marks a pallet as 'damaged' in the WMS instantly. The process to trigger the corresponding financial write-down in the ERP is often a manual, multi-step workflow. The operational state and the financial state are constantly out of sync. Without a solid way for the WMS and ERP to integrate, this gap is almost inevitable.

How to build a single source of truth for stock

Throwing more analysts at this problem is like trying to patch a dam with chewing gum. It’s better to stop the leak at its source. The fix, in my experience, isn't to replace your ERP or WMS. It's to build a dedicated reconciliation layer that sits between them and acts as the Single Source of Truth.

This usually involves two steps:

Standardise the process and metrics: First, we have to get everyone to agree on the process. We sit down with Operations, Finance, and Supply Chain to map the entire stock lifecycle. We define, with absolute clarity, the exact trigger point for every status change: 'Received', 'Quarantined', 'Available for Sale', 'Written-Off'. This isn't really a technical task, it's more of a negotiation disguised as process mapping. The result is a single, agreed-upon definition for every metric.

Turn the logic into code: Once we have that agreement, we translate that business logic into code. We build a data model that takes the raw data feeds from both the WMS and ERP. It then applies the newly standardised rules, creating a single, unified view of inventory. This new layer becomes the definitive source for all Financial Reporting. The original systems still do their jobs, but they no longer have the final say on the numbers.

The trade-offs of this approach

Putting this in place isn't a painless exercise. It requires you to slow down for a short time to build the foundations that will allow you to speed up later. The biggest cost is often the political capital needed to get department heads to give up their private spreadsheets and agree to a single, central logic. Operations will need to adapt their processes, and Finance will need to trust the new automated outputs. There will be some resistance, because you are taking away the ambiguity that allows for plausible deniability.

The result: from reactive audits to predictable operations

Once this new layer is in place, the month-end fire drill becomes a thing of the past. Inventory valuation becomes a predictable, automated process. Your audit becomes a formality, not a forensic investigation. Most importantly, you can finally trust your balance sheet. This allows you to move from basic reporting to more advanced Supply Chain Analytics, optimising cash flow and stock turnover based on data that reflects reality.

You stop patching the report and finally fix the production line.