How to prevent vendor invoice disputes, and resolve the ones you have

The disputed amount is only part of the cost. An invoice you can't check also takes staff time to chase, puts strain on a vendor you may need on the next urgent call, and, if it's paid as billed, sets the price for the next one. Common invoice problems fall into a few patterns, and each one is settled by a specific piece of data:

Disputes happen when the only record of a visit is the vendor's own invoice. The fix is to capture the record during the visit, so approval becomes a comparison instead of an investigation.

1. Capture visit data during the visit, for every vendor. Arrival with a location check, departure, the work performed, parts and photos. A process only some vendors follow leaves gaps exactly where you need records.
2. Put the record on the work order. Your team approves invoices from the work order. A record kept in a separate portal has to be found and matched by hand.
3. Write the requirement into vendor agreements. Make checking in and out, a completion record and photos a condition of payment, so asking for them is routine rather than a challenge.
4. Catch no-shows the same day. A live board of who is on site, flagging dispatched visits nobody has checked in to, turns a missed visit into a same-day phone call instead of a disputed invoice weeks later.
5. Review the exceptions, not every invoice. When every visit is checked the same way, approve the ones that match and spend your review time on the ones that don't: unverified visits, off-site check-ins and labor beyond time on site.

A useful completion record names the work performed, the parts used and any follow-up needed, with photos of the finished work.

spryggAIVR captures the visit record from the technician's phone calls, so there's nothing for the vendor to install or fill in. The technician calls one number to check in, and a one-tap texted link checks their phone's location against the site address. Each visit is marked verified on site, flagged off site or unverified. At check-out the technician describes the work by voice, it becomes a completion report (work performed, parts and follow-up by default), and they can text photos or upload them from a link. Times are shown in the site's local time zone with a zone label, so an after-hours rate can be checked against the site's clock. If a technician forgets to check out or skips the report, spryggAIVR texts reminders, and a visit left open is marked as having no check-out rather than given a time nobody recorded.

Each check-in and check-out, with the site-local time and the completion report, is written to the work order in ServiceChannel or spryggCMMS, with photos attached, or to a row on your Google Sheet with time on site, a photo count and a link to the full record. Check-in and check-out emails can go to an inbox too, so the record is there when the invoice arrives. Visits where the technician didn't share their location are still recorded in spryggAIVR and marked unverified. If your vendors already submit records like these through your CMMS for every visit, you may not need another tool. See proof of service for how verified records change invoice approval.

This process works whatever tools you use. It keeps the dispute about specific lines and specific records, which is what gets it resolved.

1. Match the invoice to its work order and contract. Pull the work order, the agreed scope, the rate schedule, any not-to-exceed amount and the response-time terms. Check whether the contract sets a window or a notice requirement for disputes.
2. Gather your own records of the visit. Look for anything not created by the vendor: check-in records on the work order, a site sign-in sheet, the site manager's notes, door access or alarm logs.
3. Compare the invoice line by line. Billed labor against time on site, billed parts against the work described, the rate against the time of day, and the number of technicians against the number who checked in.
4. Separate the lines you question from the rest. Approve or pay the undisputed lines on your normal terms where the contract allows. Holding only what you question keeps the vendor working and the dispute small.
5. Ask the vendor for specific evidence, in writing. Name the invoice, the work order and the lines in question, list the records you need (see the checklist below) and give a date to reply by.
6. Review what comes back against your records. Note which claims are backed by a record made during the visit and which rest only on the vendor's word, such as a timesheet written after the invoice was questioned.
7. Decide, and record the reason. Approve, ask for a credit or an adjusted invoice, or reject the questioned lines. Write the outcome and the reason on the work order, so the next person who looks at it doesn't start over.
8. Track outcomes by vendor. One dispute is a conversation. The same problem across many invoices from one vendor is a topic for their next performance review or contract renewal.

Ask only for what settles the lines you question. Records made during the visit carry more weight than records made after the invoice was questioned.

A missing record isn't proof the work didn't happen. It's a reason to ask, and a good vendor will usually have something to show. Keep the request factual so the conversation stays about the visit, not about trust.

Split it by what each team can judge. The facilities team reviews the work: whether the visit happened, whether the scope matches and whether the job is finished. Accounts payable reviews the money: rates, markups, payment terms and credits. When both work from the same visit record on the work order, neither has to call the site to find out what happened.