Best HR Software in India 2026

The hard question in buying HR software in India is usually not which vendor. By the time somebody sits down to compare, they usually have three names already, picked up from a colleague, a conference and whatever the finance director's last company used. What they have not decided, and what will decide whether this buy succeeds, is the shape of system they are buying.

HR software in India is one system that holds the employee record and runs payroll, attendance and leave against it, along with the statutory filings that record attracts: PF, ESI, professional tax and salary TDS. What differs between products is the shape of that system, not the length of the feature list. There are three shapes. One vendor for everything. A payroll-led core with pieces added around it. Or two or three good systems stitched together and made to talk. Those are genuinely different buys, with different failure modes, different costs in year two, and different answers depending on whether your people sit at desks or stand at machines. Pick the shape first and the vendor list mostly writes itself. Pick a vendor first and you will spend the implementation finding out which shape you bought by accident.

This piece is about the suite decision. It covers what one system has to carry in India, what to establish about your own company first, eleven platforms an Indian buyer genuinely shortlists and who each one suits, what happens at the joins between modules, and the mistakes common enough to be predictable. It is written for whoever owns the decision and then has to live inside it.

One thing before the rest. Breadth is not the same as depth, and on a feature list the two look identical. The only way to tell a suite you can use from a suite that exists on a feature list is to ask what happens where two modules meet. That is section 6.

Positions are current at October 2026 and reflect the four Labour Codes in force from 21 November 2025, the Employees' Provident Funds Scheme, 2026 effective 29 June 2026, the provident fund wage ceiling raised to ₹25,000 on 17 September 2026, and the Income-tax Rules, 2026 governing salary paid from 1 April 2026. Product descriptions are our reading of what each platform is built for and are not statements about any vendor's business. This is not legal advice. Verify anything that will affect a payment or a filing against the primary source before you act on it.

How This Is Ordered, and What We Are

We build Engage, an Indian HRMS. That is a conflict of interest, so it goes in the first section rather than in a footer. Engage is listed first in section 5 because it is ours, not because it came first on any measure. The other ten are alphabetical and the order carries no judgement.

There are no ratings, scores, rankings or review counts from any software directory anywhere in this post, and none anywhere on this site. Where we say something is true of a product, it is because the vendor has documented it or you can see it in the product. Nothing below describes how any company markets, prices publicly or positions itself. The comparisons are about what the software does, what it is scoped for, and what it cannot do.

Now the most useful sentence in this section, which is about what you should read instead of this. If you have already decided the shape of the buy and narrowed to payroll, stop here and read our comparison of payroll software in India, which goes into wage bases, arrears across a retrospective revision, and how to run a parallel month before you switch. If you have narrowed to attendance, read our comparison of attendance management software, which covers device estates, field capture and shift rostering. Neither subject is repeated here. Repeating them would make this a worse page and those two better ones. This post is only useful while the suite question is still open.

The eleven platforms below were selected on one test. Would an Indian company between roughly 25 and 10,000 employees, buying more than one HR function at once, plausibly put this product on a shortlist. That range is wider than the payroll comparison uses, deliberately, because the suite question reaches further up and further down than the payroll question does.

The Real Decision Is the Shape of the Purchase

Take the three shapes in turn, because each one is right for somebody.

The full suite means one vendor owns core HR, payroll, attendance, leave, onboarding, performance and usually recruitment, on one employee record. The argument for it is that the record is shared rather than copied. An employee created once is created everywhere, and a mid-year transfer between states updates professional tax, labour welfare fund and the reporting line in the same action. The argument against it is that you accept the vendor's weakest module along with their strongest, and you have no leverage when the weak one stays weak. Every suite has a weak module. Find out which one it is before you sign, not after.

The payroll-led core is the shape most Indian mid-market companies end up with, whether or not they chose it. Payroll and its statutory apparatus sit at the centre, because that is the part with a deadline attached. Attendance and leave get added because payroll needs them as inputs. Performance, recruitment and learning arrive later or never. This is an honest and often correct answer. It matches how the budget actually gets approved, and it means you are deep where the risk is and thin where it is not. The cost is that the later modules are bought from a position of weakness, because by then you are not comparing, you are extending.

Best-of-breed means separate systems chosen on merit for each function, connected by integrations. It is the right answer more often than buyers expect, particularly where one function is genuinely unusual. A company with 3,000 field staff and a real workforce management problem may be better served by a specialist attendance product feeding a competent payroll engine than by a suite that does both adequately. The price is that you now own the integrations, and integrations are a permanent operating cost rather than a one-time build. Somebody has to notice when one breaks. The way you usually notice is that payroll is wrong.

