HRMS implementation checklist for a smooth go-live
A smooth HRMS go-live runs in five stages: clean your employee and salary data, turn your policies into written rules, test those rules with real cases, run one payroll in parallel with your old process, then roll out to managers before employees. Don't switch off the old payroll until every difference in the parallel run is explained.
Before You Start: An Owner And A Cut-over Date
Most go-lives of new HRMS software that slip do so for two reasons: nobody owns the decisions, or the start date lands in the middle of a payroll month. Settle both first.
- Name one owner in HR who signs off on every policy and test. Add one person from payroll or finance and one site manager who will champion the rollout.
- Pick a cut-over date at the start of a payroll month. 1 April is easiest, because no year-to-date tax data has to move. If you switch mid-year, plan to carry over year-to-date earnings and TDS for every employee.
- Work the timeline backwards from that date, leaving room for at least one parallel payroll run before it.
Stage 1: Clean Your Data
Every error in the old data becomes an error in the new system, usually on an employee's first payslip. Clean it in one sheet per data type before anything is imported.
| Data | What to check |
| Employee master | One record per person, joining date, department, location, legal entity and reporting manager for everyone |
| Statutory and bank details | UAN, ESIC number, PAN, bank account and IFSC, with no blanks or duplicates |
| Salary structures | Every component and its tax treatment. Check that basic pay and DA make up at least 50% of total pay, or the excess counts as wages for PF and gratuity |
| Leave balances | Balances as of the cut-over date, signed off by each manager |
| Year-to-date figures | Earnings, TDS deducted and investment declarations, if you switch mid-year |
| Open items | Loans, salary advances, pending reimbursements, and assets issued |
The reporting manager field matters more than it looks. Approvals route through it, so a wrong manager means leave requests go to the wrong person on day one.
Stage 2: Turn Policies Into Rules
An HRMS can only apply a policy that someone has written down. Collect the rules people follow from memory and decide each one before setup.
- Attendance: shift timings, grace period, half-day and late-mark rules, regularisation limits.
- Leave: leave types, accrual, carry-forward, encashment and holiday calendars for each location.
- Approvals: who approves what, at which level, and who covers when an approver is away.
- Payroll: salary structures, overtime, statutory deductions by state and the full and final settlement process.
The Labour Codes changed several of these rules. Check them before you configure:
| Rule | What to set up |
| Annual leave eligibility | Workers become eligible after 180 days of work in a year, at 1 day for every 20 days worked |
| Leave carry-forward | Up to 30 days carried forward, with the excess encashed |
| Overtime | Twice the ordinary rate of wages beyond 8 hours a day or 48 a week |
| Wage definition | Allowances above 50% of total pay added back to wages for PF and gratuity |
| Exit settlement | Wages due on exit, including resignation, paid within two working days |
States are still notifying their own rules, so confirm the limits for each state you operate in.
Stage 3: Test With Real Cases
Pick 10 to 15 real employees who between them cover every unusual case, and run each case through the system before go-live:
- A new joiner who started mid-month
- Leave that includes a holiday or weekly off
- A night shift and an overtime day
- A day of loss of pay
- An employee in another state, for Professional Tax
- An exit with full and final settlement
- A leave request when the approver is on leave
Fix the setup, not the output. If a result is wrong, change the rule that produced it and test the case again.
Stage 4: Run Payroll In Parallel
A parallel run means processing one month's payroll in both the old process and the new system, then comparing every employee's net pay. It is the only reliable test that the new setup matches reality.
Here is part of a reconciliation from a parallel run, with example figures:
| Employee | Old net pay | New net pay | Difference | Reason found |
| Employee A | ₹32,450 | ₹32,450 | ₹0 | Matches |
| Employee B | ₹41,200 | ₹41,575 | +₹375 | Old sheet missed 1.5 hours of overtime. New system is right. |
| Employee C | ₹22,000 | ₹21,154 | −₹846 | One day of loss of pay (₹22,000 ÷ 26) is not in the old sheet. The new system is right. |
| Employee D | ₹27,300 | ₹27,100 | −₹200 | Professional Tax is set for the wrong state. Fix the setup. |
Every difference needs a reason. Some show errors in the old process, and some show setup mistakes in the new one. Go live only when every difference is explained and the setup mistakes are fixed.
Stage 5: Roll Out To Employees
- Managers first. Train them on approvals before employees can send requests, so nothing waits in an empty queue.
- Then employees, site by site. Install the app with them, and have each person check their profile, leave balance, and first punch.
- Name a contact for questions at every site for the first month.
- Set a date after which leave requests outside the system are no longer accepted.
Adoption is where most rollouts quietly fail. See why employees stop using HRMS after the demo.
Go-live Day And The First Month
- Make the old system or sheet read-only, and keep it for audits.
- Review attendance exceptions every day in the first week.
- Give the first live payroll an extra review before you lock it.
- Log every question and complaint, and fix the top three after the first payroll.
Common Mistakes
- Importing data before cleaning it. Fixing records after go-live costs more and shows up on payslips.
- Skipping the parallel run to save a month.
- Launching to employees before managers are ready to approve.
- Going live mid-month, which splits one payroll across two systems.
- Copying every old workaround into the new system instead of fixing the policy.
How QkrHR Supports Implementation
A go-live is easier when the software follows the same order as this checklist: clean data in, rules set once, a payroll that holds still while you compare, and managers ready before employees. Every QkrHR plan includes free onboarding assistance and dedicated support, and most teams are up and running within a few weeks, depending on how clean their data is and how many locations and policies they have.
What QkrHR gives you during implementation
| What QkrHR does | Why it helps your go-live |
| Free onboarding on every plan. Data migration, system configuration, and user training from the QkrHR team. | You don’t set up alone, and the system matches your policies before anyone logs in. |
| Rules set once, applied every cycle. Attendance, leave, approval, and payroll rules are configured, not calculated by hand. | A wrong result is fixed by changing the rule, exactly as this checklist recommends. |
| A three-stage payroll lock. Attendance lock, payroll finalisation and payroll lock. | Figures don’t move while you compare the parallel run line by line. |
| One inbox for approvals. The Pending Actions inbox on web and mobile, with reminders and auto-escalation. | Managers can be trained and ready before employees send their first request. |
| Dedicated support after go-live. The same team stays available through the first payroll. | First-month questions get answered instead of piling up. |
How QkrHR handles each stage of this checklist
| Checklist stage | How QkrHR handles it | Plan |
| Owner and cut-over date | The onboarding team plans the setup backwards from your cut-over date and works with your HR owner on each decision. | All plans |
| Stage 1: Clean your data | Data migration is part of onboarding. Employee master, statutory IDs, bank details, and leave balances load into one employee profile, and the reporting manager field drives every approval route. If you switch mid-year, confirm in the demo how year-to-date earnings and TDS will be carried over. | All plans |
| Stage 2: Policies into rules | Shift and attendance rules, leave types with accrual, carry-forward, encashment and sandwich leave, a holiday calendar per location, unlimited salary structures, and PF, ESI, PT, LWF and TDS are set up once. Approvals run up to 3 stages on Essential; unlimited stages and delegation come with Foundation, as does overtime automation. | All plans: Foundation for unlimited approvals, delegation, and overtime |
| Stage 3: Test with real cases | Your 10 to 15 test employees run through the same rules that will run live payroll, so every result reflects the real setup. | All plans |
| Stage 4: Parallel run | Attendance is locked first, then payroll is finalised and locked, so the numbers stay fixed while you compare. Exceptions are highlighted on the payroll dashboard instead of being found in a spreadsheet. | All plans |
| Stage 5: Roll out | Managers approve from the Pending Actions inbox on the mobile app before employees go live. Employees then check their profile, leave balance, and first punch in the Android or iOS app, site by site. | All plans |
| Go-live and first month | Attendance exceptions and regularisation requests show on the HR dashboard for daily review; every change keeps an audit trail, and dedicated support covers the first live payroll. | All plans |
Going live is only half the job. Our guide on HRMS adoption covers why employees stop using a system after launch and how to prevent it. To see how onboarding, payroll, and approvals fit together, explore the QkrHR HRMS software, or compare what each plan includes on the pricing page. In the demo, ask for an implementation plan built around your cut-over date.