Running payroll for multi-branch businesses in India

Payroll for one office is a monthly routine. Payroll for five branches across two or three states is a different job. Holidays differ by location, shifts differ by site, statutory deductions differ by state, and every difference is a chance for a salary to be wrong.

This guide covers the decisions that keep a multi-branch payroll accurate, whatever software you use.

Give each branch its own calendar

The first source of errors is usually the holiday list. Regional festivals and state holidays mean that a working day in one branch is a paid holiday in another. Keep a holiday calendar per branch, and make sure attendance reads from the right one. A single company-wide calendar forces HR into manual corrections every month.

The same applies to weekly offs. A retail branch may close on Tuesdays while head office closes on Sundays.

Turn attendance into paid days by rule

Payroll is only as good as the attendance behind it. For each branch, define:

• Shifts, including grace periods for late arrival and proper handling of night shifts that cross midnight.
• Rosters, so people on rotating shifts are judged against the shift they were actually assigned.
• Late-in, early-out, half-day and overtime rules, written once and applied the same way to everyone.
• Regularisation, so a missed punch can be corrected with an approval trail instead of a quiet edit.

When these rules are in the system, loss of pay and overtime come straight from attendance. When they live in someone's head, they get applied inconsistently.

Handle statutory rules by state

Provident Fund and ESI follow national rules, but some deductions depend on where the employee works. Professional tax is levied by states, with different slabs, and some states do not levy it at all. Labour welfare fund contributions also vary from state to state.

The practical answer is to keep statutory rules as slabs you control, attached to the branch or state, rather than hard-coded in the software. When a state revises its slabs, you update a table, not a program. Confirm current rates with your compliance adviser before each financial year.

Write salary rules as formulas

Salary structures in growing businesses rarely stay simple. Allowances depend on grade, incentives depend on sales, and a branch may have a site allowance nobody else gets. If every change needs a developer, payroll falls behind the business.

Look for salary components defined as formulas that HR can read and edit, with structures per employee and a revision history. Then a new allowance is a configuration change, and the reason for every number is visible.

Keep separate books where you need them

Many groups run more than one legal entity: a trading company, a service company, a new branch registered separately. Each needs its own payroll, its own registers and often its own statutory registrations. Running them in completely separate systems means separate logins and duplicate work.

A better setup keeps separate books and licences for each company under one login, with a simple switcher, so the same HR team can manage all of them without mixing data.

Lock the run and keep the history

Once a month's payroll is approved, it should be locked. Any later correction should be a visible revision, not an edit that overwrites the original. Keep before-and-after values for salary revisions, approvals and locks, so when an employee or an auditor asks why a number changed, there is an answer on record.

Let employees serve themselves

In a multi-branch business, HR cannot be at every site. Employee self-service removes most of the routine questions: staff apply for leave, see their balances, correct missed punches with approval and download their own payslips. Branch managers approve requests without phoning head office.

Make sure the data stays yours

Finally, check that every register and report can be exported to CSV from the screen you are looking at. Your auditors, your bank and your accountant will all ask for data in their own format.

A sensible order of rollout

You do not need to switch everything on at once. Most businesses start with the module that hurts most, usually attendance, and add leave and payroll once the attendance data is trusted.

DV Soft HRMS & Payroll is licensed module by module for exactly this reason, with branch calendars, formula-based salary components, state-wise statutory slabs, multi-company support and self-service built in. To see it with your own branch structure, book a demo.