The question that decides between them is narrower than it looks. It is not how many modules you want. It is how many times a month data has to move between two of them, and what it costs when it moves wrongly. If attendance feeds payroll monthly for 800 people, that is a high-traffic seam and it belongs inside one system. If recruitment hands over four candidates a month to onboarding, that is a low-traffic seam, and an integration or even a manual step is fine. Map your seams by traffic and by consequence, and the shape falls out of that rather than out of a feature comparison.

There is a fourth option that gets confused with the first, which is taking HR from the ERP you already run. That is a genuinely different trade, and we have written about it separately in our piece on HR software versus an ERP HR module. The short version is that the integration you get for free is the finance one, and the price is usually statutory currency and the speed of a configuration change.

One more thing while you are choosing. A full suite concentrates the operating knowledge in one or two people. Best-of-breed spreads it out and needs somebody who understands all of it. That is why companies with a single HR generalist and no technical owner do badly with it, for reasons that have nothing to do with the software.

What HR Software Has to Carry in India

Compliance is easy to treat as one row in a table. In India it is not one row. It is a set of obligations that land in different modules. So the suite question is really a question about whether every one of them has an owner inside the system, or whether some of them quietly land back on a spreadsheet.

Start with the fact that the ground moved. The four Labour Codes were brought into force on 21 November 2025, replacing twenty-nine central laws. The wage definition in section 2(y) of the Code on Wages, 2019 has the widest reach. Where excluded allowances exceed one-half of total remuneration, the excess is added back into wages, and that single figure then feeds PF, gratuity, bonus and overtime at once. Overtime itself sits in section 14 of the same Code, at not less than twice the normal rate, and it now applies across sectors rather than mainly to factories. Our piece on overtime pay calculation works through the arithmetic.

Then PF. The Employees' Provident Funds Scheme, 2026 took effect on 29 June 2026, superseding the 1952 scheme rather than amending it. More immediately, the wage ceiling for mandatory coverage under Chapter III of the Code on Social Security, 2020 was raised from ₹15,000 to ₹25,000 by notification dated 17 September 2026, superseding the 29 May 2026 notification that had restated the ₹15,000 figure. It changes who is a member. It changes employer cost for a band of employees who were previously outside it. And it will change the salary structures companies offer to new joiners. If you are running a software evaluation right now, ask every vendor on your list what they have shipped for it. The answers will be more informative than the demo.

ESI is the steadier one, at 3.25 per cent from the employer and 0.75 per cent from the employee on a wage ceiling of ₹21,000, rates unchanged since July 2019.

Professional tax is where multi-state companies find out what their software is made of. It is a state levy, capped by Article 276(2) of the Constitution at ₹2,500 per person per annum, with slabs and deduction months that differ by state and change independently of each other. It is also not permanent. Odisha repealed its professional tax entirely with effect from 1 April 2026, so a system still deducting it for an Odisha employee is deducting a tax that no longer exists. The state pages carry the current position.

Labour welfare fund is smaller in rupees and larger in nuisance. It applies in some states and not others, and the contribution cycles do not line up. Maharashtra deducts half-yearly against 30 June and 31 December, while Karnataka runs annually. For a company with people in four states, that is four different calendars for one deduction worth a few rupees a head. It is exactly the kind of obligation that gets missed until an inspection. The labour welfare fund pages show the spread.

Minimum wages are the head most often assumed to be somebody else's problem. They are state-specific, category-specific, and revised on variable dearness allowance rather than on a fixed schedule. If your system holds a wage floor at all, the question is not whether it is right today. It is how you would find out it had gone stale. Our minimum wages pages publish revision dates for that reason.

The income tax cycle changed shape this year. Salary deduction now sits under section 392 of the Income-tax Act, 2025. And from 1 April 2026 the quarterly salary statement moved from Form 24Q to Form 138, the annual salary certificate from Form 16 to Form 130, and the employee investment declaration from Form 12BB to Form 124 under the Income-tax Rules, 2026. This is the easiest currency test in the whole evaluation, because you can simply look at what the product's screens and templates say. A product still labelling those screens Form 24Q and Form 16 without qualification is telling you something factual about itself.

Now the part that belongs to the suite question rather than to payroll. Several obligations under the Codes are not payroll obligations at all, and a payroll-led shape leaves them homeless.

