التكاليف العالقة: التكاليف العامة التي لا يتحملها أحد بعد إتمام عملية البيع

التكاليف العالقة: التكاليف العامة التي لا يتحملها أحد بعد إتمام عملية البيع

باختصار

Stranded costs after divestiture are the corporate overhead left behind when a division leaves. Group IT, shared service centres, real estate leases and corporate salaries are the common examples. The revenue leaves with the buyer. The stranded costs stay behind. No division ever owned this overhead alone, so no division head now owns removing it. Reallocating stranded costs across the remaining business does not solve the problem. It only moves the damage around. Recovering RemainCo's margin needs a precise baseline. It also needs one named executive with the authority to remove the stranded costs on a fixed timetable.

The trigger: completion closes while stranded costs stay in RemainCo

The sale closes. The proceeds land in the group's accounts. The board records a clean transaction. A few months later, the group management accounts tell a different story. Operating margins across the remaining divisions have fallen. Customer demand holds steady. Pricing holds. Volumes hold too. Nothing in the operating business explains the drop.

The cause sits in the cost base, not the market. For years, the divested unit carried a share of group overhead. That included the ERP licence, the corporate treasury team, HR administration and legal retainers. The unit left. The stranded costs did not leave with it. They stayed on the parent's books, unassigned to any surviving division.

Why reallocating stranded overhead does not remove the expense

Corporate finance teams usually respond the same way. They take the unassigned overhead and spread it across the surviving divisions using the existing cost keys. Factory and business unit managers wake up to allocations that have jumped twenty or thirty per cent overnight. Nothing in what they actually run has changed.

Reallocation does not remove stranded costs. It moves them. A division that consumes no more shared service capacity than before now carries someone else's departed cost base. It carries that cost through no fault of its own.

The disagreement that follows is understandable, not dysfunctional. Divisional leaders resist absorbing overhead they do not control. Central functional heads resist cutting their own headcount, since the group still needs some transitional support for the buyer. Both positions make sense on their own terms. Together, they leave the stranded costs sitting on the books, owned by no one. The unresolved overhead quietly eats into the value the sale should have created.

Why cross-border shared services make stranded costs harder to remove

Unwinding stranded costs is difficult enough within one country. Add a group headquartered in Germany, Switzerland, Austria or France. Add shared services delivered from Poland, Czechia or Romania. The task then gets harder in three specific ways.

Enterprise vendor agreements that perpetuate stranded software costs

Vendors usually price group ERP licences, telecom contracts and engineering software at global volume tiers. When one division leaves, the contract does not shrink with it. Minimum commitments often force the parent to keep paying for capacity nobody uses. Someone has to renegotiate the agreement formally, seat by seat. Vendor contracts are where stranded costs often prove stickiest.

Shared service centres built for scale rather than stranded cost reduction

A shared service centre in Krakow, Brno or Bucharest serves several countries by design. It cannot cut headcount by the exact share one departing entity represented. Supervisory layers and facility costs stay fixed until someone redesigns the operating model, not just the headcount plan.

European employment rules that delay removing stranded headcount

Restructuring shared services across Western and Central Europe usually means works council consultation, a redundancy case and statutory notice. Employment law is often the slowest lever for removing stranded costs. A board that waits for transitional services to expire before it starts this process adds unnecessary cost. Starting the process late can add twelve to eighteen months of extra wage cost to the bill.

Recognising stranded costs before they permanently lower margin

No board receives a report titled Stranded Costs. The problem shows up instead through a consistent pattern in the first two to four quarters after completion.

Organizations typically experience several warning signs that indicate stranded overhead is eroding profitability:

Operating divisions report falling margins despite steady operational trading due to heavier corporate cost allocations.

Quarterly business reviews devolve into disputes between division heads and corporate finance over allocation fairness.

Central IT continues paying maintenance fees on legacy server capacity and software seats scaled for the pre-divestiture footprint.

Shared service teams exhibit declining productivity because unneeded support personnel have not been redeployed.

Transitional service agreements (TSAs) run past their target expiration dates without a clear exit schedule.

Treating any one of these signs as a temporary transition variance is the mistake. Left alone, each becomes a permanent line in the RemainCo cost base.

Sizing stranded overhead before scoping the separation exit

Removing stranded costs starts with a forensic baseline, not a general cost-cutting mandate. Corporate finance has to unpick years of historical allocation. Every shared line of stranded costs needs a classification: kept for ongoing operations, transferred to the buyer, or eliminated entirely.

Timing matters as much as classification. A board that waits for the transitional services agreement to end loses valuable time. Planning the shutdown of systems, facilities and headcount cannot wait for that agreement to expire. The planning has to run in the first ninety days. This holds even when the agreement itself runs for six or twelve months. Once the transitional period ends, the stranded costs behind it should already stand ready to disappear. They should not trigger a fresh review.

Establishing clear separation cost accountability and programme ownership

This is the one place in a separation where the honest answer can be simple. The group may need no outside appointment at all. Where the divested unit stood largely self-contained, the group chief financial officer can absorb the work personally. Or the CFO can delegate it to a transformation lead who reports directly. That question is about separation cost accountability for stranded costs, not capability. An internal owner can carry it well.

Treating stranded overhead as a shared responsibility across divisional finance does not work. No divisional controller holds a mandate over corporate cost. Nobody removes it, so it survives by default. The mandate has to sit with one named executive who holds explicit authority over the group cost base.

An outside appointment earns its place only under specific conditions:

The shared infrastructure spans several countries.

Renegotiating enterprise vendor contracts needs dedicated commercial capability the group does not have internally.

The executives who would otherwise lead the programme are the same people whose budgets it cuts.

