Why the invoice clock starts days after the job is done

Ask an owner how long it takes to invoice a finished job and the answer is usually "same day". Ask the person who actually raises the invoices and the answer is "when I've got everything". The gap between those two answers is one of the largest pools of cash in a commercial contracting business, and almost nobody measures it.

This guide explains where the lag comes from, how to put a number on it using data you already have, and why the job platform you've paid for hasn't closed it.

The job is finished. The paperwork isn't.

An invoice for commercial work needs several things to exist before it can go out: hours against the right job, materials with quantities, any variation with an approval attached, and whatever certificate or test result the client requires. Each of those comes from a different person, on a different day, in a different format.

So the job is complete on Tuesday and the invoice waits for the supplier invoice on Thursday, the certificate on Monday, and the answer to "were those extra hours on the variation or the base job?" whenever the technician is next in the office. None of those delays is long. Together they're a week.

Why your job platform hasn't fixed it

Most job and accounting systems can invoice a closed job instantly. The catch is the word "closed". The platform only knows what's been entered, and what's been entered depends on people who are already on the next job. The software is waiting on the seam between the field and the office, and no amount of configuration makes a voice note arrive as a line item.

This is why the lag survives system changes. Businesses move platforms expecting the problem to go away and find it moved with them, because it was never inside the platform.

Measure it in an afternoon

Pull the last 50 invoices. For each, note the job completion date from the job system and the invoice date from accounting. The difference is your lag. Sort them and look at the median, not the average, because one job that waited three months will distort the mean.

Then ask a second question: what's completed but not yet invoiced right now? Count the jobs and add up their value. That single number, on a given day, is the size of the queue the lag creates.

What seven days actually costs

Treat it as working capital, not profit, because that's what it is. If you complete around 90 jobs a month at an average of A$4,200 and the lag is nine days, taking it to two days releases roughly A$88,000 of cash that's currently sitting in the gap. That money doesn't appear as revenue. It appears as a lower overdraft, a supplier paid on time, or a hire made a month earlier.

The admin cost is separate. If the office spends six hours a week chasing what's missing, that's around 312 hours a year, and it's the part that shows up as overtime or a coordinator hire.

What closes the gap

Three things, in order of difficulty. First, a definition of "ready to invoice" that everyone can see, so the office chases specific things instead of sweeping the board on a Friday. Second, an automated chase that asks the right person for the right missing item and escalates if it doesn't arrive. Third, a daily list of what's completed, not invoiced, and why.

None of that requires new software. It requires something whose job it is to watch the seam. It's one of the first systems we expect to build for most trade businesses.