Adjusted EBITDA Add-Backs: How Finance Should Decide What Belongs

Executive summary

• An expense does not qualify as an add-back because it was unusual, unbudgeted, or non-cash. Test whether it belongs to normal operating economics.
• Adjustments that reappear across periods signal a structural cost, not noise. Track add-backs by category across at least eight quarters.
• Removing only the unfavorable items inflates Adjusted EBITDA quietly.
• Keep announced synergies and expected savings out of historical Adjusted EBITDA until they appear in reported results.
• Write the policy down before the period it governs, then present the number as a line-by-line reconciliation from reported EBITDA.

The monthly management report showed EBITDA down 18 percent. Sales were stable, gross margin had barely moved, and operating teams hit most of their targets. The difference came from a large ERP implementation cost, severance from a restructuring that had just closed, and a legal settlement management did not expect to repeat.

The CFO had two numbers in front of him: reported EBITDA, and the earnings level the business would more likely generate under normal operations.

The second number is useful only if finance calculates it correctly.

The test that should govern every Adjusted EBITDA add-back

Adjusted EBITDA has one job: show the earnings the business can sustain once genuinely unusual events are stripped out. That gives finance a single test for each proposed adjustment. Does removing this cost improve the view of sustainable operating performance without removing a normal economic cost of running the business? An item that fails the second half of the test stays in, whatever the invoice was coded as.

Three questions make the test usable during the close. Is the item tied to a discrete event with an identifiable start and end, such as a signed settlement, a board-approved restructuring plan, or a project with a go-live date? Would an operator running this business normally still incur the cost next year? Is there documentation behind the classification, or only a label in the general ledger?

Recurring costs are the most common Adjusted EBITDA add-back failure

The clearest signal that an adjustment is wrong is that it keeps coming back. Restructuring in Q1, integration costs in Q2, a second restructuring in Q4, severance in three of the last four quarters — each defensible on its own, and together a description of how the company actually operates. A business that reorganizes every year carries a reorganization cost structure, and removing it every year produces an earnings figure the business has never delivered.

Build the frequency check into the close rather than into diligence. Maintain an add-back register by category, carried across at least eight quarters, and review it before the reporting pack is finalized. Any category appearing in more than half the periods gets reclassified into operating costs and stays there until the pattern breaks. A quality-of-earnings provider will run exactly this analysis, and it is better to have the answer before someone else produces it.

Adjustments have to work in both directions

Add-backs drift because the pressure on them is one-sided. Losses get flagged, argued over, and removed; gains of the same type sit quietly in the P&L because nobody has a reason to raise them. A company that adds back the loss on disposing of a warehouse while keeping the gain on the sale of its delivery fleet has selected for unusual items rather than adjusted for them, and the resulting number climbs each period without anyone deciding that it should.

The fix is to define the treatment by event type, not by whether its impact is positive or negative. If insurance settlements are excluded, the same treatment should apply whether they create a loss or a gain. Set the policy at the event level, apply it consistently in both directions, and the resulting number is far more defensible under scrutiny.

Future savings are not earnings

Run-rate adjustments are where Adjusted EBITDA usually crosses from judgment into advocacy. Headcount reductions announced in November, procurement savings still under negotiation, and synergies from an acquisition that is halfway integrated, are all forecasts. Historical Adjusted EBITDA reports what the business generated during the period, and expected improvements enter the number only once they show up in reported results.

The information itself still matters. Present run-rate effects in a separate bridge, labeled as forward-looking, with the assumption and expected timing shown against each item. Buyers and lenders will form their own view either way; the difference is that they can see which part of the number is history and which part is a plan.

A reference table for the tricky Adjusted EBITDA add-backs

Two habits keep the number defensible over time. Write the policy down before the period it will govern, so the definition is not being negotiated while the results are already known. Then present Adjusted EBITDA as a reconciliation from reported EBITDA, line by line, with a one-line rationale beside each adjustment.

One KPI Is Never the Full Story

No single KPI gives management a complete view of performance. Adjusted EBITDA becomes more informative when it is read alongside revenue, gross margin, operating expenses, cash generation, and other measures that show whether underlying performance is actually improving.

Kudwa gives finance teams a connected view of these KPIs through dashboards and financial analysis, making it easier to identify trends, investigate movements, and focus management attention where it matters.

If you want to see how that works against your own reporting pack, take a look at Kudwa's automated reporting.

‍