What is HRMS software development?
HRMS software development is building a human resource management system around your own policies, instead of adapting your policies to a product. The finished system holds employee records, calculates leave and attendance, routes approvals and gives employees a self-service app, and it belongs to you.
An HRMS (human resource management system) covers the whole employee lifecycle, from offer letter to exit. Payroll is sometimes part of it and sometimes a separate system it feeds. The build usually has three faces: a web app for HR and managers, a mobile app for employees, and background jobs that pull biometric punches, apply leave accruals and send reminders.
At BtechWaleTech, one of us builds the application, another of us handles cloud hosting on AWS, data modelling and reporting, and the third of us runs the project plan and the workflow automation. Being three freelance developers, we suit employers from a few dozen to a few thousand employees who want a focused system, not a multi-year enterprise programme with a large vendor team.
When should an Indian company build its own HRMS instead of subscribing?
Build your own HRMS when the subscription tool keeps forcing workarounds on your HR team, when your headcount makes per-employee fees a large yearly line, or when HR data must connect deeply to other systems you own. One signal alone is rarely enough; two or three together usually are.
Leave and shift rules are the usual breaking point. A manufacturer with rotating shifts, different weekly offs per plant, state-specific holidays and a union-negotiated leave policy often finds its HR executive rebuilding attendance in a spreadsheet every month despite paying for software. Another is structure: several legal entities, a franchise network, or a large field force with geo-tagged attendance.
- HR maintains a parallel spreadsheet because the product cannot express your policy
- Per-employee fees have grown faster than the value you get
- Biometric devices at your plants are not supported, so punches are pasted in by hand
- Approval chains depend on department, location and amount in ways the product cannot model
- Management wants HR data inside your ERP or reporting stack, not in a separate silo
- You need your own brand on the employee app, for example in a franchise group
The general reasoning is covered in off-the-shelf vs custom software.
When custom HRMS software development is the wrong choice
Do not build an HRMS if your policies are standard, your headcount is small, and the main thing you need is statutory payroll done right every month. A mature subscription product will serve you better and cheaper.
Statutory payroll is the part to be most careful with. PF, ESI, professional tax by state, TDS on salary and labour welfare fund rules change, and a vendor with a dedicated compliance team keeps up with them for every customer at once. With a custom HRMS you either maintain those rules yourself with your chartered accountant's input, or, more sensibly for many employers, keep payroll with an existing provider and let the custom HRMS feed it clean attendance and leave data.
There is also an ownership cost. Someone inside your business must own the system, approve changes and review it when policies change. If nobody can take that role, subscribe. We would rather tell you that on the first call than build something that goes stale.
Mapping the employee lifecycle in a custom HRMS
A custom HRMS should follow each employee from the day a position is approved to the day their full and final settlement is complete. Mapping those stages with your HR team is the first design task and shapes every screen after it.
For each stage, we note who starts it, which documents are collected, who approves, what the employee sees and what triggers the next stage. Probation length, confirmation reviews, notice periods and exit clearances are your policies; the HRMS just applies them and reminds people when something is due.
- Requisition: a manager requests a position and it is approved
- Offer and joining: offer letter generated, documents uploaded, employee code created
- Onboarding: assets issued, induction tasks, policy acknowledgements
- Probation and confirmation: review reminders, confirmation letter
- Movement: transfers, promotions, department and shift changes with history
- Performance: goals and review cycles, if you want them in phase 1
- Exit: resignation, notice tracking, clearance checklist, full and final inputs
Document-heavy stages can use AI to read uploaded certificates and IDs into the right fields; see OCR software development for how that works.
Designing a leave-policy engine for HRMS software development
A leave-policy engine stores every leave rule as data, so HR can change a policy next year without paying for new code. It is the heart of most custom HRMS projects in India, because leave policies are where companies differ most.
Each leave type (casual, sick, earned or privilege, maternity, paternity, bereavement, comp-off, optional holidays) gets its own settings: how it accrues (yearly, monthly, per days worked), the maximum balance, carry-forward and lapse rules, encashment, minimum and maximum days per request, whether half days are allowed, whether weekends and holidays inside a leave count (the “sandwich” rule), notice required, and who is eligible by grade, location or tenure.
Holiday calendars sit alongside, often one per state or plant, because regional holidays differ. Statutory minimums must be respected; for example, maternity benefit of up to 26 weeks is set by law, not by company policy. We implement the rules you give us; your HR head and labour law adviser confirm that the policy itself is compliant. The engine then calculates balances nightly and explains every figure, so an employee can see exactly why their balance reads what it does.
How does an HRMS integrate with biometric attendance devices?
A custom HRMS integrates with biometric devices in one of three ways: calling the device vendor's cloud API, using the vendor's SDK to pull punches from devices on your network, or importing the log files the device software already exports. Which one works depends on your device models, so we check them before quoting.
Once punches arrive, the HRMS matches each one to the employee's shift for that day, handles missing punches and duplicate taps, and marks the day present, absent, late, half day or on leave. Employees can raise a regularisation request from the self-service app when a punch is missing, and it follows the approval chain.
Field staff do not stand at a biometric device, so they usually mark attendance from the mobile app with location and a selfie, restricted to allowed areas. Face recognition terminals are another option at plants. We write the software side; buying, installing and servicing devices stays with you and your device supplier. Details are on our face recognition attendance and salesman tracking app pages.
Shifts, rosters and overtime for factories and plants
Plants need shift logic that office HR tools often lack: rotating shifts that change weekly, night shifts that cross midnight, split shifts, staggered weekly offs by line, and overtime that depends on how hours fall across a day and a week.
The HRMS keeps a roster per department or line, lets supervisors swap shifts with approval, and calculates attendance against the roster rather than a fixed office timing. A night shift punch at 6 am belongs to the previous day's shift, not the new day; getting that wrong is a classic source of “marked absent” complaints on the shop floor.
Overtime rules come from your policy and the applicable labour law. India's four labour codes were brought into effect from 21 November 2025, replacing 29 older central labour laws, and central and state rules under them have been rolling out since. Your HR and legal advisers decide how overtime and working hours apply to you; the HRMS calculates according to those rules and keeps them editable as rules settle. For contract workers who come through agencies, see contract labour management software.
Approval workflows: leave, regularisation, overtime and expenses
Approval workflows decide who must say yes to a request before it takes effect. In a custom HRMS they are modelled as chains that depend on the request type, the employee's department, location and grade, and sometimes the amount or number of days.
A two-day casual leave might need only the reporting manager. A ten-day earned leave during the peak season might need the department head too. Overtime above a threshold might need the plant head, and an expense claim above a limit might go to finance. Each chain supports delegation (when a manager is on leave), escalation (when a request sits too long) and approval from the phone, including a notification on WhatsApp for managers who never open the app.
Every decision is logged with who, when and any comment, which helps during audits and disputes. The same workflow engine can later handle requisitions, asset requests or travel. For claims specifically, our expense management software page goes deeper.
Employee self-service app: what employees actually open
An employee self-service app succeeds when it answers the questions employees would otherwise ask HR: What is my leave balance? Where is my payslip? Why was I marked absent? When is the next holiday? If the app answers those quickly, HR's inbox shrinks.
We build it in Flutter, so one codebase covers Android and iPhone, published under your company's own developer accounts. Plant workers often have entry-level Android phones and limited data, so the app is kept light, works on slow connections and can run in Hindi or a regional language whose translations you provide or approve.
Typical screens: attendance calendar with punches, leave balance and apply, regularisation requests, payslips and tax documents as PDFs, holiday list per location, company policies, and manager approvals for team leads. Google Play charges a one-time US$25 registration fee and Apple's developer programme costs US$99 a year; both accounts should be in your company's name. The self-service app phase starts at ₹40,000; more on our app work is on Android and iOS app development.
Payroll in HRMS software development: build it, connect it, or keep it outsourced?
For most employers commissioning HRMS software development, the safest route is to connect the custom HRMS to an existing payroll provider or consultant, sending clean attendance, leave and overtime data each month, rather than rebuild statutory payroll from scratch.
Payroll in India involves PF and ESI contributions and returns, professional tax that varies by state, TDS on salaries with employees' investment declarations, bonus, gratuity and labour welfare fund rules, and more changes are possible as rules under the new labour codes settle. Payroll providers maintain those calculations as their core job.
Building payroll in-house makes sense when your structure is unusual (piece rates, incentives tied to production, several entities with shared staff) and you have a chartered accountant who will specify and review the rules. In that case we build the calculation engine to their specification, run parallel payrolls against the old method for at least a couple of months, and change nothing until the numbers match. Factory-specific payroll is discussed on payroll software for factories.
HRMS software development cost in India, phase by phase
HRMS software development with BtechWaleTech is priced per phase: phase 1 starts at ₹60,000, the self-service app at ₹40,000, and automation or AI add-ons at ₹40,000. Each phase is quoted separately, so you commit to one at a time and can stop once the value is clear.
Cost drivers are specific to HR work: the number of legal entities and locations, how many leave types and exceptions the policy has, shift complexity, the variety of biometric devices, the depth of approval chains, integrations with ERP, accounting or payroll, and migration of historical leave balances and employee records. Headcount affects hosting more than development.
Compare the total with what you pay today: the subscription's per-employee fee multiplied by headcount and months, plus the HR hours spent on workarounds. Over three to five years the comparison often favours building for larger or more complex employers, and favours subscribing for smaller, standard ones. For wider budget context, see custom software development cost in India and the ERP development cost guide.
How long does HRMS software development take?
Phase 1 of a custom HRMS usually goes live in 6–12 weeks; the self-service app follows in another 6–10 weeks, and automation add-ons take 2–4 weeks each. The timeline depends more on policy decisions than on coding.
The first two weeks are spent writing down rules: leave types and their settings, shift patterns, approval chains and the lifecycle stages. Clickable screens follow, then build with a test version every week. Before go-live, HR runs a parallel month: the new HRMS calculates attendance and leave alongside the old method, and every difference is explained or fixed.
Projects slow down when policies are still being negotiated, when device vendors are slow to share SDK details, or when historical data arrives in pieces. Settling policy questions before the build starts is the single most useful thing an HR head can do for the schedule.
Employee data security and the DPDP Act
An HRMS holds some of the most sensitive data in a business: salaries, bank details, identity documents, health-related leave, family members and biometric-derived attendance. It is personal data under the Digital Personal Data Protection Act, 2023, whose rules MeitY notified in November 2025 with a phased timeline running to May 2027.
Controls we build in: role-based access down to field level (a line manager sees leave but not salary), encryption in transit and at rest, audit logs of every view and change to sensitive records, secure document storage, retention and deletion rules for former employees, and single sign-on with your Google Workspace or Microsoft 365 accounts where you use them.
Biometric templates usually stay on the devices or the vendor's system; the HRMS stores punch times, not fingerprints. Hosting sits in your own cloud account, so the data never lives with us. We implement the controls; your privacy notice, consent approach and retention periods should be reviewed by your legal adviser.
Tech stack and integrations for a custom HRMS
Our usual stack is a Node.js or Python back end, PostgreSQL for employee and attendance data, a React-based web app for HR and managers, Flutter for the self-service app, and hosting on AWS in your account. Background jobs run nightly accruals, pull biometric punches and send reminders.
Integrations are where custom HRMS earns its keep. Common ones are pushing monthly attendance and leave to a payroll provider, sending employee cost centres to your ERP or accounting software, syncing new joiners into email and access systems, and feeding headcount data to a management dashboard. Each depends on the other system offering an API or a reliable import format, which we confirm during scoping.
If your ERP already has an HR module you have outgrown, we can build around it rather than replace it. Our pages on ERP software development and ERPNext development cover that side.
Moving from spreadsheets or an existing HR tool
Migration into a new HRMS should bring over current employee records, reporting lines, opening leave balances and the recent attendance history HR needs for disputes, then prove the numbers match before the old system is switched off.
Opening leave balances are the riskiest item, because every employee will check theirs on day one. We import them, produce a reconciliation sheet per employee, and HR signs off before go-live. Documents such as offer letters and ID proofs are uploaded in bulk against employee codes.
If today's HR runs on Excel, our Excel to software page describes how we turn spreadsheets into structured data without losing the logic hidden in them. If you are moving from a subscription product, request a full export before your contract ends.
Worked example: a hypothetical 350-person manufacturer in Ludhiana
Take a hypothetical bicycle-parts manufacturer in Ludhiana with two plants, 350 employees, a head office and a sales team of 25 travelling across north India. This is a scenario to show how phasing works, not a client project.
The pain points: rotating shifts differ between the plants, the subscription HR tool does not support the plants' biometric devices so punches are exported and pasted in weekly, a union-agreed leave policy needs a spreadsheet to calculate, and sales attendance is taken on trust. Payroll is run by an outside consultant and works well.
Phase 1 would include employee records, the leave-policy engine with both plants' holiday calendars, biometric sync through the device vendor's software, rotating shift rosters with night-shift handling, leave and regularisation approvals, and a monthly attendance export in the format the payroll consultant already uses. That is HRMS software development starting at ₹60,000. Phase 2 would add the self-service app with geo-tagged attendance for the sales team. Payroll would stay with the consultant.