Measuring the value
Fragmented data across departments is usually treated as a technical inconvenience. Seen through a finance lens, it is a silent tax eroding cash every day.
All it needs is headcount and department count. Revenue, orders, receivables and inventory are derived from those with ordinary ratios — every one of them editable.
Derived from your scale
Scale and labour
Orders
Receivables
Inventory
This is an estimate, not a promise. It only means anything if you take a real baseline before you change anything — see the three-step path at the end.
When sales keeps its own tracker, the warehouse runs on bin cards or a personal spreadsheet, and accounting sits on separate software, the company pays in three currencies: wasted hours reconciling, interest on money collected late, and losses from stock that is not where the system says it is.
This piece gives the method and the formulas to turn those "intangible" benefits into real cash — the kind of number you can defend in front of a board. And because this site does not believe in numbers you cannot check, the estimator above lets you enter your own scale, change every assumption, and see each step of the arithmetic.
The first version of this estimator had a mistake worth naming, because it is the easy mistake to make when quantifying anything: receivables, inventory value and order volume were left as free-standing inputs. All three are revenue-scale quantities, not headcount-scale ones — so tripling the headcount moved the total by a few percent. The output looked detailed while the two fields that mattered most barely steered it.
The fix is to chain them, each link an ordinary finance ratio you can check yourself:
All four leaks then scale with size: A with the number of department pairs and order volume, B with the people re-keying and the orders keyed wrong, C with receivables, D with orders lost and inventory held. Move headcount from 60 to 200 and the total goes from roughly 815m to roughly 2.7bn đ — proportionate, instead of the +22% the first version produced.
Every link in that chain is an editable field. If your revenue per employee is nothing like the default — and distribution is nothing like manufacturing — change that field before reading the total.
The estimator models this differently, and the difference is the point: instead of adding up people, it counts the pairs of departments that must be cross-checked. Four departments is six pairs; six departments is fifteen. Reconciliation cost does not grow with the number of departments, it grows with the number of pairs — which is why a company that "only added one more team" finds month-end got noticeably longer.
With one consistent system the receivables statement goes out on the 1st instead of the 15th. Days saved cut straight into interest.
This is usually the largest line, and the one most often missing from an ERP proposal — because it does not belong to any department. It belongs to the balance sheet.
Estimated for a company with 50–100bn đ of revenue:
| Bottleneck | Nature of the waste | Recovered per year |
|---|---|---|
| Month-end cross-checking | Wasted hours | 50–80m đ |
| Repeated manual entry | Surplus steps and rework | 100–140m đ |
| Late receivables reconciliation | Cash sitting out in the market | 200–600m đ |
| Stock and books diverging | Tied-up capital and lost orders | 150–300m đ |
| Total cash benefit | 500m – 1.12bn đ / year |
Improving an ERP until it holds a single source of truth is not technology spending. It is the act of recovering money the business is already dropping each year, through the gaps in its own operations.
The example figures illustrate a company with 50–100bn đ of revenue. They are not taken from any client's system.
Read next
The answer is usually stated as a principle, and a principle is hard to argue with and equally hard to believe. This piece turns it into money, and names the three numbers it stands on — set all three to zero and the paths cost the same.
The outbound plan almost always starts as a shared sheet, and it genuinely works until a few hundred orders a day. The cure is not forcing people back into ERP forms — it is putting the spreadsheet inside the system.
Every partner has its own print standard, so every document detours through Word. Mapping templates to customers sounds like a small interface tweak — measured, it pays for itself inside a month at mid size.