Quality of Earnings in M&A: Why Financial Statements Alone Can Deceive You

Imagine this: You've spent six months evaluating a software company. The financials look solid—$4.2M in EBITDA on $12M revenue. You've negotiated a 6x multiple, landing on a $25.2M purchase price. The deal closes. Three months later, you discover that $1.1M of those earnings came from one-time consulting contracts that won't renew. Your normalized EBITDA is actually $3.1M. At that multiple, you overpaid by $6.6M.

This isn't a hypothetical horror story. It's what happens when buyers accept financial statements at face value without questioning what those numbers actually represent. In the M&A world, we call this gap between reported and sustainable earnings "quality of earnings"—and understanding it is the difference between deals that create value and acquisitions that destroy it.

At Boundev, we've seen this pattern repeatedly. When companies acquire software businesses, they focus intensely on financial QoE—but neglect the technical equivalent. A company can have pristine financials and a codebase held together with duct tape, or strong margins and an engineering team held hostage by technical debt. This guide walks you through what Quality of Earnings analysis actually uncovers, why traditional financial QoE is necessary but not sufficient for tech acquisitions, and how to structure your due diligence to protect your investment.

What Quality of Earnings Actually Measures

Most business owners believe their financial statements tell the complete story of their company's health. They don't. A Quality of Earnings report asks a fundamentally different question than an audit: not "are these numbers accurate?" but "are these earnings sustainable?"

The distinction matters enormously. A financial audit confirms that your P&L was prepared according to GAAP and that assets equal liabilities plus equity. It doesn't tell you whether that $500,000 in "other income" represents a recurring revenue stream or a one-time gain from selling office furniture. It doesn't flag that your largest customer represents 47% of revenue and hasn't signed a renewal contract. It doesn't adjust for the owner's $380,000 annual salary for a job that a professional CFO would do for $140,000.

A QoE report normalizes these items. It converts reported EBITDA into adjusted EBITDA—the number that actually matters for valuation. In owner-operated businesses, this adjustment routinely reveals 25-40% differences between reported and sustainable earnings. The QoE analyst builds a "bridge" from reported to adjusted EBITDA, documenting every adjustment with supporting evidence. This bridge becomes the foundation for purchase price negotiations.

The EBITDA Bridge: Where Deal Value Lives or Dies

Every QoE analysis culminates in the adjusted EBITDA bridge. This document starts with reported EBITDA and walks through every adjustment that converts it to a sustainable, recurring figure. The bridge is where negotiations happen—because every adjustment has a dollar value, and that value gets subtracted from or added to the purchase price.

Here's how it typically unfolds. The target company reports $4.2M EBITDA. The QoE analyst begins building the bridge. Owner compensation adds back $380,000 (the difference between actual pay and market rate). Non-recurring legal fees from a completed lawsuit add back $175,000. A $240,000 consulting engagement from last year—a one-time project that won't recur—is subtracted. The analyst flags $320,000 in deferred revenue that was recognized early but won't generate cash this year.

After all adjustments, normalized EBITDA is $3.415M—not $4.2M. At a 6x multiple, that $785,000 difference represents $4.71M in overvaluation. This is exactly what happened to buyers who didn't conduct QoE before closing.

Why Tech Acquisitions Need a Different Kind of QoE

Here's what traditional QoE analysis misses: the technical infrastructure that determines whether those earnings are sustainable. For a manufacturing company, this matters less—equipment is visible, production capacity can be measured, and physical assets depreciate on a predictable schedule. For a software company, the core value driver is invisible in financial statements.

Consider two software companies, both showing $3M EBITDA on $8M revenue. Company A has a clean microservices architecture, comprehensive test coverage, and an engineering team of twelve with documented processes. Company B has a ten-year-old monolith held together by the work of three key engineers who built it—and no documentation whatsoever. Company A's EBITDA is sustainable because the codebase can evolve. Company B's EBITDA is entirely dependent on three people staying employed. The financial statements look identical. The risk profiles are radically different.

This is why acquisitions of software companies fail at a higher rate than traditional businesses. Buyers conduct thorough financial due diligence but skip technical due diligence. They discover after closing that the "profitable" product is built on a foundation that requires a complete rewrite to add basic features. Or that the engineering team—the actual source of value—departed six months post-close because the acquirer didn't understand what kept them there.

The Hidden Costs That Kill Software Acquisitions

Even with rigorous financial and technical due diligence, some acquisition costs lurk below the surface. Understanding these before closing changes how you structure the deal—and protects equity value at completion.

Working capital adjustments are the most commonly misunderstood post-closing mechanism. Most M&A transactions are structured on a "cash-free, debt-free" basis, with a normalized working capital peg established at closing. If actual working capital is below the peg, the seller owes money. If above, the buyer pays more. Sounds straightforward—until you realize that revenue timing, inventory decisions, and payables management can swing working capital by hundreds of thousands of dollars. In 2026, working capital purchase price adjustments appear in over 90% of private M&A transactions. The peg mechanism is your protection—or your exposure.

Another overlooked category: disclosed but unquantified liabilities. These include pending litigation (even if remote probability of loss), environmental remediation obligations, employment disputes, and contractual penalties for early termination. Financial statements capture known liabilities. They don't capture contingent ones. A thorough QoE analyst queries management on these, reviews board minutes for undisclosed items, and works with legal counsel to assess probability and magnitude of contingencies.

How Sellers Can Get Ahead of QoE Issues

The best time to address QoE issues isn't during due diligence—it's before you engage a buyer. Sellers who commission their own sell-side QoE report gain three critical advantages: they identify problems first, they control the narrative, and they enter negotiations from a position of transparency rather than defensiveness.

Consider the difference between two sellers entering the same data room. Seller A has never seen their normalized EBITDA. When the buyer's QoE analyst presents a $1.2M adjustment, Seller A reacts defensively—disputes the number, escalates to principals, and creates adversarial dynamics that poison the relationship before closing. Seller B commissioned a QoE six months before marketing. They already know about the $1.2M adjustment. They've prepared documentation supporting their position, and they've preemptively addressed the underlying issue (the non-recurring contract was a mistake—they've since signed three recurring customers in the same vertical). Seller B controls the conversation.

The practical pre-DD action plan is straightforward: clean the numbers first, document everything second, and address known issues before buyers discover them. This isn't about hiding problems—it's about presenting problems in context, with evidence and remediation plans. Buyers don't expect perfection. They expect transparency and a management team that understands their business deeply enough to explain it without panic.

How Boundev Solves This for You

Everything we've covered in this guide—EBITDA normalization, revenue quality analysis, working capital mechanics—applies to every M&A transaction. But software acquisitions have a unique exposure that traditional QoE can't address: the technical foundation that determines whether those normalized earnings are sustainable. Here's how we approach it for our clients.

Frequently Asked Questions