CPA Firm Mergers: A Retirement Plan Due-Diligence Checklist
Treat retirement plans as a defined merger workstream: identify the plans, people, entities, documents, and decisions before integration.
For related planning context, see 401(k) Due Diligence in Mergers and Acquisitions: A Buyer’s Checklist.
A CPA firm merger can change the facts that support retirement-plan administration, so due diligence should start before the closing checklist is final.
The key is to turn merger timing, entity structure, and participant records into a documented retirement-plan question early enough to make an orderly decision. In a CPA firm, titles, invoices, payroll labels, and ownership language can sound decisive while the governing facts are more nuanced. A useful review begins by separating what happened in the business from what the plan document says to do.
At a glance
- Core question: Which workforce and entity facts affect the plan decision?
- Focus: merger timing, entity structure, and participant records.
- Reading path: define the facts, compare them with the document, then implement and review.
Define the planning question
IRS materials explain that controlled and affiliated service group rules can require employees of related organizations to be treated together for certain retirement-plan purposes.[1] ERISA provides minimum standards for most voluntary private-industry retirement plans and assigns fiduciary responsibilities to those managing plan assets.[2] This is why a clean eligibility or funding review starts with a census and source records rather than a verbal description of the firm.
For this purpose, create a working file that identifies each person, the legal entity paying that person, start and end dates, service history, ownership interests, and the plan status being evaluated. Add the plan’s adoption agreement, amendments, payroll definitions, and prior administrative decisions. The exercise is not meant to turn managers into lawyers; it makes the adviser’s analysis faster and prevents a decision based on incomplete facts.
Compare the facts with the written plan
| Review lens | Question to ask | Useful record |
|---|---|---|
| People | Who is performing services and for which entity? | Census and payroll history |
| Plan terms | What do eligibility, compensation, and entry provisions say? | Signed plan document and amendments |
| Operations | Has administration followed those terms consistently? | Provider reports and communications |
The comparison should highlight differences, not force a premature conclusion. A role may be operationally similar to another role but have a different employment, ownership, or service pattern. Conversely, a new title does not automatically create a new plan category. Record the uncertainty and ask the plan’s counsel, administrator, or actuary to resolve it under the actual documents.
A sensible cadence is to update this file at a predictable business event—such as a partner transition, merger milestone, hiring season, or project closeout—and again before an annual filing or contribution decision. That creates a repeatable control rather than a scramble.
Before the meeting ends, identify both the next fact to confirm and the person responsible for confirming it. This small discipline avoids an analysis that becomes stale while the business event is still unfolding. It also gives decision-makers a clear line between documented facts, reasonable assumptions, and issues that need professional interpretation.
Good governance also means preserving the comparison, even if no change is made. Note the date reviewed, the records used, the people consulted, and why the present administration was retained or changed. A future administrator can then understand the basis for the decision instead of reconstructing it from emails and memory. That record is especially useful when the business grows quickly or the same issue returns in a later plan year.
Finally, distinguish business preference from plan administration. Leaders may prefer a fast answer for budgeting, recruiting, or transaction timing. The file should state that preference, but it should not replace the factual and document review. A clear separation helps the eventual decision remain explainable to participants, advisers, and future owners.
Implement a controlled process
Preserve plan documents, amendments, Form 5500 records, census files, service-provider contracts, and documented decisions as part of the deal record. Assign a business owner for the census and a separate reviewer for plan terms. The owner should preserve the dates and source documents used; the reviewer should record the decision, any assumptions, and the professional advice requested. This protects continuity when the finance lead, office manager, or outside provider changes.
Decision flow
- Set scope: define the requirement, scope, timing, and decision owner.
- Check evidence: check documents, reports, controls, and open exceptions.
- Assign action: assign the approved action, deadline, and accountable owner.
- Revisit: revisit evidence, changes, and unresolved exposure.
Define the workforce and entity facts. Compare them with plan terms. Implement the approved action. Review after the next business change.
Practical implementation table
| Step | Owner | Evidence to retain |
|---|---|---|
| Refresh census and entity map | Operations or payroll | Effective dates and source reports |
| Read operative plan terms | Plan administrator | Document version and amendments |
| Obtain technical review | Benefits counsel, CPA, or actuary | Questions and written conclusion |
| Carry out and monitor | Named business owner | Notices, elections, and follow-up date |
Review tradeoffs before acting
The fastest operational answer is not always the most durable one. A narrow change can reduce immediate cost or administrative effort but may produce later corrections if the participant group, compensation definition, or related-entity facts were misunderstood. A broader review takes more time, yet it can reveal conflicts before notices, contributions, or funding assumptions are finalized. Choose the path that matches the quality of the records and the materiality of the decision.
Keep employee communication separate from the technical analysis. Staff need timely, plain-language notice of changes that affect them, while the internal file should retain the legal and actuarial reasoning. Do not promise a tax result, benefit level, eligibility outcome, or funding result until the applicable professionals have reviewed the facts and governing documents.
Set a dated review reminder as part of implementation. The reminder should name the event that would reopen the analysis, such as a new entity, a change in ownership, a material staffing shift, or the next plan year. A documented follow-up is more reliable than assuming the original conclusion will remain correct indefinitely.
Editorial disclaimer: This article is general educational information, not legal, tax, investment, actuarial, or ERISA advice. Retirement-plan outcomes depend on the plan document, current law, and specific facts. Consult qualified counsel, a tax professional, and—where appropriate—an actuary or plan administrator before acting.
References
- [1] https://www.irs.gov/pub/irs-tege/epchd704.pdf
- [2] https://www.dol.gov/general/topic/retirement/erisa
- Supporting source: https://www.irs.gov/publications/p560