A warranty job marked complete with no $0 invoice: right by policy, dangerous by accident

Last updated November 5, 2026 · 5 min read

Short answer

A warranty job should produce a $0 invoice — that is why reconciliation excludes warranty from findings. But the exclusion must be earned by the data (a warranty flag or job type), never assumed: an unflagged job is checked like any other.

The data reality

Where to export: Work-order export with the warranty flag or job type; some FSMs record warranty as a job type, others as a boolean, some only in notes.

Columns that matter: Job type · Warranty flag · Notes · Invoice total · Job status

Shops disagree on what counts as warranty: manufacturer parts warranty, labor warranty, callback-redo. The exclusion list is configurable per shop — the reconciliation never hard-codes one shop's policy onto another.

Why this system leaks

Warranty noise trains the shop to ignore $0 invoices. 'It's probably warranty' becomes the answer to every missing-invoice question — including the ones that aren't warranty at all.

The $0 invoice is camouflage. A technician marking a job 'warranty' loosely, or an office skimming past zero-dollar lines, lets genuinely unbilled customer work hide inside a legitimate category.

Why exclusion beats detection here

Flagging every $0 warranty invoice would bury the report in noise the shop already knows about — the fastest way to make a reconciliation tool get ignored. Excluding warranty (when the flag or job type says so) keeps the findings list short enough to be read. A miss is forgiven; a false positive is fatal.

The callback overlap

A callback (redo work) is often invoiced $0 for a different reason: the original invoice already paid for the outcome. Treating callbacks as warranty — or vice versa — misconfigures two exclusions at once and both categories leak into the report.

A worked example

Job #20771 — blower motor replacement under manufacturer parts warranty. Parts covered; labor NOT covered under the warranty terms, per the shop's policy of billing labor on parts-warranty jobs.

Recorded work
$285.00
Invoiced
$0.00
Residual
$285.00

The job carries the warranty flag and a $0 invoice — but the shop's policy bills labor on parts-only warranty claims. Whether the $285 of labor was billed is a policy question the data cannot decide alone, which is why it surfaces as a policy-verification item rather than a verified leak.

What the data cannot show

  • The data cannot distinguish 'warranty by policy' from 'warranty by typo' — the exclusion list is the shop's statement, not the truth.
  • Callback-redo work is a separate category with its own policy and is excluded separately.

Questions shops ask

Should warranty jobs have a $0 invoice at all?

Most shops create one for the paper trail; some don't invoice at all. Either way it is unbilled-by-policy, so reconciliation excludes it — the report never counts a legitimate $0 as a leak.

What if we bill labor on parts-warranty jobs?

Then labor on those jobs is checkable, and the data will show whether it was billed. Configure the exclusion to parts-only and the reconciliation does the rest.

Run the free check on your files

Run the free check on your files

Related