TL;DR: HR shared services is the model in which a central team runs the transactional, rules-based work of HR, such as onboarding, employee records, payroll, benefits administration and exits, while HR business partners stay close to the business on the judgement calls. For a company operating across several Indian states, the design question is not whether to centralise but what to centralise, how to handle state-by-state variation, and what service levels the centre commits to. Hire-to-retire is the process spine; payroll is the hardest part of it, because every cycle has to apply central rules, state rules and location rules correctly. The timing matters: the Union Cabinet approved raising the EPFO wage ceiling for mandatory coverage from ₹15,000 to ₹25,000 a month on 16 September 2026, which changes who is covered and what payroll must calculate. The lever is governance and service levels, not software.
Most multi-location companies do not design their HR operations. They accumulate them. The first office runs HR from the founder’s desk; the second office hires its own administrator; the third state brings a new payroll vendor because the old one did not cover it. By the fifth location, the company has four ways of onboarding, three payroll calendars and nobody who can say, with confidence, that every employee in every state was paid correctly last month.
HR shared services is the answer to that drift, but only when it is designed rather than assembled. People strategy is business strategy, and in a multi-location company the operating model for HR is where that strategy either becomes consistent or breaks into local habits.
HR shared services is not a niche model. Deloitte’s 2021 Global Shared Services and Outsourcing Survey found HR present in 57% of successful multifunctional global business services organisations, second only to finance at 94% and ahead of procurement at 54% and IT at 52%.
What HR Shared Services Actually Centralises, and What Stays With the HR Business Partner
The most common design mistake is centralising the wrong things. HR shared services works when it takes the high-volume, rules-based work away from local teams and leaves the judgement-based work with people who know the business. A three-part HR model makes the split clear:
| Part of the HR model | What it does | Examples |
|---|---|---|
| HR shared services | Runs transactional, rules-based processes at scale, to a defined service level | Onboarding documentation, employee records, payroll, statutory filings, benefits administration, letters, exit settlements, employee queries |
| Centres of expertise | Designs policy and programmes where specialist knowledge matters | Compensation design, performance management frameworks, learning, labour law interpretation |
| HR business partners | Advise business leaders on people decisions | Workforce planning, organisation changes, talent reviews, employee relations cases, leadership coaching |
The test for what belongs in shared services is simple. If the task follows a rule, happens often and produces the same output wherever it is done, it belongs in the centre. If it depends on context, relationships or judgement about a specific team, it stays with the business partner or the line manager.
The Astravise Agile Shared Services practice covers four HR service lines on this basis: payroll, recruitment support, HR operations covering onboarding, documentation and employee queries, and hire-to-retire lifecycle management. The rest of this article explains how to design those lines for a company operating in several states.
The Hire-to-Retire Process Map: Stage by Stage
Hire-to-retire, often shortened to H2R, is the end-to-end process that covers every administrative event in an employee’s working life with the company, from the offer to the final settlement. It is the HR equivalent of the process towers finance shared services runs. The Astravise guide to record-to-report, procure-to-pay and order-to-cash sets out the finance side of the same design logic.
The useful way to map H2R is not by activity but by ownership. At each stage, the design has to say what the shared services centre does, what the business partner or manager retains, and where the handoff sits:
| Stage | Shared services centre owns | HR business partner or manager retains | Typical handoff risk |
|---|---|---|---|
| Recruit | Scheduling, offer letters, background verification coordination | Role definition, selection decision | Offer terms that do not match the grade structure |
| Onboard | Documentation, statutory registrations, system set-up, day-one payroll inclusion | Induction into the team, first-90-day goals | Joiner missed from the first payroll or wrong state tagged |
| Manage | Employee records, attendance and leave administration, letters, query handling | Performance conversations, development decisions | Record changes not reflected in payroll |
| Move | Transfer documentation, location and entity changes in the system | Transfer decision, role and team change | Statutory deductions left on the old location |
| Reward | Payroll, reimbursements, benefits administration, statutory remittances | Increments, promotions, variable pay decisions | Approved changes arriving after payroll cut-off |
| Exit | Full and final settlement, relieving documents, statutory closures | Exit decision, retention conversations, knowledge handover | Settlement delayed or gratuity miscalculated |
Recruitment is the first stage of H2R but usually a separate operating system in its own right. The Astravise view on RPO 2.0 and recruitment as a governed operating system covers how to govern that stage in depth; in an HR shared services design, the centre typically owns the administrative handoff from offer to joining.
Where Hire-to-Retire Breaks in a Multi-Location Company
A single-location company can run H2R on habit. A multi-location company cannot, because the same event carries different obligations depending on where the employee sits. The failure modes are predictable:
-
The transfer that payroll never hears about. An employee moves from one state to another. The manager approves it, the employee relocates, but the location field in the payroll system is not updated. Professional tax continues to be deducted and remitted for the old state, and nothing is deducted for the new one.
-
The office that runs its own onboarding. A regional office collects different documents, uses an older appointment letter and skips a registration step. Nobody notices until an audit or a transaction.
-
The late joiner. Joining data arrives after the payroll cut-off, the employee is paid late, and a manual off-cycle payment bypasses the normal controls.
-
The exit that closes in one system and not another. The employee leaves, the settlement is paid, but access, insurance or statutory records stay open.
-
The local vendor nobody reviews. A payroll or compliance vendor engaged for one state follows its own calendar and formats, and the central team has no view of what it filed.
The underlying problem is the same in each case: a process designed at head office assumed to work everywhere. The same gap appears in other compliance areas. The Astravise guide to PoSH compliance for multi-location employers shows how a head-office Internal Committee does not make every office compliant, and the same principle applies to payroll.
Payroll Controls Across States: What Has to Be True Every Cycle
Payroll is the hardest part of H2R to centralise because it sits on three layers of rules at once. A payroll design for a multi-location company has to handle all three explicitly:
-
The central layer. Rules that apply everywhere: provident fund, employees’ state insurance where applicable, income tax deduction at source, gratuity provisioning and the definition of wages under the Code on Wages, 2019.
-
The state layer. Rules that vary by state: professional tax, labour welfare fund contributions, shops and establishments registrations, and state-notified minimum wages, each with its own rates, frequencies and due dates.
-
The location layer. The data that tells the system which state rules apply to which employee: work location, entity, establishment registration and any mid-cycle transfer.
Most payroll errors in multi-location companies are not errors in the central layer. They come from the location layer being wrong, which sends the state layer to the wrong place.
Professional tax is the clearest example. Article 276(2) of the Constitution of India caps the total professional tax payable by any one person to a state, or to any local authority in it, at ₹2,500 a year. Within that cap, each state that levies the tax sets its own slabs, deduction frequency and due dates, and several states do not levy it at all. A payroll centre therefore needs a maintained state-by-state rule table, reviewed against each state’s own notification, rather than one rate applied everywhere.
The controls that should hold every cycle:
-
Location master reconciled to the HR record before each run, with transfers effective from a defined date.
-
State rule table reviewed on a set calendar and whenever a state notifies a change, with an owner and a sign-off.
-
Variance review of each run against the previous one, by state and by component, with explanations for every material movement.
-
Statutory remittance calendar by state and by central scheme, tracked to proof of payment rather than to “submitted.”
-
Maker-checker separation between the person who changes pay data and the person who approves the run.
-
Off-cycle payments limited, logged and reviewed monthly.
The Code on Wages definition of wages, which deems allowances above 50% of total remuneration to be wages, changed the base on which several of these calculations run. The Astravise analysis of the four labour codes in practice sets out what that change costs across provident fund, gratuity and other heads.
The 2026 Wage-Ceiling Shift and Why Payroll Has to Recompute It
On 16 September 2026, the Union Cabinet approved raising the wage ceiling for mandatory coverage under the Employees’ Provident Fund Organisation from ₹15,000 to ₹25,000 a month. The ceiling was last revised in September 2014. The government expects more than 51 lakh additional employees to come under mandatory EPFO coverage. The Hindu reported that the new ceiling is to apply from 17 September 2026, and quoted Labour Minister Mansukh Mandaviya as saying the employer’s contribution will rise by ₹600 per employee, with the pension contribution rising to about ₹2,082.50 a month, 8.33% of the new ceiling, from ₹1,250. The Cabinet release states that the Ministry of Labour and Employment and EPFO will take the statutory and administrative steps to implement the decision, so payroll teams should track the formal notification and EPFO’s guidance on how the change applies to part-month contributions.
For an HR shared services centre, the change creates four immediate tasks:
-
Identify newly covered employees. Anyone earning above ₹15,000 and up to ₹25,000 a month who was previously outside mandatory coverage needs to be enrolled.
-
Recompute contributions for employees whose contributions were capped at the old ceiling, including the pension component.
-
Update the cost forecast. The employer’s contribution increases for every affected employee, which feeds straight into the payroll budget.
-
Communicate to employees, because take-home pay changes for anyone whose deduction increases.
The employees’ state insurance ceiling, by contrast, has not moved since 1 January 2017. According to the Ministry of Labour and Employment, ESI covers employees drawing wages up to ₹21,000 a month, or ₹25,000 a month for persons with disability. A payroll centre that runs both schemes has to apply two different thresholds to two different wage definitions, which is exactly the kind of rule that belongs in a centrally maintained table.
Payroll: In-House, Outsourced or Shared Services
Every multi-location company eventually faces the payroll sourcing decision. The three options are not mutually exclusive, and many companies end up with a hybrid.
| In-house at each location | Outsourced to a payroll provider | HR shared services centre | |
|---|---|---|---|
| Control over rules and data | High locally, low centrally | Depends on the contract and reporting | High centrally |
| Consistency across states | Low | Medium to high, if one provider covers all states | High |
| Cost at small scale | Low | Low to medium | Higher, until volume builds |
| Cost at large scale | High, through duplication | Medium | Lower, through standardisation |
| Main risk | Drift and key-person dependency | Loss of visibility and vendor lock-in | Under-investment in the rule table and service levels |
| Best fit | Very early stage, single state | Growing company without in-house payroll expertise | Multi-location company with enough volume to standardise |
Outsourcing payroll does not outsource accountability. The employer remains responsible for statutory deductions and remittances whether a vendor processes them or not. That is why the common hybrid works well: a shared services centre owns the data, the rule table, the controls and the service levels, while a provider runs the calculation engine and filings under the centre’s supervision.
For the wider case for centralising support functions as a company grows, the Astravise perspective on shared services as a growth lever covers the economics.
Designing the SLA Layer: Response Times, Escalations and What Good Looks Like
Service levels are what turn a central HR team into a shared service. Without them, the centre is simply another department that employees and managers have to chase. The design has three parts: tiers, targets and escalation.
Tiers. A tiered model routes each request to the cheapest point that can resolve it correctly:
| Tier | Who handles it | Typical requests |
|---|---|---|
| Tier 0 | Self-service portal and knowledge base | Payslips, leave balances, policy documents, standard letters |
| Tier 1 | Shared services generalists | Record changes, onboarding queries, reimbursement status, general payroll questions |
| Tier 2 | Shared services specialists | Payroll exceptions, statutory queries, full and final settlements, transfers between states |
| Tier 3 | Centres of expertise or HR business partners | Policy interpretation, employee relations, compensation exceptions |
Targets. Each tier needs a response target and a resolution target, and payroll needs its own accuracy and timeliness measures. The right numbers depend on the company, but the measures should include:
-
Payroll accuracy: share of payslips issued without a correction in the following cycle.
-
Payroll timeliness: salary credited on the committed date, every cycle, in every state.
-
Statutory timeliness: remittances and returns filed by the due date, by scheme and by state.
-
Query resolution: share of requests resolved within target at each tier.
-
Onboarding completeness: share of joiners with complete documentation and correct payroll set-up before their first payroll.
-
Settlement time: days from last working day to full and final settlement.
Escalation. Every service level needs a named escalation path: who is told when a target is missed, how quickly, and who decides on the fix. Payroll errors that affect take-home pay should escalate faster than any other category.
Service levels also need a forum. A monthly review between the shared services lead and the HR business partners, looking at the measures above by location, is what keeps the centre accountable to the business rather than to itself.
How Astravise Services Designs an HR Shared Services Operating Model
Astravise Services designs HR shared services as part of its Agile Shared Services practice, with the people-strategy decisions led through its Strategic CHRO advisory. The work follows five steps:
-
Map the current state by location. Document how each office and each state runs onboarding, records, payroll, statutory filings and exits today, including every vendor involved.
-
Decide the split. Agree what moves to the centre, what stays with HR business partners and managers, and what the handoffs look like at each H2R stage.
-
Build the rule table and controls. Set up the central, state and location layers for payroll, with owners, review dates and the cycle controls described above.
-
Set the service levels. Define tiers, targets, escalation paths and the monthly review, and agree them with the business before go-live.
-
Migrate in waves. Move locations into the centre one group at a time, running parallel payrolls until the numbers reconcile.
The model has to be owned at a senior level, because it changes how every manager in the company gets HR support. Where a company does not yet have a senior HR leader to own that decision, the Astravise guide to when to engage a fractional CHRO sets out the scope and cost of bringing one in.
Frequently asked questions
- What is the difference between HR shared services and an HR business partner?
- HR shared services is a central team that runs transactional, rules-based HR processes such as onboarding documentation, employee records, payroll, benefits administration and exits, to defined service levels. An HR business partner works alongside business leaders on judgement-based people decisions such as workforce planning, organisation changes, talent reviews and employee relations. The shared service handles volume; the business partner handles context.
- What does the hire-to-retire process cover?
- Hire-to-retire covers every administrative event in an employee’s working life with the company. It is usually mapped in six stages: recruit, onboard, manage, move, reward and exit. In an HR shared services design, each stage is split between what the central team owns, such as documentation, records, payroll and settlements, and what the HR business partner or manager retains, such as selection, performance and transfer decisions.
- Can payroll be run from a shared services centre across multiple Indian states?
- Yes, provided the payroll design handles three layers of rules: central rules such as provident fund and income tax, state rules such as professional tax, labour welfare fund and minimum wages, and location data that tells the system which state rules apply to each employee. Most multi-state payroll errors come from incorrect location data, so the location master and transfer process need the strongest controls.
- What is professional tax, and does it apply in every state?
- Professional tax is a tax on professions, trades, callings and employments levied by states and local authorities. Article 276(2) of the Constitution caps it at ₹2,500 per person per year. Not every state levies it, and those that do set their own slabs, deduction frequency and due dates, so rates and dates should be checked against each state’s own notification.
- How does the EPFO wage ceiling change affect payroll processing?
- The Union Cabinet approved raising the EPFO wage ceiling for mandatory coverage from ₹15,000 to ₹25,000 a month on 16 September 2026, with more than 51 lakh additional employees expected to be covered. Payroll teams need to identify newly covered employees, recompute contributions that were capped at the old ceiling including the pension component, update the employer cost forecast and explain take-home pay changes to affected employees, while tracking the formal notification and EPFO guidance.
- What SLAs should an HR shared services centre commit to?
- An HR shared services centre should commit to response and resolution targets for each service tier, from self-service through specialist and expert escalation, plus specific payroll measures: payroll accuracy, salary credited on the committed date in every state, statutory remittances and returns filed on time, onboarding completeness before the first payroll, and days to full and final settlement. Each targ