Share
A company splits in two. Payroll moves. Everything else was supposed to move with it.
It did not. Benefit deductions transferred, but the benefit plans behind them did not. Onboarding templates were never rebuilt at the new entity, so new hires got no onboarding at all. An earned wage access provider was never told a new company code existed, and employees lost access to their own earned pay for two weeks. None of this was one big failure. It was a dozen small handoffs that assumed someone else had already covered them.
Last updated: September 2026
An entity change moves the legal structure, not the configuration behind it
A 656-employee restaurant group went through exactly this. Deductions moved to the new company code. The underlying plans did not, so the day after go-live, HR discovered every benefit needed to be rebuilt from scratch on a call with the carrier. Separately, nobody had told the earned wage access vendor a new company code existed, so a scheduled advance simply did not process. It took two weeks and a manually rebuilt transfer file to fix, during which employees who relied on that access had none.
The HR lead put it plainly afterward: the migration should have been tested before anyone went live, not discovered by the people it broke.
New hires after the cutover inherited nothing
Onboarding tasks and templates were never mirrored to the new entity, so every employee hired after the split date received no onboarding tasks at all. Outstanding I-9 verifications that existed before the split simply disappeared from the queue. HR only caught it because someone happened to pull a weekly report and noticed the gap. Reassigning fourteen tasks across more than thirty employees, one at a time, took several hours that nobody had budgeted for.
A similar story played out at a US entity being carved out of a global manufacturing group. The parent’s HRIS team in another country was making integration decisions for a domestic payroll problem, on a deadline that landed in the middle of open enrollment. One HR business partner was covering two entities with no additional headcount to absorb the work.
Acquisitions carry a version of the same risk in reverse
A real estate company that changed entities mid-year ended up with six months of pay history under the old name and six months under the new one, with employees from the old entity never formally closed out. Every search for an employee returned two records. The office manager’s stated fear was being billed for what looked like a hundred and fifty percent of his actual headcount, because the system had no way to show him it was the same person twice.
A hotel group acquiring properties runs into the mirror image: every new property has a different bank account and a different ownership structure, and payroll funding has to be configured before the first payroll, often inside a ten-day window. Missing the approval call from the vendor’s banking team means starting the setup over.
What to confirm before, not after, the entity changes
- Benefit plans, not just deductions — confirm the plan itself exists at the new entity before the first payroll runs there
- Every downstream provider, including earned wage access, 401(k) recordkeepers, and workers’ compensation carriers, needs the new company code before go-live, not after
- Onboarding templates and outstanding tasks — confirm they were copied to the new entity, not just the employee records
- A closed-out old entity so terminated or transferred employees do not appear as active headcount under two names
- Bank funding setup at the new entity, tested with a real payroll before it becomes the only payroll
The Department of Labor treats successor employer status as a factual question with real compliance consequences for unemployment tax rates and benefit continuity, which is one more reason to get the paperwork right at the moment of the change rather than reconstructing it later.
The fix is testing the handoff, not adding more people to watch it
None of the businesses above lacked capable HR staff. What they lacked was a single system where payroll, benefits, and onboarding share one employee record, so an entity change updates all three at once instead of requiring someone to remember every downstream system that needs a phone call.
When those pieces live separately, a split or acquisition becomes a checklist that depends on one person’s memory. When they live together, moving an employee’s company code moves their benefits, their onboarding status, and their pay history with it.
Frequently Asked Questions
Benefit plan setup, onboarding templates, and any downstream integration such as earned wage access or a 401(k) recordkeeper are the most commonly missed items. Payroll and basic deductions usually transfer correctly, but the systems that depend on the old company code often are not updated.
Plan for at least the length of one full payroll cycle before the change, so the new configuration can be tested against a real payroll before it becomes the only option. Acquisitions with new bank funding can require a ten-day setup window or longer.
This depends on how the migration is handled. Done poorly, the employee ends up with two separate records and two years of pay history split across them, which can look like duplicate headcount. Done correctly, the employee record carries forward under the same identity.
Every provider connected to that company code, including benefits carriers, retirement plan recordkeepers, workers’ compensation insurers, and earned wage access vendors. Missing even one can interrupt something an employee depends on, like same-day pay access.
Ready to Make Entity Changes Boring Instead of Risky?
See how Netchex keeps payroll, benefits, and onboarding on one employee record through a split, sale, or acquisition.
This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.
Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.
