Skip to content
Skip to content

Learn

Retroactive vs. Prospective Price Adjustment: Which to Use

A prospective adjustment applies the new price only to work done after the adjustment date. A retroactive adjustment reaches back and reprices work already invoiced. Retroactive is fairer when publication lag is long, but harder to administer, because it means correcting invoices already sent.

How to decide

  1. Estimate the publication lag. Compare how long the index takes to publish against how often the contract adjusts.
  2. Check who the lag favours. Under a prospective structure with rising prices, the buyer gets the old price a little longer, every cycle.
  3. Choose prospective if the lag is short. Simpler to administer, rarely creates a meaningful gap.
  4. Choose retroactive if the lag is long. Closes the gap, at the cost of correcting invoices already sent.

The difference in one sentence

A prospective adjustment changes the price only for work done from the adjustment date forward. A retroactive adjustment changes the price for work already done, back to when the new index value technically took effect, even if it published later.

Why this matters more than it sounds

Publication lag means the index value for a given month is not known until later. If a contract adjusts prospectively on the 1st using the prior month's index, a real cost change happens during that lag and never gets priced in. Retroactive adjustments close that gap, at the cost of reopening and correcting invoices already sent.

A worked example

A clause has a 2-month publication lag and adjusts prospectively every month. Every single cycle, the buyer pays the old, lower price for roughly 2 months before the new number catches up. Over a 3-year contract with rising prices, that structural gap is worth real money to the buyer, not a rounding error, and the supplier absorbs it every cycle without the contract ever naming it.

When prospective works fine

If the publication lag is short relative to the adjustment frequency, or the index is stable enough that a one-period lag rarely matters, prospective adjustment is simpler for both sides to administer and rarely creates a meaningful gap.

When retroactive is worth the complexity

If the publication lag is long, or the index moves fast enough that a one-period delay is a real cost, retroactive adjustment protects whichever side would otherwise absorb that gap every period. This is common in fast-moving input categories, where a systematic one-period lag compounds into an ongoing loss for one side.

Check who the lag favours

Check who benefits from the lag under a prospective structure, by default. If rising prices mean the buyer always gets a period of the old, lower price before the adjustment catches up, prospective adjustment is quietly biased in the buyer's favour, and the supplier should know that before agreeing to it.

Related reading

What is the formula for a price escalation clause?

The core formula is: adjusted portion equals covered portion multiplied by (current index divided by base index). The ratio of current to base index is the escalation factor. It is applied to the indexed part of the price, not the whole contract, and is usually bounded by a cap.

Read more →

What is a de-escalation clause in a price adjustment contract?

Most escalation clauses are written to move price only one way: up, when the index rises. A de-escalation clause is the same ratio mechanism applied when the index falls, lowering the price instead of leaving it stuck at the higher level. Without explicit de-escalation wording, a clause that only defines an upward adjustment leaves the buyer overpaying indefinitely once the index drops back down.

Read more →

When should a contract use a fixed price instead of an escalation clause?

A fixed-price contract sets one price for the term and puts all cost-index risk on whichever side accepted that price. An escalation clause instead shifts a defined slice of that risk to the buyer as costs actually move, in exchange for a starting price with no built-in risk premium. Short-term, low-volatility contracts usually do not need escalation. Long-term or volatile-input contracts usually do.

Read more →

See this calculated automatically

Escalake tracks the index, applies the formula, and gives both sides a number they can confirm, no spreadsheet required.