A three-year framework agreement with a component supplier provides for an annual price review based on a raw materials index. The anniversary date passes in January, nobody notices, and last year’s price list keeps applying. Eighteen months later the supplier spots the omission and claims a catch-up payment. Your buyer replies that the clause never kicked in, and that you paid without objection for a year and a half. The dispute begins.
The mirror image is just as common on the sales side: a software maintenance contract indexed to a services price index, never revised by sales administration, whose margin erodes year after year while payroll costs follow their own trajectory. In both cases the clause existed. What was missing was a configuration that turns it into a planned, calculated and controlled event inside the ERP.
This article walks through the mechanics of a price revision formula, how to model it in the ERP, the hard cases (retroactivity, amendments, currencies), the accounting impacts and the governance you need around it.
The Hidden Cost of a Forgotten Indexation
A missed indexation leaves no visible trace. There is no rejected invoice and no system alert: the price simply stays where it was at the last signature. The effect is cumulative and hits on three levels.
Eroded margin. On a multi-year contract, every period left unrevised widens the gap between the invoiced price and the real cost. For the seller, that is a direct margin loss. For the buyer, the omission is paradoxically favourable in the short term, but it builds a latent liability: the supplier can claim the revision for as long as the limitation period has not expired.
Contested catch-ups. Claiming several revision periods at once is the classic source of disputes. The other party argues implied waiver, good faith, or the absence of notice within the contractual deadline. Depending on how the clause is drafted, the argument can succeed. Only a dated history, with calculation and notification, lets the company defend its position.
Distorted performance management. Finance and controlling work with standard prices or budgets that assume revisions are applied. When they are not, price variances appear without explanation and profitability analyses by customer or by contract are biased. We cover this link in our guide to analytical accounting and budget management in the ERP.
Anatomy of a Price Revision Formula
Before configuring anything, you need to understand what the ERP will have to calculate. A classic revision formula looks like this:
P = P0 × (a + b × I / I0)
where P is the revised price, P0 the initial price, I the index at the revision date, I0 the index at the reference date, a the fixed share and b the variable share (a + b = 1).
Fixed Share and Variable Share
The fixed share (a) is the portion of the price that does not move with the index: overheads, margin, non-indexable items. The variable share (b) is the portion that follows the index. An IT services contract might index 85% to 100% of the price to a wage index, while a raw material purchase contract would index a smaller share if processing weighs heavily in the price.
A formula can also have several terms: one part indexed to a wage index, another to a materials index, a last one to energy. The ERP therefore has to handle formulas with N components, not just a flat percentage uplift.
Reference Indices
The choice of index determines how relevant the clause is. The most common families are:
- services and labour cost indices: wage and employment cost indices published by national statistical offices or professional federations (the Syntec index in France, the ONS Index of Labour Costs per Hour Worked in the UK, Destatis wage indices in Germany) are used to revise IT services, engineering or software maintenance contracts;
- producer price indices (PPI), published by national statistical offices by industry, suited to purchases of industrial goods; for cross-border contracts, Eurostat publishes harmonised EU series;
- raw material, energy or freight indices, depending on the cost structure;
- consumer price indices (CPI, HICP in the EU, RPI or CPIH in the UK), sometimes used for leases and standard service contracts.
One point of caution: an index can be rebased, revised or discontinued. The configuration must provide a linking coefficient between the old and the new series, otherwise the formula produces a wrong result as soon as the switch happens. French contracts relying on the Syntec index, for instance, have to deal with a revised series introduced in September 2022 (Syntec explanatory note, in French).
Reference Date
I0 is the index at the reference date, which may be the date of the tender, signature, start of performance or a fixed month. The choice is contractual, and the most frequent mistake is to use the index of the invoicing month instead of the contractual month. Another subtlety: indices are published with a lag. The index for month M is only known in M+1 or M+2. The clause then provides for a provisional index, with a later true-up. The ERP must handle both states (provisional, then final).
Caps, Floors and Trigger Thresholds
Many clauses limit the variation: an annual cap (the increase cannot exceed a given percentage), a floor (no decrease below the initial price) or a trigger threshold (the revision applies only if the index moves beyond a given gap). These limits apply either to the index or to the resulting price. This must be explicit in the configuration, because the two readings give different results.
Worked example (illustrative). Initial price P0 = €100 per unit, a = 0.15, b = 0.85, I0 = 120. At the revision date, I = 126. The ratio I / I0 is 1.05. P = 100 × (0.15 + 0.85 × 1.05) = 100 × 1.0425 = €104.25. With an annual cap on increases of 4%, the price would be limited to €104.00. These figures are fictitious and only illustrate the mechanism.
Modelling It in the ERP
Framework Contracts and Price Lines
The first principle is not to index prices keyed on orders, but to attach the formula to the framework contract (purchasing framework agreement, sales contract or service contract) and its price lines. Each line carries: the base price, the applicable formula, the reference date, the limits, the review frequency and the next review date. Orders and invoices inherit the price in force on their date. Market ERPs offer objects of this kind (purchase and sales contracts, price agreements, conditions) with varying levels of formula support: some allow configurable pricing formulas, others require custom development or an add-on module.
Index Tables and Updates
Indices live in a dedicated table, with: index code, period, value, status (provisional or final), source and publication date. Three rules apply:
- a single, identified and documented source per index (national statistics office, industry federation, Eurostat for European indices);
- updates by an authorised role, with a four-eyes check, because a wrong value spreads to every contract that uses the index;
- an automated interface when the source allows it, but never without a plausibility check (abnormal variation, missing value).
Treat this table as master data, like exchange rates: it needs an owner, a process and a history.
Periodic Triggering
A scheduled job runs daily or monthly through the contracts whose revision date has fallen due, calculates the new price, and generates a revision proposal rather than changing the price directly. The proposal shows the old price, the index used, the new price, the estimated annual impact and the notification document. After approval, the new price takes effect on its effective date. This mechanism prevents silent changes and gives internal control a mandatory checkpoint.
History and Audit Trail
Every price must remain versioned with its validity date. For any past invoice you should be able to answer: which price applied, under which formula, with which indices, approved by whom, notified when. That is the condition for defending a catch-up claim or answering an auditor. For the general framework on traceability, see our article on ERP audit trails and legal retention requirements (in French).
| Criterion | Manual handling (spreadsheets, reminders) | Automated handling in the ERP |
|---|---|---|
| Detecting due dates | Depends on memory and individual calendars | Scheduled job, alerts on anniversary dates |
| Calculation | Copied formula, risk of cell or index errors | Configured formula, index taken from a controlled table |
| Notification | Letter drafted case by case | Document generated from the revision proposal |
| Traceability | Scattered files, multiple versions | Versioned prices, approval trail |
| Financial visibility | Impact known after the fact | Impact estimated before approval |
| Dispute risk | High (omissions, weak evidence) | Reduced (enforceable history) |
Purchasing vs. Sales: Symmetry and Asymmetries
On paper, price revision is symmetric: the same formula moves up or down. In practice, three asymmetries come into play.
Negotiating power. A mid-sized company facing a large buyer rarely has the leverage to impose upward indexation, while it suffers it from its own suppliers. The result is a structural gap between purchasing clauses (often indexed) and sales clauses (sometimes frozen). The ERP lets you measure this asymmetry contract by contract, and gives the CFO a quantified argument for renegotiation.
Notification deadlines. Many clauses require the revision to be notified within a set period before it takes effect, on pain of losing the right for that period. On the sales side, the configuration must therefore trigger the alert well before the effective date. On the purchasing side, you need to check that the supplier’s notice is compliant before accepting the new price.
Automation. On the purchasing side, an invoice carrying a revised price must be compared with the price the ERP expects: this is a tolerance check to add to the three-way match between invoice, purchase order and goods receipt. On the sales side, the ERP applies the revision but the salesperson must be able to justify the increase to the customer.
Handling the Hard Cases
Retroactivity. A late-published index or a late notice raises the question of retroactive application. If the contract allows it, the ERP must calculate a catch-up amount per period, with a separate adjustment document (supplementary invoice or credit note), rather than rewriting past invoices. If the contract does not allow it, the revision applies from the notification date, and the configuration must refuse any earlier effective date without explicit approval.
Amendments. An amendment can change the formula, the limits or the index. It creates a new version of the contract, with its own effective date, without overwriting the history. The trap is to edit the existing price line: you lose the ability to recalculate earlier periods.
Open orders. The contractual rule determines which price applies to an order placed before the revision but delivered after it: price at order date, delivery date or invoice date. This choice must be a contract parameter, not a team habit. Open orders affected should be identified when the revision is approved.
Currencies. When the contract is denominated in a foreign currency, two mechanisms overlap: price indexation and conversion. You must decide whether the index applies to the price in the foreign currency (then converted at the spot rate) or to the converted price. A national index (a US one, for example) applied to a contract between two European entities is a case to handle by exception, with legal sign-off.
Accounting Impacts
Accruals and accrued income. A revision that has not yet been notified but is due creates accrued income on the seller’s side and an accrued expense on the buyer’s side. When the final index is not yet published, an estimate based on the provisional index feeds these closing entries, with a reversal on true-up. The ERP must produce, at each close, the list of due but uninvoiced revisions.
IFRS 15 for long-term contracts. An index-based escalation is generally analysed as variable consideration: the seller estimates the amount it will be entitled to and includes it in the transaction price to the extent that a significant reversal of cumulative revenue is highly improbable (IFRS 15, IASB). The same recognition principles are covered for recurring contracts in our article on subscription management and recurring billing, and for rebates in conditional rebate management. The exact treatment depends on the nature of the contract and should be agreed with your auditors.
Management control. The price revision must feed analytical accounting: purchase price variance, margin trend by contract, updates to standard prices. Without this link, indexation remains an administrative topic instead of becoming a performance lever.
Governance: Who Approves, Which Controls Before Invoicing
A clear split of roles avoids blind spots:
- the lawyer or contract manager enters and approves the formula, because it is the translation of the clause;
- management control owns the index table and checks updates;
- purchasing or sales administration approve the revision proposal, on the supplier or customer side;
- accounting checks the impact on accruals and closing entries;
- the finance department receives a dashboard: contracts due within 90 days, late revisions, cumulative gap between contractual price and applied price.
Three blocking controls should be in place before invoicing: the customer invoice price is that of the last approved version; a supplier invoice whose price departs from the expected revised price is put on hold; any revision above an impact threshold requires dual approval. Finally, alerts aligned with notification deadlines (for example two to three months before the due date, depending on the clause) make sure the right to revise is not lost.
A Five-Step Implementation Plan
- Inventory the contracts. List the multi-year customer and supplier contracts that include a revision clause, and extract formula, index, reference date, limits and notice period. Start with the contracts with the highest financial stakes.
- Standardise the formulas. Group the clauses into a limited number of templates (single index, multi-component formula, with or without limits) and decide what the ERP handles out of the box and what needs advanced configuration.
- Build the index table. Appoint the owner, the source, the update procedure and the handling of provisional indices and base changes.
- Configure and test. Set up the framework contracts, the periodic job and the revision proposals. Replay the last two years of revisions on a set of real contracts and compare with the historical calculation: the gaps reveal past omissions and configuration errors.
- Govern and measure. Put in place the approvals, the alerts, the dashboard and a quarterly review with management control. Track the number of revisions applied on time and the cumulative gap recovered.
Going Further
If your multi-year contracts still rely on spreadsheets and calendar reminders, an audit of your revision clauses is a good starting point: it typically quantifies the gap between contractual price and applied price, and it scopes the configuration work. Contact our advisory team to run this diagnostic on a sample of your contracts.
