Warehouse Labor / Revenue Leakage
How Much Finished Warehouse Work Is Sitting Unbilled?
You paid the crew. The customer got the service. Nobody sent a bill. This is the cheapest revenue in the business and the easiest to lose.
September 20, 2026 · 6 min read
Unbilled work is completed work that never became an invoice. It is the most expensive thing in a warehouse labor business, because the cost side already happened: the crew was assigned, the hours were paid, the customer got the service. Only the revenue is missing.
It is also the cheapest revenue you will ever recover. There is nothing to sell, nothing to negotiate and no work to perform. There is only a bill to send.
Every other growth idea costs something. This one is already paid for.
Why finished work goes unbilled
Not carelessness. Structure. A job has two different endings, and only one of them is visible on the floor.
Operationally, the work ends when the trailer pulls away. Everyone involved is finished, the crew moves to the next door, and the job is done. Commercially, the work ends when it appears on an invoice — days or weeks later, in a different room, done by someone who wasn't there.
Nothing in a normal day marks a job as “finished but not yet billed”.
So the jobs most likely to be lost are exactly the ones you would predict: the extra work a customer asked for verbally, the second trailer that got added at 4pm, the reslot nobody wrote down, the job that ran over a weekend, anything performed while the usual person was out. All of them are real work. None of them has a paper trail pointing at billing.
Make the queue exist
The fix is not a reminder. It is a list that the business cannot finish a month without emptying.
In FOREMAN, a completed Load carries a billing status, and Customer Billing is the queue of the ones still unbilled. It shows how many there are and what they are worth — Unbilled Loads and Unbilled Amount — and billing works directly from it: select the completed jobs for one customer, and the invoice is created from those records. A Load that has already been invoiced can't be selected again, so the same work cannot be billed twice.
That turns an invisible loss into a number with an age on it:
Illustrative example with simulated data. The figures show how the calculation works, not a measured customer result — put your own numbers in their place.
An unbilled queue that has not been read in six weeks
- Completed loads not yet invoiced
- 23
- Unbilled amount
- $18,940.00
- Oldest unbilled job
- 41 days
- Of which over 30 days old
- 6 loads / $5,120.00
- Labor already paid on all 23
- Yes
The amounts come from the jobs themselves — quantity recorded on the floor at the rate captured when the job was created — not from someone reconstructing a price at invoice time.
Unbilled work has a shelf life
A job billed a week late is an administrative delay. The same job billed seven weeks late is a conversation:
- The receiving manager who asked for the extra work has moved to another site
- The customer's own period is closed and accruing it now is your problem, not theirs
- Nobody can produce the signed paperwork, so the quantity becomes an opinion
- Some agreements limit how late a charge can be raised at all
Which is why the queue should be read weekly and aged, not swept at month end. The two questions worth asking every week are how much finished work is unbilled, and what the oldest item in it is.
The gap you can watch at the top level
Above the queue there is a simpler signal. Work performed and work invoiced are two separate figures in FOREMAN's dashboard — billable revenue and invoiced revenue — and the distance between them is the unbilled position for the period.
That gap is finished work you have already paid crew for and not yet asked anybody for. It is the same figure the labor cost and margin view reads as earned-but-unclaimed margin, and it is the first thing to look at before concluding a slow month was a demand problem.
What closing the gap actually requires
- Every job gets recorded, including the verbal ones. Work that was never captured cannot appear in any queue — which is why capturing ad-hoc work at the dock is the upstream half of this problem.
- The billable amount comes from the record. If someone has to work out a price at invoice time, that job will keep being postponed.
- The queue is somebody's job. Software makes the list; a person still has to clear it.
- Invoicing is not collecting. Getting the bill out is a different problem from getting it paid.
Common questions
What is unbilled work in a warehouse labor business?
Work that has been completed and paid for in labor but never put onto a customer invoice. It is not a billing dispute and it is not a late payment — it is a job that quietly never entered the billing process at all.
Why does completed warehouse work never get invoiced?
Usually because nothing tells anyone it is outstanding. A job is finished the moment the trailer leaves, so operationally it looks closed. Unless billing works from a list of completed-but-not-yet-invoiced jobs, the only thing standing between a job and an invoice is someone remembering it.
How do you find work that was never billed?
Compare the work you performed in a period against the work you invoiced for that period. The difference is the unbilled queue. If those two numbers come from the same operational record rather than two separate systems, the comparison is a report rather than an audit.
Can old unbilled work still be invoiced?
Often yes, but it gets harder with age. The longer the gap between the work and the bill, the more likely the customer questions it, the person who authorized it has moved on, or the period it belonged to is already closed on their side. Unbilled work has a shelf life.
See what is finished and not yet billed
FOREMAN keeps a billing status on every completed Load, so unbilled work is a queue with an amount rather than something you discover in a slow month. The full capability list covers the path from completed job to invoice.