Synergy Tracking: From Model to Realized EBITDA

Executive summary

Synergy tracking is the practice of following each synergy in a deal model from its modeled amount to the dollars that appear in EBITDA, with an owner, a frozen baseline, and evidence at every step. Without it, a synergy number is a forecast that nobody can audit. With it, you can say exactly which initiatives delivered, which were delayed, which were offset, and which were never real.

The size of the prize is a formula: modeled run-rate synergy, less the part never executed, less the part executed but not visible in the data, less offsets, equals realized run-rate. In-year EBITDA is lower again by timing, and one-time cost to achieve sits beside it. Each term is a place where a deal case quietly shrinks.

The first move is to split the model into individual initiatives and freeze a baseline for each. Everything after that depends on the baseline. This guide is the detailed method behind the synergy ledger in the PMI Playbook: Day 1 to Day 365.

When to use this

Use this guide when:

• A deal model has a single "synergies" line that the board or lender expects you to deliver.
• Integration is underway and progress is reported as a percentage that nobody can reconcile to the P&L.
• You are a platform buying add-ons and want one repeatable method across deals.
• An investment committee will ask for a model-to-realized bridge at Day 365 or at exit.

It does not replace your accounting policies or your auditors' view of what can be reported in financial statements. Use it for management tracking, and agree with your finance leadership how the numbers relate to any externally reported or covenant-defined EBITDA. Check your credit agreement and lender documents for how adjustments such as synergies are defined, and involve counsel and advisers where definitions matter.

Diagnostic questions

1. Is every synergy in the model listed as its own initiative with an amount, a type, a driver, and a timing assumption?
2. Does each initiative have a baseline with a stated data source, period, and adjustments, and was it frozen before the work started?
3. Is there a single named owner for each initiative who works inside the combined business?
4. Do cost synergies state the volume at which they were calculated, so that a volume change can be separated from a price or efficiency change?
5. Are revenue synergies stated as revenue and as contribution margin, and is the margin definition written down?
6. Does the model include one-time cost to achieve by initiative, and is it coded in the ledger?
7. Can you tell, for each initiative, whether the action is complete, and where the evidence is stored?
8. Is there a rule for when a saving counts as realized (for example, visible in invoices or payroll for a full period)?
9. Who reconciles the synergy ledger to the general ledger each month, and does the reconciliation exist?
10. What happens to a synergy that is challenged or no longer possible: is it removed and reported, or left in the total?
11. Are offsets (inflation, backfilled roles, lost customers, dis-synergies) tracked in the same ledger?
12. Does the board see executed and realized separately?

If questions 1 and 2 fail, do not start tracking yet. Rebuild the model into initiatives first, because a tracker cannot measure something that was never defined.

The framework: baseline, stage, evidence

Synergy tracking rests on three components, each of which prevents a specific kind of error.

Stages

Report all five stages as separate columns. A single "% complete" hides which stage the dollars are in.

Baseline rules

A baseline needs four things written down: the data source (a named report or table, not "finance numbers"), the period (usually trailing twelve months before the deal closed or the action began), the volume or driver at which the baseline was calculated, and the adjustments (one-offs, acquisitions, known price changes already in motion). Freeze it. If the baseline must change, record the change, the reason, and who approved it, rather than editing silently.

Step-by-step process

1. Decompose the model. List every synergy as an initiative: description, type (cost or revenue), driver, model run-rate, timing, dependency. Owner: deal lead and CFO. Output: initiative list that reconciles to the model total, with the reconciliation shown.
2. Assign owners and approvers. One accountable owner in the operating business, plus the CFO or controller as the person who signs the realized numbers. Owner: CEO. Output: owner and approver columns complete.
3. Freeze baselines. Pull the data, record source, period, and driver. Owner: FP&A with each initiative owner. Output: baseline sheet, dated and signed.
4. Validate bottom-up. Each owner rebuilds the amount from the baseline and the specific action (for example, units times new price, roles times loaded cost). Owner: initiative owners. Output: validated amount, with a variance to the model, and a list of challenged items.
5. Attach cost to achieve. For each initiative, estimate and code the one-time costs (severance, retention, migration, duplicate rent, advisers). Owner: CFO. Output: cost-to-achieve budget by initiative with project codes in the GL.
6. Set evidence rules. Define what counts as proof at stages 3, 4, and 5: a signed contract and effective date, a payroll change, invoice-level data over a full period. Owner: Controller. Output: evidence standard, one page.
7. Update monthly. Owners update stage and executed run-rate by a set day; FP&A computes stage 4 and 5 values from system data against the baseline. Owner: FP&A. Output: updated ledger.
8. Reconcile to the GL. The in-period EBITDA column for each initiative should tie to identifiable lines in the P&L, and the total effect should not exceed what the P&L can show. Owner: Controller. Output: reconciliation note and unexplained differences list.
9. Review in the integration meeting. Walk the ledger by exception: slipped dates, challenged items, stage 3 items without stage 4 data. Owner: integration lead. Output: decisions logged with dates.
10. Report the bridge. Produce the model-to-realized bridge monthly to management and quarterly to the board or sponsor. Owner: CFO. Output: bridge and commentary.

