Two plants buy the same part from the same supplier. One clears its invoices without trouble. The other sends a price variance to AP every month, and every month someone approves it because the amount is small. Before you widen the tolerance, find out where the difference starts. It may be in how the plant buys the part, how it receives it, or what the supplier is charging.
“Price variance” gets used for two different things, and mixing them up sends the exception to the wrong person.
Two variances, two owners
| Variance | Compares | Question it answers | Owner |
|---|---|---|---|
| Purchase price variance (PPV) | PO price vs standard cost | Did we buy at the cost we planned? | Cost accounting and purchasing |
| Invoice price variance (IPV) | Invoice price vs PO price | Did the supplier charge what we agreed? | AP and the buyer |
A bill can match the PO perfectly and still produce PPV, because the PO price itself differs from standard. And an invoice can be above the PO even when the PO matches standard. Oracle’s cost management documentation distinguishes purchase price variance at standard cost from invoice price variance. Oracle’s standard-cost variance documentation Use your own ERP’s costing method and posting rules when reconciling the ledger.
Illustrative example: one receipt, both variances
You receive 100 units. Standard cost is $9. The approved PO price is $10. The supplier bills $11 per unit. Ignoring tax, freight, and currency:
| Comparison | Per unit | × 100 units |
|---|---|---|
| PO price vs standard (PPV) | $10 − $9 = $1 | $100 unfavorable |
| Invoice vs PO (IPV) | $11 − $10 = $1 | $100 unfavorable |
| Invoice vs standard (total) | $11 − $9 = $2 | $200 unfavorable |
The first $100 belongs in the cost review: either the standard is stale or purchasing negotiated above plan. The second $100 needs the buyer to confirm an approved price change or dispute the bill.
In a standard-costing system that recognizes PPV at receipt, the entries might look like this:
- Receipt: debit inventory $900 (100 × $9), debit PPV $100, credit GR/IR or accrued purchases $1,000 (100 × $10).
- Invoice: debit GR/IR $1,000, debit invoice price variance $100, credit AP $1,100.
Some systems recognize PPV at invoice instead, or roll IPV into inventory under certain costing methods. Confirm your configuration before building reports on these accounts.
What a “price” variance often turns out to be
A line flagged as a price variance often isn’t a price change. Rule these out before sending anything to the buyer.
| What the bill shows | What’s often happening | First record to check |
|---|---|---|
| Unit price far above the PO | Supplier bills per case, PO is per piece | Item record, approved purchase unit, pack size |
| Unit price a little above the PO | Freight or a surcharge spread into the line price | Shipping terms and the invoice’s charge lines |
| New unit price | Approved price change not yet on the PO | Amendment or rate card and its effective date |
| Different quantity tier | Price break based on a different purchase quantity | Agreed price breaks and order quantity |
| New fuel, material, or handling surcharge | Surcharge allowed (or not) under the agreement | Agreement clause and the calculation basis |
| Small difference, foreign-currency supplier | Exchange rate between PO and invoice dates | Rates on the PO, receipt, and bill |
Illustrative examples: not a price change
Unit of measure. The PO says $0.85 per piece. The invoice says $10.20 per case. If a case is 12 pieces, $10.20 ÷ 12 = $0.85. No variance; the system needs the conversion. Keep the supplier’s original values on the bill so the buyer can see how AP got there, and route any unknown pack size to the buyer rather than guessing.
Freight in the line. The PO is $10.00 per unit for 100 units. The invoice shows $10.40. The supplier rolled a $40 freight charge into the line ($40 ÷ 100 = $0.40). If the agreement allows freight, it should be a separate charge so it can be checked and allocated; see freight invoice audit.
Work through a disputed line
- Pull the records. Approved PO version, receipt, and vendor bill for the disputed line.
- Line them up. Quantity, unit of measure, unit price, and currency side by side.
- Separate price from quantity. If the billed price differs, ask the buyer for the amendment or rate card. If quantities differ, involve receiving. Keep freight and other charges visible as their own lines.
- Decide and record. Approve against an authorized change, or dispute. Record the decision before approving the bill.
- Follow it through payment. If you dispute, keep the claim tied to the invoice until the credit posts.
Blanket orders and releases
For a blanket order, start with the release the supplier invoiced, not the current price list. The price approved for that delivery may differ from today’s price.
Illustrative: a release was approved at $12 per unit, and the bill shows $13 for 50 units. The difference is $50 (50 × $1). Find the effective date of the $13 price and compare it with the release terms. If the old price applies and the supplier agrees to credit, keep the $50 claim tied to the invoice until the credit posts. If the new price was authorized, keep the buyer’s approval with the corrected purchase record. Release reconciliation is covered in ERS, consignment, and scheduled releases.
How this works in your ERP
NetSuite. Oracle documents that NetSuite distinguishes bill price, quantity, and exchange-rate variances between purchase orders, receipts, and bills. Oracle’s guide to accounting for received purchase orders Posting depends on whether the line uses Match Bill to Receipt. Under the PO-line method, the line must be fully received and billed before variances are generated. Check the method in use before treating a missing variance journal as evidence that the bill matched. Oracle’s vendor bill variance guide
Epicor Kinetic. Epicor describes supplier cross-references, part price breaks, purchase order tracking, and receipt tracking in Kinetic Supply Chain Management. Epicor’s Kinetic supply chain overview Epicor also lists accounts payable in its Financials Core offering. Epicor Financials Core Use the records your installation exposes and check which values purchasing actually approved. When evaluating a tool, give it a bill above the order price and ask it to show which price was authorized and whether the remedy is a PO correction or a dispute.
Any ERP. Trace each variance to the affected line before combining variances in a management report. A report that nets a favorable price variance against an unfavorable quantity variance hides two problems.
Find the recurring ones
A one-off error goes back to the supplier. A repeated difference usually means something upstream is wrong.
| Repeated variance | First record to check | Who can fix the source |
|---|---|---|
| Same unit price difference every month | Approved price and when it took effect | Purchasing |
| Quantity differs at one plant | Receipt date, location, and packing unit | Receiving |
| Freight appears as an item price difference | Shipping terms and invoice freight line | Buyer and cost accounting |
| AP chooses the wrong plant | Invoice address, PO, and vendor record | AP and vendor-master owner |
| Variance only on one supplier’s invoices | Compare several invoices against the last approved price change | Buyer |
Pull invoices from two plants for the same supplier. Record what the bill said, what the ERP expected, and what resolved each difference. Count repeated cases by cause. If price changes are approved but never make it onto the PO, fix that handoff with purchasing. If the plant receives in pieces and the supplier bills in cases, fix the conversion and rerun the same bills.
Tolerances: change them last
Keep the current tolerance while you run the comparison. A wider tolerance makes the queue shorter, but it also lets real overcharges through and hides upstream problems.
If you do change it, test a valid freight charge and an overcharge on the same invoice. The reviewer should see which difference passed and which needs a decision. Record the reason for the change. Bills that exceed tolerance usually go on hold; see invoice holds and payment blocks for releasing them safely.
What goes wrong
- PPV and IPV in one bucket. Cost accounting and AP each assume the other owns it.
- Variance approved because it’s small. Repeated small approvals add up and never reach purchasing.
- Missing variance journal read as a match. On PO-based variance methods, nothing posts until the line is fully received and billed.
- Credit agreed but never tracked. The supplier agrees to credit the $50 and AP pays the full bill anyway.
- Standard costs never revisited. PPV becomes background noise.
Monthly PPV review checklist
- PPV and invoice price variance reported separately
- Each material variance traced to a PO line, receipt, and bill
- Unit-of-measure and freight-in-price cases ruled out before buyer review
- Price changes checked against effective dates of approved amendments
- Disputed amounts tied to the invoice until the supplier credit posts
- Repeated variances counted by supplier, part, plant, and cause
- Standard costs flagged for review where PPV recurs in the same direction
- Tolerance changes tested on a valid charge and an overcharge, with the reason recorded
For more receipt and split-delivery cases, see AP automation for manufacturers.