What it means
A company agrees to buy parts for $50 per unit but receives invoices at $53 after a catalogue update, and an audit checks the signed contract and any approved amendment before deciding whether the extra $3 is an overcharge. Gather the governing contract, schedules, price lists and amendments, remembering that a draft quote or old rate card may not govern the transaction and that effective dates and legal entities matter.
Collect transaction detail such as purchase orders, receipts, invoice lines, credits and rebate records, which should share identifiers or a reliable mapping, because a total invoice comparison can miss one overpriced line offset by another underpriced one. PRGX describes billing-compliance reviews that compare contract terms with purchase, receipt and invoice line items, including rebates and allowances; its commercial recovery claims are vendor-specific, and the comparison method is the useful general point.
Oracle's pricing-contract documentation shows how agreements can define pricing by conditions and effective dates, so software can support comparison, but a reviewer must validate which term applies to each transaction. Normalise units and currency, since a price per carton of 12 cannot be compared directly with a price per item, and exchange rates, tax and freight should follow stated rules.
Check quantities and eligibility, because a volume rebate may require a threshold or apply only to named products, and an audit should not claim a concession merely because a similar customer received one. An illustrative unit variance is invoice net unit price minus valid contract unit price, so an invoice at $53 against a contract at $50 shows a difference of $3 per unit, and whether it is owed back depends on terms and evidence.
Separate timing differences, because a credit may be issued in a later period and a year-end rebate may not appear on each invoice, so trace subsequent adjustments before calling a mismatch final. Include the seller side when relevant: a business auditing its own customer invoices should also correct under-applied valid discounts and accidental overcharges, not only search for underbilling.
Prioritise by materiality and recurrence, since a small error repeated across thousands of lines may matter more than one unusual transaction, although a single large contract change can also deserve immediate attention. Validate exceptions, because changed specifications, minimum order quantities or approved rush fees may explain a higher price, and do not send a demand based on an automated flag alone.
Preserve evidence and authorisation by recording the contract clause, transaction, calculation, reviewer and any approved correction, and route any disputed term through the contractual process. Review root causes such as a stale price master, wrong item mapping or missing amendment, and fix the system after correcting valid invoices.
Check limitation and notice requirements, since claims may have contractual deadlines or local legal rules and a calculation in a spreadsheet does not establish a right to recover historical amounts. Use samples carefully, because a sample can reveal a pattern but extrapolating to all transactions requires evidence that the same rule applies, so check dates and products and identify the population covered by the audit.
Track outcomes, which may be a credit, a corrected future rate or no adjustment, and measure accuracy and dispute resolution rather than gross recoveries; for an owner, a pricing audit confirms that negotiated economics actually reach the transaction.
In practice
Real-world examples.
Example
A buyer's invoice shows $53 per unit while the valid contract rate is $50. The audit team checks the signed amendment and effective date before deciding whether the $3 difference is an error or an approved increase.
Example
A distributor expects a year-end rebate that is paid after the contract year closes. The reviewer traces the credit note in the following period before calling the invoices overpriced.
Example
A wholesaler discovers that its billing master still holds an expired price list for one customer. After review, it replaces the list, corrects the affected invoices in both directions and records the clause supporting the change.
Formula
Calculation
Illustrative unit price variance = invoice net unit price - valid contract unit price. $53 - $50 = $3 per unit before eligibility review.
Worked example. An invented buyer received 4,000 units in a quarter, all invoiced at $53, while the signed contract price was $50.
- Gross variance = $3 x 4,000 = $12,000 before any review.
- A signed amendment shows the $53 price was approved from the 3,001st unit, so only 3,000 units were invoiced above the valid price; variance = $3 x 3,000 = $9,000.
- A credit note of $2,000 issued in the following period reduces the amount still to be resolved to $9,000 - $2,000 = $7,000.
The figure that matters is the last one, and it is only a candidate for correction until the contract terms, dates and evidence are confirmed.Case study
Seen in the real world.
In this entirely fictional example, Elm Components audits parts invoices and finds a $3-per-unit difference. The buyer and supplier check the latest signed amendment and learn it approved the new price only from the following month. They correct affected invoices and the price master. The case does not assume every difference is fraud or legally recoverable.
Elm's finance team also found that the catalogue update had been loaded without the amendment's start date. It added an effective-date check to its price-change process, and it measured the audit by the share of reviewed lines corrected and disputes resolved, not only by the credits received. Because the root cause was fixed, the next quarter's invoices needed fewer corrections.
Watch out
Common mistakes.
- Using an unsigned quote instead of the effective contract.
- Comparing carton and individual-unit prices without conversion.
- Calling a future rebate missing before its contractual due date.
Questions
People also ask.
What documents are needed?
Effective contracts, amendments, orders, receipts, invoices and adjustments.
Does a price difference prove an overcharge?
No. Check eligibility, dates, units and approved changes.
Can customers be overcharged too?
Yes. A fair audit corrects both directions of billing error.
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%