Late payment is usually a set of ordinary process failures rather than difficult customers. This guide names each one, explains how to tell which you have, and gives the order to fix them in.
In most distribution businesses, payment is late for five ordinary reasons: the invoice was raised late, nobody can see how old the outstanding is, no single person owns the chase, a dispute created weeks earlier surfaces only when payment is due, and agreed credit terms are not enforced when the next order is taken.
Those causes are sequential. Fixing the chase while invoices still go out a fortnight after delivery simply means chasing wrong numbers politely. Work through them in the order the money moves: raise, see, own, prevent, enforce.
The first three causes have nothing to do with the customer. They are entirely within your control, which is why they are the ones to take first.
A credit period starts from the invoice, so every day between delivery and invoicing is added to the wait at your expense. The delay comes from the same few places: goods dispatched on a challan and never converted, a service call closed on a paper job card that reaches the office days later, or a purchase order number missing so the invoice is held back.
The test is simple. Take twenty recent deliveries and service jobs and measure the gap between the work and the invoice date. If that gap is routinely days rather than hours, no amount of following up will make collections faster.
Most businesses know the total outstanding. Far fewer can say, without preparing a report, which invoices are oldest, which customer holds the largest overdue balance, and which are still within terms. Without that view, effort spreads evenly across the list instead of concentrating where the risk sits.
Collections fall between roles. Accounts assume the salesperson will mention it, the salesperson does not want to spoil the relationship before the next order, and the owner intervenes only when cash is tight. The symptom is easy to spot: ask who spoke to a customer about a given invoice, and when. Ownership means a named person per account and a contact history held against the invoice.
The remaining two causes are set in motion at the point of sale and at delivery, and only become visible as late payment.
This is the most expensive cause, because the delay is invisible until it is already long. A short delivery, a wrong rate, a missing challan copy, an incorrect GSTIN on the invoice, or a service visit billed although the machine was under contract. The customer noticed on receipt and simply did not pay, and you learn about it when you call.
The cure is upstream. Match the invoice to the order and the delivery, carry the purchase order reference and correct tax details, and keep the acknowledged delivery in the record so a claim can be settled or rejected with evidence.
If a customer can place a fresh order while earlier invoices are past terms, the terms are informal. Enforcement need not mean a hard block. It can mean the salesperson seeing the overdue balance while quoting, and an approval step before dispatch to an account past terms.
| What you see | Likely cause | What to change |
|---|---|---|
| Payment arrives well after the agreed period even from reliable customers | Invoices raised late | Invoice from the closed delivery or job card, the same day |
| Everyone is chased equally and the oldest debt keeps ageing | No ageing view | An ageing report by customer and bucket, opened weekly |
| Nobody can say when a customer was last contacted | No owner for the chase | A named owner per account and a logged contact history |
| A complaint appears only when you ask for money | Disputes found at payment time | Invoice matched to order, delivery and purchase order reference |
| Overdue accounts keep receiving fresh stock | Terms not enforced | Overdue balance shown at quotation, approval before dispatch |
Each step makes the next one worth doing. Taken out of order, the later steps produce activity rather than cash.
None of this requires a new finance department. It requires the invoice, the delivery, the contract and the payment to sit in one place, so that ageing is a by-product of daily work rather than a monthly exercise.
Receivables ageing software shows the buckets, the owner and the contact history against each invoice, with reminders sent from the payment record.
Invoices raised late. The credit period runs from the invoice date, so a delivery invoiced days after it left the warehouse has already spent part of its credit period before the customer receives the document. It is also the easiest cause to measure.
Ageing groups outstanding invoices into buckets by how long they have been unpaid, by customer. It separates invoices still within terms from genuinely overdue ones, so effort goes to the oldest and largest. See receivables ageing software.
Either works as long as one of them is named for the account and every contact is recorded. Problems come from shared responsibility, where accounts assume sales will raise it and sales avoid the subject before the next order.
Tie the invoice to the order and the acknowledged delivery, carry the purchase order reference and correct tax details on the document, and record service calls against the contract so a covered visit is never billed by mistake. Most disputes then surface at delivery.
They help with routine cases where the invoice was simply forgotten, and they free human effort for accounts that need a conversation. A reminder sent from the payment record also builds a contact history.
Make the overdue balance visible to the salesperson at quotation, and require an approval rather than an automatic refusal before dispatching to an account past terms. The conversation then happens before the order instead of months after the invoice.
Plain-language explainers.
The view this guide argues for.
The routine chase, automated.
Closing the invoicing gap.
Outstanding on one screen.
Why the ageing stays manual.
The six numbers an owner watches.
Tell us how your centre or business works today and we will tell you plainly which parts of this apply to you, and which do not.
Founder-led · Chennai, India · Built and supported by the person who wrote it