HRMS Demo Checklist 2026: 15 Questions to Ask Before You Sign

Most HRMS Demos Are Sales Pitches. Here Is How to Turn One Into an Evaluation.

A typical HRMS demo follows a familiar pattern. The salesperson shares their screen, walks through a pre-configured sample company, shows the best-looking features, and ends with a pricing discussion and a request to sign before the end of the month. You leave the call with a polished impression and almost no information about whether the software will actually work for your specific payroll structure, your compliance requirements, or your employees.

This checklist is designed to fix that. Use it before every HRMS demo you attend in 2026. The 15 questions below cover the compliance gaps, hidden costs, and implementation traps that most vendors will not address unless you ask directly.

Before You Book Any HRMS Demo

The quality of a demo depends largely on the preparation you do before it.

Know Your Non-Negotiables

Write down the three or four features without which you would not sign, regardless of how good everything else looks. For most Indian companies, these are: automated PF calculation with the new ₹25,000 wage ceiling, ESIC ECR generation without manual file editing, biometric machine integration with your specific device brand, and multi-state professional tax. If the vendor cannot demonstrate these in the demo, the conversation ends there.

Prepare Your Own Test Data

Do not let the vendor demo only their sample company. Prepare a simplified version of your own payroll — five to ten employees with a representative mix of salary bands, one employee with loss of pay for part of the month, one employee on ESIC (salary below ₹21,000), one employee above the PF wage ceiling, and one with a pending TDS declaration. Ask the vendor to run payroll for these five employees during the demo. This reveals whether the system handles your actual situation or just the sanitised demo scenario.

Invite the Right People

The person who manages payroll — often the HR manager or payroll accountant — must attend the demo. An HRMS that impresses a founder in a 30-minute overview may completely fail the payroll operator who will use it daily. If you have an IT team, have someone technical attend for the portion covering biometric integration, data security, and API capabilities.

Request a Sandbox Before the Demo

The best vendors will give you sandbox access — a working trial account with sample data — before the formal demo. This lets you explore independently and arrive at the demo with specific questions about things you have already tried. A vendor who refuses to give sandbox access before signing a contract is a red flag: it usually means the software looks better in a guided demo than in unsupervised use.

The 15 Questions Every HRMS Demo Must Answer

1. Can it calculate PF on the new ₹25,000 wage ceiling automatically?

The PF wage ceiling changed in September 2026 from ₹15,000 to ₹25,000. PF is now calculated as 12% of wages up to ₹25,000 for employees who were not already contributing on a higher base. Ask the vendor to demonstrate this calculation live, for an employee earning ₹30,000 gross. The correct employer PF contribution is 12% of ₹25,000 = ₹3,000.

Good answer: Vendor demonstrates the calculation live with the correct ceiling, explains how the system handles employees who were on a higher PF base before the notification, and shows how the EPFO-mandated wage ceiling update was pushed automatically to all customer accounts.

Bad answer: Vendor says "yes, we handle PF" without showing the calculation, or shows a ₹15,000-based calculation and says the ceiling will be updated "in the next release."

2. How does it handle ESIC ECR generation — manual or automated?

ESIC monthly returns require an ECR file in a specific format. Some HRMS products generate this file automatically from the payroll run. Others require you to manually download a template, fill in the data, and upload it to the ESIC portal. The difference is approximately two to three hours of work per month for a team of 50 employees. Ask to see the ECR file generated from the demo payroll run.

Good answer: Vendor shows the ECR file generated automatically after payroll run, with all required fields populated correctly, and explains how the file is validated before submission.

Bad answer: Vendor says ECR export is "coming soon" or shows a generic Excel export that the user must then format manually before uploading.

3. Show me a payroll run with loss-of-pay for 3 employees.

