EBITDA Bridge in Excel: Build a YoY Walk Analysis (2026)

May 24, 2026 · VeloraAI Team
Financial Modeling Data Analysis Excel

Every CFO presentation eventually lands on the same slide: a waterfall chart explaining why EBITDA went from $42M to $58M. The story is never just "we grew." It's price up $9M, volume up $7M, mix down $3M, input costs down $4M, FX a $1M drag. That slide is an EBITDA bridge in Excel — and if you can build one cleanly, you'll save your finance team hours of debate and your CEO a lot of confusion. This guide walks through a full year-over-year EBITDA bridge, including price-volume-mix (PVM) decomposition, the formulas, the waterfall chart, and the traps that double-count drivers.

What Is an EBITDA Bridge?

An EBITDA bridge is a structured waterfall analysis that reconciles the change in EBITDA between two periods into discrete drivers — typically price, volume, mix, cost inflation, productivity, FX, M&A, and one-offs. It starts at prior-period EBITDA, walks through each contributing factor as a positive or negative bar, and lands at current-period EBITDA.

The point isn't accounting precision — it's explanation. A well-built bridge converts a one-line variance ("EBITDA up $16M") into a defensible narrative ("price contributed $9M after $3M of unfavorable mix"). It is the single most-requested FP&A deliverable in board decks, lender reviews, and PE quarterly reports.

Why Bridges Beat Variance Tables

A standard variance table tells you that revenue grew $30M and COGS grew $14M. A bridge tells you why: was revenue up because you sold more units, raised prices, or shifted mix toward higher-ASP SKUs? Was COGS up because of input inflation, volume, or absorption?

💡 Pro Tip: Build your bridge in the same workbook as your three-statement model and link directly to the P&L. Hard-coding bridge inputs from a PDF is how reconciliation errors creep in.

How Do You Build an EBITDA Bridge in Excel?

To build an EBITDA bridge in Excel, start with prior-period EBITDA, isolate each driver using a fixed-base PVM convention (hold prior-year price/mix constant while flexing volume, then flex price), layer in cost variances by category, and plot the result with Excel's built-in Waterfall chart (Insert → Charts → Waterfall). The total of all driver bars must equal current-period EBITDA minus prior-period EBITDA.

The Seven-Step Build

  1. Pull two periods of P&L data at the SKU or segment level — not just consolidated totals.
  2. Calculate driver components (price, volume, mix, FX, cost inflation, productivity) using a consistent convention.
  3. Reconcile to total EBITDA delta — the sum of drivers must match within $1.
  4. Lay out the bridge table with starting EBITDA, each driver, and ending EBITDA in one row.
  5. Insert a Waterfall chart and set the start/end columns as Totals.
  6. Validate against your three-statement model — bridge EBITDA must equal P&L EBITDA.
  7. Document the convention in a footnote on the chart itself.
graph LR
    A[Prior Year EBITDA] --> B[+ Price]
    B --> C[+ Volume]
    C --> D[- Mix]
    D --> E[- Cost Inflation]
    E --> F[+ Productivity]
    F --> G[- FX]
    G --> H[+ M&A]
    H --> I[Current Year EBITDA]

What Are the Standard EBITDA Bridge Components?

A complete EBITDA bridge typically contains 6–10 line items grouped into commercial drivers (price, volume, mix), cost drivers (input inflation, productivity, fixed-cost absorption), and structural drivers (FX, M&A, one-offs). Below is the canonical structure used by most PE-owned companies and S&P 500 FP&A teams.

Driver Category Line Item Definition Typical Sign
Commercial Price Realized price change × prior-year volume + or −
Commercial Volume Volume change × prior-year price + or −
Commercial Mix Shift in product/segment weighting + or −
Cost Input Inflation Year-over-year material/labor cost increase − usually
Cost Productivity Yield, automation, sourcing savings + usually
Cost Fixed Cost Absorption Volume leverage on fixed overhead + or −
Structural FX Currency translation impact + or −
Structural M&A Acquired/divested EBITDA + or −
Structural One-offs Restructuring, legal, non-recurring + or −

