Why Most Post-Carve-Out Finance Functions Break (and How to Fix Them)

When a company is carved out of a larger organization, the assumption is that finance will “stand up” quickly.

In reality, that almost never happens.

Post-carve-out accounting cleanup is where most teams get stuck. What you’re left with is a version of the truth that technically exists—but doesn’t hold up under pressure:

• Numbers don’t tie across systems

• Intercompany is inconsistent or incomplete

• ERP and consolidation tools don’t align

• Audit adjustments live in spreadsheets instead of the system

I’ve been in the middle of this recently with a PE-backed, multi-entity environment. The systems were live. Reporting existed. But underneath, there was a lot of noise, manual workarounds, and risk.

Here’s what actually breaks, and how to fix it.

The Real Problem Isn’t the ERP, It’s the "Bridge" Between Systems

Most teams assume the issue is the ERP.

It’s not.

The real issue is the translation layer between systems:

Legacy ERP → consolidation tool (Planful, Workday, etc.)

Project/job data → financial reporting

Operational activity → accounting classification

This is where things fall apart:

1. Accounts don’t map cleanly

2. Cost classifications drift (COGS vs G&A)

3. Project-level detail doesn’t tie to financials

4. WIP and revenue recognition aren’t aligned

You end up with reporting that looks right at a high level, but doesn’t reconcile when you dig in.

Step 1: Fix Mapping Before You Touch Anything Else

If mapping is off, everything downstream is wrong.

Start here:

• Build a clean translation table between the legacy ERP and the consolidation system

• Align accounts to consistent categories (Revenue, COGS, G&A)

• Standardize how indirect costs are treated (this is almost always inconsistent)

One common issue:

Indirect costs split between COGS and G&A

Align the mapping. Lock it. Enforce it. Across ALL subsidiaries.

Until you do that, your gross margin and EBITDA will remain inconsistent.

Step 2: Rebuild Intercompany and Eliminations Logic

This is where most post-carve-out environments quietly break.

Typical issues:

• Intercompany entries don’t match between entities

• Eliminations are manual or incomplete

• Timing differences create noise every month

Fix:

• Define clear intercompany rules (who books what, when)

• Centralize elimination logic

• Use dedicated elimination entities/accounts instead of ad hoc entries

If you don’t do this, consolidation will always require manual cleanup—and audit risk stays high.

Step 3: Get Project-Level Reporting to Actually Tie

For EPC / construction / project-based businesses, this is critical.

What usually happens:

• Financials are right at the total level

• Project-level reporting is incomplete or unmapped

• Variance analysis becomes meaningless

Fix:

• Map revenue and costs by project/job in the system

• Ensure WIP is aligned to those same project codes

• Eliminate “unmapped” buckets

Once this is clean, something powerful happens: Variances actually explain themselves

Before that, you’re guessing.

Step 4: Pull Audit Adjustments Into the System (Not Excel)

This one gets ignored, creating long-term problems.

Most teams:

• Track audit adjustments in Excel

• Roll them forward manually

• Never fully integrate them into the books

Instead:

• Post adjustments directly into the system

• Separate operational vs audit-driven entries

• Build a clean rollforward process

This is the difference between:

• “We survived audit.”

  vs

• “We’re following and applying the right audit guidance.”

Step 5: Normalize What “Good” Looks Like

At some point, you need to define the target state:

• What should EBITDA include vs exclude?

• How are taxes treated across entities?

• What does “final” reporting actually mean?

In one case, we had:

• Internal EBITDA excluding certain taxes (lender vs. reportable)

• System reporting including them

• Forecast vs actual not comparable

Fixing that alignment alone changed how leadership viewed performance.

What Actually Changes When You Do This Right

Once the foundation is fixed:

• Reporting becomes consistent across systems

• Variance analysis becomes real, not narrative

• Audit becomes faster and cleaner

• Finance stops reacting—and starts leading

Most importantly: Leadership trusts the numbers again!

Final Thought

Post-carve-out finance issues aren’t usually caused by one big failure.

They’re caused by a series of small inconsistencies across systems, processes, and assumptions.

Fixing it isn’t about adding more reporting.

It’s about:

• Cleaning the structure

• Aligning the logic

• And making the system reflect how the business actually operates

That’s what turns a “functioning” finance team into a reliable one.