What independent research reveals about stranded overhead after divestiture

McKinsey's البحث on post-divestiture performance is clear. Parent companies often need up to three years to recover fully from stranded costs. Return on invested capital stays depressed until leadership restructures central and shared functions directly.

The Boston Consulting Group puts recurring stranded costs at 3 to 7 per cent of the divested unit's cost base. That figure covers something different from one-off separation and disentanglement spend. BCG also estimates that spend separately at 1 to 5 per cent of divested revenue in typical carve-outs. In complex cases, it can rise to 13 per cent. Roland Berger surveyed nearly 400 corporate separation specialists. Their research names unaddressed shared services as a leading cause of missed post-closing earnings targets across European industrial groups.

The two BCG figures answer different questions. Do not add them together. One measures the overhead a group keeps paying every year. The other measures the one-time cost of cutting the ties. Confusing the two is itself part of why boards under-plan stranded costs.

Case study: removing EUR 4.2 million in RemainCo stranded costs

The mandate: a German divestiture creating Polish shared service stranded costs

A German industrial equipment manufacturer based in Baden-Württemberg sold its non-core agricultural machinery division for EUR 110 million. The division represented thirty-five per cent of group turnover. An international trade buyer completed the purchase. The deal closed cleanly, and the group distributed net proceeds as planned.

The parent kept its central infrastructure: a corporate headquarters in Stuttgart and an IT hosting centre in Frankfurt. It also kept a shared service centre in Poznań, handling accounts payable, invoicing and payroll for the whole group. All of those stranded costs now belonged to RemainCo alone.

The friction: margin compression and idle capacity across shared functions

Within ninety days, operating margin in the surviving industrial tools business fell sharply. It dropped from 7.4 per cent to 3.8 per cent. Corporate finance reallocated EUR 6.5 million of overhead across the surviving factories in Germany and Czechia. Local plant managers pushed back against the stranded costs allocation. The new allocation put their annual bonus targets at risk, a reasonable response to a cost they could not control.

At the same time, IT kept paying for 1,400 unused SAP seats. It also paid for dedicated cloud capacity built for the divested operations. In Poznań, forty shared service accountants sat with reduced workloads. Local management held off on restructuring the team. These staff still gave informal support to the buyer under a loose transitional arrangement.

The intervention: appointing dedicated restructuring leadership within 72 hours

The supervisory board engaged CE Interim. Within 72 hours of the completed mandate brief, an interim Chief Restructuring Officer arrived in Stuttgart. The executive held full authority over the RemainCo overhead programme.

To eliminate the stranded overhead, the executive executed a structured, multi-step intervention plan:

Line-by-line account audit: Replaced arbitrary cost allocations with a transparent activity-based charging model, resolving internal disputes among plant directors.

Contractual optimization and novation: Triggered true-down clauses on 1,400 unused SAP seats and novated dedicated cloud infrastructure to the buyer, capturing EUR 1.6 million in annual savings.

Rightsizing shared services and commercialising transitional service agreements

Third, the executive restructured the Poznań centre itself. Working with Polish labour counsel, a voluntary separation programme removed twenty-five redundant administrative roles. Fifteen specialists stayed on to support the group's ongoing growth. Fourth, informal support requests to the departed business became a structured, priced service under a formal commercial rate card. This generated EUR 420,000 in fee revenue instead of absorbing cost for nothing.

The outcome: recurring overhead reduction and operating margin recovery

Within five months, the programme removed EUR 4.2 million in permanent, annualised stranded costs. That figure represented sixty-five per cent of the total stranded costs identified at the outset. The remaining EUR 2.3 million of shared services moved onto a lower cost base. The group still needed some of that capacity. Operating margins for the surviving business recovered to 7.1 per cent, close to where they stood before completion.

Frequently asked questions about stranded costs after divestiture

What expenses qualify as stranded costs after divestiture?

A stranded cost is a corporate expense that stays with the parent after a division leaves. Central IT, shared service capacity, corporate salaries, real estate and enterprise software licences all qualify. They count as stranded costs provided they once served the part of the group that has now gone.

How do recurring stranded costs differ from one-off separation costs?

A stranded cost recurs every year until someone removes it. A separation cost is a one-time expense of cutting the ties: legal work, systems disentanglement, advisory fees. BCG treats these as separate figures for good reason. Boards that plan for one and not the other under-budget the recovery.

When should a parent company size stranded overhead?

At signing, not after completion. A board that waits until the first quarterly variance appears has already lost the months when action was cheapest.

Who should take accountability for removing stranded costs?

The group chief financial officer, personally or through a delegated transformation lead. It becomes an appointment for an outside executive under two conditions. The shared infrastructure crosses several countries, or the internal owners face a conflict of interest in cutting their own budgets.

Can enterprise IT and software contracts shrink after a division sale?

Yes. Companies can trigger contractual true-down clauses and novate specific licence pools to the buyer. They can also negotiate volume reductions at renewal, or decommission redundant cloud capacity. Each route needs a technical and a commercial negotiation with the vendor, not just a request.

How long is the window to remove stranded overhead before it becomes permanent?

Roughly the length of the transitional services agreement. Once the organisation re-absorbs the departed workload as normal practice, cutting it becomes a much harder argument to win.

The decision facing the group CFO after a sale is simple to state and hard to act on. Remove stranded costs on a fixed timetable, or let them sit as a permanent tax on RemainCo's margin. Where the divested unit stood largely self-contained, internal finance teams can absorb the adjustment through the normal budget cycle. That internal model stops working once the divested unit shares something more with the rest of the group. That includes enterprise systems, global vendor agreements or cross-border shared service centres.