An invoice discrepancy is any mismatch between a vendor’s invoice and what you actually authorized or received: a price that is higher than the quote, a quantity you never got, a duplicate, or a bill for work no one confirmed. Caught before payment, it is a two-minute hold. Caught after, it is a clawback, a credit memo, and a vendor call. This guide shows you how to catch discrepancies before the money leaves.
Here is what that looks like in practice. A plumbing invoice lands for $1,240. The work order approved $800. Nobody flagged it, it gets coded, it gets paid, and three weeks later it is a variance you have to explain to the CFO. If you run accounts payable at a growing company, you have lived some version of this.
The example above is deliberate. The hardest discrepancies to catch are not the warehouse kind, where a purchase order, a goods receipt, and a bill for physical items all line up on paper. They are the service kind: a work order, no packing slip, and a bill that arrives higher than expected. Property management is the sharpest case of this, so we use it as the running example, but the control works the same in construction, facilities, and any team that buys services against an authorization.
TL;DR for finance teams
- An invoice discrepancy is a mismatch between the invoice and the purchase order, work order, or receipt. The most common form is a price that exceeds what was authorized.
- The three usual causes: scope creep after the job starts, no PO or work order tied to the spend, and manual matching that skips the busy months.
- Catching a discrepancy after payment means clawing money back. Catching it before payment means a short hold. The cost gap between those two is large.
- The fix is a matching step that compares the authorization, the receipt of goods or work, and the invoice before anyone approves payment.
- ProcureDesk automates that match and holds any invoice that does not line up, before payment. Card tools and payment tools do not, because they act after the charge.
Table of Contents
The short version
Property management AP breaks at the point where field work meets the invoice. A maintenance supervisor approves a repair verbally, the vendor does more than expected, and the invoice arrives higher than the work order with no one positioned to notice. The fix is not more people checking invoices at month-end. The fix is a matching control that sits between the invoice and the payment, compares the invoice to the original work order and the confirmation that work was done, and holds anything that does not match. Done manually this is slow and skips busy cycles. Done with software it runs on every invoice, every property, every time.
What is an invoice discrepancy, and what are the types?
An invoice discrepancy is a mismatch between a vendor’s invoice and its purchase order, work order, or receipt. The five you will see most often are:
- Price discrepancy. The invoice bills more than the quote, PO, or work order authorized. The most common of all.
- Quantity or scope discrepancy. You are billed for more units or more work than you received or approved.
- Duplicate invoice. The same bill arrives twice, often through two channels, and gets paid twice.
- Timing or terms discrepancy. Delivery dates or payment terms on the invoice do not match the agreement.
- Unverified work. An invoice for a job no one confirmed was actually completed.
For teams that buy services rather than goods, the price and unverified-work types dominate, and they are the hardest to catch because there is no packing slip to check against.
Discrepancy vs dispute vs duplicate payment
These get used interchangeably, so here is the clean distinction. A discrepancy is the mismatch itself, found before or after payment. A dispute is what happens when you formally push back on a vendor over a discrepancy. A duplicate payment is the worst outcome: a discrepancy that was never caught, so the same invoice got paid twice. The entire point of a matching control is to keep discrepancies from ever becoming disputes or duplicate payments.
Why discrepancies cluster in property management
You are managing maintenance vendors across many properties, work is approved in the field, and the person who approves the repair is rarely the person who pays the bill. That split, multiplied across every property, is where discrepancies live. The same pattern shows up in construction (subcontractors) and manufacturing (MRO), any place work is authorized away from the desk that pays for it.
Why do maintenance invoices so often not match the work order?
Most mismatches trace back to three causes, and all three are structural rather than careless.
First, scope creep on site. A vendor is dispatched for a $600 job, opens the wall, finds more damage, and keeps working. The extra work is real. The problem is that nobody updated the authorization, so the invoice looks wrong even when it is not.
Second, no purchase order tied to the work order. When a work order is just an email or a verbal go-ahead, there is no committed number for AP to match against. The invoice becomes the first hard record of the cost, which is far too late.
Third, manual matching that skips the busy months. Many teams do match invoices to work orders by hand. It works in February. It falls apart at year-end when volume triples and the AP team is trying to close the books.
What does an unmatched invoice actually cost you?
The direct cost is the overbilled amount you pay and rarely recover. The larger cost is the time your team spends chasing context after the fact.
Consider the sequence. An invoice that does not match a work order pulls an AP staffer off close to call the property manager. The property manager calls the vendor. Days pass. Meanwhile the books cannot close cleanly because the variance is unexplained. Industry AP benchmarks put the fully loaded cost of processing a single invoice in the range of several dollars to well over ten dollars once labor and rework are included, and a disputed invoice costs several times a clean one. Multiply that by the number of maintenance vendor invoices you touch each month and the number stops being small.
There is a compliance cost too. If you carry properties that face audits or owner reporting, an invoice paid above its authorized amount with no documented approval is exactly the kind of finding that turns a routine review into a long one.
How do you catch a discrepancy before you pay it?
You catch it by inserting one control between the invoice and the payment: a match against the work order and the confirmation that the work was done. If any of the three do not line up, the invoice goes on hold instead of into the payment run.
This is the single highest-leverage change a property management finance team can make. It moves the check from after the money moves to before. A discrepancy caught before payment is a two-minute hold and a quick question to the property manager. The same discrepancy caught after payment is a clawback, a credit memo, and a vendor relationship to manage.
The PO and receipt agree. The invoice does not. See it caught on your own invoices.
Book a demoInvoice verification, reconciliation, and matching: how they connect
These three terms describe the same goal at different points. Invoice verification is the check that an invoice is legitimate and correct. Invoice reconciliation is confirming the invoice agrees with your records. Matching is the mechanism that does both: comparing the invoice to the authorization and the receipt. Two-way and three-way matching are the two versions of that mechanism.
Two-way matching compares the invoice to the work order or purchase order. Three-way matching adds a third document: confirmation that the work was actually received or completed. For service and maintenance spend, three-way matching is stronger because it stops you from paying for work that was authorized but never verified.
Here is how the three pieces map to property management:
- The work order or PO is the authorization. It says what was approved and for how much.
- The receipt or completion confirmation is the proof. The property manager or on-site staff confirms the work is done.
- The invoice is the bill. It should match the first two.
When all three agree, the invoice is safe to pay automatically. When they do not, it should stop. That stop is the entire game.
How to build a work-order-to-invoice matching process
You can put a working control in place with five steps. This is the how-to your AP team can run starting this month.
- Require a work order or PO for every maintenance job. No authorization number, no dispatch. This gives AP a committed figure to match against.
- Capture completion confirmation. Have the property manager or site contact confirm the work is done before the invoice is cleared. This is your receipt.
- Match on three points. Compare the invoice to the work order and the completion confirmation. Check price, quantity, and property.
- Hold anything that does not match. Route mismatches to a named owner with the work order attached, so the question can be answered in minutes, not days.
- Track your discrepancy rate. Measure what percentage of invoices get held and why. That number tells you which vendors and which properties need attention.
Done by hand, this process is sound but fragile. It depends on a person having time. Done with procurement and AP automation software, it runs on every invoice automatically, as part of your invoice workflow, and does not skip the month you are busiest.
How do you resolve an invoice discrepancy you have already found?
If the invoice is already in front of you and does not match, work it in four steps. First, hold the payment so the clock stops. Second, categorize the gap: price, quantity, duplicate, terms, or unverified work. Third, pull the source documents, the work order or PO and the completion confirmation, and compare line by line. Fourth, resolve it with the vendor through an amended invoice, a credit, or a documented change order, and log the outcome. Catching it before payment turns this four-step cleanup into a two-minute hold, which is the whole reason to match early.
Every invoice checked against its PO and receipt before a dollar moves. Watch a mismatch get held in 20 minutes.
Where software fits, and how the options differ
Software fits at step three and step four, the matching and the hold. This is where the honest comparison between tools matters, because not every tool built for finance actually does this.
ProcureDesk captures the purchase at the point of request, issues the work order or PO, records completion, and runs automated three-way matching before payment. Any invoice that does not match the work order and the receipt is held and flagged. It syncs to QuickBooks, Sage Intacct, NetSuite, and Microsoft Business Central, so the matched, coded invoice lands in your accounting system without rekeying. This is spend control before the invoice is paid, not a report you read after.
Bill.com processes and pays invoices well, but it sits after the invoice arrives. It is built for the payment step, not for matching a maintenance invoice back to an authorized work order before you commit. Many teams run ProcureDesk for the control and Bill.com for the payment.
Ramp and other card-first tools manage what happens after a card is swiped. There is no work order, no completion confirmation, and no three-way match. For a property management company where maintenance vendors bill you directly rather than take a card, cards alone do not catch the mismatch.
Here is the distinction. ProcureDesk controls what gets committed and verifies it before payment. Payment and card tools handle what already happened. If your problem is invoices that do not match the work order, you need the control that runs before the payment.
Frequently Asked Questions
01What is a work-order/invoice discrepancy?
It is a mismatch between the amount or scope a maintenance work order authorized and what the vendor’s invoice actually bills. The most common form is an invoice that costs more than the approved work order.
02Why is this so common in property management?
Work is approved in the field, often verbally, and the person who authorizes a repair is usually not the person who pays the invoice. That gap, spread across many properties, produces frequent mismatches.
03How do I catch a discrepancy before paying it?
Add a matching step between the invoice and the payment. Compare the invoice to the work order and to confirmation that the work was done. Hold anything that does not line up before it enters the payment run.
04What is the difference between an invoice discrepancy and an invoice dispute?
A discrepancy is the mismatch itself. A dispute is the formal pushback with the vendor once a discrepancy is found. Catching discrepancies before payment keeps most of them from ever turning into disputes.
05How do you prevent duplicate payments?
Match every invoice against its authorization and check the invoice number before payment. A duplicate is a discrepancy that slipped through, so the same control that catches price and quantity gaps also stops the same bill from being paid twice.
06What is the difference between two-way and three-way matching?
Two-way matching compares the invoice to the work order or PO. Three-way matching adds confirmation that the work was received or completed. Three-way is stronger for maintenance because it stops payment for work that was never verified.
07Can Bill.com or Ramp catch these mismatches?
Not before payment. Bill.com processes invoices after they arrive, and card tools act after a swipe. Neither matches a maintenance invoice to an authorizing work order before you commit the money.
08Do I need to replace my accounting system?
No. A procurement and AP automation tool sits in front of your accounting system and syncs the matched, coded invoice into QuickBooks, Sage Intacct, NetSuite, or Microsoft Business Central.
Watch a mismatched invoice get held before a dollar goes out.