Separating real savings from noise

The hard part of synergy tracking is that the P&L moves for many reasons at once. Four adjustments recur.

Price versus volume

A purchasing synergy is a lower price on the same volume. If volume falls, total spend falls, but that is not a synergy. Measure the price effect at actual volume:

Price synergy = (Baseline unit price − New unit price) × Actual units
Volume effect = (Baseline units − Actual units) × Baseline unit price   (not a synergy)

Gross versus net headcount

A headcount synergy is the loaded cost of eliminated roles minus any cost that replaces them: backfills, contractors, overtime, and new roles created to manage the combined business. Track the replacements in the same row, not in a different budget.

Revenue versus margin, and cannibalization

A revenue synergy is revenue that would not have happened without the deal. It becomes EBITDA at contribution margin, not at revenue. Net it against revenue lost from the same customers or products (cannibalization) and from customers who left because of the deal. Require customer-level evidence: which customer bought what, and when.

Timing

A saving executed in month seven contributes roughly five months to that fiscal year but a full year to run-rate. Report both. Do not annualize a month and present it as the year.

Templates

Synergy ledger (copy into a spreadsheet)

Baseline sheet

Model-to-realized bridge

Evidence standard (example wording to adapt)

Metrics and KPIs

Setting targets without invented benchmarks. The target for each initiative is its validated bottom-up amount, with dates tied to contractual events (supplier contract renewals, lease terms, notice periods) rather than a generic capture rate. At the portfolio level, use your own prior integrations as the reference once you have two or more, and compare their validation gap and realization rate rather than quoting an outside average. If a sponsor asks for a typical rate, answer with your own ledger or a named public source, not a remembered figure.

Common mistakes

1. Counting the contract as the saving. Symptom: executed and realized are the same column. Fix: separate stages 3, 4, and 5.
2. Baselines in someone's head. Symptom: two people compute different savings from the same contract. Fix: a baseline sheet with source and period.
3. Not adjusting for volume. Symptom: savings spike in a quarter when sales fell. Fix: price-volume split.
4. Revenue counted at revenue. Symptom: EBITDA synergy equals the revenue number. Fix: contribution margin, with the margin definition written.
5. Dis-synergies unrecorded. Symptom: lost customers and backfills sit in other budgets. Fix: an offsets column in the ledger.
6. Removing items silently. Symptom: the model total never changes though three initiatives died. Fix: show removed items and reasons in the bridge.
7. Quarterly updates. Symptom: stage 3 items sit unmeasured for months. Fix: monthly measurement day.
8. Self-reported progress. Symptom: owners report green without data. Fix: finance computes stages 4 and 5 from transaction data.
9. Ignoring cost to achieve. Symptom: one-time costs in "other." Fix: project codes by initiative.
10. One number for the board. Symptom: a single percentage on a slide. Fix: the bridge by initiative.

Worked example (illustrative)

The numbers below are made up to show the method. They are not benchmarks, and they describe no real company.

A buyer integrates an acquired company and tracks three initiatives. Dollar figures are annual.

Initiative 1: packaging purchasing. Baseline (trailing twelve months, from the AP subledger): 2,000,000 units at $1.50 = $3,000,000. After consolidating suppliers, the new price is $1.35. Over the next twelve months actual volume was 1,800,000 units because a product line was discontinued.

• Naive saving = $3,000,000 − (1,800,000 × $1.35) = $3,000,000 − $2,430,000 = $570,000.
• Price synergy at actual volume = ($1.50 − $1.35) × 1,800,000 = $270,000.
• Volume effect, not a synergy = (2,000,000 − 1,800,000) × $1.50 = $300,000.
• Check: $270,000 + $300,000 = $570,000.
• Run-rate at baseline volume = $0.15 × 2,000,000 = $300,000.

Reporting the naive figure would have claimed nearly double the real price saving.

Initiative 2: headcount overlap. Eight roles eliminated at an average loaded cost of $85,000 give gross savings of 8 × $85,000 = $680,000. Two contractors were engaged to cover work from those roles at a combined $70,000. Net run-rate = $680,000 − $70,000 = $610,000. If the exits took effect at mid-year, the in-year effect is $610,000 × 6 ÷ 12 = $305,000.

