M&A Drafting: Here’s a Clearer Way to Modify the Bringdown Condition by MAE

A couple of months ago I did this blog post about the redundant reference-point exception in the bringdown condition. Today we revisit the bringdown condition to consider an issue involving how the bringdown condition is modified by materiality.

The bringdown condition allows one side to use inaccuracy in the other side’s statements of fact (traditionally referred to as representations and warranties) to relieve it of its obligation to close. A seller would prefer to have the buyer’s bringdown condition be subject to a materiality qualification. That can be accomplished in one of two ways. You can have the condition require that the statements of fact be materially accurate or accurate in all material respects (they mean the same thing). Or you can use the phrase material adverse effect or material adverse change (they too mean the same thing).

Let’s consider the latter option. Here’s the relevant part of the bringdown condition from the merger agreement at issue in the Delaware Court of Chancery’s 2018 opinion in Akorn, Inc. v. Fresenius Kabi AG (PDF here):

The representations and warranties of the Company … (ii) set forth in this Agreement … shall be true and correct … as of the date hereof and as of the Closing Date with the same effect as though made as of such date … , except, in the case of this clause (ii), where the failure to be true and correct would not, individually or in the aggregate, reasonably be expected to have a Material Adverse Effect.

This is the standard way to qualify the bringdown condition by MAE, but the semantics don’t work. The exception applies unless the inaccuracy results in an MAE. It doesn’t make sense to think in terms of an inaccuracy resulting in an MAE. Instead, if, say, a “financial statements comply with GAAP” statement of fact is found to have been inaccurate, the circumstances giving rise to that state of affairs—and not the inaccuracy itself—constitute an MAE. In the usual scheme of things, the only consequences of inaccuracy would be that the buyer doesn’t have to close or the buyer has a claim for indemnification.

I first pointed this out in my book The Structure of M&A Contracts. And because I couldn’t get it to make sense, I said don’t use MAE to qualify the bringdown condition. But while working on my forthcoming article on the ambiguous material, I took the opportunity to ask some knowledgeable people about this, and I figured out the intended meaning, namely the meaning Vice Chancellor Laster applied in Akorn, starting page 195 (if I understand it correctly). Using the Akorn bringdown condition, here’s a better way to say it:

(I’ve stuck with the traditional language instead of using my own version of the bringdown condition. And the new language tracks language used elsewhere in the merger agreement at issue in Akorn.)

As a sanity check, I asked Glenn West what he thinks. He said, “I think your wording is clearer. I think Vice Chancellor Laster interpreted the other wording to say what your wording now more clearly says.” If Glenn thinks it’s clearer, that makes me feel more comfortable about my position.

So what’s an M&A practitioner to do? If your bringdown condition is qualified by MAE, it would be a good idea to revise it consistent with my revised version. But in M&A, change is scary. A glance at any acquisition contract would tell you that being clear and concise not only isn’t a priority, it would appear to be a liability, as it involves change.

Categories M&A

About the author

Ken Adams is the leading authority on how to say clearly whatever you want to say in a contract. He’s author of A Manual of Style for Contract Drafting, and he offers online and in-person training around the world. He’s also chief content officer of LegalSifter, Inc., a company that combines artificial intelligence and expertise to assist with review of contracts.