How to audit maintenance and repair invoice lines

Executive Summary

Maintenance and repair invoices are harder to audit than freight or staffing because the reference document is a work order, not a rate card or a timesheet against a fixed schedule. Work orders get written after the fact, technicians describe scope in their own words, and nobody upstream of AP is checking whether the description matches the master service agreement.

The mechanism behind the leakage is consistent: three separate documents, the MSA, the work order, and the invoice, each get created by a different person at a different time, and nothing forces them to agree. Labor rates drift from the contracted schedule, scope expands between the approved work order and the billed line items, and warranty-covered repairs get invoiced as new work because the technician who filled out the ticket did not check the warranty term.

What changes this is treating the work order as the control document it should be: pulling it before you approve the invoice, checking it against the MSA's rate table and warranty schedule, and flagging any line that was not on the original approved scope. That is a document-comparison exercise, not a pricing calculation, and it does not require special software to start.

1. How do you audit a maintenance and repair invoice step by step?

Pull the master service agreement, the approved work order, and the invoice for the same job. Compare the invoice's labor rate against the MSA rate table. Compare billed scope line by line against the approved work order. Check whether any line item falls under a warranty term. Flag mismatches, document them, and hold payment on flagged lines only, not the whole invoice.

Start with the three documents that should describe the same job: the master service agreement, the approved work order, and the invoice. If any one of them is missing, that alone is a finding worth logging, because it means the job proceeded without an authorization record AP can check against.

Next, separate the invoice into its component lines: labor hours, labor rate, parts, and any trip or emergency service charge. Each of those checks against a different source. Labor rate checks against the MSA rate table. Parts and quantities check against the approved work order. Trip charges check against the MSA's stated terms for standard versus emergency dispatch.

When a line does not match its source document, do not reject the whole invoice. Flag the specific line, note which document it conflicts with, and route only that line for vendor clarification. This keeps the rest of the invoice moving through payment on schedule and keeps your dispute focused on the actual discrepancy instead of the whole relationship.

Log every flagged line in one place, even the small ones. A single overrun looks like noise. A logged pattern across several invoices from the same vendor is a negotiating position.

2. What documents do you need before you start the audit?

You need four documents for each job: the master service agreement with its labor rate table and warranty terms, the purchase order or work authorization, the technician's completed work order describing actual scope performed, and the vendor invoice. Missing any one of these means the audit cannot verify that specific job, and that gap should be logged as its own finding.

The MSA is the reference point for everything else. It should state the labor rate by trade or skill level, any surcharge for after-hours or emergency dispatch, and the warranty period on parts and labor for prior repairs. If your copy of the MSA is more than a year old, check whether an amendment or renewal changed the rate table before you use it as your baseline.

The purchase order or work authorization establishes what was approved before the technician arrived. The completed work order, filled out after the job, states what was actually done. Comparing these two documents against each other, before you even look at the invoice, tells you whether scope expanded on site.

Some vendors do not return a detailed work order unless asked. If yours does not, request one as a condition of the relationship going forward. An invoice without a supporting work order description is not verifiable, and that itself is worth raising with the vendor.

A. MSA rate table currency

Rate tables in maintenance MSAs get renewed on a set cycle, but repair frequency and input costs can move faster than that cycle. Confirm which version of the rate table applies to the invoice date, not the version currently in your files, before flagging a rate as wrong.

B. Warranty term visibility

Warranty periods are sometimes stated in a separate clause from the labor rate table, occasionally in the original service agreement rather than the MSA amendment. Pull that clause specifically rather than assuming the rate table page covers it.

3. Which drift types show up on maintenance invoices?

Three drift types recur on maintenance and repair spend: scope drift, where the work order expands beyond what was approved before the technician arrived; labor rate deviation, where the billed rate does not match the MSA's rate table; and warranty misclassification, where a covered repair is billed as new work. Each requires a different check against a different source document.

Scope drift happens because a technician on site finds additional issues and fixes them without a change order. The work gets done, which can be the right operational call, but it gets billed without the authorization step that would have priced it against contract terms.

Labor rate deviation happens when the invoice uses a rate that does not match the current MSA schedule. This can occur when a vendor updates its standard rate card without updating the contracted customer's terms, or when a different technician skill level is billed than was actually dispatched.

Warranty misclassification happens when the technician who fills out the work order does not check whether the original installation or prior repair is still under warranty. The repair gets coded as new billable work because nobody on the vendor side or the AP side cross-referenced the warranty clock.

Each of these needs a different document comparison, not a single check. Scope drift compares the work order to the pre-approval. Rate deviation compares the invoice to the MSA rate table. Warranty misclassification compares the repair date and equipment to the warranty clause's start date and duration.

• Scope drift: Work performed exceeds what was authorized before the technician started.
• Labor rate deviation: The billed rate does not match the MSA's contracted rate table for that trade or skill level.
• Warranty misclassification: A repair still inside its warranty window gets invoiced as new billable work.

4. How do you check a labor rate against the contract?

Pull the rate table section of the current MSA and match the invoice's labor category, whether standard, overtime, or emergency dispatch, to the corresponding contracted rate. Multiply the contracted rate by the hours shown on the work order, not the invoice, and compare that total to the invoice's labor line. Any difference is a rate deviation to flag.

