Loading page
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
Multi-branch, multi-state businesses, roughly 100 to 1,000 people
The defining difficulty of a mid-market Indian business is that its branches are one organisation operationally and several distinct compliance positions statutorily, and both have to be true at once.
A business with a head office in Pune, a branch in Bengaluru and a unit in Hyderabad experiences itself as one company. Its employees move between locations, its leadership reads one set of numbers, and its culture is singular.
Statutorily it is nothing of the sort. Professional Tax is a state subject with different slabs and different due dates. Leave entitlements sit under state Shops and Establishments Acts. Registrations, returns and inspections are per location. If there are multiple legal entities, payroll is legitimately several payrolls that leadership nonetheless wants to see as one.
Software that handles this badly forces a choice: run three instances and lose the consolidated view, or run one and hand-adjust the state differences every month. Both are common. Neither is necessary.
The renewal date of the current HR or payroll tool is coming up.
An acquisition or a new entity means two payrolls, two leave policies and one board asking for combined headcount.
A new head of HR joins and inherits several tools and a monthly report built by hand.
An appraisal cycle fails, or attrition jumps and nobody can say where it is concentrated.
Not a feature gap, the specific operational pressures this kind of company runs into, and why each one resists a spreadsheet.
Maharashtra's Professional Tax behaves differently in February. Several states apply gender-specific exemptions. Labour Welfare Fund deductions are half-yearly in some states and annual in others. Holding these as per-state rules rather than a single default is the whole game.
At thirty people everyone knows who approves what. At four hundred across three cities, an approval hierarchy has to be configured, by grade, by location, with escalation, or requests simply stall with whoever happens to be on leave.
A consolidated headcount and payroll cost figure across entities is what the board asks for. Entity-level statutory totals that reconcile to what was actually filed is what finance needs. Both have to come from the same run.
Many mid-market businesses have both. One population is salaried and desk-based; the other is shift-based with overtime, night differentials and comp-off. A single policy engine has to express both without two systems.
You do not have to switch everything on at once, and for a company like yours there is a sensible order. This is it, with the reasoning attached.
The defining administrative fact about a mid-market Indian business is that it is usually more than one legal entity. A manufacturing arm and a services arm. A holding company and an operating company. A subsidiary created for a specific client or a specific state.
Each entity carries its own PF and ESI registrations, its own professional tax registrations in the states where it employs people, and its own payroll run and returns. Employees, meanwhile, move between them, on promotion, on transfer, or because the group reorganised.
The requirement that follows is precise: entity has to be an attribute of the employee record rather than a separate installation of the system. Otherwise a transfer means recreating the person, and recreating the person breaks continuity of service, which is what gratuity eligibility and leave accrual are both computed from.
At forty people an approval is whoever is nearest. At four hundred it is a chain, and the chain has to keep working when a link is on leave, has moved department or has left the company.
Three properties do most of the work here. Routing reads the current reporting line on the record, so a request never arrives with someone who has left. A delegate can be named for a period, so approvals do not stall during a holiday. And a threshold can require a second approver, for leave beyond a number of days, or for an expense above an amount, without requiring a second approver for everything.
What this replaces is the informal escalation that mid-market companies otherwise depend on, where a stuck request is resolved by walking to somebody's desk. That works until the person is in another building.
The uncomfortable arithmetic of the mid-market is that HR administration scales roughly with headcount unless something changes, so a company that doubles adds an HR person to do the same work twice.
The parts that scale linearly are the ones worth attacking: answering lookup questions, chasing documents and approvals, assembling reports, and re-keying between systems. Each of these is removed by a different mechanism, self-service, automated reminders, reporting that reads the live record, and integration by architecture rather than by export.
What does not scale away is judgement: policy exceptions, grievances, appraisal calibration, difficult conversations. A useful test when evaluating an HR management system at this size is whether it reduces the first list without pretending to reduce the second.
Multi-entity and multi-location structures sit under a single login, with role-based permissions deciding who sees which entity. The Enterprise plan adds single sign-on and advanced security, along with succession and lifecycle modules and a dedicated success manager.
Multi-entity structures are supported under one login, with permissions determining who can see which entity. Payroll runs remain distinct per entity, as they must be for filing, while reporting consolidates across them.
Yes. Leave schemes and holiday calendars are configured per location and grade, which is what allows a company operating across states to be compliant in each without maintaining separate systems.
State-specific rule sets are configured for Maharashtra, Karnataka, Telangana, Tamil Nadu, Andhra Pradesh, Gujarat and West Bengal, including the February slab change and gender-specific exemptions where a state provides them. Applicability follows the employee's work location on the record.
Not the parts that scale linearly. Lookup questions, chasing documents and approvals, assembling reports and re-keying between systems are removed by self-service, automated reminders, live reporting and one shared record. Judgement work such as policy exceptions, grievances and appraisal calibration does not scale away.
It is preserved, because the transfer is a dated change on the existing record rather than a new record. This matters concretely: gratuity eligibility and leave accrual are both computed from the original date of joining, and an employee who is recreated has, on paper, started again.
A delegate can be named for a period, and routing reads the current reporting line rather than a fixed list, so requests do not stall or arrive with someone who has left. Thresholds can require a second approver for larger requests without adding one to every request.
Yes. One population is salaried and desk-based; the other is shift-based with overtime, night differentials and comp-off. A single policy engine expresses both, so the business does not need two systems.
The Enterprise plan adds single sign-on and advanced security, along with succession and lifecycle modules and a dedicated success manager. Multi-entity and multi-location structures sit under one login, with role-based permissions deciding who sees which entity.
Looking for a custom walkthrough or have specific statutory policy requirements? Connect with our product specialists in Pune for a 1-on-1 consultation.
14-day free trial · Full access to all 12 modules · Zero implementation fee · Cancel anytime