Read the third column, because it is the suite argument stated plainly. Every row is an obligation that has to live somewhere. In a full suite they live in modules that share a record. In a payroll-led shape, the ones that are not payroll tend to live in a spreadsheet owned by whoever asked about them last. That is not an argument that everybody should buy a suite. It is an argument that you should know, before you sign, which of these rows your chosen shape leaves unowned, and decide deliberately rather than by accident.

Multi-entity structures deserve their own sentence, because they are the most common reason an otherwise good product stops fitting. A group with three registered entities, separate PF codes, a shared leadership team and employees who move between them is not an edge case in India. Above a few hundred people it is normal. Ask whether the system models entity as a first-class object with its own statutory registrations, or whether entity is just a label on an employee record. Those two designs look identical on a demo and behave completely differently when somebody transfers.

Establish This About Your Own Company First

You can run this section before you speak to any vendor, and doing so will remove more names from your list than any demo will. The aim is to be able to state, in writing, what shape of company you are. Four things establish it.

The first is headcount band, and it matters because the bands are not a smooth continuum. Below about 25 people, a full HRMS is more system than the problem needs, and the honest answer is usually a payroll product plus a shared calendar. Between roughly 25 and 150 you are buying your first real system. The deciding factor is whether attendance feeds payroll, and the binding constraint is that nobody has time to configure anything elaborate. Between 150 and 1,000 you cross the line where a full suite starts earning its cost, because the number of seams has grown faster than headcount and somebody is now reconciling for a living. Above 1,000 the questions change again, to governance, audit trails, role-based access and what happens during a statutory audit, and the shortlist narrows to platforms built for that.

The second is workforce type, and it separates buyers more sharply than headcount does. An office-only company with salaried staff and predictable inputs has a light attendance problem and a heavy leave and performance problem, and can buy almost anything. A field workforce of sales or service staff needs location-aware capture and a mobile app people will actually open, and most office-population products handle this by adding a checkbox. A shift-based workforce in manufacturing, warehousing or healthcare needs rosters, shift differentials, overtime on a defensible wage base, and contract labour handled without a parallel sheet. This is where product fit collapses fastest. A multi-location company needs the state-level statutory handling in section 3 to be real rather than claimed.

Most Indian companies of any size are two of these at once, and that is the actual difficulty. A manufacturer has a shop floor and a head office, with different attendance rules, different leave patterns and often different entities. When you write down what you are, write down both populations, and treat the smaller one as a first-class requirement rather than an exception. The exceptions are what break configurations.

The third is where your salary structure already is. If your components map cleanly to the wage definition and your CTC breakup is conventional, migration is a fortnight of work. If you have accumulated twenty-two components over a decade, including three that exist because of one person who left in 2019, the software is not your problem and no product will fix it. Clean this up before you migrate rather than after. Migrating a mess reproduces the mess with better reporting on it. Our guide to CTC breakup in India is the structure most products expect to find.

The fourth is who will own the system. Name the person. Not the department, the person. Then ask how many hours a week they have, and what else they are responsible for. This is the single best predictor of whether an implementation lands, and the one nobody writes down. A product that needs six hours a week of an owner's attention and gets one hour will fail regardless of how good it is. A simpler product that fits the hours available will succeed. If the honest answer is that nobody has any hours, that is a finding, and it points towards a narrower buy or towards outsourcing rather than towards a broader one.

Write those four down on one page, and open every vendor conversation with it rather than with questions. The response is itself a data point. A vendor who immediately says one of your four things is outside what they do well has just saved you two months.

The Platforms, By Fit Rather Than Rank

Eleven platforms an Indian buyer genuinely shortlists when the buy is a suite rather than a single function. Engage is first because we make it. The other ten are alphabetical and the order means nothing. Each entry says who it genuinely suits, who it does not, and one thing to verify on a demo, because the demo is where fit claims either survive or do not.

Do not read the table as a scoreboard. The useful column is the second, which says what shape of buy each product is built for. A product that is excellent in a shape you are not buying is still the wrong answer.

Engage HRMS

