What to Keep in Mind for Your Next Purchase Price Adjustment Provision

What to Keep in Mind for Your Next Purchase Price Adjustment Provision

Summary

The Delaware Chancery Court’s decision in Northern Data AG v. Riot Platforms, Inc. clarifies how courts treat expert determinations in post-closing purchase price adjustment (PPA) disputes and the boundary between PPA mechanisms and indemnification claims. The court affirmed the expert on some accounting questions (defer to GAAP where required) and vacated the expert on matters it deemed legal issues tied to representations and warranties, sending those disputes to the indemnification process. The opinion stresses careful drafting of accounting rules and dispute-resolution clauses to avoid protracted litigation and unexpected costs.

Key Points

  • The court will defer to an accounting expert on factual accounting questions within the expert’s scope and where determinations comply with contractual accounting standards, reversible only for “manifest error.”
  • Interpretation of the contract’s accounting principles (for example, whether to apply GAAP alone or GAAP consistent with historical practices) is a legal question for the court and reviewed de novo.
  • If the agreement requires GAAP as the baseline, historical or illustrative accounting practices govern only to the extent they themselves comply with GAAP; otherwise the GAAP-compliant method controls.
  • Disputes that effectively challenge the accuracy of representations and warranties (e.g., alleged double-billing or misstated payables) are legal/indemnity issues and not for the PPA expert to decide.
  • Mistakenly treating indemnity claims as PPA accounting disputes can defeat negotiated indemnity caps and lead to lengthy, costly litigation despite an expert determination process.

Context and Relevance

This ruling matters for lawyers, deal teams and finance people drafting or negotiating M&A purchase agreements. It settles important questions about the limits of expert determinations and confirms that Delaware courts retain a strong gatekeeping role over legal interpretations of contractual accounting standards and the routing of claims into indemnity processes. As PPA mechanisms are intended to speed post-closing resolution, misunderstanding their scope can produce the opposite effect: long, expensive court fights and erosion of bargained-for indemnity limits.

Why should I read this?

Short version: if you do deals, this is gold. It tells you when an accounting expert will actually settle things and when you’ll end up back in court. Saves you from drafting traps that let the other side sneak around indemnity caps or turn legal warranty fights into “just an accounting” argument. Read it so you don’t pay for the other team’s loopholes later.

Practical takeaways

When negotiating or reviewing PPA and indemnity clauses, do the following:

  • Define the expert’s scope narrowly and state explicitly which accounting standard (GAAP) and whether historical practices will prevail even if non-GAAP.
  • Specify whether the expert can interpret contractual accounting language or whether legal interpretation is reserved to the court.
  • Be explicit about carve-outs to the exclusive remedy (PPA) vs indemnity process to avoid recharacterisation games.
  • Assess the target’s historical accounting for GAAP compliance before agreeing that historical practice will control.
  • Negotiate indemnity caps and thresholds with the realistic risk that true breaches of representations will be routed to indemnity and subject to those caps.

Author style

Punchy: this is a must-read for M&A counsel and dealmakers. The decision can materially change how post-closing disputes play out and whether your carefully negotiated indemnity limits actually mean anything. If your agreements use typical PPA language, don’t assume an expert will end the fight — the court might.

Source

Source: https://corpgov.law.harvard.edu/2025/09/17/what-to-keep-in-mind-for-your-next-purchase-price-adjustment-provision/

Leave a Reply

Your email address will not be published. Required fields are marked *