Note
The Cost of Work You Cannot Invoice Yet
The work is done. The truck left days ago. The technicians are already two projects further along. But the invoice for that site has not gone out. Somewhere between physical completion and the billing queue, the paperwork stalled, a signature went missing, or the project manager never passed the word to the office.
Every day that passes, the job that cost labor and time to run is paying for itself out of your working capital instead of the customer’s. That is what work you cannot invoice yet actually costs, and it is rarely measured precisely enough to know how large it has become.
What “Completed but Unbilled” Actually Costs
When a technician works six days on a site and the installation is physically done, those wages have already been paid or are owed. The same applies to fuel, tools consumed, and any subcontractor time. None of that changes based on whether a signed handover is in the file.
The customer, by contrast, has paid nothing yet. The payment clock does not start until the invoice goes out. In most commercial electrical work in Thailand, the invoice cannot go out without a signed handover document or its equivalent.
So the cost of unbilled completed work is the full cost of running the job, carried by your business, for every day between physical completion and the invoice date. That window is entirely within your control to shrink. Most businesses have not measured it.
How Do You Estimate Your Own Unbilled Backlog?
Here is an exercise to run on your own numbers.
Take any project completed in the last 90 days. Note the date the technicians finished on site. Find the invoice date. The difference is your pre-invoice lag for that job.
Repeat this for five or six recent projects. If the average lag is longer than five to seven calendar days, a structural gap exists, and it is probably not an exception. It is normal practice that has never been questioned.
To size what that gap is worth: take the average number of technician-days on a typical project. Multiply by the number of projects you run per month. Multiply by the average lag in days. Divide by your average project length in days. The result tells you, roughly, how many technician-days of completed work your business routinely carries before it can issue an invoice.
The goal is not precision. The goal is to make the gap visible. Most owners who run this calculation find the number is larger than they assumed.
Why Does the Lag Keep Growing?
The reasons are predictable, and in most businesses they combine:
- The signed handover is not captured on-site. It has to be chased, sometimes for days after the crew has left.
- The project manager treats physical completion as the end of their job, and does not see billing as their responsibility.
- The billing team has no reliable trigger to raise an invoice, so they wait to be told.
- The customer’s site engineer is unavailable on completion day, and nobody follows up systematically.
- The handover document is filled in from memory at the office and then sent for signature, adding three to five days before the process has even started.
Any one of these adds days. Combined, they can push pre-invoice lag to two or three weeks per project. In a business running eight projects a month, that lag never fully clears before new projects finish and join the queue.
What Changes When the Billing Queue Is Visible?
The single most useful structural change is splitting jobs into three explicit states: open, closed-but-unbilled, and invoiced.
Most businesses conflate the first two. A job is either running or finished. The “closed but not yet billed” category is invisible because nobody named it. When you name it, and when there is a screen or report that shows every job in that state along with its age, the behaviour around closing changes.
Project managers who can see their jobs sitting in a named billing queue tend to close them faster than those who are simply asked to remember. Making the signed handover the gate into that queue is what keeps the three states honest. The closed-but-unbilled count becomes a number, and numbers get attention.
The secondary effect is that the owner finally has a figure: the total value of work that is complete but not yet moving through the billing cycle. Track that number over time. A business where it stays high and stable has a process gap. A business where it stays low has solved the pre-invoice lag.
FAQ
Is there a normal amount of lag between completion and invoice?
Some lag is unavoidable. Invoice preparation takes time. Some customers have internal approval steps before they can sign. But the portion of the lag that belongs to your own process, from physical completion to the moment the invoice is sent, should be measured in days, not weeks. If it regularly exceeds seven calendar days, there is friction worth removing.
Does faster invoicing actually improve cash flow?
It moves the start date of the payment cycle. If a customer pays 30 days after the invoice date, invoicing one week earlier means cash arrives one week earlier. Across a business running several projects per month, those weeks accumulate into a meaningful improvement in working capital timing.
What if the customer is the bottleneck, not us?
Prepare the documentation before the last day of the installation, not after. If the customer’s site engineer is coming to sign off, schedule that as a defined closing step, not an open-ended ask. When the signature arrives, the invoice should go out the same day. Separate the delay that belongs to the customer from the delay that belongs to your process, and work to eliminate only the second.
One piece of what TRACE 30 puts in place is a closing gate and an owner screen that shows closed-but-unbilled jobs as a separate, named category, distinct from open work and invoiced work. The age of each job in that state is visible from the day it closes. If you want to understand how that works in practice, the details are at /program/. Or book a short call at /schedule-a-call/ if you want to talk through what your own pre-invoice window currently looks like.