The solution
Contract price compliance, checked every month instead of every year
Match each invoice line to the contracted price in force on that date, see why the misses missed, and turn the gap into credits you actually collect.
Compliance is a monthly control, not an annual project
A contract compliance audit run once a year finds the money after the trail has gone cold and the people involved have moved on. Running the same comparison every time invoices arrive turns purchase price variance into something you correct while the supplier still has the context to agree with you.
How the matching works
- Price lists are stored as dated versions, so the engine looks up the price in effect on the invoice date rather than the current one.
- SKUs are stemmed and family-matched, so a distributor-specific code still resolves to the contracted item.
- Units of measure are normalized per supplier with an explicit conversion factor — never an inferred one.
- Tiered, percent-off-list, and indexed contracts are evaluated with their own logic instead of a flat unit-price lookup.
- Credits and rebills are paired before anything is classified, so corrections do not double-count.
Every miss comes with a reason
An audit that reports a fifteen percent unmatched rate and stops there has handed you a research project. Each unmatched line here carries its reason — unknown SKU, no price in effect that day, unit mismatch, substitution, non-product line — so you can fix the data problems in cost order and dispute only what is genuinely wrong.
Purchase price variance you can act on
- Variance broken out by supplier, product family, project, and period.
- Undercharges classified as standing, quoted, or isolated, because a standing discount means your contracted price is above market.
- Supplier scorecards built from variance history, ready for a renewal conversation.
- A claim lifecycle — open, disputed, credited, written off — so found money is tracked until it lands.
Common questions
- What is purchase price variance in this context?
- The difference between what a supplier billed for a line and what your contract said that line should cost on the date it was invoiced, after unit-of-measure normalization.
- Do we need our price lists in a particular format?
- No. Price lists and invoices are imported from the exports your suppliers already send, and the column mapping is saved per supplier so the next file loads without setup.
- Which contract structures are supported?
- Flat contracted prices, quantity tiers, percent off a published list, and index-linked prices are each evaluated with their own logic.
- How is this different from an external recovery audit firm?
- A recovery audit is retrospective and paid as a share of what it finds. This runs continuously on your own data, so most errors are caught in the month they occur and the contract is corrected rather than mined.
See your own numbers
Audit your first 500 invoice lines free. No card, no sales call.