On the 28th, the financial controller opens the purchase price variance account and finds an unfavorable balance nobody saw coming. Purchasing says it stuck to the negotiated prices. Accounts payable approved every invoice. The balance is there all the same, and it is about to eat into the month’s gross margin.
That variance has a name: PPV, or purchase price variance. It measures the gap between the price at which the ERP values goods in inventory and the price actually paid to the supplier. Handled well, it becomes a steering signal for procurement. Handled badly, it piles up in a catch-all account and distorts product margins.
This guide is for financial controllers, CFOs and procurement leads. It explains where the variance arises, which entries the ERP posts depending on the valuation method, how to configure the system and how to break the variance down at close. All figures in the examples are fictional: they are there to illustrate the reasoning, not to serve as market benchmarks.
What PPV Is and Why It Distorts Margins When Mishandled
PPV follows a simple formula:
PPV = (actual price − reference price) × quantity
The reference price is the standard price under standard costing, or the purchase order price when you compare order and invoice. A positive variance (actual price higher) is unfavorable; a negative variance is favorable.
Three effects explain why the variance deserves attention:
- It is invisible in product cost. Under standard costing, manufactured goods carry components at their standard price. If the actual price drifts by 4%, the reported product margin stays intact, and the variance sits in a separate account that nobody reconciles to the product.
- It accumulates. A few cents per unit, multiplied across thousands of lines, ends up weighing more than an isolated billing error.
- It mixes causes of different natures. Price increase, rush purchase, currency movement, data entry error: a single balance says nothing about where it came from.
For the broader choice between standard and actual costing, see our guide on standard costing vs. actual costing in manufacturing. Here we assume a standard price exists and that you need to manage the variance it generates.
Where the Variance Arises: Order, Receipt, Invoice
The variance does not arise in a single place. It can appear at three points in the purchasing flow, and each produces a different entry. Three-way matching compares order, receipt and invoice. PPV is its accounting extension: once the invoice is accepted, what do you do with the difference?
Price Variance
This is the main case. Either the order price differs from the standard price (the supplier raised its tariff after the standard was set), or the invoice price differs from the order price (forgotten discount, material surcharge, pricing error). The two sources are not treated the same way: the first is a standard variance, which belongs to pricing policy; the second is an invoicing variance, which belongs to supplier control.
Quantity Variance
The invoiced quantity differs from the received quantity. This is not PPV in the strict sense: the ERP normally blocks the invoice at matching, or lets it through within tolerance. But a poorly set quantity tolerance creates a value variance that gets confused with PPV if the accounts are not separated.
Exchange Rate Variance
For a purchase in foreign currency, the base-currency price depends on the rate. If the standard was set at a budget rate of 1.10 and the order is placed at 1.05, the converted price is 4.8% higher without the supplier having moved its tariff. This is not the same as a realized exchange difference between invoice and payment, which is booked in financial result. For rate management, see our guide on multi-currency management in ERP.
Journal Entries by Valuation Method
PPV exists as a distinct account only under certain methods. Depending on the valuation chosen, the variance lands in a variance account, in the inventory value or in cost of goods sold. The inventory valuation guide covers each method in detail. Here is the impact on the variance.
Common fictional example: a component has a standard price of €10.00. You order and receive 1,000 units at a purchase order price of €10.40. The supplier then invoices €10.50 per unit (excluding VAT, for simplicity).
Standard Price
Inventory is always valued at standard. The variance is posted immediately to a variance account.
At goods receipt (1,000 × €10.00 to inventory, receipt liability at the order price):
| Account | Debit | Credit |
|---|---|---|
| Inventory | 10,000 | |
| Purchase price variance (PPV) | 400 | |
| Goods received/invoice received (GR/IR) | 10,400 |
At invoice (€10,500 against €10,400 received):
| Account | Debit | Credit |
|---|---|---|
| Goods received/invoice received (GR/IR) | 10,400 | |
| Purchase price variance (PPV) | 100 | |
| Accounts payable | 10,500 |
Total PPV is €500, unfavorable: €400 of standard-to-order variance and €100 of order-to-invoice variance. Inventory stays at €10.00 per unit, so the cost of manufactured products does not move. That is the method’s advantage, and its risk: the variance does not flow into product margin until someone analyzes it.
Moving Average Cost
Inventory is valued at the average price. There is no PPV in the standard-costing sense: the price paid changes the inventory value.
Suppose 2,000 units in stock at €10.00 (€20,000). After the receipt at €10.40:
| Account | Debit | Credit |
|---|---|---|
| Inventory | 10,400 | |
| Goods received/invoice received (GR/IR) | 10,400 |
Inventory rises to 3,000 units worth €30,400, an average cost of €10.133. At invoice, the €100 variance increases inventory value further if the units are still on hand:
| Account | Debit | Credit |
|---|---|---|
| Goods received/invoice received (GR/IR) | 10,400 | |
| Inventory | 100 | |
| Accounts payable | 10,500 |
The catch: if part of the units has already been consumed between receipt and invoice, the share of the variance corresponding to the units issued can no longer be attached to inventory. Depending on the ERP and its configuration, it goes to a variance account or to cost of goods sold. This is why a variance account also exists under moving average.
FIFO
Each receipt creates a cost layer. There is no standard-cost PPV, and the variance follows the layer.
The receipt creates a layer of 1,000 units at €10.40. The invoice at €10.50 corrects that layer (1,000 × 0.10 = €100) as long as it has not been consumed. If units from the layer have already been issued, the correction for the consumed portion goes to cost of goods sold or a variance account.
| Method | Where the price variance goes | Effect on product margin |
|---|---|---|
| Standard price | Variance account (PPV) from receipt | None, until the standard is revised |
| Moving average | Inventory value, then cost of goods sold on consumption | Smoothed over time |
| FIFO | Receipt layer, then cost of goods sold | Delayed according to stock turnover |
Configuration: Variance Accounts, Tolerances, Invoice Blocking
A usable PPV rests on three settings.
Variance accounts. Separate at least purchase price variance, exchange rate variance at receipt and quantity variance. A single account mixes causes you will have to untangle by hand. Set the mapping rule by material category, not by item, to keep the chart of accounts readable.
Price tolerances. They decide which invoices pass without a block. A tolerance that is too wide lets silent drift through; one that is too narrow overloads accounts payable. Think in terms of percentage and value cap, with separate rules for favorable and unfavorable variances. The method is the same as for three-way match tolerances.
Invoice blocking. When the variance exceeds tolerance, the invoice is blocked and follows an approval route: the buyer for a price issue, the warehouse for a quantity issue. Define who decides and within what time, otherwise blocked invoices age until close.
ERPs do not use the same terms for these settings. The table below gives an orientation, to be checked against your version and edition: accounts and options vary with configuration and localization.
| Topic | SAP (ECC / S/4HANA) | Dynamics 365 Finance | Odoo |
|---|---|---|---|
| Method choice | Material price control: standard price or moving average price | Item model group: standard cost, moving average, FIFO | Costing method on the product category: standard, average or FIFO |
| Purchase variance account | Posting keys for price differences, set in account determination | Accounts in the inventory posting setup | Variance account on the product category, depending on the automated valuation enabled |
| Invoice tolerances | Tolerance keys and invoice blocking | Invoice matching tolerances, by vendor group or item | Billing control and matching, depending on installed modules |
Monthly Analysis: Breaking the Variance Down
A PPV balance is not information. Close must break it down into causes someone can act on. Four axes are enough in most cases.
Supplier. Which supplier generates most of the variance? A supplier that raised its tariffs without the standard following shows up immediately.
Volume and mix. A value variance can come from the quantity bought rather than the price. Mix matters too: if purchases shift from a supplier at €10.00 to one at €10.60, the drift comes from mix, not from a price increase.
Currency. Isolate the share due to exchange rates. It is the part procurement does not control, and it belongs to a hedging policy.
Nature of the purchase. Rush or off-contract purchases are often made at full price. Spotting them separates the variance caused by purchasing policy from the variance caused by the market.
Fictional example: over one month, unfavorable PPV is €18,000. The breakdown gives:
| Cause | Amount | Owner |
|---|---|---|
| Price increases from two suppliers, standard not revised | €8,000 | Procurement |
| Currency effect on dollar purchases | €7,000 | Treasury |
| Supplier mix shift | €2,000 | Procurement |
| Rush off-contract purchases | €1,000 | Planning |
| Total | €18,000 |
This reading changes the conversation. Instead of “PPV is bad,” you get four actions with four owners, one of which (currency) is not a procurement matter at all.
Revise the Standard Price Once a Year
A standard price is not meant to track the market month after month: its value comes from its stability. The usual rule is an annual revision, before the start of the fiscal year, based on contracts, negotiated tariffs and a budget exchange rate. Each revision triggers a revaluation of existing inventory: the ERP posts the difference between the old and new inventory value to a revaluation variance account. Document the date, scope and reason for each revision, and avoid mid-year revisions except in exceptional cases (major renegotiation, supplier change), because they muddy month-to-month comparison.
A PPV Dashboard for Procurement and Finance
Two audiences, two readings. Finance looks at amount and trend. Procurement looks at causes and suppliers. A useful dashboard contains:
- PPV for the month and year to date, in value and as a percentage of spend, with favorable and unfavorable shown separately.
- PPV by supplier and by category, ranked from most unfavorable to most favorable, with the number of lines affected.
- Breakdown by cause, as in the table above.
- Resolution time for invoices blocked on price variance, to monitor the approval bottleneck.
- Gap between standard and last purchase price, by critical item, to anticipate the next revision.
To round out the supplier view, cross these indicators with the supplier scorecard: a supplier that performs very well on service but is regularly unfavorable on price deserves a renegotiation, not delisting.
Common Mistakes and Close Checklist
- A catch-all variance account. Pitfall: booking everything to one account. Consequence: price, currency and quantity cannot be separated. Countermeasure: one account per type of variance.
- A standard that is never revised. Pitfall: keeping last year’s price. Consequence: a structurally unfavorable PPV that no longer carries information. Countermeasure: a documented annual revision.
- Tolerances widened to stop the blocks. Pitfall: loosening tolerance to calm accounts payable. Consequence: price drift approved without control. Countermeasure: fix the cause of the blocks (order data, contract prices) rather than the tolerance.
- A variance not reconciled to product cost. Pitfall: leaving PPV out of the margin calculation. Consequence: a product margin that is too flattering. Countermeasure: reallocate PPV to products at close, or track it as an adjusted margin indicator.
- Freight and duty confused with PPV. Pitfall: mixing transport and customs with the price variance. Consequence: a distorted analysis. Countermeasure: treat incidental costs separately, see our guide on landed cost for imported purchases.
Monthly close checklist:
- Check that all receipts for the month are invoiced or accrued (GR/IR account).
- Clear invoices blocked on price variance, or accrue them.
- Extract the month’s PPV by supplier, category and currency.
- Break the variance down into causes and assign each cause to an owner.
- Check that PPV on consumed stock has been posted to cost of goods sold under the chosen accounting rule.
- Compare cumulative PPV to the alert threshold and trigger a standard review if needed.
Going Further
Price variance only makes sense in light of the valuation method: reread our guide on inventory valuation with FIFO, weighted average and standard cost and the one on standard vs. actual costing. To build it into your close, rely on the monthly close checklist (French).