HVAC labor billing errors: the leak hiding in your most common line item
Last updated November 16, 2026 · 6 min read
Short answer
Labor appears on nearly every HVAC invoice, so labor errors do too: hours that never reached a bill, overtime at straight time, second visits folded into the first. The check joins logged time to billed labor, job by job, and reports every gap.
The data reality
Where to export: Completed jobs' logged technician hours crossed against the labor lines on their invoices; the check verifies hours billed, rate applied, and multi-tech time.
Columns that matter: Job · Tech hours logged · Labor hours billed · Labor rate · Labor billed
Time logs live in the FSM; labor lines live on the invoice — different exports, different granularities. Time may be logged per tech per visit while the invoice shows one labor line. The check normalizes both to job-level hours and compares.
Why this system leaks
A tech logs 6.5 hours across the week on jobs that never get matching labor lines — travel time absorbed, a second visit's hours folded into the first, overtime Saturday billed at the weekday rate. Each invoice computes correctly from what was entered on it. The gap between time logged and labor billed is never computed anywhere, so it never surfaces. Across a season it is thousands of dollars of work the shop performed and did not price.
The system of record for time and the system of record for money are the same product but different modules, joined by a manual step — building the invoice — where hours are retyped from memory. Every retyping is a chance to drop an hour, and no report compares the two sides afterward.
The three shapes of labor leakage
Hours that never reach an invoice (the job was billed for parts only, or not at all). Hours that reach the invoice at the wrong rate (overtime at straight time, after-hours at standard). Hours from a second tech or second visit that collapse into the first. All three are invisible to reports, because reports see billed amounts — not the comparison to time actually logged.
Overtime is where the spread is widest
A $95 weekday rate becomes $142.50 on Saturday — a $47.50/hr gap that the invoice honors only if someone remembered to flag the day. Rushed Monday-morning invoicing of weekend work is precisely when that memory fails. The check knows which hours were logged on which days and verifies the rate matches.
One comparison, every job, every month
The reconciliation joins each job's logged time to its billed labor and reports every gap: unbilled hours, rate mismatches, multi-tech collapses. The office reviews the exceptions, marks the deliberate ones, and recovers the rest — before the month closes and the hours lose their context.
A worked example
One technician's month: 22 jobs, 6.5 hours of logged time that never appeared on any invoice — a second visit absorbed into the first, travel-plus-repair hours trimmed to rounded blocks, and 1.5 hours of Saturday overtime billed at the $95 straight-time rate instead of $142.50.
- Recorded work
- $451.25
- Invoiced
- $0.00
- Residual
- $451.25
Residual = $451.25 for one tech in one month — 6.5 hours × $95 with the overtime shortfall included. A five-tech shop loses this several times over, every month, invisibly.
What the data cannot show
- Not every logged hour is billable — shop time, training, and non-charge travel are legitimate; the check compares logged time to billed labor on customer-facing jobs and lets the office mark known non-billable categories.
- Flat-rate pricing decouples labor hours from labor dollars by design — the check still verifies the job was billed, and flags jobs with logged hours and no invoice at all, which flat rate does not excuse.
Questions shops ask
How much labor do HVAC shops typically under-bill?
Shops running their first reconciliation commonly find a few percent of logged labor hours missing from invoices — concentrated in second visits, overtime, and jobs billed parts-only. The check quantifies your exact number from your own exports in minutes.
We bill flat rate — does labor leakage still apply?
Yes, in a narrower form: a job with logged hours and no invoice at all is leakage under any pricing model. Flat rate protects the rate, not the omission. The check flags unlogged-into-invoice gaps regardless of pricing structure.
Should travel time be billed?
That is your pricing policy. The leak is the gap between what you logged and what you billed, not the policy itself. The check shows the gaps; the office decides which ones are policy and which are money.
Run the free check on your files
Run the free check on your files