Invoice faster, or chase harder?
Most businesses chase the customer when the longer delay is their own.
In short
The wait between finishing work and holding the money is two separate delays. The first runs from finished to invoiced, it is entirely inside your business, and it usually costs nothing but attention to fix. The second runs from invoiced to paid, and only the part past your own terms is really the customer being late. Measure them separately. When the first is longer than the second, chasing customers harder is effort spent on the half you control least.
Work it out in a minute
Nine questions across revenue, capacity and control. Shows which of the three is costing you most, and where to start.
Which half of the wait is actually yours?
Two dates and what you invoice in a month. It splits the delay into the part you control and the part you do not, and prices the gap.
Take the last ten jobs and average it. Guess high, everybody does.
The whole wait, not just the overdue part.
Days past this are late. Days inside it are not.
The answer
Answer the four
Sitting in the gap at any one time
0
Do this next
Show the reasoning
A second opinion
Want the first fix picked for you?
Send it over and you get back which half to work on first, the one change that usually moves it, and what the first two weeks look like. Your numbers travel with it, so there is nothing to explain twice.
Goes to one inbox.
What this usually leads to
Whichever half is yours, the fix is the same shape: a named day, a named owner and a written first message. Process automation is what removes the assembling step that keeps invoices in drafts, and data and reporting is what tells you the number moved without anybody having to ask.
This does not stand alone
One answer is never the answer
Whatever this tool just told you is kept in your browser as you go, so it can sit next to anything else you work out here. A number on its own tells you a size. Two or three from different corners tell you whether the problem is capacity, information, or the way the work is arranged, which is the part worth acting on.
What we take on
Two delays, not one
Finished to invoiced, then invoiced to paid. They have different causes, different owners and different fixes, and adding them into one number hides which is which.
One of them is entirely yours
Nobody outside the business decides when the invoice goes out. That delay is a queue, a missing approval or a person who has to be reminded, and none of those need the customer.
Terms are not the same as lateness
If your terms say thirty days, thirty days is not late. Only what comes after that is. Counting from the invoice date makes a normal customer look like a bad one.
Chasing is a process, not a personality
Whether somebody is chased should not depend on who remembers or who minds least. It depends on whether there is a named day, a named person and a written first message.
Why the shorter delay gets all the attention
Late payment feels like something being done to you, which makes it the part everybody talks about. The days before the invoice goes out feel like ordinary work, so they do not feel like a delay at all. They are, and in a lot of businesses they are the bigger half.
The reason is structural. Invoicing sits at the end of delivery, which means it is always behind something more urgent, and it is usually nobody main job. The work finishes, the file goes somewhere, and the invoice waits for whoever assembles it to have a clear afternoon. Nine days is common and nobody experiences it as a problem, because no single person waited nine days for anything.
The second delay deserves splitting too. If your terms are thirty days, a customer paying on day thirty two is two days late, not thirty two. Businesses that measure from the invoice date end up chasing customers who are behaving exactly as agreed, which wastes the relationship and the effort at the same time.
So measure both, separately, before deciding where the work goes. The tool below does the arithmetic and says which half is yours. In most cases the first fix is not a collections process at all. It is deciding that the invoice goes out the same week the work finishes, and giving that to somebody by name.
Questions we get
Is thirty days to get paid normal?
For business to business work it is unremarkable, and it is what most terms say. The question worth asking is not whether the number is normal but which part of it you agreed to.
Thirty days of agreed terms and two days of lateness is a healthy picture. Ten days of terms and twenty two days of lateness is the same total and a completely different problem.
Our invoices go out late. Where does that actually come from?
Almost always one of three places. The work finishes but nobody is sure it is finished, so the invoice waits for a confirmation that nobody asked for. Or the numbers live in more than one place and assembling them is a job. Or invoicing belongs to somebody who has a more urgent job every single day.
All three are fixable inside the business, which is the point. None of them require a customer to change anything.
Are late fees worth it?
They change behavior far less often than people expect, because the person who pays your invoice is rarely the person who feels the fee. What changes behavior is being predictable: the same reminder, on the same day, every time, from the same address.
What a late fee is genuinely useful for is the conversation. Having one written down makes the follow up a routine matter rather than an awkward one.
The client says the invoice never arrived. What now?
Treat it as true, because often it is, and it costs you nothing to assume so. The useful move is to stop it recurring: send to a named person and a shared inbox, put the purchase order or reference in the subject, and confirm receipt rather than assuming it.
If the same client says it twice, the problem is your delivery route, not their filing.
Who should be chasing, sales or finance?
Whoever the customer already knows, for the first message, and somebody consistent after that. A first reminder from the person who did the work reads as a question. The fourth one from the same person reads as a relationship in trouble.
The part that matters more than the department is that it is written down and dated. Chasing that depends on who remembers is not a process.
Do we need software for this?
Not to find out where the problem is. Twenty recent jobs, two dates each, and a spreadsheet will tell you which half is yours.
Software helps once you know, and it helps most with the reminders, because the value there is consistency rather than judgment. Buying it first tends to automate whichever half you guessed at.
More in the guides and every answer in one place.
Shaheer Shaikh, C-suite operations lead for a San Francisco AI company working with global pharma on clinical trial data and model benchmarking. Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. More about the firm