Across industries
Prices, indexation and rebates: contract calculations you can verify
Amounts linked to their clauses and source data.
Industry guide · 6 min
An application to explore with your team. Features, required data and connections will be confirmed for your context. Numerical examples are fictional.
01
Part of the calculation is already in the contract
An invoice may look correct while using the wrong index, an old rate or a rebate on the wrong base. The rule may already exist in an appendix or amendment that has never been connected to the invoice line. Repeating these checks manually becomes difficult as the contract portfolio grows.
The application to explore with Kelqio connects contract wording to the data needed to apply it. Every amount should be explainable through a clause, a formula and dated inputs. This covers prices, revisions, rebates and outcome-based fees. Calculations can support both budgeting and invoice checks, provided forecasts remain separate from amounts actually due.
02
AI prepares the rule; an engine performs the arithmetic
The process starts with the contract and its attachments. AI identifies passages defining prices, indices, percentages, periods, thresholds or caps. Each extraction retains the source document, version and passage. A suggested formula without supporting evidence is insufficient for a commercial commitment.
The prepared rule must be readable by its owner: which variables enter the calculation, on which date, for which transactions and with what exclusions? Ambiguous wording, missing attachments or contradictory clauses require clarification. The system should not silently select the interpretation producing the most favourable amount.
After approval, a deterministic engine executes the rule. It handles monetary decimals, operation order and agreed rounding. Identical inputs and rule versions must produce identical results. AI may explain the result in ordinary language; it does not replace reproducible arithmetic.
Contract calculations
Follow the clause through a validated formula to the calculated amount and supporting evidence.
What if you changed an assumption?
Try it01 · Reference
Base price
1,000 €
02 · Your assumption
New index
105
03 · Result
Revised price
€1,000 × new index / 100
Educational simulation, fictional data. The formula must match the approved clause.
What the monitoring could look like
A €1,000 base price and an index moving from 100 to 105 give €1,050 after formula approval: 1,000 × 105 / 100.
Metric to adapt to your industry: Amounts linked to their clauses and source data.
AI-generated illustration of a proposed interface. Rules, data and approvals need to be defined with your team.
03
Prices, indexation and forecasts
A revision may follow one index or a weighted combination. Identify the baseline value, applicable period, publication lag and fixed share. The latest available value is not necessarily the one specified by the contract. Caps and floors may further change the result.
Fictional example: a €100,000 contract keeps a 20% fixed share and indexes 80% against an index rising from 100 to 105. The calculation is 100,000 × (0.20 + 0.80 × 105/100) = €104,000. A €106,000 invoice creates a €2,000 discrepancy to review alongside other applicable clauses, services and amendments.
For raw materials, the same rule can support a budget: simulated period prices multiplied by volumes to purchase. Separate market scenarios, committed prices and uncertain volumes. A calculated budget is neither proof of a future market price nor authorization to place an order.
04
Tiers and rebates: define the eligible base
A 3% rebate above a threshold can mean different things. It may apply to the entire eligible spend after crossing the threshold or only to the incremental band. Confusing these rules produces an incorrect amount even when the percentage and volume were extracted accurately.
Fictional example: €240,000 of eligible annual purchases with a €200,000 threshold. If 3% applies to the whole base after the threshold is reached, the rebate is €7,200. If it applies only to the €40,000 above the threshold, it is €1,200. The €6,000 difference arises from interpretation, not arithmetic.
Identify eligible entities, suppliers, products, periods, returns and credits. Calculated rebates remain separate from confirmed rebates and amounts received or applied. A rebate already included in net pricing must not be counted again as additional savings.
05
Success fees: connect the mandate to approved savings
A buying group or procurement consultant may charge a share of savings. Record the agreed baseline, measurement period, deductible costs, thresholds, exclusions and benefit approvers. A percentage formula cannot fix an incorrectly defined base.
Fictional example: a customer approves €80,000 of net realized savings. The mandate specifies a 12% fee capped at €15,000. The calculated fee is €9,600. This rate is illustrative. Benefits depending on volumes not yet purchased should not automatically enter a realized-savings base.
Kelqio can provide calculation rules and evidence to consultants while they retain their own commercial terms. Software pricing and consultancy compensation remain distinct. Each case should trace the fee back to the transactions and clauses supporting it.
06
From expected amounts to action
A useful result shows expected amounts, observed amounts and discrepancies with their data sources. Users may request checks, confirm interpretations, prepare credit requests or approve fee calculations. Detecting a discrepancy does not itself trigger payment or a claim.
The engine can also handle explicitly agreed fixed charges, prorating, minimums, service credits and conversion rules. Required facts must be approved: actual service periods, accepted delivery, established incidents or received quantities. Tax calculations use applicable supplied parameters; the engine must not invent tax treatment from incomplete documents.
07
Amendments, missing inputs and audit history
An amendment introduces a rule version and effective date. Past calculations retain the version originally used. A newly published index should not silently overwrite history: distinguish values available at calculation time from subsequent adjustments.
Documents remain data sources. Instructions inside them must not authorize tools to transmit information or change their operating rules. Access controls, organization separation and approval responsibilities need to be agreed before production use.
08
Start with representative contracts
A first pilot can cover a fixed-price contract, simple indexation and a volume rebate. Independently prepared expected calculations help verify extraction, rules and outputs. Then introduce edge cases: missing values, unit changes, exact thresholds, caps and mid-period amendments.
Evaluate rule preparation quality, required corrections and the ability to justify results. Once this chain is dependable within the chosen scope, automation can expand. Confirm available functions, connections and responsibilities with the Kelqio team for your organization.
Questions to consider
Does AI decide the amount on its own?
It prepares a sourced interpretation. Rules are approved and then executed by a reproducible engine. Ambiguous cases require clarification.
Can we start with a PDF?
A PDF can support initial scoping. Relevant attachments and calculation inputs are also needed. Document quality determines the reading work required.
Further reading
These sources describe comparable mechanisms. They are not Kelqio customer references or performance results.
Contract intelligence
Your purchasing has its own requirements. Let’s talk.
Tell us about your contracts, flows or operational constraints. Together we can define a useful starting scope.