Solution · Multi-entity

One product across multiple legal entities, GSTINs, and PANs.

Run a holdco with three operating companies on a single instance: per-company employee data isolation, per-entity payroll, separate PT/PF registrations, group-level reporting. Built for Indian groups consolidating HR onto one platform.

What's included

The modules that matter for multi-entity groups & holdcos.

Same single SKU as everywhere else on pPULSE. These are the modules a typical multi-entity team uses every week.

Per-company isolation

Employee, attendance, leave, and payroll data scoped to each Company; HR users only see their entity.

Multi-entity payroll

Each entity runs its own payroll with its own PF/ESIC/PT registrations and bank file.

Group reporting

Holdco roll-up dashboards: total headcount, gender ratio, attrition, payroll spend across entities.

Inter-company transfers

Move an employee from Entity A to Entity B with full F&F at A and onboarding at B; F&F amount reconciled.

SAML SSO

Single sign-on across all entities; group IT manages identities once.

Approval governance

3-tier payroll approval (HR → Finance → CEO) configurable per entity.

Snapshot
Multi-entity groups & holdcos on pPULSE
India HR
Sweet spot
2-15 group entities, 500-15,000 total employees
Isolation model
Per-company row-level isolation, role-scoped access
Compliance
Separate PF, ESIC, PT, TDS, GST per entity
Implementation
4-8 weeks for the first 3 entities; 1 week per additional
Pricing
From ₹85/pp/mo, billed per entity or consolidated
FAQ

Common questions for multi-entity teams.

Can users in Entity A see data from Entity B?
Only group-admin roles can see across entities. Standard HR / payroll users in Entity A see only Entity A's data. The default queryset manager filters by company FK; cross-entity access requires explicit role grant.
How does an employee transfer between entities work?
Initiate a transfer from Entity A's profile. pPULSE generates an F&F at A (final salary, gratuity if applicable, leave encashment) and creates the new employment record at B with the chosen joining date. Salary continuity, asset reassignment, and email migration are tracked in the same workflow.
Is each entity's PF / ESIC registration handled separately?
Yes. Each entity has its own PF code, ESIC sub-code, PT registration, and TAN. Payroll runs are entity-scoped — the bank file, PF challan, and ECR file output per entity. Group finance sees the consolidated view if granted access.
What about consolidated 26AS / TDS reconciliation?
TDS is filed per entity (each has its own TAN). pPULSE outputs Form 24Q quarterly per entity. Group reconciliation is a reporting view, not a regulatory filing.

Ready to get started?

Start a free 14 day trial in minutes, or chat with us about a custom rollout for your team.

See what you'll pay

Clear per person pricing. No surprise setup or onboarding fees.

Pricing details

Book a demo

A 30 minute walkthrough, tailored to how your team actually works.

Schedule a demo