Warranty work billed as new work

Executive Summary

The root cause is rarely fraud. It is that warranty coverage lives in a document the field technician and the invoicing system never see: a purchase record, a serial number registration, or a warranty term buried in the original equipment purchase order. The work order system that generates the invoice has no field for warranty status, so it defaults to billable.

The fix is not renegotiating the contract. The warranty term is usually already there. The fix is building a check between the invoice and two things the invoice itself omits: the equipment's install or purchase date, and the vendor's own stated warranty period for that part or labor category.

Without that check, every warranty-eligible repair defaults to billable, because billable is the invoice template's only setting.

This guide covers how to recognize the pattern on an invoice, why it survives standard AP review, and what a working control looks like.

1. Why does warranty-covered work get billed as new, chargeable work?

Warranty coverage is tracked separately from the work order that triggers a service call. The technician's dispatch ticket carries a part number and a labor code, not a warranty expiration date. The invoicing system bills against the labor code and the parts list, not against a warranty table it was never connected to.

The gap is not intent. It is a missing data field between the equipment record and the billing system.

A service vendor's field technician is dispatched to fix a failed component. Their job is to diagnose and repair, not to check whether the part is inside its coverage window. The work order they close out becomes the invoice line item, generated from a labor and materials catalog that has one setting: billable.

Warranty terms, when they exist, are set at the time of equipment purchase or at contract renewal, and typically live with the buyer's asset register or the original purchase agreement, not with the vendor's field service software. The two systems do not talk to each other.

This is structurally different from a pricing error. A rate card violation happens because the wrong number was applied to a correct line. Warranty misbilling happens because the line should not have existed as billable at all.

The invoice is internally consistent. Rate, hours, and part cost all match the vendor's own price file. The defect is that the line should have carried a $0 warranty adjustment and did not.

2. What does this look like on an actual invoice?

The invoice reads exactly like any other service call: a labor line, a trip charge, and a parts line, priced at standard rates with no indication that anything is unusual. There is no flag, no separate code, and no red text. It is identical in format to a legitimate billable repair.

The only way to tell the two apart is to compare the service date and the part against a warranty term that lives outside the invoice.

Take a compressor motor replaced 14 months after equipment installation, where the manufacturer's warranty on that motor runs 24 months. The invoice shows a labor line for diagnosis and replacement, a parts line for the motor, and a standard trip or dispatch charge. Every number ties to the vendor's published rate card.

Nothing on the page signals a problem. AP staff matching this invoice to the purchase order and the technician's work order will find both match. Three-way matching checks the invoice against the PO and the goods or service receipt; it does not test whether the part replaced falls inside a manufacturer or vendor warranty window, because that window is not a field either system carries.

The pattern recurs across equipment categories: a control board replaced under an HVAC service agreement, a hydraulic pump on material handling equipment, a sensor assembly on a production line. In each case the invoice format is the same and the warranty term sits in a different document entirely.

3. How is this different from scope creep or a rate card violation?

Scope creep expands what work gets done beyond the agreement. A rate card violation charges the wrong price for correctly scoped work. Warranty misbilling charges the right price for work that should not have been billed at all, because a separate coverage term, not the service agreement's rate schedule, should have zeroed it out.

The three require different checks and different source documents to catch.

These three drift types are easy to conflate because they all surface on a maintenance or MSA invoice and all involve a technician's visit. They are not the same defect.

Scope creep happens when the work performed exceeds what the statement of work or service agreement authorized: extra hours, an unapproved additional task, a broader repair than the ticket called for. Rate card violations happen when correctly scoped, correctly warranted work is billed at the wrong labor rate, part markup, or trip charge. Warranty misbilling happens when the work itself should have carried no charge because a warranty term, sitting outside the service agreement, already covers it.

The distinction matters because each requires a different reference document to catch. Scope creep is caught against the SOW. A rate card violation is caught against the rate schedule. Warranty misbilling is caught against the equipment's purchase record and the manufacturer's or vendor's warranty term, a document AP rarely holds and rarely thinks to pull.

A. Where the boundary blurs

Extended or vendor-specific warranties complicate the picture further. A service vendor may offer its own labor warranty on a repair it performed six months earlier, separate from the original equipment manufacturer's parts warranty. A single failed component can carry two overlapping coverage terms with different expiration dates and different scopes, one covering parts and one covering labor.

An invoice that looks like a clean warranty miss on the parts side may still owe a labor charge, or the reverse. Reviewing this correctly means checking both terms independently rather than assuming one covers the other.

4. Why does this survive standard AP review and audit?

Standard AP controls confirm that an invoice matches a purchase order and that the rate matches the contract. Warranty status is not a field in either document, so a control built to check contract and PO agreement has nothing to check it against. The invoice passes every test it was designed to face and fails a test nobody built.

AP teams reviewing maintenance and MSA invoices are typically working from the purchase order, the service agreement's rate schedule, and the technician's signed work order. None of these three documents carries a warranty expiration date for the specific part or labor category involved.