ℹ️ Note: For services or SaaS businesses, replace "volume" with "customers" and "mix" with "ARPU shift." The PVM framework is universal even if the labels change.

Price-Volume-Mix Decomposition: The Formulas

PVM is the heart of any EBITDA bridge, and it's where most analysts get it wrong. The single biggest error is double-counting price within mix, which happens when you flex both price and mix off the current period instead of fixing a base.

The Fixed-Base Convention

The cleanest convention is: isolate volume first (at prior-year price and mix), then isolate price (at prior-year mix), then mix captures the residual. This avoids the order-dependency that plagues naive PVM builds.

Assume the following two-SKU dataset for FY2025 vs FY2024:

SKU PY Units PY Price CY Units CY Price
Product A 10,000 $20 12,000 $22
Product B 5,000 $50 4,000 $55

Volume Effect Formula

Hold prior-year price and prior-year mix constant. Multiply the change in total units by the prior-year weighted-average price.

=SUMPRODUCT((CY_Units-PY_Units),PY_Price)

For our dataset:

  • Product A volume effect: (12,000 − 10,000) × $20 = +$40,000
  • Product B volume effect: (4,000 − 5,000) × $50 = −$50,000
  • Total volume effect: −$10,000

Price Effect Formula

Hold prior-year units constant. Multiply the price delta by prior-year volume.

=SUMPRODUCT((CY_Price-PY_Price),PY_Units)
  • Product A price effect: ($22 − $20) × 10,000 = +$20,000
  • Product B price effect: ($55 − $50) × 5,000 = +$25,000
  • Total price effect: +$45,000

Mix Effect Formula (Residual)

Mix is the residual after volume and price are isolated. It captures the impact of selling a different blend of products at different margins.

=Total_Revenue_Delta - Volume_Effect - Price_Effect

⚠️ Warning: Never compute mix as (CY_Mix − PY_Mix) × Price and price as (CY_Price − PY_Price) × CY_Units in the same bridge. You'll double-count the interaction term and the bridge will fail to reconcile.

Putting It All Together with LET

For a cleaner build in Excel 365, wrap the PVM logic in a single LET formula to keep the model auditable:

=LET(
  rev_py,   SUMPRODUCT(PY_Units, PY_Price),
  rev_cy,   SUMPRODUCT(CY_Units, CY_Price),
  vol,      SUMPRODUCT((CY_Units-PY_Units), PY_Price),
  price,    SUMPRODUCT((CY_Price-PY_Price), PY_Units),
  mix,      (rev_cy - rev_py) - vol - price,
  CHOOSE({1;2;3;4}, "Volume", "Price", "Mix", "Total"),
  vol, price, mix, vol+price+mix
)

Pair this with our Excel LET function guide for the full syntax.

How Do You Build the Cost Side of the Bridge?

The cost side decomposes the change in COGS and OpEx into input inflation, productivity savings, and fixed-cost absorption. Pull each cost category at the line-item level, apply the same fixed-base logic, and report each as a separate bridge bar.

Input Inflation

Calculate the cost rate change per unit, then multiply by current-year volume:

=(CY_Cost_Per_Unit - PY_Cost_Per_Unit) * CY_Units

