Establishing the Baseline and Planning Fact Base

2.1 Defining the Baseline: Costs, Revenue, Headcount, Contracts, Sites, and Systems

The baseline is the agreed representation of the businesses before synergy actions are implemented. It provides the denominator for opportunity sizing and the counterfactual against which realization will later be evaluated. A useful baseline is neither a single financial statement nor an indiscriminate collection of every available data field. It is an integrated set of financial and operational measures organized around the value levers that management expects to examine.

The starting point should be scope. Teams must identify which legal entities, business units, geographies, products, functions, and periods are included. In a full-company acquisition this may appear straightforward, but exceptions arise quickly: discontinued operations, minority-owned entities, shared-service centers, recently acquired businesses, transitional service arrangements, or assets scheduled for divestiture. In a carve-out, historical reporting may not correspond to the perimeter being transferred. In a joint venture, portions of parent-company operations may support the venture without becoming part of it. Every baseline therefore needs a written perimeter definition before detailed analysis begins.

Cost baseline: Cost data should normally be captured at a level that permits both financial reconciliation and operational analysis. General-ledger accounts alone are rarely sufficient. Procurement opportunities may require spend by supplier and category; workforce opportunities require compensation by role and location; facilities opportunities require occupancy and operating cost by site; technology opportunities require vendor, application, infrastructure, and labor costs. The baseline should distinguish fixed from variable costs where the distinction matters, identify allocations separately from directly incurred expenses, and flag costs governed by long-term commitments.

A common mistake is to treat total expenses as addressable expenses. The objective is not to demonstrate how large the combined cost base is, but to establish which portions could plausibly change because of the transaction. Regulatory fees, pass-through expenses, depreciation on retained assets, or costs already committed under long-term arrangements may offer little near-term opportunity. A preliminary synergy assessment can help focus baseline work on the categories most likely to contain economically meaningful overlap rather than applying equal analytical effort everywhere.

Revenue baseline: Revenue analysis should preserve the dimensions needed to test commercial synergy hypotheses. Depending on the business, these may include customer, product, geography, channel, contract, sales representative, price, volume, recurring versus transactional revenue, and gross margin. Teams should reconcile customer-level or product-level files back to reported revenue because commercial datasets often differ from accounting records due to timing, returns, intercompany sales, discounts, or incomplete classifications.

Revenue baselines also need a clear definition of customer overlap. Two records with different names may represent the same corporate customer, while one customer identifier may encompass multiple buying entities with different decision-makers. Cross-sell analysis built on poorly matched customer masters can substantially overstate opportunity. Similar care is required when one company reports bookings, another reports billings, and the synergy model measures recognized revenue.

Headcount baseline: Workforce information should include more than employee counts. For relevant functions, capture role, organizational unit, manager, location, employment status, compensation, vacancy status, contractor use, and potentially tenure or skill information. Full-time equivalents should be distinguished from physical headcount. Vacant positions require explicit treatment: eliminating an open role can reduce future spending, but claiming both the existing vacancy benefit and an additional synergy for eliminating the position would double count value.

Contracts and supplier baseline: Contract information determines how quickly many cost actions can be executed. Teams should capture supplier, service or category, annual spend, contract term, expiration date, renewal provisions, minimum commitments, termination rights, change-of-control provisions, pricing structure, and responsible owner. A headline assumption about vendor consolidation may be economically attractive but unavailable for several years if both companies are locked into separate agreements.

Sites and assets: Facility baselines should include location, purpose, ownership or lease status, capacity, utilization, headcount, operating expense, lease expiration, exit obligations, and relevant constraints. Manufacturing and distribution analyses may require throughput, equipment capacity, logistics flows, or product qualifications. Office consolidation may depend less on square footage than on hybrid-work policy, lease terms, workforce geography, and required workplace configuration.

Systems: Technology baselines should identify applications, infrastructure, cloud services, licenses, vendors, user populations, support resources, renewal dates, interfaces, data dependencies, and criticality. The existence of two applications with similar labels does not prove that one can be eliminated. Teams need to understand functionality, integration architecture, regulatory requirements, migration effort, and the operating processes each system supports.

