Invoice Price Higher Than the PO: What to Do

Why suppliers bill more than the PO

Start with the boring truth: this is usually not fraud. It is two order-entry systems disagreeing about a price, and the invoice is simply the first place the disagreement became visible to you. Knowing which disagreement you are holding decides how you dispute it, so name it first. Five patterns cover most cases.

Price creep against your own history.The supplier's price file drifted upward across reorders, and the order was keyed at today's list price instead of the price on your PO. Nothing looks wrong on the supplier's side, because the invoice matches their system exactly. It just does not match yours, and on a part you reorder every month, the drift compounds quietly until someone compares.

Requote drift between the quote and the PO.The quote was revised, or expired, somewhere between quoting and ordering. Your PO carried one revision; the supplier's sales order carried another. This one announces itself in the paperwork: the quote number the invoice references is not the quote number your PO was cut from.

Unit-of-measure mismatch. Priced per hundred on one document and per each on the other, cases against eaches, kilograms against pounds. The tell is a delta that is a clean ratio: a unit price 10x or 100x apart, or off by 2.2046, is a conversion problem, not a pricing problem, and it can run in either direction.

Surcharges that appear at invoice time. The PO closed at a clean unit price; the invoice adds a fuel, freight, or tariff surcharge line, or folds the surcharge into the unit price itself. Whether a tariff surcharge is legitimate is its own checkable question, worked line by line in the surcharge verification guide. Either way, a charge that is not on the PO needs a basis that is not "it is a standard charge."

Tier pricing misapplied.Your quantity qualified for a volume tier on the quote, and the invoice billed the base tier anyway. Or a release against a blanket order was billed as a one-off purchase at spot pricing. The unit price is a real price from the supplier's own price list; it is just the wrong row of it for this order.

The line-level compare, from documents you already hold

Everything the dispute needs is already in your inbox or your files: the PO, the order acknowledgment, the invoice, and, when they exist, the quote and the contract behind the PO. Put them side by side and run four checks per line, in this order.

Unit of measure first. Before comparing prices, confirm both documents price the same unit. A UOM mismatch explains the largest apparent deltas, and catching it first saves you from disputing a number that is actually correct once converted.

Unit price, PO against invoice. The core comparison: for each line, the PO unit price against the invoiced unit price, then quantity times price at the extended level. Do the arithmetic yourself; extended totals carry their own errors independent of the unit price.

The acknowledgment as tiebreaker.The ack tells you when the discrepancy was born. If the supplier's ack echoed your PO price and the invoice bills higher, the error happened on the billing side, and you hold the strongest possible position: two of the supplier's own three documents agree with you. If the ack came back at the higher price and nobody flagged it at confirmation time, the drift happened months earlier, and while the PO still governs, the conversation is different, because the supplier disclosed the price and your side missed it.

The document behind the PO. If a contract or standing quote sets the price, compare the invoice against that too. An invoiced price can match the PO perfectly and still sit above the contracted rate, because the PO itself was cut wrong. The invoice-to-PO check catches billing drift; the invoice-to-contract check catches everything upstream of it.

One line, worked by hand

PO line 3 orders 8,400 EA of a machined bracket at $12.79 per unit: $107,436.00 extended. The supplier's acknowledgment echoes the line back at 8,400 EA and $12.79. The invoice arrives billing 8,400 EA at $14.32: $120,288.00 extended.

Run the checks in order. UOM: both documents say EA, so no conversion explains the gap. Unit price: $14.32 against $12.79 is $1.53 per unit, and 8,400 times $1.53 is $12,852.00 on this one line. The acknowledgment: it echoed $12.79, so the supplier's own confirmation agrees with your PO, and the invoice is the outlier among the three documents.

Notice what makes this line dangerous. The overbilling is about 12 percent: small enough to clear a percentage tolerance or a reviewer skimming a 30-line invoice, large enough to be real money. And nothing about the invoice looks malformed. The arithmetic inside it is internally consistent; it is only wrong against the documents next to it.

What to send the supplier

Line references, not vibes. "Your invoice seems high" starts a negotiation; a cited line starts a correction. The email is four items long:

• The PO number and line number, with the ordered quantity, unit of measure, and unit price.
• The acknowledgment reference and the price it echoed, if it echoed yours. This is the sentence that ends most disputes.
• The invoice number and line, the billed price, and the computed difference at the extended level.
• The ask: a corrected invoice or a credit memo for the difference, or, if they believe the billed price is right, the basis for it: which quote, which agreement, which date.

Hold the invoice out of the payment run until it resolves. Disputing before payment is a correction; disputing after payment is a collection, and you become the party asking for money back. Keep the tone procedural: most of these are order-entry mistakes, and a supplier fixes a cited line quickly. A reply of "prices have gone up" is its own answer, because it concedes the PO price was not honored and moves the conversation from billing to terms, where your PO and contract do the arguing.

Prevention: surface the mismatch before payment

The uncomfortable part is how you found this one: someone happened to look. Manual comparing is sample-based in practice. Big lines get checked, invoices that look odd get checked, and the mid-size line on reorder fourteen sails through, which is exactly where price creep lives.

The structural fix is to check the chain, not the invoice. Quote, PO, acknowledgment, receipt, and invoice verified as one connected sequence, what 5-way matching means, catches each failure where it is born: quote-to-PO catches requote drift, PO-to-ack catches the price change at confirmation time, the receipt covers the quantity leg, and the invoice against all of it catches billing drift, misapplied tiers, and surcharges that appeared at invoice time.

This is the job Kynthar does. Your ERP is a system of record: it stores the PO you entered. The acknowledgment and the invoice arrive as emails and attachments it never reads. Forward those emails to Kynthar and each document is read, body and attachments together, and connected to the PO, vendor, and item it references. The ack's echoed prices are cross-checked against the PO deterministically, invoiced prices are checked against contracted rates and your own price history, and the lines that do not reconcile land in your team's work queue with the evidence attached, before the invoice is paid. The broader family of billing patterns worth catching this way is covered in the overcharge guide, and you can run one invoice against the PO or contract behind it to see the compare on your own documents.