A component came in at a higher purchase order price than the amount in the standard cost file. Purchase price variance (PPV) measures that price gap on the quantity received. For a receipt-based standard cost report, subtract the standard unit cost from the purchase order unit price and multiply by the received quantity. With this sign convention, a positive amount is unfavorable because the agreed price exceeded the standard.
An invoice can bring a second price change after the receipt. To explain both amounts at close, keep the standard, purchase order, receipt, and invoice together at line level (including partial receipts and later credits). The same purchase order can contribute to different months as each delivery arrives.
Calculate the variance for each receipt
Oracle documents the receipt-based method in its Purchase Price Variance Report. Start with the receipt transaction, then find its purchase order line and the standard cost used in the receipt accounting. Retain the receipt date, transaction type, and the item and costing organization that identify the standard. Treat a return or correction according to the signed quantity and accounting treatment in your system so the reversal lands against the right receipt.
Convert the purchase price and the standard to the same currency and unit before multiplying. A purchase order for ten cases of 50 brackets at $525 per case translates to $10.50 per bracket. Comparing the case price with a $10.00 standard per bracket would manufacture a difference of $515 before any receipt quantity was counted. For foreign-currency purchases, retain the rate and rate date used for the report so a movement in exchange rates can be investigated on its own.
Use the standard recorded for the receipt or recover its effective version from the cost records. An updated standard can make an old receipt look favorable on today’s export even when the posted amount was unfavorable. Keep a variance against a negotiated contract price as a separate column if procurement also needs a view of contract compliance.
Bridge a partial delivery to its invoice
Assume a supplier agreed to sell 800 brackets at $10.50 each and delivered 500 this month. The approved standard is $10.00 per bracket and the invoice for those 500 shows $10.70 each. All figures in this hypothetical example use US dollars and exclude freight and tax. The example records the receipt and invoice price differences separately.
| Measure | Calculation | Amount |
|---|---|---|
| Purchase price variance at receipt | 500 × ($10.50 − $10.00) | $250 unfavorable |
| Invoice price variance on matched units | 500 × ($10.70 − $10.50) | $100 unfavorable |
| Invoice price above standard on matched units | 500 × ($10.70 − $10.00) | $350 unfavorable |
The $250 receipt variance belongs to the 500 received brackets. The remaining 300 stay outside that receipt calculation until a later delivery posts. If the invoice covered just 200 of the received brackets, its price difference would be $40. The other 300 received units would still contribute to the receipt variance and remain unmatched on the invoice side.
Oracle’s standard cost variance documentation describes separate purchase price and invoice price variance events. Oracle Fusion’s receipt costing documentation describes a method that can update acquisition cost when the invoice arrives. Check the posting model and included cost elements before adding receipt and invoice report totals. If one report already reflects the adjustment, summing it with the same invoice price difference counts the change twice.
Assign price exceptions using line evidence
Start with the largest absolute receipt differences, then group related lines by item, supplier, and plant. Keep favorable and unfavorable amounts visible in the detail. The net can hide a recurring premium at one supplier if an unrelated standard change produced a favorable result elsewhere. A buyer can validate the effective date of a supplier price agreement against the purchase order. The cost accountant can check whether the item standard was current for that receipt.
Work through pricing and matching in order. Pull the agreed purchase order revision, the received quantity, and any invoice correction for the same line. If a supplier billed at the correct price per case but AP entered that price per bracket, the invoice exception starts with a unit mismatch. Three-way matching covers the separate approval checks across those records.
Reconcile the receipt report with the posted variance accounts for the same period and organization. Match on the receipt transaction identifier where the ledger carries it, or use the accounting distribution that links them. A buyer may review the full delivery while finance has only the portion posted before close. Keep unmatched items with their posting status instead of forcing the operational and ledger totals to agree by moving transaction dates.
A purchase order revision can also replace the price on the current order after a receipt was valued. Preserve the line revision or recorded transaction price used in the posting. A later change can then be checked against its adjustment record without rewriting the original comparison.
Treat a supplier premium and a change in material consumption as separate investigations. A bracket’s price can rise even when production uses the approved quantity. The material usage variance calculation compares the quantity consumed with the quantity allowed for actual output.
Use the total manufacturing cost formula if you also need to place the materials amounts alongside labor and overhead. Keep this receipt bridge at the transaction level so the same price difference can be traced when it appears in a broader cost review.
Inspect receipt detail in one source
Connect a supported ERP source and identify which permitted transaction fields can be reused in a receipt-level report.
Where Permute fits in purchase cost review
Permute is the context layer we sell between business records and the AI tools people use. We can connect supported data sources and use the line identifiers you provide to relate purchase orders, receipts, invoice lines, and approved cost records.
We can apply your declared currency, unit conversion, and reporting rules in a repeatable calculation. Keep receipt price changes and invoice adjustments separate in the output, with an exception when a required cost or match is missing.
A cost accountant can ask which receipts drove an unfavorable result and trace the answer to the line records and cost version they’re permitted to see.
Leave postings and cost policy with finance
We read from connected systems and do not write back to the system of record. Finance approves the standard, decides which costs belong in its variance report, and posts any adjustment in the accounting system.
Reconcile the price change at each event
Purchase price variance starts with a price difference on a specific receipt. In the bracket example, receiving 500 units produced a $250 unfavorable receipt variance and the matched invoice added $100. Match quantities, dates, and units at line level so the two events can be checked independently. Assign the exception once the evidence shows which price or standard changed.
Review a purchase cost exception with Permute
Bring an item standard and a matched purchase order, receipt, and invoice so you can review the fields your cost report depends on.
Questions about purchase price variance at close
Does an open purchase order create a receipt variance?
Under the receipt-based method here, an open purchase order can show expected exposure at the agreed price. The receipt calculation uses the quantity that has been received.
What if the standard cost is missing?
Flag the affected receipt and have the cost owner verify the applicable version. A missing standard and a standard set to zero have different meanings and produce different interpretations.