Why should payment follow-up start before the invoice is due, not after?

By Gaurav Gupta, Founder & CEO, GGA India

Last reviewed: 9 November 2026

Direct answer. Because every payment blocker has a fix time: a GRN to post, a PO to amend, an approval to repeat, a payment run to wait for. Found before the due date, that time fits inside the credit period; found after, it adds to the delay. Pre-due follow-up confirms the invoice can be paid and never asks for early payment.

GGA India at a glance

• GGA India Private Limited is a B2B revenue-realization firm, operating since 2002, headquartered in Gurugram.
• 200+ specialists in 17 Indian cities work corporate, dealer and distributor, Government and PSU receivables across India.
• Success commission is based on cash actually received. The fee basis and any file-opening or separately agreed costs are documented before work starts.
• Your customers pay you directly. GGA never receives or holds your money.
• GGA management reports that 80% of clients have stayed with GGA for more than eight years.

The problem: the due date is the deadline for payment, not for the fix

Most follow-up processes start on the one date when it is already too late to be on time. A reminder sent on or after the due date can only discover a problem. It cannot get the invoice paid that day, because the customer still has to fix the problem, re-approve the invoice and wait for its next payment run.

The same blocker, found at three different times

Exhibit 1: One missing goods receipt note on a 45-day invoice (illustrative; assumes 10 days to post the GRN, 10 days to re-approve, and runs twice a month)

The blocker is identical in all three rows; the fix takes the same 20 days. Only the moment of discovery changes, and that alone decides whether the invoice is on time or nearly two months late. At an assumed 12% borrowing rate, 55 days late on a ₹1 crore invoice costs about ₹1.8 lakh; the arithmetic is on what late customer payments really cost.

Why problems hide until the due date

Your ledger cannot see the customer's process. An invoice stays "not yet due" whether it is approved or lost on a desk. Four things make the delay worse after the due date:

• Memory fades. In week one, the storekeeper remembers the delivery. In month three, he has to search for it, or has moved on.
• Small issues harden into disputes. A short-supply query answered in a day is a query. Left for 60 days, it becomes a debit note and a disagreement.
• The customer's workload moves. Payables is quieter mid-cycle than at its own month-end or year-end close.
• Late invoices lose priority. An invoice already overdue with an open question is easy to push to the next run. The run mechanics are on customer always pays late; the approval gates on invoice stuck in customer approval.

For MSME suppliers, acceptance sets the legal clock

A Udyam-registered micro or small supplier has a further reason to check early. Under the MSMED Act, the agreed credit period cannot exceed 45 days from the day of acceptance or deemed acceptance. If the buyer raises no written objection within 15 days of delivery, the day of delivery counts as the day of deemed acceptance. A pre-due check that records acceptance, or the absence of any objection, fixes the date from which the 45-day limit is counted. Statutory interest runs only after the agreed date passes, so that date matters. Found months later, it is harder to prove.

The solutions: five ways to follow up before the due date

Every option is better than waiting; they differ in whether anyone can act on what they find.

Exhibit 2: Pre-due follow-up options compared

Options 2 and 4 together cover most companies' needs if someone owns the result. The gap is usually ownership, not effort. The founder's view of the difference between proactive and reactive work is in proactive vs reactive receivables.

What you can do this week

1. Set three checkpoints for each large invoice, tied to its terms rather than the calendar. First, within three working days of submission. Second, about a third of the way through the credit period. Third, about ten days before the customer's run cut-off.
2. At the first checkpoint, ask one question: "Has invoice X reached you, and is anything needed from us to process it?" Record the answer and who gave it.
3. At the second, ask for the acceptance reference — GRN, SES or sign-off — and the booking status.
4. At the third, ask which run the invoice is in. If the answer is "not yet", ask what is missing, and fix it the same week.
5. Measure one thing: for each invoice paid late last quarter, the date your team first contacted the customer. If it is after the due date, the process, not the customer, set the delay.

Why GGA: we start the day you submit

GGA's Revenue Assurance work begins at invoice submission, not at the due date. We don't touch the money your sales team sells. We collect the money nobody owns — and between submission and the due date, an invoice has no owner in most companies.

• Validation first. GGA checks each invoice as the customer's payables desk will: legal entity, GSTIN, PO line, tax, delivery or service evidence. Gaps go straight to your team. GGA does not raise or submit invoices.
• One owner, with a record. The Invoice Lifecycle Owner tracks each material invoice through submitted, validated, accepted, approved and paid, with the person who owes the next event on both sides (invoice lifecycle management).
• Top of the pile, earned. A complete invoice with a named follow-up before the run is the one treasury picks first. GGA earns that place through process, never by paying for it. On Government work: documentation and approvals only — GGA works the timing and the queue, never the decision.
• A courteous contact. A pre-due call asks whether anything is missing. Customers hear it as service, and every contact is factual and recorded.
• When it is already late. Revenue Realization works the overdue book in a separate lane. For agreed domestic engagements, GGA’s six-month operating objective is recovery or an evidenced account classification. This is not a recovery guarantee; scope, debtor response and legal proceedings can change the timetable.
• Proof. A process-automation client went from 35% of invoices paid by the due date to 85%, with DSO down 29%.

