Purchase Price Variance: What the Number Means and What AP Should Do About It

Purchase price variance is the difference between the price actually paid for an item and the price that was expected, multiplied by the quantity purchased. The expected price is either the standard cost carried in the ERP or the price agreed on the purchase order.

The formula takes about four seconds to learn. What takes longer is deciding what to do on a Tuesday afternoon when an invoice arrives eleven dollars over the PO and somebody has to either pay it, hold it, or send it back to procurement. That decision is governed by a tolerance number, and in most companies nobody alive remembers where that number came from.

Key Takeaways

• PPV equals actual price minus standard or PO price, times quantity. Positive is unfavorable under the common sign convention; negative is favorable.

• A favorable variance is not automatically good news. It can mean a substitution, a quality change, or a standard cost that has gone stale.

• The variance surfaces during three-way matching, and whether it stops the payment depends entirely on the tolerance you configured.

• Tolerances should be set by dollar impact and exception cost, not inherited from whatever the system shipped with.

• Small-value variances cost more to resolve than they are worth, which is an argument for moving low-value buying onto controlled cards instead of POs.

What is purchase price variance?

Purchase price variance measures whether you paid what you planned to pay for a purchased item. In a standard costing environment it compares the invoice price to the standard cost held in inventory; in a PO-based environment it compares the invoice price to the price on the order.

Which baseline you use changes what the number means. Against standard cost, PPV tells you whether your cost model still reflects the market. Against the PO, it tells you whether the price your buyer negotiated is the price the supplier billed, which is a supplier compliance question rather than a costing one. Plenty of teams report one and interpret it as the other.

What is the formula, and which way does the sign run?

PPV equals actual unit price minus expected unit price, multiplied by actual quantity purchased. Work it with real figures:

Illustrative figures for the calculation. Not client data.

The sign convention trips people up because it inverts between disciplines. Most ERPs record a positive PPV when actual exceeds standard, and label that unfavorable, since the company spent more than planned. Some management reporting flips the sign so that favorable results show as positive numbers on a variance report. Both conventions are defensible and mixing them in one company is not, so write yours down.

What makes a variance favorable or unfavorable?

Paying less than expected is favorable; paying more is unfavorable. The labels describe direction against plan, and they carry no judgment about whether anything good or bad happened.

That distinction matters more than the arithmetic. A buyer who hits an unfavorable variance because a steel price moved 9% in a quarter did nothing wrong, and a buyer who books a favorable variance by substituting a lower grade of material may have created a warranty problem. Price movement is real and it is external. The producer price index for final demand rose 0.4% in August 2026 and 5.4% over the twelve months ended August 2026, according to the Bureau of Labor Statistics' Producer Price Index news release for the month. Against a standard cost set last January, that alone generates unfavorable variance across a whole category with no purchasing decision behind it.

Why does a purchase price variance appear at all?

Because the expected price was set at one moment and the purchase happened at another, and something changed in between. The useful analytical move is separating causes that sit with procurement from causes that sit with the standard itself, since those two groups get fixed by different people.

Which causes sit with procurement?

Buying decisions, mostly, and they are the ones a variance report is supposed to make visible:

• Rush orders placed inside lead time, which usually carry a premium

• Orders placed below a volume break the contract price assumed

• Off-contract or maverick buying from a supplier outside the agreement

• A negotiated price change that was never reflected on the PO or in the item master

• Freight or surcharge terms that differ from the quoted basis

The fourth cause is the one I see most often and the one nobody logs. Procurement renegotiates and the buyer knows, then AP finds out when the invoice arrives and fails the match. Sector data suggests the better-run procurement functions treat that handoff as part of the savings rather than an afterthought. Procurement leaders met or exceeded plan on cost savings 96% of the time against 80% for followers, and on cost avoidance 94% against 75%, according to Deloitte's 2025 Global Chief Procurement Officer Survey. A negotiated price that never reaches the ERP is a saving that exists in a slide deck.

Which causes sit with the standard cost itself?

A standard set annually is wrong by construction for most of the year. Goods and services also move at different rates, which breaks any single escalation assumption applied across a category. Final demand goods prices advanced 1.1% in August 2026 while final demand services rose 0.1%, an eleven-fold gap in one month between what a buyer pays for goods and what it pays for services, per the same Bureau of Labor Statistics release.

Currency, commodity indexation, and supplier mix changes belong in this group too. The tell that your standard is the problem rather than your buyers is a variance that runs consistently in one direction across many suppliers in a category. One supplier running unfavorable is a supplier conversation, and an entire category running unfavorable is a costing conversation.

