Late numbers are history, not control

Reporting lag is the metric nobody tracks

Businesses track revenue, margin and cash. Few track how long it takes for those figures to become visible. Yet the reporting lag determines whether the financials are a control mechanism or a historical record.

Consider a project-based business where costs are booked at month-end close, twenty days after the month ends. A project that started going wrong in the first week of the month is visible to the owner roughly seven weeks later. By then the overrun is not a decision — it is a fact to be absorbed.

Where the lag actually comes from

The delay is rarely in the accounting work itself. It accumulates upstream:

• Capture delay. Field reports, timesheets and supplier invoices arrive days or weeks after the work they describe.
• Entry delay. Documents sit in a queue waiting for someone to key them in.
• Reconciliation delay. Discrepancies are investigated at close rather than as they appear.
• Assembly delay. Reports require manual export, merge and formatting before anyone can read them.
• Distribution delay. The finished report waits for a scheduled meeting rather than reaching the person who needs it.

Each stage is defensible on its own. Together they produce a number that arrives too late to be useful, and no single person owns the total.

Multi-entity structures compound every one of these

With several related operating entities, the delays do not simply add — they wait on each other. Consolidated reporting cannot complete until the slowest entity closes. Intercompany balances must agree before anything reconciles. Shared costs need allocating before entity-level margin means anything.

The common result is that entity-level numbers exist and consolidated numbers are produced quarterly, by hand, under protest. Cash is managed account by account rather than across the structure, which is precisely the view an owner of multiple entities needs and is least likely to have.

What shortening the lag involves

Capture at the point of work

Timesheets, field reports and receipts entered where and when the work happens, not transcribed later from memory or paper. This single change removes more lag than anything downstream.

Continuous reconciliation rather than close-driven

Match transactions as they arrive and route only the exceptions to a person. Reconciliation done continuously is a small ongoing task; deferred to close, it becomes the bottleneck that defines the close date.

Automated assembly and distribution

If a report requires manual assembly, its frequency is limited by someone's availability. Automated assembly makes weekly or daily reporting cost the same as monthly.

A chart of accounts designed for the decision

Many charts of accounts are built for tax filing and then asked to answer operational questions they were never structured for. If project margin, entity margin or cost per unit of output is the decision being made, the structure has to support it directly rather than through a spreadsheet built after the fact.

Controls proportionate to the business

Internal controls should match the size and risk of the operation, not an audit template. Over-specified controls get bypassed under pressure, which is worse than having fewer controls that are consistently followed.

A reasonable target

The right lag depends on what decisions the business actually makes and how quickly. A project-based construction business that commits labour weekly needs cost visibility weekly. A business making quarterly capital decisions may not.

The useful exercise is to list the decisions that get made, note how often each one occurs, and check whether the supporting number arrives before or after the decision point. Any number that arrives after is a record, not a control — and should either be accelerated or stop being treated as management information.

Ask what decision each report supports, and whether it arrives before that decision has to be made. Reports that fail this test are documentation, not management.