Loading page
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
HRMagix is an HRMS in the strict sense: a single authoritative record of every employee, from which attendance, payroll, performance and documents all draw. Nothing is re-keyed, because there is only one place the data lives.
Human Resource Management System at a glance
Most companies do not buy an HRMS system because they want one. They buy one because the fourth spreadsheet has stopped agreeing with the third, and nobody can say which is right.
The fragmentation is rarely dramatic. It starts with a biometric machine that exports a CSV, a leave tracker somebody built in Excel, a payroll package that lives on one finance laptop, and appraisal forms circulated as PDFs once a year. Each holds up on its own. Together they mean that the answer to a question as simple as "how many days was this person actually present in March" depends on who you ask.
An HRMS is the decision to stop asking. One record per employee, one place it is edited, and every downstream workflow reading from it rather than from its own private copy.
Several disconnected tools, a monthly headcount report built by hand, and a leadership team asking questions the data cannot answer.
The moments that usually start the search
The current system's renewal date is approaching.
Leadership asks for a number, headcount, attrition, cost, and producing it takes days.
A new entity or acquisition doubles the records that have to be reconciled.
Grouped by what it is for rather than by which screen it appears on. If a field you rely on is missing from this list, it is worth raising before a migration rather than after one.
“One record, edited in one place, read by everything else.”
HRMagix is an HRMS in the strict sense: a single authoritative record of every employee, from which attendance, payroll, performance and documents all draw. Nothing is re-keyed, because there is only one place the data lives.
An employee in HRMagix is not a row in a table with a name and a salary. It is a versioned record: personal and statutory identifiers, employment history within the company, reporting line, department and location, the compensation structure in force on any given date, the leave balances accrued against it, and the documents that evidence all of it.
The versioning matters more than it sounds. When a payroll run for March is questioned in September, the platform can answer with the structure that was in force in March, not the one in force today. That single property is the difference between a system you can audit and a system you have to defend.
Plenty of tools claim integration and deliver an overnight sync. The distinction that matters operationally is whether a correction propagates. If an approved leave application is backdated on the 28th, does the loss-of-pay register for that month change before the cutoff, or does somebody have to remember to reconcile it?
In HRMagix the modules are not separate products joined by an API. Attendance, leave and payroll read the same attendance ledger, so a backdated approval is not a message sent between systems, it is the same number, seen from a different page. There is nothing to reconcile because there was never a second copy.
Indian companies rarely fit a default. A manufacturing business with three plants may run different shift patterns, different overtime rules and different leave quotas at each, and still file one set of returns. A services firm may have the same policy everywhere and different approval chains by grade.
HRMagix handles this with a policy engine rather than customisation: leave categories, accrual rules, shift definitions, grace periods, approval hierarchies, salary components and statutory applicability are all settings, configured per entity, location or grade. There is no implementation project that has to be repeated every time a rule changes.
The work of adopting HRMS software is not the software. It is deciding what your data currently says, because the migration is the first time anyone has looked at all of it at once.
In practice the sequence is the same everywhere. Employee master data comes across first, because everything else hangs off it, names, identifiers, dates of joining, departments, reporting lines, salary structures. Then the balances that have a history: leave accrued and taken so far this year, and where relevant the year-to-date payroll figures that Form 16 will eventually have to reconcile against.
Two things reliably surface during that exercise. Duplicate records for the same person, usually created when someone was rehired or moved between entities. And salary structures that were described one way in the offer letter and calculated another way in practice. Neither is caused by the migration; the migration is simply the first process that compares them.
The safest cutover for payroll is a parallel run: process one month in both the outgoing system and the new one, and compare the results head by head before switching over.
That comparison is worth doing properly rather than as a total. A total that matches to the rupee can still conceal two offsetting errors, and the differences that matter are usually in the same few places, a rounding convention on PF, an allowance treated as part of the gross in one system and outside it in the other, an employee whose ESI eligibility changed mid-year.
Once the two agree line by line for one month, the historical figures can be carried in with confidence, because the thing that had to be trusted was the calculation rather than the import.
A single record read by twelve workflows raises an obvious question: who is allowed to read which part of it. The answer in an HR platform for companies of any size has to be structural rather than conventional.
Access is granted by role against the record, not by trust. A reporting manager sees their team's attendance, leave and goals. Finance roles see salary components and the payroll run. HR administrators see the whole record. An employee sees themselves. Nobody sees a part of the system because they have been there a long time.
Underneath that, the record keeps its own history. Every change to a salary component, a reporting line, a leave balance or a document carries who made it and when. That is what makes a figure easy to defend six months later, when the question is not what the number is but how it came to be that number.
These are the fields every other module in the platform reads. They are entered once, at onboarding, and versioned from then on.
PAN, Aadhaar, UAN, ESIC IP number, bank account and IFSC, date of birth, gender, emergency contact.
Drives EPF, ESI and TDS applicability
Date of joining, employment type, probation and confirmation dates, grade, designation, reporting manager, department, work location and legal entity.
Drives approval routing and gratuity eligibility
Basic, HRA, allowances, employer contributions and deductions, effective-dated so a mid-year revision does not rewrite history.
Drives every payroll calculation
Shift pattern, weekly off, holiday calendar, leave scheme, grace period and overtime eligibility.
Drives attendance and loss of pay
Offer and appointment letters, joining forms, statutory declarations, policy acknowledgements, certificates and their expiry dates.
Drives reminders and audit trails
Nobody adopts an HR management system on a quiet week. There is almost always a specific event that makes the spreadsheets unworkable.
PF becomes mandatory at twenty employees and ESI at ten in most states, and the informal arrangements that worked for a handful of people become statutory filings with dates attached.
Contributions are derived from the salary structure on the record rather than maintained separately, and the monthly returns are produced from the run that generated them. The compliance obligation arrives whether or not a system is ready for it.
A second office brings a different professional tax regime, a different holiday calendar and a manager who has never met most of the people approving their team's leave.
Location and entity are attributes of the record, so policies vary by where somebody works without running a second installation. Approvals route by the current reporting line rather than by proximity.
An inspection, a due diligence exercise or an investor's people-data request asks for evidence rather than assurances, across a period nobody documented at the time.
Attendance, leave, payroll and document acknowledgement all sit in one record with their own history, so the period can be reconstructed as it stood rather than as it is remembered.
In most companies under a hundred people, HR is part of a finance or operations role, and the administrative load is the part that crowds out the rest of the job.
The recurring work, payslips, balances, letters, reminders, approvals, either automates or moves to self-service. What is left is the part that needed a person.
Where every employee starts the day.
The records and paperwork that sit behind every employee.
Attendance, leave and the rules that govern them.
Goals, reviews and growth plans.
The conversations and recognition that keep teams connected.
The monthly run, from salary structure to payslip.
Company communication and personal settings.
The questions that come up when a company is deciding whether to consolidate onto one record.
Payroll software calculates salaries. An HRMS holds the employee record that payroll needs in order to calculate them correctly, attendance, approved leave, the compensation structure in force, statutory identifiers and the documents behind them. HRMagix is both: the record and the run, which is why a backdated leave approval changes the loss-of-pay register without anyone re-entering anything.
Most Indian organisations complete setup within two to three days. Employee master data, historical leave balances, previous salary structures and department hierarchies come in through structured Excel templates, and an onboarding specialist works through policy validation and a dry-run payroll before the first live cutoff.
Yes. The Starter plan covers attendance, leaves, the employee directory and documents; payroll, performance, OKRs, recognition and analytics arrive with Growth. Because every module reads the same record, switching one on later is a setting rather than a migration.
Employee master data first, names, statutory identifiers, dates of joining, departments, reporting lines and salary structures, because everything else references it. Then leave balances accrued and taken in the current leave year, and year-to-date payroll figures if you are moving mid-financial-year, since Form 16 has to reconcile across the whole year.
For a mid-year switch, yes. Process one month in both and compare head by head rather than in total, because two offsetting errors produce a matching total. Differences usually cluster around rounding on PF, allowances treated differently in the gross, and mid-year ESI eligibility changes.
Only roles with payroll access, and the employee themselves. A reporting manager sees their team's attendance, leave and goals but not their salary components. Access is a property of the role rather than of seniority, and every view of a restricted field is recorded.
No. It produces the payroll outputs accounting needs, the cost by head, the statutory liabilities, the bank transfer file, and the accounting system remains where the ledger lives. The overlap is the handover, not the function.
Policies carry effective dates rather than being edited in place, so a change applies from the date it takes effect and the earlier periods stay calculated under the rule that governed them. Recomputing history to match a new rule is almost always the wrong answer, and is what makes past payslips indefensible.
Looking for a custom walkthrough or have specific statutory policy requirements? Connect with our product specialists in Pune for a 1-on-1 consultation.
A walkthrough against your own policies, with a dry-run before the first live cutoff.
14-day free trial · Full access to all 12 modules · Zero implementation fee · Cancel anytime