Core HR, attendance, leave and payroll run off one record rather than an integration. That is the whole argument for buying a suite, and it decides how bad your month end is. Statutory coverage goes past the four heads everybody does, to labour welfare fund, the quarterly salary statement, investment declarations and proofs, Payment of Bonus Act computation, gratuity and the annual salary TDS certificate. Salary journals post to Tally, Zoho Books and QuickBooks. Bank transfer files come out in the bank's prescribed format. Single sign-on works with Google Workspace, Microsoft Entra ID and Okta. Hosting is in an Indian data centre region and we hold ISO 27001. Suits Indian companies with mixed office and field or shift populations, single or multi-site, that want one record rather than two. On a demo, ask us to move an employee between two of your entities mid-year, and show what happens to professional tax, labour welfare fund and continuous service.

Darwinbox

Built for enterprise, deployed widely across large Indian and South-East Asian organisations, with configuration depth that goes well past payroll and multi-country handling that works rather than being claimed. Suits organisations above roughly a thousand people with a governance function that will ask for audit trails on everything, and with operations in more than one country. Does not suit small and mid-sized companies, where implementation is a project measured in months against a problem that did not need one. On a demo, ask how long a new salary component takes to configure and who does it. Configuration depth and configuration speed are not the same property, and this platform trades one for the other.

factoHR

Strong where the workforce is industrial. Shift handling, overtime and workforce management around the payroll engine are deeper than most, and the statutory handling for factory environments is real. Suits manufacturers and multi-state operations, particularly groups with plants in several states and a mix of permanent and contract labour. Does not suit a company with an office-only population and a simple requirement, where the breadth of the suite becomes configuration effort you get nothing back for. On a demo, ask to see a contract labour population handled inside the system rather than beside it. That is the specific thing this product is for, and the specific thing most competitors handle with a spreadsheet.

greytHR

The long-established default for Indian small and mid-sized employers, with statutory payroll knowledge built up over a long period, and documentation detailed enough that it usually answers a specific scenario question before a conversation does. Suits companies under a few hundred people buying a payroll-led core, especially where statutory correctness is the first requirement and attendance is straightforward. Does not suit complex shift patterns or field capture, where attendance depth is lighter than the specialists, and parts of the interface show their age. On a demo, ask what a mid-year change to a statutory rate costs you as a user. The answer describes how the whole product is maintained.

HROne

A mid-market suite with unusually wide biometric device integration and a workflow engine deeper than most at its level. Suits companies that have inherited a mixed set of readers across several sites and would rather configure around them than replace them, and companies whose approval chains are genuinely complicated. Does not suit very small deployments, where you are configuring a mid-market platform to do a small company's job. The device breadth buys you nothing if you are starting fresh, or if your people never pass a fixed reader. On a demo, ask them to connect one of your actual reader models rather than a reference device.

Keka

The usability leader in this category. For companies whose real problem is adoption rather than compliance, that is a stronger argument than it sounds. A system employees actually open for declarations, claims and payslips removes more HR work than one with two extra statutory heads. Suits IT services companies and funded startups with office populations. Does not suit shifts, piece rates or contract labour, where payroll inputs come from a shop floor rather than a leave calendar. On a demo, ask what happens to a rostered employee whose shift crosses midnight.

Pocket HRMS

Sized for small Indian employers, which is a design decision rather than a shortcoming. A forty-person company can run payroll and attendance on it without a dedicated payroll person, and without configuring a larger platform downwards. Suits a payroll-led core under a couple of hundred people. Does not suit a company expecting to double inside two years, where you are buying a migration along with a product. On a demo, ask what the export looks like, because you will want it sooner than you think.

SAP SuccessFactors

Enterprise core HR built for standardising process across many countries, with the governance, reporting and role-based access an organisation of that size needs. Suits multinationals above a few thousand people, where the Indian entity is one of many and global consistency outranks local convenience. Does not suit a company whose problem is Indian statutory payroll, which generally arrives through a local payroll engine or partner rather than from the core. On a demo, ask specifically who owns the Indian statutory updates, and on what schedule they reach you.

Workday

Strong enterprise core HR, workforce planning and analytics, with an object model that holds complex organisational structures well. Suits large multinationals treating HR as a planning function as much as an administrative one. Does not suit an Indian company whose central requirement is a correct payslip under the Codes, because Indian statutory payroll sits outside the core and depends on what you connect to it. On a demo, ask to see a full Indian payslip produced end to end, and ask which component of the stack produced it.

Zimyo

Broad suite at a mid-market cost, with core HR, payroll, attendance, leave and performance in one place. Suits a cost-conscious company of a few hundred people that wants one system rather than three, and can accept that breadth is spread out rather than concentrated. Does not suit a company with statutory edge cases, which is where thin depth shows first. On a demo, ask about labour welfare fund across your specific states, bonus computation and a retrospective revision, in that order.

