Appearance
Groups and sites
A group is a processing partition inside the company: runs and exports split on it, attendance can be marked by it, and — for labour contractors and multi-state companies — a group can be a site with its own location, registrations and contract details.
Where: People → Employees → Groups (the button beside the list). Who: the administrator or anyone with edit employees.
Membership is organisational, never statutory — moving someone between groups changes who files for them, not what they are paid.
Create a group
- Groups → type the New group name → Add group.
- Employees join a group at hire (the group field on Add employee), from the import wizard's department column, or on their Details page. The list shows each group's member count; N member(s) with no group is "the absence of a group" and cannot be edited.
A group with members cannot be deleted — reassign them first; deleting never silently un-groups anyone.
Make a group a site
Site… on the group row opens Site & compliance:
- Location state — blank = the company's state. This decides the PT slabs and the LWF for the site's employees (precedence: employee override → group site → structure → company).
- Registrations — pick the code this site files under per kind: PF, ESIC, PT, LWF. Codes are added under Configurations → Compliance → Registrations; PT and LWF registrations must belong to the site's state. No pick = the company's default code. No registration numbers entered yet — the group will file under the company's codes.
- Statutory overrides for this group — PF / ESIC / PT parameters that apply to this site only, with reason and audit exactly like company overrides.
- Contract (for the statutory registers) — Principal employer, its address, nature of work, work location, Contract / work order no. These print on the CLRA registers (wages, muster roll, advances, fines, damage).
- Save site.
What changes once sites exist
- PF ECR and ESIC MC downloads produce one file per registration, zipped, with a README naming which employees fell under which code.
- Registers can be produced per site and carry the principal employer and contract.
- The attendance register can be marked per attendance group — an employee's attendance group may differ from their payroll group (a worker paid under head office but marked at a site).
- Moving a worker between sites is a group change on the employee's Details; months already processed stay under the old code, the next run files under the new one.
The other cases
Same company, two states. One group per state with its location state set; employees in each group get that state's PT and LWF automatically.
A contractor's worker moves site. Change the group on his Details before running the month he moves in; that month and onward file under the new site's code. A split within one month is not supported — pick the site he worked the majority of the month at.
A site without a PT registration. Leave PT unpicked — it files under the company's default; if the company has none in that state, add the registration first.