The Working Capital Data Framework
One overdue invoice is four different objects. To the collector it is a worklist item. To the manager it is a roll-rate cohort. To the CFO it is a component of DSO. To the board it is capital. Same record, four altitudes, four different right answers about what to measure, how often, and which chart tells the truth.
On the charts below. Every figure in them is invented. They are shaped to make the form legible and to demonstrate the trap named in that cell — not to tell you what good looks like, which is industry-specific and not something a framework can settle.
What to measure
The mistake
Every cell has one that is close to universal.
Latency test
Rule two, applied to the cell you have open. If your data moves slower than the decision, the number is an ornament.
Six rules that hold across every cell
Chart grammar
Chart type is not a styling decision. It encodes the comparison you are asking the reader to make, and choosing the wrong one is how an honest number becomes a misleading slide. Each row is drawn below it on illustrative data, taken from the first cell that calls for that form. Usage count is how many of the 24 cells ask for it.
| Form | Use it when you want to | Why | Cells |
|---|
How to use this without building anything
Take your existing reporting pack and lay it over the grid. Three failure modes show up almost immediately, and none of them need a new tool to fix.
1. Empty cells
Most packs light up the AR column and leave payables nearly dark. That is not an oversight about reporting — it is an oversight about authority. Receivables are influenced; payables are decided. A working-capital review that cannot see discount capture or the gap between DPO and contractual terms is missing the half of the cycle management directly controls.
2. Cells filled at the wrong altitude
The classic is the aging report sent to collectors, and its mirror, transaction detail in a board pack. Both are real numbers delivered to an altitude that cannot act on them. The test is simple: can the person reading this make a decision from it, with the authority they hold, inside the horizon they work in? If not, it belongs one floor up or one floor down.
3. Metrics that cannot move before the decision does
Run the latency test above across your pack. A weekly collections priority built on a monthly extract, a cash position refreshed overnight when payments run at four, a credit limit review on an annual calendar for an account whose score moved last Tuesday. These are the cheapest fixes available, because the fix is usually a schedule change rather than a system.
What this framework does not settle
It does not tell you what good looks like — the thresholds are industry-specific, and a 60-day receivable cycle that is routine in capital goods would be alarming in food retail. It says nothing about data quality, which is upstream of everything here and quietly determines whether any of it is true. And it assumes the four altitudes exist as separate roles; in a company of forty people one person occupies all four, in which case the value is not the grid but the reminder to switch hats deliberately rather than looking at the collector's queue and calling it a strategy review.
The related tools on this site sit inside specific cells: the working capital and DSO calculator is the CFO row of the collections column, splitting DSO into the half you chose and the half you are suffering. The corporate rating scorecard and equipment finance scorecard are the operator cell of the credit column. The stress forecaster is the board row of cash.