Insights · Guide

Add-backs and quality of earnings: what survives QoE

The seller's adjusted EBITDA and the number that survives the buyer's quality-of-earnings review are rarely the same figure. Here is the gap, category by category, and how to close it before a buyer finds it.

10 min readUpdated October 2026Capital Refinery research

The short answer

An add-back is an adjustment to reported EBITDA for a cost the buyer would not inherit after close, such as above-market owner pay or a genuine one-time expense. A quality-of-earnings (QoE) team tests each one against four standards: is it recurring, does it reflect the real cost of replacing the role or asset, is it documented, and does it fit a conservative overall pattern. Add-backs that fail any test get rejected, and the seller's presented EBITDA shrinks accordingly.

8add-back categories a QoE team routinely tests
4tests each add-back has to pass
10-25%typical shrink in presented EBITDA during diligence

What add-backs actually are

A business sells on a multiple of earnings, and the earnings number that sets the price is not the EBITDA on the financial statements. It is an adjusted EBITDA, normalized for items a new owner would not carry forward. Those adjustments are add-backs, and they are a normal part of how middle-market companies trade.

The concept is legitimate. Owners run a company with a financial structure that reflects ownership, not enterprise economics: above-market pay, personal expenses on the books, family on payroll, below- or above-market rent to a related entity. None of that describes the business under institutional ownership, so the buyer adjusts for it.

The problem is asymmetry. The seller's banker builds an adjusted EBITDA with each normalization that helps the number. The buyer's QoE team then reviews each one under a stricter standard, and the gap between what gets presented and what survives is one of the most common sources of post-LOI renegotiation in middle-market deals.

Sellers who learn the QoE team's standard before going to market keep the headline number. Sellers who learn it during diligence do not.

The leverage compounds because price is not a dollar-for-dollar swap. A single add-back that gets rejected reduces EBITDA directly, and the purchase price is a multiple of EBITDA, so a modest rejected amount moves the final price by several times its own value. That leverage is why both sides treat the add-back conversation as consequential rather than a line-item exercise.

Eight categories: what survives QoE and what doesn't

Nearly all add-backs in a middle-market deal fall into one of eight categories. In each, there is a credible version and a theatrical version, and the QoE team's job is to tell them apart.

CategoryWhat survives QoEWhat doesn't
Owner compensationThe gap between owner pay and a market-rate CEO, documented with a comp study, adjusted down to a realistic replacement cost.Adding back the full owner salary as if the role disappears, or pricing the replacement far below market.
Family members on payrollPay for family who genuinely do not work in the business, or whose role can be eliminated without consequence, backed by a role analysis.Pay for family who do real work, since the role gets backfilled at the same or higher cost.
Personal expensesSpecific, individually documented personal charges: a named vehicle, a club, a defined trip.Broad categories that mix business and personal use, challenged across the whole category once the pattern shows.
One-time expensesGenuine one-time costs: a settled litigation matter, a one-time move, a discrete integration cost, each bounded and verifiable.Costs labeled one-time that recur year after year, such as annual legal fees or cyclical IT upgrades.
Related-party rentAbove-market rent to owner-held real estate adjusted down to market, backed by a third-party study and a clean lease the buyer can inherit.Below-market rent adjusted up, or above-market rent adjusted down without a clean lease at close.
Discontinued linesGenuinely discontinued operations with a clear end date, no residual revenue and no continuing obligations.A customer who left over a quality or service dispute, relabeled as discontinued rather than treated as churn.
Pro-forma acquisitionsTrailing-twelve-month results that include a mid-period tuck-in's full-year performance, backed by clean pre-close financials.Adjustments that assume synergies the seller has not actually captured.
Run-rate adjustmentsAlmost nothing. Buyers underwrite trailing-twelve-month performance.Annualizing one strong quarter, or crediting a new customer or new pricing as if it ran a full year.

Run-rate adjustments are the single most discounted add-back category. A strong quarter is not a strong year.

How the QoE team tests an add-back

The buyer's QoE team is not adversarial in posture. It is methodical, and it runs each add-back through the same four tests.

01

Recurring-pattern test

A cost that shows up two years running is recurring, even if the specific cause changes each time.

02

Role-replacement test

What does it actually cost to replace this role or asset once ownership changes? Benchmarked against market data.

03

Documentation test

Vague add-backs get discounted. Specific, individually documented ones survive.

04

Pattern test

Add-backs are read together. A few theatrical ones put a tighter standard on each other adjustment in the package.

The QoE team looks at three to five years of history specifically to test recurrence, and a cost that appears repeatedly, even under different labels, gets rejected as one-time.

Why theatrical add-backs cost more than they add

A theatrical add-back does not just fail on its own terms. It changes the buyer's posture across the deal. A buyer who expected honest normalization and found aggressive accounting instead shifts from closing the deal to protecting against the seller.

Aggressive presentation

  • Each normalization that helps the number, documented thinly or not at all
  • Rejected add-backs reduce the price directly
  • Reps and warranties tighten in response
  • Escrow rises and earn-outs lengthen on top of the price cut