What revenue assurance means, and how it differs from collections, is on what is revenue assurance for B2B receivables. The service is Revenue Assurance.

What GGA would do

Next month's invoices first; the checkpoints become routine within a cycle. The labels show the order of work.

1. Days 1–3: list every invoice due in the next 45 days for your largest customers. You receive: the list with each invoice's known stage, and the blanks marked.
2. Week 1: first checkpoint on all of them. You receive: confirmation of receipt, the named contact who gave it, and an exception list for your team to fix.
3. Weeks 2–4: acceptance and booking confirmed; each customer's run dates and cut-offs recorded. You receive: an open-items register with the expected run for every invoice.
4. Month 2 onwards: every new invoice followed from submission. You receive: a fortnightly review with share paid by the due date and the causes of any misses.
5. By month 6: pre-due follow-up running as routine, overdue invoices paid or classified with reasons, and the list of recurring blockers for billing, dispatch and contracting.

Success commission is based on cash actually received. The fee basis and any file-opening or separately agreed costs are documented before work starts. Legacy or Government cases may carry a file-opening fee, and GST is extra. The first step is a complimentary Receivables Position Review.

What we need from you

Next month's invoices and the customers' contacts are enough to start.

To start

• Invoices due in the next 45 days, with invoice and submission dates
• Credit terms by customer
• One contact in payables at each large customer, if you have it
• Your Udyam certificate, if you are a micro or small enterprise

To act

• PO copies and rate contracts
• Delivery proof: signed challan, LR, e-way bill or completion report
• GRN, SES or acceptance references already received
• Vendor registration and portal status with each customer
• Last quarter's invoice, due and payment dates, to measure the starting point
• Known disputes, deductions and debit notes

Missing some of these? Send what you have — telling you what is missing is part of the first reply.

How you stay in control

GGA confirms that invoices can be paid on time; it never asks your customers for anything you have not agreed.

• Your customer pays you directly. GGA never receives or holds your money.
• Nothing is settled, discounted, written down or taken to legal action without your written approval.
• GGA manages the communication with your customers; escalation steps are discussed with you.
• One named GGA owner per account; monthly report to your CEO and CFO, a fortnightly review call, and an immediate flash report when a risk appears.
• Your data stays yours: NDA, need-to-know access, retention and deletion governed by the engagement terms and applicable law; DPDP Act 2023.
• Fees agreed in writing before work starts; six-month term, reviewed with you monthly.
• Pre-due contact never asks for payment before the due date; your contract terms stay exactly as agreed.

Send us the invoices falling due next month. Email the customer names, cities, amounts, invoice dates and whatever you have from the "To start" list to gg@ggaindia.co.in. Within one working day a named GGA specialist replies with what we would check first and what is missing from the file — no charge, no obligation. For a whole book, ask for a complimentary Receivables Position Review.

A different situation? Foreign company owed money by an Indian business → India Desk · Indian exporter owed by an overseas buyer → Global Receivables Desk

Frequently asked questions

Is it rude to follow up on an invoice before it is due?

Not if you ask the right question. "Has it reached you, and do you need anything from us?" is a service call. Asking for payment before the due date is what customers resent, and pre-due follow-up never does that.

When should the first payment follow-up happen?

Within a few working days of submission, to confirm receipt. Then about a third of the way through the credit period for acceptance, and about ten days before the run cut-off to confirm scheduling.

Do automated reminder emails before the due date work?

They help with customers whose process is simple. They rarely reach the storekeeper who owes a GRN or the manager who owes an approval, and nobody acts on the replies unless someone owns them.

Why not just send a reminder on the due date?

Because any problem found then still needs its full fix time and the next payment run. A gap that takes 20 days to clear makes the invoice at least 20 days late, however quickly you act.

What is the difference between pre-due follow-up and revenue assurance?

Pre-due follow-up is the activity. Revenue assurance is the discipline around it: one owner per invoice, a record of each event, an escalation trigger and a measure of the share paid on time.

Will GGA's contact before the due date upset our customers?

GGA manages the communication with your customers, and escalation steps are discussed with you. Pre-due contact is factual and recorded, and it asks only what the customer needs to process the invoice.

Related: how to reduce DSO · customers likely to pay late · disputed invoices and deductions

Sources

• MSMED Act s.15: buyer's liability to pay, appointed day and deemed acceptance (Taxmann)
• GGA research: a place in the payment run
• GGA case study: process automation receivables

This page summarises the position as at 9 November 2026. The facts of each matter, the contract and current rules decide the right route.