Standalone Costs in Carve-Out Due Diligence: Estimating the True Cost of Independence

Standalone Costs in Carve-Out Due Diligence: Estimating the True Cost of Independence

When a business unit is carved out from a larger group, its historical financials do not reflect its true standalone cost structure. Functions currently provided by the parent company at nil cost or through internal allocations must be replaced. The standalone cost analysis estimates what the business would cost to operate independently.

This analysis is critical for both buyers and sellers. Buyers need to understand the real cost base they are acquiring. Sellers need a credible standalone cost estimate for the vendor due diligence report. Getting it wrong can mean mispricing the transaction by millions.

Why Historical Costs Mislead

A carved-out entity's reported financials typically include parent company allocations that do not reflect economic reality. Common issues include:

Below-market allocations. The parent provides IT infrastructure, payroll processing, or treasury services at an allocated cost that is lower than what the carved-out entity would pay independently. A parent company running SAP S/4HANA across the group might allocate a fraction of the license cost to the division, but the standalone entity would need its own ERP system at full cost.

Shared personnel. The group CFO, general counsel, or HR director provides services to multiple divisions. Their cost is allocated, but the carved-out entity would need its own hires or outsourced replacements.

Group procurement benefits. Volume discounts on insurance, raw materials, or professional services may not survive the separation. The carved-out entity's standalone procurement costs could be 10 to 20 percent higher for certain categories.

Zero-cost services. Some functions may not be allocated at all. Group-level compliance, internal audit, investor relations, or corporate development functions that benefit all divisions may carry no allocation to the carved-out entity.

The Standalone Cost Framework

A structured approach to standalone cost estimation examines each function that the parent currently provides or subsidizes:

Corporate Functions

Infrastructure

The technology stack requires particular attention. Migrating from the parent's ERP environment to a standalone system is one of the most significant post-separation costs. This includes:

• ERP licensing and implementation (SAP, Oracle, NetSuite, or Microsoft Dynamics)
• Financial reporting tools
• CRM and sales management systems
• IT infrastructure (servers, networking, security)

Transitional Services

Most carve-outs involve a Transitional Services Agreement (TSA) where the parent continues providing services for 6 to 24 months while the standalone entity builds its own capabilities. The TSA cost represents the bridge between the current allocated cost and the long-term standalone cost.

Data Requirements for Standalone Analysis

Estimating standalone costs requires data that extends beyond the standard due diligence dataset:

• Group cost allocation schedules: Documenting how parent costs are allocated to the carved-out division
• Shared services agreements: Current internal pricing for inter-divisional services
• Headcount data: Staff who split time between the carved-out entity and other divisions
• Technology landscape: Systems used by the carved-out entity and their licensing/hosting arrangements
• Third-party contracts: Agreements that reference the parent entity and may need to be renegotiated

This data often resides in the parent's GL under cost center or intercompany account codes. Extracting and analyzing it requires access to the chart of accounts mapping at a level of detail that identifies intercompany charges by nature and function.

Quantification Approach

For each standalone cost item, the analysis produces:

1. Current allocated cost: What the parent currently charges the division
2. Estimated standalone cost: What the function would cost on an independent basis, based on market benchmarking, third-party quotes, or comparable company analysis
3. Incremental standalone cost: The difference (standalone minus allocated), representing the additional cost the carved-out entity will bear
4. Implementation cost: One-time expenses to establish the standalone capability (hiring costs, system implementation, legal restructuring)

The total incremental standalone cost is then reflected as a pro forma adjustment to the carved-out entity's normalized EBITDA.

Common Pitfalls

Underestimating IT costs. ERP migration is expensive. A mid-market company implementing a new ERP system typically spends 500K to 3M EUR over 12 to 18 months. This cost is often underestimated in standalone assessments.

Ignoring diseconomies of scale. As a standalone entity, the business loses the parent's purchasing power. Insurance premiums, banking fees, and audit costs often increase.

Overlooking regulatory requirements. A standalone entity may need its own regulatory registrations, compliance infrastructure, or reporting obligations that were previously handled at the group level.

Double-counting with working capital. Some items that affect standalone costs also affect the working capital mechanism. Consistency between the two analyses is essential.

The Advisory Team's Role

Standalone cost estimation requires a combination of financial analysis, operational understanding, and market knowledge. The Transaction Services team typically works closely with the target's management to understand the current cost allocation methodology, then independently assesses the reasonableness of standalone cost estimates.

The quality of this analysis depends on the granularity of the underlying data. Teams that can efficiently extract, map, and analyze cost center-level data across multiple entities produce more credible standalone estimates in less time.