The work is done. The invoice is three weeks away

The engineer finished the site on the second of the month. The invoice goes out on the twenty-fourth. In between, you have paid for the fuel, the engineer's day and the lab analysis, and the client has paid for nothing. That gap is a loan. You are making it, interest-free, to a customer who would never dream of offering you the same terms.

For most water hygiene contractors that gap is not a billing problem. The office knows perfectly well how to raise an invoice. It is a paperwork problem: the invoice is waiting on the visit report, the report is waiting on the engineer to write it up, and no one upstream can bill work they cannot yet prove happened. Close the paperwork gap and most of the lag closes with it.

How long the loan actually runs

Start with the number everyone quotes and few act on. In construction the average stretch from invoice to payment runs to 83 days. Read it carefully: 83 days from the invoice, not from the work. Every day you add before the invoice goes out is a day stacked on top of the 83. Sit on the bill for three weeks at month-end and you have quietly stretched a payment cycle that was already the wrong side of eleven weeks.

Completed work you have not yet invoiced has a name in accounting. It is underbilling: money spent but never requested. You paid the labour and the materials, the job is finished, and the request for payment simply has not gone out. Until it does, the firm is financing that work out of its own pocket, and the firm doing the financing is usually the one that can least afford to.

If billing is a month-end ritual, the gap has a floor you cannot get under. Treating invoicing as a month-end task builds in a 30-day blind spot: work done on the second waits three and a half weeks for the same billing run as work done on the thirtieth. The early job is not early. It is just waiting for the calendar to come round.

The lag is a balance, not a one-off

It is tempting to picture the gap as a single wait: this invoice, this month, then it clears. It does not clear. The work repeats every month, so the unbilled gap repeats with it, and what you are really carrying is a rolling balance of finished-but-unbilled work that never empties. Shorten your average lag by two weeks and you have not saved two weeks once. You have permanently freed up two weeks of every month's revenue, month after month, which is working capital you currently have tied up in paperwork nobody got round to finishing. That is the figure worth caring about, and it is the one a month-end habit hides best, because at month-end the balance looks like it clears and then quietly refills on the first.

Why compliance work waits longer than most

Here is the part specific to our trade. The invoice waits on the report, and the report is real work that someone has to sit down and finish.

A job marked complete in the field is not the same as a job ready to bill. If the report is missing, the photos never synced, or a signature was not captured, the office cannot raise an accurate invoice against it. The work is done and undocumented, which for billing purposes is the same as not done at all. We wrote separately about the proof debt that piles up in unfinished visit reports; the cash-flow lag is the other end of that same debt.

Month-end turns billing into archaeology. By the twenty-fifth someone in the office is reconstructing three-week-old visits from half-finished paperwork, chasing an engineer to remember which TMV on which site, re-keying readings off a photographed notepad. That reconstruction is slow, it is error-prone, and every hour of it pushes the invoice back another hour. It is also, not by coincidence, the same double data entry we costed out elsewhere, wearing a different hat.

The chain is only as quick as its slowest link, and the slowest link is usually the one furthest from the office. An engineer who finishes a site at four o'clock, drives home, and writes up three visits over the weekend has done nothing wrong. But the invoice for Monday's job now waits on Saturday's paperwork, and if Saturday's paperwork waits on a photo that never left the phone, the invoice waits on that too. Every handoff between the field and the office is a place the report can stall, and each stall is billable revenue standing still.

Who actually absorbs the lag

Not a finance department. In a firm of this size there usually isn't one. The owner absorbs it. Owner-operators describe working on the tools all day and then quoting and invoicing at night, with 65 to 70-hour weeks not unheard of, a second shift at the dinner table doing the admin the working day left no room for. The invoice is late because the only person who can raise it already spent the day fixing calorifiers. The quoting half of that night shift has its own cost, incidentally: prices worked out tired and late are prices worked out badly.

Change the trigger, not the tempo

The instruction "invoice faster" is useless, because nobody is being slow on purpose. Change what triggers the invoice instead.

• Bill on completion events, not the calendar. When a visit is genuinely finished, that is the moment to raise the invoice, whether it lands on the second or the thirtieth. Month-end batching is the 30-day blind spot dressed up as a routine.
• Put the evidence inside the definition of "done". A visit is not complete when the engineer drives away. It is complete when the report, the readings, the photos and the signature are captured. Define it that way and "done but unbillable" stops being a category, because the thing that blocks the invoice is now the same thing that blocks "done".
• Chase from records, not memory. When every invoice is backed by a timestamped report the client already received, a late payer is arguing with a document rather than your recollection. That is a shorter conversation, and you win it more often.

BlueWave ties the invoice to the work finishing in the field. When an engineer submits a completed visit the report is already attached, so the job becomes billable in the same moment it is done and invoicing follows completion rather than the calendar. Nothing sits in the done-but-undocumented limbo that month-end billing runs on. The invoice itself is raised in the same platform too — itemised, VAT-correct, numbered at issue — so "ready to bill" and "billed" stop being separate days.

None of this shortens the 83 days once the invoice is out; that clock belongs to the client. What it shortens is everything before the invoice, which is the part you actually control. The blunt version: the client's clock does not start until you send the bill, so the only days worth arguing about are the ones you are adding before the clock even starts. Invoice lag is one of eight leaks we map across a water hygiene operation; it is the only one with an interest rate.