Part of the Private equity and the finance function series.
A carve-out does not separate one finance function from another - in most cases it reveals that the carved-out entity never had a finance function of its own at all. It lived on the parent's ERP, the parent's shared-service centre, the parent's chart of accounts, and the parent's month-end calendar. Day one changes the ownership line; it does not conjure systems, people or processes into existence.
What does a carved-out group actually inherit on day one?
On day one, the carved-out group inherits its legal obligations and very little else in finance terms. What it does not inherit is a finance stack: no consolidation tool, no planning and budgeting environment, no statutory reporting workflow, and frequently no finance team with direct experience of running those processes end-to-end - because those processes were always handled centrally or upstream. The entity was a reporting unit, not an independent office of the CFO. That distinction matters enormously when the clock starts.
Is the transitional service agreement a solution?
A transitional service agreement is a deadline, not a solution. It gives the carved-out group continued access to the parent's systems and people for a defined period, and the temptation is to treat that period as breathing space. It is not. Every month of TSA dependency is a month in which the new entity is not building its own capability - and TSA exit is rarely extended without cost or political friction. What tends to be underestimated in TSA scope is the granularity of what the parent was actually doing: not just running an ERP but managing the period-end timetable, owning the intercompany eliminations logic, producing the statutory packs, filing the VAT returns, and maintaining the data mappings that make consolidated reporting possible. When carve-out teams list TSA items, they list the headlines. The detail - the hundreds of micro-processes embedded in shared services - tends to surface only when the TSA is exiting and those processes have no owner on the new side.
What sequence has to hold?
The non-negotiable sequence is: statutory obligations first, a close that runs second, then the reporting the new owner wants. Statutory obligations - filing deadlines, audit readiness, payroll, tax - carry legal consequence. They cannot wait for the new owner's management reporting format to be agreed. A close that runs means the entity can produce a set of numbers on a predictable timetable, even if those numbers are produced manually and the process is far from elegant. Only once those two things are stable does it make sense to invest in the reporting layer - the consolidated view, the KPI pack, the board dashboard - that the acquirer or new ownership structure requires. Groups that invert this sequence, prioritising the reporting the new owner wants before the underlying close is reliable, build an attractive façade on an unstable foundation. The first audit finds it.
Why is copying the parent's finance function the wrong instinct?
The instinct to rebuild the parent's finance function in miniature is understandable and usually wrong. The parent's finance stack was designed for the parent's scale, structure and reporting obligations. It was almost certainly over-engineered for what is now a standalone entity of smaller size and simpler structure. Replicating it introduces cost, complexity and implementation risk that the carved-out group does not need - particularly during the period when it is also managing TSA exit and standing up statutory processes simultaneously. The better instinct is to ask what the minimum viable finance function looks like for this entity's actual obligations: how many ledgers, how many legal entities, how many currencies, what reporting standard. Start from those constraints and build forward, rather than starting from the parent's architecture and stripping back.
What does a practical day-one readiness sequence look like?
Before TSA exit, the carved-out group needs to have answered four questions in order. First: which statutory obligations fall due in the next twelve months and who owns each one on the new side? Second: what is the minimum close process - people, system access, timetable - that will produce a set of numbers the auditors can rely on? Third: what data does the new owner need, in what format, and by when - and is that ask compatible with the close process that exists, or does the close process need to change first? Fourth: what is the target-state finance model for this entity at steady state, and how does the build sequence get there without disrupting the first three? That fourth question is where the Maturity Matrix is useful: rating each area of the office of the CFO - planning and budgeting, month-end close, consolidation, forecasting, statutory reporting - honestly against the 1-to-5 scale from Manual to AI-embedded, and then treating the gap not as an aspiration but as a costed build sequence.
Where does the Finance Value Score fit?
Finance Value Score gives the carved-out finance leader one honest number - a 0-100 score - that reflects where the function stands across every coverage area, and a business case that costs the gap to the level-5 frontier in pounds. For a group standing up a finance function from scratch, that score is a baseline: it makes the build sequence visible, it quantifies the value at stake from closing specific gaps, and it produces a board-ready output that a new owner can read without a briefing. The score is the headline; the pounds are the point.
Common questions
What is the most common gap discovered in a finance carve-out?
The most common gap is that the carved-out entity had no independent finance function - it relied entirely on the parent's ERP, shared services and close processes. On day one it has legal obligations but no infrastructure to meet them. The TSA provides temporary access to the parent's systems but does not transfer capability.
How should a carved-out group prioritise its finance build?
The correct sequence is statutory obligations first, a reliable close process second, and management or owner reporting third. Inverting that sequence - building the reporting layer before the close is stable - creates a presentable facade over an unreliable foundation that the first audit will expose.
What is a transitional service agreement in a carve-out context?
A transitional service agreement (TSA) is a contractual arrangement allowing the carved-out entity to continue using the parent's systems and services for a defined period after separation. It is a deadline, not a solution: every month of TSA dependency is time not spent building independent capability, and the scope of what the parent was actually doing is routinely underestimated when the TSA is drafted.
Why is replicating the parent's finance function a mistake in a carve-out?
The parent's finance stack was designed for the parent's scale and complexity, which almost always exceeds that of the newly independent entity. Replicating it imports unnecessary cost, implementation risk and operational complexity at exactly the moment the carved-out group is also managing TSA exit and standing up statutory processes. The right approach is to design for the entity's actual obligations, then build forward.
What should a carve-out finance leader know about TSA scope?
TSA scope is routinely underestimated because carve-out teams list the headline services - ERP access, payroll processing - but miss the hundreds of micro-processes embedded in shared services: period-end timetabling, intercompany eliminations logic, data mapping, VAT filing and audit pack production. These surface as gaps only when TSA exit approaches and they have no owner on the new side.