An operational description of a collections routine: when to send, what to write, who calls and when - and why most late payments are a stuck invoice rather than a refusal.
Key takeaways
- Most late payments are an operational fault rather than a refusal - and they are handled entirely differently.
- The first contact should come before the due date, not after.
- A fixed ladder beats deciding case by case, because it prevents both forgetting and overreacting.
- What matters more than the reminder is that the invoice went out correctly in the first place.
An operational description, not advice. What options you have contractually or legally against an unpaid debt is a question for a lawyer and your accountant. What follows is the routine only: when you make contact, what you write, and who calls.
The figure that surprises businesses is that most late payments are not refusals. They are an invoice that reached the wrong address, an approval sitting with somebody, or simply forgetfulness. An orderly routine resolves most of those without a single uncomfortable conversation.
Why invoices go unpaid
| The reason | How common | The fix |
|---|---|---|
| Never reached the right person | Very | Confirm the recipient before sending |
| Waiting on internal approval | Very | Ask who approves and when |
| A detail missing - order number, references | Common | Establish the requirements in advance |
| Forgotten | Common | An automatic reminder |
| A cash-flow problem at the customer | Sometimes | A conversation, and an arrangement |
| A dispute about what was delivered | Sometimes | Not collections - a service matter |
The first five rows are solved by process; only the sixth requires an entirely different conversation, which is why identifying it early matters rather than treating it like an ordinary delay.
The ladder that works
- Before the due date - a friendly reminder: this invoice falls due next week.
- The day after - a short message: this may have been missed, here it is again.
- A week after - a personal contact, by call or message: is everything in order with the invoice.
- Two weeks after - a conversation with whoever approves, not the usual contact.
- Beyond that - a deliberate decision: a payment arrangement, stopping service, or external handling.
Step 1 saves most of the rest, and it is the only one that does not feel like collections. A reminder before the due date reads as service, and it reveals early whether the invoice was even received.
What to write
Short, factual, and without apology. Four elements: the invoice number, the amount, the due date, and a link or attachment. One question at the end - "is everything in order?" - produces far more replies than a demand.
What does not work: long messages with explanations, apologetic wording signalling you feel awkward asking, and early threats. The first goes unread, the second invites deferral, and the third damages a relationship at a stage where the cause is usually forgetfulness.
What raises the chance of being paid on time
- Send early - an invoice issued on the working day becomes an earlier payment.
- Send to the right person - not a generic business address.
- Include what they need - order number, billing details, payment method.
- Offer an easy way to pay - a link, not only bank details.
- Confirm receipt - one question in a follow-up message.
The first two together explain a large share of late payments. The operational side of issuing invoices on time is covered in running a monthly subscription invoice cycle, and it is directly relevant here: collections start at issuing, not at reminding.
Who calls, and when
At steps 1-3, whoever owns collections or manages the relationship - it is still operational. At step 4, better that it is somebody with a mandate to agree an arrangement, because the conversation may lead to a decision.
What is not advisable is the owner entering at the first step. When they call, the conversation acquires a weight that is hard to step back from - so keep them for the stage where a decision is genuinely required.
What to do with a debt that does not move
At some point the routine ends and a decision is required. The three practical options are a payment arrangement, stopping service or supply, and external handling. Which is right and what is permitted in each route is a question for a lawyer and your accountant, not an improvised decision.
What is operational: decide in advance when you stop, and be consistent. A business that keeps supplying a customer who has not paid for three months teaches them that they can, and produces the same problem with other customers who are watching.
How do you know the routine is working?
By three numbers measured monthly: average days from invoice to payment; what share of invoices were paid within terms; and how much debt is open beyond 30 days. All three move slowly, so look at them across a quarter rather than week to week.
What surprises businesses that start measuring is that the first number is nearly always worse than assumed. A business that believes it is paid within thirty days often finds the real average is considerably longer - which changes all cash planning, as covered in a weekly cash visibility routine.
The second metric is the one showing whether the routine itself works: when it rises after two months of disciplined reminders, that is exactly what you wanted to know.
What to do when a customer does not respond at all
Complete silence is a different signal from refusal, and it calls for a change of channel rather than another message. Somebody who ignored three emails will ignore a fourth; what works is trying another route - a phone call, a message, or contacting somebody else at the same business.
It is also worth checking the basics: whether the address is correct, whether your messages are landing in spam, and whether the contact still works there. In small businesses, a good share of "customers who never respond" are in fact emails reaching somebody who left six months ago - and that surfaces only when somebody picks up the phone.
Sources
Frequently asked questions
How many reminders are too many?
The ladder above - four contacts over two weeks - is almost always enough. Beyond that another reminder changes nothing: somebody who has not paid after four contacts did not forget, and from there it is an entirely different conversation.
Should we stop providing service?
That is a business decision that should be defined in advance and applied consistently, not taken under pressure. What matters is telling the customer before you do it rather than after - advance notice produces payment in some cases, while a surprise stoppage produces a dispute.
What about a customer too important to press?
Separate the relationship from the process: the routine continues as normal - it is operational rather than personal - while whoever manages the relationship finds out what is happening. Large customers usually appreciate an orderly process more than a concession, because they have procedures of their own.
Should we charge up front?
In many businesses yes, at least partly, and it changes the whole collections routine. A deposit or advance payment on part of the work reduces exposure and also filters customers who never intended to pay - a commercial decision best made before the engagement rather than after.
Keep reading
Related service
MVP Development
Turn an idea into a validated product in weeks, not months.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.