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
Employee management is unglamorous until it fails: a promotion that never reached payroll, a certificate that expired unnoticed, a policy nobody can prove was acknowledged. HRMagix makes each of those a scheduled event rather than a discovery.
Employee Management at a glance
Ask an HR team what takes their time and very few will say strategy. They will describe chasing: a bank detail that was never updated, a driving licence that expired three weeks ago, an appointment letter somebody needs for a visa application by Friday.
None of these are difficult. They are simply invisible until the moment they are urgent. The problem employee management software actually solves is not storage, a shared drive stores things perfectly well. It is knowing, without being told, what has changed and what is about to.
Two halves of the same module: the directory colleagues use daily, and the document store almost nobody opens until it matters urgently.
Employee management is unglamorous until it fails: a promotion that never reached payroll, a certificate that expired unnoticed, a policy nobody can prove was acknowledged. HRMagix makes each of those a scheduled event rather than a discovery.
Every change to an employee record in HRMagix is dated rather than overwritten. A grade revision in July does not erase the grade that applied in June; it succeeds it. This is what makes it possible to answer questions about the past truthfully, which structure applied when a particular payroll ran, who the approving manager was at the time a leave was sanctioned, when a policy was acknowledged.
It also means promotions, transfers and confirmations do not need to be communicated to payroll separately. They are the same record, so they arrive automatically at the next cutoff.
A personnel file is a mixture of documents that never change and documents that stop being valid. Offer and appointment letters are permanent. Visas, driving licences, professional certifications and contractor agreements are not.
HRMagix holds both kinds in an encrypted vault with role-based access, and treats expiry as a property of the document rather than something a person has to remember. Alerts fire ahead of the date, to the employee and to whoever is accountable, which turns an expired certificate from an incident into an errand.
Handbook acknowledgements, non-disclosure agreements and compliance policies all share the same weakness: circulating them is easy, and proving each person received and accepted them is not.
Acknowledgement is tracked per employee per policy version in HRMagix, so a change to a policy re-opens the acknowledgement rather than automatically applying to people who accepted an earlier text. The workplace policy library shipped with the platform is designed to be issued this way.
In most companies the organisation chart is a slide. Someone maintains it, it is accurate on the day it is made, and it drifts from that afternoon onward, because a reporting line changed in a conversation and the slide was not in the room.
In an employee management system the reporting line is a field on the record, so the chart is drawn from it rather than maintained alongside it. Changing a manager changes the chart, and it also changes who approves that person's leave, who sees their attendance regularisation, and whose queue their appraisal lands in.
That is the practical argument for keeping structure in the record instead of a document: an org chart nobody updates is merely out of date, but an approval routing nobody updates sends requests to someone who left.
An employee directory is useful precisely because it is open, names, roles, departments, work contact details, the things colleagues look up a dozen times a week. An employee record is useful precisely because it is not: it holds bank details, statutory identifiers, salary, and documents that were handed over in confidence.
The two live in the same HR management system and are separated by role rather than by keeping a second, quieter spreadsheet. A colleague sees the directory. A reporting manager sees their team's attendance, leave and goals. Payroll roles see salary components. HR administrators see the full record, and the record notes that they looked.
Every widening of access is therefore a deliberate change to a role rather than an informal favour, which is the difference between a permission model and a habit.
Records go stale in predictable places: a new address after a move, a changed bank account, a phone number, an emergency contact recorded on the day of joining and never revisited.
Almost all of these are things the employee knows and HR does not. The self-service portal lets them correct their own details, and routes anything with a downstream consequence, a bank account change ahead of a payroll run, for instance, for confirmation before it takes effect.
The result is that accuracy stops depending on an annual data-cleaning exercise. The people with the correct information are the ones entering it, and the audit trail records what changed, when, and at whose request.
Each of these is an alert rather than a report somebody has to remember to run.
Visas, driving licences, professional certificates and agreements, with lead time before the date.
Confirmation dates flagged to the reporting manager ahead of time, not after.
Per employee, per policy version, re-opened when the policy text changes.
Missing PAN, UAN, ESIC IP number or bank details flagged before they block a payroll run.
Hardware and workspace assets tracked against the person they were issued to.
Not on the day it is created, on the days something has to be proved, produced or reconstructed at short notice.
An inspector asks for appointment letters, wage records and proof of policy communication for a sample of employees, and gives you the rest of the day.
Documents sit on the records they belong to rather than in a shared drive organised by whoever filed them last. The acknowledgement trail shows which version of a policy each person received and when they confirmed it.
A key person leaves and their handover is partly in their head and partly in files nobody else can find.
The record already holds their assets, access, documents and reporting lines, so the exit checklist is generated from what is known rather than reconstructed from memory. Clearance moves through the same approval chain as everything else.
A fixed-term contract, a work authorisation or a mandatory certification expires, and the first anyone hears of it is the day it stops being valid.
Documents carry expiry dates, and the reminder fires against the date rather than against someone remembering. The risk is procedural, so the control is procedural.
A second entity is registered, and half the workforce now sits under a different PF code, a different professional tax registration and a different payroll run.
Entity is an attribute of the record, so people move between entities without being recreated, and their history travels with them. Statutory obligations stay attached to the entity that owes them.
The records and paperwork that sit behind every employee.
Mostly asked by HR teams who have been burned once by a document nobody could find.
Visibility is set by role rather than by folder. An employee sees their own file, a reporting manager sees what their role permits, and HR sees what its role permits. The vault is encrypted, and access is governed by the same role-based permissions used across the platform.
Acknowledgement is tracked against a policy version. Publishing a new version re-opens acknowledgement for everyone it applies to, rather than allowing an earlier acceptance to stand in for the new text.
No. Grade, designation and compensation changes are effective-dated on the employee record, and the payroll run for the relevant month reads the structure that was in force. There is no second entry to make or forget.
The directory is the open part, name, role, department, work contact details, that colleagues are meant to look up. The record is everything else: statutory identifiers, bank details, salary components, documents and history. They are the same system separated by role permissions, not two databases.
Yes, through the employee self service portal. Changes with a downstream consequence, a bank account before a payroll run, for example, are routed for confirmation rather than applied automatically. Everything else takes effect immediately and is recorded in the audit trail.
No. The reporting line is a field on the employee record, so the chart is drawn from it. Changing a manager also changes approval routing, which is the part that matters more than the diagram.
Through a bulk import of the fields you already hold, with validation on the ones that have to be well formed, identifiers, dates of joining, salary components. Records that fail validation are reported individually rather than skipped, so nobody is missing from the first payroll run.
It is retained rather than deleted. Statutory records have to survive the employment that produced them, gratuity, Form 16 reissues and inspections all reach backwards, so an exited record moves out of active views but stays queryable.
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