What it means
A buyer agrees a unit price of $90 for a component but one purchase order uses $100, and price compliance asks whether the order line uses the rate that applies under the supplier agreement, quantity, dates and location. Oracle documentation shows that purchase order pricing can depend on blanket agreement price breaks and the pricing date, and its invoice price variance report compares purchase and invoice values, which is a related but different check.
Identify the source of truth, since an executed agreement, approved quote or catalogue may control, and do not compare every PO with an outdated spreadsheet. Check legal entity and supplier site, because the same supplier group may offer different rates to different buying entities or delivery locations, and confirm item and specification, since similar part numbers can differ in packaging, grade or unit of measure and a false comparison creates unnecessary exceptions.
Choose the pricing date, as some agreements use order date and others use requested delivery date, which can affect the selected price break, and review quantity tiers, checking cumulative versus order-specific volume rules because a larger order may qualify for a lower unit price. Check currency too, since a price quoted in one currency cannot be compared directly with another without an approved exchange method.
Account for freight, because some rates include delivery while others are ex-works, so keep unit-price compliance separate from landed-cost review, and capture approved deviations, since an emergency order may use an exception price with authorisation that should be reported rather than treated as ordinary compliance. Define the numerator by counting compliant eligible PO lines or compliant value, because a single large error and ten tiny errors look different under each measure, and avoid counting drafts, since orders not yet released can be fixed before commitment and pre-release prevention should be tracked separately from post-release error.
Preserve revisions, as a change order may update quantity, date or price, so keep the prior values and approval history. Check discount fields, because a nominal list price with a separate discount can equal the agreed net rate, so compare effective price using the right fields, and distinguish rebates, since a future volume rebate may not be embedded in the PO unit price and should be tracked separately until earned.
Match the invoice later, because a correct PO does not guarantee the supplier bills correctly and invoice price variance is a second control. Review effective periods as well: a new rate may start next month while an older PO retains prior terms, so do not rewrite history to match the latest contract.
Look at automated defaults, since a wrong catalogue mapping can generate many noncompliant orders and the rule should be fixed rather than correcting every PO manually, and track unresolved exceptions, because an order with a material price gap may need buyer or finance action before supplier acceptance. Contact the supplier where needed, since a disputed quote or missing amendment requires evidence and a contractual breach should not be asserted from system fields alone.
Reconcile taxes, as unit prices may be tax-inclusive or exclusive, and compare on a like-for-like basis under the agreement, then segment results so that contracted and spot-buy orders, which have different references, are separated and noncontract purchases excluded only under a stated policy. Review trends, since repeated variance for one item may mean the master price was not updated while a one-off exception may be a data entry error, and protect savings claims, because a negotiated lower rate only becomes useful when orders and invoices use it, so link price compliance to verified savings.
Include a cutoff control: a rate amended during an open order should trigger review of whether existing lines are grandfathered or repriced, and committed terms should not change silently. For owners, purchase order price compliance tests whether buyers actually order at approved rates, and its strength is the precise agreement and line-level evidence.
In practice
Real-world examples.
Example
A PO for steel brackets uses $100 per unit despite an applicable agreed rate of $90. The buyer had picked an old catalogue line. Procurement corrects the order before the supplier ships.
Example
A valid quantity tier explains a lower unit rate on a large order of office paper. The buyer's order passes 5,000 units, which triggers the lower price in the agreement. The check marks the line as compliant.
Example
An emergency exception for urgent laboratory supplies is approved by the category manager and reported separately. The higher price is recorded with the approval and reason. It does not distort the ordinary compliance rate.
Formula
Calculation
Illustrative compliant-line rate = compliant eligible PO lines / all eligible PO lines x 100. Ninety-five of one hundred lines = 95% under stated rules.
Worked example. A fictional buyer releases 100 eligible lines worth $200,000 in total, and 5 lines worth $30,000 use a price that does not match the agreement.
- Line compliance = 95 / 100 x 100 = 95%.
- Value compliance = ($200,000 - $30,000) / $200,000 x 100 = $170,000 / $200,000 x 100 = 85%.
- The value view looks worse because the errors sit on large lines. One of those lines is 500 units ordered at $100 against an agreed $90, so the overpayment is 500 x ($100 - $90) = $5,000.Case study
Seen in the real world.
This entirely fictional case follows Cedar Motors. Buyers thought a supplier had raised prices, but purchase orders were pulling an old catalogue rate. Procurement updated the mapping and checked later invoices against the corrected orders. The case does not establish a real contractual rate.
In the invented story, the old catalogue rate was $4 a unit above the agreed price on a part ordered at 1,000 units a month. The mapping error therefore added 1,000 x $4 = $4,000 to each monthly order. After the fix, procurement reran the compliance report and found the lines at 100%, and finance confirmed that the next invoices matched the corrected orders.
Watch out
Common mistakes.
- Comparing different units of measure or currencies.
- Using the latest agreement price for orders governed by an older rate.
- Treating PO compliance as proof the invoice is correct.
Questions
People also ask.
What is the benchmark?
The applicable approved rate and conditions for each eligible line.
Can an exception be compliant?
It can be authorized under a defined exception process and reported separately.
Why check invoices too?
A supplier can bill a different rate despite a correct PO.
From the founder's library

Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%