Retrospective insurer settlements and tariff true-ups (variable consideration and the constraint)

Retrospective tariff true-ups can swing revenue by material amounts long after the underlying services were billed; waiting for a signed reconciliation to record the adjustment means financial statements systematically lag known or reliably estimable changes, understating or overstating revenue relative to economic reality precisely in the periods analysts and lenders care about most.

Is there a contractual mechanism, such as an annual reconciliation clause, rebate/step-down tariff or most-favored-payor clause, that could retrospectively change consideration already billed and recognized? What is the current status and realistic range of outcomes of ongoing tariff negotiations or disputes with major payors? Is the true-up estimated using the expected value of a range of negotiated outcomes, or the single most likely settlement amount, and is that choice consistent with the population of contracts involved?

1) Review each major payor contract for retrospective adjustment mechanisms: annual reconciliation clauses, volume-based tariff step-downs, most-favored-payor clauses, or disputed historical billing settlement provisions. 2) For each mechanism, assess the current status and likely range of outcomes of negotiations or contractual triggers as of the reporting date, using the latest correspondence and historical settlement patterns with that payor. 3) Treat the expected retrospective adjustment as variable consideration from inception of the billing period it relates to: include in revenue only the amount for which it is highly probable that a significant reversal will not occur when the uncertainty is resolved, and recognise a refund liability for the expected reduction; do not wait for a signed settlement before reducing revenue. 4) Update the constrained estimate at each reporting date as negotiations progress, treating changes as a revision to the original transaction price estimate (cumulative catch-up), not a new, unrelated event. 5) Distinguish tariff true-ups (a pricing/measurement issue under IFRS 15) from routine claim-level rejections (a separate variable consideration estimate) to avoid double-counting or confusion in disclosure. 6) Formalize the adjustment once the settlement is finalized, true-ing up the earlier estimate to the confirmed amount.

Use the expected value method when a range of plausible negotiated outcomes exists with reasonably estimable probabilities, or the most likely amount when the settlement is essentially binary (e.g. a fixed step-down that either triggers or does not based on a clear volume threshold); incorporate the latest correspondence, historical settlement patterns with the payor, and legal/commercial advice into the estimate; apply the constraint so that revenue includes the variable amount only to the extent it is highly probable that a significant reversal of cumulative revenue will not occur; an expected reduction is therefore reflected without waiting for it to become highly probable, while a possible favourable outcome stays out of revenue until the constraint is met.

Disclose significant retrospective adjustment mechanisms embedded in payor contracts (reconciliation clauses, step-downs, most-favored-payor terms); disclose the amount of revenue affected by tariff true-up estimates during the period; disclose the nature of major unresolved negotiations as of the reporting date and the estimation method used; disclose the refund liability balance separately from other contract liabilities where material.

• Deferring any accounting recognition until a tariff dispute or annual reconciliation is contractually finalized, or reducing revenue only once a cut becomes highly probable, ignoring the requirement to estimate and constrain the outcome earlier
• treating an expected retrospective tariff cut as a subsequent, unrelated adjustment rather than a revision to the original transaction price estimate
• failing to distinguish tariff true-ups from insurer claim rejections in disclosure, confusing users about the nature of revenue volatility
• not updating the estimate as negotiation status changes materially during the year, leaving a stale position at each interim reporting date.