Reviewing variance causes is also a decent way to find out how much of your spend is running outside the process you think it is running through. If a lot of it is, the procure-to-pay chain is worth mapping end to end before touching tolerances.

What should AP do when the invoice price does not match the PO?

Categorize before escalating. An AP clerk who emails procurement about every price difference trains procurement to ignore the emails, and an AP clerk who pays every small difference trains suppliers to send them.

Where does the variance surface inside three-way matching?

At the price comparison between the invoice line and the PO line, after quantity has been checked against the receipt. A price difference inside tolerance posts the variance to a PPV account and lets the payment proceed. A difference outside tolerance creates an exception that blocks payment until someone resolves it.

Understanding where it fires matters because it determines what evidence is available at that moment. The matcher has the PO, the receipt, and the invoice, which is enough to tell you the price differs and nothing about why. That is why exception routing has to carry the invoice to a person who knows the commercial context, a point the guide to three-way matching develops in more detail. The document-level distinctions behind the match are covered in purchase order vs invoice.

Which variances should hold payment and which should not?

Hold when the difference is large enough to matter, when the pattern is repeating, or when there is no documented authorization for the change. Pay when the difference is inside tolerance, or when it is documented and immaterial and the cost of the exception exceeds the amount in dispute. Here is the routing I would put on the wall:

Illustrative routing table for discussion, not a control standard.

The bottom two rows are where money actually leaks. A supplier adding a small percentage to every invoice collects real dollars precisely because each instance is too small to argue about, and only a pattern view catches it. That pattern is also where a price variance stops being an accounting question. Of 2,402 occupational fraud cases across 143 countries causing more than $3.4 billion in losses, asset misappropriation, the category containing billing schemes, appeared in 90% of cases, at a median loss of $104,000 and a median 12 months before detection, according to the Association of Certified Fraud Examiners' Occupational Fraud 2026: A Report to the Nations. A repeating small overage that nobody ever aggregates is exactly the shape that report describes. Routing design generally, including who gets exceptions and how long they sit, is worked through in invoice approval workflows.

Protect cash flow with modern AP

Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.

Download the whitepaper

Where does the tolerance number come from?

It should come from arithmetic about your own exception cost, and in most companies it came from a consultant in 2014. Somebody set 5% or $50, the system has enforced it ever since, and the buying profile it was set against has changed twice.

How do you set a threshold that is defensible?

Start from what an exception costs you to work, then set the threshold so you are not spending more to resolve a variance than the variance is worth. If a touched exception takes twenty minutes of a person's time end to end, a dollar threshold below roughly that labor cost is guaranteed to lose money on every instance.

Then layer three refinements onto the base number:

• Combine a percentage with an absolute dollar floor, so the rule does not wave through four figures on a large order or trap three dollars on a small one

• Set different tolerances by category, since a volatile commodity deserves more room than a contracted service with a fixed rate card

• Cap the percentage in absolute terms on your largest orders, where a small percentage is a large cheque

Automation changes the arithmetic underneath all of this, because it changes what an exception costs. Companies with a touchless invoice-processing rate of 30% or higher average 3.5 times higher AP productivity, the evaluated platforms' customers averaged a 60% touchless rate, and AP cycle times improved 59% after implementation, according to The Hackett Group's Digital World Class Matrix for accounts payable. When the cost of handling an exception falls, the defensible tolerance tightens.

What does a priced change order do to the tolerance?

It removes the variance rather than excusing it. A properly executed change order amends the PO, so the invoice matches the revised order and the price difference never reaches the tolerance test at all. That is the outcome you want, and it depends entirely on the change order reaching the ERP before the invoice does.

When it does not, you get the worst version of this process, where a legitimate price and an unmatched invoice produce a two-week email thread that ends with someone overriding the match. Give procurement a same-day path to amend a PO and most of your unfavorable exception volume goes away. Tie the approval path for the change to the same routing you use for a purchase requisition so it inherits a control rather than needing a new one.

What does purchase price variance not tell you?

It does not tell you whether the purchase was a good decision. PPV is a price measure on a single dimension, silent on quality and delivery reliability, on total cost of ownership, and on whether you needed the item at all.

When is a favorable variance a warning?

When it comes from a substitution, a quantity break you bought into by over-ordering, or a standard that has drifted above market. Each of those produces a number that reads as good news on the variance report while something worth knowing is happening underneath.

Over-buying to hit a price break is the sneakiest, because it converts a P&L variance into a balance sheet problem. The favorable PPV posts this period and the excess inventory carries cost, obsolescence risk, and storage for as long as it sits. If the buyer is measured on PPV, you have paid them to do it.

A stale standard shows up differently. Consistent favorable variance across an entire category, with no purchasing initiative behind it, means the standard is above market and every product costed with it is showing a margin you do not have.

