Walk into the back office of almost any Indian SMB on the 1st of the month and the same scene plays out. The HR person squints at a biometric export. The accountant has three Excel files open — attendance, last month's salary, arrears and reimbursements. A WhatsApp group is full of "sir, my OD was approved but not reflected" and "please correct my LOP". A printer is warming up to produce 70 salary slips for folding by hand.
Payroll is the one process every employee notices the instant it goes wrong. A salary credited a day late, a PF number missing in Form 16, a wrong basic that messes up gratuity at exit — each becomes a story that travels faster than any internal memo. And yet in most Indian SMBs of 30 to 300 employees, payroll still runs on a stitched-together combination of biometric software, three or four Excel sheets, a separate Tally or accounting tool for ledger postings and a "trusted" external consultant who handles PF, ESI and TDS returns once a quarter.
This guide covers what HR and payroll management really means inside a modern ERP, the realities specific to Indian SMBs, and an Ahmedabad case study with concrete rupee impact.
Why HR & Payroll Belong Inside the ERP — Not Beside It
The argument against running payroll inside the ERP usually goes: "We have a biometric system, our CA handles PF and TDS, and salary slips are generated in Excel — why disturb a working setup?" The honest answer is that the setup is not actually working; it is held together by one or two trusted people whose calendars block out the last week of every month and whose exit would create a small crisis. The cost of that fragility never lands on the P&L, so it stays invisible until something breaks.
An ERP that owns HR and payroll natively does three things a stitched setup cannot:
- One employee master, one salary structure, one source of truth. Attendance, leave, advances, reimbursements, statutory deductions and salary postings all reference the same employee record — no more "the name in PF portal does not match the name in salary register" reconciliations.
- Payroll posts directly to the accounting ledger. Each month's salary, PF employer share, ESI employer share, gratuity provision and bonus provision land in the right ledgers automatically. The connection to financial management and accounting is real-time, not retrospective.
- Statutory effort collapses. PF ECR, ESI contribution file, professional tax challan, Form 24Q quarterly return, Form 16 and gratuity workings are all derived from the same payroll run — not assembled from screenshots at quarter-end.
The Indian Payroll Reality No Generic HR Tool Handles Well
Most globally-marketed HR tools handle India "as a region" rather than as a primary market — and the gaps show up exactly where the cost of a mistake is highest. An ERP built for Indian SMBs has to understand the following without configuration heroics:
Salary structures that look Indian
Basic, HRA, DA where applicable, conveyance, medical, special allowance, LTA, performance pay, attendance allowance, shift allowance, washing allowance, food coupons and a dozen other heads — each with its own taxability, PF applicability, ESI applicability and proration logic. The structure must be a template so that adding the 71st employee is one click, not one hour.
Statutory deductions handled at source
PF at 12% on Basic + DA (with the wage-ceiling rule, the voluntary higher contribution option and the EPS split), ESI at the prevailing rates with the wage-ceiling cut-off, Professional Tax by state slab (different in Gujarat, Maharashtra, Karnataka, West Bengal and Tamil Nadu), Labour Welfare Fund where applicable, TDS on salary under section 192 with old-regime versus new-regime selection, and the 80C / 80D / HRA / home-loan exemptions that go with it. None of this should require a separate consultant once configured.
Attendance and leave with Indian operational realities
Multiple shifts, night-shift allowances, weekly-off rotation, state-specific holidays, sandwich-leave rules, half-day handling, late-mark and grace-time logic, on-duty marking for field staff, work-from-home days and biometric-miss handling all have to flow into payroll with an audit trail. Casual leave, sick leave, earned/privilege leave with accrual and lapse rules, maternity leave under the Maternity Benefit Act, paternity leave per company policy, compensatory off and leave encashment must each carry their own carry-forward, lapse and eligibility logic — without an HR person doing year-end calculations on a calculator.
Full-and-final settlement and statutory returns
Exit notice period, recoverable items (laptop, ID card, advance, training bond), payable items (last salary, leave encashment, gratuity if eligible, pro-rata bonus, reimbursements), Form 16 issuance, PF transfer support and relieving letter generation — one workflow, not eight emails. Form 24Q quarterly with annexures, Form 16 and Form 12BA at year-end, gratuity actuarial workings, bonus register under the Payment of Bonus Act and Form C / Form D under the Minimum Wages Act should all derive from the same payroll history.
From Joining to Salary: 7 Steps in ApicalERP HR & Payroll
Employee Onboarding & Master Setup
New joiner record captures personal details, KYC, PF and ESI numbers, PAN, bank account, salary structure, reporting manager, department, branch and cost centre. Document checklist (offer letter, KYC, education proofs, previous Form 16) is tracked with status. Biometric enrolment and ID card generation are triggered from the same record.
Daily Attendance Capture
Biometric devices push punches into the ERP through scheduled sync or live API. Mobile app captures field-staff attendance with GPS stamp for off-site days. Shift assignment, weekly off, public holiday and on-duty marking are applied automatically. Late marks, half days and missing punches surface for HR review the same day, not at month-end.
Leave & OD Approval Workflow
Employee raises a leave or OD request on the self-service portal or mobile app. The request routes to the reporting manager with available leave balance shown. Multi-level approval is supported for longer leaves. On approval, attendance and leave balance update automatically. Pairs with our document management and approval workflows guide.
Monthly Payroll Run
On the payroll cut-off date, the system pulls attendance, approved leaves, OD days, holidays, weekly offs, advances, reimbursements and one-time adjustments. Each component of the salary structure is calculated per the configured rules. LOP is auto-derived. Variable components (overtime, attendance allowance, incentives) flow from their source records. A draft payroll register is produced for HR review.
Statutory Deductions & Net Salary
PF (employee + employer + EPS split), ESI, Professional Tax by state, Labour Welfare Fund, TDS under section 192 (old or new regime per declaration), recoverable advances, loan EMIs and other authorised deductions are applied. The net salary, salary slip and a per-employee tax computation sheet are generated in one pass.
Bank Transfer & Salary Slip Delivery
A bank-format salary file (NEFT or company-specific bank format) is generated for upload. Salary slips are emailed to each employee and made available on the self-service portal. A consolidated salary JV posts to the accounting ledgers automatically — salary expense, statutory liabilities, net payable — with full traceability back to the payroll run.
Statutory Filing & Year-End
PF ECR, ESI contribution file, PT challan working, Form 24Q quarterly return, Form 16 and Form 12BA at year-end, bonus register, gratuity provision and leave-liability workings are all generated from the same payroll history. F&F settlement at exit is a one-click workflow with all dues, recoveries and statutory closures handled together.
Core HR & Payroll Capabilities to Insist On
Attendance & Shift Management
Biometric, mobile and web punch with shift, weekly-off, holiday and OD logic — applied automatically.
- Direct integration with common biometric brands
- Mobile app with GPS for field and site staff
- Multi-shift, night-shift, rotational and split-shift support
- Late mark, grace time, half-day and missing punch handling
- State-wise holiday calendars and branch overrides
Leave Management
Multiple leave types with accrual, lapse, carry-forward and encashment rules — all employee-visible.
- CL, SL, EL/PL, ML, paternity, comp-off, LOP all tracked
- Configurable accrual frequency and lapse rules
- Self-service application and approval via mobile
- Real-time balance visibility to employee and manager
- Year-end encashment and carry-forward automation
Salary Structure & Payroll Engine
Indian salary structure templates with PF, ESI, PT and TDS handled at source — every cycle, every employee.
- Template-based structures for grade, role and branch
- Basic, HRA, DA, conveyance, medical, LTA, special heads
- PF wage-ceiling, EPS split and voluntary contribution logic
- State-wise PT slabs and ESI ceiling cut-offs
- TDS under section 192 — old regime and new regime
Statutory & Year-End Filings
PF ECR, ESI file, Form 24Q, Form 16, Form 12BA, bonus register, gratuity provision — all native.
- PF ECR file and ESI contribution file generation
- Form 24Q with annexures every quarter
- Form 16 and Form 12BA at year-end per employee
- Gratuity, leave-encashment and bonus provision workings
- Audit-ready registers under Bonus Act and Minimum Wages Act
The Components Indian SMB Payroll Has to Get Right
It is one thing to "run payroll". It is another to run it for an Indian SMB where the workforce is a mix of office staff, shop-floor workers, contract labour, field sales reps and apprentices — each with different attendance logic, statutory treatment and leave entitlement. A serious ERP HR module handles each component cleanly.
Employee master and salary structure as a template
One employee, one record — personal details, KYC, PAN, PF UAN, ESI IP, bank account, nominees, salary structure, reporting manager, department, branch, cost centre, joining date. Salary structures are defined as templates per grade, role or branch — never hand-built per employee. Each head carries metadata: taxable or exempt, PF applicable, ESI applicable, proratable, recurring or one-time. Adding a fuel allowance for field staff is one template edit, not 40 spreadsheet rewrites.
Attendance the way Indian factories and offices actually work
Biometric punches flow from devices into the ERP, where they hit shift, weekly-off, holiday and on-duty logic. A factory with general shift plus two production shifts plus security on a four-shift roster needs the ERP to assign the correct shift per employee per day. Late marks, half days and missing punches need sensible rules — three late marks become one half-day, two consecutive missing punches become an absence. Field sales staff need a mobile app with GPS-stamped attendance, because they will never reach a biometric device.
Statutory deductions calculated, not assumed
PF at 12% on Basic + DA, subject to the wage-ceiling rule, with the EPS split applied correctly so the pension portion is capped and the balance flows into the employee EPF account. ESI at the prevailing rate up to the wage-ceiling cut-off, with the half-year contribution-period logic respected. Professional Tax by state slab. Labour Welfare Fund where applicable. TDS under section 192 with the employee's regime selection (old vs new) honoured, 80C / 80D / HRA / home-loan exemptions worked into the monthly TDS — no March surprise.
Variable pay, reimbursements, loans and disbursal
Incentives, OT, shift allowance, performance pay and festival bonus each need a clean source — incentive from the sales register, OT from the attendance log, bonus from an HR-authorised note. Reimbursements (mobile, fuel, travel) need their own workflow with bills attached. Loans and advances carry an EMI schedule that auto-deducts and auto-recovers at F&F. A bank file in the company's bank format (HDFC, ICICI, SBI, Axis) is generated for direct credit; salary slips are emailed and on the portal — no folding and stapling. The consolidated salary JV posts to the right ledgers automatically — salary expense by cost centre, PF / ESI / PT / TDS payables, salary payable, advance recovery — so finance enters zero manual vouchers for payroll. The connection to the financial management module is built in.
| Aspect | Biometric + Excel + Tally + Consultant | ApicalERP HR & Payroll |
|---|---|---|
| Monthly Payroll Close | 4-6 working days; last day always a fire | 2-4 hours once attendance is locked; no fire |
| Source of Truth | Excel of attendance, Excel of salary, separate Tally JV | One employee record; payroll posts straight to ledger |
| Statutory Returns | Outsourced; quarterly scramble; corrections frequent | PF ECR, ESI, PT, 24Q, Form 16 generated natively |
| Leave Balance Visibility | Asked by email; reconciled at year-end | Live on employee self-service and mobile app |
| Field Staff Attendance | Manual marking; disputes every month | Mobile app with GPS-stamped punch |
| Full & Final Settlement | 3-6 weeks; relieving letter delayed; disputes common | Within 7 working days; single workflow; clean exit |
| Salary Slip Delivery | Printed, folded, stapled, distributed by hand | Emailed and on self-service portal — instant access |
| Audit Readiness | Reassembled from Excel and consultant files at audit | Registers, ledgers and returns available on demand |
Self-Service That Employees Actually Use
The single biggest unlock from an ERP HR module is taking transactional questions off the HR person's desk. In a 100-person company, an HR head on salary-slip-day answers the same six questions: how much CL is left, why is my OT short, when will my reimbursement be paid, can I change my tax regime, where is my Form 16, why has my PF UAN not been issued. A real self-service portal answers all six without a single email.
What "good" self-service looks like for an Indian SMB:
- Profile and KYC on first login. Employee verifies personal details, uploads PAN and bank proof, updates nominees and dependents — no Excel form circulated by HR.
- Attendance and leave at a glance. Monthly attendance summary, late marks, half-days, leave balance by type, last six months of history. Disputes raised via workflow with the punch evidence attached.
- Apply for leave on mobile. Pick dates, type, balance shown live, submit to reporting manager. Status visible, cancellation supported — no "did you approve my leave?" WhatsApp messages.
- Reimbursement claims with bill attachment. Employee uploads bill photo, selects category, submits. Approved reimbursements flow into the next salary automatically.
- Tax regime declaration and investment proofs. Employee picks old or new regime once a year, declares 80C / 80D / HRA / home-loan interest, submits proofs at year-end. Monthly TDS reflects the declaration immediately.
- Salary slips, tax computation and document repository. Last 12 slips, current year's tax computation, Form 16 history, offer letter, increment letters and training certificates — all on demand.
When self-service works, the HR function shifts from data entry to actual people work — onboarding, training, performance, retention. That is the single largest soft return on an ERP HR implementation.
Benefits of ERP HR & Payroll Management
Implementation Best Practices
HR and payroll go-live is unlike any other ERP module because the cost of a single mistake is an unhappy employee on payday. The rollout pattern that consistently works in Indian SMBs:
1. Clean the employee master before anything else
- Audit every active record: PAN, bank account, PF UAN, ESI IP, salary structure, joining date, reporting manager
- Fix PF portal vs salary register name mismatches now — this single fix eliminates 80% of Form 16 corrections later
- Assign cost centre, department and branch correctly — these drive every report and ledger split
- Lock master-creation rights to HR head plus one backup
2. Configure salary structures as templates, not per employee
- Build 5-8 templates covering office, shop floor, field sales, supervisor, manager, leadership and apprentice
- Each template fully defines basic ratio, allowance heads, PF/ESI applicability, taxability and proration
- Assign each employee to a template plus a gross figure — never hand-build a structure for one person
3. Parallel run for two cycles before retiring the legacy
- Run ERP payroll and the legacy Excel payroll side by side for at least two months
- Reconcile every variance employee by employee — they surface real master-data and rule-config errors
- Sunset the legacy only when HR and finance agree the ERP is more accurate
- Do not skip under timeline pressure; one wrong payroll undoes a year of goodwill
4. Drive self-service adoption from day one
- Mandate that leave, reimbursement and investment declarations come only through the portal — no email, no paper
- Run a 20-minute training for every employee on the mobile app within the first week
- Make salary slips available only on the portal after month two — printed slips quietly retire themselves
5. Connect to accounting and lock the cut-off
- Map every salary head to a ledger before the first ERP payroll run; verify auto-JV against manual JV for three months, then trust it
- Set a hard attendance cut-off date (typically the 25th) after which the cycle is frozen — system enforces, not the HR person
- Late corrections flow into the next cycle as adjustments, not back into the closed month
- This single discipline collapses the month-end firefight more than any other change
6. Rehearse year-end and exit cycles
- The monthly run is one workflow; year-end (Form 16, gratuity, bonus, leave encashment) is another — walk through a mock before March
- Walk through a mock F&F settlement before any real exit
- Both are infrequent and high-stakes; rehearsal is mandatory
Real-World Success Story
👥 Case Study: Ahmedabad Precision Engineering Company
Company Profile: ₹46 crore turnover precision-engineering and machined components manufacturer headquartered in Ahmedabad (Gujarat), supplying to automotive OEMs and tier-1 customers across western India. Workforce of 138 — 28 office and management staff, 84 shop floor operators and technicians across two production shifts, 14 contract security and housekeeping staff billed separately, 8 field sales and service representatives, and 4 apprentices. Three locations — head office and main plant in Ahmedabad, a finishing unit at Vatva, and a small warehouse-cum-dispatch point near Sanand. Heavy statutory load — monthly PF and ESI, quarterly Form 24Q, annual Form 16 generation, factory licence renewals, labour-law returns and ISO/TS audits.
Challenges Before ApicalERP:
- Five-day payroll close: The HR executive and the senior accountant together spent 4-5 working days on every monthly payroll — biometric export, Excel attendance compilation, manual LOP calculation, salary computation in another Excel, statutory deductions worked separately by the external consultant, salary slip printing, and finally the manual Tally JV. The 1st of every month was effectively a write-off for both
- Three sets of numbers, three sources of truth: The biometric report, the HR attendance sheet and the supervisor's manual register routinely showed different numbers for the same employee for the same month; salary disputes were common, especially among shop-floor staff
- Statutory penalties paid year after year: PF ECR was filed late in 4 of the previous 12 months due to consultant unavailability and Excel reconciliation delays; ESI corrections were submitted twice in the same year; cumulative interest, damages and late-fee outgo was approximately ₹1.85 lakh in the year before ERP — and the more painful cost was three notices from the regional PF office that required an officer's day to respond to
- TDS surprises every March: Investment proofs were collected on paper in February, computed manually by the consultant, and the last two months' TDS often spiked sharply to recover under-deducted amounts; six employees per year on average filed grievances about year-end TDS that they did not anticipate
- Field sales attendance disputes: The 8 field sales and service staff marked attendance through phone calls to HR or supervisor sign-offs on monthly visits to head office; disputes about absent days, customer visits and travel days were a monthly affair, with the HR head spending hours per cycle resolving them
- Leave balance was a black box: Leave was tracked in a single Excel maintained by the HR executive; balances were reconciled only at year-end, by which time discrepancies of 3-5 days per employee were common; year-end encashment computation took 3 days
- F&F settlement stretched 4-6 weeks: Exits required the HR executive to manually compute leave encashment, gratuity, recoveries, last salary and TDS — followed by physical sign-offs from department head, IT, accounts and admin; relieving letters were delayed by 30-45 days routinely; two ex-employees had filed labour-court grievances over unsettled dues in the previous two years
- Form 16 was a year-end project: The external consultant took 4-6 weeks every year to generate and distribute Form 16s; corrections came back from employees for the next 6 weeks; some employees filed personal IT returns with provisional figures because Form 16 had not arrived
- HR strategic work crowded out: The HR executive spent so much time on attendance reconciliation, payroll firefighting and statutory chasing that onboarding, performance reviews and training calendars were perpetually slipping; attrition among shop-floor staff was running at 28% annually with no documented exit-interview pattern
ApicalERP HR & Payroll Implementation Results (12 months):
- Payroll close from 5 days to 4 hours: Biometric integration plus a 25th-of-the-month attendance freeze and template-based salary structures collapsed the monthly run to 4 hours of HR review plus a 1-hour finance review; the 1st of the month went from firefight to a normal working day; recovered approximately 50 person-days of HR and accounting effort per year
- Single source of truth: Biometric punches flow directly into the ERP; shop-floor supervisor disputes are now raised inside the system against the biometric record with evidence, not as parallel registers; monthly salary disputes dropped from 8-12 per cycle to under 2
- Zero statutory late filings: PF ECR, ESI contribution and PT challan workings are generated on the day the payroll closes; in 12 months of ERP-driven payroll, zero late filings, zero correction returns; statutory penalty outgo of ₹1.85 lakh recurring per year eliminated entirely; one PF officer visit during this period was closed in 20 minutes with on-screen evidence
- TDS smoothing across the year: Investment declaration is captured on the portal in April and updated through the year; monthly TDS reflects the declaration immediately; year-end TDS spike eliminated; zero grievances on year-end TDS this year (versus 6 the previous year)
- Field sales attendance closed: All 8 field reps now mark attendance through the mobile app with GPS stamp; HR head time on attendance disputes for this group dropped from approximately 6 hours per month to under 30 minutes; supervisor approval of field visits is now a workflow with evidence, not a memory test
- Leave balance live on phone: Every employee sees real-time leave balance by type; year-end leave encashment calculation that took 3 days now takes under an hour; carry-forward and lapse rules apply automatically per policy; no disputes on leave balance in the past 8 months
- F&F in 5 working days: Single workflow handles last salary, leave encashment, gratuity, recoveries, TDS adjustment, relieving letter and Form 16 partial; average F&F closure cycle dropped from 4-6 weeks to 5 working days; zero new labour-court matters in 12 months; two earlier matters were settled and closed using audit-ready ERP records as evidence
- Form 16 issued within two weeks of year-end: Form 16 and Form 12BA for all 138 employees generated and emailed within 14 days of year-end (versus 4-6 weeks earlier); employee corrections in the first 6 weeks dropped from a typical 15-20 to 3; consultant fee for Form 16 generation of approximately ₹40,000 per year eliminated
- HR shifted from transactions to people: HR head recovered approximately 70 hours per month of self-service-driven time; onboarding workflow tightened, three exit-interview pattern reports identified two consistent attrition causes (shift roster fairness and lack of skill-pay clarity), corrective actions reduced shop-floor attrition from 28% to 19% in the year
Total Annual Financial Impact: Approximately ₹1.85 lakh of statutory penalty and interest outgo eliminated, ₹40,000 consultant fee for Form 16 eliminated, roughly ₹4.2 lakh of HR and accounting time recovered, approximately ₹6 lakh of attrition-related rehire and training cost saved through the 9-point attrition drop, plus the harder-to-quantify gains from clean F&F settlements (zero new labour matters and faster ex-employee resolution). Documented recurring annual benefit of around ₹12 lakh in direct P&L impact plus significant risk reduction on statutory and labour-law fronts — payback on the HR and payroll module well inside the first six months.
Key Success Factors: The implementation team insisted on a two-cycle parallel run with the legacy Excel and consultant-driven payroll before the ERP took over fully — every variance found in those two months was traced to a master-data error (mostly PF UAN mismatches and incorrect cost-centre tagging) and fixed at root. Salary structures were rebuilt as eight templates covering all worker categories, not 138 individual structures. The 25th-of-the-month attendance cut-off was enforced through the system, not through reminders — this single discipline collapsed the month-end firefight. Self-service adoption was pushed hard from week one — leave applications stopped being accepted by email or paper after week three. The CFO sponsorship was visible — the auto-posted salary JV was reviewed by finance every month for the first quarter, after which it was trusted unconditionally. The HR head moved from being the payroll fire-fighter to being the people leader the company actually needed, and that single role evolution is what made the ROI sustainable.
Common Mistakes to Avoid
HR and payroll rollouts go wrong in remarkably consistent ways. Watch for these traps:
- Going live without parallel runs. Two cycles of ERP payroll alongside the legacy is non-negotiable. Skipping this guarantees a salary mistake in month one and erodes a year of trust.
- Building salary structures per employee. Hand-built structures for 100 employees become 100 versions of "almost the same thing" — use templates, always.
- Treating attendance as an afterthought. If biometric, mobile and shift logic are not designed before payroll go-live, every month becomes attendance reconciliation week.
- Letting investment declarations stay annual and on paper. Move to the portal from day one and refresh annually — the year-end TDS spike disappears.
- Skipping self-service. Without it, HR remains the bottleneck for every leave query and the ERP is seen as "just another tool".
- Not connecting payroll to accounting. If finance still enters a manual salary JV after the ERP runs payroll, the two systems drift apart within months.
- Treating F&F as a paper process. Email and physical sign-offs take weeks; a workflow-based F&F closes in a week.
- Forgetting state-specific rules. PT, holidays, minimum wages and labour-law returns vary by state — assume nothing is national.
Conclusion
For an Indian SMB of 30 to 300 people, the gap between "we have an HR person and a payroll consultant" and "we run HR and payroll from the ERP" is one of the largest invisible cost lines in the business. The stitched-together setup that feels free is actually paid for in HR firefighting time, statutory penalties, employee disputes, delayed Form 16s, drawn-out exits and the slow attrition of the HR function itself into a data-entry role.
An ERP that owns HR and payroll natively turns each of those costs around. Payroll closes in hours instead of days. Statutory filings happen the same day the payroll runs. Employees check their own leave, apply for their own reimbursements and download their own Form 16. Exits close cleanly inside a week. The salary JV posts straight to the ledger. The HR head finally has time to do HR — onboarding, performance, retention, culture — instead of recompiling attendance from three sources.
The right time to put this in place is before the next payroll surprise — the late PF filing, the angry shop-floor query about LOP, the F&F that drags into a labour-court matter. ApicalERP ships with template-based Indian salary structures, biometric and mobile attendance, a complete leave engine, PF / ESI / PT / TDS at source, native Form 24Q and Form 16, self-service portal and mobile app, single-workflow F&F and direct posting to the accounting ledger — built for how Indian SMBs actually run payroll.