What to check before buying HR software — pre-purchase checklist covering statutory compliance, rollout readiness, mobile capability, and operational fit.
Three months after a 180-employee operation in Pune signed an HR software contract on price and feature comparison, the HR head's review with the founder surfaced five gaps none of the demo sessions had exposed: a 6–10 week statutory update lag, a mobile self-service module available only as a paid add-on, a split-shift configuration pending as a customisation request, a Form 24Q output requiring Excel export and external validation, and a finance integration running through manual journal entry. Every gap was visible before contract signature — if the right questions had been asked.
Use this checklist to verify what to check before buying HR software for your operation. For the broader framework covering how to compare platforms, licensing models, and vendor track record, see how to choose the right HRMS for your operation.
Verify statutory compliance handling against the 2026 notification cycle. The platform must handle PF computation (EPFO rates, EPS wage cap, VPF, UAN portability), ESI (current gross threshold and rate), TDS on salary (Form 24Q in the current assessment year format), professional tax by state slab, and labour welfare fund contributions. For 2026: confirm specifically how the vendor has absorbed the revised EPFO notification cycle, the ESIC rate handling changes, and the Form 24Q revised format requirements. Ask which statutory notifications were absorbed in the last three release cycles and on what date each reached production.
Ask how statutory updates reach your production instance — and get the timeline in writing. This is the most operationally significant question most evaluations skip. Some vendors absorb statutory updates within days of notification through standard release cycles. Others route updates through a deployment process that adds 6–10 weeks of lag — during which payroll runs on outdated rates. The lag does not appear in any demo scenario. Ask: "How many days from a statutory notification to the update reaching our production instance?" Get the answer documented, not verbal. If the vendor cannot give a specific number, that is an answer.
Test mobile and employee self-service on actual devices during evaluation. Run the mobile self-service test with workers on actual Android and iOS devices — not on a tablet at a vendor demo table. Confirm that attendance check-in, leave application and balance, salary slip download, and investment declaration are part of the standard subscription. If the vendor routes any of these to a separately licensed app or a premium tier, that is not mobile-first capability built into the platform. A platform that positions mobile as an add-on will require a separate procurement decision and a second budget conversation post-go-live.
Demo the platform against your documented workforce reality — not the vendor's standard scenarios. Before the demo, prepare a scenario sheet: attendance patterns (fixed-location, field, hybrid, split-shift, overtime structures), leave types (privilege, sick, casual, comp-off, maternity, paternity), salary components across your worker grades, and your statutory deduction profile by state. Require the vendor to demonstrate the platform handling each of your documented scenarios. If the vendor substitutes their prepared demo flow for your specific requirements, the operational fit gaps will surface only after rollout commitment — not during evaluation.
Validate salary structure configuration depth without raising a customisation request. Confirm that earnings components (basic, HRA, allowances, special allowance), deductions (statutory deductions, voluntary PF, loan recovery), reimbursements (fuel, phone, LTA), and perquisite handling configure through the standard UI. Operations that require customisation requests for standard Indian salary structure variations typically accumulate 8–15 pending requests within the first year, each carrying a 4–12 week turnaround cycle. Ask the vendor to configure one of your salary grades live during the evaluation — not in a scripted demo environment.
Request live statutory output samples — not demo environment samples. Ask for a Form 24Q file, a PF challan, and an ECR file generated from a live client instance with a statutory profile similar to your operation. Compare the Form 24Q sample against the current prescribed format from the income tax department. If the vendor offers demo environment samples only, or declines the request entirely, that is a material signal about the accuracy of their current statutory output in production. A platform that generates correctly formatted statutory output should have no hesitation producing live samples.
Facing similar workforce management challenges?
See how exactllyHRMS manages payroll governance, attendance management, and statutory compliance — built for operational businesses.
See how exactllyHRMS governs payroll and compliance →Confirm integration capability against your specific finance system and banking partner. Salary cost-centre allocation to your finance system, salary file generation in your banking partner's required format, and payslip distribution should run as configured workflow — not as flat-file export and manual upload. Ask: "How does salary journal entry reach our finance system — named-ERP integration, configured API, or flat-file export?" Unnamed "open API capability" that requires custom development is not a ready-configured integration. The ERP and HRMS integration question becomes critical when your finance team expects cost-centre visibility without manual intervention each payroll cycle.
Assess the vendor's post-go-live support model for statutory updates and configuration changes. Post-go-live support covers two distinct categories. Statutory update absorption should happen through the vendor's standard release cycle without your team raising a support ticket for each regulatory change. Configuration change requests — adding an allowance component, adjusting a leave structure, modifying an approval workflow — should carry a documented turnaround SLA. Ask: "What is the typical turnaround time for a configuration change request after go-live?" Operations where the answer is vague or aspirational typically face the 8–15 request backlog within the first year.
Evaluate rollout governance discipline across master data, parallel run, and stabilisation. A disciplined HRMS implementation runs 8–12 weeks. Ask the implementation partner to walk through their approach to master data preparation (worker master fields per employee, statutory enrolment data, salary structure mapping), UAT against your documented scenarios, training on the configured baseline, and parallel run through the first payroll cycle. If the implementation team cannot articulate the parallel run process specifically — when it starts, what it validates, who signs off — that is a rollout governance risk. Most implementations that land at 18–26 weeks failed at master data preparation or parallel run discipline, not at configuration.
Calculate total cost of ownership across three years — not year-one subscription. The year-one subscription comparison misses the positions that differentiate platforms across a three-to-five year window. The full TCO: implementation cost, customisation requests over the window (8–15 requests at ₹15,000–₹60,000 each adds ₹1.5–₹6 lakh), statutory update delivery overhead if the vendor uses a deployment lag cycle that requires manual workarounds, capability addition cost (self-service configuration versus paid development work), IT support requirement, and switching cost at the multi-year mark. For a 180-employee operation, the three-year TCO difference between the lowest year-one cost platform and a platform with deeper configured capability often runs ₹8–15 lakh — enough to change the selection outcome.
The pattern across operations that applied this checklist during evaluation versus those that did not:
| Outcome | Checklist-based selection | Feature-based purchase |
|---|---|---|
| Statutory update in production | Within standard release cycle | 6–10 week deployment lag |
| Rollout timeline | 8–12 weeks | 18–26 weeks |
| Post-go-live configuration requests | 1–3 in year one | 8–15 in year one |
| Mobile self-service | Standard subscription | Separate add-on |
| Finance integration | Configured cost-centre flow | Manual journal entry |
| Parallel-tool persistence at month 3 | Under 20% | 50–65% |
For the broader HRMS evaluation guide, the criteria above address pre-commitment verification — not the full platform selection methodology.
How exactllyHRMS handles this checklist
exactllyHRMS is built around the operational realities this checklist tests for. Attendance integration covers biometric, mobile self-service, and structured check-in in the standard platform — not as a separately licensed module. Salary structures across worker grades — earnings, deductions, reimbursements, and perquisite components — configure through the standard UI without customisation requests for standard Indian payroll structures. Statutory masters for PF, ESI, TDS, and professional tax reflect current rates through standard release cycles. Form 24Q, PF challan, and ECR file generation runs from configured data, reducing the need for Excel export or external consultant validation in standard deployments.
Three checklist items from above that exactllyHRMS addresses specifically: the statutory compliance module supports PF, ESI, and TDS rate changes through the standard release cycle for most notification types, reducing dependence on delayed manual updates. The mobile self-service interface covers attendance, leave, payroll, declarations, and documents in the standard subscription on Android and iOS — not as a separately licensed add-on. Cost-centre salary journal entry to the finance system can run as a configured data flow where the finance integration is enabled, reducing flat-file export and manual upload dependency.
Request a demo against your documented workforce reality — your attendance patterns, leave structures, statutory deduction profile, and finance integration requirement — before signing.
