Latest / The Acquisition Talk with Fexingo: Mergers, Buyouts, and Business Sales for Operators / The M&A Disclosure Schedules Trap That Cost a Buyer $60 Million
Transcript
- Lucas: Let's say you're buying a company for $300 million. You've negotiated 40 pages of representations and warranties. You've got indemnification, escrow, the whole deal. You sign. And then you find out the seller had a $60 million liability that they never told you about — and legally, they didn't have to. Luna: Wait — didn't have to? How is that possible? The reps and warranties should cover that. Lucas: That's what most buyers think. And that's exactly the trap. It's all in the disclosure schedules — those thousand-page appendices that get dumped in an Excel file at the last minute. If you don't read every cell, you can lose tens of millions. Luna: So the schedules are where the seller carves out exceptions to their reps. If they disclose a problem there, they're covered. Lucas: Exactly. And that's fair — you want sellers to be transparent. But the trick is in how they draft them. Vague entries, buried footnotes, references to documents that aren't attached. The buyer's legal team might review the schedules, but the business team doesn't always dig into the details. Luna: And you said this cost a buyer $60 million. What's the specific case? Lucas: I'm thinking of a deal that closed in early 2025 — a private equity firm bought a manufacturing company. The seller's disclosure schedules had a line item that said 'Certain customer contracts subject to renegotiation or termination.' That's it. No list, no amounts. The buyer's team flagged it but assumed it was standard — maybe 5% of revenue at risk. Luna: But it wasn't 5%. Lucas: It was one contract — 40% of revenue — with a termination clause triggered by a change of control. The seller knew, but because they disclosed it in the schedules, they were off the hook. The buyer found out six months later when the customer walked. $60 million in lost value. Luna: That's brutal. And you're telling me the buyer had no recourse? No indemnification claim? Lucas: None. The rep on material contracts said 'except as set forth in Schedule 3.12.' And Schedule 3.12 had that vague line. The buyer's own lawyers had signed off on the disclosure schedules. The judge said the seller fulfilled its obligation. Luna: So the buyer's only mistake was not reading the schedules carefully enough. But in a $300 million deal, how do you audit every line of a thousand-page appendix? Lucas: You can't do it manually in a two-week due diligence window. And that's exactly the point. This is a structural trap in how M&A is practiced. The schedules are often treated as a back-office afterthought — the lawyers draft them, the seller stuffs them in a data room, and no one reads them with the same rigor as the main agreement. Luna: And the sellers know this. So they hide the real risks in plain sight. Lucas: Right. It's not fraud — it's exploitation of a process flaw. And I've seen it happen again and again. In fact, this very podcast is possible because listeners like you support the work we do to surface these traps. We deliberately don't run ads on these episodes. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. Luna: Yeah, and honestly, keeping this ad-free means we can dig into these details without interruption. It's worth it. Lucas: So back to the schedules — the first trap is vagueness. But there's a second, even more insidious one: the 'knowledge qualifier' trap. Luna: Oh, I know this one. The seller says 'to the best of the seller's knowledge, there are no undisclosed liabilities.' But the schedules only list what the seller actually knows. If they didn't know about a problem, it's not disclosed. Lucas: Exactly. And then the buyer can't claim a breach because the rep was qualified by knowledge. So the schedules become a safe harbor — anything the seller knew is disclosed, anything they didn't know is not a breach. But the buyer still bears the risk. Luna: So how do you protect against this? As a buyer, what's the practical fix? Lucas: First, you require the seller to reproduce the full text of every disclosure schedule in the agreement itself — not just reference an Excel file. That forces them to be specific. Second, you negotiate a 'bring-down' condition that requires the schedules to be accurate as of closing, not just signing. Luna: But wouldn't that give the seller an out to update the schedules right before closing? They could add a bunch of new disclosures at the last minute. Lucas: That's a risk. So you also negotiate a 'no material adverse effect' qualifier — any new disclosure that would have a material adverse effect gives the buyer a walk right. Or you negotiate a specific indemnity for any schedule item that wasn't disclosed before signing. Luna: So it's a balancing act. You want to force specificity without giving the seller a chance to sandbag you with new disclosures at closing. Lucas: Exactly. And there's a third fix: hire a disclosure schedule auditor. Some firms now specialize in this — they read every schedule line by line, cross-reference it with the data room documents, and flag inconsistencies. It costs maybe $50,000 to $100,000 on a $300 million deal. That's cheap insurance. Luna: I've heard of those. They basically do what the buyer's legal team should do but doesn't have time for. Lucas: Right. And the best ones use AI tools to scan for patterns — like vague language, missing dollar amounts, or references to documents that aren't attached. It's a new niche, but it's growing fast. Luna: Let's talk about another variation: the 'rolling disclosure' trap. I've seen sellers update schedules continuously during due diligence, and the buyer never gets a final, clean set. Lucas: That's a huge problem. The seller emails a new version of Schedule 4.15 on a Friday at 5 PM — the buyer's team doesn't see it until Monday, and by then the deal is signed. The best practice is to freeze the schedules at signing and only allow updates for de minimis items. Luna: And what about the seller's perspective? Is there a legitimate reason for vague schedules? Lucas: Sometimes. If the seller has hundreds of customer contracts, listing every single one with details would be impractical. So they group them by category. But the trick is to be specific enough that a reasonable buyer can assess the risk. If you say 'certain contracts contain change of control provisions,' that's too vague. But if you say 'contracts with customers A, B, and C contain change of control provisions that could result in termination,' that's specific. Luna: And as a seller, you want to avoid post-closing disputes. Vague schedules just invite litigation. Lucas: Exactly. So it's in both parties' interest to be clear. But the power dynamic matters — in a competitive auction, sellers can push vague schedules because buyers are afraid to ask too many questions and lose the deal. Luna: So the buyer has to decide: is this a deal-breaker, or do I accept the risk? Lucas: And that's the core of M&A negotiation. You can't eliminate all risk. But you can structure the deal so that the risk is priced in — either through a lower purchase price, a larger escrow, or specific indemnities for identified schedule items. Luna: Give me a concrete example of a good schedule — one that protects both sides. Lucas: Sure. Let's say the seller is a software company. The rep says 'all customer contracts are in full force and effect.' The schedule then lists: 'Contract with Customer X is under negotiation for renewal — estimated 20% revenue reduction if not renewed by Q3 2026.' That's specific. The buyer knows the risk, can diligence it, and can decide whether to adjust price or walk. Luna: And if the seller hides that in a footnote in a 500-page appendix, that's the trap. Lucas: Right. And the buyer's team has to be disciplined enough to read every footnote. That's hard to do in a hot deal market. Luna: So what's the one takeaway you want listeners to remember from this episode? Lucas: Treat disclosure schedules as a primary deal document, not an afterthought. If you're a buyer, assign a dedicated team member — or an outside auditor — to read every line. If you're a seller, be specific to avoid post-closing litigation. A vague schedule is a time bomb. Luna: And if you're a seller, you might also be tempted to hide things. But as we've seen in previous episodes, that often backfires. Lucas: Yeah, the long-term cost of a reputation for tricky schedules is higher than the short-term gain. Look, I'm curious — do you think AI tools will eventually automate this whole process? I mean, an AI that reads every schedule, cross-references every contract, and flags every vague line. Luna: I think it's coming. But for now, human judgment is still needed to assess whether a vague line is actually material. The AI can flag it, but a human has to decide if it's worth fighting over. Lucas: So the trap will evolve, but it won't disappear. That's a good note to end on. Thanks for listening.