The deal closes. Then somebody asks who runs payroll on Monday.
A spin-off, divestiture or carve-out leaves a company that has never owned its own HR, payroll or ERP suddenly having to, on a date it did not choose, using systems that belong to somebody else. I run that program: the separation itself, the standalone platform underneath it, and the sequencing that gets you to a first pay cycle nobody notices.
Every separation runs on the same clock.
The corporate structure differs. The problem underneath does not: a fixed date, a former parent whose goodwill is on a timer, and a payroll that cannot miss.
A business unit becoming its own public company. It inherits people, contracts and obligations, but not the systems that ran them. Everything has to stand up standalone before the transition services agreement expires.
A unit sold to a buyer or a private equity sponsor. Employees transfer, data has to be split cleanly along a line that was never designed to be split, and two sets of lawyers care exactly where it falls.
A piece of the business separated onto its own instance while still sitting inside the group. All of the separation work, none of the clean break, and shared services that have to be untangled without stopping.
How I run a separation.
A separation is two programs against one deadline: the new platform, and the unwinding. The second one is where these get lost, because it is nobody's obvious job. Five things decide whether you reach a clean first pay cycle.
Build the separation matrix first
Before anything else, go application by application and department by department and answer the unglamorous questions. What access to the parent's systems continues past the separation date, and until when. What data and reports must be pulled before the cutoff, and who owns pulling them. What happens to historical payroll and check history. Who at the parent fields an ad hoc request afterward, and under what arrangement. Which records carry a retention obligation that outlives the relationship. Read together, the answers are an unsentimental inventory of everything the parent quietly did for you that nobody wrote down. Programs that skip this discover the list one emergency at a time.
Treat the date as contractual, not aspirational
A normal program that runs late negotiates a new date. A separation program that runs late is a breach, or an expensive extension paid to the company you are trying to leave. That inverts how you plan. Scope becomes the only lever, so decisions get forced early and on the record, and the steering committee's real job is to cut scope quickly rather than to admire status reports.
Spend the parent's goodwill early
Every request for data, access or support goes to an organization that is itself reorganizing, with its own priorities and its own people heading for the exits. Goodwill is real but finite, and it decays as the date approaches. Anything you need from them, you need while they still have the staff who know where it is. The last month of a transition services agreement is the worst possible time to discover a dependency.
Prove payroll in parallel before you retire anything
The only acceptable evidence that a new payroll works is that it produces the same answers as the old one, on real data, before the old one goes away. That means genuine parallel cycles with reconciliation, not a demo. It also means the downstream feeds get proven at the same time: retirement providers, health carriers, employment verification, general ledger. Each has its own file format and its own idea of a valid record, and each one fails quietly.
Aim for an uneventful first Friday
The measure of a separation is not the go-live date. It is that on the first ordinary pay cycle afterward, people are paid the right amount, deductions are right, the feeds land, and nobody outside the program notices anything happened. Payroll is unforgiving in a way most enterprise systems are not: everyone finds out at once, and in a business with union agreements a bad first cycle stops being an IT problem and becomes a labor problem.
Read the case study: a cable network group cut loose from its parent's payroll →
Facing a separation?
Spin-off, divestiture or carve-out, the clock is contractual and the first pay cycle is the exam. Put someone on your side of the table who has done it before, while there is still room to move.