Two companies merge. Leadership is aligned. Everyone's fired up. And then, almost immediately after close, the ‘pay related noise’ starts.

What do we do about job levels? Bonus eligibility? Are we keeping both structures or picking one?

Comp in an M&A tends to be more involved than it looks on the surface. You're not just reconciling two sets of salary bands – you're reconciling two entirely different philosophies, how performance gets rewarded, and what a title like "Head of" actually means.

We've seen this same pattern across clients of all sizes – from first-time acquisitions to complex multi-entity integrations. Here's what we've learned and what you can do about it.

The Bonus Problem Is Usually a Leveling Problem in Disguise

In a recent integration, the surface-level issue looked like a bonus misalignment. Different eligibility rules, different target amounts, one company offering bonuses company-wide while the other didn't. Someone had to reconcile all of it – and Finance was holding their breath about what "evening it out" might cost.

But before you can have a conversation about the combined bonus program, there's almost always a more foundational problem to solve first. 

One or both organizations have inconsistent titles and job levels. A "Director" at one company carried a scope of responsibility that looked nothing like a "Director" at the other. One org was top-heavy; the other ran lean. You can't build a solid bonus program on top of that. Fix the foundation first.

Where to start: Align on levels before aligning on pay

Conduct a job leveling audit across both companies before you touch the bonus program.

• Pull all titles from both orgs and organize them by job family and level. Before anything else, you need to see the full picture in one place.
• Ask the hard question for every role: Does this title represent equivalent scope, accountability, and impact across both companies, or are we just assuming it does?
• Flag the outliers including inflated titles, roles lacking clarity, and levels that do not map cleanly to either legacy structure.
• Schedule working sessions with the relevant functional leaders to talk through the flagged roles. Some will be quick wins, a title cleanup or a level adjustment that everyone can agree on quickly.
• Make a decision on every outlier. Others will require a harder conversation about what the role actually needs to be in the combined org, and whether the current scope still makes sense. Either way, get to a decision. Unresolved outliers will become contentious comp cases later.
• Build a shared leveling framework that both sides of the combined org can agree on. Everything comp related, including the bonus conversation Finance is waiting on, gets built on top of that.

Why Leveling Has to Come Before Anything Else

Job leveling is the foundation. Without it, you can't cost model the bonus program and you can't make defensible pay decisions. It's the work that feels like it might slow things down – but it's actually what makes everything else move faster.

When we've done this with clients, it meant working directly with leaders across both organizations to revisit career paths, redefine what each level actually required, and build a framework both sides could stand behind.

These conversations aren't always easy. Some leaders were found trying to inflate levels. But most had never thought about their org structure in those terms before and found the exercise genuinely useful and helped them make more thoughtful hiring and promotion decisions going forward. By the end, there was a shared language across the org. That turned out to matter more than people expected. Finance could finally model costs. Recruiters had clearer guardrails. HRBPs had something to point to.

And once the leveling was solid, instead of debating whose bonus program was "better," we were able to focus on the data clearly – where there were gaps, and what a fair, competitive, unified approach actually looked like for the combined org.

What to do: Get both sides in the room

• Run leveling work sessions with functional leaders from both companies. This is not a solo HR exercise. It requires the people who actually own the roles to be part of the conversation.
• Use a clear set of compensable factors to evaluate roles consistently across both organizations, including scope of decision making, people leadership, accountability, and degree of independent work.
• Pressure-test career paths by job family while you are already in those sessions. For each job family flesh out the growth opportunities for employees. 
• Make sure every level and title reflects a real business need for the next two to three years, not just what existed before the deal closed.

How to Approach the Bonus Program Once Leveling is Done

With a shared leveling framework in place, the bonus audit becomes a structured exercise rather than a political negotiation.

Start by documenting both incentive structures side-by-side: eligibility requirements, target percentages or flat dollar amounts by level, performance metrics, and payout timing. Then ask a few key questions for each element: Is this aligned with what the combined company is trying to accomplish? How does it compare to the market? Does it actually drive the behaviors you want? And is maintaining two parallel structures for a bit longer a reasonable bridge while you plan the transition?

Sustaining two structures short-term is sometimes the right call – but it needs a clear end date and a communication plan. Sprinkling changes out over time without a coordinated approach creates confusion. When employees start comparing notes with peers and the logic isn't clear, perceived unfairness sets in fast.

What’s next: Anchor bonus targets to levels, not legacy

• Use the leveling framework to anchor bonus targets to confirmed levels. If a role is leveled as a Manager in the combined org, the bonus target should reflect that, regardless of what the person was called or paid before.
• Set a harmonization timeline of ideally no longer than 12 months and plan the sequencing thoughtfully. Not everything needs to happen at once, but everything needs a deadline.
• For employees with below-market base salaries, consider whether reallocating some or all of the bonus into base makes more sense, especially if the bonus is not meaningfully driving behavior anyway.
• For employees gaining bonus eligibility for the first time, tie it to a natural moment such as a promotion, a performance review, or a comp review cycle, so it feels intentional rather than arbitrary.
• When you are ready to communicate changes, batch them. Staggered announcements create confusion and comparison. One clear message, at the right time, lands better.

The Comp Cycle No One Dreaded

When it came time to run the first combined comp review cycle, this client expected it to be painful. New process, two legacy cultures, managers making decisions across an org they were still getting to know. Instead, it just worked.

Because those managers had already been through the leveling work, they walked into the comp cycle knowing exactly where the market data came from, how roles had been structured, and what the guardrails were. We ran training sessions so decision-makers felt confident with their pay decisions. Our manager approval workflow gave the whole process structure without making it feel bureaucratic.

Next steps: Calibrate before you delegate

• Don’t assume managers know how to make pay decisions just because they have done it before. The combined org is new territory, and this cycle will surface gaps quickly if people are not prepared.
• Before the cycle opens, run a calibration session walking managers through where the market data comes from, what the budget parameters are, and what good pay decisions factor in.
• Use concrete examples and hypotheticals to make the training stick. For example: if you have two people at the same level and one is at the midpoint and one is above it, here is how to think about that.
• Build in a People team review layer before anything is finalized, where decisions get reviewed for internal equity before they are communicated to employees.

A Practical Timeline for People Leaders

Every deal is different, but here's a sequencing that works across most M&A integrations:

• Pre-close (if you have access): Map titles and levels across both orgs. Identify the biggest misalignments and flag roles that will need the most work. The earlier you can see the gap, the better positioned you are on Day 1.
• Days 1 to 60: Prioritize leveling worksessions with leaders. Get agreement on the framework before you need to make any individual decisions with it. Start communicating the process and timeline to other management team members, then employees – you don't need all the answers yet, you just need people to know there's a plan.
• Days 60 to 120: Run the comp audit using the leveling framework as the anchor. Identify gaps, overlaps, and equity issues. Build the business case for the unified comp strategy and start the Finance conversation with actual data.
• Days 120 to 180: Train managers. Stand up the review and approval process. Communicate any pay changes to employees with enough lead time to feel thoughtful, not reactive. Batch pay changes and respective communications wherever possible.
• Days 180 to 240: Target a fully unified incentive structure. Review the leveling framework against market data and adjust if needed now that the combined org has had time to stabilize.

The Takeaway

Job leveling is the part that makes everything else work in compensation.

If you're heading into an M&A and comp is on your list, don't start with the bonus structure. Start with the question underneath it: do we actually know how each role is leveled and how that connects to how we pay people?

Get that right, and the rest gets so much easier. Skip it, and you'll be back at the drawing board in 12 months wondering why the compensation strategy isn't landing – and when you go back to Finance for the budget to fix it, don't expect a warm reception.