Which second metric belongs next to it?

Something that measures the rest of the decision, because a price number read alone rewards behavior you would not choose. Three additions cover the ground PPV ignores:

• Price variance by supplier over time, which separates market movement from supplier behavior

• Cost avoidance and on-time delivery, which measure the parts of the decision price cannot

• Total landed cost, which catches the freight and duty games a unit price hides

Risk posture is the fourth axis, and procurement leaders say so themselves. 74% of chief procurement officers named alternative supply sources their most effective risk mitigation, 64% prioritized supply chain visibility, and 61% named supplier collaboration, per the same Deloitte survey. A sourcing strategy optimized purely on unit price tends to concentrate supply, which is the opposite of what those answers describe.

Companies that track spend at a category level rather than invoice by invoice generally catch these tradeoffs earlier, which is one of the practical arguments for the broader discipline in spend management.

Resolve price variances at receipt with Corpay

The variance that costs the most is the eleven-dollar one sitting in a queue for two weeks, because the handling cost dwarfs the amount and the supplier is now calling about it. AP automation from Corpay captures every supplier invoice as structured data, runs the match against the PO and the receipt automatically, and routes only genuine exceptions to a person, with the payment going out by virtual card, ACH, or check once it clears.

Fully managed AP handles the supplier-facing half of that loop. We enroll your suppliers, deliver the payments, and take the follow-up calls, which typically returns about 40% time saved on payables work, and most customers go live in weeks. Paying by card also returns money rather than consuming it, with $800M+ in rebates paid to customers per year.

The direction of travel supports the move. Checks accounted for 26% of B2B payments in 2025, down from 33% in 2022, and 76% of organizations plan to update their payments strategy within the next three years, according to the Association for Financial Professionals' 2025 AFP Digital Payments Survey.

What does structured invoice capture change about variance handling?

It moves the detection from close to receipt. When an invoice enters as data on arrival, the price comparison happens immediately, the exception is raised while the receiving record is fresh, and procurement can still get the supplier on the phone about an order placed last week rather than last quarter.

The second change is categorical rather than procedural. Card-based buying with defined limits removes whole classes of low-value variance from the queue, because a controlled card purchase has no PO to disagree with and no standard cost to miss. Moving small-ticket, high-frequency spend onto corporate purchase cards with per-transaction and merchant limits is often the fastest way to cut exception volume, and the control design is covered in card controls and spend policies. Single-use virtual cards handle the one-off buys that would otherwise become a PO nobody wants to raise.

Worth naming honestly. Shifting spend to cards relocates price risk rather than removing it, moving the control from a matching tolerance to a spend limit, which fits small purchases well and contracted volume buys poorly.

Which ERPs does it connect to?

Corpay maintains 100+ ERP integrations, including NetSuite, Sage Intacct, Microsoft Dynamics 365 Business Central, and Acumatica, connected by API, SFTP, or file-based transfer. For variance work, the questions that decide fit are whether the integration reads PO and receipt data for matching and whether it can write the PPV posting to the account your controller expects.

Ask to see the exception queue at a reference customer with your invoice volume, not in a demo environment, and ask what percentage of their invoices touch a human. That number tells you more about what your team's week will look like than any feature list. The surrounding steps are mapped out in the guide to the accounts payable process.

Frequently Asked Questions

What is purchasing price variance?

Purchasing price variance is another name for purchase price variance, the difference between the price actually paid for an item and the standard or purchase order price, multiplied by the quantity bought. It isolates the price component of a cost difference, separate from any usage or quantity variance.

What is an unfavorable purchase price variance?

An unfavorable variance means you paid more per unit than the standard or PO price, so actual cost exceeded plan. Common causes include rush orders, buying below a volume break, off-contract purchasing, and price increases that were agreed but never reflected on the purchase order.

What is the formula for calculating purchase price variance?

Actual unit price minus expected unit price, multiplied by the quantity purchased. Using the worked example in this article, a seventy-cent gap across four thousand units gives an unfavorable variance of twenty-eight hundred dollars.

What is PPV in simple terms?

PPV is the gap between what you thought something would cost and what you actually paid, expressed in dollars for the whole purchase. It answers one narrow question about price, and it says nothing about quality, delivery, or whether the purchase should have happened.

What tolerance should AP use before holding an invoice?

Set it from your own exception handling cost, using a percentage with an absolute dollar floor so the rule behaves sensibly on both large and small orders. Many mid-market teams land in the low single digits as a percentage, with a floor somewhere between $25 and $100, then tighten it by category once exception volume is measured.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

AP Automation

Procure-to-Pay