One plan. Everything in it.

Because tiering an HRMS means tiering compliance, and that is the wrong thing to sell. In a three-tier model the statutory depth — multi-state Professional Tax, LWF frequency, contribution-period handling, labour-code wage definitions — always lands in the upper tier. The company least able to absorb a PF notice ends up with the weakest coverage. We would rather charge one rate and let headcount do the scaling.

No. The price is exclusive of GST, charged at the applicable rate on your invoice. We state it this way round deliberately — a price that quietly includes tax is the one that causes an argument at the first invoice.

No implementation fee. Configuration, data migration, the parallel payroll run and training are part of the subscription. We take the view that an implementation charge is a fee for making the product work, which is a strange thing to invoice for separately.

Subscriptions are annual, and the rate on this page is the annual-billing rate. Monthly billing is available at the higher rate shown when you switch the toggle in the calculator.

You are billed on active employees, so joiners and exits are reflected at the next billing date rather than requiring a contract change. There is no minimum headcount — ten employees or ten thousand, you pay for the people you actually employ.

No. Entities, locations and statutory registrations are unlimited on the same subscription. This is the charge most often buried elsewhere, and it is the one that punishes exactly the companies EZER is built for — a group running a corporate office, two factories and a warehouse should not pay four times.

Yes, at any point, and there is no charge for it. Employee master, payroll history, statutory records and documents export in standard formats. We consider an exit route a feature: a system you cannot leave is one you should not enter.

Not at the moment, and the reason is honest rather than commercial. Payroll cannot be meaningfully evaluated on sample data — the value only shows up when it is running against your salary structures, your states and your registrations. So we demo against your own scenario instead, and during implementation we run one full cycle in parallel with your existing process before you cut over. You see your own numbers reconcile before anything depends on them.