How to Prepare Your Payroll for a Business Acquisition or Merger

The LOI is signed. The deal team is focused on financials, legal structure, and integration planning. Payroll is usually an afterthought until Day 1 — when someone realizes that a 300-person workforce needs to get paid in 11 days and nobody has established which system, which EIN, or which bank account the money is coming from.

Payroll integration deserves the same structured attention as any other operational workstream in an acquisition. This guide covers the due diligence checklist, the successor employer election that most buyers miss entirely, the three Day 1 payroll approaches, and how to handle the employee experience through the transition.

Payroll Due Diligence: What to Find Before You Close

The payroll due diligence checklist should be completed before the transaction closes, because the answers affect both deal structure and post-close integration complexity. Request from the target company: complete payroll registers for the past 12 months, all active state and local tax registrations with account numbers, current state unemployment insurance rates and experience rating history, all active garnishment orders and wage assignments, documentation of any pending DOL or state wage investigations, W-2 and 941 filings for the past three years, the current payroll processing schedule and banking setup, all active direct deposit authorizations, and documentation of any deferred compensation, equity, or bonus programs that affect payroll timing.

Common due diligence findings that affect the deal: unregistered states where employees are working, payroll tax deposits that are late or missing, worker misclassification issues (employees paid as contractors), and wage-and-hour liabilities from overtime calculation errors. These aren’t just payroll problems — they’re representations and warranties issues. Find them before close, not after.

The Successor Employer Election: The Financial Decision Most Buyers Miss

When one employer acquires the workforce of another, the IRS successor employer rules affect how FUTA and SUTA wage bases are handled for the year of the acquisition. This decision has a direct, calculable financial impact — and it must be made at or shortly after closing. Most deal teams miss it entirely until post-close reconciliation.

You have two options. The first is to treat the acquired workforce as new hires, resetting wage bases. FUTA applies to the first $7,000 of federal wages per employee per year. If you reset, every acquired employee starts at zero — you pay FUTA on their wages from the acquisition date forward as if they’d just been hired. The second option is to elect successor employer status under IRC Section 3306(b), carrying over wage bases from the predecessor. Acquired employees who had already exceeded the FUTA wage base at the predecessor don’t restart the clock. You pay no additional FUTA on their wages for the remainder of the year.

The financial impact is real. For an acquisition closing in September with 200 employees who each earned $50,000+ at the predecessor: under a wage base reset, all 200 employees restart their FUTA base. At 6% FUTA on the first $7,000 (before state credit), that’s up to $8,400 in additional FUTA liability for Q4 alone. Under the successor election, if those employees already exceeded $7,000 in wages at the predecessor, the Q4 FUTA liability is $0. The wage base carryover value can run $10,000–$100,000+ depending on workforce size and acquisition timing in the calendar year. The election requires the predecessor’s cooperation to provide wage base records and must be properly documented.

Day 1 Payroll: Three Integration Approaches

The Day 1 payroll decision is the most operationally visible aspect of any acquisition. Whatever approach you choose must be decided, communicated, and operational before the first payroll date post-close.

Approach A: Run Parallel Systems Temporarily

The acquired workforce continues on their existing payroll system for one to three payroll cycles while the acquirer configures and validates the new system. Both systems run simultaneously. This works when the acquirer isn’t yet ready to absorb the acquired workforce and when the predecessor’s system can continue operating independently post-close. The key risk: parallel systems mean parallel payroll tax accounts. If the predecessor’s system is using the predecessor’s EIN, tax deposits and 941 filings continue under that EIN — which creates complications if the entity has been dissolved or transferred. Define clearly who is filing what under which EIN before the first pay date.

Approach B: Migrate Immediately on Day 1

The acquired workforce moves to the acquirer’s payroll system on the transaction close date. All payroll processing runs on the new system under the acquirer’s EIN from the start. This works when the payroll system migration is completed before close — which requires significant pre-close preparation — and when the predecessor’s system is being terminated. The risk: mid-year data migration is complex. YTD payroll data, tax withholding history, and wage base information must be imported accurately before the first payroll run. If the migration is incomplete, the first payroll under the new system may be incorrect — which is the worst possible outcome for employee trust in a transition already under scrutiny.

Approach C: Phase by Entity or Location

For acquisitions with multiple locations or legal entities, a phased approach migrates one location or entity at a time, starting with the simplest. This reduces single-point-of-failure risk and lets the integration team learn from the first migration before tackling more complex ones. It’s also the most forgiving approach if the pre-close preparation was compressed — you have time to course-correct before the higher-complexity locations go live.

The Employee Experience: The #1 Post-Acquisition Complaint Is Payroll

Employee surveys of recently acquired workforces consistently identify payroll changes as the top source of post-acquisition dissatisfaction — ahead of leadership changes, culture concerns, and benefit modifications. A wrong first paycheck, a delayed direct deposit during transition, or a benefits deduction that disappears without explanation can undermine the credibility of the entire integration before it’s had a chance to succeed.

Before the first payroll runs under the new system, communicate clearly to all affected employees: what is changing (system, pay stub format, self-service portal), what is not changing (pay rate, pay frequency if maintained, direct deposit if maintained), who to contact if something looks wrong (named contact in HR with direct email and phone, not a generic helpdesk ticket), and a specific timeline for correcting errors. Set a commitment and keep it — “if your check is incorrect, we will issue a correction within [X] business days” means something to an employee wondering if they can cover rent.

Benefit changes are the second most common source of complaints. If health insurance, 401(k), or PTO policies are changing, communicate the specifics, the effective date, and the enrollment process well in advance — not in the same email as general acquisition news. Benefits changes require focused communication with specific actions required from employees. Burying them in a general integration announcement is how enrollment deadlines get missed and employees lose coverage they expected to have.

Netchex’s payroll and HR platform is built to handle mid-year workforce migrations, successor employer configurations, and multi-entity payroll structures — so the integration complexity doesn’t land on your team’s plate all at once. Talk to a Netchex consultant about payroll integration planning before your deal closes.

Frequently Asked Questions

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.

Print this page