These baseline components should be connected through common organizational and financial identifiers wherever possible. The purpose is to allow a team to trace a proposed initiative from an operating fact to a financial outcome. If a procurement initiative affects a supplier contract, for example, the analyst should be able to identify the relevant spend, business owners, legal commitment, cost centers, and financial accounts without reconstructing the fact base from scratch.

2.2 Establishing Consistent Definitions, Time Periods, and Accounting Treatment

Combining two datasets does not create a combined-company baseline unless the underlying definitions are comparable. Businesses frequently use the same word for different measures and different words for the same measure. One company may define headcount as active employees on payroll, another may include contractors, and a third may report budgeted positions. One may classify hosting expense as technology while another places it inside product cost. Without a common data dictionary, apparent differences and overlaps may be artifacts of classification rather than genuine synergy opportunities.

The baseline team should establish definitions before large-scale modeling begins. At minimum, definitions should cover revenue, gross margin, operating expense, headcount, full-time equivalents, contractors, procurement spend, capital expenditure, recurring costs, one-time costs, intercompany transactions, allocations, and the principal functional categories used in synergy planning. Definitions need not duplicate the entire accounting policy manual. They should resolve the issues that could change opportunity sizing or realization reporting.

Time periods: The preferred baseline is usually a recent period that represents normal operations and can be reconciled to official records. Depending on the transaction, this may be the latest fiscal year, trailing twelve months, a current-year forecast, or a combination of historical actuals and forecast data. Using a single month multiplied by twelve is generally weak unless seasonality and unusual events are immaterial. Using an old fiscal year may be equally misleading if the business has grown, restructured, or changed pricing materially since then.

Teams should specify whether every dataset uses fiscal or calendar periods and document differences in fiscal year ends. They should also establish a common currency and translation convention for multinational businesses. Average exchange rates may be appropriate for income-statement items, while balance-sheet measures may require period-end rates. The important point is consistency: synergy opportunities should not appear to change merely because different workstreams apply different foreign-exchange assumptions.

Accounting treatment: Financial classification affects both the baseline and the future proof of realization. Teams should determine whether costs are recorded above or below EBITDA, capitalized or expensed, treated as cost of goods sold or operating expense, and allocated or directly incurred. They should understand lease accounting, stock-based compensation, restructuring charges, intercompany transactions, and other material policies that differ between the businesses. Relevant M&A financial analysis can help reconcile transaction economics with management reporting when accounting conventions complicate comparisons.

Allocations deserve special attention. Corporate functions commonly distribute costs to business units using revenue, headcount, transaction volumes, or other drivers. A business-unit P&L may therefore contain an allocated charge that will disappear, persist, or be replaced after integration. Eliminating an allocation in a spreadsheet does not create value if the underlying cost remains elsewhere in the enterprise. Teams should identify the original cost pool, allocation methodology, and economic owner before recognizing savings.

Intercompany activity can create similar distortions. Revenue from one entity may be expense to another, and combining two organizations may eliminate the accounting transaction without changing consolidated economics. Conversely, a new shared-services arrangement may create charges between entities without changing total enterprise cost. Baselines should therefore distinguish external economics from internal transfers.

The team should also establish conventions for partial ownership and joint ventures. A venture may report 100 percent of its operating economics internally while a parent recognizes only its proportional interest or equity earnings. Parent-provided employees, intellectual property, facilities, or services may be charged under negotiated agreements rather than recorded at the underlying parent cost. The planning baseline should reflect the economic level at which the synergy will actually be managed, while separately showing how value flows to shareholders when necessary.

A concise baseline policy document can prevent weeks of later debate. It should identify scope, reference period, currency, accounting basis, organizational taxonomy, major definitions, allocation treatment, normalization conventions, and the authority responsible for resolving exceptions. Once approved, changes should be controlled. Analysts should not silently redefine a metric because a different treatment improves an initiative’s economics.

2.3 Building the Synergy Planning Data Request and Fact Base

A well-designed data request translates the synergy hypotheses into specific information needs. Poor requests ask broadly for “all financial data,” “all contracts,” or “organizational information,” overwhelming management while still failing to obtain the fields required for analysis. Effective requests begin with the decisions the team expects to make and work backward to the minimum data necessary to support them.

