The Escalator in the Small Print: A 45-Day Review of Index-Linked Supplier Terms
Index-linked price clauses rarely arrive through a single, deliberate decision. They accumulate: a framework agreement here, a facilities contract there, a software renewal that references an inflation measure because that was the wording in an earlier template. By the time a finance team reviews them, the clause may be several years old, the contract owner may have left, and the invoice may simply be paid because it always has been. The result is a recurring cost that is visible in the accounts but rarely examined at the level of the individual clause.
A 45-day audit is not an exercise in rejecting indexation. Indexation can be a reasonable way to share inflation risk over a long supply relationship. The purpose is narrower and more practical: to establish whether the index, the timing, the base figure and the calculation method are what the contract actually permits, and to quantify the difference between the wording and the practice. For UK mid-market boards, that difference is often small per invoice and material across a year.
Why the clause survives routine review
Most procurement reviews focus on the headline price at the point of award. The escalation mechanism sits in a schedule or a set of terms and conditions, and it is often tested only when the annual increase is applied. By then, the supplier has issued the revised price, the operational team has absorbed it into the budget, and finance is comparing the new invoice with the previous one rather than with the contract.
There are three common sources of drift. First, the index may have changed in practice: a contract may refer to RPI, while the invoice applies CPI, or the supplier may use a published series that is broader or narrower than the one named. Second, the timing may be wrong: an increase may be applied on the anniversary of the first invoice rather than the contract commencement date, or before the notice period has expired. Third, the base figure may have moved without a corresponding contractual basis, particularly where a contract has been varied, renewed or novated.
None of these necessarily indicates bad faith. They are the ordinary consequence of decentralised contract management. But they do mean that the board cannot assume the escalator is operating as agreed simply because the invoice is being paid.
Days 1 to 10: Build the schedule before testing it
The first task is to create a single schedule of every supplier arrangement that contains an index-linked price mechanism. This should include contracts that are clearly active, contracts that renew automatically, and arrangements where the pricing schedule refers to an external index even if the main contract does not use the word inflation.
For each arrangement, record the supplier, the contract owner, the start date, the renewal date, the relevant clause reference, the named index, the base date, the frequency of adjustment, the notice period and the current annual value. Do not attempt to resolve discrepancies at this stage. The objective is completeness: a clause that is omitted from the schedule will not be tested later.
The schedule should be built from contracts and purchase orders rather than from the accounts payable ledger alone. The ledger will show what was paid, but it will not reliably show what was agreed. A parallel review of the top twenty suppliers by spend is useful as a sense-check, but the schedule should be contract-led.
Days 11 to 20: Test the wording against the mechanism
The second phase is a clause-by-clause reading. For each entry, compare the contractual wording with the mechanism actually applied. The questions are straightforward but need to be answered consistently.
Does the contract name a specific index, and does the invoice use that index? Is the relevant index the headline measure or a variant, such as CPIH rather than CPI? Is the base month clearly stated, and does the supplier use the same base month each year? Does the contract permit an increase on a fixed date, or on the anniversary of commencement, and has that date been applied correctly? Is there a cap, a collar, a floor or a right to challenge the increase? Does the clause require evidence of the index movement, or prior notice, before the increase takes effect?
Where the wording is ambiguous, record the ambiguity rather than resolving it in the supplier's favour. Ambiguity is a governance finding in its own right, because it creates a recurring negotiation point that nobody owns.
Days 21 to 30: Reconstruct the invoice history
Contract wording alone does not establish the cost of drift. The next step is to reconstruct the invoice history for each material arrangement, typically over the past two or three adjustment cycles. This is where the quantification begins.
For each cycle, calculate what the invoice would have been under a strict reading of the contract and compare it with what was actually charged. The difference may arise from index choice, timing, base figure, rounding, or the application of an increase to a price that had already been varied. Small differences should be recorded, not dismissed; their significance lies in whether they recur.
This phase also tests whether the operational and finance teams are working from the same assumptions. A supplier may have applied an increase correctly under the contract while the budget holder believed a different index applied. That is still a control gap, because the business cannot manage a cost it has not correctly described.
Days 31 to 38: Quantify and rank the exposure
The output of the reconstruction should be a ranked schedule. For each arrangement, show the annual value, the cumulative difference identified, the recurring annual effect if the current practice continues, and the strength of the contractual position. A clause with a large annual value but a weak challenge case may rank below a smaller contract with a clear wording mismatch and a long remaining term.
The board does not need a list of every rounding difference. It needs a small number of decisions: which clauses should be corrected at renewal, which should be raised with the supplier now, which should be accepted as commercially reasonable, and which require a contract variation to remove future ambiguity. The schedule should make those choices explicit.
Days 39 to 45: Convert findings into governance
The final week should produce more than a report. It should assign ownership. Each material clause needs a named contract owner, a review date and a documented position on the index and base figure. Renewal diaries should be updated so that notice periods are not missed. Finance should have a standing test for index-linked invoices, not merely a comparison with last month.
It is also worth deciding where the organisation stands on indexation as a matter of policy. A business that accepts CPI-linked increases as standard should say so, and should ensure that suppliers are not applying RPI or a broader measure by default. A business that expects caps or notice periods should put those expectations into its template terms rather than relying on negotiation at renewal.
What the board should see
A useful board summary is one page: total annual spend affected by index-linked clauses, the number of clauses tested, the number with a wording or application mismatch, the cumulative difference identified, and the recurring annual effect. Alongside that, the board should see the three or four decisions it is being asked to endorse.
The point is not to treat every supplier as an adversary. It is to ensure that the escalator in the small print is a deliberate commercial term, reviewed on a known cycle, rather than a habit that continues because nobody has tested it since procurement last looked.