Flat-rate vs T&M: the same audit checks different things
Last updated November 5, 2026 · 5 min read
Short answer
Flat-rate shops leak in the pricebook surface: unsold recommendations, parts, missing fees. T&M shops leak in hours: logged but unbilled. Hour checks on flat-rate jobs create false alarms; the audit must know the billing model first.
The data reality
Where to export: Work-order export carrying the billing-model fields (isFlatRate flag or job-type); invoice lines export distinguishing labor-by-hour from labor-by-task.
Columns that matter: Billing model · Labor line code · Labor line qty · Job total · Pricebook code
MIXED shops are both at once — the check must run per job, not per shop. A labor line with a non-null code is billed-by-task even at a shop that is otherwise T&M.
Why this system leaks
Generic audit advice applies hour checks everywhere. On flat-rate pricing, hours are the tech's problem, not the customer's — so hour-based findings accuse the pricebook of crimes it did not commit.
The billing model determines WHERE the leak can physically exist: flat-rate leaks hide in what was never added to the invoice; T&M leaks hide in quantities that were added but rounded down. One check cannot serve both.
The flat-rate checklist
Flat-rate leaks: recommended-but-unsold work sitting in job notes, parts pulled but never added to the invoice, and trip/diagnostic fees missing on declined-repair visits. The hours are already inside the price — audit the pricebook surface, not the clock.
The T&M checklist
T&M leaks: logged hours exceeding billed hours beyond tolerance, parts billed at cost without margin (a different audit), and the same missing-fee surface as flat-rate. The hour check runs on every T&M job with a MEDIUM-confidence classification, because logged hours are only as honest as the timesheet.
A worked example
Same compressor-replacement job, two shops. Flat-rate shop: pricebook price $1,290 billed in full; 7.5 tech hours logged — irrelevant to billing. T&M shop: 7.5 hours × $95 = $712.50 billable; invoice billed 5.0 hours = $475.
- Recorded work
- $712.50
- Invoiced
- $475.00
- Residual
- $237.50
Flat-rate shop: residual $0 — the pricebook price was billed; logged hours do not change that. T&M shop: residual = (7.5 − 5.0) × $95 = $237.50, over the half-hour tolerance. Same job, two different audits — which is why the model is the first question any reconciliation asks.
What the data cannot show
- MIXED billing requires the per-job flag to be right in the data; a job mislabeled FLAT_RATE silences its hour check, and vice versa.
- Flat-rate hour checks are disabled, not impossible — a shop that pays techs by productive hours may still want the data, but it is not a billing leak.
Questions shops ask
We're MIXED — how does the audit handle that?
Per job. The work-order's flat-rate flag decides which checks apply to that job. Hour checks run on T&M jobs and skip flat-rate jobs, even inside the same month.
Why are hour findings only 'needs confirmation'?
The arithmetic is exact but the input (logged hours) depends on timesheet discipline. Honest classification keeps them out of the verified headline until a human agrees.
One file, one report
One file, one report