Two locations is where the spreadsheet finally breaks
The second branch doubles the work and halves the visibility. Different holidays, a different PT slab, a manager who reports attendance differently — and one payroll that has to absorb all of it.
Run HR across branches and states
Rules Follow The Workplace
Professional tax, holiday calendars and minimum wages apply by location, which is the thing multi-state companies most often get wrong.
One Headcount View
People, attendance and cost by branch, so a location’s numbers can be checked rather than reported.
One Payroll Run
A single run covering every location, with each employee treated under their own workplace rules.
The second location does not double the work
It more than doubles it, because the second location is not a copy of the first. It has its own holidays, possibly its own professional tax slab, its own minimum wage notification, and a manager with his own way of reporting attendance.
And it halves the visibility, because now somebody has to consolidate before anybody can see the whole picture.
Rules follow the workplace
This is the point most systems get wrong, and the error is invisible until you have two locations. Professional tax follows the place of work, not the registered address. So do labour welfare fund and the holiday calendar.
A system that resolves these from the entity rather than the workplace produces correct output for every single-location company — and quietly wrong output for exactly the companies that needed a multi-location system.
One run, one view
A single payroll run covers every location, with each employee treated under the rules that apply where they actually work. Headcount, attendance and cost are visible per branch without anybody at a branch producing a report.
That second part matters more than it sounds. Consolidation done by asking each location for a sheet is consolidation that is always a week old and never quite reconciles.
Where each rule is decided
The workplace
Professional tax, labour welfare fund and holidays resolve from where the person works.
The entity
Registrations, statutory numbers and filings sit here, above the workplace.
One payroll run
Every location in a single run, each employee under their own applicable rules.
One view
Headcount, attendance and cost per branch, without asking a branch for a sheet.
Run HR across branches and states FAQs
Do we need separate registrations per state?
For professional tax, generally yes where it applies. Registration and remittance are state-specific, and one registration does not cover employees working elsewhere.
Can each branch have its own holiday list?
Yes — that is the normal case. Holidays resolve per workplace, and a branch can have a different list from the head office without anything being duplicated.
What about employees who move between locations?
The assignment history records the move with an effective date, and the location-driven rules follow from that date. The register shows where they actually worked.
Is it one payroll run or one per branch?
One run covering everybody, with the location-specific rules applied per employee. You still get cost and headcount broken out per branch.
Do all locations have to follow the same rules?
No — and they usually cannot, because holidays, professional tax and welfare fund obligations differ by state. Policies resolve by location rather than by company.
Can a regional manager see only their locations?
Yes, scope follows role. Reporting that ignores scope is how salary data travels further than intended.
Try it on your own payroll
Fourteen days, no card, and every record exports back out if you decide against it.