The planning team should first map each major synergy hypothesis to its required evidence. Workforce consolidation may require organizational charts, employee rosters, compensation, vacancies, contractors, and functional activity data. Procurement analysis may require accounts-payable transactions, supplier masters, contracts, category classifications, and purchase volumes. Commercial analysis may require customer-level revenue, products purchased, margins, pipeline data, churn, sales territories, and channel relationships. Technology consolidation may require application inventories, contracts, infrastructure usage, license counts, support headcount, and migration dependencies.

A practical initial request typically covers six categories:

• Financial data: Income statements, balance sheets where relevant, general-ledger extracts, budgets, forecasts, cost-center hierarchies, account mappings, and management reporting.
• Commercial data: Customer and product revenue, volumes, pricing, margins, contracts, channels, pipeline information, and customer segmentation.
• People data: Employee and contractor rosters, organization structures, compensation, vacancies, locations, reporting relationships, and functional classifications.
• Third-party spend: Accounts-payable transactions, supplier masters, category mappings, contracts, purchase orders, and committed expenditures.
• Asset and site data: Facilities, leases, capacity, utilization, equipment, logistics nodes, and relevant capital plans.
• Technology data: Applications, infrastructure, vendors, licenses, users, costs, interfaces, renewal dates, and planned investments.

Each request should specify the fields, time period, level of granularity, expected file format, source system, owner, and required date. This reduces the risk of receiving a PDF summary when transaction-level data were required or receiving current headcount without historical compensation needed to reconstruct cost. A request tracker should record submission status, quality issues, follow-up questions, and replacements so the team knows which analyses rest on provisional information.

The fact base should distinguish source data from analytical transformations. Original extracts should be preserved unchanged. Cleaning, mappings, assumptions, exclusions, currency conversions, and calculated fields should occur in controlled working files or models with documented logic. This makes it possible to trace an output back to its source when management challenges a number. It also prevents successive analysts from applying undocumented adjustments to already modified data.

Data lineage becomes particularly important when multiple workstreams use the same information. Procurement, finance, operations, and technology teams may all use vendor-spend data. If each independently cleans suppliers and applies exclusions, they can produce inconsistent totals and overlapping savings claims. A central fact base should provide agreed master dimensions for organizational entities, cost centers, suppliers, customers, sites, and systems. A broader integration planning process should define where shared data, assumptions, and dependencies are maintained so functional workstreams do not develop competing versions of the combined company.

Pre-close information restrictions require deliberate design. Clean teams may be permitted to analyze competitively sensitive information that operating teams cannot yet see. Customer-level pricing, future commercial strategy, compensation, or supplier terms may require restricted access. The synergy team should identify which analyses can proceed with aggregated information and which require a clean-team process. Legal counsel should determine the applicable restrictions; synergy ambition never justifies inappropriate information sharing.

Data quality should be assessed as information arrives rather than after every request is complete. Useful tests include reconciliation to reported totals, duplicate detection, completeness by month or entity, unexplained null values, inconsistent identifiers, and abrupt changes in classification. Analysts should quantify important gaps. “Supplier data are incomplete” is less actionable than “12 percent of addressable spend lacks a category classification, concentrated in three business units.”

Management interviews remain necessary even when datasets are excellent. Source systems tell the team what is recorded; operating leaders explain why it is recorded that way and what can actually change. A contract database may show an expiration date but not an informal commercial commitment. An organizational chart may show duplicated roles while concealing materially different responsibilities. A systems inventory may identify redundant applications but not the regulatory process that depends on one of them.

Joint ventures require explicit attention to data ownership. Parent companies may have relevant customer, technology, intellectual-property, or employee information that cannot simply be transferred into the venture. The planning team should establish what data the venture may receive, how it may be used, who can access it, and whether aggregated analyses are sufficient. Data rights can become a genuine constraint on synergy execution, particularly where parents remain competitors outside the venture.

The goal is a fact base that is decision-ready rather than theoretically perfect. Teams should prioritize material data defects, document residual uncertainty, and avoid delaying high-confidence actions because an immaterial field remains incomplete. At the same time, unresolved gaps affecting major targets should be visible in the confidence assessment rather than buried inside the model.

