Menu

FOUNDER PERSPECTIVE · GAURAV GUPTA

Why Ageing Tells You What Is Late—but Not Why

Last reviewed: 5 November 2026

Ageing is indispensable accounting information. It is not, by itself, a diagnosis, a forecast or an operating plan.

Ageing

Who · How much · How old

Revenue Intelligence

Where · Why · Who owns it · What next · What evidence · When cash

Ageing measures time, not causation

A receivables ageing report answers important questions: who owes money, how much and for how long. Those are necessary controls. But two invoices in the same bucket can have entirely different economic realities.

One may be approved and scheduled for payment. Another may be genuinely disputed. A third may lack proof of delivery. A fourth may sit with a counterparty whose condition has deteriorated.

Why management can get false comfort

Portfolio totals can move even while persistent old balances remain. New sales can change the denominator. One large receipt can improve a headline number while unresolved exceptions continue rolling forward.

GGA's Revenue Realization Gap research separately examines persistence and movement rather than assuming a single period-end ratio tells the whole story.

Add the operating layer

For material receivables, management needs to know the lifecycle stage, cause, evidence, internal and external owner, next action, commitment quality, expected realization and escalation status.

This is the difference between a rear-view financial report and a forward-looking operating view.

Ageing plus intelligence

Ageing remains the financial backbone. Revenue Intelligence does not replace it; it explains it. The two should work together.

Ageing: amount, customer, invoice, days outstanding.

Revenue Intelligence: where, why, who, what next, what evidence, when cash is credibly expected and what should change if the expected event fails.

Use exceptions, not noise

Not every invoice deserves the same depth of investigation. Portfolio segmentation should concentrate management and specialist effort where exposure, persistence, cause or counterparty risk makes the exception material.

The principle

Ageing tells you what is late. Revenue Intelligence tells you why it is late and what should happen next.

That distinction is central to moving receivables management from activity reporting toward decision support.

A worked example: two invoices, same bucket

Invoice A and Invoice B are both 120 days old and each is ₹25 lakh. Invoice A has been approved, appears in the customer's payment schedule and has a named treasury event next week. Invoice B is disputed, the underlying service acceptance is incomplete and the original salesperson has left.

Ageing treats them as equals. An operating view does not. Invoice A needs monitoring of a known event. Invoice B needs reconstruction of evidence, ownership of the dispute and a different realization plan.

This is why prioritisation by ageing alone can misallocate effort.

The counter-argument: adding fields creates administrative burden

It can, if every invoice is forced through the same level of analysis. The answer is segmentation. Routine invoices should flow with minimal intervention. Material exceptions receive deeper diagnosis.

Revenue Intelligence should reduce noise by concentrating attention, not create a larger reporting bureaucracy.

What a CFO can do on Monday

  • Add a cause field to the top material overdue items.
  • Add next event and evidence fields rather than another free-text comment.
  • Separate “payment-ready” from “problem unresolved.”
  • Track ageing migration and persistence, not only month-end totals.
  • Create an exception view for the CEO instead of sending the full ageing ledger.

Evidence, interpretation and limits

GGA distinguishes financial benchmarks, operating experience and management principles. Benchmark figures are population-level observations and do not prove causation or predict the outcome of an individual receivable. Company-specific conclusions require the underlying account, transaction and counterparty evidence.

What changes when management treats this as a system

The immediate benefit of a system view is not a new report; it is a different sequence of questions. Instead of beginning with the age of the invoice, management begins with the commercial obligation, the customer's payment requirements, the evidence available, the counterparty condition and the next observable event. That sequence makes it easier to distinguish a normal timing issue from a recurring process failure or a genuine credit problem.

It also creates a cleaner division of responsibility. Sales does not have to become a collection department. Finance does not have to resolve product issues. Operations does not have to own credit risk. Each function owns the part of the cause it can actually change, while one operating layer keeps the invoice moving across functions.

What this does not mean

A stronger receivables operating model does not mean chasing customers before payment is due, escalating every delay, or replacing commercial judgement with a rigid workflow. B2B credit exists for legitimate commercial reasons, and important customers can have complex approval processes.

The objective is to make those processes visible enough that the company knows the difference between expected timing and avoidable delay. Where the evidence is incomplete, uncertainty should be shown rather than hidden behind a convenient forecast date. Where a customer has a legitimate dispute, resolution should come before escalation. Where the counterparty risk has changed, the credit response should change with it.

A practical management cadence

A useful cadence separates routine exposure from exceptions. Routine invoices continue through the normal organisation. Material exceptions are reviewed by cause, evidence, owner and next event. Repeated exceptions are then analysed for the upstream rule that should change: a sales approval, documentation requirement, customer-onboarding control, invoice-readiness check or escalation trigger.

The measure of maturity is therefore not the number of calls made. It is whether the same causes recur, whether expected realization becomes more credible and whether the organisation is creating fewer legacy receivables while resolving the old ones.

Three principles I would keep

First, treat this as an operating question before it becomes a reporting question. A company cannot manage what it has not distinguished: process delay, dispute, internal failure, counterparty weakness and deliberate non-payment require different responses.

Second, evidence should improve as the receivable becomes more material or more difficult. A casual promise may be enough for a routine invoice; a large persistent exposure needs a clearer payment-process position, documentary support, named ownership and a defined escalation path.

Third, the case is not complete when cash arrives. Management should ask what created the delay and whether the same commercial behaviour can create another legacy receivable. The value of realization is the cash; the value of Revenue Intelligence is the institutional learning that remains after the case closes.

Email GGA gg@ggaindia.co.in