All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com

Onboarding is the visible end of employee lifecycle management, but the same record carries confirmation, transfer, promotion and exit. HRMagix treats all five as stages of one process rather than five unrelated pieces of paperwork.
Onboarding & Lifecycle at a glance
A new joiner's first day is usually spent doing data entry. They fill in a joining form with information the company already has from their offer, photocopy a PAN card, sign a policy pack they will not read, and wait for a laptop that was requested that morning.
None of this is anybody's fault. It happens because the offer, the documents, the IT request and the payroll setup are four separate processes owned by four different people, all triggered by the same event and none of them aware of each other.
From before day one to after the last one. The middle stages are the ones companies usually have no process for, which is why they are listed here alongside the obvious two.
Onboarding is the visible end of employee lifecycle management, but the same record carries confirmation, transfer, promotion and exit. HRMagix treats all five as stages of one process rather than five unrelated pieces of paperwork.
The most valuable thing an onboarding system does is move work earlier. A candidate who has accepted an offer gets access to a self-service pre-boarding portal, where PAN, Aadhaar, bank details, previous employment documents and statutory declarations are uploaded before they arrive.
Appointment letters are generated from the offer data with digital signature capability, so the paperwork is concluded rather than carried into the first morning. IT hardware and workspace assets are provisioned from a checklist that starts when the offer is accepted, not when the person walks in.
Because the pre-boarding data lands directly on the employee record, day one produces no re-entry. Statutory identifiers are already present, so EPF and ESI applicability is already determined. The compensation structure is already effective-dated from the joining date, so the first payroll run needs no special handling. The leave scheme is already attached, so accrual starts on the right date.
The department welcome workflow, introductions, systems access, first-week goals, runs on top of a record that is already complete, rather than being the thing that completes it.
Confirmation after probation, an internal transfer between locations, a promotion, a change of reporting line: each is a lifecycle event with statutory and payroll consequences, and each is usually handled by email.
In HRMagix these are effective-dated changes on the same record, which means the consequence is automatic. A transfer to a different state changes Professional Tax applicability. A confirmation date reached without action is flagged to the reporting manager. A promotion reaches the next payroll run without a second entry.
An exit generates more obligations than a joining: notice-period computation, asset recovery, clearance across departments, full-and-final settlement including gratuity where the five-year threshold has been met, and documents the person may need for years afterwards.
Handling this as a checklist against the same record means the settlement is computed from the same attendance and leave ledger everything else used, and the record remains available afterwards rather than being deleted along with the login.
Probation is a defined period with a decision at the end of it, and the decision is the part that most often goes missing. The period lapses, nobody confirms anything, and the employee is left in an ambiguous status that becomes awkward precisely when it matters, at an increment, or at an exit.
The mechanism that fixes this is unglamorous: the probation end date is a field on the employee record, and it raises the confirmation decision before it arrives rather than after. The outcome, confirmation, extension with reasons, or separation, is recorded against the record with its date, and any change it triggers, such as eligibility for earned leave, follows from the same event.
It is worth being clear that the platform holds the date and the outcome. What the probation period is, how performance is assessed during it, and what an extension requires are the employer's decisions, written into their own policy.
A promotion, a transfer between locations and a move between legal entities are all treated in most companies as administrative footnotes, and all three have the same shape as a joining: a new reporting line, a new set of approvals, sometimes a new payroll treatment, and a new set of things the person needs access to.
Handling them as changes to the existing record rather than as new records is what preserves continuity of service, which is not a technicality, because gratuity eligibility and leave accrual both depend on it. An employee who moves between entities and is recreated has, on paper, started again.
The same record therefore carries the history: the grades held, the managers reported to, the locations worked at, and the dates each changed. Tenure is then a fact rather than a reconstruction.
The experience of a good first week is usually described in cultural terms, but what employee onboarding software actually has to solve underneath it is documentary. A new joiner has to provide statutory identifiers, bank details and proof documents; the employer has to issue an appointment letter, communicate its policies and record that they were received.
Done over email, this generates a fortnight of correspondence and leaves the evidence scattered across three inboxes. Done through the portal before day one, the employee completes their own record, the documents attach to it as they are supplied, and the policy acknowledgements are captured against the versions actually issued.
What that buys is not only speed. It means the first payroll run has the identifiers it needs, and that the company can later show what a specific person was told on the day they joined.
Five stages, one record. Each stage inherits everything the previous one established.
Self-service upload of PAN, Aadhaar, bank and previous employment documents. Appointment letter generated and signed digitally. Asset checklist opens.
Record activates with statutory identifiers, compensation structure, leave scheme and shift policy already attached. Welcome workflow runs on a complete record.
Probation end date is flagged to the reporting manager ahead of time; confirmation is an effective-dated change with its own consequences.
Transfers, promotions and reporting-line changes are dated rather than overwritten, so payroll, approvals and statutory applicability follow automatically.
Notice period, clearance, asset recovery and full-and-final settlement including gratuity where eligible, computed from the same ledger, with documents retained.
The practical questions about joining, confirmation and exit that a policy document rarely answers.
They log in to a pre-boarding portal and upload PAN, Aadhaar, bank details, previous employment documents and statutory declarations, and sign their appointment letter digitally. Because that data lands on the employee record directly, their first day involves no re-entry and their first payroll run needs no special handling.
Where the employee has completed five years of continuous service, the settlement includes gratuity computed on the Payment of Gratuity Act formula of fifteen days of last drawn basic salary per completed year. Provisioning runs before that point so the liability is visible rather than sudden.
The record is retained rather than deleted with the login, which is what makes it possible to issue a document or answer a statutory question about a former employee months later.
The probation end date sits on the employee record and raises the confirmation decision before it lapses. The outcome, confirmed, extended, or separated, is recorded with its date, and anything that follows from it, such as eligibility for earned leave, takes effect from that event. The length of probation and the criteria are the employer's policy, not ours.
It is a change to the existing record rather than a new one, which is what preserves continuity of service for gratuity and leave accrual. The record keeps the grades held, the managers reported to and the locations worked at, each with the date it changed.
Yes, and it is the main reason pre-boarding exists. The joiner completes their own details, uploads statutory and proof documents, and acknowledges the policies issued to them, so day one is not spent on data entry and the first payroll run has the identifiers it needs.
Yes. Assets issued and access granted are recorded against the employee when they are given, so the clearance list at exit is generated from what is known rather than assembled from memory. Each item is cleared by whoever is responsible for it, through the same approval routing as everything else.
The configuration is the checklist itself, which documents are collected, which policies are issued, who clears what, and it is defined once and reused. The work is deciding the sequence, not building it, which is why companies usually start from their existing joining formalities rather than designing a new process.
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