Zoho People

Core HR and leave that integrate with the rest of the Zoho estate in a way nothing else will, which is a legitimate reason to choose it if you already run Zoho for accounting or CRM. Suits companies inside that ecosystem buying a best-of-breed component rather than a suite. Does not suit a buyer who wants payroll on the same record, because payroll is a separate product and the seam in section 6 applies. On a demo, ask to watch attendance data move into payroll, and note how many steps it takes.

The Seams Between Modules

A seam is any place where one module's output is another module's input. Every seam has a data contract, whether or not anybody wrote one down, and unwritten contracts are where suites fail. This is the section that separates a real suite from a feature list, because a feature list has no seams in it.

The busiest seam in an Indian company is attendance into payroll, and the interesting question is not how attendance is captured. That belongs to the attendance comparison linked in section 1. The suite question is about ordering and authority. When does the attendance month lock, when does payroll lock, and what happens to a regularisation approved in the gap between them. Most systems handle the happy path. Fewer have a defined answer for an approved regularisation that arrives after payroll has been processed. The answer you want is an arrears entry in the next cycle with a visible trail, not a silent recomputation, and not a manual adjustment somebody remembers to make.

The second seam is leave into attendance, which looks trivial and is not, because it creates two records of the same absence. If leave and attendance are separate modules with separate approvals, an employee can be on approved leave and marked absent at the same time, and whichever module payroll reads decides whether they get paid. Ask which one wins, and why.

The third is core HR into payroll, and the issue there is effective dating. A promotion effective 1 April, entered on 12 July, has to reach back and recompute. Whether the system treats that as a new record with a date, or as an edit to the existing one, decides whether you can reconstruct what the salary was in May. If you cannot, your first dispute becomes an exercise in reading old emails.

The fourth is recruitment into onboarding, which is low-traffic and high-value. If the candidate record becomes the employee record without re-entry, a day of retyping and a class of errors disappear together.

Now the point most buyers miss. One vendor does not guarantee one record. Suites assembled over time, or by acquisition, carry internal seams that behave exactly like integrations between two companies' products, except that you cannot see them from outside and nobody will describe them to you. The test is not the org chart of the vendor. It is a demo question. Change an employee's department, their location and their salary in one action, then show me every module where that change landed and the timestamp on each. A single record produces one timestamp. Two records produce two, and the gap between them is where your reconciliation will live. Our payroll compliance checklist is a reasonable script for testing the statutory end of the same thing.

What Buyers Get Wrong

These are mechanical rather than anecdotal, in the sense that each one follows from how the buy is structured rather than from anybody being careless.

Buying breadth that never gets configured. This is the most common and the most expensive, and it is specific to suite buys. A company buys eleven modules, configures core HR, payroll, attendance and leave, and never turns on performance, learning or recruitment. Turning a module on is a project with an owner and a policy decision behind it, and nobody has either. Two years later the licence covers modules nobody has opened. The defence is to decide at purchase which modules go live in year one, and to treat the rest as an option you have not exercised. Then check the commercial model actually supports that, rather than charging for the full set from day one. If performance management or hiring is genuinely coming later, say so and make it a milestone rather than an assumption.

Underestimating implementation and data migration. The software is almost never the variable. The variable is the state of your existing data, and how quickly your team can answer configuration questions. That is why implementations stall in the middle rather than at the start. Opening balances, leave balances, year-to-date figures, and enough salary history to produce a correct annual certificate, are all work regardless of who does it.

Choosing on demo polish. A demo is a rehearsed path through a clean data set. It tells you about the interface and almost nothing about the engine. The correction is to stop watching demos and start setting them. Bring one of your own messy employees, with a mid-year transfer between states, an approved regularisation and a retrospective increment, and ask the vendor to produce the outcome.

Ignoring the seam between attendance and payroll. Covered in section 6, and worth repeating here, because it is the seam that costs money every single month rather than once.

Not checking who actually does the statutory filings. This is the question buyers most often assume the answer to. Some products compute and file. Some compute and hand you a file to upload. Some compute and leave the filing entirely with you. All three are legitimate, and the difference is several hours a month, plus the question of who is answerable when a return is late. Ask it explicitly, head by head, and write the answer down.

Questions People Ask

Which is the best HR software in India for a mid-sized company?

