It is the twenty-eighth. Your accounts person, the one who runs payroll, is on leave with a fever and is not answering. The salary file lives on her laptop. The attendance sheet lives in a WhatsApp group she moderates. Nobody else knows which of the four files named “Salary_Final” is the real one, and thirty-eight people expect money in two days.
That is payroll process risk, and almost every SMB in India carries it without naming it. It is not a technology problem. It is the fact that one person holds the file, the logic, the passwords and the history, and nothing about that arrangement is written down.
What actually breaks when that person is away
Most owners assume the worst case is a delay. The delay is the visible part. Underneath it are four failures that cost more and take longer to unwind.
The calculation logic is undocumented. The spreadsheet has formulas, but nobody wrote down why the LTA line is prorated for people who joined mid year, or why one sales team is on a different incentive slab. The person who knows is asleep with a fever. Whoever steps in either guesses or copies last month, and copying last month means paying the person who resigned on the ninth.
The inputs are scattered and undated. Attendance came from a register. Overtime came from a supervisor’s WhatsApp message. Two loan deductions came from a verbal instruction in the corridor. None of it has a timestamp or an author. When the numbers are questioned in March, there is no way to reconstruct what was known on the twenty-eighth of November.
Statutory filings slip quietly. PF, ESI and TDS have their own dates and they do not care about your fever. A one month gap in filing is an interest liability and a correction return, and corrections take three times as long as the original.
Trust drops faster than it recovers. A salary that arrives four days late is remembered for a year. People do not tell you they lost confidence. They start asking friends what other firms pay.
The common thread is that none of this is about the person’s competence. It is usually the opposite. The most reliable person in the office accumulates the most undocumented process, because everything they touch stops being a problem and therefore stops being examined.
Test your own exposure in ten minutes
Do not audit the whole thing. Ask five questions and note where you hesitate.
- If the payroll owner did not come in tomorrow, who would run this month? Name a person, not a department.
- Where does the master salary data live right now? A path on one laptop is a fail. A shared drive that only one person opens is also a fail.
- Can anyone else explain how gross becomes net for a mid level employee, without opening the file?
- Where is the record of the last three months of one-off deductions and their approvals?
- Who has the login for the PF and ESI portals, and is that written anywhere a second person can find it?
If you hesitated on two or more, your payroll process risk is not theoretical. It is a scheduling accident away from being real.
Centralise three things first
You do not need to redesign payroll to reduce the risk materially. Three moves cover most of it, and they can be done in a fortnight.
1. The employee master
One record per person, in one place, holding the things that never change month to month: date of joining, designation, department, reporting manager, CTC structure, bank account, PAN, UAN, ESI number, PF applicability, and date of exit if there is one.
Today this data is usually spread across the offer letter, an HR folder, the payroll sheet and someone’s memory. On BizvoraOne it sits in the HR and Payroll module, which means the person covering for a month is reading the same record the regular owner reads.
The test for whether this is done: someone who has never run payroll can answer “what is this person’s fixed monthly gross” in under thirty seconds, without asking anyone.
2. The monthly input log
Everything that changes month to month goes into one list, with a date and a name attached. Attendance and leave without pay. Overtime. Incentives and bonuses. Loan and advance deductions. New joiners with their prorated first month. Exits with their final settlement. Salary revisions with the effective date.
The rule that makes this work is boring and non negotiable: if it is not in the log by the cut-off date, it goes into next month. No verbal instructions on the twenty-seventh. No WhatsApp voice note that only one person heard.
This is the single highest value change, because it converts payroll from an act of memory into an act of reading.
3. The compliance calendar and credentials
Write down every statutory obligation with its date, the portal it is filed on, and who has access. PF, ESI, professional tax where applicable, TDS deposit and quarterly returns. Store credentials somewhere at least two people can reach, with a record of who holds what.
This is not glamorous work. It is also the part that becomes expensive fastest when it lapses, because interest and penalties accrue without anyone sending you a reminder.
The handover checklist
Run this before planned leave, and keep it current so it also works for unplanned leave. Print it. Sign it. Two names on the page.
Access
- Login credentials for the payroll system, banking portal, PF, ESI and TDS filing portals, recorded where the stand-in can reach them
- Bank authorisation: confirm the stand-in is an approved maker or checker, and test it before the leave starts, not on the twenty-eighth
- Email access or a rule forwarding payroll related mail to the stand-in
Data
- Employee master reviewed and current, with joiners and exits from the last sixty days reflected
- The input log for the current month, with the cut-off date written on it
- Last month’s completed payroll register, as the reference for what normal looks like
- Any open items: pending settlements, disputed attendance, salary revisions awaiting approval
Logic
- A one page note explaining the non-obvious rules: which allowances are prorated, which are fixed, how incentives are calculated, which employees sit outside the standard structure and why
- A worked example for one employee, gross to net, line by line
Calendar
- The payroll run date and the disbursement date
- The statutory due dates falling within the leave period
- Who approves the final register before disbursement, and what happens if that person is also unavailable
Escalation
- Two named people the stand-in can call, in order
- A stated rule for what to do if something cannot be resolved: pay the standard amount and correct next month, or hold the individual line and pay everyone else
That last item matters more than it looks. Without a stated rule, a stand-in facing one uncertain line will often delay the whole run for everybody. Decide in advance that thirty-seven people get paid on time while one line is held.
What a written process actually buys you
It is easy to treat this as a leave contingency. It is broader than that. A payroll process that lives outside one head also survives resignation, hospitalisation, a laptop that dies, and the perfectly ordinary event of your business growing past the point where one person can hold it all.
It also makes the month calmer for the person who normally runs it. A written sequence with dates attached is easier to execute than a remembered one, which is the case made in our walkthrough of a payroll month day by day. And when the calculation is reproducible, the output stops generating queries, which is half of what makes a payslip people can actually read worth the effort of designing properly.
One honest limit. If you have eight employees on identical fixed salaries with no variable component, this is less urgent than it sounds. Write down the credentials and the compliance dates, keep the file on a shared drive, and move on. The risk scales with headcount, with variable pay, and with how many people sit outside the standard structure. A forty person team with incentives, shift allowances and three loan deductions is a different animal from eight people on flat salaries.
Where to start this week
Pick the next payroll cycle and shadow it. Sit with whoever runs it and write down every input as it arrives, every source it came from, and every decision made that was not written anywhere. That document is your first draft of the process, and it will be more accurate than anything produced in a meeting.
Then do one thing: move the employee master out of the personal laptop and into somewhere a second person can open it. That single move removes the sharpest edge of payroll process risk. The input log and the compliance calendar can follow next month.
You are not trying to make the payroll owner replaceable. You are trying to make sure that their week off does not become everyone else’s problem.
