"Salary slip generator" is one of the most-searched payroll phrases in India. The search is the symptom: the numbers on the slip are being typed, not computed.
A salary slip is produced correctly when it is computed from three records — the month's attendance, the employee's salary structure and the statutory deductions — and then rendered, rather than typed into a template. Online generators and Excel formats fail because they start at the rendering step: someone types basic, HRA and the deductions from memory or from another sheet, and the slip inherits every transcription error. The process below runs the other way — days first, structure second, slip last — and issues every slip by the 7th, which the Code on Wages now requires for wage payment.
A template is a layout with blanks. A generator is a template with arithmetic for the totals. Neither knows how many days the employee worked, whether their salary was revised on the 16th, whether they had two days of loss-of-pay, or what professional tax slab applies. Someone types those in. Five things then go wrong, in roughly this order of frequency:
None of these are arithmetic errors. They are all record errors, and a better template cannot fix a record.
The full payslip format guide covers each line; the minimum is:
The attendance block is the one that templates leave out and employees need most: with it, a person can check their own slip in a minute; without it, every question becomes an HR ticket.
Employee on gross ₹40,000 (basic ₹20,000, HRA ₹8,000, other allowance ₹12,000). September has 30 days; she had 2 LOP days, so 28 paid days. Professional tax ₹200. No PF (company below threshold), no TDS (income below the exemption limit after standard deduction).
| Basic | 20,000 × 28 ÷ 30 = ₹18,667 |
|---|---|
| HRA | 8,000 × 28 ÷ 30 = ₹7,467 |
| Other allowance | 12,000 × 28 ÷ 30 = ₹11,200 |
| Gross (earned) | ₹37,333 — equivalently, full gross ₹40,000 less LOP ₹2,667 |
| Deductions | Professional tax ₹200 |
| Net pay | ₹37,133 |
Show LOP either as reduced earnings (as above) or as a full-gross earnings block with LOP as a deduction line — both are accepted, but use one consistently, and always show the paid-days figure so the employee can reproduce it.
A slip contains a person's salary, PAN-linked deductions and often their bank account. Send it only to that person: an individual email with the slip attached or linked, or a self-service portal where each employee downloads their own. A shared drive folder, a group email or a WhatsApp forward is a data-protection incident waiting for a wrong tap — the checklist for what an HR system should do with this data.
| Inputs | Locked attendance, salary structure with effective dates, applicable deductions |
|---|---|
| Three blocks | Attendance (paid/LOP days) · Earnings · Deductions |
| Order | Days → structure → compute → review → render → distribute → archive |
| Deadline | Wages by the 7th of the following month (Code on Wages) |
| Distribution | Individually, one slip to one employee; self-service download preferred |
| Corrections | Issue a revised slip; never edit an issued one |
Start from the month's locked attendance to get paid days and loss-of-pay days per employee, apply each employee's salary structure pro rata, compute the deductions that apply to them, review the resulting register for unexplained variances, and only then render one slip per employee showing attendance, earnings, deductions and net pay. Typing directly into a template skips the first four steps, which is where the errors are.
Employee name and ID, designation, month and date of issue; days in the month, paid days and LOP days; each earning component — basic, HRA, other allowances, incentives, arrears — and gross; each deduction — PF and ESI where applicable, professional tax, TDS, LOP — and the total; and net pay with the payment date. Showing the attendance figures lets the employee verify the slip themselves.
It is only as accurate as the numbers typed into it, and many free generators run in a browser tab with no record of what was issued. For a team of any size the risks are wrong paid-day counts, inconsistent LOP divisors and no archive. Use a process that computes the slip from recorded attendance and keeps every issued slip.
Individually — one document, to one employee, by email or through a self-service portal where each person downloads only their own. Never through a shared folder, a group email or a messaging group, because a slip contains salary, tax and often bank details.
You should not. If a slip was wrong, issue a revised slip clearly marked as such and keep the original; the register and the employee's copy must always match. Silent edits create two versions of the truth and are the first thing questioned in any dispute.
Either as reduced earnings — each component multiplied by paid days over days in the month — or as full earnings with a separate LOP deduction line. Both are accepted; pick one and use it consistently, and always show the paid-days and LOP-days figures that produced it.
In Merik the slip is the last step, not the first. Employees record attendance, leave and work-from-home through the month; corrections go through approval; and when the month is locked, payroll is computed on the server — basic, HRA, other allowance, professional tax, LOP, incentives and arrears — from the days already recorded. Nothing is typed into a slip.
Payslips are generated per employee, stored as issued, and emailed individually or in bulk; each employee also downloads their own from their dashboard, so the salary of one person is never in a file that another can open. See the payroll module, or how attendance reaches payroll in the first place.
The line items a payslip needs so an employee can check their own pay.
What CTC really means and how monthly net pay is calculated.
How connecting attendance and leave directly to payroll removes errors.