Can you run a merit cycle in Excel?

Yes, and plenty of organizations do it well. Below roughly 300 employees with a handful of managers and one budget pool, a spreadsheet is a legitimate tool. The trouble starts when the number of managers grows, because a spreadsheet cycle scales by adding files — one per planner — and every file added is another thing to distribute, chase, and reconcile.

At what size do spreadsheets stop working?

It tracks managers rather than employees. Around 20 planners it is uncomfortable; by 100 or more it is a coordination job of its own. Multiple budget pools, several countries, or a mid-cycle reorganization each pull the threshold lower.

What actually goes wrong most often?

Three things, in order: budget overruns discovered during reconciliation; broken formulas and stale copies producing increases nobody intended; and pay gaps that widen because two managers applied the same policy differently and nothing compared them.

Is switching worth it if we only run merit once a year?

That is precisely the case for switching. A process you run once a year is one nobody stays fluent in — the spreadsheet is rebuilt from memory every January, and last year’s fixes are re-learned. Software keeps the configuration between cycles so year two starts where year one finished.

What about the merit module we already own in our HRIS?

It solves workflow, not modeling. Most teams still export to Excel to allocate budgets and correct pay gaps, then load the results back in — so they own a merit module and still run a spreadsheet cycle. That round trip is what HyperEquity removes.

Comparison

Spreadsheets do not fail at merit. They fail at scale.

An honest look at where the spreadsheet cycle actually breaks, what it costs when it does, and the point at which replacing it pays for itself.

Try It Free

Side By Side

The same four employees, twice

The spreadsheet way3+ weeks

Merit_v7Merit_v7_FINALOpsSalesR&D+19

Employee	Rating	Salary	Incr.
A. Rivera	Exceeds	$92,400	4.0%
J. ChenSame role, half the increase	Exceeds	$91,800	2.0%
M. OkaforBroken formula	Meets	$78,200	#REF!
S. PatelOverpaid, still raised	Below	$84,000	3.5%

Budget: $1,041,880 allocated of $1,000,000 — over by $41,880

The HyperEquity way10 seconds

One cycle. Every manager.

Employee	Rating	Why	Incr.
A. Rivera	Exceeds	Top performer, below midpoint	5.8%
J. Chen	Exceeds	Gap to A. Rivera closed	5.8%
M. Okafor	Meets	On policy	3.1%
S. Patel	Below	Above range, no increase	0.0%

Budget used$1,000,000 of $1,000,000

To the dollar. Pay gap between Rivera and Chen closed.

In Fairness

Where the spreadsheet is genuinely fine

It is worth saying plainly: if you have 150 employees, five managers, one budget pool, and a compensation philosophy that fits on an index card, Excel is a perfectly reasonable tool. You do not need software for that, and anyone telling you otherwise is selling.

The spreadsheet does not break because of employee count. It breaks because of manager count. A merit cycle in Excel scales by adding one workbook per planner — so 20 managers means 20 files to build, distribute, chase, collect, and reconcile, and 200 managers means 200. That is not a compensation problem any more. It is a logistics problem wearing a compensation problem's clothes.

Line By Line

What changes when you stop using files

	Spreadsheets	HyperEquity
Spreadsheets per cycle	One per manager. Twenty at 300 employees, two hundred at 2,000.	None. Every manager works in the same live cycle.
Budget allocation	Manual. Split by hand, reconcile by hand, discover the overage at the end.	Automatic, down to the individual, exact to the dollar.
Multiple budget pools	A separate workbook per country or division, reconciled manually.	Set a rate per pool; each allocates independently against its own population.
Pay equity	Invisible unless someone goes looking, and usually a separate project when they do.	Unexplained gaps surfaced and closed inside the merit allocation.
Manager experience	An emailed tab, no guardrails, no live budget, version confusion.	Guided planner, live budget counter, inline policy warnings.
Errors	Broken references, stale copies, and overwrites — often found after approval.	No formulas to break; validation runs before anything is submitted.
Audit trail	Whatever the file history happens to preserve.	Complete record of every change, recommendation, and approval.
Elapsed time	Three weeks or more of coordination for most organizations.	Configuration in a day; recommendations for the whole population in seconds.

The Cost

Three weeks is the visible part

The elapsed time is what everyone counts. It is rarely the expensive part.

The overrun

Allocation by hand across dozens of workbooks reliably lands a few percent off. Finding that at the end of the cycle means clawing back increases managers have already promised.

The gap you did not see

Two people in the same job, same tenure, same rating, thousands of dollars apart. In a spreadsheet nothing compares them, so the gap survives another year and compounds.