Even where a warranty tracking system exists, it commonly lives with facilities, engineering, or the asset management function, not with AP. The invoice approval workflow and the warranty registry are maintained by different teams on different timelines, and reconciling them for every service invoice is not part of either team's job description.

Catching this requires a step most invoice-to-contract matching processes do not include by default: pulling the equipment's install date and applicable warranty term at the time a service invoice for that asset arrives, and testing the invoice date against it before the line is approved for payment. See n-way invoice matching explained for how additional matching layers, beyond the standard three-way check, are built to catch line-level defects like this one.

5. How do you build a check that catches this before payment?

The check requires three data points brought together at invoice time: the asset's install or purchase date, the applicable warranty term by part and labor category, and the service date on the invoice. Where the service date falls inside the warranty window for that specific part or labor line, the invoice should carry a $0 or credited adjustment. Building this as a standing rule, not a one-time review, is what prevents recurrence.

The starting point is an asset register that records install date, warranty term, and warranty type (parts, labor, or both) for every piece of equipment under a maintenance agreement. Where this register does not exist, it has to be built from purchase records and original equipment documentation before the check can run at all.

At invoice time, the check compares three things: the asset identified on the service invoice, the service date, and the warranty term on file for that asset and part category. Any service date falling inside the warranty window for the specific component involved gets flagged for the vendor to credit or re-invoice at $0.

This is a control problem, not a one-time cleanup. A single audit finds the historical instances and recovers what is owed. Preventing recurrence means the check runs on every incoming maintenance invoice, not just during a periodic review.

The quarterly margin drift review a control design pattern lays out how a standing review cadence catches this kind of defect on an ongoing basis rather than once.

6. Who should own this check, and what does it take to run it well?

The check sits between two functions that do not normally share a workflow: whoever maintains the equipment asset register, usually facilities or engineering, and whoever approves service invoices for payment, usually AP. Neither owns the full picture alone. A working process assigns a named owner to keep the warranty term data current and a named checkpoint in the AP workflow where that data gets applied before payment.

Facilities or engineering teams typically hold the best source of truth on install dates and original warranty terms, because they handled the equipment purchase. AP holds the invoice and the payment decision. Without a defined handoff, each side assumes the other is checking.

A practical structure names one owner for keeping the asset and warranty register current, tied to new equipment purchases and any vendor warranty extensions or renewals, and a defined checkpoint in the AP approval workflow where that register gets consulted before a maintenance or repair invoice clears for payment. This does not need to be a separate system. A shared field on the vendor master or asset record, checked as a standing step in invoice review, closes most of the gap.

See vendor master hygiene and the duplicate vendor problem for related groundwork on keeping vendor and asset data usable rather than stale.

Where the volume of maintenance invoices makes a manual check impractical, this is exactly the kind of rule that belongs in a documented, repeatable process rather than an ad hoc spot check, because a spot check only catches what someone happened to look at.

For the wider pattern this sits inside, start with the margin drift guide.

7. Frequently Asked Questions (People Also Ask)

How do I know if a repair on my invoice should have been covered by warranty?

Check the equipment's install or purchase date against the manufacturer's or vendor's published warranty term for that part or labor category. If the service date on the invoice falls inside that window, the line should carry a $0 charge or a credit, not a standard billable rate.

Is this the vendor's fault or an internal process gap?

Usually both contribute. The vendor's field service and billing systems typically have no warranty field to check against. The buyer's asset register and AP workflow typically have no step that pulls warranty data before approving a maintenance invoice. Neither side built the check.

Does this only apply to equipment under a maintenance contract?

It applies most visibly on maintenance and MSA invoices because those generate recurring service calls, but the same gap exists on any repair invoice for equipment that carries an active manufacturer or vendor warranty, contract or no contract.

Can standard three-way invoice matching catch this?

No. Three-way matching checks the invoice against the purchase order and the goods or service receipt. It confirms the line was ordered and delivered, not whether the part or labor involved falls inside a warranty term. That check requires a separate data source.

What is the difference between this and a substitution pricing problem?

Substitution pricing involves a part changing between what was ordered and what was delivered, with the price not adjusting to match. Warranty misbilling involves the correct part being billed at the correct price when it should have carried no charge at all, because a warranty term covers it.

Who should be responsible for tracking warranty terms internally?

Whichever team manages the original equipment purchase, typically facilities or engineering, is usually best positioned to record install dates and warranty terms. AP then needs a defined checkpoint to consult that record before approving a maintenance invoice for payment.

What if the vendor offers its own labor warranty separate from the manufacturer's parts warranty?

Track both terms independently. A repair the vendor previously performed may carry its own labor warranty with a different expiration date than the original equipment manufacturer's parts warranty, and a single invoice can be correct on one and wrong on the other.

How far back can we recover warranty misbilling once it is found?

Recovery windows depend on the specific service agreement's terms and the vendor's own credit or dispute policies, which vary by contract. Review the agreement's audit and credit provisions to determine the applicable lookback period for a given vendor relationship.