Menu

FOUNDER PERSPECTIVE · GAURAV GUPTA

The Four Reasons Revenue Gets Stuck

Last reviewed: 16 November 2026

An overdue invoice is a symptom. GGA's Four Causes framework helps management investigate the commercial system behind it: Product or Service, Sales Process, Customer Selection and Customer Payment Process.

01

Product / Service

Did delivery and performance meet the obligation?

02

Sales Process

Were terms, promises and documents right?

03

Customer Selection

Was the exposure appropriate?

04

Payment Process

Do we know how this customer pays?

Why a cause framework matters

Ageing can tell you that an invoice is 60, 120 or 240 days old. It cannot tell you why. Without a diagnosis, organisations can repeat the same calls, promises and escalations while the underlying cause remains untouched.

The Four Causes framework is not a scoring model. It is a disciplined starting point for investigation and ownership.

01 — Product or Service

Was delivery complete? Was the specification correct? Did installation, performance, quality, service level or acceptance meet the commercial obligation?

When the answer is no—or the evidence is unclear—the receivable may be the financial expression of an operating problem. Finance cannot solve that alone. The relevant operational owner has to close the underlying issue and create evidence that supports payment.

02 — Sales Process

Were payment terms, customer requirements, commercial commitments, schemes, deductions, documentation and billing conditions understood before revenue was booked?

A verbal commitment can later become a deduction. A missing PO condition can become an invoice rejection. A project invoiced before its contractual milestone can sit in ageing even though the customer's objection is predictable. Sales-process intelligence converts these recurring surprises into preventable controls.

03 — Customer Selection

Did the business create exposure to a counterparty with the capacity, intent and governance to pay as expected? Credit decisions are not only about a financial statement at onboarding. Exposure can change, counterparties can deteriorate and actual payment behaviour can reveal information that external data did not.

GGA's counterparty intelligence combines Desk check, Site Verification and a Combined Assessment with the client's own receivables experience.

04 — Customer Payment Process

A perfectly valid invoice can remain unpaid because the seller does not understand how that customer converts it into cash. Receipt, GRN or service confirmation, validation, technical approval, accounts payable, budget, treasury and payment-run timing can all matter.

This is why the customer's payment process is part of the seller's revenue process.

More than one cause can be true

The framework should not force an invoice into a single box. A product issue can create a dispute; an undocumented sales commitment can delay approval; a weak counterparty can use a process issue to postpone payment.

The practical output is: cause → evidence → owner → next action → next event → escalation → learning.

The management implication

When recurring receivables are classified by cause, management can see whether it has a collections problem, a product problem, a commercial-governance problem, a credit problem or a payment-process intelligence problem.

That distinction determines where management attention and process redesign should go.

A worked example: one invoice, several causes

A project invoice can appear as a 150-day receivable. Investigation may show that commissioning evidence is incomplete (Product/Service), a documentation deviation agreed during the sale was never recorded for Finance (Sales Process), the customer has begun stretching all suppliers (Customer Selection / changing risk), and the invoice is not yet in the customer's approved payment run (Payment Process).

Calling the customer more often does not resolve all four. Operations may need to complete evidence; Commercial may need to document the deviation; Credit may need to reconsider further exposure; Finance or the realization team may need to map and move the approval path.

The framework matters because it assigns the right problem to the right owner.

The counter-argument: every overdue is ultimately a collection problem

At the final stage, cash must indeed be collected. But defining every delay as a collection problem can send the organisation toward the wrong intervention. A genuine quality dispute cannot be solved by reminder frequency. A weak counterparty requires different action from an invoice waiting for a GRN.

The Four Causes do not replace collections. They improve the diagnosis that precedes collection, escalation or process correction.

What management can do on Monday

  • Take the 20 largest overdue items and classify the likely cause or causes.
  • Mark every item where the cause is still unknown; unknown is a valid exception status.
  • Assign internal owners for Product/Service and Sales Process causes.
  • Escalate Customer Selection cases to credit/risk rather than leaving them only with collections.
  • Map the payment process for the customers that repeatedly create unexplained delay.

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.

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