Completed jobs with no invoice: the leak that hides in plain sight
Last updated November 5, 2026 · 5 min read
Short answer
A completed job with no invoice happens when completion and billing are different steps by different people. The check is one subtraction per job: recorded work value minus invoiced dollars. A positive remainder with no exclusion reason is a leak.
The data reality
Where to export: Export completed jobs from your field software (filter status = Completed), and export invoices from your accounting system for the same period.
Columns that matter: Job status · Completed date · Job total · Invoice number · Invoice total
Job totals often include unsold recommendations; invoice balances show what is owed, not what was billed. Both distort naive scans — reconciliation strips them before comparing.
Why this system leaks
The field closes the job; the office invoices it. Every busy week, sick day, and staff change widens the gap between the two steps — and the gap never raises an alarm because both boards look healthy on their own.
No system shows the negative space. The jobs list and the invoice list are each internally consistent; the leak only exists when you put one list against the other and do the subtraction.
Who it hits hardest
Growing shops with new techs and a busy season. Every new hire does not know the billing rules; every spring rush closes jobs in a hurry. The leak is not one bad employee — it is a process gap that scales with volume.
The five-minute monthly check
Export completed jobs. Export invoices. Match job to invoice (reference field first, then exact ID, then customer-plus-date). Subtract billed from recorded. Anything positive with no exclusion reason is unbilled work. Shops that do this monthly stop the drift while the customer still remembers the visit.
A worked example
Job #20418 — compressor replacement recorded at $1,140 (labor $430 + parts $710), completed October 14.
- Recorded work
- $1,140.00
- Invoiced
- $0.00
- Residual
- $1,140.00
No non-void invoice references the job or its customer inside the completion window. Residual = $1,140 − $0. One job. Now imagine one per week — that is $4,700/month of drift from a single repeating gap.
What the data cannot show
- Some zero-invoice jobs are correct by policy — warranty, callbacks, maintenance-agreement visits. The check must exclude them or it cries wolf.
- Partial invoices bill real dollars; the remainder is the residual, never the whole job value.
Questions shops ask
Is a completed job with no invoice always a mistake?
No — warranty jobs, callbacks, and maintenance-agreement visits are legitimately zero-invoiced. The check is only honest when it knows your policies and excludes them.
How much does this leak cost a typical shop?
It varies by shop and we never claim a number we have not measured — which is exactly why the free reconciliation check exists: upload three files, see your own figure.
Run the free check on your files
Run the free check on your files