Employee management software built around one governed record.

Employee management software keeps one governed record for every employee and runs the routine work around it: self-service edits, document storage, role-based access and an audit trail of changes. It replaces the scattered spreadsheets and shared drives where employee data usually lives, so there is a single, trustworthy source for each person instead of several copies that drift apart.

LekhaHR groups the record into four tabs. About holds name, legal name, date of birth, contact and emergency contact. Job holds title, department, work location and state, the primary manager, typed secondary relationships, the HR Partner, date of joining, employment type and status. Documents holds uploaded files. Finances holds the bank account and IFSC, PAN stored masked, and CTC shown for display only. Which fields count as sensitive comes from tenant config, not from hardcoded client logic.

Yes, with a boundary. Safe fields save directly when the employee edits them. Sensitive fields such as bank, PAN, legal name and date of birth do not change the record on their own; they raise a change-request that routes to an approver, and the stored value only changes once HR approves it. An open request on a field blocks a second one, and no one can approve their own request.

Only roles that hold the people.salary.view permission. Field-level access is a separate permission from seeing the profile, so a manager can open a team member's record but the salary, CTC and bank block is omitted from the server response entirely. It is not greyed out or locked on screen; the data is never sent to the browser at all.

Yes. Every write to a record lands in the audit log with the before value, the after value and the actor who made the change. There is a per-employee change timeline for anyone with people.audit.view, and even bulk operations are audited one row per employee. Report exports are logged too, recording who exported which report containing personal data and when.

Yes. Each profile has a Documents tab where you upload files such as a PAN card, an appointment letter or a certificate. A document on the record can also satisfy a pending leave or regularization requirement in another module by its attachment id, so the same proof is not uploaded twice, and an oversize upload returns a clean error rather than failing silently.

PAN is stored masked with its raw value encrypted at rest, and a consent notice is shown at collection, following the DPDP posture. Bank IFSC and account fields are validated on save. Work location carries its own state so profession tax and shops-and-establishment rules follow the right state per employee. Specific statutory figures are not quoted on this page; those live in dated fixtures rather than in marketing copy.

The record shows the lifecycle state today, whether onboarding, probation, confirmed, notice or exited, and the directory filters by it. The onboarding and exit workflows themselves, from offer and preboarding through resignation, clearance and full-and-final, arrive with the Onboarding & Exits module, which is behind the M5 release gate. We show the state; we do not claim to run that workflow yet.

We will not rank ourselves, and we have no customer logos or testimonials to point at yet, so any "we are number one" claim would be invented. The honest answer is a fit answer: LekhaHR suits an Indian team that wants one governed record with server-enforced access and a real audit trail, and it is the wrong choice if you need released payroll, an onboarding workflow or employee monitoring today.

When you need a released payroll run, an onboarding or exit workflow, performance reviews or workforce analytics right now, since those are gated modules we deliberately do not claim. Also when you want employee monitoring or productivity tracking, or biometric kiosk hardware, since LekhaHR reads location only at a punch and runs no continuous tracking.

There is no free-forever plan. LekhaHR offers a 14-day trial, then per-active-employee pricing with no base platform fee and no minimum headcount. The published rates are on the pricing page and GST is charged separately, so a small team pays only for the people it actually has on the record.