School Payroll Software India: End the Salary Register [2026]

<h2>Introduction</h2> <p>Every Indian school has one. A hardbound register with fourteen ruled columns, a name list that has not changed order since 2016, and a page for each month that is filled in by hand, re-checked by hand, and corrected in white fluid. The principal signs it on the 7th. The bank upload happens on the 8th. And somewhere between the 1st and the 7th, three people spend four days doing arithmetic that a machine should do in four minutes.</p> <p><strong>School payroll software India</strong> needs to exist as its own category because school payroll is genuinely not factory payroll. A school pays per period taught, hires mid-session, runs two employment types side by side, and answers to PF, ESI, professional tax and TDS at the same time. A generic HR tool either cannot express the formula or makes the accountant fight it every month.</p> <p>This guide is for principals, trustees and school accountants running CBSE, ICSE and state board institutions of 40 to 300 staff — the size where payroll is too big for a notebook and too small to justify a full HR department.</p> <h2>Why school payroll breaks generic software</h2> <p>The first surprise for any school shopping for payroll software is that the ₹99-per-employee SaaS tool everyone else uses does not survive contact with a real school's salary structure. Here is where it actually fails.</p> <table> <thead> <tr><th>What the school actually does</th><th>Why off-the-shelf payroll struggles</th></tr> </thead> <tbody> <tr><td>Pays some teachers per period taught</td><td>Salary is a formula over assigned periods, not a fixed monthly number. Change one teacher's timetable and the payable amount changes.</td></tr> <tr><td>Hires across the year, heaviest in April and June</td><td>Part-month calculation with 15 different joining dates in one cycle, plus pro-rata leave accrual from each date.</td></tr> <tr><td>Runs four or five employment types</td><td>Permanent, probation, part-time, visiting faculty, and support staff (drivers, guards, aayas, lab assistants) — each with different leave and deduction rules.</td></tr> <tr><td>Pays increments from April but arrears later</td><td>Arrears must be split across financial years for correct TDS, which most simple tools cannot do.</td></tr> <tr><td>Gives salary and festival advances</td><td>Recovery is spread over months in a notebook that only one clerk understands.</td></tr> <tr><td>Substitutes absent teachers daily</td><td>Extra periods taught become honorarium — payable only if someone recorded them.</td></tr> <tr><td>Files 24Q every quarter and Form 16 by 15 June</td><td>Requires a twelve-month per-employee projection, not a monthly total.</td></tr> </tbody> </table> <p>None of these are exotic. Together, they are why the salary register survives: it is the only tool flexible enough to hold the mess — and the only tool that cannot tell you, in September, whether you are paying a teacher who resigned in July.</p> <h2>What school payroll software in India actually does</h2> <p>Ignore the feature brochure. A working system closes one loop reliably, and everything valuable follows from it.</p> <ol> <li><strong>One staff master record per person.</strong> Employee code, joining date, designation, department, employment type, bank account, IFSC, PF and ESI numbers, PAN, and the salary structure version that applies this year.</li> <li><strong>Attendance that feeds salary, not sits beside it.</strong> Biometric or face device punches, leave applications, and approved substitutions all land in the same monthly attendance sheet — which is the input to the salary run, not a separate register.</li> <li><strong>Salary structures as formulas, not typed amounts.</strong> Basic, DA, HRA, allowances, per-period honorarium, PF, ESI, professional tax, TDS and deductions defined once per grade, then applied to everyone in that grade.</li> <li><strong>One click to a bank file.</strong> NEFT or RTGS upload in the format your bank accepts, with a control total that must match the salary register before anyone hits upload.</li> <li><strong>Payslips that reach staff without printing.</strong> Email or app delivery, with a locked PDF — because the most common payroll complaint in Indian schools is not the amount, it is "I never got my payslip."</li> <li><strong>Statutory outputs, not statutory guesswork.</strong> ECR file for EPF, ESI challan data, professional tax statement for your state, and 24Q-ready TDS workings.</li> <li><strong>An audit trail.</strong> Who changed whose salary, when, and with whose approval. This one field ends most staff disputes before they start.</li> </ol> <p>That is the whole product. The value is that the salary register, the attendance register, the leave file and the bank advice finally describe the same month.</p> <h2>The eleven fields that end the monthly argument</h2> <p>Most schools track four things: name, designation, gross salary and a deduction. Seven more decide whether the register is defensible a year later.</p> <table> <thead> <tr><th>Field</th><th>Why it matters in an Indian school</th><th>Common mistake</th></tr> </thead> <tbody> <tr><td>Employee code</td><td>The only identifier that survives a name change after marriage and a re-join</td><td>Using serial numbers that shift when someone leaves</td></tr> <tr><td>Joining date</td><td>Drives pro-rata salary, leave accrual and probation confirmation</td><td>Recording the appointment letter date, not the first working day</td></tr> <tr><td>Employment type</td><td>Decides leave rules, PF applicability and notice period</td><td>Marking everyone "permanent" because it is the default dropdown</td></tr> <tr><td>Salary structure version</td><td>April increment creates a new version; history stays intact</td><td>Overwriting last year's figures so arrears become unprovable</td></tr> <tr><td>Payable days / periods</td><td>Connects attendance to money</td><td>Paying full month and adjusting next month "somehow"</td></tr> <tr><td>Bank account and IFSC</td><td>A wrong IFSC is a bounced salary and an angry phone call</td><td>Storing it in a WhatsApp message</td></tr> <tr><td>PAN</td><td>Required for TDS and Form 16; missing PAN triggers higher deduction</td><td>Collecting it after the first salary run</td></tr> <tr><td>PF / ESI numbers</td><td>Needed for the ECR and challan, and to avoid duplicate UANs</td><td>Letting each new hire create a fresh UAN</td></tr> <tr><td>Leave balance</td><td>Encashment and loss-of-pay both depend on it</td><td>Tracking leave in a separate diary that never reconciles</td></tr> <tr><td>Advance balance</td><td>The only reliable way to recover a festival advance</td><td>Recovering it from whoever remembers</td></tr> <tr><td>Exit date and full-and-final status</td><td>Stops the single most expensive payroll error: paying a resigned teacher</td><td>Deleting the record instead of closing it</td></tr> </tbody> </table> <p>Eleven fields, filled once per employee. Schools that fail usually try to fill them for 200 staff in one week. The ones that succeed start with the 20 people whose salary is hardest to calculate — usually per-period teachers and support staff — and let the rest arrive during the first parallel run.</p> <h2>The statutory layer nobody warns you about</h2> <p>This is where school payroll stops being bookkeeping and becomes compliance. The thresholds below are the ones that matter most in a school, and they change — confirm current rates with your CA before you configure anything.</p> <table> <thead> <tr><th>Head</th><th>Who it applies to</th><th>What the school must file</th></tr> </thead> <tbody> <tr><td>EPF (Employees' Provident Fund)</td><td>Establishments with 20+ employees; wage ceiling ₹15,000/month basic + DA</td><td>Monthly ECR upload and challan via the <a href="https://www.epfo.gov.in/" target="_blank" rel="noopener">EPFO portal</a></td></tr> <tr><td>ESI (Employees' State Insurance)</td><td>Establishments with 10+ employees; wage ceiling ₹21,000/month</td><td>Monthly contribution and return on the ESIC portal</td></tr> <tr><td>Professional tax</td><td>State-specific — levied in Maharashtra, Karnataka, West Bengal, Tamil Nadu and others; not in every state</td><td>Monthly or annual statement to the state commercial tax department</td></tr> <tr><td>TDS on salary (Section 192)</td><td>Every employer, once taxable income is projected above the exemption limit</td><td>Quarterly Form 24Q and annual <a href="https://www.incometax.gov.in/iec/foportal/" target="_blank" rel="noopener">Form 16</a> by 15 June</td></tr> <tr><td>Maternity benefit</td><td>Establishments covered under the Maternity Benefit Act; 26 weeks paid leave</td><td>Correct leave accounting so the absence is not treated as loss of pay</td></tr> <tr><td>Gratuity</td><td>Staff with five or more years of continuous service</td><td>Accrual provision in the books, settled at exit</td></tr> </tbody> </table> <p>Two things go wrong here more than any other. First, a school treats a part-time or visiting teacher as an employee for salary and as a contractor for PF — and gets caught in an inspection. Second, the school deposits PF and ESI late and discovers that interest and damages are calculated by the department, not negotiated by the school. Both are configuration problems, solved once in the master data instead of every month.</p> <h2>Staff attendance is the other half of payroll</h2> <p>Payroll software without attendance is just a calculator. In an Indian school the attendance rules are what make the salary run defensible — and they are all local.</p> <table> <thead> <tr><th>Leave type</th><th>Typical school rule</th><th>What breaks when it is manual</th></tr> </thead> <tbody> <tr><td>Casual leave</td><td>8–12 days a year, often not carried forward</td><td>Two registers give two different balances by October</td></tr> <tr><td>Sick leave</td><td>7–15 days, sometimes with a medical certificate above 3 days</td><td>Certificate never attached, leave still marked paid</td></tr> <tr><td>Earned / privilege leave</td><td>Accrues monthly; encashable at exit in many schools</td><td>Accrual is estimated at exit, and the school overpays</td></tr> <tr><td>Maternity leave</td><td>26 weeks paid, as per the Act</td><td>Marked as absence, salary deducted, dispute follows</td></tr> <tr><td>Duty leave</td><td>Board exam duty, training, sports meets</td><td>Treated as absence because nobody filed the form</td></tr> <tr><td>Loss of pay</td><td>Beyond balance, or unauthorised absence</td><td>Applied inconsistently across departments</td></tr> </tbody> </table> <p>The attendance device matters less than the rule engine behind it. A ₹6,000 biometric reader with badly configured leave rules will create more disputes than a paper register, because now there is a machine to blame. Configure the rules first; the hardware is the easy part.</p> <h2>What the manual cycle actually costs</h2> <p>The salary register never appears in a budget because its cost is paid in staff hours and quiet errors. Here is where it shows up.</p> <table> <thead> <tr><th>Cost line</th><th>How it happens</th><th>Illustrative annual impact (120-staff school)</th></tr> </thead> <tbody> <tr><td>Payroll preparation time</td><td>2–4 days a month across accountant and clerk</td><td>₹1.8–3.6 lakh of staff time</td></tr> <tr><td>Re-work after errors</td><td>Wrong deduction, missed attendance, re-issued payslip</td><td>₹40,000–1 lakh</td></tr> <tr><td>Late PF / ESI deposits</td><td>Interest and damages levied by the department</td><td>₹25,000–1.5 lakh, avoidably</td></tr> <tr><td>Salary paid to exited staff</td><td>No exit status on the register; recovery is awkward</td><td>One month's salary per incident</td></tr> <tr><td>TDS correction and revised 24Q</td><td>Arrears not split by financial year</td><td>CA fees plus interest</td></tr> <tr><td>Principal's time on disputes</td><td>Every disputed payslip escalates to the office</td><td>2–3 hours a month, forever</td></tr> </tbody> </table> <p>These are illustrative ranges, not quotes — a 40-staff school will sit at the bottom, a 300-staff group at the top. The point is that the cost is not the software subscription. It is the four days, every month, plus the errors nobody logs.</p> <p>One more cost that never appears on any sheet: salary data is personal data. Bank accounts, PAN, PF numbers and home addresses sit in a register that lives in a cupboard. Under the DPDP Act 2023 that is a storage and access-control question, not just a filing question — which is why payroll belongs inside the same access-controlled system as student records, with an audit trail and a named data owner. Our <a href="/blog/post/school-software-data-security-checklist-india-dpdp-act-2023-2026/">DPDP security checklist</a> covers the questions to ask any vendor holding it.</p> <h2>A 30-day rollout that does not stop salary</h2> <p>The mistake almost every school makes is switching payroll in April, the same week as admissions and the new session. Do it in a quiet month, in parallel, and the risk drops to almost nothing.</p> <table> <thead> <tr><th>Week</th><th>What you do</th><th>What must be true before you move on</th></tr> </thead> <tbody> <tr><td>Week 1</td><td>Build the staff master — 11 fields, all 100% complete. Photograph PAN, bank proof and PF/ESI records.</td><td>Zero blank fields for the 20 highest-risk staff</td></tr> <tr><td>Week 2</td><td>Configure salary structures by grade and per-period formula, leave rules, and the attendance device feed.</td><td>Three test employees produce the exact current salary</td></tr> <tr><td>Week 3</td><td>Run the month in parallel — software and register side by side.</td><td>Difference of ₹0 on gross, deductions and net for every employee</td></tr> <tr><td>Week 4</td><td>Go live on the bank file and statutory outputs. Lock the register, keep it only as an archive.</td><td>Bank control total matches; ECR and 24Q data verified by the CA</td></tr> </tbody> </table> <p>Two rules make this stick. First, never run the first live payroll in the same month as an increment or arrears — you will not know whether a difference is a bug or a real change. Second, tell staff in advance what changes and what does not: payslip format, leave application route, and who to ask. Staff resistance to biometric attendance is almost never about the device; it is about not being told why. Our <a href="/blog/post/teacher-adoption-of-school-software-in-india-a-30-day-plan-2026/">30-day staff adoption plan</a> handles that conversation in detail.</p> <p>Finally, make sure payroll posts to accounts. If salary, PF and ESI are entered into Tally by hand after the salary run, you have automated the easy half and kept the error-prone half. The <a href="/blog/post/school-software-integration-india-whatsapp-upi-tally-2026/">integration checklist</a> covers what a clean Tally hand-off looks like.</p> <h2>The bottom line</h2> <p>The salary register is not a record. It is a monthly reconstruction of a month that has already happened, done by people who have other jobs. <strong>School payroll software India</strong> schools actually keep using does one thing well: it makes attendance, leave, salary and statutory filing describe the same number, so that a teacher's payslip, the bank advice and the PF challan all agree before anyone signs.</p> <p>That is worth more than the four days a month. It is worth the argument you stop having in the staff room on the 8th.</p> <p>If your school is still closing payroll by hand, start with the staff master — not the software. <a href="/saksham/">Saksham AI</a> includes staff attendance, leave, payroll and statutory outputs in the same platform as admissions, fees and academics, so there is one staff record instead of four. See <a href="/pricing/">what it costs for your school size</a>, or <a href="/#demo">book a free 30-minute demo</a> and bring one month of your salary register — we will run it live and show you the difference line by line.</p>