Why should warranty jobs be invoiced at $0 instead of left uninvoiced?
Short answer: A $0 invoice is a record; a missing invoice is a hole. The $0 invoice documents that the work happened under warranty, preserves the parts trail, supports the manufacturer's labor claim, and keeps your completed-jobs data complete for reconciliation. Left uninvoiced, the job looks exactly like a billing mistake — to you and to every report that scans your books.
The four reasons the $0 invoice matters
1. It's the warranty claim's backbone. Manufacturer labor-claim programs want evidence: what failed, when, what was replaced, serial numbers. The $0 invoice is where all of that lives in your system. No invoice means reconstructing the claim from memory and photos.
2. It keeps the customer's history true. Next tech on that equipment needs to know the compressor was replaced under warranty 14 months ago — inside or outside the extended window. The $0 invoice is that history.
3. It makes reconciliation possible. When every completed job has an invoice — $0 or not — "completed job with no invoice" becomes a pure signal. Warranty noise disappears from the leak report, and what remains is real money.
4. It protects you on the audit that matters. If a manufacturer audits claims, or a customer disputes a charge touching that equipment, the $0 invoice is your evidence that you did the work and charged nothing.
The rule that makes it work
ZeroInvoiceIfWarranty: every completed warranty job gets an invoice with total $0, part lines listed at $0, labor at $0, and the warranty reference in the description or memo.
The parts still appear — at $0. Why? Because the supplier statement reconciliation needs them: a compressor purchased and matched to a $0 warranty invoice is explained. A compressor purchased and matched to nothing is indistinguishable from an unbilled part.
The exception that isn't
Extended-warranty and labor-claim programs that pay you are not customer billing. Bill the manufacturer what the program owes (or file the claim in their portal) — but the customer-facing invoice is still $0. Two records, two directions, one job.
A worked example
Job for the Hendersons, September: condenser fan motor replaced under the manufacturer's 10-year parts warranty. Two ways to record it:
- No invoice. The job shows "complete", $0 collected. In the monthly reconciliation it appears as "$1,140 of recorded work, $0 invoiced" — a false alarm that your office learns to ignore. And no record exists for the labor claim ($150) you could have filed.
- $0 invoice. Same completion, invoice at $0 with "WARRANTY — Lennox, claim #LN-88231" in the memo and the motor listed at $0. The reconciliation sees a properly excluded warranty job — silence, which is the right answer — and the claim number proves the $150 labor claim was filed.
Same job. One version creates noise and loses money; the other creates a record and recovers it.
Common mistakes
- Leaving warranty jobs uninvoiced because "there's nothing to bill." The invoice isn't for the customer's money — it's the claim record.
- Claiming parts but never labor (or the reverse) because nobody checks $0 invoices against claim programs.
- Burying the warranty reference in the customer's name field. It belongs on the invoice, where reconciliation and audits look.
What breaks when warranty jobs aren't invoiced
- The claim never gets filed → you donated labor and sometimes parts to the manufacturer.
- The reconciliation reports a false leak → your office wastes time investigating.
- Worse, your office learns to ignore "job with no invoice" findings — and now real leaks hide behind warranty noise.
Author: Unbilled. Our engine treats warranty jobs as exclusions when they're properly $0-invoiced — and flags them as an operations gap when they're not. Send three files, get the report.