The most expensive moment in any HR system isn’t payroll day. It’s the day someone’s salary changes. Get it right and nobody notices. Get it wrong and you’re explaining to an employee why their May payslip is short, why finance booked the raise to the wrong cost centre, or why the new allowance triggered a tax-code change nobody saw coming.
Most companies handle salary amendments in a Slack DM, a spreadsheet, or both. That works until the headcount doubles or the auditor asks why a raise applied two months early. This post covers what a salary amendment workflow needs to survive scale, and how the new salary amendment workflow in Leave Balance handles the parts that usually break.
What a salary amendment actually involves
A salary change is rarely just a number change. It typically involves:
- A proposing manager (or HR business partner) with a reason
- An effective date that may differ from the date approval lands
- One or more approvers — often the manager’s manager, sometimes finance, sometimes the CEO above a threshold
- A downstream payroll update that has to land in the right pay period
- A retroactive adjustment if the effective date is in the past
- An audit record that survives long after the participants leave the company
When any one of those is missing, you get the failure modes everyone has lived through: raises that landed in the wrong month, allowances that doubled because two people approved separately, retroactive top-ups that were paid but never reconciled.
The four rules that make a salary amendment process work
After watching customers run this on tools ranging from Google Sheets to Workday, four rules separate the workflows that hold up from the ones that don’t.
1. Effective date is data, not metadata
Do not treat the effective date as a comment on a Slack message. It is the field that determines which payroll run the change lands in, whether retroactive pay applies, and how the year-end taxable salary line is built. Make it a required, structured field, and let the system compute the rest.
2. Approval chain is parallel to leave, not separate
A company’s “approval chain” is not a per-feature thing. It’s a property of the organisation. The same hierarchy that approves leave should approve salary amendments above a threshold — with optional finance review for amounts past a cap. Two parallel approval systems is one approval system you’ll forget to update when someone changes manager.
3. The payroll handoff is event-driven
When the amendment is approved, the payroll system needs to know — without a human re-keying the value. Whether that’s a webhook to your bundled payroll module, an API call to Xero or KeyPay, or a CSV upload, the integration has to be automatic. Manual re-entry is where 80% of payroll errors originate.
4. The audit record survives the participants
Two years from now, an auditor or a departing employee will ask “when was this raise approved, by whom, and why?” The system that gives the answer cleanly is the one whose audit log is part of the data model, not a Slack scroll-back.
leave emails? Track your employee's leave with Leave Balance
How Leave Balance handles salary amendments
The salary amendment workflow lives in Leave Balance now, not the payroll system. That choice is deliberate — the decision to change someone’s salary is an HR/management decision, while the calculation of how that decision flows through tax and payslip lines is a payroll-engine decision. Splitting those lets each system do what it’s good at.
What you get out of the box:
- Structured request form — current salary, proposed salary, effective date, reason category, free-text justification.
- Approval chain reuse — same chain as leave, with optional thresholds that pull in finance or executive approval automatically.
- Notifications to all stakeholders at each state change — proposed, approved, rejected, effective.
- Webhook to payroll on approval, so the next payroll run applies the new amount automatically. For bundled customers (Nepal), this hits PayrollApp directly. For others, the webhook delivers to the payroll system you’ve configured.
- Retroactive handling — if the effective date is in the past, the system flags the back-pay amount for the next run.
- Immutable audit log — every state change with timestamp, actor, and the data snapshot.
What it replaces
If your current process looks like any of these, you’re a candidate to migrate:
- Manager-to-HR Slack DM with “can you bump Alex to 75k starting May 1”
- Shared Google Sheet with a “pending changes” tab
- A Notion database with comments
- A Trello board called “comp changes Q2”
These all work — until they don’t. The work-until-they-don’t moment is usually a missed effective date or a duplicate approval, and it usually costs more than the SaaS fee.
What it doesn’t try to be
We are not trying to replace dedicated compensation-management tools like Pave, Figures, or CompTool. Those are for benchmarking and band design. Salary amendment in Leave Balance is for executing a change once you’ve decided to make it.
If you need market data, range bands, or letter generation, layer those on top. The amendment workflow handles the transactional half — the half that has to be auditable and has to land in payroll on the right day.
leave emails? Track your employee's leave with Leave Balance
The bigger point
Salary changes are the highest-stakes recurring transaction in HR, and they’re usually run on the lowest-grade tooling in the company. Bringing them into the same system that already handles leave, expenses, and payroll handoffs eliminates the integration risk that makes them painful in the first place.
If you’re still running comp changes on a spreadsheet, the migration cost is one afternoon. The error cost of staying on the spreadsheet is one mistimed payslip away.