Why your invoices go out late, and what to fix first
Invoice lag is usually blamed on admin. It is almost always an hours problem — and every day of it is a day of working capital you never get back.
Ask a firm when it invoices and you will hear "end of month." Ask when the invoice actually left, and the answer is the ninth. Sometimes the fourteenth.
Nobody planned that. It is the residue of a process where every step is slightly late and no step is anybody's specific job. And it is expensive in a way that does not show up as a line in the accounts, which is why it survives for years.
What the lag actually costs
Invoice lag is not a delay you catch up on. It is a permanent shift.
A firm billing $2M a year turns over roughly $5,480 a day. If invoices leave on the ninth rather than the second, seven days of revenue are permanently in transit — about $38,000 sitting somewhere between "work delivered" and "money arrived", at all times, forever.
You do not earn that back next month. Next month has the same seven days. The only way to recover it is to shorten the gap once, after which the improvement is permanent in the other direction.
There is a second cost that is harder to price. A late invoice is queried more often. Bill three weeks after the work and the client has forgotten the context, the person who approved it is on holiday, and a line that would have been waved through in week one now needs explaining. Each query adds days of its own.
Where the days actually go
Almost every firm assumes the delay is in the invoicing itself — the assembling, the checking, the sending. It rarely is. That part takes an afternoon.
The lag is nearly always upstream, and it is usually one of four things.
1. The hours aren't finished. This is the answer most of the time. You cannot invoice work that has not been written down, so the invoice waits on the slowest timesheet. One person who fills theirs in on the fifth sets the date for everyone.
2. Nobody owns the date. "End of month" is not a person. When the invoice run belongs to everybody it belongs to nobody, and it happens when someone notices — which is usually when a cash question is asked.
3. Approval has no deadline. Where hours are reviewed before billing — which is right, and particularly on retainers — the review step frequently has no clock on it. Hours sit finished and unapproved for days, which is the most frustrating kind of delay because the work is genuinely done.
4. Scope questions surface at invoice time. "Did we agree this was billable?" is a fine question in week one and a bad one in week five, because by then it delays money rather than preventing a misunderstanding.
Notice that three of the four have nothing to do with invoicing.
- Hours still arriving — 5 days
- Waiting for approval — 3 days
- Assembling and sending — 1 days
- Hours already complete — 0 days
- Waiting for approval — 2 days
- Assembling and sending — 1 days
The invoicing itself is one day in both. Everything else is upstream.
Fix them in this order
First: shorten the hours gap. Not "chase harder at month end" — move the logging closer to the work. Hours captured the same day are more accurate and remove the dependency on the slowest person, because there is nothing to chase.
This is the fix that makes the other three easier, and skipping it makes them cosmetic. A firm with a named invoice owner and a strict approval deadline still cannot invoice hours that do not exist yet.
Second: put a name and a date on the invoice run. One person, one date, in a calendar, recurring. Not "early in the month." The second working day.
Third: timebox the approval. Two working days from submission. If a reviewer has not responded, it escalates or it goes as submitted — pick one in advance and write it down. An approval step with no deadline is not a control, it is a queue.
Fourth: move scope conversations upstream. Anything unusual gets raised when it happens, not when it is invoiced. This costs one awkward conversation in week one and saves several in week five.
How to tell which one is yours
Measure two gaps for last quarter:
- Period end → invoice sent. The number you are trying to reduce.
- Work done → hours logged. The number that usually explains it.
If the second is large, you have an hours problem wearing an invoicing costume, and no amount of invoicing discipline will fix it. If the second is small and the first is large, the delay is genuinely in ownership or approval — which is much easier to fix, and worth being pleased about.
Most firms have never measured either, which is why the diagnosis usually lands on the person who sends the invoices. They are almost never the cause.
The part that keeps it fixed
Whatever you change, the thing to protect is the distance between doing work and recording it. Every other problem here grows out of that gap: the chasing, the missed lines, the reconstructed justifications, the queries.
Close it and the invoice run becomes what it should be — an afternoon of assembly, on a known date, by a named person, from hours that were already finished.
Disclosure: we build Timsio, which drafts timesheets from your calendar so hours are captured close to when they're worked, and sends and chases the invoices that follow. That's the bias to read this with. The four causes above are worth measuring whatever you use — the diagnosis in the last section takes an hour with a spreadsheet and a list of invoice dates.