Conservative presentation

  • Only the normalizations that will survive QoE, documented up front
  • The presented number holds close to the final number
  • Negotiating posture stays intact on the rest of the terms
  • Diligence finds more strength than the marketing book promised, not less

None of the tightened terms recover the rejected add-back. They are surcharges layered on top of the price cut the rejection already caused, and the math rarely works in the seller's favor: a rejected add-back costs multiple times the rejected amount in price, plus the cumulative cost of the tighter reps, larger escrow and longer earn-out that follow it. The honest version of the same number, the one that leaves the theatrical portion out from the start, costs only the gap between the theatrical and the credible amount, and it preserves negotiating posture on the rest of the agreement.

Why run-rate adjustments get rejected outright

Run-rate adjustments get a category of their own because QoE teams discount them more aggressively than any other add-back type. The logic is straightforward: a buyer underwrites trailing-twelve-month performance, not a projection built from the best recent month.

  • A strong fourth quarter annualized into a full year of implied EBITDA.
  • A new customer that just signed, credited as if it had already produced a year of revenue.
  • New pricing introduced mid-year, credited as if it covered the entire trailing period.

Almost nothing in this category survives. The QoE team rejects run-rate adjustments categorically rather than case by case, because the underlying logic, crediting a future run rate as if it were already history, does not change from deal to deal.

How to walk in with add-backs that hold

  1. 01Run a QoE-style review on your own EBITDA before going to market. Take each potential add-back through the four tests, and leave out anything that fails one.
  2. 02Document each add-back individually, with the source record, date and amount. A spreadsheet of adjustments is the standard; a vague category is a finding waiting to surface.
  3. 03Reconcile add-back history across the trailing three to five years. If this year's categories do not match last year's, that reads as a credibility issue across the whole package.
  4. 04Normalize owner compensation to a realistic post-close number, not zero and not the minimum. The buyer has to fund a real replacement.
  5. 05Treat family payroll, related-party rent and personal expenses with extra rigor. These are the three categories QoE teams discount most often, so documentation and market-rate benchmarks are the price of admission.

The seller who presents an adjusted EBITDA that survives QoE largely intact keeps the headline price. The seller whose EBITDA shrinks by 10-25% during diligence usually watches the price, and the deal structure, shrink with it.

None of this requires hiding anything from anyone at all. It requires running the same review on your own numbers that the buyer's team will run on them in a few months, early enough that there is still time to fix what the review finds instead of just disclosing it to a skeptical audience.

How Capital Refinery handles add-backs in the EBITDA bridge

Capital Refinery reads the QoE add-back schedule alongside the income statement, balance sheet, cash flow, bank statements, credit agreement and compliance certificate, among the 41 document families it classifies. Figures are traced to source, cited where a locator resolves, and advisory reconciliation checks flag inconsistencies on the spread without blocking the analysis.

  • Each add-back on the schedule carries a buyer position, accepted, rejected or negotiated, so the gap between presented and surviving EBITDA is visible line by line.
  • A fixed set of five house stress scenarios, rate, NOI and collateral shocks, shows how the number holds up under pressure.
  • Risk signals grade against the firm's own policy thresholds, and the memo re-grades on the next render if a threshold moves.
  • Memo sections for the financials and the bridge are assembled from that cited evidence, with the narrative sections staying with the deal team.
EBITDA bridge screen: screen coming soon
Live product screen · illustrative data

Questions

What is an add-back in a business sale?

An add-back is an adjustment to reported EBITDA for a cost or benefit the buyer would not inherit after close, such as above-market owner pay, a personal expense run through the business, or a genuine one-time cost. Add-backs raise the adjusted EBITDA the sale price is based on.

Why does adjusted EBITDA shrink during quality of earnings review?

Because the buyer's QoE team applies a stricter standard than the seller's banker did when preparing the adjusted EBITDA. Add-backs that are undocumented, recurring in disguise, or assume a role simply disappears get rejected, and the EBITDA the price is based on falls.

What is the recurring-pattern test for add-backs?

It is the QoE team's check for whether a cost labeled one-time actually recurs. A cost that shows up two years running is treated as recurring, even if its specific cause changes each year, and recurring costs cannot be added back.

How much can presented EBITDA shrink during diligence?

A 10% to 25% shrink in presented adjusted EBITDA during diligence is common, and the purchase price typically shrinks with it since price is set as a multiple of EBITDA.

Does owner compensation get added back in full?

Rarely. QoE teams typically add back only the gap between what the owner is paid and what a market-rate replacement would cost, not the full owner salary, since the buyer has to fund a real CEO after close.

How should a seller document add-backs before going to market?

Individually, with the source record, date, amount and reason for each adjustment. Vague categories get discounted as a group; specific, bounded transactions are the ones that survive QoE review.

Accelerate your deal execution process.

Private markets, connected. Bring automation to your deal execution.

Founder-led access. Every working session runs on your actual documents, not a generic demo.