The problem: twelve locations, zero shared truth
A global automotive MNC operating manufacturing and assembly facilities across twelve locations had, over decades of growth, accumulated an HR data landscape that no one had intentionally designed. Each major location had its own attendance system, often from a different vendor. Leave policies existed in policy documents but were applied inconsistently — the rules for casual leave encashment were interpreted differently at three different plants. Contractor workforce data lived entirely outside any formal system.
The organisation employed more than 15,000 people across direct and indirect categories: permanent employees on the core payroll, fixed-term contract employees, third-party contractor staff, and apprentices under statutory schemes. Each category had different entitlements, different compliance requirements, and historically had been managed by different teams using different tools.
The core payroll and personnel master were managed in SAP HCM. Talent and performance management lived in SuccessFactors. Attendance data came from biometric recorders — hardware from multiple vendors, some cloud-connected, some requiring manual data pulls. Leave applications were submitted through an internal intranet portal that could not enforce approval hierarchies correctly for multi-level management structures. Travel advances and expense claims were handled via email.
Every payroll cycle, the HR operations team spent several hours reconciling attendance data before it could be fed into SAP for processing. Discrepancies between biometric records and supervisor approvals were common. Late-night plant shifts created attendance records that straddled calendar dates in ways the intranet system could not handle. The result was a payroll run that was stressful, error-prone, and required heroic effort from a small team to complete on time each month.
The solution: a unified HRMS with differentiated access
The core design principle of Teamnet HRMS for this deployment was that a single platform must serve meaningfully different user populations. A shop floor operator accessing the system from a shared terminal at a plant gate has different needs — and a different tolerance for interface complexity — than a plant HR manager running headcount reports or a senior executive approving a travel policy exception.
The system was built with distinct UI modes for direct and indirect employees. Direct employees — those on the permanent payroll — access a full-featured self-service portal covering leave applications, attendance history, payslips, travel requests, expense claims, and personal data updates. Indirect employees and contractors access a simplified interface covering only the transactions relevant to their status: shift attendance, gate pass requests, and contractor-specific compliance documents.
Behind both interfaces is a single employee master and a single policy engine. Leave entitlements, shift patterns, attendance rules, and approval hierarchies are configured once, at the policy level, and apply consistently across all twelve locations. Location-specific overrides — where a particular plant has a legitimately different policy under its settlement agreement — are handled as policy variants rather than as separate system configurations.
Multi-level conditional approval workflows were a specific requirement driven by the complexity of the management structure. A travel request from an employee in a certain band requires approval from the direct supervisor and the department head. Above a certain amount, it requires additional sanction from the plant HR manager. If the direct supervisor is on leave, the workflow automatically reroutes to the designated alternate. These rules are configured in the workflow engine, not hardcoded — HR administrators can modify approval chains without a software release.
Integration architecture: SAP, SuccessFactors, and the attendance layer
The integration requirements for this deployment were among the most complex the team had encountered. SAP HCM was non-negotiable as the payroll engine — the organisation had invested years in its payroll configuration, and the risk of migrating that configuration was correctly assessed as too high. SuccessFactors was similarly entrenched as the performance and talent platform.
The design decision was therefore to position the HRMS as the operational HR layer — the system where day-to-day HR transactions happen — while treating SAP HCM and SuccessFactors as integration targets rather than replacements. Bidirectional sync ensures that the employee master in the HRMS and the personnel master in SAP HCM are always consistent. Attendance data processed in the HRMS is pushed to SAP HCM in the format required for payroll computation. Leave balances are maintained in the HRMS and reflected in SuccessFactors.
The attendance recorder layer was rationalised as part of the deployment. Existing biometric devices that supported cloud-direct connectivity were reconfigured to push punch data directly to the HRMS. Legacy devices that could only export files were replaced with cloud-connected units. The HRMS now receives punch data from all twelve locations in real time, applies shift rules and exception logic, and presents processed attendance records for supervisor approval — a workflow that previously required manual data extraction and spreadsheet processing.
Attendance processing used to start at 8 AM and sometimes wasn't done until after lunch. Now it's a 15-minute review of exceptions. The rest is automated.
Contractor and canteen management: the long tail of workforce data
Enterprise HR systems typically focus on permanent employees and treat contractor workforce management as an afterthought. For a manufacturer with a substantial contingent workforce, this gap is significant. Contractors move between locations, their engagements are time-bound, their compliance documentation must be tracked against statutory deadlines, and their attendance data must be reconciled with billing from the contractor firm.
The HRMS manages contractor workforce alongside direct employees but with a separate data model that captures contractor-firm relationships, engagement validity, PF and ESIC registration status, and skill certifications. Automated alerts fire when a contractor's engagement is approaching expiry or when a compliance document is due for renewal. This visibility replaced a manual tracking spreadsheet that was perpetually out of date.
Canteen management was integrated at the request of the facilities team. Employee meal bookings, subsidy calculations based on grade and shift, and vendor billing reconciliation now run through the HRMS. The canteen data also feeds the access control system — employees who have not clocked in for the day cannot book a subsidised meal, eliminating a category of leakage that had been difficult to audit manually.
Results: from reconciliation to exception management
The shift in how HR operations works is best described as a transition from reconciliation to exception management. Before the deployment, most of the team's time was spent producing correct data from incorrect or incomplete inputs. After the deployment, the data is correct by default, and the team's time is spent reviewing the edge cases — the genuine exceptions that require human judgement.
- Attendance processing: The daily attendance run for 15,000+ employees went from several hours of manual work to a 15-minute review of system-generated exception reports. The processing time reduction — 93% — reflects the elimination of manual data extraction, format conversion, and reconciliation steps.
- Policy compliance: Leave encashment rules, overtime eligibility, and statutory entitlements are now enforced by the system. HR business partners at each location no longer receive escalations about policy inconsistencies between plants.
- Employee self-service: The volume of routine HR queries — leave balance enquiries, payslip requests, travel advance status — dropped substantially after self-service went live. HR teams report that their inbound query volume fell by more than half within the first quarter.
- Single source of truth: Headcount reports, compliance reports, and payroll inputs now come from one system. The previous situation — where SAP HCM, SuccessFactors, and various local spreadsheets gave different answers to the same question — has been resolved.
- Audit readiness: Statutory compliance audits, previously a multi-week exercise in assembling documents from multiple systems, can now be addressed from a single audit export. PF, ESIC, and labour law compliance data is maintained in the system as a by-product of normal operations.
The deployment also shifted the relationship between HR operations and the business. When HR data is reliable and accessible, business managers begin to use it — headcount analysis, attrition trends, overtime patterns — as inputs to operational decisions. That shift, from HR as an administrative function to HR as a data source for management, is perhaps the least visible but most durable outcome of the project.