Signing a supplier contract does not guarantee that every subsequent purchase order and invoice follows its terms. Price lists may change, amendments may take effect on different dates, quantity tiers may apply, and units or freight terms may be interpreted differently across systems.
Contract-price compliance is therefore a cross-system investigation: compare the relevant contract terms with transaction evidence, then determine whether a difference is valid, explainable or requires review.
Why contract checks fail after signature
The contract may live in a document repository, purchase orders in an ERP, invoices in accounts payable, and amendments in email or a contract-management system. Even where every source is available, the relevant terms may not have the same structure or identifier.
| Contract term | Transaction evidence | Potential issue |
|---|---|---|
| Unit price | PO and invoice line price | Different unit of measure |
| Effective date | Order and invoice dates | Wrong price version applied |
| Volume tier | Cumulative eligible quantity | Threshold calculated on the wrong basis |
| Freight responsibility | Invoice and logistics charges | Freight counted twice or omitted |
| Rebate | Purchase history and credit note | Eligibility or timing unresolved |
| Currency | Contract currency and invoice currency | Exchange-rate basis differs |
A useful control starts with a small set of high-value terms and explicitly documents how each term is interpreted.
From clause to reviewed exception
- Start Identify the contract and applicable version
- Extract or encode the relevant term
- Determine effective dates, units and eligibility
- Match PO and invoice lines
- Calculate the candidate variance
- Valid exception under policy?
- No Document the accepted explanation.
- Yes Route the evidence for procurement or finance review.
- Approve a correction or close with a reason
- Outcome Retain the decision trail
A valid amendment, rebate, freight adjustment or tier may explain a difference. An unstructured clause is a limitation, not an invitation to invent an interpretation.
The system should not assume that a difference is invalid merely because the numeric price differs. A valid amendment, rebate, freight adjustment or tier may explain it. Equally, the absence of a structured clause should be treated as a limitation, not filled with an invented interpretation.
Prioritise by materiality and confidence
A useful review queue considers at least:
- estimated value of the candidate variance;
- confidence that the correct contract and transaction were matched;
- whether the clause is machine-readable and unambiguous;
- whether the price difference is already explained by an amendment;
- recurrence across multiple transactions;
- time remaining for a claim, credit or dispute;
- accountable owner and required approval.
This makes the process operational rather than a list of unexplained alerts.
Where Qwry.AI fits
Qwry.AI’s procurement use cases provide a relevant starting point for exploring relationships between supplier records, purchasing data and contractual context. The feasibility of any contract-compliance workflow depends on the available documents, structured terms, source connectors and validation rules.
A sensible proof of value should start with one contract category, a known set of transactions and a human-validated baseline.
Next step: Select a contract type with repeat purchasing. Identify the terms that can be expressed as testable rules, map the related transaction sources and review a sample of candidate variances with procurement and finance.
FAQ
Frequently asked questions.
It is the process of checking whether transactions apply the relevant agreed commercial prices and terms, using the correct contract version, dates, quantities and conditions.
No. It may be explained by an amendment, tier, currency rule, unit conversion, freight term or legitimate exception. The evidence must be checked before classifying leakage.
Document extraction can assist, but extracted clauses should be validated, especially where terms are ambiguous, conditional or legally significant.
Prioritise material candidate variances with strong contract and transaction matches, recurring patterns and a clear route to resolution. Keep ambiguous matches visible for review.