KEY OUTCOME
Monthly payroll processing: 4 days → 4 hours. HR calls for payslips and leave balance: 60+/month → near zero.
THE PROBLEM
The company ran a factory with 280 employees across three categories: 160 permanent staff on monthly salaries, 80 contract workers on fixed-term engagements with different PF eligibility rules, and 40 daily wage workers paid on an attendance-per-day basis. Each category had different payroll logic, different statutory treatment, and different payslip formats. All three were being managed in the same Excel workbook — a file that had grown over seven years into something no one fully understood except the HR manager who had built it.
Every month, payroll started with the biometric attendance download. The factory's biometric system exported a raw CSV — employee code, date, punch-in time, punch-out time, one row per day per employee. The HR manager imported this into a second Excel, matched employee codes to names manually, calculated present days, half-days, late arrivals, and absent days, then transferred the totals into the salary Excel. This step alone took two days. Any mismatch between the biometric export and the salary Excel — a wrong employee code, a missing entry from a system reboot — produced a payroll error that was discovered only when the affected employee called to report a salary discrepancy.
PF calculations were the most fragile part of the process. Employee PF was 12% of basic. Employer PF was split: 3.67% to EPF and 8.33% to EPS — but EPS had a ceiling of ₹15,000 on the pensionable salary, above which only EPF applied. Contract workers with Basic above ₹15,000 had a different calculation from those below. Daily wage workers who met the wage threshold needed to be included mid-month if they crossed it. The HR manager tracked all of this in a separate PF Excel, manually cross-checking with the salary Excel. Discrepancies were found during the annual PF audit — after the challan had already been filed.
ESI was managed separately again. Workers earning above ₹21,000 gross were exempt; those at or below it contributed 0.75% and the employer contributed 3.25%. Gross salary fluctuated every month based on overtime, incentives, and variable attendance — which meant the ESI eligibility of a worker could change month to month. The HR manager maintained a third Excel for this. When a worker crossed the ESI threshold mid-year, the transition had to be handled manually. It was not always caught in time.
TDS was the component the HR manager described as 'the one I'm most afraid of getting wrong'. The 280 employees had a mix of old-regime and new-regime tax choices. Declarations of HRA, 80C investments, and medical insurance premiums were collected in January on paper forms and manually entered into the TDS projection Excel. When an employee changed their declaration in February, the TDS for the remaining months had to be recalculated. Errors in TDS showed up in the employee's Form 26AS and became the HR manager's problem during tax season.
Professional tax varied by state. The company had a branch office in Maharashtra (where PT slabs were different from Haryana where the factory was located) and a few employees who had transferred between locations mid-year. PT for transferred employees was calculated incorrectly for two consecutive years before the error was identified during a state tax audit.
The employee experience was poor in ways that affected retention. A worker who wanted to know their leave balance had to call HR. A worker who wanted to verify a deduction in their payslip had to visit HR physically, because the payslip was delivered as a printed A4 sheet once a month and the HR manager had to pull out the salary Excel to explain any query. When a worker resigned and asked for their full and final settlement, the HR manager had to calculate earned leave encashment, notice pay adjustment, gratuity eligibility, and the final PF withdrawal process — all manually, across four separate files. The process took three weeks on average. Workers who needed the money faster had no recourse.
Salary revisions were another manual cascade. When a permanent employee received an increment, the HR manager had to update the salary Excel with the new CTC breakup, recalculate PF contribution on the new basic, recalculate TDS projections for the remaining months of the financial year, and calculate arrears for any months between the effective date and the processing date. For a 5% increment cycle covering 80 permanent employees, this exercise took a full week and was the source of a disproportionate number of errors.
“Payroll takes my HR manager four full working days every month. She is a qualified HR professional and she spends four days copy-pasting attendance data from one Excel into another, manually calculating PF deductions, and typing payslips in a Word template. That is not HR work. That is data entry.”
BEFORE
4 days
Every month consumed by the HR team to process payroll for 280 employees — from attendance to bank transfer file
12–15
Payroll errors requiring manual correction each month — wrong attendance, missed LOP, incorrect PF calculation
60+
Calls to HR every month from employees asking for payslips, leave balances, and salary clarifications
3 weeks
Average time to process full and final settlement for an exiting employee
PLATFORM WORKFLOW
Click any module to explore what was built
Every employee has a structured profile with their CTC breakup, bank details, PAN, Aadhaar, PF UAN, and ESI IP number. The system auto-applies the correct statutory logic — PF eligibility based on basic salary, ESI threshold by gross, and PT slab by state of posting — without the HR manager flagging anything manually.
THE SYSTEM
I built an integrated HR and payroll platform that handled all three employee categories — permanent, contract, and daily wage — with separate payroll logic per category but a single interface for the HR manager. Every calculation that was previously done in Excel was moved into the system's engine. The HR manager's job shifted from data entry and calculation to review and approval.
**Employee master:** Each employee has a structured profile — personal details, bank account (IFSC-validated), PAN, Aadhaar, PF UAN, ESI IP number, and document uploads (offer letter, identity proof, educational certificates) stored in GCS with access-controlled signed URLs. The CTC breakup is configured per employee: basic, HRA, special allowance, conveyance, medical reimbursement, LTA, and any company-specific components. The system validates the PF eligibility rule (basic above/below ₹15,000), ESI eligibility threshold, and PT slab based on the employee's state of posting — and applies the correct statutory logic automatically without manual flagging.
**Attendance integration:** The biometric system's daily attendance export is pulled into the platform via a scheduled SFTP job that runs at midnight. The system parses the CSV, matches employee codes, and calculates present days, half-days (based on configurable punch-in thresholds), late arrivals, and Loss of Pay days — for all 280 employees simultaneously. Exceptions — employees with no punch record, biometric failures, or manual adjustments — are surfaced in an exceptions queue for HR review. The HR manager reviews exceptions; the system handles everything else.
**Leave management:** Leave policies are configured per employee category — Earned Leave (accruing at 1.25 days per month for permanent staff), Casual Leave, Sick Leave, Maternity Leave (26 weeks), and Paternity Leave. Employees apply for leave through the self-service portal. The leave request routes to the employee's reporting manager for approval. Approved leaves auto-deduct from the balance and feed into the attendance module so the payroll engine sees approved leave as present rather than LOP. Leave balance is always current. The HR manager never needs to maintain a separate leave tracker.
**Salary calculation engine:** On the 26th of each month, the HR manager clicks Run Payroll. The engine pulls the month's attendance data and approved leaves, applies the salary structure for each employee, and calculates gross-to-net for all 280 employees in parallel. For daily wage workers, pay is calculated as (daily rate × days present). For contract workers, the engine checks PF applicability based on basic salary. For permanent staff, it applies the full CTC breakup with all components. The output is a salary register showing every employee's earnings, deductions, and net pay — reviewable before any disbursement is triggered.
**Statutory deductions — PF:** Employee PF is 12% of basic. Employer contribution is split: EPF at 3.67% and EPS at 8.33% — but EPS is capped at ₹15,000 pensionable salary. The system applies the cap automatically. For employees with basic above ₹15,000, the EPS ceiling calculation runs without the HR manager touching it. Voluntary PF contributions above the statutory rate are configured per employee and deducted correctly. On payroll approval, the system generates the ECR file for EPFO upload — formatted to the EPFO's exact specification, with the month's employee and employer contributions per UAN. The HR manager downloads the file and uploads it to the EPFO portal. No manual challan preparation.
**Statutory deductions — ESI:** The system tracks each worker's gross salary month by month. Workers whose gross is ₹21,000 or below are subject to ESI — employee contribution 0.75%, employer contribution 3.25%. When a worker's gross fluctuates due to attendance variation, the ESI applicability recalculates automatically. Mid-year threshold crossings are flagged for HR review. The ESI return file is generated on payroll approval and ready for upload to the ESIC portal.
**Statutory deductions — Professional Tax:** PT slabs are configured per state. Haryana PT (₹200/month for salary above ₹25,000) and Maharashtra PT (slab-based, ₹2,500/year collected in February) are both configured in the system. Employees who transferred between states mid-year have their PT recalculated from the transfer date. The PT register is generated monthly with the correct amounts per state for the company's PT return filing.
**TDS computation:** Each permanent employee declares their tax regime (old or new) at the start of the financial year. Old-regime employees submit investment declarations — Section 80C, HRA exemption (auto-calculated from rent receipts uploaded to the system), medical insurance premium under 80D, and LTA. The system projects annual income based on current salary structure and calculates the monthly TDS required to collect the full year's liability evenly across remaining months. When an employee changes their declaration in February or receives a salary revision, TDS recalculates automatically for the remaining months. Form 16 Part A and Part B are generated at the end of the financial year per employee and available for download from the self-service portal.
**Payslip generation and disbursement:** On payroll approval, the system generates a PDF payslip for every employee simultaneously — branded with the company name and logo, itemised earnings and deductions, net pay, YTD figures, and the statutory deduction breakdown. Payslips are pushed to the employee's self-service portal instantly. The bank transfer file is generated in the format required by the company's bank — RTGS bulk transfer format — and downloaded by the accounts team. The transfer is processed. Payroll is done.
**Full and final settlement:** When an employee's exit is logged in the system, the F&F module calculates automatically: earned leave encashment (at last drawn basic), notice pay recovery or payout based on whether the notice period was served, gratuity (if service is above 5 years: 15 days' basic per year of service), any outstanding advance recovery, and final salary for the days worked in the exit month. The system generates the F&F statement for HR review, the final payslip, and — after approval — the exit letter and Form 16 for the partial year. What took three weeks now takes two working days.
**Employee self-service portal:** Every employee logs in with their employee code and phone-verified OTP. They can download their payslip for any month, view their YTD salary summary, check their leave balance and application history, upload investment declarations for TDS, view their PF UAN and monthly PF credit statement, raise a salary query (which routes to HR with the relevant payslip attached), and download their Form 16. The 60+ monthly HR calls for routine payroll information dropped to near zero within the first month of the portal going live.
**Salary revision workflow:** When an employee receives an increment, the HR manager enters the new CTC breakup and the effective date. The system calculates the new component breakup, recalculates PF on the new basic, recomputes TDS projections for the remaining months of the financial year using the new salary, and calculates arrears for any gap between the effective date and the processing date. A revision letter is generated automatically. The entire process takes 15 minutes instead of a week.
Attendance data flows from the factory biometric system into payroll automatically. Late arrivals, half-days, and absent days are calculated as Loss of Pay without manual entry. The HR manager reviews exceptions — not raw data.
Click Run Payroll on the 26th. The engine calculates gross-to-net for all 280 employees — including PF (employee + employer), ESI, professional tax by state, and TDS under the old and new regime. The salary register, payslips, and bank transfer file are ready simultaneously.
Every employee logs in to download their payslip, apply for leave, check their leave balance, view their PF statement, and raise salary queries. The 60+ monthly HR calls for routine information drop to near zero.
THE OUTCOME
The most immediate and measurable change was in payroll processing time. The four-day monthly exercise — attendance download, manual LOP calculation, PF worksheet, ESI worksheet, TDS update, payslip typing — was replaced by a process that took 4 hours: 30 minutes to review the biometric exceptions queue, 20 minutes to review the salary register, 10 minutes to approve and download the bank transfer file. The HR manager described the first month as 'the first time in three years I've had time to actually do HR work in payroll week'.
Payroll errors dropped from 12–15 per month to an average of 1–2. The errors that remained were genuine edge cases — an employee who changed banks mid-month, an exceptional attendance pattern during a factory shutdown. The systemic errors — wrong PF calculation, incorrect LOP count, missed TDS update after a salary change — disappeared because the calculations were no longer manual.
The PF compliance improvement was significant beyond just time saved. The ECR file generated by the system was formatted correctly for EPFO upload from the first month. In the 11 months since go-live, there has been no PF challan discrepancy. The annual PF audit — which previously required 3 days of the HR manager's time to reconcile the payroll Excel with the ECR history — was completed in 4 hours by pulling the system's audit export.
The TDS recalculation capability proved its value in February, when 34 employees submitted revised investment declarations. In previous years, this had caused TDS to be under-deducted for the rest of the year — discovered by employees when their Form 26AS showed a shortfall. In the first year with the system, TDS was recalculated for all 34 employees within 24 hours of declaration submission. Form 16 was generated correctly for all 280 employees at year-end without a single error requiring correction.
The self-service portal addressed an HR workload that had not been quantified before: the 60+ monthly calls from employees asking for payslips, leave balances, and salary clarifications. Within the first month of portal go-live, HR logged 4 salary-related calls — all for genuine queries requiring HR judgement, not routine information retrieval. The HR manager's estimate was that the portal returned 6–8 hours per month of time previously spent on the phone.
The three-week F&F settlement cycle was the change that had the most direct impact on employee experience. In the 11 months since go-live, the average F&F settlement time across 7 employee exits has been 2 working days. In two cases where the employee needed the settlement urgently, it was processed on the same day. The Managing Director noted that the company's Glassdoor reviews had seen a noticeable shift — two reviews specifically mentioned that the exit process had been handled professionally and quickly.
Monthly payroll processing time
Payroll errors requiring correction
HR calls for payslips and leave balance
PF/ESI challan preparation time
Salary revision processing time
Full and final settlement time
Want a system like this for your manufacturing organisation?
Get a quote for HR & Payroll System