Invoice faster, or chase harder?
Most businesses chase the customer when the longer delay is their own.
The wait between finishing work and holding the money is two delays. Finished to invoiced sits entirely inside your business. Invoiced to paid is the customer. Measure them separately. When the first is longer, chasing customers harder is effort spent on the half you control least.
Is it a fit?
Your half
Days between finishing the work and sending the invoice.
Their half
Days between sending the invoice and the money landing.
Which is longer
Measure both before you change anything.
Which half of the wait is 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?
We reply within one business day.
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.
Saved in this browser, nowhere else. See all your answers together · All twenty-five tools
What you get
Two delays, not one
Finished to invoiced, then invoiced to paid.
One of them is entirely yours
Nobody outside the business decides when the invoice goes out.
Terms are not the same as lateness
If your terms say thirty days, thirty days is not late.
Chasing is a process, not a personality
Whether somebody is chased should not depend on who remembers or who minds least.
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 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.
If the invoice is late because the books are behind, accounting and bookkeeping is the service that fixes the rhythm first; the bookkeeping questions cover what a catch-up involves. Card payments have a third failure mode, and payment dispute management covers that one.
The two halves of the wait
Five rows, read across. One half is entirely inside your business and costs nothing but attention. Measure both before deciding which to work on.
| Factor | Finished to invoiced | Invoiced to paid |
|---|---|---|
| Who controls it | You, entirely. Nobody outside the business is involved. | The customer, past your own terms. The terms themselves are still yours to set. |
| What fixing it costs | Attention. Usually one named owner and a slot in the calendar. | Goodwill and staff time, spent on people you would rather keep. |
| What fixing it looks like | Invoice on completion rather than on a monthly run, with one person owning it. | Terms stated up front, a reminder before the due date, a call after it. |
| How to measure it | Days from the work being finished to the invoice going out, across the last ten jobs. | Days from invoice to payment, minus your stated terms. Only the remainder is lateness. |
| The usual mistake | Never measuring it, because it appears on no report anybody reads. | Chasing harder before checking whether this half is even the larger one. |
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 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 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.
An unaged debtor book is also the first thing underwriting notices. Preparing for a lender. If the invoice is late because the books are behind, catch up the books or start fresh is the decision underneath it.
More in the guides and every answer in one place.
Read next
The books behind both delays, the system that does the chasing, and where else the same money leaks.
Shaheer leads the work, with engineers, writers, filers and analysts behind him. C-suite operations for a San Francisco AI company, Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. See what we have built