2.4 Normalizing Baselines for Growth, Restructuring, and Other Changes

Historical actuals are often an inappropriate counterfactual for future synergy measurement. Businesses grow, shrink, restructure, change prices, open facilities, exit products, hire employees, renegotiate contracts, and implement productivity programs independent of a transaction. A baseline that ignores these changes can make ordinary business movements appear to be synergy or can hide genuine transaction-related benefits.

Normalization adjusts the reported baseline to represent the economic position that would reasonably have existed without the synergy initiative. The purpose is not to create a more attractive target. It is to improve comparability between the counterfactual and the realized outcome. Every significant normalization should have a documented rationale, supporting evidence, financial impact, and approval of the owner.

Growth: A rapidly growing business may require more employees, warehouse capacity, cloud consumption, or customer-support resources even after integration. Holding historical spending flat could therefore overstate savings. Teams may need to create a volume-adjusted baseline based on revenue, transactions, units produced, customers served, or another operational driver. Conversely, declining volumes may naturally reduce costs, and those reductions should not automatically be attributed to synergy.

Inflation and pricing: Supplier prices, salaries, utilities, freight, and other inputs can change materially during the capture period. If a category would have increased from $20 million to $22 million without the transaction and integration actions hold spend at $20 million, the economic benefit may be $2 million even though reported expenditure did not decline. The treatment should be agreed in advance because inflation-adjusted savings can otherwise become highly subjective.

Standalone restructuring: Transactions often coincide with cost programs already underway. If Company A had independently approved the closure of a facility before the deal, those savings should generally remain part of the standalone case rather than being reclassified as merger synergy. Teams should identify announced, approved, funded, or substantially committed initiatives and establish a consistent rule for what is considered business as usual.

Recent acquisitions, disposals, and reorganizations: Historical results may include businesses that are no longer in scope or omit assets that recently entered the perimeter. Pro forma adjustments may be necessary to put both organizations on the same basis. The same principle applies to functions transferred between cost centers or entities. Organizational movement should not create artificial savings merely because an expense is reported in a different location.

Vacancies and planned hiring: Headcount baselines should address open positions and approved future hires explicitly. If a vacant role is necessary to operate the standalone business but integration removes the underlying work, avoiding the hire may represent a valid benefit. If the vacancy already reflects a company-wide hiring freeze unrelated to the transaction, claiming the full amount as synergy may be inappropriate. The key is the counterfactual, not whether cash happened to be spent in the historical period.

Capital and technology programs: Planned system replacements, facility investments, automation projects, or capacity additions can complicate both cost and capital baselines. A merger may eliminate the need for a planned investment, accelerate it, or replace it with a different program. Avoided capital expenditure should be identified separately from operating savings, and teams should document whether the investment was sufficiently committed to belong in the standalone case.

Normalization should not become an unrestricted opportunity to rewrite history. A useful control is to maintain both the reported baseline and the normalized baseline, with a bridge showing each adjustment. The model should preserve who proposed the adjustment, its source, its approval date, and its impact. Significant changes should be reviewed by finance rather than accepted solely by initiative owners.

Joint ventures require normalization of parent-company contributions as well. If a parent intends to provide a service under a transitional arrangement, historical internal cost may differ substantially from the fee charged to the venture. Likewise, assets contributed at formation may have accounting values that differ from their economic replacement cost. The planning baseline should reflect the economics relevant to the venture’s business plan while allowing shareholders to understand differences from their own pre-venture cost structures.

Normalization matters most where performance will later be challenged. A sophisticated model is unnecessary for immaterial categories, but large or contentious initiatives need a defensible counterfactual. The baseline should answer a simple question: absent the transaction-related action, what would management reasonably expect this cost, revenue, headcount, or investment requirement to have been?

2.5 Baseline Validation Checklist and Reconciliation with Finance

A synergy baseline should not become official merely because a consulting team completed the model. Finance must be able to reconcile it to the company’s records, understand material adjustments, and apply the same logic when benefits are reported months later. Baseline validation is therefore both an analytical control and a governance process.

