Purchase Order Variance Analysis

A buyer orders 100 units at $20 each, receives 95 and gets an invoice for 100 at $22, which raises separate quantity and price questions, and paying, rejecting or changing the purchase order without checking evidence can create another problem. Start with the version of the approved purchase order in force when the goods were supplied, since amendments, split shipments and cancellations can make the original document an outdated baseline.

Compare three records, order, receipt and invoice, because a three-way match links what was approved, what arrived and what is being charged, subject to the company's control policy. Oracle's payables documentation describes invoice price, quantity and exchange-rate variances in a purchase-order-matched process, and although its accounting mechanics are system-specific, the categories help separate causes.

Record a price difference using a clear baseline: at a PO price of $20 and an invoice price of $22 for 100 billed units, the illustrative price variance is $200 unfavourable before other charges or tax. Investigate quantity separately, since goods received may be short, damaged, in transit or documented under another receipt, and a billed quantity mismatch is not proof of fraud.

QuickBooks' explanation of three-way matching connects an order, receiving record and supplier invoice, and because the records may be created at different times, an apparent mismatch may be temporary. Set a tolerance policy in which tiny rounding differences may be handled automatically while large or repeated gaps need investigation, reflecting risk and control requirements rather than convenience alone.

Check units of measure, since a case of 12 compared with individual units can create a dramatic false variance, so convert before computing any rate. Review contract terms, since freight, rebates, volume tiers and currency clauses may explain a price change, and a valid charge still needs proper authorisation and recording.

Separate exchange-rate effects, because a foreign-currency invoice can have the same contractual unit price but a different amount in reporting currency, and price and FX should not be blended without disclosure. Track partial receipts, so that if only half an order arrived the invoice is compared with the appropriate received portion and open balance, not automatically with the entire original order, and keep tax and ancillary charges distinct, since shipping or tax differences need a different response from a unit price breach.

Prioritise recurring patterns, since one unusual invoice may be a clerical mistake while repeated overcharges from a supplier or item may reveal a contract setup or master-data problem. Record resolution through a credit note, corrected invoice, authorised PO change or confirmed receipt, with a traceable explanation, because a dashboard that never reflects closure accumulates stale noise.

Protect payment timing by holding only the disputed portion where process and contract allow, since an unjustified full hold can strain a supplier relationship or lose a discount. Look for internal causes as well, because an incorrect item price in the PO, late approval or misrecorded receipt can originate inside the buyer's workflow, and the objective is accuracy, not blame.

Use trend reports with context, since variance amount, number of exceptions, supplier and item category help spot concentration and a higher count can also reflect stronger controls catching small differences, and review the accounting outcome, because a variance can affect inventory cost, expense or payable balances under the company's system and policy. For an owner, purchase order variance analysis links buying promises to delivery and payment, and it is useful when each difference has a cause, an owner and a documented closeout.