01 · Platform

One record, every entity.

A single employee master across all your companies and branches, with a schema you can extend, an audit trail on everything sensitive, and a workflow engine that automates the processes around it.

Per tenant
5entities
State-aware
36jurisdictions
Custom fields
∞
Field-level audit
100%

Employee master

The single source of truth.

Everything downstream — attendance, payroll, statutory applicability, settlement — reads from here. Change it once and it propagates with an effective date.

HRIS-1

Employee profile

Personal, employment, payroll and contact data, with every employee linked to a company, a primary branch, a department, a grade and a reporting manager. That mapping is what drives professional tax, labour welfare fund and payroll-run membership.
HRIS-2

Custom fields

Define your own fields with types and validation. They appear in profiles, reports and workflow conditions immediately — no engineering ticket, no schema migration.
HRIS-3

Org structure & chart

Department and location hierarchies, with reporting relationships generating the org chart automatically. Changing a manager rewires every approval chain that depends on it.
HRIS-4

Document management

Employee documents with expiry tracking and role-based access. Expiring documents raise tasks rather than sitting silently until someone notices.
HRIS-5

Field-level audit trail

Change history on everything sensitive — role, salary, bank details, statutory identifiers — recording who, when, from what, to what, and through which surface.

Multi-company

The second office should not be a migration.

Most platforms in this segment model one company and bolt on the rest. Lekha treats multiple legal entities as the normal case, because a group of 400 people across three entities is our median customer.

MC-1

Company master

Each legal entity carries its own PAN, TAN, PF establishment code, ESIC code, state-wise PT registrations and LWF registrations. One can be flagged default so a single-entity customer never sees the complexity.
MC-2

Branch & location master

Branches carry a state or UT code, which derives PT and LWF applicability from the statutory tables — overridable by an admin when a law changes before we ship the update.
MC-3

Employee mapping

Every employee belongs to exactly one company and one primary branch. That single relationship drives statutory applicability, payroll membership and reporting scope.
MC-4

Company-level runs

A payroll run is always scoped to one company and one period. Run each entity separately, produce company-wise bank files and statutory returns, and consolidate for reporting.

Permissions follow entities

Roles are scoped per company, and compensation carries its own visibility scope on top. One entity’s HR team can be fully blind to another’s payroll — and every unmasked view of someone else’s salary is logged as an access event, not merely permitted.

Workflow engine

No-code, and load-bearing.

The workflow builder is not a notifications add-on. It is the engine that runs onboarding, exit, clearance, confirmation and every approval in the product — which means it has to be good enough for us to build on.

  • Visual builder with triggers, conditional branching, forms and parallel approval paths
  • Actions that write back to the employee record, raise tasks or call a webhook
  • Templates per company, department or employment type
  • Full execution logs — what fired, when, on whose action, and what it changed
  • SLA tracking per step, with escalation when a step goes overdue

Onboarding

Document collection, statutory declarations, provisioning fan-out and induction, running as one instance per joiner.

Exit & clearance

Manager, IT, admin, finance and HR clearance in parallel, gating settlement release.

Confirmation

Raised before probation ends, with confirm, extend, terminate or convert as outcomes.

Salary change

Approval chain with the before-and-after break-up, feeding arrears automatically when back-dated.

Self-service

Most people should never need to ask HR.

Employee

What they get

Profile, attendance, leave balance and applications, payslips and year-to-date figures, tax worksheet and declarations, reimbursement claims, loan balances, and every document ever issued to them.

Manager

What they get

Team attendance and regularisation, leave approvals with coverage visibility, confirmation and exit sign-offs, and compensation visibility only where you enable it.

Admin

What they get

Configuration with effective dates, the run console, the compliance calendar, the audit pack, and role management scoped per entity.

NextLifecycle — onboarding through exit
Continue →