Workflow leakage rarely announces itself. It shows up first as a number that drifted by 4 percent and nobody noticed because the trend looked like normal seasonality. Then the drift compounds. Then a close cycle stretches by three days. Then a quarter ends with a surprise that, traced back, started 90 days earlier in a handoff that everyone assumed was working.
The CFO's job is to catch the drift before it becomes the surprise. The instinct is to watch the lagging indicators harder, but the lagging indicators are by definition late. They tell you the leak has already cost you. The leading indicators tell you the leak is starting. The combination is what gives you 6 weeks of warning instead of zero.
Here are five lagging indicators most CFOs already track, four leading indicators most do not, and how each connects to a specific workflow handoff that, when leaking, eventually shows up in the financial statements.
Lagging Indicator 1: DSO Creep
Days Sales Outstanding moves up two days. Then three. Then five. By the time the trend is obvious in the AR aging report, the leak has been running for 60 to 90 days. Tracing it back, the cause is almost always at one of three handoffs: the invoice was generated late because the project closed without the trigger, the invoice was generated correctly but routed to the wrong AP contact at the customer, or the collection follow-up cadence broke because the AR clerk left and the queue was never picked up.
The leak is in the workflow, not in the customer relationship. Fix the workflow and DSO recovers within 60 days. Push harder on collection without fixing the underlying handoff and DSO holds steady at the new elevated level.
Lagging Indicator 2: AR Aging Shifts
The 60 to 90 day bucket starts to grow as a percentage of total AR. This is more specific than DSO creep. It tells you that some invoices are getting stuck in a particular phase rather than every invoice slipping uniformly. The cause is usually a single dispute pattern, a single customer behavior, or a single missing reconciliation step.
Trace it: pull the invoices in the 60 to 90 day bucket and look for common attributes. Same customer? Same product line? Same approval workflow? The leak is in whatever workflow those invoices share. Fix that one workflow and the bucket shrinks.
Lagging Indicator 3: Close-Cycle Drag
The close used to take 7 days. Now it takes 9. Then 11. The team blames it on more transactions. Sometimes that is true. Usually it is not. The drag is from manual reconciliation steps that were always there but used to be tolerable when the volume was lower.
Close-cycle drag is one of the cleanest indicators of workflow leakage because the cost is concentrated in a small group of people who can articulate exactly where the time is going. Ask the controller and the senior accountant where their close days are spent. The answer will name the specific reconciliation steps that are leaking time.
Lagging Indicator 4: Expense-Category Surprises
The marketing line item came in 18 percent over budget. The IT line came in 22 percent over. Nobody flagged it during the month because the approvals were happening in Bill.com and the budget tracking was happening in the ERP, and the two were not talking until close.
The leak is in the categorization workflow. Expenses get coded by whoever is approving them, often without a clear category convention. By close, the categorization has drifted from what the budget was built against. Trace the surprise back and you usually find that 60 percent of the variance was misclassification, not actual overspend.
Lagging Indicator 5: Hiring-Cycle Bloat
The headcount plan called for 12 hires this year. The actual hires came in at 16. The HR director is sure each one was justified. The CFO is sure the plan was the budget. Both are right, and the gap is the leak.
The leak is in how requisitions get approved. Each one looks reasonable in isolation. The cumulative effect is invisible because nobody is tracking the running total against the plan. By the time the year-end accounting catches the gap, the four extra hires are on the payroll and not coming off it.
Now the Leading Indicators
The five lagging indicators above are useful, but they tell you the leak has happened. The four leading indicators below tell you the leak is starting. The window between leading and lagging is roughly six weeks for most workflows. That is enough time to fix the issue before it shows up in the statements.
Leading Indicator 1: Handoff Delay Time
Measure the time between when one step in a process completes and when the next step starts. Healthy workflows have median handoff times under 24 hours. Leaking workflows have median handoff times of 3 to 7 days, with long tails of 14 to 30 days for the steps that nobody owns.
Pull this measurement from the timestamps in your CRM, project tool, and ERP. The handoffs with the longest median delays are where your leakage is starting. Six weeks later, those delays show up as DSO creep, close-cycle drag, or whatever lagging indicator the workflow feeds into.
Leading Indicator 2: Exception Ratio
Track the percentage of transactions that route to a manual review queue versus the percentage that flow through automated. Healthy workflows have exception ratios under 10 percent. Leaking workflows have exception ratios of 25 to 40 percent.
The exception ratio rises before the close cycle stretches. When 30 percent of invoices need manual review, the close team is doing 30 percent more work than the system was designed for. They will keep up for a few cycles. Then the cycle stretches and the lagging indicator triggers.
Leading Indicator 3: Manual Reconciliation Hours
Have the controller log the hours their team spends reconciling between systems each week. Healthy operations have manual reconciliation under 10 hours per week. Leaking operations creep up through 15, 20, and 30 hours per week before the close cycle visibly stretches.
This indicator is uncomfortable to track because it requires the team to admit how much manual work they are doing. The first measurement often shocks both the CFO and the controller. The shock is the value: it forces the conversation about which reconciliations belong in code versus which ones genuinely require judgment.
Leading Indicator 4: Executive Context-Switching Time
Track how often you, as CFO, switch tabs or tools to answer a question about the business. The number itself does not matter as much as the trend. If you are switching more than you were a quarter ago, the underlying data is becoming harder to access. Six weeks later, your reports will arrive later because the same friction is hitting the analyst who builds them.
This is the indicator most CFOs dismiss as personal annoyance rather than systemic signal. We have started to think it is the most underrated leading indicator in finance. Your discomfort is the leakage announcing itself before the lagging indicators trigger.
Tracing Each Indicator Back to a Workflow
Each of the nine indicators above maps to a specific workflow handoff. The audit pattern is straightforward: take the indicator, identify the systems involved, and walk the handoff between them. The leak is almost always at the seam, not inside the system.
For example: DSO creep maps to the project completion to invoice generation handoff. The systems involved are the project tool and the ERP. The seam is whoever is supposed to trigger the invoice generation when the project hits a billing milestone. If that trigger is manual and the trigger person is overloaded, the seam leaks.
The fix at the seam is either an AI agent that watches for the milestone and triggers the invoice automatically, or a unified dashboard that surfaces the missing trigger so a human can act. Either approach closes the leak before DSO creeps further. We walk through the full audit pattern in our workflow leakage audit guide.
Building the Dashboard That Watches All Nine
If your finance team is going to watch nine indicators continuously, the work has to be automated. Doing it by hand is more work than the close itself. The pattern that works is a CFO dashboard that pulls the leading and lagging indicators from the underlying systems and surfaces them in one view, with thresholds that turn amber or red when the trend turns.
The dashboard is not exotic. It is a thin layer on top of your existing CRM, ERP, and project tool, with the indicator math done in code rather than in someone's head. The CFO opens it Monday morning and gets the picture in 90 seconds.
For the architecture, see our Apps and Dashboards page. For the CFO-specific framing, see Heed AI for CFOs. For the build approach, the 30-day operations diagnostic maps the leakage points first so the dashboard targets the actual leaks rather than vanity metrics.
The Bottom Line
The lagging indicators tell you the leak cost you money. The leading indicators tell you the leak is starting. The fix is the same in both cases: identify the seam, close the handoff, and make the workflow enforceable. The difference is whether you find out from your dashboard six weeks early or from your audit committee six weeks late.
Most CFOs we talk to are watching the lagging side carefully and the leading side not at all. Adding the leading set is the cheapest leverage available in the finance function. The data is already in your systems. It just needs to be surfaced in a working view that the CFO can actually use.