Invoice Verification for Contractors: The Complete Guide

Search for "invoice verification" and most of what comes back is written for corporate accounts-payable departments: three-way matching, purchase-order workflows, approval chains, ERP modules. That world assumes a discipline that doesn't exist on most jobsites, and it's worth being honest about why.

Corporate AP assumes every purchase starts with a purchase order. In the field, a foreman calls the supply house at 6:40 a.m. because the crew is short on fittings, the counter pulls the order, and the paperwork — if there is any — is a delivery ticket signed on a tailgate. There's no PO number to match against because there was never a PO. That's not sloppiness; it's how work gets done when the alternative is a crew standing around.

Corporate AP also assumes one invoice per purchase. Contractors live with progress billing — one contract billed against monthly, with retainage held and change orders layered on — and with supply-house statements where one month's invoice covers a dozen separate pulls against a quote written half a year earlier. Rough-in and trim might be two deliveries, months apart, billed against one fixture package priced at bid. The matching problem isn't one invoice to one PO; it's many invoices, over many months, against one quote that the market has been drifting away from the whole time.

So when contractors are told to "implement three-way matching," the advice fails on contact. The documents it depends on don't exist in the field, and the billing patterns it assumes don't match how material actually moves. Contractors don't need a worse version of corporate AP. They need verification built around the documents they actually have.

Here is the core distinction, and it's the one most software gets wrong. AP automation tools verify an invoice against a purchase order: did we get billed for what purchasing ordered? That's the right question inside a company with a purchasing department. It's the wrong question on a job, because the PO — when one exists at all — was usually written from the quote anyway, and often written loosely.

For a trade contractor, the document that locked the price is the quote. That's the number the job was bid against, the number the estimate was built on, the number margin depends on. So the verification that actually protects money is invoice-to-quote matching: every line on the invoice checked against the corresponding line on the quote or contract, at the unit level.

The difference isn't academic. Invoice-to-PO matching answers "did we get what we ordered?" Invoice-to-quote matching answers "did we pay the price we bid the job on?" — and it catches an entire class of errors PO matching can't see: price escalation applied between bid and delivery, substitutions shipped at a different price than the quoted item, unit-of-measure switches where the quote priced per foot and the invoice bills per case, and fees that were never part of the quoted number at all. Every one of those can pass a PO match cleanly and still cost you money against the bid.

Whether you do it by hand or with software, the process is the same. What changes is how long it takes.

Step 1: Pull the source documents. Get the original quote or contract for the job, plus any change orders, and the delivery tickets or packing slips for the period the invoice covers. If the invoice references a statement, pull the individual tickets behind it. Verification against memory isn't verification.

Step 2: Match line items, not totals. For each line on the invoice, find the corresponding line on the quote. Confirm it's the same item — same SKU or a substitution you approved — not just a similar description. This is where substitutions hide: a different brand of the same fitting reads fine at a glance and bills at a different price.

Step 3: Check quantities against what was signed for. The invoice quantity should match the delivery ticket, and the running total across all invoices should match the quote quantity. Partial deliveries signed for in full, returns never credited, and "safe" overages that quietly became billed quantities all surface here.

Step 4: Check unit prices and units of measure together. A correct price on the wrong unit is still an overcharge. Convert both sides to the same basis — per foot, per each, per case — before comparing. This single step catches errors that survive every total-level review.

Step 5: Isolate everything that wasn't quoted. Fuel surcharges, delivery fees, restocking charges, small-order fees. Some are legitimate supplier policy; none should pass unexamined. Flag them, decide, and track what you're accepting so it can be priced into the next bid.

Step 6: Dispute in writing, with the documents attached. A dispute that cites the quote line, the invoice line, and the difference gets resolved fast, because there's nothing to argue about. Suppliers correct documented errors as a matter of routine — it's undocumented complaints that stall.

Step 7: Record the outcome. The verified number — not the invoiced number — is what should land in your accounting system and your job cost report. A verification that doesn't flow into the books just gets overwritten by the wrong number later.

The process above, compressed into what to actually look at on every invoice:

• Right job, right quote. The invoice references the correct job and is matched against the quote actually used at bid — including the right revision, if the quote was reissued.
• Every item exists on the quote. Any line with no quoted counterpart is a substitution, an unquoted charge, or someone else's material.
• Substitutions were approved and priced. A swapped item is fine; a swapped item billed above the quoted item's price is a dispute.
• Quantities match delivery records. Invoice quantity equals what the field signed for, and cumulative billed quantity doesn't exceed the quote.
• Unit prices match the quote. Line by line, not on average. Escalation applied after the quote date is a conversation, not an automatic pass.
• Units of measure agree. Per foot vs. per stick, per each vs. per case. Do the conversion before trusting the comparison.
• Math checks out. Quantity times unit price equals the line total; line totals sum to the invoice total. Simple clerical errors are more common than anyone expects.
• Fees and surcharges are itemized and expected. Nothing rides along unexamined.
• Credits actually landed. Returns, short shipments, and prior disputes show up as credits on this or a prior invoice — promised credits have a way of never materializing.
• Retainage and progress-billing math is right. On contract billing, the percent-complete, retainage held, and previously-billed figures match your own records.

Ten items, applied to every invoice, catches the overwhelming majority of what the 39% error rate is made of. The catch is the next section.

Done by hand, the checklist above is real work. A high line-count supply-house invoice — a fixture package, a rough-in pull — can take an afternoon to verify properly, and the invoices keep coming whether or not anyone has an afternoon. So most offices triage: verify the invoices that look wrong, let the rest through. The problem is that the errors doing the damage don't look wrong. They're a drifted unit price on line 41 of 90, sitting in a column of plausible numbers. Triage systematically passes exactly the errors it exists to catch.

The other cost of manual verification is that it's the first task dropped under schedule pressure — which means coverage is worst precisely when order volume is highest and errors are most likely. The math of skipping it is unforgiving: at 2.5% average overbilling, every unchecked $100,000 in material spend leaks about $2,500, silently, into someone else's ledger.

This is the part of the job that software genuinely changes, because the work is document reading at volume — exactly what humans are slowest at and machines aren't. CheckIT Invoice does the invoice-to-quote match automatically: drag in the invoice and the quote or contract, and it reads every line on both and flags every difference — unit prices off the quote, quantities that were never ordered, charges that were never quoted — with a one-click dispute email drafted for each flag. Verified invoices push into QuickBooks Online as bills with per-line cost codes, retainage-aware, so the checked number is the one that lands in the books. Setup takes about five minutes; there's no IT project. Contractors running verification this way report about 75% less manual review time than checking by hand, which turns "verify the suspicious ones" into "verify all of them."

The recovered money is the point. On annual material spend between $500K and $2M, checking every line against the quote has recovered an estimated $50K–$150K annually. That range is extrapolated from early pilot results — outcomes vary with invoice volume and contract complexity — but the direction is consistent: full coverage finds what triage was passing through.

You don't need to overhaul your payables process to find out what verification is worth. Pick one active job with a healthy stack of invoices already in — ideally one with a big material package quoted months ago — and run every invoice on it against the quote, line by line, using the checklist above. Not the suspicious ones. All of them.

If the job comes back clean, you've confirmed your suppliers and your review process are tight, and that's worth knowing before you bid the next one. If it doesn't — a substitution billed high, a quantity nobody signed for, a fee that was never quoted — you've found the leak while there's still time to dispute it and while the pattern can still be stopped on the rest of the job. Either way, one job gives you the number that decides whether verification deserves a permanent place in your workflow. If you'd rather have a second set of eyes on that first pass, the founder-run free audit does exactly this for one job's invoices.