Loss of Pay (LOP) handling is a compliance area where many HRMS products have gaps. LOP affects not just the salary calculation (daily salary × LOP days) but also PF calculation for that month, ESIC contribution (if LOP reduces the month's wages below ₹21,000), and potentially professional tax. Ask the vendor to run payroll for three employees — one with 2 days LOP, one with 5 days, and one with half a day — and show how each deduction is recalculated.

Good answer: System recalculates all statutory deductions based on reduced wages, uses the correct formula for LOP (monthly salary ÷ number of working days × LOP days), and handles the edge case where LOP reduces ESIC applicability.

Bad answer: LOP deduction is manual, or the system recalculates gross but does not automatically recalculate statutory deductions.

4. How do you handle professional tax across multiple states?

If your company has employees in Maharashtra, Karnataka, Andhra Pradesh, and Gujarat, professional tax is calculated differently in each state — different slabs, different deduction frequencies, and different payment processes. An HRMS that handles multi-state PT correctly should have current PT slabs for every applicable state built in and should apply the correct slab automatically based on each employee's work state.

Good answer: Vendor shows a demo company with employees in at least three states, confirms that PT slabs are updated automatically when state governments revise them, and shows the challan generation for each state separately.

Bad answer: PT is configured manually by the customer, or the vendor is unsure which states are pre-configured.

5. Can I import our existing salary structure from Excel?

Every company has an Excel salary register or a salary structure template. The ability to import this directly — rather than manually recreating each employee's salary in the new system — is the difference between a two-hour data migration and a two-week one. Ask the vendor to show you an actual import using your sample data, not a demo file.

Good answer: Vendor shows a field-by-field mapping interface, imports a sample file, shows validation errors clearly, and confirms the data looks correct after import.

Bad answer: Import is available but requires a specific template that is different from your format, or import is only done by the vendor's implementation team "during onboarding."

6. What biometric machine brands does it integrate with natively?

Native integration means the HRMS pulls attendance data directly from the machine, automatically, on a schedule. It does not mean you download a file from the machine's software and upload it to the HRMS manually. Ask which specific brands are supported (ZKTeco, ESSL/eSSL, Realtime, Matrix, Hikvision), whether the integration requires any additional hardware, and what happens to attendance data if the internet connection drops for a day.

Good answer: Vendor names specific supported brands and models, explains the integration method (direct API, SDK, or FTP pull), and confirms no additional hardware is required for standard setups.

Bad answer: Integration is via a third-party connector, requires a separate subscription to an integration service, or relies on manual file export/import.

7. Show me the employee self-service portal on mobile.

In India, most employees access HR self-service on their phones, not on a desktop. Ask the vendor to open the employee self-service portal on a mobile device — not a demo of what it looks like, but an actual demonstration of applying for leave, downloading a payslip, and viewing attendance on a phone. If it does not work well on mobile, your employees will not use it.

Good answer: Vendor demonstrates on an actual phone (not a desktop browser zoomed to phone size), the interface is touch-friendly, payslip download works, and leave application is a two-tap process.

Bad answer: Mobile is only available through a dedicated app that requires a separate download, the app has poor reviews on the Play Store, or the vendor says "mobile app is on the roadmap."

8. How are arrears calculated when a salary structure changes mid-month?

When an employee receives a salary increment effective from a date in the middle of a month, the system must calculate the arrear — the difference between old and new salary for the portion of the month after the effective date — and add it to the current month's payroll. This calculation involves recalculating all statutory deductions on the revised figures.

Good answer: Vendor shows a salary revision for one employee with a mid-month effective date, calculates arrear automatically, recalculates PF and other deductions on the total revised figure, and shows the payslip clearly labelling the arrear component.

Bad answer: Arrears require manual entry, or the system adds the arrear to gross without recalculating statutory deductions.

9. What happens if the payroll run fails halfway — can it be rolled back?

Payroll runs involve multiple steps — calculating gross, applying deductions, generating payslips, updating leave balances, preparing challan files. If the run fails midway because of a data error or system issue, you need to be able to roll back to the pre-run state cleanly.

Good answer: Payroll runs are transactional — either the full run completes or nothing is committed. Rollback is automatic on failure, and the vendor can show a test of this in the sandbox.

Bad answer: Rollback requires vendor support intervention, or the vendor says this has "never happened" without explaining the technical guarantee.

10. Show me how TDS is calculated for an employee with 80C declarations.

TDS calculation for salaried employees involves projecting annual income, applying the selected tax regime (old or new), deducting 80C investments declared by the employee, and dividing the net tax liability evenly over the remaining months of the financial year. Ask to see this for one employee who has declared ₹1,50,000 in 80C investments and is under the old tax regime.

Good answer: Vendor shows the TDS calculation screen with projected annual income, 80C deduction applied, old regime slabs applied correctly, tax rounded to rupee, and distributed evenly over remaining months.

Bad answer: TDS is calculated by the accountant manually and entered as a flat deduction, or the system does not support employee 80C declarations.

11. How does it handle contractor or consultant payments versus regular payroll?

Many Indian companies pay consultants through payroll software for convenience, but consultant payments have different tax treatment (TDS at 10% under section 194J, no PF, no ESIC), different payslip format, and different compliance reporting.

Good answer: Vendor shows a distinct consultant/contractor payment module with appropriate TDS rate, no statutory deductions, and separate reporting that does not mix with regular payroll.

Bad answer: Consultants are added as regular employees with manual overrides, or the system handles only regular payroll.

12. What is the implementation timeline for a 100-employee company?

Ask for a week-by-week implementation plan, not a range of weeks. The plan should cover: data collection and validation (Week 1), salary structure and policy configuration (Week 1–2), parallel payroll run (one full payroll cycle), employee data import and portal access provisioning (Week 2), training for HR team (Week 2–3), and go-live (month start after parallel payroll confirms).

Good answer: Vendor provides a milestone-based implementation plan with clear owner responsibilities (vendor vs. customer) at each step, and gives references of similar-sized companies they have implemented for.

Bad answer: Implementation timeline is "four to six weeks" with no further detail, or the vendor says implementation depends entirely on how quickly the customer provides data.

13. What does "support" actually mean after I sign?

Ask specifically: What is the response time SLA for a payroll failure on month close date? Do I get a named support contact or a ticket queue? Is there phone support or only email/chat? Does support coverage include statutory compliance questions, or only technical product questions?

Good answer: Vendor provides a specific SLA (e.g., four-hour response for critical payroll issues), names a dedicated implementation manager for the first 90 days, and confirms that compliance configuration questions are within support scope.

Bad answer: Support is "24x7" without a defined response time, or payroll-day support is only available on the premium plan you are not considering.

14. What are the exit clauses — can I export all data if I leave?

Ask to see the data portability section of the standard contract before the demo ends. Specifically: Can you export complete employee data, payroll history, and compliance filing history at any time, without requesting it from support? What formats are available (CSV, Excel, JSON)? Is there a fee for data export on cancellation?

Good answer: Full data export is available at any time through the self-serve admin panel, no exit fee for data, data retained for 90 days post-cancellation and deleted on request.

Bad answer: Data export requires a support request, takes five to ten business days, has a processing fee, or the vendor says "data is yours but extraction is complex."

15. Show me the total cost — including implementation, migration, and annual increases.

The headline monthly subscription price is almost never the total cost. Ask for a fully-loaded cost estimate covering: monthly subscription at your employee count, one-time implementation fee (if any), data migration fee, training fee, biometric integration fee (if charged separately), annual price escalation clause, and the cost of any modules you will need but are not in the base plan.

Good answer: Vendor provides a written cost breakdown in the demo follow-up email, including all one-time and recurring costs, with the annual price escalation cap stated explicitly.

Bad answer: "Pricing is custom, we will send a proposal" with no indication of what the proposal will contain, or a proposal that arrives two weeks later after multiple follow-ups.

Red Flags to Watch for During Any HRMS Demo

• Demo uses only screenshots, not the live product. Any serious HRMS can be demonstrated live. If the vendor shows slides or pre-recorded video for key features, the live product does not match the marketing.
• No sandbox available before purchase. A vendor confident in their product gives you access to try it. Withholding sandbox access is a sign they know unsupervised use reveals problems.
• India compliance features demonstrated vaguely. "We handle PF and ESIC" is not a demonstration. If the vendor cannot show you a specific PF calculation with the correct wage ceiling, they either do not know their own product or the feature is not as mature as claimed.
• Implementation timeline is vague. "Two to four weeks depending on your complexity" means the vendor has no structured implementation process.
• Pricing changes between the demo and the contract. Always get pricing in writing before the demo ends, and read the contract pricing clause before signing.

Frequently Asked Questions About HRMS Demos

How many HRMS demos should I book before deciding?

Three to five demos is the right range for most companies. Fewer than three risks missing a better option; more than five typically produces diminishing returns and decision fatigue. Book demos in order of your priority list — start with the vendor you are most likely to choose and use each subsequent demo to pressure-test your initial impression rather than to discover entirely new options.

Is a free trial better than a guided demo?

Both serve different purposes. A guided demo is efficient for understanding the product's breadth quickly. A free trial is better for testing specific workflows that matter to you — particularly payroll runs, compliance configuration, and self-service features. The ideal sequence is a one-hour guided demo followed by two weeks of sandbox access, with a follow-up call to resolve questions that came up during the trial.

What is the average HRMS implementation time in India?

For a company with 10–50 employees and a standard salary structure, a well-run implementation should complete in two to three weeks including parallel payroll validation. For 50–200 employees with multiple departments, multi-state payroll, and complex leave policies, three to five weeks is realistic. Any vendor quoting less than two weeks for a 100-employee implementation is either underestimating the work or skipping the parallel payroll step, which is a risk not worth taking.

Can I negotiate HRMS pricing during or after the demo?

Yes, and you should. Most HRMS vendors have more flexibility on pricing than the initial quote suggests, particularly on implementation fees, multi-year discounts, and the minimum employee count threshold. The best time to negotiate is before signing, not after. Specific negotiating points that often yield results: a commitment to a multi-year contract in exchange for a first-year discount, waiving the implementation fee in exchange for a case study or testimonial, or requesting a free quarter of service if the implementation exceeds the promised timeline.

---

Book a PeopleVio demo and we will show you live payroll — not slides. Bring your own test data. We will run payroll, generate an ECR file, and show you the employee self-service portal on mobile during the call. If we cannot answer any of these 15 questions to your satisfaction, we will tell you so directly.