Measuring the value
Measuring the ROI of a single source of truth
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.
Estimated cash recovered per year
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
Assumptions — click to see and change every number
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.
How the estimator derives everything from scale
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:
Orders / year = revenue ÷ average order value
Receivables = revenue × DSO ÷ 365
Inventory = revenue × (1 − gross margin) ÷ turns
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.
1. Four cash leaks caused by fragmented data
- The reconciliation tax. Accounting, the warehouse and sales lose dozens of hours a week opening files, comparing rows, and arguing about whose number is right.
- Duplicate-entry waste. One document gets typed again by each department. It costs hours, and it raises the error rate, which costs invoice cancellations and re-issues.
- Cash and decision latency. Receivables that do not agree push the reconciliation statement one to two weeks past close. Money arrives later, which means more interest paid.
- Book and physical stock diverging. Sales commits against phantom stock and orders get cancelled; conversely the warehouse believes it is out and over-orders, tying up capital.

2. Four formulas that turn this into cash
A. Reconciliation tax → evaporated payroll
Loaded cost per hour = real pay (gross + social insurance + allowances) ÷ 176 hours
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.
B. Duplicate entry → surplus hours and rework
C. Collection delay → saved cost of capital
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.
D. Stock mismatch → tied-up capital and lost orders
3. Summary
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 |
4. A three-step path to measuring it for real
- Take a baseline before you improve anything. Record how many days close currently takes, time the meetings spent resolving mismatches, note the cancellation rate caused by stock errors, and your DSO. Without this step every later number is an anecdote.
- Lock the point where data is created. Eliminate the habit of exporting to Excel and working outside the flow. Configure approvals and validation so data is entered once, at source.
- Audit again after 90–180 days. Compare close time, interest saved and hours freed, against the same group of people and the same season as the baseline.
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
-
Make-up orders from a supermarket chain: one PO in 26, and only the receipt tells
A store raises a PO and receives it the same day to pay back goods already delivered without one. The PO header still says "deliver tomorrow", so a make-up order is easily delivered twice and the goods behind it never invoiced. Measured on 1,258 POs, with a matching threshold chosen from the data.
-
One screen for a delivery crew's day: 43% of notes posted before the truck delivers, and returns nobody can record
The warehouse posts the delivery note as the truck leaves; the driver's screen read it as "done" and locked the returns field. Over 14 days, early-posted notes had a signed slip 1% of the time and a returned quantity 0.4%, against 89% and 15.5%. Reopen the note for the driver, add a vehicle & fuel tab that reads photos with AI — what that saves a month.
-
Exceptions that arrive with a reason: 82 slips to check, but only 68 need someone to think
When invoices to supermarket chains raise themselves, the remaining slips reach the accountant with a reason in words. Read by what has to be done, the reasons fall into three kinds: judgement, wait, one-time fix. Measured on 291 slips, and the price of the minutes spent searching.