Payslip Format for Private Companies in India

The dominant format is one A4 page: company header across the top, the employee block below it, a two-column table of earnings and deductions in the middle, and a bolded net-pay line near the bottom, above the bank-reference note.

A payslip must state the pay period, the employee's identity, gross earnings, each deduction, and net paid — this is the substance of the wage-slip requirement. Company-specific extras like year-to-date columns and the leave balance are good practice but not statutory.

The most useful additions are YTD columns, the employer's PF and ESI contributions shown separately, an annual-to-date attendance note, and the leave balance. Banks do not require them, but they save your employees the reconciliation calls and make the document look designed rather than thrown together.

Anisha runs accounts at a Pune SaaS company issuing payslips to eighty staff. Her format: company header, employee block, and a table with earnings on the left and deductions on the right. For an employee with gross ₹52,000 — basic ₹26,000, HRA ₹15,600, special allowance ₹10,400 — deductions of EPF ₹3,120, professional tax ₹200 and TDS ₹4,800 give a net of ₹43,880, printed bold under 'Net Pay'.

The net-pay line is what employees quote, banks match and auditors sample. Make it the boldest element on the page and pair it with the amount in words. A payslip where the reader has to hunt for take-home pay is a payslip that generates support tickets every month.

Excel formats give small teams full control over layout but inherit formula risk in the deduction lines. Payroll suites standardise the layout across months and add statutory regs automatically. A generator sits between them: standardised layout with deductions computed from the structure, no formulas to maintain.

Keep off the payslip anything per-employee-sensitive that is not pay-related: medical diagnosis history, performance ratings, or disciplinary notes. These belong in separate HR records. The payslip is a pay document — the cleaner its scope, the fewer questions it invites.

Email the payslip as a named PDF (payslip-YYYY-MM-name.pdf) the same day every month. A fixed delivery date is itself a professional signal, and PDF payslips archive cleanly for the wage register, Form 16 season and loan requests.

Part-time and daily-wage employees in private companies need the same statement, with the pay basis made explicit: the days or hours worked, the daily rate and the earned amount. Where the establishment is covered by ESI, the 0.75% employee share appears as its own deduction line even on these thinner slips.

Keep a separate register for this workforce with the working-days column — it is the column labour inspections check first, and it is also the source your own monthly reconciliation against the payslips draws from.

Companies in states with strong local-language labour practice often print the payslip in two languages: the employee-facing earnings table in the local language and the statutory references in English. Nothing in the wage rules mandates this, but it improves the statement's readability and reduces the monthly explanation load on the HR desk.

State-specific additions are the real variable: professional tax lines in the states that levy them, the minimum-wages notification reference where the establishment is covered, and ESI registration details in ESI-covered units. Adapt the footer, never the substance.

Run the format against a three-question test before it goes live: can a stranger identify employer, employee and month from the top half alone; can a bank match net pay to the credit line; and does the deduction list have a statutory anchor for every line? A format that passes the three questions needs no further approval.

Then issue a test payslip for one employee and walk it past accounts and HR together. The pair will notice the two or three layout details — alignment, column order, the words in the footer — that no template review catches, and fixing them before month-end beats fixing them after the whole team has seen it.

Salary revisions paid as arrears deserve their own line — 'arrears of Apr–Jun' — rather than being folded into the regular basic, so the month's payslip stays readable and the tax treatment stays honest. Arrears can be taxed in the year of receipt, which the TDS line should reflect.

One-off additions like a joining bonus or a retention installment go on a separate 'other earnings' row, never silently added to basic. The employee reads an unexplained bump as an error and raises a ticket; a named line answers itself.

When a salary revision lands mid-year, the payslip format must show the change visibly: new basic from the revision date, revised PF base, and fresh YTD for the changed lines. Employees on the old structure and the new structure may need different slips in the same month, so the generator or payroll template should branch on the effective date.

A mid-year revision is also the moment to reprint the structure note. With the payslip itself carrying the revised figures, the pair — new structure letter plus the first payslip — closes every query the old format used to generate.

The earnings and deduction tables must survive a black-and-white print and an A5 screenshot: use tabular numbers aligned right, at least 9pt for the figures, and no column narrower than the largest value it holds. A payslip that blurs at 80% scale on a phone is a payslip that generates screenshots of the wrong line.

Test the format at the sizes it will actually be seen: printed A4, emailed PDF, and a phone screenshot. The three views surface different failures — a column cut in print, an unreadable figure at phone size — and all three are cheaper to fix once, at setup, than every month.