Validation should occur progressively. Waiting until the end of planning to involve finance can reveal fundamental inconsistencies after functional teams have already built hundreds of initiatives. Finance representatives should participate when scope, accounting conventions, and normalization rules are established, then review material category baselines as they stabilize. This does not require finance to approve every row of operating data; it requires finance ownership of the financial logic that converts operational actions into reported value.

A practical validation checklist should address five questions:

• Is the perimeter correct? Confirm included legal entities, businesses, functions, geographies, discontinued operations, carve-out adjustments, and joint-venture interests.
• Does the baseline reconcile? Tie financial totals to audited results, management accounts, budgets, or an explicitly approved forecast, with unexplained differences investigated.
• Are classifications consistent? Confirm common definitions for functions, accounts, employees, suppliers, customers, sites, systems, and recurring versus one-time items.
• Are adjustments defensible? Review growth, inflation, restructuring, acquisitions, disposals, vacancies, foreign exchange, allocations, and other normalizations, with evidence for material changes.
• Can realization be measured later? Ensure each major value pool can be traced to accounts, cost centers, operating measures, contracts, budgets, or other evidence that will remain available during implementation.

The reconciliation should start from a recognized financial control total and bridge to the analytical baseline. For example, an operating-expense baseline might begin with reported company expense, remove out-of-scope entities, eliminate intercompany items, reclassify certain accounts into common functional categories, add approved pro forma changes, and arrive at the synergy-planning baseline. The bridge should make every material difference visible. A reader should never have to choose between believing the synergy model and believing the financial statements.

Detailed operating data should then reconcile upward to those control totals. Supplier spend should connect to accounts payable or relevant expense accounts; headcount cost should reconcile to payroll and compensation accounts; site expense should tie to lease, occupancy, and facility records; technology expense should align with vendor spend, payroll, and capitalized costs. Perfect one-to-one reconciliation may be impossible because operational and accounting systems serve different purposes, but residual differences should be quantified and understood.

Finance validation also establishes the future measurement method. If a procurement baseline is built from invoiced spend but initiative owners later report purchase-order savings, reported realization will be inconsistent. If workforce savings are calculated from fully loaded compensation during planning but actual results are validated using salary only, the initiative will appear to underperform for methodological reasons. Definitions established at baseline should therefore flow into the rules used for integration performance tracking.

Responsibility should be explicit. Initiative owners are accountable for operational assumptions and execution. Functional finance teams typically validate local economics. Corporate finance or the integration finance lead establishes common rules and reconciles aggregate results. The synergy office maintains the initiative and assumption record. Internal audit or controllership may become involved for particularly material, externally communicated, or sensitive measures. These roles should complement rather than duplicate one another.

Disagreements should be resolved before targets are locked. When finance and an operating team differ on the baseline, the issue should be framed precisely: whether a cost is in scope, whether an adjustment belongs in the standalone case, whether a benefit is recurring, or whether evidence is sufficient. Escalating a defined issue is far more productive than debating an unexplained difference between two spreadsheets.

Baseline governance must continue after approval. New information may reveal missing contracts, incorrect classifications, changed transaction perimeters, or errors in historical data. Teams should permit corrections, but changes must be controlled. The original baseline, revised baseline, rationale, financial impact, approval, and date should remain traceable. Initiative owners should not be able to improve reported performance by quietly reducing their denominator or shifting costs outside the measured category.

The final baseline package should be usable by someone who did not build it. At minimum, it should contain the perimeter definition, data dictionary, source inventory, financial reconciliation, normalization bridge, material assumptions, known limitations, and approved baseline values by relevant function or value pool. Supporting detail should permit analysts to trace important figures back to source systems and documents.

For joint ventures, validation should include the venture finance team and, where economics flow differently to each shareholder, appropriate parent representatives. The parties should distinguish venture operating performance from shareholder-specific accounting effects, transfer prices, service fees, and contributions. Agreement on these rules at formation reduces the risk that parents later reach different conclusions about whether the same synergy was realized.

A validated baseline does more than support a synergy model. It creates the common economic language for the remainder of the capture program. Once management agrees what the business would have looked like without the transaction, subsequent debates can focus on the actions, assumptions, timing, and evidence that determine whether value is actually being created.