Procurement Contract Price Variance

A supplier invoice uses a different unit price from the amount agreed in the applicable contract, and procurement contract price variance measures the difference for qualifying purchases to help identify an unauthorised price change, a missing amendment or a data mismatch. It is not automatically evidence that the supplier overcharged.

Identify the reference as the effective signed contract, price schedule or approved amendment for the item and purchase date, because a stale price list is not a reliable baseline. A purchase order may validly incorporate a negotiated price or later amendment, so establish the document hierarchy before declaring a variance.

Use comparable units and specifications, since a price per case, per kilogram and per piece cannot be compared without conversion and packaging context, and similar product codes can carry different grades, sizes or service levels. Specify price components too, because freight, discounts, rebates, taxes and duties may be included or excluded under the contract.

Determine the effective date, since a contract price may change by order date, shipment date or service period, and check quantity tiers because a volume discount may depend on ordered, delivered or cumulative quantity and the lowest tier should not be assumed for every invoice. Separate currency effects, as a different exchange rate can change the functional-currency expense without changing the supplier's contracted currency price, and Oracle describes exchange-rate variance separately from invoice price variance in its payables guidance.

Price variance is multiplied by the qualifying invoiced quantity, while a quantity shortfall is a distinct issue. Record a sign convention, because a positive amount can mean an unfavourable higher invoice price under one convention, and state it so managers do not reverse the conclusion.

Distinguish timing, since an invoice received before a retroactive amendment is entered may appear wrong until the authorised record is updated, and check credits because a supplier may issue a later price credit, so report the initial variance and the resolved amount rather than deleting the exception. Avoid automatic payment of a mismatched invoice, which may require contract review and approval, and document tolerance rules so tiny rounding differences are not reported as material exceptions.

Keep item-level detail, as a total invoice may equal the expected total despite one overpriced line and another underpriced line. Review procurement behaviour, because a high variance rate may reflect buyers selecting an incorrect contract or failing to record amendments, and classify causes such as wrong catalogue price, missed discount, wrong product, contract version or invoice error since each needs a different fix.

Treat estimates carefully, as a purchase order created with a provisional price should not be the final contract baseline without approved terms, and consider price index clauses, which need the correct observation date and formula before variance is computed. Separate contract and standard cost, since manufacturing standard cost may differ intentionally from the negotiated purchase price and this measure compares commercial terms, not a factory costing standard.

Use a consistent cohort of posted invoices, received lines or purchase orders under one declared unit, and check accounting treatment because the operational variance may not equal the journal-entry variance under the entity's system and reporting framework. Preserve an audit trail with price source, units, invoice and correction, track supplier concentration where repeated variance in one category may justify a pricing discussion, and resolve the cause before escalation, because a variance is a signal to investigate the commercial record, not a presumption of bad faith.