A payslip is one of the few documents a company produces that its own staff will keep for a decade. It gets read by strangers, long after the person who generated it has left, and nobody is available to answer a question about it.
What the payslip actually gets used for
The design brief follows from the readers, so it is worth listing them.
A loan underwriter takes the last three payslips and the matching bank statements and checks that they agree. They are looking for a net figure on the slip that appears as a credit in the statement, on or about the date the slip claims. Eligibility is then computed from a gross or from named components, which is why a slip showing only a final number is sent back.
A visa officer wants consecutive months from a named employer, each one identifying the employee and the period. Gaps and inconsistent formatting are read as weak evidence, not as a filing quirk.
A new employer's HR team verifies last drawn salary, and the components matter more than the total — a great many Indian offers are built off basic, not off CTC. A slip that lumps everything into "salary" makes that conversation harder for your former employee.
And the employee uses it for rent agreements, for HRA claims, for their own return, and to check that the month is right. That last one is the only reader who will tell you when something is wrong, and only if the arithmetic is followable.
What belongs on a payslip
Nothing here is decoration. Each field exists because one of those readers cannot do their job without it.
| Field | Why |
|---|---|
| Employer name and address | The reader has to know who paid, on a document that travels. |
| Pay period | The month the money is for. |
| Pay date | The day it was credited — this is what a bank statement is matched against. |
| Employee name | As it appears on PAN and the bank account, not a nickname. |
| Employee ID | What a verification call is keyed on. |
| Designation and department | Used by a new employer and in visa files. |
| Date of joining | Establishes tenure without a separate letter. |
| PAN | Links the income to a tax record and makes the slip usable as evidence. |
| UAN or PF number | Needed when the employee transfers PF to their next job. |
| Bank account, masked | Confirms which account was credited. |
| Days paid and LOP days | Explains a month that is lower than the one before it. |
| Earnings lines | Named the same way every month, each with its own amount. |
| Deductions lines | Same, in a separate table. |
| Gross, deductions, net | All three, as their own totals. |
| Net in words | A check on the digits. |
The free salary slip template puts earnings and deductions in two separate tables rather than one list with negative numbers in it. That is deliberate. A single combined list is more compact and materially harder to check, and it is where reconciliation errors hide — a deduction typed as a positive number in a mixed list quietly becomes an earning, and the net still looks plausible.
Gross, deductions and net — all three, in that order
The most common thing missing from a homemade payslip is one of the three totals, usually gross.
Each of them has a different reader. Net is what the employee received and what the bank statement will show. Total deductions is what makes the other two reconcile. Gross is what loan eligibility, offer benchmarking and most statutory questions are computed from. Drop any one and somebody downstream has to reconstruct it, which means they either add up your line items by hand or send the document back.
The arithmetic has to survive ten seconds of scrutiny: earnings subtotal minus deductions subtotal equals net, exactly. Rounding is where this breaks. If you round the net to the rupee, round the components so they still sum to it — a slip whose lines add to ₹86,417 against a net of ₹86,420 gets queried, and the three rupees cost more in explanation than they ever saved.
The other quiet mismatch is money paid outside payroll. If a travel reimbursement of ₹7,500 goes out in the same bank transfer as August salary, the credit in the statement no longer equals the net on the slip, and an underwriter matching the two has found a discrepancy you did not know you created. Either show it on the slip as a separate non-taxable line, or transfer it separately.
Below the net, the amount in words survives on payslips for two reasons that are still good ones. It is a genuine check — a figure and its written form disagreeing is caught instantly, where a single wrong digit is not. And a payslip is a document that gets forwarded, photocopied and re-scanned by people with an interest in the number; altering a digit in a PDF is easy, altering it in both places consistently is less so. Write it in the conventional form, ending in "Only", and generate it in the same step that computes the net rather than typing it afterwards.
Pay period and pay date are different dates
A slip that carries only one date is ambiguous, and the ambiguity lands on the reader who can least afford it.
The pay period is the month the earnings relate to — 01–31 August 2026. The pay date is
the day the money moved — 02 September 2026. They are usually in different months, which
is exactly the problem: an underwriter holding three payslips and three bank statements
sees credits on 2 September, 2 October and 2 November, and if your slips are labelled only
"August, September, October" the two sets appear to be off by one. Printing both dates
removes the question.
Two related cases are worth handling explicitly rather than hoping nobody notices.
Arrears. If August's slip includes a July revision, give it its own earnings line and name the period it belongs to — "Arrears (July 2026)". Folded into basic, it makes one month look anomalous and drags the average that somebody else is computing from three slips.
Off-cycle payments. A bonus, an incentive or a full-and-final settlement paid on a different date is not part of the monthly run. Give it its own slip with its own pay date, or label the line unmistakably. A ₹1.5 lakh spike inside a normal month is the kind of thing that gets treated as an error in the document rather than an event in the year.
How much of an identifier to print
A payslip travels further than most internal documents. It gets emailed to a loan agent, uploaded to a portal, handed across a desk, kept in a shared drive. That is the context for deciding what goes on it in full.
The bank account should be masked to the last four digits — XXXXXX4417. That is
enough to confirm which account was credited, which is the only job the field has. Nobody
downstream needs the full number, and there is no reason at all to print the IFSC beside
it: an account number plus an IFSC is a payment instruction, not a piece of evidence.
PAN is conventionally printed in full, because linking the income to a tax record is precisely what makes the slip stronger than a letter claiming a salary. Some employers mask the middle characters. Either is defensible; what is not defensible is leaving it off and then being surprised when a bank asks for a separate income certificate.
Employee ID is internal and safe in full — it is what a verification call is keyed on, and printing it saves your HR team from searching by name. UAN is worth including for the same reason: the employee will need those twelve digits when they transfer PF, and they will ask you for them at the worst possible moment if the slip does not carry them.
Whatever you choose, mask it the same way every month. An account number that appears in full in March and masked in April looks like two different accounts to somebody comparing slips, and that is a question you will have to answer in writing.
Before you run the month
Three checks catch nearly everything, and all three are faster than the email that follows from missing them.
Confirm that gross minus deductions equals net exactly on every slip, including the ones with loss of pay. Confirm that a pay date is present and matches the date the transfer actually went out. And confirm that component names, masking and layout are identical to last month — a payslip that changes shape between months is a payslip somebody has to read twice.
Then stop producing them by hand. Payroll already holds every value on the page, the layout does not change, and editing a document per employee per month is both slow and the most reliable way to send one person's figures to another. Generate them from the payroll run, and keep them somewhere the employee can fetch an old one without asking.