One platform. Entities that stay properly separate.
A group is not one company with branches. Each legal entity has its own registrations, its own fiscal year, its own statutory obligations — and payroll that must not blend across them. Klok models that separation rather than papering over it.
Company, Entity, Plant
A real hierarchy, not a single flat tenant with a location field. Statutory identity attaches to the legal entity, where it belongs.
Country Profiles
The country profile drives the statutory rules and the fiscal year, so an entity in a different country is not forced into Indian defaults.
Policy Layering
Defaults, then company, then grade, then shift. A policy set at one level is replaced cleanly at the next, so exceptions do not require duplicating an entire ruleset.
Statutory Setups Per Entity
PF, ESI, PT and LWF registrations sit at the entity and workplace level, dated by financial year — because a rate that changed in April must not rewrite last year.
A group is not one company with branches
Treat it as one and the compliance breaks immediately. Each legal entity has its own registrations, its own PF and ESI numbers, its own fiscal year in some jurisdictions, and its own filings. Employees belong to an entity, not to the group.
Klok models company, then legal entity, then plant or workplace. Statutory obligations attach at the entity; location-driven rules — professional tax, labour welfare fund, holidays — resolve at the workplace, which is where they actually apply.
The mistake that survives every happy-path test
Professional tax follows the place of work, not the registered address. A system that reads entity state instead of workplace state produces correct-looking output for every single-location company and quietly wrong output for the multi-location ones — which is precisely the case you bought a multi-entity system for.
Country profiles carry the statutory rules
Where a group operates across countries, the statutory pack and the fiscal year come from the country profile rather than from code. Adding a country is a configuration exercise, and the entities already running are unaffected by it.
Where each rule resolves
Company
The group. Users, branding and the modules you have switched on.
Legal entity
Registrations, statutory numbers, fiscal year, filings. Employees belong here.
Workplace
Professional tax, labour welfare fund and holidays resolve from the actual place of work.
Country profile
The statutory pack and fiscal year that the entity inherits, configured rather than coded.
Multi-Entity & Multi-Country FAQs
Can we run several companies in one account?
Yes — that is the design, not an accommodation. Each legal entity keeps its own statutory setup, financial year, holiday calendars and registrations, while your team works from one place with scope following their role. The alternative most groups live with — one entity's rules quietly applied to another's payroll — is how the wrong PF number reaches the wrong return, and it is the specific mess this exists to prevent.
Do policies have to be identical across entities?
No, and they usually cannot be: two entities in different states rarely share holidays, professional tax, welfare-fund obligations or even a financial-year convention when one is foreign-parented. Statutory profiles, leave rules and calendars resolve per entity and location, so each company is right by its own rules rather than approximately right by somebody else's.
Can one person work across entities without seeing everything?
Scope follows role per entity, so a group accountant can span companies while a plant HR sees only theirs. Reporting respects the same boundaries. The failure this prevents is the familiar one — a shared login with group-wide visibility because setting up proper access felt like work — which is how salary data travels far beyond anyone's intention.
What about transfers between entities?
A transfer is a placement change with history, not a delete-and-recreate: the person's record carries their past employment in the group, while statutory treatment switches cleanly to the receiving entity from the effective date. Full-and-final in one entity and joining in another, where that is the correct treatment, are both produced from the same spine rather than reconstructed by hand.
Is multi-entity an enterprise-priced add-on?
No — it is how the product is built, and billing stays per active employee with modules you switch off unbilled. A second entity is configuration, not a commercial negotiation. Groups of two and three companies are normal in Indian SMB manufacturing and services; pricing that punishes the structure your business already has would be pricing against our own market.
Do the entities share one compliance calendar?
Each entity carries its own obligations — its registrations, due dates and state-specific filings — surfaced together so the person responsible sees everything, attributed correctly. The dangerous version is a single merged list where one entity's PT deadline is assumed to cover the group; here every obligation belongs to a named entity, because that is how the penalty notice will be addressed too.
See it on your own data
Fourteen days, no card. Load a handful of employees and judge it against how you work today.