The check itself is simple arithmetic once you have the right rate table: contracted rate multiplied by authorized hours should equal the labor line on the invoice. The difficulty is making sure you are using the hours from the work order, which reflects what was actually authorized and performed, rather than the hours as stated on the invoice, which is the number you are trying to verify.

Watch for rate category mismatches specifically. A vendor might dispatch a journeyman-level technician but bill at a senior or specialist rate, or apply an emergency dispatch surcharge to a job that was scheduled during standard hours. The MSA should define what qualifies as emergency or after-hours work; check the job's actual timestamp against that definition rather than accepting the invoice's own labeling.

If the rate table itself looks high relative to your expectation, do not assume overbilling before checking whether input costs in that trade have moved. Per the US Bureau of Labor Statistics Producer Price Index for commercial machinery repair and maintenance (series PCU8113--8113--, read September 5, 2026), the July 2026 index value was 237.468, up 9.1% year over year. A rate increase in that range can reflect a documented cost trend in the industry rather than an error, so confirm the increase is reflected in an actual contract amendment before treating it as drift.

5. How do you tell scope drift from a legitimate emergency repair?

Check whether the additional work was documented and communicated before it was performed, not just before it was billed. A legitimate emergency addition has a timestamped note, a verbal or written approval, and a clear description of why the issue was found. Scope that appears only on the final invoice, with no contemporaneous record, is what you flag as drift.

Equipment fails in ways nobody scoped in advance, and a technician who finds a second problem while fixing the first one can be doing the job correctly. The audit question is not whether the extra work was legitimate. It is whether the vendor's process captured authorization for it at the time, rather than presenting it for the first time on the invoice.

Look for a change order, a signed field ticket, or even an email thread that shows the additional scope was flagged before it was completed, not after. If your vendor relationship does not currently require this step, that is a process gap worth raising, separate from any specific invoice dispute.

When the documentation is missing entirely, treat the line as unverifiable rather than automatically wrong. Route it back to the vendor for the missing authorization record. A vendor with a legitimate emergency repair can produce a technician's field notes even without a formal change order; a vendor who cannot produce anything at all is a different kind of finding.

6. How do you close the loop once you find a discrepancy?

Document the specific line, the source document it conflicts with, and the dollar amount in dispute. Send it to the vendor as a discrete item rather than a general complaint. Hold payment on that line while releasing the rest of the invoice. Track the resolution and the time to close, and use the pattern across invoices to renegotiate the underlying process, not just the one bill.

A discrepancy that is not documented in a form the vendor can act on tends to sit unresolved. State the invoice number, the line item, the amount, and the specific document it contradicts, whether that is the MSA rate table, the approved work order, or the warranty clause.

Release payment on every line that checks out cleanly. Holding an entire invoice over one disputed line item damages the vendor relationship for no reason and slows down your own AP metrics without improving recovery.

Track how long each dispute takes to close and what the vendor's response was. A vendor who corrects the same type of error repeatedly is telling you something about their internal process, not just about one technician's mistake. That pattern is what justifies a conversation about adding stricter authorization requirements to the next contract renewal, or about moving from a periodic review to a standing control that checks every invoice before it is paid rather than sampling after the fact.

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

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

7. Frequently Asked Questions (People Also Ask)

What is the fastest way to spot a mispriced maintenance invoice?

Compare the billed labor rate directly against the current MSA rate table for that trade or skill level before checking anything else. A mismatch there is a common check that catches drift, and it takes less time than reviewing the full work order.

Can we dispute a line item without holding the whole invoice?

Yes. Flag the specific line, document which source document it conflicts with, and route only that line to the vendor. Release payment on the remaining lines that check out, so the dispute does not slow down the rest of the relationship.

Who should own the maintenance invoice audit inside AP?

Whoever owns vendor relationships for facilities or maintenance spend should review flagged lines, since they have context on the job and the vendor. AP can perform the document comparison, but resolution usually needs someone who understands the operational side of the work order.

What if the vendor never provides a detailed work order?

Treat that as a process gap and raise it directly with the vendor. An invoice with no supporting work order description cannot be verified against contract terms, so request one going forward as a condition of continuing the relationship.

How do we handle a repair that should have been under warranty?

Pull the warranty clause, check the repair date and equipment against its stated start date and duration, and if the repair falls inside the window, dispute the invoice as a warranty misclassification rather than a pricing error.

Does this audit require special software?

No. It is a document-comparison exercise between the MSA, the work order, and the invoice. A spreadsheet or shared log is enough to start, though a standing control that checks every invoice before payment reduces manual review over time.

What counts as an emergency dispatch under most MSAs?

The MSA itself should define the hours or conditions that qualify for an emergency or after-hours surcharge. Check the job's actual timestamp against that definition rather than accepting the label the vendor applied on the invoice.

How long should we keep prior work orders on file?

Keep them at least as long as the equipment's warranty period, since a warranty misclassification check depends on comparing a current repair date against a prior installation or repair record.

What is the difference between scope drift and a legitimate change order?

A legitimate change involves documentation created before or during the job: a signed field ticket, a timestamped note, or an approval email. Scope that appears for the first time on the final invoice, with no contemporaneous record, is what gets flagged as drift.

Should this audit apply to every maintenance invoice or a sample?

The document comparison works the same way regardless of volume. Whether you review every invoice or a sample depends on your AP team's capacity, but any invoice above your organization's review threshold should get the full check.