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

As a teaching example, take an index with a 2-month publication lag and a clause that 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.

Lag differs by index. The BLS producer price index publishes about two weeks after the month it covers, so for a PPI clause the gap is much smaller than in this example. The publication lag guide covers how to measure 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.

Run this on your own numbers

Enter a base value, a current value, and a contract amount to see the adjustment.

Related reading

Should a contract use CPI-U or CPI-W?

Use CPI-U for general commercial, service and lease contracts, and CPI-W for wage agreements, pensions and payments tied to Social Security cost-of-living adjustments. Both are US city average, not seasonally adjusted, never revised, and published the same day.

Read more →

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 →

See this calculated automatically

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