There is no single answer, because it turns on your situation rather than on the product. Between roughly 150 and 1,000 employees the deciding factor is workforce type, not headcount. Office-only populations are well served by Keka, Zimyo and us. Shift and factory populations narrow the list quickly to factoHR and us. Statutory-first buyers with simple attendance do well with greytHR. Establish which of those you are before you compare anything.

Should we buy one HR suite or separate payroll and attendance systems?

Decide it on seam traffic rather than on preference. If attendance feeds payroll every month for a population of any size, that is a high-traffic seam with a monthly cost attached, and it belongs inside one system on one record. If the functions barely exchange data, separate systems chosen on merit are a legitimate and often better answer. The thing to avoid is buying them separately by accident, which is what happens when payroll is bought first and attendance is added a year later.

How long does an HRMS implementation take in India?

For a single-state company under 200 people with clean data, four to six weeks is realistic, including a parallel payroll month. Multi-state, multi-entity or contract labour in the mix pushes it to two or three months. The software is rarely the variable. What decides it is the state of your existing data, and how fast your team answers configuration questions. That is why implementations stall in the middle rather than at the start.

Can HR software handle multi-state and multi-entity compliance?

Some can, and many handle it partially, which is worse because it is harder to detect. Three things to test specifically. Whether professional tax and labour welfare fund follow an employee who transfers states mid-year. Whether entity is modelled as a first-class object with its own statutory registrations rather than as a label on an employee record. And whether continuous service survives a transfer between two group entities with separate PF codes. Ask for all three on a demo, using your own structure.

Which HR modules do companies buy and never use?

Performance management, learning and recruitment, roughly in that order. Not because the modules are poor, but because turning one on requires a policy decision and an owner, and a suite buy supplies neither. The practical response is to name at purchase which modules go live in year one, treat the rest as options you have not exercised, and confirm the commercial arrangement actually reflects that rather than charging for everything from day one.

Where This Leaves You

Do these in order. Decide the shape of the buy before you look at a product, using the seam traffic test in section 2. Write down the four things in section 4, particularly who will own the system and how many hours they have. Take section 3 and check which statutory obligations your chosen shape leaves without an owner. Then, and only then, shortlist from section 5 on fit rather than rank, and set the demos yourself with one of your own messy employees rather than watching a rehearsed path. Ask the single-record question from section 6 of every vendor, and ask who does the filings, head by head.

If you want to run that against us, our HR management software is the suite. Payroll and attendance sit on the same record rather than either side of an integration, and pricing is published. Bring your four-line description of your own company.

Sources

• Ministry of Labour and Employment, labour.gov.in. Commencement of the four Labour Codes on 21 November 2025; the Employees' Provident Funds Scheme, 2026 effective 29 June 2026; and the provident fund wage ceiling of ₹25,000 notified on 17 September 2026 under Chapter III of the Code on Social Security, 2020, superseding the notification of 29 May 2026.
• Code on Wages, 2019, enacted text on India Code, indiacode.nic.in. Section 2(y) on the definition of wages and the one-half proportion rule, and section 14 on overtime at not less than twice the normal rate.
• Code on Social Security, 2020, enacted text on India Code, indiacode.nic.in. Section 53 on gratuity, including one year of continuous service for fixed-term employees, and the creche obligation at fifty employees.
• Occupational Safety, Health and Working Conditions Code, 2020, section 6. Appointment letter for every employee.
• Income Tax Department, incometax.gov.in. The Income-tax Act, 2025, section 392 on deduction from salary, and the Income-tax Rules, 2026 renumbering Form 24Q to Form 138, Form 16 to Form 130 and Form 12BB to Form 124 for salary paid from 1 April 2026.
• Employees' State Insurance Corporation, esic.gov.in. Contribution rates of 3.25 per cent and 0.75 per cent and the ₹21,000 wage ceiling, in force since July 2019.
• Constitution of India, Article 276(2). The ₹2,500 per person per annum cap on professional tax.
• Finance Department, Government of Odisha. Repeal of professional tax with effect from 1 April 2026.
• Sexual Harassment of Women at Workplace (Prevention, Prohibition and Redressal) Act, 2013, sections 4 and 21. Internal committee at ten employees and the annual report.

Product descriptions above are our reading of what each platform is built for, based on vendor documentation and product observation. No ratings, scores, rankings or review counts from any software directory are used anywhere on this site. Nothing here describes how any company markets, prices publicly or positions itself. Test every claim, including ours, against the product.