Menu

FOUNDER PERSPECTIVE · GAURAV GUPTA

Your Customer's Payment Process Is Part of Your Revenue Process

Last reviewed: 5 November 2026

Raising an invoice is not the final operational step in a sale. The seller still depends on the customer's receipt, validation, acceptance, approval, accounts-payable and treasury process before cash can arrive.

SubmitReceipt evidenced
→
ValidateRequirements met
→
AcceptIssues resolved
→
ApprovePayment-ready
→
CashReconciled

What happens after the invoice leaves your ERP

The internal sales process may appear complete at invoicing, but the customer's process is only beginning. The invoice can require acknowledgement, delivery evidence, GRN, service confirmation, milestone certification, portal submission, tax validation, technical approval, financial approval and inclusion in a payment run.

Different invoice types can follow different paths even inside the same customer.

Why reactive follow-up wastes the credit period

A common operating model waits until the due date, discovers that cash did not arrive and only then asks the customer what is wrong. If the answer is a missing document, unresolved acceptance issue or rejected portal submission, the business has effectively allowed the problem to age invisibly.

Revenue Assurance reverses that sequence: understand the payment requirements early and check that the invoice is progressing through them.

The invoice lifecycle needs observable events

For each material invoice, the useful fields are not merely invoice date, due date and amount. Management also needs stage, blocker, responsible stakeholder, evidence, next action and next expected event.

Where the customer does not provide a date, do not invent one. Missing information is itself a management signal.

Supplies, services and projects are different

A supply invoice may depend on delivery and GRN. A service invoice may require service confirmation or SES. A project invoice can depend on measurement, milestone certification or commissioning. AMC, retention, EMD, Bank Guarantee and Security Deposit releases can have their own conditions.

A serious Invoice Lifecycle system therefore allows multiple commercial objects rather than forcing every receivable through one generic workflow.

The Control Tower

GGA's Control Tower connects Exposure → Lifecycle Stage → Blocker → Owner → Next Action → Evidence → Expected Realization → Actual Realization → Escalation → Learning.

The purpose is not more reporting. It is to give the organisation one operational view of what has to happen before the financial asset becomes cash.

The strategic implication

Once the customer's payment process is treated as part of revenue management, collections changes character. It becomes less about asking “When will you pay?” and more about knowing where the invoice is, what prevents the next event, who can resolve it and whether the expected cash date is evidence-based.

A worked example: a service invoice that is “not due” operationally

A service provider may issue an invoice with a contractual due date 30 days later. Internally, the clock starts at invoice date. The customer's AP team, however, may not process the invoice until a service-entry sheet is approved. If the service confirmation is missing for 18 days, the seller has already lost most of the nominal credit period before the invoice becomes payment-ready.

A lifecycle view exposes the missing event immediately. The action is not an early payment demand; it is completion of the legitimate prerequisite so that the customer's payment clock can actually run.

The counter-argument: we cannot manage the customer's internal process

A supplier cannot control a customer's authority, budget or treasury decision. But it can understand requirements, maintain evidence, identify where the invoice sits, resolve its own blockers promptly and escalate through agreed channels.

That distinction matters. GGA tracks where the invoice sits and works to move it through the process; the payer retains approval and payment.

What Finance can do on Monday

  • Choose one major customer and draw the actual invoice-to-payment path.
  • Separate invoice types—supply, service, project, AMC—where their acceptance events differ.
  • List which lifecycle dates are known, unknown and assumed.
  • Stop replacing missing customer-side dates with false precision; flag the gap.
  • Measure how long invoices spend in each stage, not only how old they are overall.

Selected primary sources

These sources support specific contextual propositions in this article; they do not substitute for company-specific legal, commercial or recovery analysis.

  • Reserve Bank of India — TReDS FAQ — RBI's TReDS process illustrates how invoice confirmation/acceptance is a distinct event before financing and settlement for eligible MSME receivables.

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.

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.

References used on this page

These sources support the specific regulatory or enforcement context discussed on this page. Applicability depends on the transaction, counterparty and current rules.

Email GGA gg@ggaindia.co.in