It is the third of the month. Someone from the production floor is standing at the HR desk holding a printout, and the question is always the same: why is this less than last month. Twenty minutes later, after opening the attendance register, the salary sheet and last month’s payslip side by side, the answer turns out to be two days of loss of pay and a PF arrear. The information was on the payslip the whole time. It just was not readable.
Most payroll queries are not disputes. They are comprehension failures. A payslip format that explains itself removes the conversation entirely, and it costs nothing but layout discipline.
Why payslips generate queries
Three things make a payslip unreadable, and almost every bad payslip has at least two of them.
The first is a single column of numbers. Earnings and deductions run down the page in one list, so the employee cannot see at a glance what was added and what was taken away. They read the last number, compare it to the last number from last month, and come to you with the difference.
The second is jargon without arithmetic. A line that says “LOP” with a rupee figure next to it tells the employee nothing about how that figure was arrived at. A line that says “Loss of pay, 2 days of 26” tells them everything.
The third is missing context. The payslip shows this month in isolation. It does not say how many days were payable, how many were paid, what the leave balance now is, or whether anything on the slip relates to a previous month. Every one of those absences is a question waiting to be asked.
What belongs on a payslip
Start with the identifying block. This is the part nobody reads until they need it, usually when applying for a loan or a visa.
- Legal name of the employer and the establishment address
- Employee name, employee code and designation
- Department or cost centre
- Date of joining
- Pay period, stated as a month and year, not a date range that could be read two ways
- Payment date and mode
- Bank account number, masked except the last four digits
- PF number, UAN, ESI number where applicable
- PAN
Then the attendance block, which is the single most useful addition most SMB payslips are missing.
- Total days in the period
- Payable days
- Days paid
- Loss of pay days
- Leave taken in the period, by type
- Leave balance carried forward
If the attendance block is present and correct, roughly half of your monthly queries never get asked, because the employee can reconcile the pay themselves before walking over.
Then earnings, deductions, and three totals. That is the core of the payslip format and it deserves its own section.
Statutory requirements differ by state and by which acts apply to your establishment, so check what your state’s shops and establishments rules and the wage legislation applicable to you actually mandate. Treat the list above as the practical floor, not the legal ceiling.
A payslip format that explains itself
Two columns, side by side, on one page.
The left column is earnings. Basic, house rent allowance, conveyance, special allowance, and then anything variable: overtime, incentive, arrears, reimbursement. Each line gets a rate or a basis where one exists. Overtime should read as hours times rate, not as a single figure.
The right column is deductions. Provident fund employee share, ESI employee share, professional tax, income tax deducted at source, salary advance recovery, loan instalment, and any other recovery. Each recovery line should carry the balance remaining. An advance line that says “instalment 3 of 6, balance remaining” ends the query about how long this will continue.
Below the two columns, three totals in this order:
- Gross earnings
- Total deductions
- Net pay, in figures and in words
Net pay in words is not decoration. It is the line the employee’s bank statement gets matched against, and it removes an entire category of decimal confusion.
One page. If your payslip format needs a second page, you have put the CTC breakdown on it, and the CTC breakdown does not belong there.
Employer contributions, and where to show them
Employer PF, employer ESI and gratuity accrual are real costs and employees should know about them. They are not deductions from salary and they must never appear in the deductions column. Put them in a small separate block, labelled clearly as employer contributions, below the totals. Anything else invites the belief that the company is taking money out of the employee’s pay twice.
The five lines that cause the most questions
Fix the wording on these five and the volume drops immediately.
Loss of pay. Never a bare figure. Write the days and the divisor: two days out of twenty six payable. If your calendar-day and working-day logic differ across departments, that inconsistency will surface here first, which is useful.
Arrears. Always name the month the arrear belongs to and the reason. “Arrear, increment effective 1 April, paid with May” is self explanatory. “Arrear” alone reads as a mistake.
Provident fund. Show the wage the contribution was calculated on. When an employee’s PF does not move in step with a salary revision because of the statutory wage ceiling, the calculation basis on the payslip is the only thing that prevents a long conversation.
Tax deducted at source. Show the amount deducted this month and the cumulative amount deducted in the financial year so far. TDS is lumpy by design, and the year to date figure is what makes a jump in one month look deliberate rather than arbitrary.
Reimbursements. Keep them out of gross earnings if they are not taxable pay. A reimbursement mixed into gross inflates the number an employee quotes on a loan application, and then the bank’s verification comes back to you.
Distribution, not just design
A well laid out payslip that reaches people late, or by forwarded WhatsApp image, undoes half the benefit.
- Issue on a fixed date every month, and issue it whether or not anybody asks
- One PDF per employee, generated from the payroll run, not exported and split by hand
- Password protected with a documented convention, and tell people what the convention is
- Delivered to the work email address of record, with a copy retained in the system
- Downloadable by the employee later without an HR request
That last point matters more than it sounds. Most payslip requests are for old months, usually for a loan or a rental agreement, and each one interrupts whoever holds the payroll file. Self service on past payslips is the cheapest query reduction available. This is also part of why running payroll from a personal machine causes trouble beyond the obvious: as covered in the piece on payroll living on one person’s laptop, when the file and the PDFs sit in one place, every historical request becomes a dependency on one person being available.
On BizvoraOne, payslip PDFs come out of the payroll run itself, so the slip and the register are generated from the same numbers rather than reconciled afterwards. The layout discipline is still yours to set. Software does not decide whether your loss of pay line shows the divisor.
A checklist you can run on last month’s payslip
Pull one payslip from your last run, ideally for an employee who had loss of pay or an arrear, and check:
- Can you tell how many days were payable and how many were paid, without opening another file
- Are earnings and deductions in two visibly separate columns
- Does every variable line carry its basis, in days, hours or units
- Are employer contributions shown separately from employee deductions
- Does every recovery line show the remaining balance
- Is TDS shown both for the month and year to date
- Is net pay written in words
- Does the whole thing fit on one page
- Would a bank officer accept it as proof of income without a covering letter
- Would a new joiner understand it in the first month, with no explanation from HR
Anything you fail on that list is a query you will receive, repeatedly, until you fix it.
What this will not fix
A good payslip format ends confusion. It does not end disagreement. If your leave policy is unclear, if attendance is captured inconsistently across sites, or if increments are communicated verbally and applied two months later, the payslip will simply display that problem more legibly. That is still progress, but do not expect the layout to do policy work.
It also will not fix timing. Slips issued a week after salary credit will generate queries no matter how well they read, because people have already asked by then. A fixed monthly rhythm, with the payslip release on a stated date, is the other half of this. The day by day payroll month sets out where that date sits relative to attendance cutoff and statutory deposits.
What to do first
Do not redesign anything yet. Take the ten queries you received after the last payroll run and write down what each person actually wanted to know. You will find they cluster into three or four questions, and every one of those questions maps to a line on the payslip that is missing, unlabelled or ambiguous.
Fix those lines. Reissue nothing, just apply the changes to next month’s run. Then count the queries again in the first week of the month after. If the number has not moved, the problem was never the payslip format, and you have learned something more useful than a layout tweak.