Initiative 3: cross-sell. The model assumed $1,200,000 of incremental revenue at a 35% contribution margin: $1,200,000 × 35% = $420,000. Customer-level data shows $200,000 of existing revenue from the same customers was displaced by the new products (cannibalization): $200,000 × 35% = $70,000. Net run-rate = $420,000 − $70,000 = $350,000.

Total realized run-rate = $300,000 + $610,000 + $350,000 = $1,260,000.

What the operator learns: the ledger shows the packaging line is real but half the size the naive calculation suggested, the headcount line carries a hidden offset that must be reported in the same row, and the revenue line needs a margin and a cannibalization figure to mean anything. In the bridge, each of these appears as a named line instead of a surprise at the board meeting. Whether any of these lines is eligible for an adjustment in a covenant or financing calculation depends on your agreements; confirm with counsel and your lender documents.

AI prompt assistance

Use AI to prepare and check the ledger. Provide your own data, and verify results against source records.

1. Build a price-volume split.

I will paste invoice-level purchases for one category for two periods (baseline and current) with units and unit prices. Compute price effect at actual volume, volume effect at baseline price, and mix effect if SKUs differ. Show the formulas and the arithmetic for each step, and confirm the three effects sum to the total change in spend.

Check: recompute the totals from the invoice data in a spreadsheet and confirm they tie to the AP subledger.

2. Flag ledger weaknesses.

Here is our synergy ledger. List initiatives with no named owner, no baseline source, stage 3 for more than 90 days without stage 4 data, or realized amounts that exceed executed run-rate. Return a table with the initiative ID and the issue.

Check: confirm each flag against the ledger yourself before raising it with owners.

3. Draft the bridge commentary.

Using this model-to-realized bridge, write a one-page explanation for the board: what changed since last quarter by initiative, which lines are at risk, and decisions needed. Use only numbers in the bridge and mark any statement that is an assumption.

Check: reconcile every number to the bridge and have the CFO approve before sending.

Implementation guide

Governance: the CEO owns the integration result, the initiative owner owns delivery, FP&A computes realized values, the controller signs the reconciliation, and the board or sponsor receives the bridge. Initiative owners should not sign off their own stage 5 values.

Downloadable assets

The ledger, baseline sheet, bridge, and evidence standard above are designed to be copied into a spreadsheet. The acquisition synergy calculator models synergy phasing and the cost to achieve it.

Related resources

• PMI Playbook: Day 1 to Day 365: the parent playbook for the full integration sequence.
• Integration Management Office (IMO) Setup: the cadence in which the ledger is reviewed.
• EBITDA bridge and continuous tracking: linking initiative results to reported EBITDA.
• Vendor Consolidation Playbook: the process behind purchasing synergies.
• EBITDA improvement calculator: sizing the earnings effect of an improvement.

Frequently asked questions

What is synergy tracking?

Synergy tracking is following each synergy from the deal model to realized EBITDA, with a named owner, a frozen baseline, a stage, and evidence at every step. It separates actions taken from results observed in transaction data and the P&L, so management and the board can see which synergies are real.

What is the difference between run-rate and realized synergies?

Run-rate synergy is the annualized value of an action once it is fully in place. Realized synergy is the part you can observe in invoices, payroll, orders, and the P&L, net of offsets. Run-rate is a statement about the future level; realized in-period EBITDA reflects what actually fell inside the year, which is usually lower because of timing.

How do you set a baseline for a synergy?

Write down the data source, period, volume or driver, and adjustments, then freeze it before the action starts. For purchasing, that is typically trailing spend by category with units and unit prices. If the baseline must change later, record the reason and the approver instead of editing it silently.

How do you count revenue synergies in EBITDA?

Count them at contribution margin, not revenue, and net out cannibalization and any customers lost because of the deal. Require customer-level evidence showing who bought what and when. State the margin definition in the ledger, and apply it consistently across initiatives and periods.

Why do synergies not show up in the P&L?

Common reasons are volume changes that mask price savings, backfilled roles and contractors, timing within the year, revenue assumed at full value rather than margin, and actions that were announced but not completed. A ledger that separates executed, run-rate realized, and in-period EBITDA identifies which reason applies to each initiative.

How this works in a System of Performance

A synergy ledger is only as good as the links between the plan, the transaction data, and the general ledger. In most companies those live in a deal model, an ERP, and a set of spreadsheets that drift apart. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. To see how your own integration numbers reconcile, bring it to us as a launch partner.