To measure working capital at group and entity level, track days sales outstanding (DSO), days inventory outstanding (DIO), days payables outstanding (DPO) and the cash conversion cycle for each entity and for the group, using one definition, intercompany items removed, and balances taken as at each period end rather than today.
This guide is for CFOs, VPs of finance and controllers who report working capital across several legal entities or business units and no longer trust a single blended number. It explains which KPIs to track, which data an ERP has to hold to calculate them, and why an average of entity ratios can point you at the wrong problem. The data requirements are the same whether you buy a packaged system or build one; for a custom build, see enterprise ERP development. Definitions here are general practice. Confirm any definitions that feed covenants, lender reporting or published accounts with your auditor.
Key takeaways
- Working capital KPIs only compare across entities if every entity uses the same formula, the same day-count and the same balance basis.
- Group figures must exclude intercompany receivables, payables, sales and purchases, otherwise ratios are distorted.
- A simple average of entity ratios is usually wrong. Compute group ratios from group totals, and show entity ratios beside them.
- Track the same KPIs by entity, by business unit, by customer or supplier segment and by currency, so a problem can be located.
- The ERP must keep period-end snapshots and payment history. Without them, trends cannot be rebuilt.
- Real-time dashboards are useful only when the underlying definitions are agreed first.
Which working capital KPIs should a group track?
A group should track six core measures: DSO, DIO, DPO, the cash conversion cycle, trade working capital as an amount, and the overdue share of receivables and payables. Add collection effectiveness and inventory ageing if the business is receivable-heavy or stock-heavy. Each one answers a different question about where cash is held.
| KPI | Common formula | Question it answers |
|---|
| DSO | Trade receivables / revenue x days in period | How long do customers take to pay? |
| DIO | Inventory / cost of sales x days in period | How long is cash held in stock? |
| DPO | Trade payables / cost of sales x days in period | How long do we take to pay suppliers? |
| Cash conversion cycle | DSO + DIO - DPO | How many days is cash tied up between paying and collecting? |
| Trade working capital | Receivables + inventory - payables | How much cash is tied up in trade balances? |
| Overdue share | Overdue balance / total balance | Is the average hiding late payers? |
| Collection effectiveness index | (Opening receivables + credit sales - closing receivables) / (opening receivables + credit sales - closing current receivables) x 100 | Of what was collectable in the period, how much did we collect? |
In the collection effectiveness row, closing current receivables means receivables not yet past due. Some teams compute DPO against purchases instead of cost of sales, and some use average balances over the period instead of the closing balance. Either can be reasonable. What matters is that the definition is written down and applied to every entity.
What data does the ERP need to hold?
The ERP needs transaction-level dates and statuses, plus history, because a closing balance alone cannot produce a trend or an overdue analysis. It must be able to rebuild ageing, stock value and payment timing as at any past date for every entity. At a minimum it should hold:
- Invoice date, due date, payment terms and payment date for every customer and supplier invoice, so ageing can be rebuilt as at any date.
- Entity, business unit and currency on every document, with transaction, entity and group currency amounts.
- An intercompany flag or counterparty entity, so group figures can exclude those items.
- Credit notes, disputes and write-offs linked to the original invoice.
- Inventory quantity and value as at a date, with valuation method, not only today's stock.
- Period-end snapshots, frozen when the period closes, so a restated number is visible as a restatement.
- Customer and supplier hierarchies, so a parent group's balances across entities can be seen together.
- Fiscal calendars, if entities have different year-ends or period definitions.
If any of these live only in spreadsheets, the KPI will be rebuilt by hand each month and will drift. Our ERP reports every finance team needs guide covers the supporting reports, and business dashboards people actually use explains how to define and refresh KPIs.
How do you avoid misleading averages?
Compute group ratios from group totals, never by averaging entity ratios. A simple average gives a small services entity the same weight as a large manufacturer and hides the entities that hold most of the cash. The cleanest method is to rebuild the ratio from the consolidated numerator and denominator after intercompany items are removed.
Four other traps recur:
- Intercompany items left in. Group receivables look larger than what outsiders owe.
- Mixed day counts. One entity uses 360 days and another 365.
- Seasonality. A year-end balance can flatter a business that peaks mid-year. Show trailing averages next to the closing figure.
- Currency translation. Ratios are less sensitive to currency than amounts, but translating the numerator and denominator at different rates distorts them. Use consistent rates.
Worked example: three entities and one group
All figures are illustrative, in USD thousands, using annual revenue, closing balances and a 365-day year. They are not benchmarks.
| Entity | Revenue | Cost of sales | Receivables | Inventory | Payables |
|---|
| E1 Distribution | 60,000 | 48,000 | 9,000 | 8,000 | 6,000 |
| E2 Services | 30,000 | 18,000 | 7,500 | 0 | 1,500 |
| E3 Manufacturing | 40,000 | 28,000 | 4,000 | 10,000 | 5,000 |
E3 sold 15,000 of goods to E1 within the year. E3's receivables include 2,500 owed by E1, and E1's payables include the same 2,500 owed to E3. For the group, that intercompany revenue and cost of sales, and the 2,500 receivable and payable, are removed. (This example ignores unrealised profit in stock for simplicity.)
Entity ratios (days).
| Entity | DSO | DIO | DPO | Cash conversion |
|---|
| E1 | 54.8 | 60.8 | 45.6 | 70.0 |
| E2 | 91.3 | 0.0 | 30.4 | 60.8 |
| E3 | 36.5 | 130.4 | 65.2 | 101.7 |
| Simple average (do not use) | 60.8 | 63.7 | 47.1 | 77.5 |
Group, built from external totals. Revenue is 60,000 + 30,000 + 40,000 - 15,000 = 115,000. Cost of sales is 48,000 + 18,000 + 28,000 - 15,000 = 79,000. Receivables are 20,500 - 2,500 = 18,000. Payables are 12,500 - 2,500 = 10,000. Inventory is 18,000.
| Measure | Group |
|---|
| DSO | 57.1 |
| DIO | 83.2 |
| DPO | 46.2 |
| Cash conversion | 94.1 |
| Trade working capital | 26,000 |
What the example shows.
- The simple average cash conversion figure is 77.5 days; the group figure is 94.1. The average understates the problem because the manufacturer holds more than half of the group's stock, yet counts as one third of the average.
- E2 has the worst DSO at 91 days, but its receivables are 7,500 of 18,000, and it carries no stock. Collections are a real issue there, but stock is the larger cash lever for the group.
- Trade working capital is the same, 26,000, with or without the intercompany pair, because the receivable and payable cancel. The ratios still change, which is why you remove the pair before calculating them.
- Finance would next ask whether E3's 130-day stock cover reflects slow-moving lines, planned build-up or an inventory valuation issue.
How should the KPIs be sliced?
Slice by the dimension where a decision can be made. Entity is the first slice because it matches legal and management accountability. Then add business unit, customer segment, supplier category, country and currency. For receivables, add a view by top customers and by age band. For inventory, add a view by warehouse and by age band.
A dashboard should let a reader move from group to entity to customer or item in a few clicks, and the numbers should match at every level. If a drill-down total differs from the headline, the definitions are not shared.
What does real-time reporting mean for working capital?
Real-time here means the dashboard reads from the live ledger and subledgers without a manual export, so a change in an invoice or a payment shows quickly. It does not mean every number is final. Period-end figures are still frozen at close, and the dashboard should label which view the reader is seeing: live, or as at a closed period.
When you evaluate platforms for multi-unit dashboards, do not ask who is best. Ask each vendor to show your own data model answering these questions:
| Question | What good looks like |
|---|
| Can the dashboard exclude intercompany items? | A switch or built-in rule, with the rule visible |
| Can I see group and entity side by side? | Same definitions, same screen |
| Can I reproduce a past period? | Snapshots or date-effective queries |
| Is the drill-down to documents consistent with totals? | Totals reconcile to the ledger |
| How fresh is the data and how is it refreshed? | A stated refresh method, not "real time" alone |
| Can each business unit see only its own data? | Row-level permissions |
Check each vendor's current documentation for these capabilities. This guide does not assess named products.
When this is the wrong approach
Detailed group working capital KPIs are the wrong first investment if the entities still use different charts of accounts, if intercompany balances do not tie, or if invoice dates are not captured reliably. Fix the data first, or the dashboard only reports the inconsistencies faster. Likewise, a single-entity business with a few customers can track DSO and stock days in a spreadsheet and does not need a group framework. If the ERP itself cannot hold the data, start from the legacy software modernization assessment.
Glossary: DSO, days sales outstanding; DIO, days inventory outstanding; DPO, days payables outstanding; cash conversion cycle, DSO plus DIO minus DPO; trade working capital, receivables plus inventory minus payables, as used in this guide; intercompany, between entities of the same group.
How Timeline Digital approaches this work
When a group wants working capital reporting that matches its own entity structure, Timeline Digital begins in the Plan step by writing down the KPI definitions and the data each entity must supply, and the schedule is set from those requirements. Timeline Digital is a custom software development company founded in 2013 and headquartered in Islamabad, Pakistan, delivering remotely. A free pilot of 2 to 3 key modules lets your team test the result before the final agreement, and code ownership passes on full payment. See our custom ERP software page for the approach.