Running a salary hike cycle without guesswork

Published 2 August 2026 · Updated 10 August 2026 · Merik team · 6 min read

A salary hike cycle is the annual or half-yearly process of reviewing and revising employee compensation. Done well it has four stages: set the budget pot, allocate it against evidence, fix effective dates and arrears, then record the revision so the history stays intact. Small businesses usually get stages one and two roughly right and stages three and four badly wrong — which is why arrears go missing and nobody can reconstruct why someone earns what they earn.

Stage 1 — Set the pot before you look at names

The failure mode is universal: managers propose increments person by person, HR adds them up in March, and the total is 14% of payroll against an intended 8%. Then someone has to go back and cut, which is worse for morale than a smaller pot honestly communicated up front.

Do it the other way round. Start from your annual payroll cost, decide what percentage of it you can commit to permanently — remember an increment is a recurring cost, not a one-time payment — and split the pot into buckets before any individual number is discussed:

• Merit pool — the main bucket, distributed by performance.
• Market correction pool — for roles where you are demonstrably below market and at risk.
• Promotion pool — for role changes, kept separate because a promotion is a different decision from a raise.
• Reserve — 10–15% held back for the cases you will not anticipate. You will need it.

Stage 2 — Allocate against evidence, not impressions

Distributing the merit pool by recollection favours whoever was visible in the last six weeks. If you have been running structured reviews, you already have a better basis — and if those reviews are grounded in logged work rather than memory, better still. A 20-minute monthly review process is described here, and the reason it matters at increment time is exactly this: twelve short monthly records beat one annual reconstruction.

Useful evidence, in rough order of reliability:

• Documented review outcomes across the period, not just the most recent one.
• Delivery record against commitments — what was logged, completed and shipped.
• Scope change: is this person doing materially more than they were a year ago?
• Retention risk, assessed honestly and separately from performance.

Write one sentence of justification per person. If you cannot write it, the number is not ready.

Stage 3 — Decide what changes inside the salary structure

A hike is not just a bigger number; it is a change to a structure. Decide:

• Does basic change proportionally? Basic drives statutory calculations, so raising it raises provident fund contributions too — which affects both employer cost and employee take-home. A 10% CTC rise with a flat basic and a bigger special allowance costs less and feels different to the employee.
• Which components absorb the increase? Loading everything into special allowance is common but leaves the structure increasingly lopsided over years.
• Is any part variable? Splitting a rise into fixed and performance-linked components changes the risk profile for both sides — and must be explained clearly, or it will be heard as a smaller raise.

How CTC translates into monthly take-home is worth re-reading before you communicate, because the number that matters to the employee is the one at the bottom of the payslip, not the one in the letter.

Stage 4 — Effective dates and arrears

This is the stage that generates the most avoidable mess. Three separate dates exist and are often conflated:

• The effective date — when the new salary starts applying.
• The decision date — when you finalised it.
• The first revised payslip date — the payroll run that first reflects it.

If the effective date is 1 April but the decision lands on 20 June, the employee is owed arrears for April, May and June at the difference between old and new pay. Arrears must appear as a separate, clearly labelled payslip line — "Arrears (Apr–Jun)" — never folded into the month's earnings, or the employee will think their new monthly salary is far higher than it is and be disappointed the following month.

Arrears are simple arithmetic that goes wrong constantly, because the calculation happens once and nobody checks it. Compute it as (new monthly gross − old monthly gross) × months elapsed, adjusted for any LOP days in those months.

Those LOP adjustments matter: if someone had unpaid days in May, their arrears for May are proportionally lower. The per-day arithmetic is here.

Stage 5 — Record it as history, not as an overwrite

The most damaging small habit in small-business HR: opening the employee record and typing the new CTC over the old one. It takes two seconds and erases the answer to every question you will later be asked — what were they on before, from when, and why did it change?

Keep a dated revision history per employee: previous CTC, new CTC, effective date, reason, approver. This gives you, at no extra effort:

• Correct arrears calculations, because the old figure and its date still exist.
• The ability to answer "when was she last revised?" without archaeology.
• A defensible basis if a revision is ever disputed.
• Accurate historical payroll — a payslip from before the revision still reconciles.

Stage 6 — Communicate it properly

A revision letter should state, in this order: the new annual CTC, the effective date, the revised component structure, the expected monthly take-home (approximate is fine — say so), when the first revised payslip will arrive, and whether arrears are due and in which run.

Two practical notes. First, deliver revisions to everyone in a tight window; staggered communication over two weeks turns into corridor comparison and speculation. Second, when someone receives no increase, say so directly with a reason. Silence is heard as an oversight, and the conversation you avoid in April becomes a resignation in July.

The stored CTC history is also what a gratuity calculation depends on years later.

Quick reference

Cycle stages	Set the pot → allocate on evidence → fix structure → set effective date and arrears → record history → communicate
Pot rule	Decide the total percentage of payroll first; allocating individually always overshoots
Recommended reserve	10–15% of the pot, held back for unanticipated cases
Three dates to keep separate	Effective date · decision date · first revised payslip date
Arrears formula	(New monthly gross − old monthly gross) × months elapsed, adjusted for LOP days
Arrears on the payslip	A separate labelled line — e.g. "Arrears (Apr–Jun)" — never merged into earnings
Record keeping	Dated CTC history per employee: old value, new value, effective date, reason, approver

Frequently asked questions

How Merik handles it

Merik keeps salary as a history rather than a single editable field. Each revision is recorded with its own effective date, so the CTC that applied in May is still the CTC that May's payroll used — which is what makes arrears calculable and old payslips reconcilable. The effective CTC for any month is resolved from that history rather than from whatever value happens to be current.

Because payroll reads the same records, a revision applied with a back-dated effective date is visible where you need it, and the monthly run continues to compute server-side from attendance and the salary in force. Monthly performance reviews live in the same workspace, so the evidence you allocate increments against is the record your managers already maintain. See salary and payroll modules, the feature list, or how it works.

Create your workspace →

Or talk to us about your team →