The Work Is Finished. Why Hasn’t the Invoice Gone Out?

Where the stall actually lives

Start with the handoff from the field to the office. The proof that the job is billable — the signed work order, the timesheets, the photos, the delivery confirmation — rides around in a truck cab, sits in a foreman’s phone as a text thread, or waits in an inbox behind everything louder. The office cannot bill what it has not received, so the invoice waits on a document that already exists somewhere.

Then there are the extras. The customer asked for something mid-job, somebody said sure, and the addition was never written down or priced. Now the person drafting the invoice faces a choice: bill only the original scope and eat the difference, or hold the whole invoice while a verbal agreement gets reconstructed from memory. Holding it feels safer. The invoice waits again — this time on a conversation.

Then the internal loop. In plenty of companies every invoice, or every invoice above some threshold, waits for a review — by the owner, the project manager, whoever knows the job. That person is busy precisely because they are the person who knows the job. So a finished, drafted, correct invoice sits in a queue behind estimates, hiring, and fires, waiting for a moment of attention it needs and cannot get.

And underneath it all, batching. Billing happens “when the bookkeeper has a quiet Friday” or on the last day of the month, because that is how it has always been done. Batching means the job that finished on the second waits for the thirtieth by design. Nobody decided to lend customers a month of free credit; somebody decided invoicing was a chore to be gathered up, and the credit followed.

Three scenes from the done-not-billed file

The pattern crosses industries so cleanly that the scenes below are nearly interchangeable. They are invented as illustrations — each one is the kind of gap that shows when you line up completion dates against invoice dates in a real company.

None of these companies has a cash problem in the usual sense. Each has already paid for the labor, the materials, the licenses, the payroll that produced the finished work. What they have is a translation problem: turning proof of work into a request for money requires documents, a decision, and a trigger — and each scene below is missing exactly one of the three.

• Construction: the job is physically complete and the final draw is the largest single invoice on the project — and it is waiting on a punch-list sign-off nobody has scheduled, because scheduling it belongs to no one. The crew has moved to the next site; the money has not moved at all.
• Managed services: the T&M ticket was closed with every hour logged neatly inside it. Nobody pushed those hours to an invoice, because closing tickets belongs to engineers and billing belongs to the office, and no rule connects the two. The work is documented to the minute and billed never.
• Agency work: the milestone shipped and the client is already using it, but the invoice is on hold because someone is “waiting for the email confirming acceptance” — an email nobody has actually asked the client to send. The confirmation everyone is waiting on has no owner either.

Different industries, same anatomy: the work is done, the proof is scattered, and the trigger that should turn one into the other is a person hoping someone else does it.

The fix is an owner and a same-day rule

The fix is not software and it is not a new payment policy. It is a rule: the event that marks a job done is the event that triggers the invoice — same day. Ticket closed, punch list signed, milestone accepted: whatever ends the work starts the bill. Not the following Friday, not month-end, not whenever the paperwork surfaces. The same day, as the default that requires no decision.

A rule without a name on it is a wish. One person owns done-not-billed — not the accounting department, a person — with standing authority to demand the field paperwork, price the verbal extras, and pull an approval out of a busy manager’s queue. And every exception gets a reason code: waiting on sign-off, waiting on documents, waiting on approval, disputed scope. Vague exceptions are where the float goes to hide.

Then make it visible on a rhythm. A weekly done-not-billed report — every finished job without an invoice, its age, its reason code — read aloud in the same meeting by the person who owns it. Read aloud matters. A report someone must speak to by name gets shorter week after week; a report that lives in a dashboard gets scrolled past. What gets read aloud gets billed.

Measure the float before you touch anything else

Before changing payment terms, buying software, or lecturing the field about paperwork, measure what you have. Your records already hold both dates: when jobs actually finish — the closed ticket, the final timesheet, the signed acceptance — and when invoices actually go out. Line them up across your recent completed jobs and the float stops being a feeling and becomes a number of days, with job numbers and names attached.

If you want the dollar version first, our free Leak Calculator takes a few numbers you already know and shows what delay and leakage cost per year — before anyone talks to anyone. If the number is not small, The Revenue Review is the diagnosis step: $4,500, fixed, two weeks. We read your own records — completions, invoices, and the gap between them — name where the days go, and hand you a 90-day fix list in priority order with the arithmetic behind every line.

There is a worked sample report on this site, so you can see exactly what you would be holding before you spend anything. And if you would rather talk first, the call is 20 minutes and free. Bring one number if you bring anything: how many finished jobs are sitting unbilled right now. If you cannot answer that today, that is not a failure — it is the finding.