If raw material cost per unit rose from $8 to $9 and you sold 16,000 units this year, input inflation is ($9 − $8) × 16,000 = −$16,000 (negative because it's a cost increase).

Productivity / Savings

This is the negotiated or engineered cost reduction, typically tracked as a separate line in the cost ledger. It shows up as a positive EBITDA bar.

=SUMIFS(Savings_Ledger[Amount], Savings_Ledger[FY], CY)

Fixed Cost Absorption

When volume grows, fixed overhead is spread over more units, improving margin. Calculate the implicit absorption gain:

=Fixed_Costs_PY * (CY_Units - PY_Units) / PY_Units

💡 Pro Tip: Always show productivity as a separate bar even if it nets to a small number. Operators want to see whether savings programs are landing. Burying productivity inside "cost inflation" is how Lean teams lose their budget.

Reconciliation: Make the Bridge Tie

A bridge that doesn't tie is worse than no bridge — it shakes confidence in the entire deck. Build an explicit reconciliation row that checks Starting EBITDA + Sum of Drivers = Ending EBITDA and conditional-format the cell red if the difference exceeds $1.

=IF(ABS((Start_EBITDA + SUM(Drivers)) - End_EBITDA) > 1, "CHECK", "OK")

graph TD
    A[Prior Year P&L] --> B[Driver Calculations]
    C[Current Year P&L] --> B
    B --> D[Bridge Table]
    D --> E{Bridge Total = Actual Delta?}
    E -->|Yes| F[Insert Waterfall Chart]
    E -->|No| G[Re-check PVM Convention]
    G --> B
    F --> H[Board-Ready Slide]

How Do You Create the Waterfall Chart in Excel?

To create a waterfall chart in Excel, select your bridge table (driver name in column A, value in column B), go to Insert → Charts → Waterfall, then right-click the first and last bars and check "Set as Total". Excel automatically colors positive bars one color, negatives another, and totals a third.

Step-by-Step Chart Build

  1. Lay out your data in two columns: driver labels (e.g., "PY EBITDA," "Price," "Volume," ... "CY EBITDA") and values.
  2. Select the range including headers.
  3. Click Insert → Insert Waterfall, Funnel, Stock... → Waterfall.
  4. Right-click the "PY EBITDA" bar → Set as Total. Repeat for "CY EBITDA."
  5. Adjust the connector lines (Format Data Series → Series Options) and remove gridlines.
  6. Add data labels with Add Chart Element → Data Labels → Outside End.

Example: A clean board-ready waterfall shows PY EBITDA in gray, positive drivers in green, negatives in red, and CY EBITDA in gray. Avoid the default Office palette — it's instantly recognizable as a template.

Native Waterfall vs Stacked-Column Hack

Before Excel 2016, analysts faked waterfalls with stacked column charts using invisible "base" series. The native waterfall (Excel 2016+) is faster but has two limitations: it can't easily display subtotals mid-chart, and it doesn't support secondary axes. If your bridge has subtotals (e.g., "Commercial Subtotal" after Price/Volume/Mix), either stick with the stacked-column hack or split into two charts — our Excel waterfall chart guide covers both the native Waterfall chart and the stacked-column method in detail, including how to handle mid-chart subtotals and connector line formatting.

Method Pros Cons When to Use
Native Waterfall (2016+) One-click, auto-colors, totals supported No mid-chart subtotals, limited formatting 80% of cases
Stacked-Column Hack Full control, supports subtotals, runs on Excel 2013 Tedious to build, breaks when data changes Complex bridges, legacy systems
Power BI / Tableau Interactive, drill-down Outside Excel workflow Recurring exec dashboards

Common EBITDA Bridge Mistakes (And How to Fix Them)

After auditing hundreds of bridges, the same five errors show up over and over. Catch them before your board does.

1. Double-Counting Price and Mix

Already covered above, but worth repeating: fix the base before you flex. If mix and price both move the same period, your convention determines which captures the interaction. Document the choice in a chart footnote.

2. Ignoring Acquired EBITDA

If you bought a company mid-year, its EBITDA shows up in CY but not PY. Without an "M&A" bar, you'll attribute organic price/volume bars that don't actually exist. The fix: split CY into "Organic" and "Acquired" using stub-period reporting from the target's standalone P&L.

3. Lumping FX into Volume

For international businesses, currency translation can be the biggest single driver. Always isolate FX as its own bar, computed as:

=SUMPRODUCT(CY_Local_EBITDA, (CY_FX_Rate - PY_FX_Rate))

This holds local-currency performance constant and isolates the translation impact.

4. Showing One-Offs in the Wrong Place

Restructuring charges, legal settlements, and impairments belong in a separate "Non-Recurring" bar — never buried in OpEx. Otherwise you're telling investors your operating run-rate includes $5M of severance.

5. Not Reconciling to Reported EBITDA

If your bridge ends at $58.2M but the press release says $58.0M, you have a problem. Build a tie-out at the bottom that pulls reported EBITDA directly from the consolidated P&L and flags discrepancies.

⚠️ Warning: When a bridge fails to tie by more than rounding, the most common culprit is using different SKU dimensions in PY and CY data pulls. Always validate that both periods include the same product hierarchy.

Advanced: Building a Dynamic, Re-Runnable Bridge

A static bridge slide is fine for one board meeting. An FP&A team that builds bridges monthly needs a dynamic version — one that pulls fresh actuals, recomputes drivers, and refreshes the chart automatically.

Power Query for the Data Pull

Connect Power Query to your ERP or data warehouse. Build two queries — one for PY, one for CY — both pulling SKU-level revenue and cost. Append them into a unified fact table, then drive your bridge formulas from this table using SUMIFS or PivotTable references. For the full Power Query setup, see our Power Query for Financial Reporting walkthrough.

Dynamic Driver Calculation with LAMBDA

Wrap each driver in a LAMBDA so the formula can be reused across products, segments, or geographies:

=LAMBDA(py_u, py_p, cy_u, cy_p,
  LET(
    vol, SUMPRODUCT((cy_u - py_u), py_p),
    pri, SUMPRODUCT((cy_p - py_p), py_u),
    mix, SUMPRODUCT(cy_u, cy_p) - SUMPRODUCT(py_u, py_p) - vol - pri,
    VSTACK(vol, pri, mix)
  )
)

Name this PVM_Bridge in Name Manager, and call it as =PVM_Bridge(PY_Units, PY_Price, CY_Units, CY_Price) to spill volume/price/mix into three rows. See our LAMBDA custom functions guide for more.

Auto-Refresh the Waterfall

The native Waterfall chart auto-refreshes when its source data changes. Combine this with a single "Reporting Date" cell that drives all SUMIFS filters, and you have a one-click monthly bridge.

Frequently Asked Questions

What is the difference between an EBITDA bridge and a revenue bridge?

A revenue bridge decomposes only the top-line change into price, volume, and mix. An EBITDA bridge extends this by adding cost drivers (input inflation, productivity, fixed-cost absorption) and structural items (FX, M&A, one-offs). Most boards want the EBITDA version because it shows margin, not just demand.

How granular should EBITDA bridge drivers be?

Aim for 6–10 bars in the final chart. Fewer than 5 looks generic; more than 12 becomes unreadable. If you have 20 product lines, aggregate them into 3–4 categories for the chart but keep the SKU-level math in a supporting tab so you can drill down on questions.

Can I build an EBITDA bridge without SKU-level data?

You can build a partial bridge using segment-level revenue and cost, but you'll have to combine price and volume into a single "Net Revenue" bar. Without unit economics, true PVM is impossible. The fix is to push back on your data team to expose SKU-level actuals — it's table stakes for modern FP&A.

What's the right base period for a quarterly EBITDA bridge?

Use the same prior-year quarter for like-for-like comparison (Q2'25 vs Q2'24) to neutralize seasonality. Sequential comparisons (Q2'25 vs Q1'25) only make sense for non-seasonal businesses or when management wants to show recent momentum. Always label the chart with the exact comparison periods.

How do I handle negative starting EBITDA in a waterfall?

Excel's native Waterfall handles negative totals correctly — the bar simply renders below the axis. The visual gets awkward when the start is deeply negative and drivers push toward zero. In that case, anchor the chart axis manually (Format Axis → Bounds) and add a clear "From Loss to Profit" annotation.

Wrapping Up

An EBITDA bridge is the financial analyst's clearest tool for turning a one-line variance into a board-ready story. Get the PVM convention right, isolate cost drivers cleanly, reconcile to reported EBITDA, and let the native waterfall chart do the visualization work. The hard part is never the chart — it's the discipline of decomposing drivers without double-counting.

If you're building bridges monthly across multiple segments, VeloraAI can generate the PVM formulas and reconciliation logic from a natural-language description of your data, then audit the bridge against your P&L to flag tie-out errors before the deck goes out. For the next step, pair this with our sensitivity analysis and variance analysis guides to round out your FP&A toolkit.