About Sapcon Instruments
Sapcon Instruments Pvt. Ltd. is an Indore-based manufacturer of level measurement and speed monitoring instruments. They have been in business for over 40 years and serve more than 15,000 clients in industries like cement, steel, packaging, and fuel. Their products – vibrating fork switches, RF capacitance transmitters, rotary paddles – are used in process automation plants across India and in international markets.
Sapcon has been on ERPNext for years. Accounts, operations, inventory – all running on the platform. But payroll was still being done through Excel sheets and manual registers. Every month the HR team would run a separate process outside the system, check numbers against multiple sheets, and hope nothing slipped through.
That is a situation many manufacturing companies in India find themselves in. The ERP is there, but payroll software for manufacturing environments – with daily workers, variable hours, government wages, and strict statutory rules – often turns out to be harder to implement than expected. This is the story of how that problem was solved at Sapcon.
What Made Payroll Difficult at Sapcon
It was not one problem. It was several, all connected.
Daily workers and salaried staff under the same roof
About half of Sapcon’s 500+ employees are daily-wage workers on the shop floor. They do not earn a fixed monthly salary. Their pay depends on how many days they worked, how many hours, and what government minimum wages apply based on their skill level – skilled, semi-skilled, or unskilled. These rates are also revised by the government roughly every six months. Managing this alongside a salaried white-collar workforce, within a single payroll system, with clean accounting output at the end – that is the core challenge of payroll software for manufacturing companies.
Overtime with no standard solution
Overtime is not optional at Sapcon – it is a regular part of how daily workers are compensated. The rules are specific. There is a minimum threshold before overtime is counted. Hours are rounded in set increments. If a worker has an absent day in the same month, that affects the overtime payout. And if someone works on a holiday or week-off, that also needs to be factored in. ERPNext does not handle overtime out of the box, and doing it manually outside the system meant a separate calculation every month with no audit trail.
Leave policies that are not uniform
Different departments at Sapcon follow different leave rules. When leave is credited, when it can be encashed, how unused balance is handled – none of this is the same across the company. Configuring multiple leave policies inside one system, so that each one runs correctly without manual intervention, required getting into specifics that most payroll software for manufacturing skips over.
Attendance data from biometric devices
Attendance at Sapcon comes from biometric check-in and check-out. At 500+ employees, that is a large volume of raw data that needs to be processed through shift rules, grace periods, and holiday calendars before it is usable. Any gap in that pipeline creates wrong numbers downstream in payroll.
PF, PT, and other statutory requirements
Provident Fund, Professional Tax, Labour Welfare Fund, EDLI contributions – each with its own calculation conditions and accounting treatment. Getting these right every month, and having the journal entries come out in the right accounts, is non-negotiable. The finance team at Sapcon was reviewing these manually and needed to see that a system could produce the same results reliably.
A finance team that needed convincing
The people who sign off on payroll at Sapcon had been working with manual registers for years. They were not going to sign off on a system just because it was implemented. They needed to see the numbers come out correctly – repeatedly – before they would trust it. That is not unreasonable. It is actually the right attitude. But it meant that the implementation had to be done carefully, with enough time built in to prove the system worked.
How CitrusLeaf Approached the Implementation
CitrusLeaf Software is an ERPNext implementation partner based in Indore. That local presence mattered from the start. Multiple site visits meant the team could spend time with Sapcon’s HR and accounts staff, go through their actual workflows, and understand the logic behind the Excel sheets before any configuration was done.
The approach was straightforward: understand first, build second. Training sessions ran in both directions – CitrusLeaf explained how ERPNext works, and Sapcon’s team explained how their payroll actually works. Both sides learned from each other. Every component, every leave type, every statutory rule was mapped out before anything was configured in the system.
The other principle was to keep customisations minimal. ERPNext has a lot of built-in flexibility. The goal was to use that flexibility as far as possible and only write custom code where there was genuinely no other way. When custom development was needed, it was built to be maintainable – not a workaround that only the person who wrote it can understand.
What Was Built
The implementation covered every part of the payroll process – salary structures, overtime, leave, attendance, statutory compliance, and payment disbursement.
Salary structures that match how pay actually works
Sapcon does not use a CTC structure. Pay is built around a fixed in-hand amount, with government minimum wages as the floor for daily workers and other components arranged around that. The salary structures in ERPNext were set up to match this exactly. Formula-based components mean that when minimum wages are revised or any input changes, the downstream numbers update automatically – no manual reworking of individual employee records.
Overtime built into the payroll workflow
A custom overtime solution was developed and connected directly to the Payroll Entry process. It pulls attendance data from the biometric system, applies all the rules around thresholds, rounding, absent-day adjustments, and holiday working, and generates the correct payroll entries without any manual calculation. The HR team now handles overtime as part of the regular monthly payroll – same screen, same workflow, no separate process.
Worth noting: The overtime solution was built as an extension of ERPNext’s standard payroll flow, not a replacement. That matters because it means the system stays maintainable as ERPNext is updated.
Leave configured department by department
Each department’s leave policy was set up as a separate configuration in ERPNext – its own leave types, allocation schedule, and encashment rules. Leave encashment was set up as a standalone transaction rather than being tied to the monthly salary slip, with the encashment amount calculated automatically from the employee’s daily salary rate. Once set up, allocations, carry-forward, and encashment all run on schedule without anyone having to trigger them manually.
Biometric attendance feeding straight into payroll
The biometric device data now feeds into ERPNext through the Employee Check-in module. Shift rules, grace periods, and holiday calendars are configured so that check-in and check-out times are automatically converted into clean attendance records ready for salary processing. A custom report gives HR a daily view of actual working hours and overtime across the workforce.
Statutory compliance with correct accounting
PF, PT, LWF, and employer contributions are set up as formula-based salary components with the correct eligibility conditions. Each one posts to the right ledger automatically. Payroll payable accounts are configured at the party level so that month-end reconciliation is straightforward and the finance team can verify entries without running separate calculations.
Bank-wise disbursement
Sapcon pays salaries from more than one bank account. A filter was added to the Payroll Entry screen so HR can separate employees by bank before running payroll. It removes a step that was previously done manually and eliminates a category of errors that came from that manual step.
Where ERPNext Helped
ERPNext was already in use at Sapcon. The question was whether it could handle the complexity of their payroll environment. The answer was yes – but it required proper implementation, not just switching on the HRMS module.
The formula-based salary component system meant that complex wage rules – government minimums, PF conditions, overtime amounts – could be expressed as configurations rather than code. The leave and attendance modules gave a solid structure to extend. And the built-in accounting integration was the most important feature in the whole project for one specific reason: every payroll journal entry posted directly to the correct accounts, automatically.
That is what payroll software for manufacturing needs to do, and it is what ERPNext delivered here. A standalone HR tool that produces a payroll register but leaves the accounting to be done separately would not have worked for Sapcon. The finance team needed the system to close the loop all the way to the books.
When they saw PF payable, PT payable, and salary payable all landing in the right accounts after the first few test runs, their position shifted. The numbers matched what they knew to be correct. That was the proof they needed.
Three Months Running Both Systems Together
The go-live approach was to run both systems – ERPNext and the existing Excel process – in parallel for three months. Every month, payroll was processed in ERPNext and then checked against the manual workings. Where numbers did not match, the team investigated and fixed the root cause.
Some gaps were configuration issues. Some were policies that had never been written down anywhere and only surfaced when a specific case was tested. All of them were fixed before the manual process was switched off.
By the end of three months, the numbers were matching across every type of employee and every payroll scenario. The finance team had seen it work. They had asked questions, found edge cases, and seen those too handled correctly. The trust was earned through evidence, not through a presentation.
Being a local partner made this phase significantly easier. When something came up that needed to be reviewed face to face, the CitrusLeaf team could be at Sapcon’s office. That speed of resolution – and the working relationship that came from it – was a real factor in how the project finished.
Where Things Stand Now
Sapcon’s payroll runs entirely inside ERPNext. The change is visible across the business:
- 500+ employees processed through a single payroll system each month – no Excel running alongside.
- Overtime, attendance, and leave calculated automatically, with all rules applied consistently every month.
- Leave encashment processed on schedule for each department, with amounts and accounting entries generated automatically.
- PF, PT, and LWF handled inside the payroll structure, with clean journal entries and no manual reconciliation.
- Finance team reviewing payroll accounting that matches their expectations, every month, without needing to verify it against a separate calculation.
- Salary disbursement across multiple bank accounts done through a filtered, one-step process.
Bottom line: A payroll process that was being managed through Excel and institutional memory is now running on ERPNext – accurately, on time, with full accounting integration.
What This Means for Other Manufacturing Businesses
Sapcon is not unusual. Most manufacturing companies in India with a mixed workforce – daily workers, salaried staff, government wages, shift-based attendance – face some version of this same payroll problem. Generic payroll software does not handle it well. It either lacks the flexibility for complex wage structures, or it handles payroll in isolation without the accounting integration that finance teams need.
ERPNext, properly configured, handles it. But the implementation has to be done right – with enough time spent understanding how the business actually works, with customisations that are minimal and maintainable, and with a validation process long enough for the finance team to trust what they are seeing.
If your manufacturing business is still running payroll outside your ERP, or if you have tried to implement payroll software before and it did not stick, the issue is usually not the platform. It is the approach.
CitrusLeaf implements ERPNext HRMS and payroll for manufacturing and industrial businesses across India. If payroll has been a problem your ERP has not been able to solve, we are happy to talk through why.
